From 05dedace84ef8c93fea5309c3ac55f889011429b Mon Sep 17 00:00:00 2001
From: CVS to git conversion script <webmaster@postgresql.org>
Date: Thu, 20 Jun 2002 20:29:55 +0000
Subject: This commit was manufactured by cvs2git to create branch
 'ecpg_big_bison'.

Sprout from master 2002-06-20 20:29:54 UTC Bruce Momjian <bruce@momjian.us> 'Update copyright to 2002.'
Delete:
    COPYRIGHT
    GNUmakefile.in
    HISTORY
    INSTALL
    Makefile
    README
    aclocal.m4
    config/ac_func_accept_argtypes.m4
    config/c-compiler.m4
    config/c-library.m4
    config/config.guess
    config/config.sub
    config/cxx.m4
    config/docbook.m4
    config/general.m4
    config/install-sh
    config/java.m4
    config/libtool.m4
    config/missing
    config/mkinstalldirs
    config/perl.m4
    config/prep_buildtree
    config/programs.m4
    config/python.m4
    config/tcl.m4
    configure
    configure.in
    contrib/Makefile
    contrib/README
    contrib/array/Makefile
    contrib/array/README.array_iterator
    contrib/array/array_iterator.c
    contrib/array/array_iterator.h
    contrib/array/array_iterator.sql.in
    contrib/btree_gist/Makefile
    contrib/btree_gist/README.btree_gist
    contrib/btree_gist/btree_gist.c
    contrib/btree_gist/btree_gist.sql.in
    contrib/btree_gist/data/test_btree.data
    contrib/btree_gist/data/test_btree_ts.data
    contrib/btree_gist/expected/btree_gist.out
    contrib/btree_gist/sql/btree_gist.sql
    contrib/chkpass/Makefile
    contrib/chkpass/README.chkpass
    contrib/chkpass/chkpass.c
    contrib/chkpass/chkpass.sql.in
    contrib/contrib-global.mk
    contrib/cube/Makefile
    contrib/cube/README.cube
    contrib/cube/buffer.c
    contrib/cube/buffer.h
    contrib/cube/cube.c
    contrib/cube/cube.sql.in
    contrib/cube/cubedata.h
    contrib/cube/cubeparse.y
    contrib/cube/cubescan.l
    contrib/cube/data/test_cube.data
    contrib/cube/expected/cube.out
    contrib/cube/sql/cube.sql
    contrib/dbase/Makefile
    contrib/dbase/README.dbf2pg
    contrib/dbase/dbf.c
    contrib/dbase/dbf.h
    contrib/dbase/dbf2pg.1
    contrib/dbase/dbf2pg.c
    contrib/dbase/endian.c
    contrib/dblink/Makefile
    contrib/dblink/README.dblink
    contrib/dblink/dblink.c
    contrib/dblink/dblink.h
    contrib/dblink/dblink.sql.in
    contrib/dbsize/Makefile
    contrib/dbsize/README.dbsize
    contrib/dbsize/dbsize.c
    contrib/dbsize/dbsize.sql.in
    contrib/earthdistance/Makefile
    contrib/earthdistance/README.earthdistance
    contrib/earthdistance/earthdistance.c
    contrib/earthdistance/earthdistance.sql.in
    contrib/findoidjoins/Makefile
    contrib/findoidjoins/README.findoidjoins
    contrib/findoidjoins/findoidjoins.c
    contrib/findoidjoins/make_oidjoins_check
    contrib/fulltextindex/Makefile
    contrib/fulltextindex/README.fti
    contrib/fulltextindex/TODO
    contrib/fulltextindex/fti.c
    contrib/fulltextindex/fti.pl
    contrib/fulltextindex/fti.sql.in
    contrib/fulltextindex/timings.sh
    contrib/fuzzystrmatch/Makefile
    contrib/fuzzystrmatch/README.fuzzystrmatch
    contrib/fuzzystrmatch/README.soundex
    contrib/fuzzystrmatch/fuzzystrmatch.c
    contrib/fuzzystrmatch/fuzzystrmatch.h
    contrib/fuzzystrmatch/fuzzystrmatch.sql.in
    contrib/intagg/Makefile
    contrib/intagg/README.int_aggregate
    contrib/intagg/int_aggregate.c
    contrib/intagg/int_aggregate.sql.in
    contrib/intarray/Makefile
    contrib/intarray/README.intarray
    contrib/intarray/_int.c
    contrib/intarray/_int.sql.in
    contrib/intarray/bench/bench.pl
    contrib/intarray/bench/create_test.pl
    contrib/intarray/data/test__int.data
    contrib/intarray/expected/_int.out
    contrib/intarray/sql/_int.sql
    contrib/ipc_check/README
    contrib/ipc_check/ipc_check.pl
    contrib/isbn_issn/Makefile
    contrib/isbn_issn/README.isbn_issn
    contrib/isbn_issn/isbn_issn.c
    contrib/isbn_issn/isbn_issn.sql.in
    contrib/lo/Makefile
    contrib/lo/README.lo
    contrib/lo/lo.c
    contrib/lo/lo.sql.in
    contrib/lo/lo_drop.sql
    contrib/lo/lo_test.sql
    contrib/mSQL-interface/Makefile
    contrib/mSQL-interface/README.mpgsql
    contrib/mSQL-interface/mpgsql.c
    contrib/mac/README.mac
    contrib/mac/createoui
    contrib/mac/dropoui
    contrib/mac/ouiparse.awk
    contrib/mac/updateoui
    contrib/miscutil/Makefile
    contrib/miscutil/README.misc_utils
    contrib/miscutil/misc_utils.c
    contrib/miscutil/misc_utils.h
    contrib/miscutil/misc_utils.sql.in
    contrib/mysql/README
    contrib/mysql/my2pg.pl
    contrib/mysql/mysql2pgsql
    contrib/noupdate/Makefile
    contrib/noupdate/README.noup
    contrib/noupdate/noup.c
    contrib/noupdate/noup.sql.in
    contrib/oid2name/Makefile
    contrib/oid2name/README.oid2name
    contrib/oid2name/oid2name.c
    contrib/oracle/CHANGES
    contrib/oracle/Ora2Pg.pm
    contrib/oracle/README.ora2pg
    contrib/oracle/TODO
    contrib/oracle/ora2pg.html
    contrib/oracle/ora2pg.pl
    contrib/pg_controldata/Makefile
    contrib/pg_controldata/README.pg_controldata
    contrib/pg_controldata/pg_controldata.c
    contrib/pg_dumplo/Makefile
    contrib/pg_dumplo/README.pg_dumplo
    contrib/pg_dumplo/lo_export.c
    contrib/pg_dumplo/lo_import.c
    contrib/pg_dumplo/main.c
    contrib/pg_dumplo/pg_dumplo.h
    contrib/pg_dumplo/utils.c
    contrib/pg_logger/Makefile
    contrib/pg_logger/README.pg_logger
    contrib/pg_logger/pg_logger.c
    contrib/pg_resetxlog/Makefile
    contrib/pg_resetxlog/README.pg_resetxlog
    contrib/pg_resetxlog/pg_resetxlog.c
    contrib/pg_upgrade/README
    contrib/pg_upgrade/pg_upgrade
    contrib/pg_upgrade/pg_upgrade.1
    contrib/pgbench/Makefile
    contrib/pgbench/README.pgbench
    contrib/pgbench/README.pgbench_jis
    contrib/pgbench/pgbench.c
    contrib/pgcrypto/API
    contrib/pgcrypto/Makefile
    contrib/pgcrypto/README.pgcrypto
    contrib/pgcrypto/blf.c
    contrib/pgcrypto/blf.h
    contrib/pgcrypto/crypt-blowfish.c
    contrib/pgcrypto/crypt-des.c
    contrib/pgcrypto/crypt-gensalt.c
    contrib/pgcrypto/crypt-md5.c
    contrib/pgcrypto/expected/blowfish.out
    contrib/pgcrypto/expected/crypt-blowfish.out
    contrib/pgcrypto/expected/crypt-des.out
    contrib/pgcrypto/expected/crypt-md5.out
    contrib/pgcrypto/expected/crypt-xdes.out
    contrib/pgcrypto/expected/hmac-md5.out
    contrib/pgcrypto/expected/hmac-sha1.out
    contrib/pgcrypto/expected/init.out
    contrib/pgcrypto/expected/md5.out
    contrib/pgcrypto/expected/rijndael.out
    contrib/pgcrypto/expected/sha1.out
    contrib/pgcrypto/internal.c
    contrib/pgcrypto/md5.c
    contrib/pgcrypto/md5.h
    contrib/pgcrypto/mhash.c
    contrib/pgcrypto/misc.c
    contrib/pgcrypto/openssl.c
    contrib/pgcrypto/pgcrypto.c
    contrib/pgcrypto/pgcrypto.h
    contrib/pgcrypto/pgcrypto.sql.in
    contrib/pgcrypto/px-crypt.c
    contrib/pgcrypto/px-crypt.h
    contrib/pgcrypto/px-hmac.c
    contrib/pgcrypto/px.c
    contrib/pgcrypto/px.h
    contrib/pgcrypto/random.c
    contrib/pgcrypto/rijndael.c
    contrib/pgcrypto/rijndael.h
    contrib/pgcrypto/rijndael.tbl
    contrib/pgcrypto/sha1.c
    contrib/pgcrypto/sha1.h
    contrib/pgcrypto/sql/blowfish.sql
    contrib/pgcrypto/sql/crypt-blowfish.sql
    contrib/pgcrypto/sql/crypt-des.sql
    contrib/pgcrypto/sql/crypt-md5.sql
    contrib/pgcrypto/sql/crypt-xdes.sql
    contrib/pgcrypto/sql/hmac-md5.sql
    contrib/pgcrypto/sql/hmac-sha1.sql
    contrib/pgcrypto/sql/init.sql
    contrib/pgcrypto/sql/md5.sql
    contrib/pgcrypto/sql/rijndael.sql
    contrib/pgcrypto/sql/sha1.sql
    contrib/pgstattuple/Makefile
    contrib/pgstattuple/README.pgstattuple
    contrib/pgstattuple/README.pgstattuple.euc_jp
    contrib/pgstattuple/pgstattuple.c
    contrib/pgstattuple/pgstattuple.sql.in
    contrib/retep/CHANGELOG
    contrib/retep/Implementation
    contrib/retep/Makefile
    contrib/retep/README
    contrib/retep/build.xml
    contrib/retep/data/cds.dtd
    contrib/retep/data/cds.xml
    contrib/retep/retep.jpx
    contrib/retep/uk/org/retep/dtu/DCollection.java
    contrib/retep/uk/org/retep/dtu/DConstants.java
    contrib/retep/uk/org/retep/dtu/DElement.java
    contrib/retep/uk/org/retep/dtu/DEnvironment.java
    contrib/retep/uk/org/retep/dtu/DModule.java
    contrib/retep/uk/org/retep/dtu/DModuleXML.java
    contrib/retep/uk/org/retep/dtu/DNode.java
    contrib/retep/uk/org/retep/dtu/DProcessor.java
    contrib/retep/uk/org/retep/dtu/DTransform.java
    contrib/retep/uk/org/retep/tools/Tool.java
    contrib/retep/uk/org/retep/tools.properties
    contrib/retep/uk/org/retep/util/ExceptionDialog.java
    contrib/retep/uk/org/retep/util/Globals.java
    contrib/retep/uk/org/retep/util/Logger.java
    contrib/retep/uk/org/retep/util/Main.java
    contrib/retep/uk/org/retep/util/StandaloneApp.java
    contrib/retep/uk/org/retep/util/hba/Editor.java
    contrib/retep/uk/org/retep/util/hba/Main.java
    contrib/retep/uk/org/retep/util/hba/Record.java
    contrib/retep/uk/org/retep/util/misc/IPAddress.java
    contrib/retep/uk/org/retep/util/misc/PropertiesIO.java
    contrib/retep/uk/org/retep/util/misc/WStringTokenizer.java
    contrib/retep/uk/org/retep/util/models/HBATableModel.java
    contrib/retep/uk/org/retep/util/models/PropertiesTableModel.java
    contrib/retep/uk/org/retep/util/proped/Main.java
    contrib/retep/uk/org/retep/util/proped/PropertyEditor.java
    contrib/retep/uk/org/retep/xml/core/XMLFactory.java
    contrib/retep/uk/org/retep/xml/core/XMLFactoryException.java
    contrib/retep/uk/org/retep/xml/jdbc/XMLDatabase.java
    contrib/retep/uk/org/retep/xml/jdbc/XMLResultSet.java
    contrib/retep/uk/org/retep/xml/parser/TagHandler.java
    contrib/retep/uk/org/retep/xml/parser/TagListener.java
    contrib/retep/uk/org/retep/xml/test/XMLExport.java
    contrib/rserv/ApplySnapshot.in
    contrib/rserv/CleanLog.in
    contrib/rserv/GetSyncID.in
    contrib/rserv/InitRservTest.in
    contrib/rserv/Makefile
    contrib/rserv/MasterAddTable.in
    contrib/rserv/MasterInit.in
    contrib/rserv/MasterSync.in
    contrib/rserv/PrepareSnapshot.in
    contrib/rserv/README.rserv
    contrib/rserv/RServ.pm
    contrib/rserv/Replicate.in
    contrib/rserv/RservTest.in
    contrib/rserv/SlaveAddTable.in
    contrib/rserv/SlaveInit.in
    contrib/rserv/master.sql.in
    contrib/rserv/regress.sh
    contrib/rserv/rserv.c
    contrib/rserv/slave.sql.in
    contrib/rtree_gist/Makefile
    contrib/rtree_gist/README.rtree_gist
    contrib/rtree_gist/bench/bench.pl
    contrib/rtree_gist/bench/create_test.pl
    contrib/rtree_gist/data/test_box.data
    contrib/rtree_gist/expected/rtree_gist.out
    contrib/rtree_gist/rtree_gist.c
    contrib/rtree_gist/rtree_gist.sql.in
    contrib/rtree_gist/sql/rtree_gist.sql
    contrib/seg/Makefile
    contrib/seg/README.seg
    contrib/seg/buffer.c
    contrib/seg/buffer.h
    contrib/seg/data/test_seg.data
    contrib/seg/expected/seg.out
    contrib/seg/seg-validate.pl
    contrib/seg/seg.c
    contrib/seg/seg.sql.in
    contrib/seg/segdata.h
    contrib/seg/segparse.y
    contrib/seg/segscan.l
    contrib/seg/sort-segments.pl
    contrib/seg/sql/seg.sql
    contrib/spi/Makefile
    contrib/spi/README.spi
    contrib/spi/autoinc.c
    contrib/spi/autoinc.example
    contrib/spi/autoinc.sql.in
    contrib/spi/insert_username.c
    contrib/spi/insert_username.example
    contrib/spi/insert_username.sql.in
    contrib/spi/moddatetime.c
    contrib/spi/moddatetime.example
    contrib/spi/moddatetime.sql.in
    contrib/spi/preprocessor/README.MAX
    contrib/spi/preprocessor/example.sql
    contrib/spi/preprocessor/step1.c
    contrib/spi/preprocessor/step1.e
    contrib/spi/preprocessor/step2.pl
    contrib/spi/refint.c
    contrib/spi/refint.example
    contrib/spi/refint.sql.in
    contrib/spi/timetravel.c
    contrib/spi/timetravel.example
    contrib/spi/timetravel.sql.in
    contrib/start-scripts/freebsd
    contrib/start-scripts/linux
    contrib/string/Makefile
    contrib/string/README.string_io
    contrib/string/string_io.c
    contrib/string/string_io.h
    contrib/string/string_io.sql.in
    contrib/tips/Makefile
    contrib/tips/README.apachelog
    contrib/tools/add-emacs-variables
    contrib/tools/find-sources
    contrib/tools/make-tags
    contrib/tsearch/Makefile
    contrib/tsearch/README.tsearch
    contrib/tsearch/crc32.c
    contrib/tsearch/crc32.h
    contrib/tsearch/data/test_tsearch.data
    contrib/tsearch/deflex.h
    contrib/tsearch/dict/porter_english.dct
    contrib/tsearch/dict/russian_stemming.dct
    contrib/tsearch/dict.h
    contrib/tsearch/expected/tsearch.out
    contrib/tsearch/gistidx.c
    contrib/tsearch/gistidx.h
    contrib/tsearch/makedict/makedict.pl
    contrib/tsearch/morph.c
    contrib/tsearch/morph.h
    contrib/tsearch/parser.h
    contrib/tsearch/parser.l
    contrib/tsearch/query.c
    contrib/tsearch/query.h
    contrib/tsearch/rewrite.c
    contrib/tsearch/rewrite.h
    contrib/tsearch/sql/tsearch.sql
    contrib/tsearch/tsearch.sql.in
    contrib/tsearch/txtidx.c
    contrib/tsearch/txtidx.h
    contrib/userlock/Makefile
    contrib/userlock/README.user_locks
    contrib/userlock/user_locks.c
    contrib/userlock/user_locks.h
    contrib/userlock/user_locks.sql.in
    contrib/vacuumlo/Makefile
    contrib/vacuumlo/README.vacuumlo
    contrib/vacuumlo/vacuumlo.c
    contrib/xml/Makefile
    contrib/xml/README
    contrib/xml/TODO
    contrib/xml/pgxml.c
    contrib/xml/pgxml.h
    contrib/xml/pgxml.source
    contrib/xml/pgxml_dom.c
    contrib/xml/pgxml_dom.source
    doc/FAQ
    doc/FAQ_AIX
    doc/FAQ_DEV
    doc/FAQ_HPUX
    doc/FAQ_IRIX
    doc/FAQ_MSWIN
    doc/FAQ_QNX4
    doc/FAQ_SCO
    doc/FAQ_Solaris
    doc/FAQ_german
    doc/FAQ_japanese
    doc/FAQ_polish
    doc/FAQ_russian
    doc/KNOWN_BUGS
    doc/MISSING_FEATURES
    doc/Makefile
    doc/README.mb.big5
    doc/README.mb.jp
    doc/TODO
    doc/TODO.detail/README
    doc/TODO.detail/atttypmod
    doc/TODO.detail/crossdb
    doc/TODO.detail/cursor
    doc/TODO.detail/drop
    doc/TODO.detail/exists
    doc/TODO.detail/foreign
    doc/TODO.detail/fsync
    doc/TODO.detail/inheritance
    doc/TODO.detail/java
    doc/TODO.detail/mmap
    doc/TODO.detail/namedatalen
    doc/TODO.detail/optimizer
    doc/TODO.detail/performance
    doc/TODO.detail/persistent
    doc/TODO.detail/pool
    doc/TODO.detail/prepare
    doc/TODO.detail/privileges
    doc/TODO.detail/replication
    doc/TODO.detail/schema
    doc/TODO.detail/tablespaces
    doc/TODO.detail/thread
    doc/TODO.detail/transactions
    doc/TODO.detail/typeconv
    doc/TODO.detail/update
    doc/TODO.detail/vacuum
    doc/TODO.detail/view
    doc/TODO.detail/win32
    doc/TODO.detail/yacc
    doc/bug.template
    doc/src/FAQ/FAQ.html
    doc/src/FAQ/FAQ_DEV.html
    doc/src/FAQ/FAQ_german.html
    doc/src/FAQ/FAQ_japanese.html
    doc/src/FAQ/FAQ_polish.html
    doc/src/FAQ/FAQ_russian.html
    doc/src/Makefile
    doc/src/graphics/catalogs.ag
    doc/src/graphics/catalogs.cgm
    doc/src/graphics/catalogs.gif
    doc/src/graphics/catalogs.ps
    doc/src/graphics/clientserver.ag
    doc/src/graphics/clientserver.gif
    doc/src/graphics/connections.ag
    doc/src/graphics/connections.gif
    doc/src/sgml/Makefile
    doc/src/sgml/admin.sgml
    doc/src/sgml/advanced.sgml
    doc/src/sgml/arch-dev.sgml
    doc/src/sgml/arch-pg.sgml
    doc/src/sgml/array.sgml
    doc/src/sgml/backup.sgml
    doc/src/sgml/biblio.sgml
    doc/src/sgml/bki.sgml
    doc/src/sgml/book-decl.sgml
    doc/src/sgml/catalogs.sgml
    doc/src/sgml/charset.sgml
    doc/src/sgml/client-auth.sgml
    doc/src/sgml/compiler.sgml
    doc/src/sgml/contacts.sgml
    doc/src/sgml/cvs.sgml
    doc/src/sgml/datatype.sgml
    doc/src/sgml/datetime.sgml
    doc/src/sgml/developer.sgml
    doc/src/sgml/dfunc.sgml
    doc/src/sgml/diskusage.sgml
    doc/src/sgml/docguide.sgml
    doc/src/sgml/ecpg.sgml
    doc/src/sgml/extend.sgml
    doc/src/sgml/features.sgml
    doc/src/sgml/filelist.sgml
    doc/src/sgml/fixrtf
    doc/src/sgml/func-ref.sgml
    doc/src/sgml/func.sgml
    doc/src/sgml/geqo.sgml
    doc/src/sgml/gist.sgml
    doc/src/sgml/history.sgml
    doc/src/sgml/indexcost.sgml
    doc/src/sgml/indices.sgml
    doc/src/sgml/info.sgml
    doc/src/sgml/inherit.sgml
    doc/src/sgml/install-win32.sgml
    doc/src/sgml/installation.sgml
    doc/src/sgml/intro.sgml
    doc/src/sgml/jdbc.sgml
    doc/src/sgml/keywords.sgml
    doc/src/sgml/legal.sgml
    doc/src/sgml/libpgeasy.sgml
    doc/src/sgml/libpgtcl.sgml
    doc/src/sgml/libpq++.sgml
    doc/src/sgml/libpq.sgml
    doc/src/sgml/lobj.sgml
    doc/src/sgml/maintenance.sgml
    doc/src/sgml/manage-ag.sgml
    doc/src/sgml/manage.sgml
    doc/src/sgml/monitoring.sgml
    doc/src/sgml/mvcc.sgml
    doc/src/sgml/nls.sgml
    doc/src/sgml/notation.sgml
    doc/src/sgml/odbc.sgml
    doc/src/sgml/page.sgml
    doc/src/sgml/perform.sgml
    doc/src/sgml/plperl.sgml
    doc/src/sgml/plpython.sgml
    doc/src/sgml/plsql.sgml
    doc/src/sgml/pltcl.sgml
    doc/src/sgml/postgres.sgml
    doc/src/sgml/problems.sgml
    doc/src/sgml/programmer.sgml
    doc/src/sgml/protocol.sgml
    doc/src/sgml/pygresql.sgml
    doc/src/sgml/queries.sgml
    doc/src/sgml/query.sgml
    doc/src/sgml/recovery.sgml
    doc/src/sgml/ref/abort.sgml
    doc/src/sgml/ref/allfiles.sgml
    doc/src/sgml/ref/alter_database.sgml
    doc/src/sgml/ref/alter_group.sgml
    doc/src/sgml/ref/alter_table.sgml
    doc/src/sgml/ref/alter_trigger.sgml
    doc/src/sgml/ref/alter_user.sgml
    doc/src/sgml/ref/analyze.sgml
    doc/src/sgml/ref/begin.sgml
    doc/src/sgml/ref/checkpoint.sgml
    doc/src/sgml/ref/close.sgml
    doc/src/sgml/ref/cluster.sgml
    doc/src/sgml/ref/comment.sgml
    doc/src/sgml/ref/commit.sgml
    doc/src/sgml/ref/copy.sgml
    doc/src/sgml/ref/create_aggregate.sgml
    doc/src/sgml/ref/create_constraint.sgml
    doc/src/sgml/ref/create_database.sgml
    doc/src/sgml/ref/create_domain.sgml
    doc/src/sgml/ref/create_function.sgml
    doc/src/sgml/ref/create_group.sgml
    doc/src/sgml/ref/create_index.sgml
    doc/src/sgml/ref/create_language.sgml
    doc/src/sgml/ref/create_operator.sgml
    doc/src/sgml/ref/create_rule.sgml
    doc/src/sgml/ref/create_schema.sgml
    doc/src/sgml/ref/create_sequence.sgml
    doc/src/sgml/ref/create_table.sgml
    doc/src/sgml/ref/create_table_as.sgml
    doc/src/sgml/ref/create_trigger.sgml
    doc/src/sgml/ref/create_type.sgml
    doc/src/sgml/ref/create_user.sgml
    doc/src/sgml/ref/create_view.sgml
    doc/src/sgml/ref/createdb.sgml
    doc/src/sgml/ref/createlang.sgml
    doc/src/sgml/ref/createuser.sgml
    doc/src/sgml/ref/current_date.sgml
    doc/src/sgml/ref/current_time.sgml
    doc/src/sgml/ref/current_timestamp.sgml
    doc/src/sgml/ref/current_user.sgml
    doc/src/sgml/ref/declare.sgml
    doc/src/sgml/ref/delete.sgml
    doc/src/sgml/ref/drop_aggregate.sgml
    doc/src/sgml/ref/drop_database.sgml
    doc/src/sgml/ref/drop_domain.sgml
    doc/src/sgml/ref/drop_function.sgml
    doc/src/sgml/ref/drop_group.sgml
    doc/src/sgml/ref/drop_index.sgml
    doc/src/sgml/ref/drop_language.sgml
    doc/src/sgml/ref/drop_operator.sgml
    doc/src/sgml/ref/drop_rule.sgml
    doc/src/sgml/ref/drop_sequence.sgml
    doc/src/sgml/ref/drop_table.sgml
    doc/src/sgml/ref/drop_trigger.sgml
    doc/src/sgml/ref/drop_type.sgml
    doc/src/sgml/ref/drop_user.sgml
    doc/src/sgml/ref/drop_view.sgml
    doc/src/sgml/ref/dropdb.sgml
    doc/src/sgml/ref/droplang.sgml
    doc/src/sgml/ref/dropuser.sgml
    doc/src/sgml/ref/ecpg-ref.sgml
    doc/src/sgml/ref/end.sgml
    doc/src/sgml/ref/explain.sgml
    doc/src/sgml/ref/fetch.sgml
    doc/src/sgml/ref/grant.sgml
    doc/src/sgml/ref/initdb.sgml
    doc/src/sgml/ref/initlocation.sgml
    doc/src/sgml/ref/insert.sgml
    doc/src/sgml/ref/ipcclean.sgml
    doc/src/sgml/ref/listen.sgml
    doc/src/sgml/ref/load.sgml
    doc/src/sgml/ref/lock.sgml
    doc/src/sgml/ref/move.sgml
    doc/src/sgml/ref/notify.sgml
    doc/src/sgml/ref/pg_config-ref.sgml
    doc/src/sgml/ref/pg_ctl-ref.sgml
    doc/src/sgml/ref/pg_dump.sgml
    doc/src/sgml/ref/pg_dumpall.sgml
    doc/src/sgml/ref/pg_restore.sgml
    doc/src/sgml/ref/pgaccess-ref.sgml
    doc/src/sgml/ref/pgtclsh.sgml
    doc/src/sgml/ref/pgtksh.sgml
    doc/src/sgml/ref/postgres-ref.sgml
    doc/src/sgml/ref/postmaster.sgml
    doc/src/sgml/ref/psql-ref.sgml
    doc/src/sgml/ref/reindex.sgml
    doc/src/sgml/ref/reset.sgml
    doc/src/sgml/ref/revoke.sgml
    doc/src/sgml/ref/rollback.sgml
    doc/src/sgml/ref/select.sgml
    doc/src/sgml/ref/select_into.sgml
    doc/src/sgml/ref/set.sgml
    doc/src/sgml/ref/set_constraints.sgml
    doc/src/sgml/ref/set_session_auth.sgml
    doc/src/sgml/ref/set_transaction.sgml
    doc/src/sgml/ref/show.sgml
    doc/src/sgml/ref/truncate.sgml
    doc/src/sgml/ref/unlisten.sgml
    doc/src/sgml/ref/update.sgml
    doc/src/sgml/ref/vacuum.sgml
    doc/src/sgml/ref/vacuumdb.sgml
    doc/src/sgml/refentry.sgml
    doc/src/sgml/reference.ced
    doc/src/sgml/reference.sgml
    doc/src/sgml/regress.sgml
    doc/src/sgml/release.sgml
    doc/src/sgml/rules.sgml
    doc/src/sgml/runtime.sgml
    doc/src/sgml/sources.sgml
    doc/src/sgml/spi.sgml
    doc/src/sgml/sql.sgml
    doc/src/sgml/standalone-install.sgml
    doc/src/sgml/start.sgml
    doc/src/sgml/stylesheet.css
    doc/src/sgml/stylesheet.dsl
    doc/src/sgml/syntax.sgml
    doc/src/sgml/trigger.sgml
    doc/src/sgml/tutorial.sgml
    doc/src/sgml/typeconv.sgml
    doc/src/sgml/user-manag.sgml
    doc/src/sgml/user.sgml
    doc/src/sgml/version.sgml
    doc/src/sgml/wal.sgml
    doc/src/sgml/xaggr.sgml
    doc/src/sgml/xfunc.sgml
    doc/src/sgml/xindex.sgml
    doc/src/sgml/xoper.sgml
    doc/src/sgml/xplang.sgml
    doc/src/sgml/xtypes.sgml
    doc/src/sgml/y2k.sgml
    register.txt
    src/DEVELOPERS
    src/Makefile
    src/Makefile.global.in
    src/Makefile.shlib
    src/backend/Makefile
    src/backend/access/Makefile
    src/backend/access/common/Makefile
    src/backend/access/common/heaptuple.c
    src/backend/access/common/indextuple.c
    src/backend/access/common/indexvalid.c
    src/backend/access/common/printtup.c
    src/backend/access/common/scankey.c
    src/backend/access/common/tupdesc.c
    src/backend/access/gist/Makefile
    src/backend/access/gist/gist.c
    src/backend/access/gist/gistget.c
    src/backend/access/gist/gistscan.c
    src/backend/access/gist/giststrat.c
    src/backend/access/hash/Makefile
    src/backend/access/hash/hash.c
    src/backend/access/hash/hashfunc.c
    src/backend/access/hash/hashinsert.c
    src/backend/access/hash/hashovfl.c
    src/backend/access/hash/hashpage.c
    src/backend/access/hash/hashscan.c
    src/backend/access/hash/hashsearch.c
    src/backend/access/hash/hashstrat.c
    src/backend/access/hash/hashutil.c
    src/backend/access/heap/Makefile
    src/backend/access/heap/heapam.c
    src/backend/access/heap/hio.c
    src/backend/access/heap/tuptoaster.c
    src/backend/access/index/Makefile
    src/backend/access/index/genam.c
    src/backend/access/index/indexam.c
    src/backend/access/index/istrat.c
    src/backend/access/nbtree/Makefile
    src/backend/access/nbtree/README
    src/backend/access/nbtree/nbtcompare.c
    src/backend/access/nbtree/nbtinsert.c
    src/backend/access/nbtree/nbtpage.c
    src/backend/access/nbtree/nbtree.c
    src/backend/access/nbtree/nbtsearch.c
    src/backend/access/nbtree/nbtsort.c
    src/backend/access/nbtree/nbtstrat.c
    src/backend/access/nbtree/nbtutils.c
    src/backend/access/rtree/Makefile
    src/backend/access/rtree/rtget.c
    src/backend/access/rtree/rtproc.c
    src/backend/access/rtree/rtree.c
    src/backend/access/rtree/rtscan.c
    src/backend/access/rtree/rtstrat.c
    src/backend/access/transam/Makefile
    src/backend/access/transam/clog.c
    src/backend/access/transam/rmgr.c
    src/backend/access/transam/transam.c
    src/backend/access/transam/varsup.c
    src/backend/access/transam/xact.c
    src/backend/access/transam/xid.c
    src/backend/access/transam/xlog.c
    src/backend/access/transam/xlogutils.c
    src/backend/bootstrap/.cvsignore
    src/backend/bootstrap/Makefile
    src/backend/bootstrap/bootparse.y
    src/backend/bootstrap/bootscanner.l
    src/backend/bootstrap/bootstrap.c
    src/backend/catalog/Makefile
    src/backend/catalog/README
    src/backend/catalog/aclchk.c
    src/backend/catalog/catalog.c
    src/backend/catalog/genbki.sh
    src/backend/catalog/heap.c
    src/backend/catalog/index.c
    src/backend/catalog/indexing.c
    src/backend/catalog/namespace.c
    src/backend/catalog/pg_aggregate.c
    src/backend/catalog/pg_largeobject.c
    src/backend/catalog/pg_namespace.c
    src/backend/catalog/pg_operator.c
    src/backend/catalog/pg_proc.c
    src/backend/catalog/pg_type.c
    src/backend/commands/Makefile
    src/backend/commands/_deadcode/recipe.c
    src/backend/commands/_deadcode/recipe.h
    src/backend/commands/_deadcode/version.c
    src/backend/commands/aggregatecmds.c
    src/backend/commands/analyze.c
    src/backend/commands/async.c
    src/backend/commands/cluster.c
    src/backend/commands/comment.c
    src/backend/commands/copy.c
    src/backend/commands/dbcommands.c
    src/backend/commands/define.c
    src/backend/commands/explain.c
    src/backend/commands/functioncmds.c
    src/backend/commands/indexcmds.c
    src/backend/commands/lockcmds.c
    src/backend/commands/operatorcmds.c
    src/backend/commands/portalcmds.c
    src/backend/commands/proclang.c
    src/backend/commands/schemacmds.c
    src/backend/commands/sequence.c
    src/backend/commands/tablecmds.c
    src/backend/commands/trigger.c
    src/backend/commands/typecmds.c
    src/backend/commands/user.c
    src/backend/commands/vacuum.c
    src/backend/commands/vacuumlazy.c
    src/backend/commands/variable.c
    src/backend/commands/view.c
    src/backend/executor/Makefile
    src/backend/executor/README
    src/backend/executor/_deadcode/nodeTee.c
    src/backend/executor/execAmi.c
    src/backend/executor/execJunk.c
    src/backend/executor/execMain.c
    src/backend/executor/execProcnode.c
    src/backend/executor/execQual.c
    src/backend/executor/execScan.c
    src/backend/executor/execTuples.c
    src/backend/executor/execUtils.c
    src/backend/executor/functions.c
    src/backend/executor/instrument.c
    src/backend/executor/nodeAgg.c
    src/backend/executor/nodeAppend.c
    src/backend/executor/nodeFunctionscan.c
    src/backend/executor/nodeGroup.c
    src/backend/executor/nodeHash.c
    src/backend/executor/nodeHashjoin.c
    src/backend/executor/nodeIndexscan.c
    src/backend/executor/nodeLimit.c
    src/backend/executor/nodeMaterial.c
    src/backend/executor/nodeMergejoin.c
    src/backend/executor/nodeNestloop.c
    src/backend/executor/nodeResult.c
    src/backend/executor/nodeSeqscan.c
    src/backend/executor/nodeSetOp.c
    src/backend/executor/nodeSort.c
    src/backend/executor/nodeSubplan.c
    src/backend/executor/nodeSubqueryscan.c
    src/backend/executor/nodeTidscan.c
    src/backend/executor/nodeUnique.c
    src/backend/executor/spi.c
    src/backend/lib/Makefile
    src/backend/lib/bit.c
    src/backend/lib/dllist.c
    src/backend/lib/lispsort.c
    src/backend/lib/stringinfo.c
    src/backend/libpq/Makefile
    src/backend/libpq/README.SSL
    src/backend/libpq/auth.c
    src/backend/libpq/be-fsstubs.c
    src/backend/libpq/be-secure.c
    src/backend/libpq/crypt.c
    src/backend/libpq/hba.c
    src/backend/libpq/md5.c
    src/backend/libpq/pg_hba.conf.sample
    src/backend/libpq/pg_ident.conf.sample
    src/backend/libpq/pqcomm.c
    src/backend/libpq/pqformat.c
    src/backend/libpq/pqsignal.c
    src/backend/main/Makefile
    src/backend/main/main.c
    src/backend/nodes/Makefile
    src/backend/nodes/README
    src/backend/nodes/copyfuncs.c
    src/backend/nodes/equalfuncs.c
    src/backend/nodes/list.c
    src/backend/nodes/makefuncs.c
    src/backend/nodes/nodeFuncs.c
    src/backend/nodes/nodes.c
    src/backend/nodes/outfuncs.c
    src/backend/nodes/print.c
    src/backend/nodes/read.c
    src/backend/nodes/readfuncs.c
    src/backend/optimizer/Makefile
    src/backend/optimizer/README
    src/backend/optimizer/geqo/Makefile
    src/backend/optimizer/geqo/geqo_copy.c
    src/backend/optimizer/geqo/geqo_cx.c
    src/backend/optimizer/geqo/geqo_erx.c
    src/backend/optimizer/geqo/geqo_eval.c
    src/backend/optimizer/geqo/geqo_main.c
    src/backend/optimizer/geqo/geqo_misc.c
    src/backend/optimizer/geqo/geqo_mutation.c
    src/backend/optimizer/geqo/geqo_ox1.c
    src/backend/optimizer/geqo/geqo_ox2.c
    src/backend/optimizer/geqo/geqo_pmx.c
    src/backend/optimizer/geqo/geqo_pool.c
    src/backend/optimizer/geqo/geqo_px.c
    src/backend/optimizer/geqo/geqo_recombination.c
    src/backend/optimizer/geqo/geqo_selection.c
    src/backend/optimizer/path/Makefile
    src/backend/optimizer/path/_deadcode/predmig.c
    src/backend/optimizer/path/_deadcode/xfunc.c
    src/backend/optimizer/path/allpaths.c
    src/backend/optimizer/path/clausesel.c
    src/backend/optimizer/path/costsize.c
    src/backend/optimizer/path/indxpath.c
    src/backend/optimizer/path/joinpath.c
    src/backend/optimizer/path/joinrels.c
    src/backend/optimizer/path/orindxpath.c
    src/backend/optimizer/path/pathkeys.c
    src/backend/optimizer/path/tidpath.c
    src/backend/optimizer/plan/Makefile
    src/backend/optimizer/plan/README
    src/backend/optimizer/plan/createplan.c
    src/backend/optimizer/plan/initsplan.c
    src/backend/optimizer/plan/planmain.c
    src/backend/optimizer/plan/planner.c
    src/backend/optimizer/plan/setrefs.c
    src/backend/optimizer/plan/subselect.c
    src/backend/optimizer/prep/Makefile
    src/backend/optimizer/prep/_deadcode/prepkeyset.c
    src/backend/optimizer/prep/prepqual.c
    src/backend/optimizer/prep/preptlist.c
    src/backend/optimizer/prep/prepunion.c
    src/backend/optimizer/util/Makefile
    src/backend/optimizer/util/clauses.c
    src/backend/optimizer/util/joininfo.c
    src/backend/optimizer/util/pathnode.c
    src/backend/optimizer/util/plancat.c
    src/backend/optimizer/util/relnode.c
    src/backend/optimizer/util/restrictinfo.c
    src/backend/optimizer/util/tlist.c
    src/backend/optimizer/util/var.c
    src/backend/parser/.cvsignore
    src/backend/parser/Makefile
    src/backend/parser/README
    src/backend/parser/analyze.c
    src/backend/parser/gram.y
    src/backend/parser/keywords.c
    src/backend/parser/parse_agg.c
    src/backend/parser/parse_clause.c
    src/backend/parser/parse_coerce.c
    src/backend/parser/parse_expr.c
    src/backend/parser/parse_func.c
    src/backend/parser/parse_node.c
    src/backend/parser/parse_oper.c
    src/backend/parser/parse_relation.c
    src/backend/parser/parse_target.c
    src/backend/parser/parse_type.c
    src/backend/parser/parser.c
    src/backend/parser/scan.l
    src/backend/parser/scansup.c
    src/backend/po/Makefile
    src/backend/po/cs.po
    src/backend/po/de.po
    src/backend/po/hu.po
    src/backend/po/nls.mk
    src/backend/po/ru.po
    src/backend/po/zh_CN.po
    src/backend/po/zh_TW.po
    src/backend/port/Makefile
    src/backend/port/aix/mkldexport.sh
    src/backend/port/beos/Makefile
    src/backend/port/beos/sem.c
    src/backend/port/beos/shm.c
    src/backend/port/beos/support.c
    src/backend/port/darwin/Makefile
    src/backend/port/darwin/README
    src/backend/port/darwin/system.c
    src/backend/port/dynloader/README.dlfcn.aix
    src/backend/port/dynloader/aix.c
    src/backend/port/dynloader/aix.h
    src/backend/port/dynloader/beos.c
    src/backend/port/dynloader/beos.h
    src/backend/port/dynloader/bsdi.c
    src/backend/port/dynloader/bsdi.h
    src/backend/port/dynloader/darwin.c
    src/backend/port/dynloader/darwin.h
    src/backend/port/dynloader/dgux.c
    src/backend/port/dynloader/dgux.h
    src/backend/port/dynloader/freebsd.c
    src/backend/port/dynloader/freebsd.h
    src/backend/port/dynloader/hpux.c
    src/backend/port/dynloader/hpux.h
    src/backend/port/dynloader/irix5.c
    src/backend/port/dynloader/irix5.h
    src/backend/port/dynloader/linux.c
    src/backend/port/dynloader/linux.h
    src/backend/port/dynloader/netbsd.c
    src/backend/port/dynloader/netbsd.h
    src/backend/port/dynloader/nextstep.c
    src/backend/port/dynloader/nextstep.h
    src/backend/port/dynloader/openbsd.c
    src/backend/port/dynloader/openbsd.h
    src/backend/port/dynloader/osf.c
    src/backend/port/dynloader/osf.h
    src/backend/port/dynloader/qnx4.c
    src/backend/port/dynloader/qnx4.h
    src/backend/port/dynloader/sco.c
    src/backend/port/dynloader/sco.h
    src/backend/port/dynloader/solaris.c
    src/backend/port/dynloader/solaris.h
    src/backend/port/dynloader/sunos4.c
    src/backend/port/dynloader/sunos4.h
    src/backend/port/dynloader/svr4.c
    src/backend/port/dynloader/svr4.h
    src/backend/port/dynloader/ultrix4.c
    src/backend/port/dynloader/ultrix4.h
    src/backend/port/dynloader/univel.c
    src/backend/port/dynloader/univel.h
    src/backend/port/dynloader/unixware.c
    src/backend/port/dynloader/unixware.h
    src/backend/port/dynloader/win.c
    src/backend/port/dynloader/win.h
    src/backend/port/gethostname.c
    src/backend/port/getrusage.c
    src/backend/port/hpux/tas.c.template
    src/backend/port/inet_aton.c
    src/backend/port/inet_aton.h
    src/backend/port/ipc_test.c
    src/backend/port/isinf.c
    src/backend/port/memcmp.c
    src/backend/port/nextstep/Makefile
    src/backend/port/nextstep/port.c
    src/backend/port/posix_sema.c
    src/backend/port/qnx4/Makefile
    src/backend/port/qnx4/ipc.h
    src/backend/port/qnx4/isnan.c
    src/backend/port/qnx4/rint.c
    src/backend/port/qnx4/sem.c
    src/backend/port/qnx4/sem.h
    src/backend/port/qnx4/shm.c
    src/backend/port/qnx4/shm.h
    src/backend/port/qnx4/tstrint.c
    src/backend/port/qnx4/tstsem.c
    src/backend/port/qnx4/tstshm.c
    src/backend/port/random.c
    src/backend/port/snprintf.c
    src/backend/port/srandom.c
    src/backend/port/strcasecmp.c
    src/backend/port/strerror.c
    src/backend/port/strtol.c
    src/backend/port/strtoul.c
    src/backend/port/sunos4/Makefile
    src/backend/port/sunos4/float.h
    src/backend/port/sysv_sema.c
    src/backend/port/sysv_shmem.c
    src/backend/port/tas/dummy.s
    src/backend/port/tas/hpux.s
    src/backend/port/tas/solaris_i386.s
    src/backend/port/tas/solaris_sparc.s
    src/backend/postmaster/Makefile
    src/backend/postmaster/pgstat.c
    src/backend/postmaster/postmaster.c
    src/backend/regex/COPYRIGHT
    src/backend/regex/Makefile
    src/backend/regex/WHATSNEW
    src/backend/regex/engine.c
    src/backend/regex/re_format.7
    src/backend/regex/regcomp.c
    src/backend/regex/regerror.c
    src/backend/regex/regex.3
    src/backend/regex/regexec.c
    src/backend/regex/regfree.c
    src/backend/regex/retest.c
    src/backend/rewrite/Makefile
    src/backend/rewrite/rewriteDefine.c
    src/backend/rewrite/rewriteHandler.c
    src/backend/rewrite/rewriteManip.c
    src/backend/rewrite/rewriteRemove.c
    src/backend/rewrite/rewriteSupport.c
    src/backend/storage/Makefile
    src/backend/storage/buffer/Makefile
    src/backend/storage/buffer/README
    src/backend/storage/buffer/buf_init.c
    src/backend/storage/buffer/buf_table.c
    src/backend/storage/buffer/bufmgr.c
    src/backend/storage/buffer/freelist.c
    src/backend/storage/buffer/localbuf.c
    src/backend/storage/file/Makefile
    src/backend/storage/file/buffile.c
    src/backend/storage/file/fd.c
    src/backend/storage/freespace/Makefile
    src/backend/storage/freespace/freespace.c
    src/backend/storage/ipc/Makefile
    src/backend/storage/ipc/README
    src/backend/storage/ipc/ipc.c
    src/backend/storage/ipc/ipci.c
    src/backend/storage/ipc/pmsignal.c
    src/backend/storage/ipc/shmem.c
    src/backend/storage/ipc/shmqueue.c
    src/backend/storage/ipc/sinval.c
    src/backend/storage/ipc/sinvaladt.c
    src/backend/storage/large_object/Makefile
    src/backend/storage/large_object/inv_api.c
    src/backend/storage/lmgr/Makefile
    src/backend/storage/lmgr/README
    src/backend/storage/lmgr/deadlock.c
    src/backend/storage/lmgr/lmgr.c
    src/backend/storage/lmgr/lock.c
    src/backend/storage/lmgr/lwlock.c
    src/backend/storage/lmgr/proc.c
    src/backend/storage/lmgr/s_lock.c
    src/backend/storage/lmgr/spin.c
    src/backend/storage/page/Makefile
    src/backend/storage/page/bufpage.c
    src/backend/storage/page/itemptr.c
    src/backend/storage/smgr/Makefile
    src/backend/storage/smgr/README
    src/backend/storage/smgr/md.c
    src/backend/storage/smgr/mm.c
    src/backend/storage/smgr/smgr.c
    src/backend/storage/smgr/smgrtype.c
    src/backend/tcop/Makefile
    src/backend/tcop/dest.c
    src/backend/tcop/fastpath.c
    src/backend/tcop/postgres.c
    src/backend/tcop/pquery.c
    src/backend/tcop/utility.c
    src/backend/tioga/Arr_TgRecipe.h
    src/backend/tioga/Makefile
    src/backend/tioga/Varray.c
    src/backend/tioga/Varray.h
    src/backend/tioga/tgRecipe.c
    src/backend/tioga/tgRecipe.h
    src/backend/utils/.cvsignore
    src/backend/utils/Gen_fmgrtab.sh
    src/backend/utils/Makefile
    src/backend/utils/adt/Makefile
    src/backend/utils/adt/acl.c
    src/backend/utils/adt/arrayfuncs.c
    src/backend/utils/adt/arrayutils.c
    src/backend/utils/adt/ascii.c
    src/backend/utils/adt/bool.c
    src/backend/utils/adt/cash.c
    src/backend/utils/adt/char.c
    src/backend/utils/adt/date.c
    src/backend/utils/adt/datetime.c
    src/backend/utils/adt/datum.c
    src/backend/utils/adt/encode.c
    src/backend/utils/adt/float.c
    src/backend/utils/adt/format_type.c
    src/backend/utils/adt/formatting.c
    src/backend/utils/adt/geo_ops.c
    src/backend/utils/adt/geo_selfuncs.c
    src/backend/utils/adt/inet_net_ntop.c
    src/backend/utils/adt/inet_net_pton.c
    src/backend/utils/adt/int.c
    src/backend/utils/adt/int8.c
    src/backend/utils/adt/like.c
    src/backend/utils/adt/like_match.c
    src/backend/utils/adt/mac.c
    src/backend/utils/adt/misc.c
    src/backend/utils/adt/nabstime.c
    src/backend/utils/adt/name.c
    src/backend/utils/adt/network.c
    src/backend/utils/adt/not_in.c
    src/backend/utils/adt/numeric.c
    src/backend/utils/adt/numutils.c
    src/backend/utils/adt/oid.c
    src/backend/utils/adt/oracle_compat.c
    src/backend/utils/adt/pg_locale.c
    src/backend/utils/adt/pg_lzcompress.c
    src/backend/utils/adt/pgstatfuncs.c
    src/backend/utils/adt/quote.c
    src/backend/utils/adt/regexp.c
    src/backend/utils/adt/regproc.c
    src/backend/utils/adt/ri_triggers.c
    src/backend/utils/adt/ruleutils.c
    src/backend/utils/adt/selfuncs.c
    src/backend/utils/adt/sets.c
    src/backend/utils/adt/tid.c
    src/backend/utils/adt/timestamp.c
    src/backend/utils/adt/varbit.c
    src/backend/utils/adt/varchar.c
    src/backend/utils/adt/varlena.c
    src/backend/utils/adt/version.c
    src/backend/utils/cache/Makefile
    src/backend/utils/cache/catcache.c
    src/backend/utils/cache/fcache.c
    src/backend/utils/cache/inval.c
    src/backend/utils/cache/lsyscache.c
    src/backend/utils/cache/relcache.c
    src/backend/utils/cache/syscache.c
    src/backend/utils/error/Makefile
    src/backend/utils/error/assert.c
    src/backend/utils/error/elog.c
    src/backend/utils/error/exc.c
    src/backend/utils/error/excabort.c
    src/backend/utils/error/excid.c
    src/backend/utils/error/format.c
    src/backend/utils/fmgr/Makefile
    src/backend/utils/fmgr/README
    src/backend/utils/fmgr/dfmgr.c
    src/backend/utils/fmgr/fmgr.c
    src/backend/utils/hash/Makefile
    src/backend/utils/hash/dynahash.c
    src/backend/utils/hash/hashfn.c
    src/backend/utils/hash/pg_crc.c
    src/backend/utils/init/Makefile
    src/backend/utils/init/findbe.c
    src/backend/utils/init/globals.c
    src/backend/utils/init/miscinit.c
    src/backend/utils/init/postinit.c
    src/backend/utils/mb/Makefile
    src/backend/utils/mb/README
    src/backend/utils/mb/Unicode/ISO10646-GB18030.TXT
    src/backend/utils/mb/Unicode/Makefile
    src/backend/utils/mb/Unicode/UCS_to_8859.pl
    src/backend/utils/mb/Unicode/UCS_to_BIG5.pl
    src/backend/utils/mb/Unicode/UCS_to_EUC_CN.pl
    src/backend/utils/mb/Unicode/UCS_to_EUC_JP.pl
    src/backend/utils/mb/Unicode/UCS_to_EUC_KR.pl
    src/backend/utils/mb/Unicode/UCS_to_EUC_TW.pl
    src/backend/utils/mb/Unicode/UCS_to_GB18030.pl
    src/backend/utils/mb/Unicode/UCS_to_GBK.pl
    src/backend/utils/mb/Unicode/UCS_to_JOHAB.pl
    src/backend/utils/mb/Unicode/UCS_to_SJIS.pl
    src/backend/utils/mb/Unicode/UCS_to_UHC.pl
    src/backend/utils/mb/Unicode/UCS_to_WIN874.pl
    src/backend/utils/mb/Unicode/UCS_to_WINX.pl
    src/backend/utils/mb/Unicode/UCS_to_cyrillic.pl
    src/backend/utils/mb/Unicode/alt_to_utf8.map
    src/backend/utils/mb/Unicode/big5_to_utf8.map
    src/backend/utils/mb/Unicode/euc_cn_to_utf8.map
    src/backend/utils/mb/Unicode/euc_jp_to_utf8.map
    src/backend/utils/mb/Unicode/euc_kr_to_utf8.map
    src/backend/utils/mb/Unicode/euc_tw_to_utf8.map
    src/backend/utils/mb/Unicode/gb18030_to_utf8.map
    src/backend/utils/mb/Unicode/gbk_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_10_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_13_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_14_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_15_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_16_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_2_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_3_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_4_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_5_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_6_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_7_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_8_to_utf8.map
    src/backend/utils/mb/Unicode/iso8859_9_to_utf8.map
    src/backend/utils/mb/Unicode/johab_to_utf8.map
    src/backend/utils/mb/Unicode/koi8r_to_utf8.map
    src/backend/utils/mb/Unicode/sjis_to_utf8.map
    src/backend/utils/mb/Unicode/tcvn_to_utf8.map
    src/backend/utils/mb/Unicode/ucs2utf.pl
    src/backend/utils/mb/Unicode/uhc_to_utf8.map
    src/backend/utils/mb/Unicode/utf8_to_alt.map
    src/backend/utils/mb/Unicode/utf8_to_big5.map
    src/backend/utils/mb/Unicode/utf8_to_euc_cn.map
    src/backend/utils/mb/Unicode/utf8_to_euc_jp.map
    src/backend/utils/mb/Unicode/utf8_to_euc_kr.map
    src/backend/utils/mb/Unicode/utf8_to_euc_tw.map
    src/backend/utils/mb/Unicode/utf8_to_gb18030.map
    src/backend/utils/mb/Unicode/utf8_to_gbk.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_10.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_13.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_14.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_15.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_16.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_2.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_3.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_4.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_5.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_6.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_7.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_8.map
    src/backend/utils/mb/Unicode/utf8_to_iso8859_9.map
    src/backend/utils/mb/Unicode/utf8_to_johab.map
    src/backend/utils/mb/Unicode/utf8_to_koi8r.map
    src/backend/utils/mb/Unicode/utf8_to_sjis.map
    src/backend/utils/mb/Unicode/utf8_to_tcvn.map
    src/backend/utils/mb/Unicode/utf8_to_uhc.map
    src/backend/utils/mb/Unicode/utf8_to_win1250.map
    src/backend/utils/mb/Unicode/utf8_to_win1251.map
    src/backend/utils/mb/Unicode/utf8_to_win1256.map
    src/backend/utils/mb/Unicode/utf8_to_win874.map
    src/backend/utils/mb/Unicode/win1250_to_utf8.map
    src/backend/utils/mb/Unicode/win1251_to_utf8.map
    src/backend/utils/mb/Unicode/win1256_to_utf8.map
    src/backend/utils/mb/Unicode/win874_to_utf8.map
    src/backend/utils/mb/alt.c
    src/backend/utils/mb/big5.c
    src/backend/utils/mb/conv.c
    src/backend/utils/mb/encnames.c
    src/backend/utils/mb/iso.c
    src/backend/utils/mb/mbutils.c
    src/backend/utils/mb/sjis.map
    src/backend/utils/mb/wchar.c
    src/backend/utils/mb/win.c
    src/backend/utils/mb/win1251.c
    src/backend/utils/mb/wstrcmp.c
    src/backend/utils/mb/wstrncmp.c
    src/backend/utils/misc/.cvsignore
    src/backend/utils/misc/Makefile
    src/backend/utils/misc/README
    src/backend/utils/misc/database.c
    src/backend/utils/misc/guc-file.l
    src/backend/utils/misc/guc.c
    src/backend/utils/misc/postgresql.conf.sample
    src/backend/utils/misc/ps_status.c
    src/backend/utils/misc/superuser.c
    src/backend/utils/mmgr/Makefile
    src/backend/utils/mmgr/README
    src/backend/utils/mmgr/aset.c
    src/backend/utils/mmgr/mcxt.c
    src/backend/utils/mmgr/portalmem.c
    src/backend/utils/sort/Makefile
    src/backend/utils/sort/logtape.c
    src/backend/utils/sort/tuplesort.c
    src/backend/utils/sort/tuplestore.c
    src/backend/utils/time/Makefile
    src/backend/utils/time/tqual.c
    src/bin/Makefile
    src/bin/initdb/Makefile
    src/bin/initdb/initdb.sh
    src/bin/initlocation/Makefile
    src/bin/initlocation/initlocation.sh
    src/bin/ipcclean/Makefile
    src/bin/ipcclean/ipcclean.sh
    src/bin/pg_config/Makefile
    src/bin/pg_config/pg_config.sh
    src/bin/pg_ctl/Makefile
    src/bin/pg_ctl/pg_ctl.sh
    src/bin/pg_dump/Makefile
    src/bin/pg_dump/README
    src/bin/pg_dump/common.c
    src/bin/pg_dump/cs.po
    src/bin/pg_dump/de.po
    src/bin/pg_dump/nls.mk
    src/bin/pg_dump/pg_backup.h
    src/bin/pg_dump/pg_backup_archiver.c
    src/bin/pg_dump/pg_backup_archiver.h
    src/bin/pg_dump/pg_backup_custom.c
    src/bin/pg_dump/pg_backup_db.c
    src/bin/pg_dump/pg_backup_db.h
    src/bin/pg_dump/pg_backup_files.c
    src/bin/pg_dump/pg_backup_null.c
    src/bin/pg_dump/pg_backup_tar.c
    src/bin/pg_dump/pg_backup_tar.h
    src/bin/pg_dump/pg_dump.c
    src/bin/pg_dump/pg_dump.h
    src/bin/pg_dump/pg_dumpall.sh
    src/bin/pg_dump/pg_restore.c
    src/bin/pg_dump/ru.po
    src/bin/pg_dump/sv.po
    src/bin/pg_dump/zh_CN.po
    src/bin/pg_dump/zh_TW.po
    src/bin/pg_encoding/Makefile
    src/bin/pg_encoding/pg_encoding.c
    src/bin/pg_id/Makefile
    src/bin/pg_id/pg_id.c
    src/bin/pgaccess/Makefile
    src/bin/pgaccess/README
    src/bin/pgaccess/copyright.html
    src/bin/pgaccess/demo/formdemo.sql
    src/bin/pgaccess/doc/html/a_right.gif
    src/bin/pgaccess/doc/html/addindex.gif
    src/bin/pgaccess/doc/html/api.html
    src/bin/pgaccess/doc/html/ball.gif
    src/bin/pgaccess/doc/html/contents.html
    src/bin/pgaccess/doc/html/copyright.html
    src/bin/pgaccess/doc/html/documentation.html
    src/bin/pgaccess/doc/html/download.html
    src/bin/pgaccess/doc/html/faq.html
    src/bin/pgaccess/doc/html/features.html
    src/bin/pgaccess/doc/html/formdemo.sql
    src/bin/pgaccess/doc/html/forms.gif
    src/bin/pgaccess/doc/html/forms.html
    src/bin/pgaccess/doc/html/function.gif
    src/bin/pgaccess/doc/html/help.gif
    src/bin/pgaccess/doc/html/index.html
    src/bin/pgaccess/doc/html/irix.html
    src/bin/pgaccess/doc/html/linux1.gif
    src/bin/pgaccess/doc/html/maillist.html
    src/bin/pgaccess/doc/html/main.html
    src/bin/pgaccess/doc/html/mainwindow.gif
    src/bin/pgaccess/doc/html/newtable.gif
    src/bin/pgaccess/doc/html/newuser.gif
    src/bin/pgaccess/doc/html/old_index.html
    src/bin/pgaccess/doc/html/permissions.gif
    src/bin/pgaccess/doc/html/pg93patch.html
    src/bin/pgaccess/doc/html/pga-rad.html
    src/bin/pgaccess/doc/html/qbtclet.html
    src/bin/pgaccess/doc/html/qbtclet.tcl
    src/bin/pgaccess/doc/html/screenshots.html
    src/bin/pgaccess/doc/html/specialchars.html
    src/bin/pgaccess/doc/html/todo.html
    src/bin/pgaccess/doc/html/tutorial/addref.jpg
    src/bin/pgaccess/doc/html/tutorial/altern_q.jpg
    src/bin/pgaccess/doc/html/tutorial/altern_v.jpg
    src/bin/pgaccess/doc/html/tutorial/copyright.html
    src/bin/pgaccess/doc/html/tutorial/index.html
    src/bin/pgaccess/doc/html/tutorial/intro.html
    src/bin/pgaccess/doc/html/tutorial/irix.html
    src/bin/pgaccess/doc/html/tutorial/newref.txt
    src/bin/pgaccess/doc/html/tutorial/newtable.jpg
    src/bin/pgaccess/doc/html/tutorial/newtable.tga
    src/bin/pgaccess/doc/html/tutorial/problems.html
    src/bin/pgaccess/doc/html/tutorial/screen1.jpg
    src/bin/pgaccess/doc/html/tutorial/sel_tbl.jpg
    src/bin/pgaccess/doc/html/tutorial/start.html
    src/bin/pgaccess/doc/html/tutorial/tut.html
    src/bin/pgaccess/doc/html/tutorial/tut_edit.html
    src/bin/pgaccess/doc/html/tutorial/tut_new.html
    src/bin/pgaccess/doc/html/tutorial/tut_sel1.html
    src/bin/pgaccess/doc/html/tutorial/tut_user.html
    src/bin/pgaccess/doc/html/vdesigner.gif
    src/bin/pgaccess/doc/html/whatsnew.html
    src/bin/pgaccess/doc/html/win32.html
    src/bin/pgaccess/images/icon_button.gif
    src/bin/pgaccess/images/icon_checkbutton.gif
    src/bin/pgaccess/images/icon_entry.gif
    src/bin/pgaccess/images/icon_frame.gif
    src/bin/pgaccess/images/icon_label.gif
    src/bin/pgaccess/images/icon_listbox.gif
    src/bin/pgaccess/images/icon_query.gif
    src/bin/pgaccess/images/icon_radiobutton.gif
    src/bin/pgaccess/images/icon_text.gif
    src/bin/pgaccess/lib/database.tcl
    src/bin/pgaccess/lib/forms.tcl
    src/bin/pgaccess/lib/functions.tcl
    src/bin/pgaccess/lib/help/abort.hlp
    src/bin/pgaccess/lib/help/add_records.hlp
    src/bin/pgaccess/lib/help/alter_table.hlp
    src/bin/pgaccess/lib/help/alter_user.hlp
    src/bin/pgaccess/lib/help/author.hlp
    src/bin/pgaccess/lib/help/begin.hlp
    src/bin/pgaccess/lib/help/close.hlp
    src/bin/pgaccess/lib/help/cluster.hlp
    src/bin/pgaccess/lib/help/commit.hlp
    src/bin/pgaccess/lib/help/copy.hlp
    src/bin/pgaccess/lib/help/copyrights.hlp
    src/bin/pgaccess/lib/help/create_aggregate.hlp
    src/bin/pgaccess/lib/help/create_database.hlp
    src/bin/pgaccess/lib/help/create_function.hlp
    src/bin/pgaccess/lib/help/create_index.hlp
    src/bin/pgaccess/lib/help/create_language.hlp
    src/bin/pgaccess/lib/help/create_operator.hlp
    src/bin/pgaccess/lib/help/create_rule.hlp
    src/bin/pgaccess/lib/help/create_sequence.hlp
    src/bin/pgaccess/lib/help/create_table.hlp
    src/bin/pgaccess/lib/help/create_table_as.hlp
    src/bin/pgaccess/lib/help/create_trigger.hlp
    src/bin/pgaccess/lib/help/create_type.hlp
    src/bin/pgaccess/lib/help/create_user.hlp
    src/bin/pgaccess/lib/help/create_view.hlp
    src/bin/pgaccess/lib/help/data_types.hlp
    src/bin/pgaccess/lib/help/datefunc.hlp
    src/bin/pgaccess/lib/help/declare.hlp
    src/bin/pgaccess/lib/help/delete.hlp
    src/bin/pgaccess/lib/help/drop_aggregate.hlp
    src/bin/pgaccess/lib/help/drop_database.hlp
    src/bin/pgaccess/lib/help/drop_function.hlp
    src/bin/pgaccess/lib/help/drop_index.hlp
    src/bin/pgaccess/lib/help/drop_language.hlp
    src/bin/pgaccess/lib/help/drop_operator.hlp
    src/bin/pgaccess/lib/help/drop_rule.hlp
    src/bin/pgaccess/lib/help/drop_sequence.hlp
    src/bin/pgaccess/lib/help/drop_table.hlp
    src/bin/pgaccess/lib/help/drop_trigger.hlp
    src/bin/pgaccess/lib/help/drop_type.hlp
    src/bin/pgaccess/lib/help/drop_user.hlp
    src/bin/pgaccess/lib/help/drop_view.hlp
    src/bin/pgaccess/lib/help/explain.hlp
    src/bin/pgaccess/lib/help/fetch.hlp
    src/bin/pgaccess/lib/help/form_design.hlp
    src/bin/pgaccess/lib/help/forms.hlp
    src/bin/pgaccess/lib/help/functions.hlp
    src/bin/pgaccess/lib/help/geomfunc.hlp
    src/bin/pgaccess/lib/help/grant.hlp
    src/bin/pgaccess/lib/help/history.hlp
    src/bin/pgaccess/lib/help/index.hlp
    src/bin/pgaccess/lib/help/inheritance.hlp
    src/bin/pgaccess/lib/help/insert.hlp
    src/bin/pgaccess/lib/help/ipv4func.hlp
    src/bin/pgaccess/lib/help/isolation.hlp
    src/bin/pgaccess/lib/help/keywords.hlp
    src/bin/pgaccess/lib/help/listen.hlp
    src/bin/pgaccess/lib/help/load.hlp
    src/bin/pgaccess/lib/help/lock.hlp
    src/bin/pgaccess/lib/help/mathfunc.hlp
    src/bin/pgaccess/lib/help/move.hlp
    src/bin/pgaccess/lib/help/mvcc.hlp
    src/bin/pgaccess/lib/help/new_query.hlp
    src/bin/pgaccess/lib/help/new_table.hlp
    src/bin/pgaccess/lib/help/notify.hlp
    src/bin/pgaccess/lib/help/open_query.hlp
    src/bin/pgaccess/lib/help/open_table.hlp
    src/bin/pgaccess/lib/help/pgfunctions.hlp
    src/bin/pgaccess/lib/help/postgresql.hlp
    src/bin/pgaccess/lib/help/queries.hlp
    src/bin/pgaccess/lib/help/reports.hlp
    src/bin/pgaccess/lib/help/reset.hlp
    src/bin/pgaccess/lib/help/revoke.hlp
    src/bin/pgaccess/lib/help/rollback.hlp
    src/bin/pgaccess/lib/help/schema.hlp
    src/bin/pgaccess/lib/help/scripts.hlp
    src/bin/pgaccess/lib/help/select.hlp
    src/bin/pgaccess/lib/help/select_into.hlp
    src/bin/pgaccess/lib/help/sequences.hlp
    src/bin/pgaccess/lib/help/set.hlp
    src/bin/pgaccess/lib/help/show.hlp
    src/bin/pgaccess/lib/help/sql_guide.hlp
    src/bin/pgaccess/lib/help/sqlfunc.hlp
    src/bin/pgaccess/lib/help/stringfunc.hlp
    src/bin/pgaccess/lib/help/tables.hlp
    src/bin/pgaccess/lib/help/unlisten.hlp
    src/bin/pgaccess/lib/help/update.hlp
    src/bin/pgaccess/lib/help/users.hlp
    src/bin/pgaccess/lib/help/vacuum.hlp
    src/bin/pgaccess/lib/help/view_table_structure.hlp
    src/bin/pgaccess/lib/help/views.hlp
    src/bin/pgaccess/lib/help/visual_designer.hlp
    src/bin/pgaccess/lib/help/y2k.hlp
    src/bin/pgaccess/lib/help.tcl
    src/bin/pgaccess/lib/languages/chinese_big5
    src/bin/pgaccess/lib/languages/chinese_gb
    src/bin/pgaccess/lib/languages/czech
    src/bin/pgaccess/lib/languages/deutsch
    src/bin/pgaccess/lib/languages/euskara
    src/bin/pgaccess/lib/languages/francais
    src/bin/pgaccess/lib/languages/italiano
    src/bin/pgaccess/lib/languages/japanese
    src/bin/pgaccess/lib/languages/magyar
    src/bin/pgaccess/lib/languages/nederlands
    src/bin/pgaccess/lib/languages/portugues
    src/bin/pgaccess/lib/languages/romana
    src/bin/pgaccess/lib/languages/russian.koi8r
    src/bin/pgaccess/lib/languages/russian_win
    src/bin/pgaccess/lib/languages/spanish
    src/bin/pgaccess/lib/mainlib.tcl
    src/bin/pgaccess/lib/preferences.tcl
    src/bin/pgaccess/lib/queries.tcl
    src/bin/pgaccess/lib/reports.tcl
    src/bin/pgaccess/lib/schema.tcl
    src/bin/pgaccess/lib/scripts.tcl
    src/bin/pgaccess/lib/sequences.tcl
    src/bin/pgaccess/lib/tables.tcl
    src/bin/pgaccess/lib/users.tcl
    src/bin/pgaccess/lib/views.tcl
    src/bin/pgaccess/lib/visualqb.tcl
    src/bin/pgaccess/main.tcl
    src/bin/pgaccess/pgaccess.sh
    src/bin/pgtclsh/Makefile
    src/bin/pgtclsh/README
    src/bin/pgtclsh/pgtclAppInit.c
    src/bin/pgtclsh/pgtclUtils.tcl
    src/bin/pgtclsh/pgtkAppInit.c
    src/bin/pgtclsh/updateStats.tcl
    src/bin/psql/.cvsignore
    src/bin/psql/Makefile
    src/bin/psql/command.c
    src/bin/psql/command.h
    src/bin/psql/common.c
    src/bin/psql/common.h
    src/bin/psql/copy.c
    src/bin/psql/copy.h
    src/bin/psql/create_help.pl
    src/bin/psql/cs.po
    src/bin/psql/de.po
    src/bin/psql/describe.c
    src/bin/psql/describe.h
    src/bin/psql/fr.po
    src/bin/psql/help.c
    src/bin/psql/help.h
    src/bin/psql/input.c
    src/bin/psql/input.h
    src/bin/psql/large_obj.c
    src/bin/psql/large_obj.h
    src/bin/psql/mainloop.c
    src/bin/psql/mainloop.h
    src/bin/psql/mbprint.c
    src/bin/psql/mbprint.h
    src/bin/psql/nls.mk
    src/bin/psql/print.c
    src/bin/psql/print.h
    src/bin/psql/prompt.c
    src/bin/psql/prompt.h
    src/bin/psql/ru.po
    src/bin/psql/settings.h
    src/bin/psql/startup.c
    src/bin/psql/stringutils.c
    src/bin/psql/stringutils.h
    src/bin/psql/sv.po
    src/bin/psql/tab-complete.c
    src/bin/psql/tab-complete.h
    src/bin/psql/variables.c
    src/bin/psql/variables.h
    src/bin/psql/win32.mak
    src/bin/psql/zh_CN.po
    src/bin/psql/zh_TW.po
    src/bin/scripts/Makefile
    src/bin/scripts/createdb
    src/bin/scripts/createlang.sh
    src/bin/scripts/createuser
    src/bin/scripts/dropdb
    src/bin/scripts/droplang
    src/bin/scripts/dropuser
    src/bin/scripts/vacuumdb
    src/corba/CosQuery.idl
    src/corba/CosQueryCollection.idl
    src/corba/pgsql.idl
    src/corba/pgsql_int.idl
    src/corba/server.cc
    src/data/charset.conf
    src/data/isocz-wincz.tab
    src/data/koi-alt.tab
    src/data/koi-iso.tab
    src/data/koi-koi.tab
    src/data/koi-mac.tab
    src/data/koi-win.tab
    src/include/Makefile
    src/include/access/attnum.h
    src/include/access/clog.h
    src/include/access/genam.h
    src/include/access/gist.h
    src/include/access/gistscan.h
    src/include/access/hash.h
    src/include/access/heapam.h
    src/include/access/hio.h
    src/include/access/htup.h
    src/include/access/ibit.h
    src/include/access/iqual.h
    src/include/access/istrat.h
    src/include/access/itup.h
    src/include/access/nbtree.h
    src/include/access/printtup.h
    src/include/access/relscan.h
    src/include/access/rmgr.h
    src/include/access/rtree.h
    src/include/access/rtscan.h
    src/include/access/sdir.h
    src/include/access/skey.h
    src/include/access/strat.h
    src/include/access/transam.h
    src/include/access/tupdesc.h
    src/include/access/tupmacs.h
    src/include/access/tuptoaster.h
    src/include/access/valid.h
    src/include/access/xact.h
    src/include/access/xlog.h
    src/include/access/xlogdefs.h
    src/include/access/xlogutils.h
    src/include/bootstrap/bootstrap.h
    src/include/c.h
    src/include/catalog/catalog.h
    src/include/catalog/catname.h
    src/include/catalog/catversion.h
    src/include/catalog/duplicate_oids
    src/include/catalog/heap.h
    src/include/catalog/index.h
    src/include/catalog/indexing.h
    src/include/catalog/namespace.h
    src/include/catalog/pg_aggregate.h
    src/include/catalog/pg_am.h
    src/include/catalog/pg_amop.h
    src/include/catalog/pg_amproc.h
    src/include/catalog/pg_attrdef.h
    src/include/catalog/pg_attribute.h
    src/include/catalog/pg_class.h
    src/include/catalog/pg_control.h
    src/include/catalog/pg_database.h
    src/include/catalog/pg_description.h
    src/include/catalog/pg_group.h
    src/include/catalog/pg_index.h
    src/include/catalog/pg_inherits.h
    src/include/catalog/pg_language.h
    src/include/catalog/pg_largeobject.h
    src/include/catalog/pg_listener.h
    src/include/catalog/pg_namespace.h
    src/include/catalog/pg_opclass.h
    src/include/catalog/pg_operator.h
    src/include/catalog/pg_proc.h
    src/include/catalog/pg_relcheck.h
    src/include/catalog/pg_rewrite.h
    src/include/catalog/pg_shadow.h
    src/include/catalog/pg_statistic.h
    src/include/catalog/pg_trigger.h
    src/include/catalog/pg_type.h
    src/include/catalog/pg_version.h
    src/include/catalog/unused_oids
    src/include/commands/async.h
    src/include/commands/cluster.h
    src/include/commands/comment.h
    src/include/commands/copy.h
    src/include/commands/dbcommands.h
    src/include/commands/defrem.h
    src/include/commands/explain.h
    src/include/commands/lockcmds.h
    src/include/commands/portalcmds.h
    src/include/commands/proclang.h
    src/include/commands/schemacmds.h
    src/include/commands/sequence.h
    src/include/commands/tablecmds.h
    src/include/commands/trigger.h
    src/include/commands/user.h
    src/include/commands/vacuum.h
    src/include/commands/variable.h
    src/include/commands/version.h
    src/include/commands/view.h
    src/include/executor/execdebug.h
    src/include/executor/execdefs.h
    src/include/executor/execdesc.h
    src/include/executor/executor.h
    src/include/executor/functions.h
    src/include/executor/hashjoin.h
    src/include/executor/instrument.h
    src/include/executor/nodeAgg.h
    src/include/executor/nodeAppend.h
    src/include/executor/nodeFunctionscan.h
    src/include/executor/nodeGroup.h
    src/include/executor/nodeHash.h
    src/include/executor/nodeHashjoin.h
    src/include/executor/nodeIndexscan.h
    src/include/executor/nodeLimit.h
    src/include/executor/nodeMaterial.h
    src/include/executor/nodeMergejoin.h
    src/include/executor/nodeNestloop.h
    src/include/executor/nodeResult.h
    src/include/executor/nodeSeqscan.h
    src/include/executor/nodeSetOp.h
    src/include/executor/nodeSort.h
    src/include/executor/nodeSubplan.h
    src/include/executor/nodeSubqueryscan.h
    src/include/executor/nodeTidscan.h
    src/include/executor/nodeUnique.h
    src/include/executor/spi.h
    src/include/executor/spi_priv.h
    src/include/executor/tuptable.h
    src/include/fmgr.h
    src/include/lib/dllist.h
    src/include/lib/lispsort.h
    src/include/lib/stringinfo.h
    src/include/libpq/auth.h
    src/include/libpq/be-fsstubs.h
    src/include/libpq/crypt.h
    src/include/libpq/hba.h
    src/include/libpq/libpq-be.h
    src/include/libpq/libpq-fs.h
    src/include/libpq/libpq.h
    src/include/libpq/password.h
    src/include/libpq/pqcomm.h
    src/include/libpq/pqformat.h
    src/include/libpq/pqsignal.h
    src/include/mb/pg_wchar.h
    src/include/miscadmin.h
    src/include/nodes/execnodes.h
    src/include/nodes/makefuncs.h
    src/include/nodes/memnodes.h
    src/include/nodes/nodeFuncs.h
    src/include/nodes/nodes.h
    src/include/nodes/params.h
    src/include/nodes/parsenodes.h
    src/include/nodes/pg_list.h
    src/include/nodes/plannodes.h
    src/include/nodes/primnodes.h
    src/include/nodes/print.h
    src/include/nodes/readfuncs.h
    src/include/nodes/relation.h
    src/include/optimizer/_deadcode/xfunc.h
    src/include/optimizer/clauses.h
    src/include/optimizer/cost.h
    src/include/optimizer/geqo.h
    src/include/optimizer/geqo_copy.h
    src/include/optimizer/geqo_gene.h
    src/include/optimizer/geqo_misc.h
    src/include/optimizer/geqo_mutation.h
    src/include/optimizer/geqo_pool.h
    src/include/optimizer/geqo_random.h
    src/include/optimizer/geqo_recombination.h
    src/include/optimizer/geqo_selection.h
    src/include/optimizer/joininfo.h
    src/include/optimizer/pathnode.h
    src/include/optimizer/paths.h
    src/include/optimizer/plancat.h
    src/include/optimizer/planmain.h
    src/include/optimizer/planner.h
    src/include/optimizer/prep.h
    src/include/optimizer/restrictinfo.h
    src/include/optimizer/subselect.h
    src/include/optimizer/tlist.h
    src/include/optimizer/var.h
    src/include/parser/analyze.h
    src/include/parser/gramparse.h
    src/include/parser/keywords.h
    src/include/parser/parse_agg.h
    src/include/parser/parse_clause.h
    src/include/parser/parse_coerce.h
    src/include/parser/parse_expr.h
    src/include/parser/parse_func.h
    src/include/parser/parse_node.h
    src/include/parser/parse_oper.h
    src/include/parser/parse_relation.h
    src/include/parser/parse_target.h
    src/include/parser/parse_type.h
    src/include/parser/parser.h
    src/include/parser/parsetree.h
    src/include/parser/scansup.h
    src/include/pg_config.h.in
    src/include/pg_config.h.win32
    src/include/pgstat.h
    src/include/port/aix.h
    src/include/port/beos.h
    src/include/port/bsdi.h
    src/include/port/darwin.h
    src/include/port/dgux.h
    src/include/port/freebsd.h
    src/include/port/hpux.h
    src/include/port/irix5.h
    src/include/port/linux.h
    src/include/port/netbsd.h
    src/include/port/nextstep.h
    src/include/port/openbsd.h
    src/include/port/osf.h
    src/include/port/qnx4.h
    src/include/port/sco.h
    src/include/port/solaris.h
    src/include/port/sunos4.h
    src/include/port/svr4.h
    src/include/port/ultrix4.h
    src/include/port/univel.h
    src/include/port/unixware.h
    src/include/port/win.h
    src/include/port/win32.h
    src/include/postgres.h
    src/include/postgres_ext.h
    src/include/postgres_fe.h
    src/include/regex/cclass.h
    src/include/regex/cname.h
    src/include/regex/regex.h
    src/include/regex/regex2.h
    src/include/regex/utils.h
    src/include/rewrite/prs2lock.h
    src/include/rewrite/rewriteDefine.h
    src/include/rewrite/rewriteHandler.h
    src/include/rewrite/rewriteManip.h
    src/include/rewrite/rewriteRemove.h
    src/include/rewrite/rewriteSupport.h
    src/include/rusagestub.h
    src/include/storage/backendid.h
    src/include/storage/block.h
    src/include/storage/buf.h
    src/include/storage/buf_internals.h
    src/include/storage/buffile.h
    src/include/storage/bufmgr.h
    src/include/storage/bufpage.h
    src/include/storage/fd.h
    src/include/storage/freespace.h
    src/include/storage/ipc.h
    src/include/storage/item.h
    src/include/storage/itemid.h
    src/include/storage/itempos.h
    src/include/storage/itemptr.h
    src/include/storage/large_object.h
    src/include/storage/lmgr.h
    src/include/storage/lock.h
    src/include/storage/lwlock.h
    src/include/storage/off.h
    src/include/storage/page.h
    src/include/storage/pg_sema.h
    src/include/storage/pg_shmem.h
    src/include/storage/pmsignal.h
    src/include/storage/pos.h
    src/include/storage/proc.h
    src/include/storage/relfilenode.h
    src/include/storage/s_lock.h
    src/include/storage/shmem.h
    src/include/storage/sinval.h
    src/include/storage/sinvaladt.h
    src/include/storage/smgr.h
    src/include/storage/spin.h
    src/include/strdup.h
    src/include/tcop/dest.h
    src/include/tcop/fastpath.h
    src/include/tcop/pquery.h
    src/include/tcop/tcopdebug.h
    src/include/tcop/tcopprot.h
    src/include/tcop/utility.h
    src/include/utils/acl.h
    src/include/utils/array.h
    src/include/utils/ascii.h
    src/include/utils/bit.h
    src/include/utils/builtins.h
    src/include/utils/cash.h
    src/include/utils/catcache.h
    src/include/utils/date.h
    src/include/utils/datetime.h
    src/include/utils/datum.h
    src/include/utils/dynahash.h
    src/include/utils/dynamic_loader.h
    src/include/utils/elog.h
    src/include/utils/exc.h
    src/include/utils/excid.h
    src/include/utils/fcache.h
    src/include/utils/fmgrtab.h
    src/include/utils/formatting.h
    src/include/utils/geo_decls.h
    src/include/utils/guc.h
    src/include/utils/hsearch.h
    src/include/utils/inet.h
    src/include/utils/int8.h
    src/include/utils/inval.h
    src/include/utils/logtape.h
    src/include/utils/lsyscache.h
    src/include/utils/memutils.h
    src/include/utils/nabstime.h
    src/include/utils/numeric.h
    src/include/utils/palloc.h
    src/include/utils/pg_crc.h
    src/include/utils/pg_locale.h
    src/include/utils/pg_lzcompress.h
    src/include/utils/portal.h
    src/include/utils/ps_status.h
    src/include/utils/rel.h
    src/include/utils/relcache.h
    src/include/utils/selfuncs.h
    src/include/utils/sets.h
    src/include/utils/syscache.h
    src/include/utils/timestamp.h
    src/include/utils/tqual.h
    src/include/utils/tuplesort.h
    src/include/utils/tuplestore.h
    src/include/utils/varbit.h
    src/interfaces/Makefile
    src/interfaces/cli/example1.c
    src/interfaces/cli/example2.c
    src/interfaces/cli/sqlcli.h
    src/interfaces/jdbc/CHANGELOG
    src/interfaces/jdbc/Implementation
    src/interfaces/jdbc/Makefile
    src/interfaces/jdbc/README
    src/interfaces/jdbc/build.xml
    src/interfaces/jdbc/example/ImageViewer.java
    src/interfaces/jdbc/example/Unicode.java
    src/interfaces/jdbc/example/basic.java
    src/interfaces/jdbc/example/blobtest.java
    src/interfaces/jdbc/example/corba/StockClient.java
    src/interfaces/jdbc/example/corba/StockDB.java
    src/interfaces/jdbc/example/corba/StockDispenserImpl.java
    src/interfaces/jdbc/example/corba/StockItemImpl.java
    src/interfaces/jdbc/example/corba/StockServer.java
    src/interfaces/jdbc/example/corba/readme
    src/interfaces/jdbc/example/corba/stock.idl
    src/interfaces/jdbc/example/corba/stock.sql
    src/interfaces/jdbc/example/datestyle.java
    src/interfaces/jdbc/example/metadata.java
    src/interfaces/jdbc/example/psql.java
    src/interfaces/jdbc/example/threadsafe.java
    src/interfaces/jdbc/jdbc.jpx
    src/interfaces/jdbc/org/postgresql/Connection.java
    src/interfaces/jdbc/org/postgresql/Driver.java.in
    src/interfaces/jdbc/org/postgresql/Field.java
    src/interfaces/jdbc/org/postgresql/PG_Stream.java
    src/interfaces/jdbc/org/postgresql/PostgresqlDataSource.java
    src/interfaces/jdbc/org/postgresql/ResultSet.java
    src/interfaces/jdbc/org/postgresql/Statement.java
    src/interfaces/jdbc/org/postgresql/core/BytePoolDim1.java
    src/interfaces/jdbc/org/postgresql/core/BytePoolDim2.java
    src/interfaces/jdbc/org/postgresql/core/Encoding.java
    src/interfaces/jdbc/org/postgresql/core/MemoryPool.java
    src/interfaces/jdbc/org/postgresql/core/ObjectPool.java
    src/interfaces/jdbc/org/postgresql/core/QueryExecutor.java
    src/interfaces/jdbc/org/postgresql/core/SimpleObjectPool.java
    src/interfaces/jdbc/org/postgresql/core/StartupPacket.java
    src/interfaces/jdbc/org/postgresql/errors.properties
    src/interfaces/jdbc/org/postgresql/errors_de.properties
    src/interfaces/jdbc/org/postgresql/errors_fr.properties
    src/interfaces/jdbc/org/postgresql/errors_it.properties
    src/interfaces/jdbc/org/postgresql/errors_nl.properties
    src/interfaces/jdbc/org/postgresql/errors_zh_TW.properties
    src/interfaces/jdbc/org/postgresql/fastpath/Fastpath.java
    src/interfaces/jdbc/org/postgresql/fastpath/FastpathArg.java
    src/interfaces/jdbc/org/postgresql/geometric/PGbox.java
    src/interfaces/jdbc/org/postgresql/geometric/PGcircle.java
    src/interfaces/jdbc/org/postgresql/geometric/PGline.java
    src/interfaces/jdbc/org/postgresql/geometric/PGlseg.java
    src/interfaces/jdbc/org/postgresql/geometric/PGpath.java
    src/interfaces/jdbc/org/postgresql/geometric/PGpoint.java
    src/interfaces/jdbc/org/postgresql/geometric/PGpolygon.java
    src/interfaces/jdbc/org/postgresql/jdbc1/CallableStatement.java
    src/interfaces/jdbc/org/postgresql/jdbc1/Connection.java
    src/interfaces/jdbc/org/postgresql/jdbc1/DatabaseMetaData.java
    src/interfaces/jdbc/org/postgresql/jdbc1/PreparedStatement.java
    src/interfaces/jdbc/org/postgresql/jdbc1/ResultSet.java
    src/interfaces/jdbc/org/postgresql/jdbc1/ResultSetMetaData.java
    src/interfaces/jdbc/org/postgresql/jdbc1/Statement.java
    src/interfaces/jdbc/org/postgresql/jdbc2/Array.java
    src/interfaces/jdbc/org/postgresql/jdbc2/CallableStatement.java
    src/interfaces/jdbc/org/postgresql/jdbc2/Connection.java
    src/interfaces/jdbc/org/postgresql/jdbc2/DatabaseMetaData.java
    src/interfaces/jdbc/org/postgresql/jdbc2/PBatchUpdateException.java
    src/interfaces/jdbc/org/postgresql/jdbc2/PreparedStatement.java
    src/interfaces/jdbc/org/postgresql/jdbc2/ResultSet.java
    src/interfaces/jdbc/org/postgresql/jdbc2/ResultSetMetaData.java
    src/interfaces/jdbc/org/postgresql/jdbc2/Statement.java
    src/interfaces/jdbc/org/postgresql/jdbc2/UpdateableResultSet.java
    src/interfaces/jdbc/org/postgresql/largeobject/BlobInputStream.java
    src/interfaces/jdbc/org/postgresql/largeobject/BlobOutputStream.java
    src/interfaces/jdbc/org/postgresql/largeobject/LargeObject.java
    src/interfaces/jdbc/org/postgresql/largeobject/LargeObjectManager.java
    src/interfaces/jdbc/org/postgresql/largeobject/PGblob.java
    src/interfaces/jdbc/org/postgresql/largeobject/PGclob.java
    src/interfaces/jdbc/org/postgresql/test/JDBC2Tests.java
    src/interfaces/jdbc/org/postgresql/test/README
    src/interfaces/jdbc/org/postgresql/test/jdbc2/ANTTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/BatchExecuteTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/BlobTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/ConnectionTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/DatabaseMetaDataTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/DateTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/DriverTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/EncodingTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/JBuilderTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/MiscTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/ResultSetTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/TimeTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/TimestampTest.java
    src/interfaces/jdbc/org/postgresql/test/jdbc2/UpdateableResultTest.java
    src/interfaces/jdbc/org/postgresql/util/MD5Digest.java
    src/interfaces/jdbc/org/postgresql/util/MessageTranslator.java
    src/interfaces/jdbc/org/postgresql/util/PGbytea.java
    src/interfaces/jdbc/org/postgresql/util/PGmoney.java
    src/interfaces/jdbc/org/postgresql/util/PGobject.java
    src/interfaces/jdbc/org/postgresql/util/PGtokenizer.java
    src/interfaces/jdbc/org/postgresql/util/PSQLException.java
    src/interfaces/jdbc/org/postgresql/util/Serialize.java
    src/interfaces/jdbc/org/postgresql/util/UnixCrypt.java
    src/interfaces/jdbc/org/postgresql/xa/ClientConnection.java
    src/interfaces/jdbc/org/postgresql/xa/TwoPhaseConnection.java
    src/interfaces/jdbc/org/postgresql/xa/TxConnection.java
    src/interfaces/jdbc/org/postgresql/xa/XAConnectionImpl.java
    src/interfaces/jdbc/org/postgresql/xa/XADataSourceImpl.java
    src/interfaces/jdbc/utils/CheckVersion.java
    src/interfaces/jdbc/utils/buildDriver
    src/interfaces/jdbc/utils/changelog.pl
    src/interfaces/libpgeasy/Makefile
    src/interfaces/libpgeasy/README
    src/interfaces/libpgeasy/examples/Makefile
    src/interfaces/libpgeasy/examples/pginsert.c
    src/interfaces/libpgeasy/examples/pgmultiresult.c
    src/interfaces/libpgeasy/examples/pgnulltest.c
    src/interfaces/libpgeasy/examples/pgwordcount.c
    src/interfaces/libpgeasy/halt.c
    src/interfaces/libpgeasy/halt.h
    src/interfaces/libpgeasy/libpgeasy.c
    src/interfaces/libpgeasy/libpgeasy.h
    src/interfaces/libpgtcl/Makefile
    src/interfaces/libpgtcl/README
    src/interfaces/libpgtcl/libpgtcl.def
    src/interfaces/libpgtcl/libpgtcl.h
    src/interfaces/libpgtcl/pgtcl.c
    src/interfaces/libpgtcl/pgtclCmds.c
    src/interfaces/libpgtcl/pgtclCmds.h
    src/interfaces/libpgtcl/pgtclId.c
    src/interfaces/libpgtcl/pgtclId.h
    src/interfaces/libpgtcl/win32.mak
    src/interfaces/libpq/Makefile
    src/interfaces/libpq/README
    src/interfaces/libpq/cs.po
    src/interfaces/libpq/de.po
    src/interfaces/libpq/fe-auth.c
    src/interfaces/libpq/fe-auth.h
    src/interfaces/libpq/fe-connect.c
    src/interfaces/libpq/fe-exec.c
    src/interfaces/libpq/fe-lobj.c
    src/interfaces/libpq/fe-misc.c
    src/interfaces/libpq/fe-print.c
    src/interfaces/libpq/fe-secure.c
    src/interfaces/libpq/fr.po
    src/interfaces/libpq/libpq-fe.h
    src/interfaces/libpq/libpq-int.h
    src/interfaces/libpq/libpq.rc
    src/interfaces/libpq/libpqdll.c
    src/interfaces/libpq/libpqdll.def
    src/interfaces/libpq/nls.mk
    src/interfaces/libpq/pqexpbuffer.c
    src/interfaces/libpq/pqexpbuffer.h
    src/interfaces/libpq/pqsignal.c
    src/interfaces/libpq/pqsignal.h
    src/interfaces/libpq/ru.po
    src/interfaces/libpq/sv.po
    src/interfaces/libpq/win32.c
    src/interfaces/libpq/win32.h
    src/interfaces/libpq/win32.mak
    src/interfaces/libpq/zh_CN.po
    src/interfaces/libpq/zh_TW.po
    src/interfaces/libpq++/CHANGES
    src/interfaces/libpq++/Makefile
    src/interfaces/libpq++/README
    src/interfaces/libpq++/TODO
    src/interfaces/libpq++/examples/Makefile
    src/interfaces/libpq++/examples/testlibpq0.cc
    src/interfaces/libpq++/examples/testlibpq1.cc
    src/interfaces/libpq++/examples/testlibpq2.cc
    src/interfaces/libpq++/examples/testlibpq2.sql
    src/interfaces/libpq++/examples/testlibpq3.cc
    src/interfaces/libpq++/examples/testlibpq3.sql
    src/interfaces/libpq++/examples/testlibpq4.cc
    src/interfaces/libpq++/examples/testlibpq4.sql
    src/interfaces/libpq++/examples/testlibpq5.cc
    src/interfaces/libpq++/examples/testlibpq5.sql
    src/interfaces/libpq++/examples/testlibpq6.cc
    src/interfaces/libpq++/examples/testlo.cc
    src/interfaces/libpq++/libpq++.h
    src/interfaces/libpq++/libpq++dll.rc
    src/interfaces/libpq++/pgconnection.cc
    src/interfaces/libpq++/pgconnection.h
    src/interfaces/libpq++/pgcursordb.cc
    src/interfaces/libpq++/pgcursordb.h
    src/interfaces/libpq++/pgdatabase.cc
    src/interfaces/libpq++/pgdatabase.h
    src/interfaces/libpq++/pglobject.cc
    src/interfaces/libpq++/pglobject.h
    src/interfaces/libpq++/pgtransdb.cc
    src/interfaces/libpq++/pgtransdb.h
    src/interfaces/libpq++/win32.mak
    src/interfaces/odbc/GNUmakefile
    src/interfaces/odbc/bind.c
    src/interfaces/odbc/bind.h
    src/interfaces/odbc/columninfo.c
    src/interfaces/odbc/columninfo.h
    src/interfaces/odbc/connection.c
    src/interfaces/odbc/connection.h
    src/interfaces/odbc/convert.c
    src/interfaces/odbc/convert.h
    src/interfaces/odbc/descriptor.h
    src/interfaces/odbc/dlg_specific.c
    src/interfaces/odbc/dlg_specific.h
    src/interfaces/odbc/dlg_wingui.c
    src/interfaces/odbc/drvconn.c
    src/interfaces/odbc/environ.c
    src/interfaces/odbc/environ.h
    src/interfaces/odbc/execute.c
    src/interfaces/odbc/gpps.c
    src/interfaces/odbc/gpps.h
    src/interfaces/odbc/info.c
    src/interfaces/odbc/info30.c
    src/interfaces/odbc/iodbc.h
    src/interfaces/odbc/isql.h
    src/interfaces/odbc/isqlext.h
    src/interfaces/odbc/license.txt
    src/interfaces/odbc/lobj.c
    src/interfaces/odbc/lobj.h
    src/interfaces/odbc/md5.c
    src/interfaces/odbc/md5.h
    src/interfaces/odbc/misc.c
    src/interfaces/odbc/misc.h
    src/interfaces/odbc/multibyte.c
    src/interfaces/odbc/multibyte.h
    src/interfaces/odbc/notice.txt
    src/interfaces/odbc/odbc.sql
    src/interfaces/odbc/odbcapi.c
    src/interfaces/odbc/odbcapi25w.c
    src/interfaces/odbc/odbcapi30.c
    src/interfaces/odbc/odbcapi30w.c
    src/interfaces/odbc/odbcapiw.c
    src/interfaces/odbc/odbcinst.ini
    src/interfaces/odbc/options.c
    src/interfaces/odbc/parse.c
    src/interfaces/odbc/pgapi30.c
    src/interfaces/odbc/pgapifunc.h
    src/interfaces/odbc/pgtypes.c
    src/interfaces/odbc/pgtypes.h
    src/interfaces/odbc/psqlodbc.c
    src/interfaces/odbc/psqlodbc.h
    src/interfaces/odbc/psqlodbc.rc
    src/interfaces/odbc/psqlodbc.reg
    src/interfaces/odbc/psqlodbc30.reg
    src/interfaces/odbc/psqlodbc30w.reg
    src/interfaces/odbc/psqlodbc_api30.def
    src/interfaces/odbc/psqlodbc_api30w.def
    src/interfaces/odbc/psqlodbc_apiw.def
    src/interfaces/odbc/psqlodbc_win32.def
    src/interfaces/odbc/qresult.c
    src/interfaces/odbc/qresult.h
    src/interfaces/odbc/readme.txt
    src/interfaces/odbc/resource.h
    src/interfaces/odbc/results.c
    src/interfaces/odbc/setup.c
    src/interfaces/odbc/setup.rul
    src/interfaces/odbc/socket.c
    src/interfaces/odbc/socket.h
    src/interfaces/odbc/statement.c
    src/interfaces/odbc/statement.h
    src/interfaces/odbc/tuple.c
    src/interfaces/odbc/tuple.h
    src/interfaces/odbc/tuplelist.c
    src/interfaces/odbc/tuplelist.h
    src/interfaces/odbc/version.h
    src/interfaces/odbc/win32.mak
    src/interfaces/odbc/win32_30.mak
    src/interfaces/odbc/win32_30w.mak
    src/interfaces/odbc/win32w.mak
    src/interfaces/odbc/win_md5.c
    src/interfaces/odbc/win_setup.h
    src/interfaces/odbc/win_unicode.c
    src/interfaces/perl5/Changes
    src/interfaces/perl5/GNUmakefile
    src/interfaces/perl5/MANIFEST
    src/interfaces/perl5/Makefile.PL
    src/interfaces/perl5/Pg.pm
    src/interfaces/perl5/Pg.xs
    src/interfaces/perl5/README
    src/interfaces/perl5/examples/ApachePg.pl
    src/interfaces/perl5/examples/example.newstyle
    src/interfaces/perl5/examples/example.oldstyle
    src/interfaces/perl5/ppport.h
    src/interfaces/perl5/test.pl
    src/interfaces/perl5/typemap
    src/interfaces/python/Announce
    src/interfaces/python/ChangeLog
    src/interfaces/python/GNUmakefile
    src/interfaces/python/PyGreSQL.spec
    src/interfaces/python/README
    src/interfaces/python/README.linux
    src/interfaces/python/Setup.in.raw
    src/interfaces/python/pg.py
    src/interfaces/python/pgdb.py
    src/interfaces/python/pgmodule.c
    src/interfaces/python/setup.py
    src/interfaces/python/tutorial/advanced.py
    src/interfaces/python/tutorial/basics.py
    src/interfaces/python/tutorial/func.py
    src/interfaces/python/tutorial/syscat.py
    src/interfaces/ssl/client.conf
    src/interfaces/ssl/mkcert.sh
    src/interfaces/ssl/pgkeygen.sh
    src/interfaces/ssl/root.conf
    src/interfaces/ssl/server.conf
    src/makefiles/Makefile.aix
    src/makefiles/Makefile.beos
    src/makefiles/Makefile.bsdi
    src/makefiles/Makefile.darwin
    src/makefiles/Makefile.dgux
    src/makefiles/Makefile.freebsd
    src/makefiles/Makefile.hpux
    src/makefiles/Makefile.irix5
    src/makefiles/Makefile.linux
    src/makefiles/Makefile.netbsd
    src/makefiles/Makefile.openbsd
    src/makefiles/Makefile.osf
    src/makefiles/Makefile.qnx4
    src/makefiles/Makefile.sco
    src/makefiles/Makefile.solaris
    src/makefiles/Makefile.sunos4
    src/makefiles/Makefile.svr4
    src/makefiles/Makefile.ultrix4
    src/makefiles/Makefile.univel
    src/makefiles/Makefile.unixware
    src/makefiles/Makefile.win
    src/nls-global.mk
    src/pl/Makefile
    src/pl/plperl/GNUmakefile
    src/pl/plperl/README
    src/pl/plperl/SPI.xs
    src/pl/plperl/eloglvl.c
    src/pl/plperl/eloglvl.h
    src/pl/plperl/plperl.c
    src/pl/plperl/ppport.h
    src/pl/plpgsql/Makefile
    src/pl/plpgsql/src/.cvsignore
    src/pl/plpgsql/src/INSTALL
    src/pl/plpgsql/src/Makefile
    src/pl/plpgsql/src/gram.y
    src/pl/plpgsql/src/pl_comp.c
    src/pl/plpgsql/src/pl_exec.c
    src/pl/plpgsql/src/pl_funcs.c
    src/pl/plpgsql/src/pl_handler.c
    src/pl/plpgsql/src/plpgsql.h
    src/pl/plpgsql/src/scan.l
    src/pl/plpgsql/test/README
    src/pl/plpgsql/test/expected/tables.out
    src/pl/plpgsql/test/expected/test.out
    src/pl/plpgsql/test/expected/triggers.out
    src/pl/plpgsql/test/expected/views.out
    src/pl/plpgsql/test/runtest
    src/pl/plpgsql/test/tables.sql
    src/pl/plpgsql/test/test.sql
    src/pl/plpgsql/test/triggers.sql
    src/pl/plpgsql/test/views.sql
    src/pl/plpython/Makefile
    src/pl/plpython/README
    src/pl/plpython/TODO
    src/pl/plpython/error.expected
    src/pl/plpython/feature.expected
    src/pl/plpython/plpython.c
    src/pl/plpython/plpython.h
    src/pl/plpython/plpython_depopulate.sql
    src/pl/plpython/plpython_deschema.sql
    src/pl/plpython/plpython_drop.sql
    src/pl/plpython/plpython_error.sql
    src/pl/plpython/plpython_function.sql
    src/pl/plpython/plpython_populate.sql
    src/pl/plpython/plpython_schema.sql
    src/pl/plpython/plpython_setof.sql
    src/pl/plpython/plpython_test.sql
    src/pl/plpython/test.sh
    src/pl/tcl/Makefile
    src/pl/tcl/license.terms
    src/pl/tcl/modules/Makefile
    src/pl/tcl/modules/README
    src/pl/tcl/modules/pltcl_delmod.in
    src/pl/tcl/modules/pltcl_listmod.in
    src/pl/tcl/modules/pltcl_loadmod.in
    src/pl/tcl/modules/unknown.pltcl
    src/pl/tcl/pltcl.c
    src/pl/tcl/test/README
    src/pl/tcl/test/runtest
    src/pl/tcl/test/test.expected
    src/pl/tcl/test/test_queries.sql
    src/pl/tcl/test/test_setup.sql
    src/template/aix
    src/template/beos
    src/template/bsdi
    src/template/darwin
    src/template/dgux
    src/template/freebsd
    src/template/hpux
    src/template/irix5
    src/template/linux
    src/template/netbsd
    src/template/nextstep
    src/template/openbsd
    src/template/osf
    src/template/qnx4
    src/template/sco
    src/template/solaris
    src/template/sunos4
    src/template/svr4
    src/template/ultrix4
    src/template/univel
    src/template/unixware
    src/template/win
    src/test/Makefile
    src/test/bench/Makefile
    src/test/bench/WISC-README
    src/test/bench/create.sh
    src/test/bench/create.source
    src/test/bench/perquery
    src/test/bench/query01
    src/test/bench/query02
    src/test/bench/query03
    src/test/bench/query04
    src/test/bench/query05
    src/test/bench/query06
    src/test/bench/query07
    src/test/bench/query08
    src/test/bench/query09
    src/test/bench/query10
    src/test/bench/query11
    src/test/bench/query12
    src/test/bench/query13
    src/test/bench/query14
    src/test/bench/query15
    src/test/bench/query16
    src/test/bench/query17
    src/test/bench/query18
    src/test/bench/query19
    src/test/bench/query20
    src/test/bench/query21
    src/test/bench/query22
    src/test/bench/query23
    src/test/bench/query24
    src/test/bench/query25
    src/test/bench/query26
    src/test/bench/query27
    src/test/bench/query28
    src/test/bench/query29
    src/test/bench/query30
    src/test/bench/query31
    src/test/bench/query32
    src/test/bench/runwisc.sh
    src/test/bench/wholebench.sh
    src/test/examples/Makefile
    src/test/examples/testlibpq.c
    src/test/examples/testlibpq2.c
    src/test/examples/testlibpq2.sql
    src/test/examples/testlibpq3.c
    src/test/examples/testlibpq3.sql
    src/test/examples/testlibpq4.c
    src/test/examples/testlo.c
    src/test/locale/Makefile
    src/test/locale/README
    src/test/locale/de_DE.ISO8859-1/Makefile
    src/test/locale/de_DE.ISO8859-1/README
    src/test/locale/de_DE.ISO8859-1/expected/de-ctype.out
    src/test/locale/de_DE.ISO8859-1/expected/test-de-char.sql.out
    src/test/locale/de_DE.ISO8859-1/expected/test-de-select.sql.out
    src/test/locale/de_DE.ISO8859-1/expected/test-de-sort.out
    src/test/locale/de_DE.ISO8859-1/expected/test-de-text.sql.out
    src/test/locale/de_DE.ISO8859-1/expected/test-de-upper-char.sql.out
    src/test/locale/de_DE.ISO8859-1/expected/test-de-upper-text.sql.out
    src/test/locale/de_DE.ISO8859-1/expected/test-de-upper-varchar.sql.out
    src/test/locale/de_DE.ISO8859-1/expected/test-de-varchar.sql.out
    src/test/locale/de_DE.ISO8859-1/runall
    src/test/locale/de_DE.ISO8859-1/test-de-select.sql.in
    src/test/locale/de_DE.ISO8859-1/test-de-sort.in
    src/test/locale/de_DE.ISO8859-1/test-de-upper.sql.in
    src/test/locale/de_DE.ISO8859-1/test-de.sql.in
    src/test/locale/gr_GR.ISO8859-7/Makefile
    src/test/locale/gr_GR.ISO8859-7/README
    src/test/locale/gr_GR.ISO8859-7/expected/gr-ctype.out
    src/test/locale/gr_GR.ISO8859-7/expected/test-gr-char.sql.out
    src/test/locale/gr_GR.ISO8859-7/expected/test-gr-select.sql.out
    src/test/locale/gr_GR.ISO8859-7/expected/test-gr-sort.out
    src/test/locale/gr_GR.ISO8859-7/expected/test-gr-text.sql.out
    src/test/locale/gr_GR.ISO8859-7/expected/test-gr-varchar.sql.out
    src/test/locale/gr_GR.ISO8859-7/runall
    src/test/locale/gr_GR.ISO8859-7/test-gr-select.sql.in
    src/test/locale/gr_GR.ISO8859-7/test-gr-sort.in
    src/test/locale/gr_GR.ISO8859-7/test-gr.sql.in
    src/test/locale/koi8-r/Makefile
    src/test/locale/koi8-r/expected/koi8-ctype.out
    src/test/locale/koi8-r/expected/test-koi8-char.sql.out
    src/test/locale/koi8-r/expected/test-koi8-select.sql.out
    src/test/locale/koi8-r/expected/test-koi8-sort.out
    src/test/locale/koi8-r/expected/test-koi8-text.sql.out
    src/test/locale/koi8-r/expected/test-koi8-varchar.sql.out
    src/test/locale/koi8-r/runall
    src/test/locale/koi8-r/test-koi8-select.sql.in
    src/test/locale/koi8-r/test-koi8-sort.in
    src/test/locale/koi8-r/test-koi8.sql.in
    src/test/locale/koi8-to-win1251/Makefile
    src/test/locale/koi8-to-win1251/README
    src/test/locale/koi8-to-win1251/expected/test-koi8-char.sql.out
    src/test/locale/koi8-to-win1251/expected/test-koi8-select.sql.out
    src/test/locale/koi8-to-win1251/expected/test-koi8-sort.out
    src/test/locale/koi8-to-win1251/expected/test-koi8-text.sql.out
    src/test/locale/koi8-to-win1251/expected/test-koi8-varchar.sql.out
    src/test/locale/koi8-to-win1251/runall
    src/test/locale/koi8-to-win1251/test-koi8-select.sql.in
    src/test/locale/koi8-to-win1251/test-koi8-sort.in
    src/test/locale/koi8-to-win1251/test-koi8.sql.in
    src/test/locale/sort-test.pl
    src/test/locale/sort-test.py
    src/test/locale/test-ctype.c
    src/test/locale/test-pgsql-locale.c
    src/test/mb/README
    src/test/mb/expected/big5.out
    src/test/mb/expected/euc_cn.out
    src/test/mb/expected/euc_jp.out
    src/test/mb/expected/euc_kr.out
    src/test/mb/expected/euc_tw.out
    src/test/mb/expected/mule_internal.out
    src/test/mb/expected/sjis.out
    src/test/mb/expected/unicode.out
    src/test/mb/mbregress.sh
    src/test/mb/sql/big5.sql
    src/test/mb/sql/euc_cn.sql
    src/test/mb/sql/euc_jp.sql
    src/test/mb/sql/euc_kr.sql
    src/test/mb/sql/euc_tw.sql
    src/test/mb/sql/mule_internal.sql
    src/test/mb/sql/sjis.sql
    src/test/mb/sql/unicode.sql
    src/test/performance/results/PgSQL.970926
    src/test/performance/runtests.pl
    src/test/performance/sqls/connection
    src/test/performance/sqls/crtsimple
    src/test/performance/sqls/crtsimpleidx
    src/test/performance/sqls/drpsimple
    src/test/performance/sqls/inssimple
    src/test/performance/sqls/inssimple.data
    src/test/performance/sqls/orbsimple
    src/test/performance/sqls/slcsimple
    src/test/performance/sqls/slcsimple.data
    src/test/performance/sqls/vacuum
    src/test/performance/start-pgsql.sh
    src/test/regress/GNUmakefile
    src/test/regress/Makefile
    src/test/regress/README
    src/test/regress/data/agg.data
    src/test/regress/data/constrf.data
    src/test/regress/data/constro.data
    src/test/regress/data/dept.data
    src/test/regress/data/desc.data
    src/test/regress/data/emp.data
    src/test/regress/data/hash.data
    src/test/regress/data/onek.data
    src/test/regress/data/person.data
    src/test/regress/data/real_city.data
    src/test/regress/data/rect.data
    src/test/regress/data/streets.data
    src/test/regress/data/stud_emp.data
    src/test/regress/data/student.data
    src/test/regress/data/tenk.data
    src/test/regress/expected/abstime-solaris-1947.out
    src/test/regress/expected/abstime.out
    src/test/regress/expected/aggregates.out
    src/test/regress/expected/alter_table.out
    src/test/regress/expected/arrays.out
    src/test/regress/expected/bit.out
    src/test/regress/expected/boolean.out
    src/test/regress/expected/box.out
    src/test/regress/expected/btree_index.out
    src/test/regress/expected/case.out
    src/test/regress/expected/char.out
    src/test/regress/expected/char_1.out
    src/test/regress/expected/circle.out
    src/test/regress/expected/comments.out
    src/test/regress/expected/create_aggregate.out
    src/test/regress/expected/create_index.out
    src/test/regress/expected/create_misc.out
    src/test/regress/expected/create_operator.out
    src/test/regress/expected/create_table.out
    src/test/regress/expected/create_type.out
    src/test/regress/expected/create_view.out
    src/test/regress/expected/date.out
    src/test/regress/expected/domain.out
    src/test/regress/expected/errors.out
    src/test/regress/expected/euc_cn.out
    src/test/regress/expected/euc_jp.out
    src/test/regress/expected/euc_kr.out
    src/test/regress/expected/euc_tw.out
    src/test/regress/expected/float4-exp-three-digits.out
    src/test/regress/expected/float4.out
    src/test/regress/expected/float8-exp-three-digits.out
    src/test/regress/expected/float8-fp-exception.out
    src/test/regress/expected/float8-small-is-zero.out
    src/test/regress/expected/float8.out
    src/test/regress/expected/foreign_key.out
    src/test/regress/expected/geometry-alpha-precision.out
    src/test/regress/expected/geometry-bsdi-precision.out
    src/test/regress/expected/geometry-i86-gnulibc.out
    src/test/regress/expected/geometry-intel-beos.out
    src/test/regress/expected/geometry-irix.out
    src/test/regress/expected/geometry-positive-zeros-bsd.out
    src/test/regress/expected/geometry-positive-zeros.out
    src/test/regress/expected/geometry-powerpc-aix4.out
    src/test/regress/expected/geometry-powerpc-darwin.out
    src/test/regress/expected/geometry-powerpc-linux-gnulibc1.out
    src/test/regress/expected/geometry-solaris-i386-pc.out
    src/test/regress/expected/geometry-solaris-precision.out
    src/test/regress/expected/geometry-uw7-cc.out
    src/test/regress/expected/geometry-uw7-gcc.out
    src/test/regress/expected/geometry.out
    src/test/regress/expected/hash_index.out
    src/test/regress/expected/horology-no-DST-before-1970.out
    src/test/regress/expected/horology-solaris-1947.out
    src/test/regress/expected/horology.out
    src/test/regress/expected/inet.out
    src/test/regress/expected/inherit.out
    src/test/regress/expected/insert.out
    src/test/regress/expected/int2.out
    src/test/regress/expected/int4.out
    src/test/regress/expected/int8-exp-three-digits.out
    src/test/regress/expected/int8.out
    src/test/regress/expected/interval.out
    src/test/regress/expected/join.out
    src/test/regress/expected/limit.out
    src/test/regress/expected/lseg.out
    src/test/regress/expected/mule_internal.out
    src/test/regress/expected/name.out
    src/test/regress/expected/numeric.out
    src/test/regress/expected/numeric_big.out
    src/test/regress/expected/numerology.out
    src/test/regress/expected/oid.out
    src/test/regress/expected/oidjoins.out
    src/test/regress/expected/opr_sanity.out
    src/test/regress/expected/path.out
    src/test/regress/expected/plpgsql.out
    src/test/regress/expected/point.out
    src/test/regress/expected/polygon.out
    src/test/regress/expected/portals.out
    src/test/regress/expected/portals_p2.out
    src/test/regress/expected/privileges.out
    src/test/regress/expected/random.out
    src/test/regress/expected/reltime.out
    src/test/regress/expected/rules.out
    src/test/regress/expected/sanity_check.out
    src/test/regress/expected/select.out
    src/test/regress/expected/select_distinct.out
    src/test/regress/expected/select_distinct_on.out
    src/test/regress/expected/select_having.out
    src/test/regress/expected/select_having_1.out
    src/test/regress/expected/select_implicit.out
    src/test/regress/expected/select_implicit_1.out
    src/test/regress/expected/select_into.out
    src/test/regress/expected/select_views.out
    src/test/regress/expected/select_views_1.out
    src/test/regress/expected/sql_ascii.out
    src/test/regress/expected/strings.out
    src/test/regress/expected/subselect.out
    src/test/regress/expected/temp.out
    src/test/regress/expected/text.out
    src/test/regress/expected/time.out
    src/test/regress/expected/timestamp.out
    src/test/regress/expected/timestamptz.out
    src/test/regress/expected/timetz.out
    src/test/regress/expected/tinterval-solaris-1947.out
    src/test/regress/expected/tinterval.out
    src/test/regress/expected/transactions.out
    src/test/regress/expected/triggers.out
    src/test/regress/expected/type_sanity.out
    src/test/regress/expected/union.out
    src/test/regress/expected/varchar.out
    src/test/regress/expected/varchar_1.out
    src/test/regress/input/constraints.source
    src/test/regress/input/copy.source
    src/test/regress/input/create_function_1.source
    src/test/regress/input/create_function_2.source
    src/test/regress/input/misc.source
    src/test/regress/output/constraints.source
    src/test/regress/output/copy.source
    src/test/regress/output/create_function_1.source
    src/test/regress/output/create_function_2.source
    src/test/regress/output/misc.source
    src/test/regress/parallel_schedule
    src/test/regress/pg_regress.sh
    src/test/regress/regress.c
    src/test/regress/regressplans.sh
    src/test/regress/resultmap
    src/test/regress/serial_schedule
    src/test/regress/sql/abstime.sql
    src/test/regress/sql/aggregates.sql
    src/test/regress/sql/alter_table.sql
    src/test/regress/sql/arrays.sql
    src/test/regress/sql/bit.sql
    src/test/regress/sql/boolean.sql
    src/test/regress/sql/box.sql
    src/test/regress/sql/btree_index.sql
    src/test/regress/sql/case.sql
    src/test/regress/sql/char.sql
    src/test/regress/sql/circle.sql
    src/test/regress/sql/comments.sql
    src/test/regress/sql/create_aggregate.sql
    src/test/regress/sql/create_index.sql
    src/test/regress/sql/create_misc.sql
    src/test/regress/sql/create_operator.sql
    src/test/regress/sql/create_table.sql
    src/test/regress/sql/create_type.sql
    src/test/regress/sql/create_view.sql
    src/test/regress/sql/date.sql
    src/test/regress/sql/domain.sql
    src/test/regress/sql/drop.sql
    src/test/regress/sql/errors.sql
    src/test/regress/sql/euc_cn.sql
    src/test/regress/sql/euc_jp.sql
    src/test/regress/sql/euc_kr.sql
    src/test/regress/sql/euc_tw.sql
    src/test/regress/sql/float4.sql
    src/test/regress/sql/float8.sql
    src/test/regress/sql/foreign_key.sql
    src/test/regress/sql/geometry.sql
    src/test/regress/sql/hash_index.sql
    src/test/regress/sql/horology.sql
    src/test/regress/sql/inet.sql
    src/test/regress/sql/inherit.sql
    src/test/regress/sql/insert.sql
    src/test/regress/sql/int2.sql
    src/test/regress/sql/int4.sql
    src/test/regress/sql/int8.sql
    src/test/regress/sql/interval.sql
    src/test/regress/sql/join.sql
    src/test/regress/sql/limit.sql
    src/test/regress/sql/lseg.sql
    src/test/regress/sql/mule_internal.sql
    src/test/regress/sql/name.sql
    src/test/regress/sql/numeric.sql
    src/test/regress/sql/numeric_big.sql
    src/test/regress/sql/numerology.sql
    src/test/regress/sql/oid.sql
    src/test/regress/sql/oidjoins.sql
    src/test/regress/sql/opr_sanity.sql
    src/test/regress/sql/path.sql
    src/test/regress/sql/plpgsql.sql
    src/test/regress/sql/point.sql
    src/test/regress/sql/polygon.sql
    src/test/regress/sql/portals.sql
    src/test/regress/sql/portals_p2.sql
    src/test/regress/sql/privileges.sql
    src/test/regress/sql/random.sql
    src/test/regress/sql/reltime.sql
    src/test/regress/sql/rules.sql
    src/test/regress/sql/sanity_check.sql
    src/test/regress/sql/select.sql
    src/test/regress/sql/select_distinct.sql
    src/test/regress/sql/select_distinct_on.sql
    src/test/regress/sql/select_having.sql
    src/test/regress/sql/select_implicit.sql
    src/test/regress/sql/select_into.sql
    src/test/regress/sql/select_views.sql
    src/test/regress/sql/sql_ascii.sql
    src/test/regress/sql/strings.sql
    src/test/regress/sql/subselect.sql
    src/test/regress/sql/temp.sql
    src/test/regress/sql/text.sql
    src/test/regress/sql/time.sql
    src/test/regress/sql/timestamp.sql
    src/test/regress/sql/timestamptz.sql
    src/test/regress/sql/timetz.sql
    src/test/regress/sql/tinterval.sql
    src/test/regress/sql/transactions.sql
    src/test/regress/sql/triggers.sql
    src/test/regress/sql/type_sanity.sql
    src/test/regress/sql/union.sql
    src/test/regress/sql/varchar.sql
    src/tools/RELEASE_CHANGES
    src/tools/backend/README
    src/tools/backend/backend_dirs.html
    src/tools/backend/flow.fig
    src/tools/backend/flow.gif
    src/tools/backend/index.html
    src/tools/ccsym
    src/tools/copyright
    src/tools/entab/Makefile
    src/tools/entab/entab.c
    src/tools/entab/entab.man
    src/tools/entab/halt.c
    src/tools/find_badmacros
    src/tools/find_static
    src/tools/find_typedef
    src/tools/make_ctags
    src/tools/make_diff/README
    src/tools/make_diff/cporig
    src/tools/make_diff/difforig
    src/tools/make_diff/rmorig
    src/tools/make_etags
    src/tools/make_keywords
    src/tools/make_mkid
    src/tools/pgcvslog
    src/tools/pginclude/README
    src/tools/pginclude/pgcompinclude
    src/tools/pginclude/pgdefine
    src/tools/pginclude/pgfixinclude
    src/tools/pginclude/pgrminclude
    src/tools/pgindent/README
    src/tools/pgindent/indent.bsd.patch
    src/tools/pgindent/pgcppindent
    src/tools/pgindent/pgindent
    src/tools/pgindent/pgjindent
    src/tutorial/Makefile
    src/tutorial/README
    src/tutorial/advanced.source
    src/tutorial/basics.source
    src/tutorial/beard.c
    src/tutorial/complex.c
    src/tutorial/complex.source
    src/tutorial/funcs.c
    src/tutorial/funcs.source
    src/tutorial/funcs_new.c
    src/tutorial/syscat.source
    src/utils/Makefile
    src/utils/README
    src/utils/dllinit.c
    src/utils/getopt.c
    src/utils/strdup.c
    src/win32.mak
---
 doc/src/FAQ/FAQ.html                    | 1349 --------
 doc/src/FAQ/FAQ_DEV.html                |  840 -----
 doc/src/FAQ/FAQ_german.html             | 1136 -------
 doc/src/FAQ/FAQ_japanese.html           | 1418 ---------
 doc/src/FAQ/FAQ_polish.html             | 1448 ---------
 doc/src/FAQ/FAQ_russian.html            | 1387 ---------
 doc/src/Makefile                        |   44 -
 doc/src/graphics/catalogs.ag            | 1220 --------
 doc/src/graphics/catalogs.cgm           |  Bin 6306 -> 0 bytes
 doc/src/graphics/catalogs.gif           |  Bin 26163 -> 0 bytes
 doc/src/graphics/catalogs.ps            | 1018 ------
 doc/src/graphics/clientserver.ag        |   99 -
 doc/src/graphics/clientserver.gif       |  Bin 2823 -> 0 bytes
 doc/src/graphics/connections.ag         |  486 ---
 doc/src/graphics/connections.gif        |  Bin 9485 -> 0 bytes
 doc/src/sgml/Makefile                   |  231 --
 doc/src/sgml/admin.sgml                 |   62 -
 doc/src/sgml/advanced.sgml              |  425 ---
 doc/src/sgml/arch-dev.sgml              | 4095 ------------------------
 doc/src/sgml/arch-pg.sgml               |  116 -
 doc/src/sgml/array.sgml                 |  328 --
 doc/src/sgml/backup.sgml                |  459 ---
 doc/src/sgml/biblio.sgml                |  540 ----
 doc/src/sgml/bki.sgml                   |  245 --
 doc/src/sgml/book-decl.sgml             |   11 -
 doc/src/sgml/catalogs.sgml              | 2750 ----------------
 doc/src/sgml/charset.sgml               | 1259 --------
 doc/src/sgml/client-auth.sgml           |  796 -----
 doc/src/sgml/compiler.sgml              |   77 -
 doc/src/sgml/contacts.sgml              |   35 -
 doc/src/sgml/cvs.sgml                   |  879 ------
 doc/src/sgml/datatype.sgml              | 3113 -------------------
 doc/src/sgml/datetime.sgml              | 1122 -------
 doc/src/sgml/developer.sgml             |   34 -
 doc/src/sgml/dfunc.sgml                 |  331 --
 doc/src/sgml/diskusage.sgml             |  109 -
 doc/src/sgml/docguide.sgml              | 1274 --------
 doc/src/sgml/ecpg.sgml                  | 1085 -------
 doc/src/sgml/extend.sgml                |  285 --
 doc/src/sgml/features.sgml              | 1844 -----------
 doc/src/sgml/filelist.sgml              |  112 -
 doc/src/sgml/fixrtf                     |   43 -
 doc/src/sgml/func-ref.sgml              |   19 -
 doc/src/sgml/func.sgml                  | 5182 -------------------------------
 doc/src/sgml/geqo.sgml                  |  318 --
 doc/src/sgml/gist.sgml                  |  109 -
 doc/src/sgml/history.sgml               |  269 --
 doc/src/sgml/indexcost.sgml             |  291 --
 doc/src/sgml/indices.sgml               |  933 ------
 doc/src/sgml/info.sgml                  |  177 --
 doc/src/sgml/inherit.sgml               |  188 --
 doc/src/sgml/install-win32.sgml         |  131 -
 doc/src/sgml/installation.sgml          | 1842 -----------
 doc/src/sgml/intro.sgml                 |  121 -
 doc/src/sgml/jdbc.sgml                  | 2605 ----------------
 doc/src/sgml/keywords.sgml              | 3202 -------------------
 doc/src/sgml/legal.sgml                 |  105 -
 doc/src/sgml/libpgeasy.sgml             |  152 -
 doc/src/sgml/libpgtcl.sgml              | 2239 -------------
 doc/src/sgml/libpq++.sgml               |  840 -----
 doc/src/sgml/libpq.sgml                 | 2738 ----------------
 doc/src/sgml/lobj.sgml                  |  590 ----
 doc/src/sgml/maintenance.sgml           |  441 ---
 doc/src/sgml/manage-ag.sgml             |  347 ---
 doc/src/sgml/manage.sgml                |  228 --
 doc/src/sgml/monitoring.sgml            |  555 ----
 doc/src/sgml/mvcc.sgml                  |  845 -----
 doc/src/sgml/nls.sgml                   |  489 ---
 doc/src/sgml/notation.sgml              |   76 -
 doc/src/sgml/odbc.sgml                  |  805 -----
 doc/src/sgml/page.sgml                  |  155 -
 doc/src/sgml/perform.sgml               |  729 -----
 doc/src/sgml/plperl.sgml                |  333 --
 doc/src/sgml/plpython.sgml              |  223 --
 doc/src/sgml/plsql.sgml                 | 3003 ------------------
 doc/src/sgml/pltcl.sgml                 |  704 -----
 doc/src/sgml/postgres.sgml              |   58 -
 doc/src/sgml/problems.sgml              |  356 ---
 doc/src/sgml/programmer.sgml            |  111 -
 doc/src/sgml/protocol.sgml              | 2102 -------------
 doc/src/sgml/pygresql.sgml              | 4484 --------------------------
 doc/src/sgml/queries.sgml               |  958 ------
 doc/src/sgml/query.sgml                 |  819 -----
 doc/src/sgml/recovery.sgml              |  104 -
 doc/src/sgml/ref/abort.sgml             |  154 -
 doc/src/sgml/ref/allfiles.sgml          |  136 -
 doc/src/sgml/ref/alter_database.sgml    |  171 -
 doc/src/sgml/ref/alter_group.sgml       |  160 -
 doc/src/sgml/ref/alter_table.sgml       |  497 ---
 doc/src/sgml/ref/alter_trigger.sgml     |  178 --
 doc/src/sgml/ref/alter_user.sgml        |  280 --
 doc/src/sgml/ref/analyze.sgml           |  220 --
 doc/src/sgml/ref/begin.sgml             |  229 --
 doc/src/sgml/ref/checkpoint.sgml        |   63 -
 doc/src/sgml/ref/close.sgml             |  167 -
 doc/src/sgml/ref/cluster.sgml           |  246 --
 doc/src/sgml/ref/comment.sgml           |  213 --
 doc/src/sgml/ref/commit.sgml            |  164 -
 doc/src/sgml/ref/copy.sgml              |  703 -----
 doc/src/sgml/ref/create_aggregate.sgml  |  316 --
 doc/src/sgml/ref/create_constraint.sgml |  149 -
 doc/src/sgml/ref/create_database.sgml   |  368 ---
 doc/src/sgml/ref/create_domain.sgml     |  242 --
 doc/src/sgml/ref/create_function.sgml   |  570 ----
 doc/src/sgml/ref/create_group.sgml      |  176 --
 doc/src/sgml/ref/create_index.sgml      |  458 ---
 doc/src/sgml/ref/create_language.sgml   |  314 --
 doc/src/sgml/ref/create_operator.sgml   |  506 ---
 doc/src/sgml/ref/create_rule.sgml       |  344 --
 doc/src/sgml/ref/create_schema.sgml     |  240 --
 doc/src/sgml/ref/create_sequence.sgml   |  398 ---
 doc/src/sgml/ref/create_table.sgml      |  904 ------
 doc/src/sgml/ref/create_table_as.sgml   |  170 -
 doc/src/sgml/ref/create_trigger.sgml    |  319 --
 doc/src/sgml/ref/create_type.sgml       |  467 ---
 doc/src/sgml/ref/create_user.sgml       |  274 --
 doc/src/sgml/ref/create_view.sgml       |  275 --
 doc/src/sgml/ref/createdb.sgml          |  282 --
 doc/src/sgml/ref/createlang.sgml        |  225 --
 doc/src/sgml/ref/createuser.sgml        |  294 --
 doc/src/sgml/ref/current_date.sgml      |  148 -
 doc/src/sgml/ref/current_time.sgml      |  158 -
 doc/src/sgml/ref/current_timestamp.sgml |  166 -
 doc/src/sgml/ref/current_user.sgml      |  167 -
 doc/src/sgml/ref/declare.sgml           |  329 --
 doc/src/sgml/ref/delete.sgml            |  211 --
 doc/src/sgml/ref/drop_aggregate.sgml    |  176 --
 doc/src/sgml/ref/drop_database.sgml     |  171 -
 doc/src/sgml/ref/drop_domain.sgml       |  185 --
 doc/src/sgml/ref/drop_function.sgml     |  175 --
 doc/src/sgml/ref/drop_group.sgml        |  136 -
 doc/src/sgml/ref/drop_index.sgml        |  167 -
 doc/src/sgml/ref/drop_language.sgml     |  174 --
 doc/src/sgml/ref/drop_operator.sgml     |  225 --
 doc/src/sgml/ref/drop_rule.sgml         |  173 --
 doc/src/sgml/ref/drop_sequence.sgml     |  163 -
 doc/src/sgml/ref/drop_table.sgml        |  196 --
 doc/src/sgml/ref/drop_trigger.sgml      |  172 -
 doc/src/sgml/ref/drop_type.sgml         |  179 --
 doc/src/sgml/ref/drop_user.sgml         |  148 -
 doc/src/sgml/ref/drop_view.sgml         |  208 --
 doc/src/sgml/ref/dropdb.sgml            |  221 --
 doc/src/sgml/ref/droplang.sgml          |  206 --
 doc/src/sgml/ref/dropuser.sgml          |  213 --
 doc/src/sgml/ref/ecpg-ref.sgml          |  426 ---
 doc/src/sgml/ref/end.sgml               |  168 -
 doc/src/sgml/ref/explain.sgml           |  274 --
 doc/src/sgml/ref/fetch.sgml             |  405 ---
 doc/src/sgml/ref/grant.sgml             |  384 ---
 doc/src/sgml/ref/initdb.sgml            |  298 --
 doc/src/sgml/ref/initlocation.sgml      |   88 -
 doc/src/sgml/ref/insert.sgml            |  271 --
 doc/src/sgml/ref/ipcclean.sgml          |   84 -
 doc/src/sgml/ref/listen.sgml            |  210 --
 doc/src/sgml/ref/load.sgml              |   79 -
 doc/src/sgml/ref/lock.sgml              |  523 ----
 doc/src/sgml/ref/move.sgml              |  148 -
 doc/src/sgml/ref/notify.sgml            |  252 --
 doc/src/sgml/ref/pg_config-ref.sgml     |  165 -
 doc/src/sgml/ref/pg_ctl-ref.sgml        |  368 ---
 doc/src/sgml/ref/pg_dump.sgml           |  745 -----
 doc/src/sgml/ref/pg_dumpall.sgml        |  203 --
 doc/src/sgml/ref/pg_restore.sgml        |  706 -----
 doc/src/sgml/ref/pgaccess-ref.sgml      |  405 ---
 doc/src/sgml/ref/pgtclsh.sgml           |   83 -
 doc/src/sgml/ref/pgtksh.sgml            |   86 -
 doc/src/sgml/ref/postgres-ref.sgml      |  422 ---
 doc/src/sgml/ref/postmaster.sgml        |  528 ----
 doc/src/sgml/ref/psql-ref.sgml          | 2553 ---------------
 doc/src/sgml/ref/reindex.sgml           |  270 --
 doc/src/sgml/ref/reset.sgml             |  122 -
 doc/src/sgml/ref/revoke.sgml            |  154 -
 doc/src/sgml/ref/rollback.sgml          |  152 -
 doc/src/sgml/ref/select.sgml            | 1077 -------
 doc/src/sgml/ref/select_into.sgml       |  165 -
 doc/src/sgml/ref/set.sgml               |  515 ---
 doc/src/sgml/ref/set_constraints.sgml   |   76 -
 doc/src/sgml/ref/set_session_auth.sgml  |  120 -
 doc/src/sgml/ref/set_transaction.sgml   |  135 -
 doc/src/sgml/ref/show.sgml              |  124 -
 doc/src/sgml/ref/truncate.sgml          |  142 -
 doc/src/sgml/ref/unlisten.sgml          |  193 --
 doc/src/sgml/ref/update.sgml            |  219 --
 doc/src/sgml/ref/vacuum.sgml            |  305 --
 doc/src/sgml/ref/vacuumdb.sgml          |  310 --
 doc/src/sgml/refentry.sgml              |    1 -
 doc/src/sgml/reference.ced              | 1597 ----------
 doc/src/sgml/reference.sgml             |  218 --
 doc/src/sgml/regress.sgml               |  437 ---
 doc/src/sgml/release.sgml               | 4444 --------------------------
 doc/src/sgml/rules.sgml                 | 2026 ------------
 doc/src/sgml/runtime.sgml               | 2736 ----------------
 doc/src/sgml/sources.sgml               |   84 -
 doc/src/sgml/spi.sgml                   | 3921 -----------------------
 doc/src/sgml/sql.sgml                   | 2156 -------------
 doc/src/sgml/standalone-install.sgml    |   42 -
 doc/src/sgml/start.sgml                 |  420 ---
 doc/src/sgml/stylesheet.css             |   59 -
 doc/src/sgml/stylesheet.dsl             |  623 ----
 doc/src/sgml/syntax.sgml                | 1503 ---------
 doc/src/sgml/trigger.sgml               |  635 ----
 doc/src/sgml/tutorial.sgml              |   72 -
 doc/src/sgml/typeconv.sgml              |  903 ------
 doc/src/sgml/user-manag.sgml            |  212 --
 doc/src/sgml/user.sgml                  |   59 -
 doc/src/sgml/version.sgml               |    7 -
 doc/src/sgml/wal.sgml                   |  379 ---
 doc/src/sgml/xaggr.sgml                 |  137 -
 doc/src/sgml/xfunc.sgml                 | 1887 -----------
 doc/src/sgml/xindex.sgml                |  595 ----
 doc/src/sgml/xoper.sgml                 |  507 ---
 doc/src/sgml/xplang.sgml                |  179 --
 doc/src/sgml/xtypes.sgml                |  207 --
 doc/src/sgml/y2k.sgml                   |   95 -
 214 files changed, 127514 deletions(-)
 delete mode 100644 doc/src/FAQ/FAQ.html
 delete mode 100644 doc/src/FAQ/FAQ_DEV.html
 delete mode 100644 doc/src/FAQ/FAQ_german.html
 delete mode 100644 doc/src/FAQ/FAQ_japanese.html
 delete mode 100644 doc/src/FAQ/FAQ_polish.html
 delete mode 100644 doc/src/FAQ/FAQ_russian.html
 delete mode 100644 doc/src/Makefile
 delete mode 100644 doc/src/graphics/catalogs.ag
 delete mode 100644 doc/src/graphics/catalogs.cgm
 delete mode 100644 doc/src/graphics/catalogs.gif
 delete mode 100644 doc/src/graphics/catalogs.ps
 delete mode 100644 doc/src/graphics/clientserver.ag
 delete mode 100644 doc/src/graphics/clientserver.gif
 delete mode 100644 doc/src/graphics/connections.ag
 delete mode 100644 doc/src/graphics/connections.gif
 delete mode 100644 doc/src/sgml/Makefile
 delete mode 100644 doc/src/sgml/admin.sgml
 delete mode 100644 doc/src/sgml/advanced.sgml
 delete mode 100644 doc/src/sgml/arch-dev.sgml
 delete mode 100644 doc/src/sgml/arch-pg.sgml
 delete mode 100644 doc/src/sgml/array.sgml
 delete mode 100644 doc/src/sgml/backup.sgml
 delete mode 100644 doc/src/sgml/biblio.sgml
 delete mode 100644 doc/src/sgml/bki.sgml
 delete mode 100644 doc/src/sgml/book-decl.sgml
 delete mode 100644 doc/src/sgml/catalogs.sgml
 delete mode 100644 doc/src/sgml/charset.sgml
 delete mode 100644 doc/src/sgml/client-auth.sgml
 delete mode 100644 doc/src/sgml/compiler.sgml
 delete mode 100644 doc/src/sgml/contacts.sgml
 delete mode 100644 doc/src/sgml/cvs.sgml
 delete mode 100644 doc/src/sgml/datatype.sgml
 delete mode 100644 doc/src/sgml/datetime.sgml
 delete mode 100644 doc/src/sgml/developer.sgml
 delete mode 100644 doc/src/sgml/dfunc.sgml
 delete mode 100644 doc/src/sgml/diskusage.sgml
 delete mode 100644 doc/src/sgml/docguide.sgml
 delete mode 100644 doc/src/sgml/ecpg.sgml
 delete mode 100644 doc/src/sgml/extend.sgml
 delete mode 100644 doc/src/sgml/features.sgml
 delete mode 100644 doc/src/sgml/filelist.sgml
 delete mode 100755 doc/src/sgml/fixrtf
 delete mode 100644 doc/src/sgml/func-ref.sgml
 delete mode 100644 doc/src/sgml/func.sgml
 delete mode 100644 doc/src/sgml/geqo.sgml
 delete mode 100644 doc/src/sgml/gist.sgml
 delete mode 100644 doc/src/sgml/history.sgml
 delete mode 100644 doc/src/sgml/indexcost.sgml
 delete mode 100644 doc/src/sgml/indices.sgml
 delete mode 100644 doc/src/sgml/info.sgml
 delete mode 100644 doc/src/sgml/inherit.sgml
 delete mode 100644 doc/src/sgml/install-win32.sgml
 delete mode 100644 doc/src/sgml/installation.sgml
 delete mode 100644 doc/src/sgml/intro.sgml
 delete mode 100644 doc/src/sgml/jdbc.sgml
 delete mode 100644 doc/src/sgml/keywords.sgml
 delete mode 100644 doc/src/sgml/legal.sgml
 delete mode 100644 doc/src/sgml/libpgeasy.sgml
 delete mode 100644 doc/src/sgml/libpgtcl.sgml
 delete mode 100644 doc/src/sgml/libpq++.sgml
 delete mode 100644 doc/src/sgml/libpq.sgml
 delete mode 100644 doc/src/sgml/lobj.sgml
 delete mode 100644 doc/src/sgml/maintenance.sgml
 delete mode 100644 doc/src/sgml/manage-ag.sgml
 delete mode 100644 doc/src/sgml/manage.sgml
 delete mode 100644 doc/src/sgml/monitoring.sgml
 delete mode 100644 doc/src/sgml/mvcc.sgml
 delete mode 100644 doc/src/sgml/nls.sgml
 delete mode 100644 doc/src/sgml/notation.sgml
 delete mode 100644 doc/src/sgml/odbc.sgml
 delete mode 100644 doc/src/sgml/page.sgml
 delete mode 100644 doc/src/sgml/perform.sgml
 delete mode 100644 doc/src/sgml/plperl.sgml
 delete mode 100644 doc/src/sgml/plpython.sgml
 delete mode 100644 doc/src/sgml/plsql.sgml
 delete mode 100644 doc/src/sgml/pltcl.sgml
 delete mode 100644 doc/src/sgml/postgres.sgml
 delete mode 100644 doc/src/sgml/problems.sgml
 delete mode 100644 doc/src/sgml/programmer.sgml
 delete mode 100644 doc/src/sgml/protocol.sgml
 delete mode 100644 doc/src/sgml/pygresql.sgml
 delete mode 100644 doc/src/sgml/queries.sgml
 delete mode 100644 doc/src/sgml/query.sgml
 delete mode 100644 doc/src/sgml/recovery.sgml
 delete mode 100644 doc/src/sgml/ref/abort.sgml
 delete mode 100644 doc/src/sgml/ref/allfiles.sgml
 delete mode 100644 doc/src/sgml/ref/alter_database.sgml
 delete mode 100644 doc/src/sgml/ref/alter_group.sgml
 delete mode 100644 doc/src/sgml/ref/alter_table.sgml
 delete mode 100644 doc/src/sgml/ref/alter_trigger.sgml
 delete mode 100644 doc/src/sgml/ref/alter_user.sgml
 delete mode 100644 doc/src/sgml/ref/analyze.sgml
 delete mode 100644 doc/src/sgml/ref/begin.sgml
 delete mode 100644 doc/src/sgml/ref/checkpoint.sgml
 delete mode 100644 doc/src/sgml/ref/close.sgml
 delete mode 100644 doc/src/sgml/ref/cluster.sgml
 delete mode 100644 doc/src/sgml/ref/comment.sgml
 delete mode 100644 doc/src/sgml/ref/commit.sgml
 delete mode 100644 doc/src/sgml/ref/copy.sgml
 delete mode 100644 doc/src/sgml/ref/create_aggregate.sgml
 delete mode 100644 doc/src/sgml/ref/create_constraint.sgml
 delete mode 100644 doc/src/sgml/ref/create_database.sgml
 delete mode 100644 doc/src/sgml/ref/create_domain.sgml
 delete mode 100644 doc/src/sgml/ref/create_function.sgml
 delete mode 100644 doc/src/sgml/ref/create_group.sgml
 delete mode 100644 doc/src/sgml/ref/create_index.sgml
 delete mode 100644 doc/src/sgml/ref/create_language.sgml
 delete mode 100644 doc/src/sgml/ref/create_operator.sgml
 delete mode 100644 doc/src/sgml/ref/create_rule.sgml
 delete mode 100644 doc/src/sgml/ref/create_schema.sgml
 delete mode 100644 doc/src/sgml/ref/create_sequence.sgml
 delete mode 100644 doc/src/sgml/ref/create_table.sgml
 delete mode 100644 doc/src/sgml/ref/create_table_as.sgml
 delete mode 100644 doc/src/sgml/ref/create_trigger.sgml
 delete mode 100644 doc/src/sgml/ref/create_type.sgml
 delete mode 100644 doc/src/sgml/ref/create_user.sgml
 delete mode 100644 doc/src/sgml/ref/create_view.sgml
 delete mode 100644 doc/src/sgml/ref/createdb.sgml
 delete mode 100644 doc/src/sgml/ref/createlang.sgml
 delete mode 100644 doc/src/sgml/ref/createuser.sgml
 delete mode 100644 doc/src/sgml/ref/current_date.sgml
 delete mode 100644 doc/src/sgml/ref/current_time.sgml
 delete mode 100644 doc/src/sgml/ref/current_timestamp.sgml
 delete mode 100644 doc/src/sgml/ref/current_user.sgml
 delete mode 100644 doc/src/sgml/ref/declare.sgml
 delete mode 100644 doc/src/sgml/ref/delete.sgml
 delete mode 100644 doc/src/sgml/ref/drop_aggregate.sgml
 delete mode 100644 doc/src/sgml/ref/drop_database.sgml
 delete mode 100644 doc/src/sgml/ref/drop_domain.sgml
 delete mode 100644 doc/src/sgml/ref/drop_function.sgml
 delete mode 100644 doc/src/sgml/ref/drop_group.sgml
 delete mode 100644 doc/src/sgml/ref/drop_index.sgml
 delete mode 100644 doc/src/sgml/ref/drop_language.sgml
 delete mode 100644 doc/src/sgml/ref/drop_operator.sgml
 delete mode 100644 doc/src/sgml/ref/drop_rule.sgml
 delete mode 100644 doc/src/sgml/ref/drop_sequence.sgml
 delete mode 100644 doc/src/sgml/ref/drop_table.sgml
 delete mode 100644 doc/src/sgml/ref/drop_trigger.sgml
 delete mode 100644 doc/src/sgml/ref/drop_type.sgml
 delete mode 100644 doc/src/sgml/ref/drop_user.sgml
 delete mode 100644 doc/src/sgml/ref/drop_view.sgml
 delete mode 100644 doc/src/sgml/ref/dropdb.sgml
 delete mode 100644 doc/src/sgml/ref/droplang.sgml
 delete mode 100644 doc/src/sgml/ref/dropuser.sgml
 delete mode 100644 doc/src/sgml/ref/ecpg-ref.sgml
 delete mode 100644 doc/src/sgml/ref/end.sgml
 delete mode 100644 doc/src/sgml/ref/explain.sgml
 delete mode 100644 doc/src/sgml/ref/fetch.sgml
 delete mode 100644 doc/src/sgml/ref/grant.sgml
 delete mode 100644 doc/src/sgml/ref/initdb.sgml
 delete mode 100644 doc/src/sgml/ref/initlocation.sgml
 delete mode 100644 doc/src/sgml/ref/insert.sgml
 delete mode 100644 doc/src/sgml/ref/ipcclean.sgml
 delete mode 100644 doc/src/sgml/ref/listen.sgml
 delete mode 100644 doc/src/sgml/ref/load.sgml
 delete mode 100644 doc/src/sgml/ref/lock.sgml
 delete mode 100644 doc/src/sgml/ref/move.sgml
 delete mode 100644 doc/src/sgml/ref/notify.sgml
 delete mode 100644 doc/src/sgml/ref/pg_config-ref.sgml
 delete mode 100644 doc/src/sgml/ref/pg_ctl-ref.sgml
 delete mode 100644 doc/src/sgml/ref/pg_dump.sgml
 delete mode 100644 doc/src/sgml/ref/pg_dumpall.sgml
 delete mode 100644 doc/src/sgml/ref/pg_restore.sgml
 delete mode 100644 doc/src/sgml/ref/pgaccess-ref.sgml
 delete mode 100644 doc/src/sgml/ref/pgtclsh.sgml
 delete mode 100644 doc/src/sgml/ref/pgtksh.sgml
 delete mode 100644 doc/src/sgml/ref/postgres-ref.sgml
 delete mode 100644 doc/src/sgml/ref/postmaster.sgml
 delete mode 100644 doc/src/sgml/ref/psql-ref.sgml
 delete mode 100644 doc/src/sgml/ref/reindex.sgml
 delete mode 100644 doc/src/sgml/ref/reset.sgml
 delete mode 100644 doc/src/sgml/ref/revoke.sgml
 delete mode 100644 doc/src/sgml/ref/rollback.sgml
 delete mode 100644 doc/src/sgml/ref/select.sgml
 delete mode 100644 doc/src/sgml/ref/select_into.sgml
 delete mode 100644 doc/src/sgml/ref/set.sgml
 delete mode 100644 doc/src/sgml/ref/set_constraints.sgml
 delete mode 100644 doc/src/sgml/ref/set_session_auth.sgml
 delete mode 100644 doc/src/sgml/ref/set_transaction.sgml
 delete mode 100644 doc/src/sgml/ref/show.sgml
 delete mode 100644 doc/src/sgml/ref/truncate.sgml
 delete mode 100644 doc/src/sgml/ref/unlisten.sgml
 delete mode 100644 doc/src/sgml/ref/update.sgml
 delete mode 100644 doc/src/sgml/ref/vacuum.sgml
 delete mode 100644 doc/src/sgml/ref/vacuumdb.sgml
 delete mode 100644 doc/src/sgml/refentry.sgml
 delete mode 100644 doc/src/sgml/reference.ced
 delete mode 100644 doc/src/sgml/reference.sgml
 delete mode 100644 doc/src/sgml/regress.sgml
 delete mode 100644 doc/src/sgml/release.sgml
 delete mode 100644 doc/src/sgml/rules.sgml
 delete mode 100644 doc/src/sgml/runtime.sgml
 delete mode 100644 doc/src/sgml/sources.sgml
 delete mode 100644 doc/src/sgml/spi.sgml
 delete mode 100644 doc/src/sgml/sql.sgml
 delete mode 100644 doc/src/sgml/standalone-install.sgml
 delete mode 100644 doc/src/sgml/start.sgml
 delete mode 100644 doc/src/sgml/stylesheet.css
 delete mode 100644 doc/src/sgml/stylesheet.dsl
 delete mode 100644 doc/src/sgml/syntax.sgml
 delete mode 100644 doc/src/sgml/trigger.sgml
 delete mode 100644 doc/src/sgml/tutorial.sgml
 delete mode 100644 doc/src/sgml/typeconv.sgml
 delete mode 100644 doc/src/sgml/user-manag.sgml
 delete mode 100644 doc/src/sgml/user.sgml
 delete mode 100644 doc/src/sgml/version.sgml
 delete mode 100644 doc/src/sgml/wal.sgml
 delete mode 100644 doc/src/sgml/xaggr.sgml
 delete mode 100644 doc/src/sgml/xfunc.sgml
 delete mode 100644 doc/src/sgml/xindex.sgml
 delete mode 100644 doc/src/sgml/xoper.sgml
 delete mode 100644 doc/src/sgml/xplang.sgml
 delete mode 100644 doc/src/sgml/xtypes.sgml
 delete mode 100644 doc/src/sgml/y2k.sgml

(limited to 'doc/src')

diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
deleted file mode 100644
index 32762e38ea2..00000000000
--- a/doc/src/FAQ/FAQ.html
+++ /dev/null
@@ -1,1349 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD html 4.01 transitional//EN">
-
-<HTML>
-  <!-- DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN" -->
-  <!-- HTML -->
-
-  <HEAD>
-    <META name="generator" content="HTML Tidy, see www.w3.org">
-
-    <TITLE>PostgreSQL FAQ</TITLE>
-  </HEAD>
-
-  <BODY bgcolor="#ffffff" text="#000000" link="#ff0000" vlink="#a00000"
-  alink="#0000ff">
-    <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
-
-    <P>Last updated: Tue Jun 11 06:36:10 EDT 2002</P>
-
-    <P>Current maintainer: Bruce Momjian (<A href=
-    "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
-    </P>
-
-    <P>The most recent version of this document can be viewed at <A
-    href=
-    "http://www.Postgresql.org/docs/faq-english.html">http://www.PostgreSQL.org/docs/faq-english.html</A>.</P>
-
-    <P>Platform-specific questions are answered at <A href=
-    "http://www.PostgreSQL.org/users-lounge/docs/faq.html">http://www.PostgreSQL.org/users-lounge/docs/faq.html</A>.</P>
-    <HR>
-
-    <H2 align="center">General Questions</H2>
-    <A href="#1.1">1.1</A>) What is PostgreSQL? How is it
-    pronounced?<BR>
-     <A href="#1.2">1.2</A>) What is the copyright on PostgreSQL?<BR>
-     <A href="#1.3">1.3</A>) What Unix platforms does PostgreSQL run
-    on?<BR>
-     <A href="#1.4">1.4</A>) What non-Unix ports are available?<BR>
-     <A href="#1.5">1.5</A>) Where can I get PostgreSQL?<BR>
-     <A href="#1.6">1.6</A>) Where can I get support?<BR>
-     <A href="#1.7">1.7</A>) What is the latest release?<BR>
-     <A href="#1.8">1.8</A>) What documentation is available?<BR>
-     <A href="#1.9">1.9</A>) How do I find out about known bugs or
-    missing features?<BR>
-     <A href="#1.10">1.10</A>) How can I learn <SMALL>SQL</SMALL>?<BR>
-     <A href="#1.11">1.11</A>) Is PostgreSQL Y2K compliant?<BR>
-     <A href="#1.12">1.12</A>) How do I join the development team?<BR>
-     <A href="#1.13">1.13</A>) How do I submit a bug report?<BR>
-     <A href="#1.14">1.14</A>) How does PostgreSQL compare to other
-    <SMALL>DBMS</SMALL>s?<BR>
-     <A href="#1.15">1.15</A>) How can I financially assist
-    PostgreSQL?<BR>
-     
-
-    <H2 align="center">User Client Questions</H2>
-    <A href="#2.1">2.1</A>) Are there <SMALL>ODBC</SMALL> drivers for
-    PostgreSQL?<BR>
-     <A href="#2.2">2.2</A>) What tools are available for using
-    PostgreSQL with Web pages?<BR>
-     <A href="#2.3">2.3</A>) Does PostgreSQL have a graphical user
-    interface? A report generator? An embedded query language
-    interface?<BR>
-     <A href="#2.4">2.4</A>) What languages are available to
-    communicate with PostgreSQL?<BR>
-     
-
-    <H2 align="center">Administrative Questions</H2>
-    <A href="#3.1">3.1</A>) How do I install PostgreSQL somewhere other
-    than <I>/usr/local/pgsql</I>?<BR>
-     <A href="#3.2">3.2</A>) When I start <I>postmaster</I>, I get a
-    <I>Bad System Call</I> or core dumped message. Why?<BR>
-     <A href="#3.3">3.3</A>) When I try to start <I>postmaster</I>, I
-    get <I>IpcMemoryCreate</I> errors. Why?<BR>
-     <A href="#3.4">3.4</A>) When I try to start <I>postmaster</I>, I
-    get <I>IpcSemaphoreCreate</I> errors. Why?<BR>
-     <A href="#3.5">3.5</A>) How do I control connections from other
-    hosts?<BR>
-     <A href="#3.6">3.6</A>) How do I tune the database engine for
-    better performance?<BR>
-     <A href="#3.7">3.7</A>) What debugging features are available?<BR>
-     <A href="#3.8">3.8</A>) Why do I get <I>"Sorry, too many
-    clients"</I> when trying to connect?<BR>
-     <A href="#3.9">3.9</A>) What are the <I>pg_sorttempNNN.NN</I>
-    files in my database directory?<BR>
-     
-
-    <H2 align="center">Operational Questions</H2>
-    <A href="#4.1">4.1</A>) What is the difference between binary
-    cursors and normal cursors?<BR>
-     <A href="#4.2">4.2</A>) How do I <SMALL>SELECT</SMALL> only the
-    first few rows of a query?<BR>
-     <A href="#4.3">4.3</A>) How do I get a list of tables or other
-    things I can see in <I>psql</I>?<BR>
-     <A href="#4.4">4.4</A>) How do you remove a column from a
-    table?<BR>
-     <A href="#4.5">4.5</A>) What is the maximum size for a row, a
-    table, and a database?<BR>
-     <A href="#4.6">4.6</A>) How much database disk space is required
-    to store data from a typical text file?<BR>
-     <A href="#4.7">4.7</A>) How do I find out what tables, indexes,
-    databases, and users are defined?<BR>
-     <A href="#4.8">4.8</A>) My queries are slow or don't make use of
-    the indexes. Why?<BR>
-     <A href="#4.9">4.9</A>) How do I see how the query optimizer is
-    evaluating my query?<BR>
-     <A href="#4.10">4.10</A>) What is an R-tree index?<BR>
-     <A href="#4.11">4.11</A>) What is the Genetic Query Optimizer?<BR>
-     <A href="#4.12">4.12</A>) How do I perform regular expression
-    searches and case-insensitive regular expression searches? How do I
-    use an index for case-insensitive searches?<BR>
-     <A href="#4.13">4.13</A>) In a query, how do I detect if a field
-    is <SMALL>NULL</SMALL>?<BR>
-     <A href="#4.14">4.14</A>) What is the difference between the
-    various character types?<BR>
-     <A href="#4.15.1">4.15.1</A>) How do I create a
-    serial/auto-incrementing field?<BR>
-     <A href="#4.15.2">4.15.2</A>) How do I get the value of a
-    <SMALL>SERIAL</SMALL> insert?<BR>
-     <A href="#4.15.3">4.15.3</A>) Don't <I>currval()</I> and
-    <I>nextval()</I> lead to a race condition with other users?<BR>
-     <A href="#4.15.4">4.15.4</A>) Why aren't my sequence numbers
-    reused on transaction abort? Why are there gaps in the numbering of
-    my sequence/SERIAL column?<BR>
-     <A href="#4.16">4.16</A>) What is an <SMALL>OID</SMALL>? What is a
-    <SMALL>TID</SMALL>?<BR>
-     <A href="#4.17">4.17</A>) What is the meaning of some of the terms
-    used in PostgreSQL?<BR>
-     <A href="#4.18">4.18</A>) Why do I get the error <I>"ERROR: Memory
-    exhausted in AllocSetAlloc()"</I>?<BR>
-     <A href="#4.19">4.19</A>) How do I tell what PostgreSQL version I
-    am running?<BR>
-     <A href="#4.20">4.20</A>) Why does my large-object operations get
-    <I>"invalid large obj descriptor"</I>?<BR>
-     <A href="#4.21">4.21</A>) How do I create a column that will
-    default to the current time?<BR>
-     <A href="#4.22">4.22</A>) Why are my subqueries using
-    <CODE><SMALL>IN</SMALL></CODE> so slow?<BR>
-     <A href="#4.23">4.23</A>) How do I perform an outer join?<BR>
-     <A href="#4.24">4.24</A>) How do I perform queries using multiple
-    databases?<BR>
-     <A href="#4.25">4.25</A>) How do I return multiple rows or columns
-    from a function?<BR>
-     <A href="#4.26">4.26</A>) Why can't I reliably create/drop
-    temporary tables in PL/PgSQL functions?<BR>
-     
-
-    <H2 align="center">Extending PostgreSQL</H2>
-    <A href="#5.1">5.1</A>) I wrote a user-defined function. When I run
-    it in <I>psql</I>, why does it dump core?<BR>
-     <A href="#5.2">5.2</A>) How can I contribute some nifty new types
-    and functions to PostgreSQL?<BR>
-     <A href="#5.3">5.3</A>) How do I write a C function to return a
-    tuple?<BR>
-     <A href="#5.4">5.4</A>) I have changed a source file. Why does the
-    recompile not see the change?<BR>
-     
-    <HR>
-
-    <H2 align="center">General Questions</H2>
-
-    <H4><A name="1.1">1.1</A>) What is PostgreSQL?</H4>
-
-    <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>.</P>
-
-    <P>PostgreSQL is an enhancement of the POSTGRES database management
-    system, a next-generation <SMALL>DBMS</SMALL> research prototype.
-    While PostgreSQL retains the powerful data model and rich data
-    types of POSTGRES, it replaces the PostQuel query language with an
-    extended subset of <SMALL>SQL</SMALL>. PostgreSQL is free and the
-    complete source is available.</P>
-
-    <P>PostgreSQL development is performed by a team of Internet
-    developers who all subscribe to the PostgreSQL development mailing
-    list. The current coordinator is Marc G. Fournier (<A href=
-    "mailto:scrappy@PostgreSQL.org">scrappy@PostgreSQL.org</A>). (See
-    below on how to join). This team is now responsible for all
-    development of PostgreSQL.</P>
-
-    <P>The authors of PostgreSQL 1.01 were Andrew Yu and Jolly Chen.
-    Many others have contributed to the porting, testing, debugging,
-    and enhancement of the code. The original Postgres code, from which
-    PostgreSQL is derived, was the effort of many graduate students,
-    undergraduate students, and staff programmers working under the
-    direction of Professor Michael Stonebraker at the University of
-    California, Berkeley.</P>
-
-    <P>The original name of the software at Berkeley was Postgres. When
-    <SMALL>SQL</SMALL> functionality was added in 1995, its name was
-    changed to Postgres95. The name was changed at the end of 1996 to
-    PostgreSQL.</P>
-
-    <H4><A name="1.2">1.2</A>) What is the copyright on
-    PostgreSQL?</H4>
-
-    <P>PostgreSQL is subject to the following COPYRIGHT:</P>
-
-    <P>PostgreSQL Data Base Management System</P>
-
-    <P>Portions copyright (c) 1996-2002, PostgreSQL Global Development
-    Group Portions Copyright (c) 1994-6 Regents of the University of
-    California</P>
-
-    <P>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.</P>
-
-    <P>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.</P>
-
-    <P>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 "AS IS" BASIS, AND THE
-    UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE,
-    SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.</P>
-
-    <P>The above is the BSD license, the classic open-source license.
-    It has no restrictions on how the source code may be used. We like
-    it and have no intention of changing it.</P>
-
-    <H4><A name="1.3">1.3</A>) What Unix platforms does PostgreSQL run
-    on?</H4>
-
-    <P>In general, a modern Unix-compatible platform should be able to
-    run PostgreSQL. The platforms that had received explicit testing at
-    the time of release are listed in the installation
-    instructions.</P>
-
-    <H4><A name="1.4">1.4</A>) What non-Unix ports are available?</H4>
-
-    <P><STRONG>Client</STRONG></P>
-
-    <P>It is possible to compile the <I>libpq</I> C library, psql, and
-    other interfaces and binaries to run on MS Windows platforms. In
-    this case, the client is running on MS Windows, and communicates
-    via TCP/IP to a server running on one of our supported Unix
-    platforms. A file <I>win31.mak</I> is included in the distribution
-    for making a Win32 <I>libpq</I> library and <I>psql</I>. PostgreSQL
-    also communicates with <SMALL>ODBC</SMALL> clients.</P>
-
-    <P><STRONG>Server</STRONG></P>
-
-    <P>The database server can run on Windows NT and Win2k using
-    Cygwin, the Cygnus Unix/NT porting library. See
-    <I>pgsql/doc/FAQ_MSWIN</I> in the distribution or the <A href=
-    "http://www.postgresql.org/docs/faq-mswin.html">MS Windows FAQ</A>
-    on our web site. We have no plan to do a native port to any
-    Microsoft platform.</P>
-
-    <H4><A name="1.5">1.5</A>) Where can I get PostgreSQL?</H4>
-
-    <P>The primary anonymous ftp site for PostgreSQL is <A href=
-    "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub</A>.
-    For mirror sites, see our main web site.</P>
-
-    <H4><A name="1.6">1.6</A>) Where can I get support?</H4>
-
-    <P>The main mailing list is: <A href=
-    "mailto:pgsql-general@PostgreSQL.org">pgsql-general@PostgreSQL.org</A>.
-    It is available for discussion of matters pertaining to PostgreSQL.
-    To subscribe, send mail with the following lines in the body (not
-    the subject line):</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-
-    <P>to <A href=
-    "mailto:pgsql-general-request@PostgreSQL.org">pgsql-general-request@PostgreSQL.org</A>.</P>
-
-    <P>There is also a digest list available. To subscribe to this
-    list, send email to: <A href=
-    "mailto:pgsql-general-digest-request@PostgreSQL.org">pgsql-general-digest-request@PostgreSQL.org</A>
-    with a body of:</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-    Digests are sent out to members of this list whenever the main list
-    has received around 30k of messages. 
-
-    <P>The bugs mailing list is available. To subscribe to this list,
-    send email to <A href=
-    "mailto:pgsql-bugs-request@PostgreSQL.org">pgsql-bugs-request@PostgreSQL.org</A>
-    with a body of:</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-    There is also a developers discussion mailing list available. To
-    subscribe to this list, send email to <A href=
-    "mailto:pgsql-hackers-request@PostgreSQL.org">pgsql-hackers-request@PostgreSQL.org</A>
-    with a body of: 
-<PRE>
-    subscribe
-    end
-</PRE>
-
-    <P>Additional mailing lists and information about PostgreSQL can be
-    found via the PostgreSQL WWW home page at:</P>
-
-    <BLOCKQUOTE>
-      <A href="http://www.PostgreSQL.org">http://www.PostgreSQL.org</A>
-    </BLOCKQUOTE>
-
-    <P>There is also an IRC channel on EFNet, channel
-    <I>#PostgreSQL</I>. I use the Unix command <CODE>irc -c
-    '#PostgreSQL' "$USER" irc.phoenix.net.</CODE></P>
-
-    <P>A list of commercial support companies is available at <A href=
-    "http://www.postgresql.org/users-lounge/commercial-support.html">http://www.postgresql.org/users-lounge/commercial-support.html</A>.</P>
-
-    <H4><A name="1.7">1.7</A>) What is the latest release?</H4>
-
-    <P>The latest release of PostgreSQL is version 7.2.1.</P>
-
-    <P>We plan to have major releases every four months.</P>
-
-    <H4><A name="1.8">1.8</A>) What documentation is available?</H4>
-
-    <P>Several manuals, manual pages, and some small test examples are
-    included in the distribution. See the <I>/doc</I> directory. You
-    can also browse the manual online at <A href=
-    "http://www.PostgreSQL.org/users-lounge/docs/">http://www.PostgreSQL.org/users-lounge/docs/</A>.</P>
-
-    <P>There are two PostgreSQL books available online at <A href=
-    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
-    and <A href=
-    "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook/</A>.
-    There is a list of PostgreSQL books available for purchase at <A
-    href=
-    "http://www.postgresql.org/books/">http://www.postgresql.org/books/</A>.
-    There is also a collection of PostgreSQL technical articles at <A
-    href=
-    "http://techdocs.postgresql.org/">http://techdocs.postgresql.org/</A>.</P>
-
-    <P><I>psql</I> has some nice \d commands to show information about
-    types, operators, functions, aggregates, etc.</P>
-
-    <P>Our web site contains even more documentation.</P>
-
-    <H4><A name="1.9">1.9</A>) How do I find out about known bugs or
-    missing features?</H4>
-
-    <P>PostgreSQL supports an extended subset of <SMALL>SQL</SMALL>-92.
-    See our <A href="http://developer.PostgreSQL.org/todo.php">TODO</A>
-    list for known bugs, missing features, and future plans.</P>
-
-    <H4><A name="1.10">1.10</A>) How can I learn
-    <SMALL>SQL</SMALL>?</H4>
-
-    <P>The PostgreSQL book at <A href=
-    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
-    teaches <SMALL>SQL</SMALL>. There is another PostgreSQL book at <A
-    href=
-    "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook.</A>
-    There is a nice tutorial at <A href=
-    "http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A>
-    at <A href=
-    "http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM">
-    http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM,</A>
-    and at <A href=
-    "http://sqlcourse.com/">http://sqlcourse.com.</A></P>
-
-    <P>Another one is "Teach Yourself SQL in 21 Days, Second Edition"
-    at <A href=
-    "http://members.tripod.com/er4ebus/sql/index.htm">http://members.tripod.com/er4ebus/sql/index.htm</A></P>
-
-    <P>Many of our users like <I>The Practical SQL Handbook</I>,
-    Bowman, Judith S., et al., Addison-Wesley. Others like <I>The
-    Complete Reference SQL</I>, Groff et al., McGraw-Hill.</P>
-
-    <H4><A name="1.11">1.11</A>) Is PostgreSQL Y2K compliant?</H4>
-
-    <P>Yes, we easily handle dates past the year 2000 AD, and before
-    2000 BC.</P>
-
-    <H4><A name="1.12">1.12</A>) How do I join the development
-    team?</H4>
-
-    <P>First, download the latest source and read the PostgreSQL
-    Developers documentation on our web site, or in the distribution.
-    Second, subscribe to the <I>pgsql-hackers</I> and
-    <I>pgsql-patches</I> mailing lists. Third, submit high quality
-    patches to pgsql-patches.</P>
-
-    <P>There are about a dozen people who have commit privileges to the
-    PostgreSQL <SMALL>CVS</SMALL> archive. They each have submitted so
-    many high-quality patches that it was impossible for the existing
-    committers to keep up, and we had confidence that patches they
-    committed were of high quality.</P>
-
-    <H4><A name="1.13">1.13</A>) How do I submit a bug report?</H4>
-
-    <P>Please visit the <A href=
-    "http://www.postgresql.org/bugs/bugs.php">PostgreSQL BugTool</A>
-    page, which gives guidelines and directions on how to submit a
-    bug.</P>
-
-    <P>Also check out our ftp site <A href=
-    "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub</A> to
-    see if there is a more recent PostgreSQL version or patches.</P>
-
-    <H4><A name="1.14">1.14</A>) How does PostgreSQL compare to other
-    <SMALL>DBMS</SMALL>s?</H4>
-
-    <P>There are several ways of measuring software: features,
-    performance, reliability, support, and price.</P>
-
-    <DL>
-      <DT><B>Features</B></DT>
-
-      <DD>PostgreSQL has most features present in large commercial
-      <SMALL>DBMS</SMALL>s, like transactions, subselects, triggers,
-      views, foreign key referential integrity, and sophisticated
-      locking. We have some features they do not have, like
-      user-defined types, inheritance, rules, and multi-version
-      concurrency control to reduce lock contention.<BR>
-      <BR>
-      </DD>
-
-      <DT><B>Performance</B></DT>
-
-      <DD>PostgreSQL has performance similar to other commercial and
-      open source databases. it is faster for some things, slower for
-      others. In comparison to MySQL or leaner database systems, we are
-      slower on inserts/updates because of transaction overhead. Of
-      course, MySQL does not have any of the features mentioned in the
-      <I>Features</I> section above. We are built for reliability and
-      features, though we continue to improve performance in every
-      release. There is an interesting Web page comparing PostgreSQL to
-      MySQL at <A href= "http://openacs.org/why-not-mysql.html">
-
-      http://openacs.org/why-not-mysql.html</A><BR>
-
-      <BR>
-      </DD>
-
-      <DT><B>Reliability</B></DT>
-
-      <DD>We realize that a <SMALL>DBMS</SMALL> must be reliable, or it
-      is worthless. We strive to release well-tested, stable code that
-      has a minimum of bugs. Each release has at least one month of
-      beta testing, and our release history shows that we can provide
-      stable, solid releases that are ready for production use. We
-      believe we compare favorably to other database software in this
-      area.<BR>
-      <BR>
-      </DD>
-
-      <DT><B>Support</B></DT>
-
-      <DD>Our mailing list provides a large group of developers and
-      users to help resolve any problems encountered. While we can not
-      guarantee a fix, commercial <SMALL>DBMS</SMALL>s do not always
-      supply a fix either. Direct access to developers, the user
-      community, manuals, and the source code often make PostgreSQL
-      support superior to other <SMALL>DBMS</SMALL>s. There is
-      commercial per-incident support available for those who need it.
-      (See <A href="#1.6">support FAQ item</A>.)<BR>
-      <BR>
-      </DD>
-
-      <DT><B>Price</B></DT>
-
-      <DD>We are free for all use, both commercial and non-commercial.
-      You can add our code to your product with no limitations, except
-      those outlined in our BSD-style license stated above.<BR>
-      <BR>
-      </DD>
-    </DL>
-
-    <H4><A name="1.15">1.15</A>) How can I financially assist
-    PostgreSQL?</H4>
-
-    <P>PostgreSQL has had a first-class infrastructure since we started
-    six years ago. This is all thanks to Marc Fournier, who has created
-    and managed this infrastructure over the years.</P>
-
-    <P>Quality infrastructure is very important to an open-source
-    project. It prevents disruptions that can greatly delay forward
-    movement of the project.</P>
-
-    <P>Of course, this infrastructure is not cheap. There are a variety
-    of monthly and one-time expenses that are required to keep it
-    going. If you or your company has money it can donate to help fund
-    this effort, please go to <A href=
-    "http://www.pgsql.com/pg_goodies">http://www.pgsql.com/pg_goodies</A>
-    and make a donation.</P>
-
-    <P>Although the web page mentions PostgreSQL, Inc, the
-    "contributions" item is solely to support the PostgreSQL project
-    and does not fund any specific company. If you prefer, you can also
-    send a check to the contact address.</P>
-    <HR>
-
-    <H2 align="center">User Client Questions</H2>
-
-    <H4><A name="2.1">2.1</A>) Are there <SMALL>ODBC</SMALL> drivers
-    for PostgreSQL?</H4>
-
-    <P>There are two <SMALL>ODBC</SMALL> drivers available, PsqlODBC
-    and OpenLink <SMALL>ODBC</SMALL>.</P>
-
-    <P>PsqlODBC is included in the distribution. More information about
-    it can be gotten from <A href=
-    "ftp://ftp.PostgreSQL.org/pub/odbc/">ftp://ftp.PostgreSQL.org/pub/odbc/</A>.</P>
-
-    <P>OpenLink <SMALL>ODBC</SMALL> can be gotten from <A href=
-    "http://www.openlinksw.com/">http://www.openlinksw.com</A>. It
-    works with their standard <SMALL>ODBC</SMALL> client software so
-    you'll have PostgreSQL <SMALL>ODBC</SMALL> available on every
-    client platform they support (Win, Mac, Unix, VMS).</P>
-
-    <P>They will probably be selling this product to people who need
-    commercial-quality support, but a freeware version will always be
-    available. Please send questions to <A href=
-    "mailto:postgres95@openlink.co.uk">postgres95@openlink.co.uk</A>.</P>
-
-    <P>See also the <A href=
-    "http://www.postgresql.org/devel-corner/docs/programmer/odbc.html">ODBC
-    chapter of the Programmer's Guide</A>.</P>
-
-    <H4><A name="2.2">2.2</A>) What tools are available for using
-    PostgreSQL with Web pages?</H4>
-
-    <P>A nice introduction to Database-backed Web pages can be seen at:
-    <A href="http://www.webreview.com">http://www.webreview.com</A></P>
-
-    <P>There is also one at <A href=
-    "http://www.phone.net/home/mwm/hotlist/">http://www.phone.net/home/mwm/hotlist/.</A></P>
-
-    <P>For Web integration, PHP is an excellent interface. It is at <A
-    href="http://www.php.net">http://www.php.net</A>.</P>
-
-    <P>For complex cases, many use the Perl interface and CGI.pm.</P>
-
-    <H4><A name="2.3">2.3</A>) Does PostgreSQL have a graphical user
-    interface? A report generator? An embedded query language
-    interface?</H4>
-
-    <P>We have a nice graphical user interface called <I>pgaccess</I>,
-    which is shipped as part of the distribution. <I>pgaccess</I> also
-    has a report generator. The Web page is <A href=
-    "http://www.flex.ro/pgaccess">http://www.flex.ro/pgaccess</A></P>
-
-    <P>We also include <I>ecpg</I>, which is an embedded SQL query
-    language interface for C.</P>
-
-    <H4><A name="2.4">2.4</A>) What languages are available to
-    communicate with PostgreSQL?</H4>
-
-    <P>We have:</P>
-
-    <UL>
-      <LI>C (libpq)</LI>
-
-      <LI>C++ (libpq++)</LI>
-
-      <LI>Embedded C (ecpg)</LI>
-
-      <LI>Java (jdbc)</LI>
-
-      <LI>Perl (perl5)</LI>
-
-      <LI>ODBC (odbc)</LI>
-
-      <LI>Python (PyGreSQL)</LI>
-
-      <LI>TCL (libpgtcl)</LI>
-
-      <LI>C Easy API (libpgeasy)</LI>
-
-      <LI>Embedded <SMALL>HTML</SMALL> (<A href=
-      "http://www.php.net">PHP from http://www.php.net</A>)</LI>
-    </UL>
-    <HR>
-
-    <H2 align="center">Administrative Questions</H2>
-
-    <H4><A name="3.1">3.1</A>) How do I install PostgreSQL somewhere
-    other than <I>/usr/local/pgsql</I>?</H4>
-
-    <P>Specify the <I>--prefix</I> option when running
-    <I>configure</I>.</P>
-
-    <H4><A name="3.2">3.2</A>) When I start <I>postmaster</I>, I get a
-    <I>Bad System Call</I> or core dumped message. Why?</H4>
-
-    <P>It could be a variety of problems, but first check to see that
-    you have System V extensions installed in your kernel. PostgreSQL
-    requires kernel support for shared memory and semaphores.</P>
-
-    <H4><A name="3.3">3.3</A>) When I try to start <I>postmaster</I>, I
-    get <I>IpcMemoryCreate</I> errors. Why?</H4>
-
-    <P>You either do not have shared memory configured properly in your
-    kernel or you need to enlarge the shared memory available in the
-    kernel. The exact amount you need depends on your architecture and
-    how many buffers and backend processes you configure for
-    <I>postmaster</I>. For most systems, with default numbers of
-    buffers and processes, you need a minimum of ~1 MB. See the <A
-    href=
-    "http://www.postgresql.org/idocs/index.php?kernel-resources.html">PostgreSQL
-    Administrator's Guide</A> for more detailed information about
-    shared memory and semaphores.</P>
-
-    <H4><A name="3.4">3.4</A>) When I try to start <I>postmaster</I>, I
-    get <I>IpcSemaphoreCreate</I> errors. Why?</H4>
-
-    <P>If the error message is <I>IpcSemaphoreCreate: semget failed (No
-    space left on device)</I> then your kernel is not configured with
-    enough semaphores. Postgres needs one semaphore per potential
-    backend process. A temporary solution is to start <I>postmaster</I>
-    with a smaller limit on the number of backend processes. Use
-    <I>-N</I> with a parameter less than the default of 32. A more
-    permanent solution is to increase your kernel's
-    <SMALL>SEMMNS</SMALL> and <SMALL>SEMMNI</SMALL> parameters.</P>
-
-    <P>Inoperative semaphores can also cause crashes during heavy
-    database access.</P>
-
-    <P>If the error message is something else, you might not have
-    semaphore support configured in your kernel at all. See the
-    PostgreSQL Administrator's Guide for more detailed information
-    about shared memory and semaphores.</P>
-
-    <H4><A name="3.5">3.5</A>) How do I control connections from other
-    hosts?</H4>
-
-    <P>By default, PostgreSQL only allows connections from the local
-    machine using Unix domain sockets. Other machines will not be able
-    to connect unless you add the <I>-i</I> flag to <I>postmaster</I>,
-    <B>and</B> enable host-based authentication by modifying the file
-    <I>$PGDATA/pg_hba.conf</I> accordingly. This will allow TCP/IP
-    connections.</P>
-
-    <H4><A name="3.6">3.6</A>) How do I tune the database engine for
-    better performance?</H4>
-
-    <P>Certainly, indexes can speed up queries. The
-    <SMALL>EXPLAIN</SMALL> command allows you to see how PostgreSQL is
-    interpreting your query, and which indexes are being used.</P>
-
-    <P>If you are doing many <SMALL>INSERTs</SMALL>, consider doing
-    them in a large batch using the <SMALL>COPY</SMALL> command. This
-    is much faster than individual <SMALL>INSERTS.</SMALL> Second,
-    statements not in a <SMALL>BEGIN WORK/COMMIT</SMALL> transaction
-    block are considered to be in their own transaction. Consider
-    performing several statements in a single transaction block. This
-    reduces the transaction overhead. Also, consider dropping and
-    recreating indexes when making large data changes.</P>
-
-    <P>There are several tuning options. You can disable <I>fsync()</I>
-    by starting <I>postmaster</I> with a <I>-o -F</I> option. This will
-    prevent <I>fsync()</I>s from flushing to disk after every
-    transaction.</P>
-
-    <P>You can also use the <I>postmaster</I> <I>-B</I> option to
-    increase the number of shared memory buffers used by the backend
-    processes. If you make this parameter too high, the
-    <I>postmaster</I> may not start because you have exceeded your
-    kernel's limit on shared memory space. Each buffer is 8K and the
-    default is 64 buffers.</P>
-
-    <P>You can also use the backend <I>-S</I> option to increase the
-    maximum amount of memory used by the backend process for temporary
-    sorts. The <I>-S</I> value is measured in kilobytes, and the
-    default is 512 (i.e. 512K).</P>
-
-    <P>You can also use the <SMALL>CLUSTER</SMALL> command to group
-    data in tables to match an index. See the <SMALL>CLUSTER</SMALL>
-    manual page for more details.</P>
-
-    <H4><A name="3.7">3.7</A>) What debugging features are
-    available?</H4>
-
-    <P>PostgreSQL has several features that report status information
-    that can be valuable for debugging purposes.</P>
-
-    <P>First, by running <I>configure</I> with the --enable-cassert
-    option, many <I>assert()</I>s monitor the progress of the backend
-    and halt the program when something unexpected occurs.</P>
-
-    <P>Both <I>postmaster</I> and <I>postgres</I> have several debug
-    options available. First, whenever you start <I>postmaster</I>,
-    make sure you send the standard output and error to a log file,
-    like:</P>
-<PRE>
-    cd /usr/local/pgsql
-    ./bin/postmaster &gt;server.log 2&gt;&amp;1 &amp;
-</PRE>
-
-    <P>This will put a server.log file in the top-level PostgreSQL
-    directory. This file contains useful information about problems or
-    errors encountered by the server. <I>Postmaster</I> has a <I>-d</I>
-    option that allows even more detailed information to be reported.
-    The <I>-d</I> option takes a number that specifies the debug level.
-    Be warned that high debug level values generate large log
-    files.</P>
-
-    <P>If <I>postmaster</I> is not running, you can actually run the
-    <I>postgres</I> backend from the command line, and type your
-    <SMALL>SQL</SMALL> statement directly. This is recommended
-    <B>only</B> for debugging purposes. Note that a newline terminates
-    the query, not a semicolon. If you have compiled with debugging
-    symbols, you can use a debugger to see what is happening. Because
-    the backend was not started from <I>postmaster</I>, it is not
-    running in an identical environment and locking/backend interaction
-    problems may not be duplicated.</P>
-
-    <P>If <I>postmaster</I> is running, start <I>psql</I> in one
-    window, then find the <SMALL>PID</SMALL> of the <I>postgres</I>
-    process used by <I>psql</I>. Use a debugger to attach to the
-    <I>postgres</I> <SMALL>PID.</SMALL> You can set breakpoints in the
-    debugger and issue queries from <I>psql</I>. If you are debugging
-    <I>postgres</I> startup, you can set PGOPTIONS="-W n", then start
-    <I>psql</I>. This will cause startup to delay for <I>n</I> seconds
-    so you can attach to the process with the debugger, set any
-    breakpoints, and continue through the startup sequence.</P>
-
-    <P>The <I>postgres</I> program has <I>-s, -A</I>, and <I>-t</I>
-    options that can be very useful for debugging and performance
-    measurements.</P>
-
-    <P>You can also compile with profiling to see what functions are
-    taking execution time. The backend profile files will be deposited
-    in the <I>pgsql/data/base/dbname</I> directory. The client profile
-    file will be put in the client's current directory. Linux requires
-    a compile with <I>-DLINUX_PROFILE</I> for proper profiling.</P>
-
-    <H4><A name="3.8">3.8</A>) Why do I get <I>"Sorry, too many
-    clients"</I> when trying to connect?</H4>
-
-    <P>You need to increase <I>postmaster</I>'s limit on how many
-    concurrent backend processes it can start.</P>
-
-    <P>The default limit is 32 processes. You can increase it by
-    restarting <I>postmaster</I> with a suitable <I>-N</I> value or
-    modifying <I>postgresql.conf</I>.</P>
-
-    <P>Note that if you make <I>-N</I> larger than 32, you must also
-    increase <I>-B</I> beyond its default of 64; <I>-B</I> must be at
-    least twice <I>-N</I>, and probably should be more than that for
-    best performance. For large numbers of backend processes, you are
-    also likely to find that you need to increase various Unix kernel
-    configuration parameters. Things to check include the maximum size
-    of shared memory blocks, <SMALL>SHMMAX;</SMALL> the maximum number
-    of semaphores, <SMALL>SEMMNS</SMALL> and <SMALL>SEMMNI;</SMALL> the
-    maximum number of processes, <SMALL>NPROC;</SMALL> the maximum
-    number of processes per user, <SMALL>MAXUPRC;</SMALL> and the
-    maximum number of open files, <SMALL>NFILE</SMALL> and
-    <SMALL>NINODE.</SMALL> The reason that PostgreSQL has a limit on
-    the number of allowed backend processes is so your system won't run
-    out of resources.</P>
-
-    <P>In PostgreSQL versions prior to 6.5, the maximum number of
-    backends was 64, and changing it required a rebuild after altering
-    the MaxBackendId constant in
-    <I>include/storage/sinvaladt.h</I>.</P>
-
-    <H4><A name="3.9">3.9</A>) What are the <I>pg_sorttempNNN.NN</I>
-    files in my database directory?</H4>
-
-    <P>They are temporary files generated by the query executor. For
-    example, if a sort needs to be done to satisfy an <SMALL>ORDER
-    BY,</SMALL> and the sort requires more space than the backend's
-    <I>-S</I> parameter allows, then temporary files are created to
-    hold the extra data.</P>
-
-    <P>The temporary files should be deleted automatically, but might
-    not if a backend crashes during a sort. If you have no backends
-    running at the time, it is safe to delete the pg_tempNNN.NN
-    files.</P>
-    <HR>
-
-    <H2 align="center">Operational Questions</H2>
-
-    <H4><A name="4.1">4.1</A>) What is the difference between binary
-    cursors and normal cursors?</H4>
-
-    <P>See the <SMALL>DECLARE</SMALL> manual page for a
-    description.</P>
-
-    <H4><A name="4.2">4.2</A>) How do I <SMALL>SELECT</SMALL> only the
-    first few rows of a query?</H4>
-
-    <P>See the <SMALL>FETCH</SMALL> manual page, or use
-    <SMALL>SELECT</SMALL> ... <SMALL>LIMIT</SMALL>....</P>
-
-    <P>The entire query may have to be evaluated, even if you only want
-    the first few rows. Consider a query that has an <SMALL>ORDER
-    BY.</SMALL> If there is an index that matches the <SMALL>ORDER
-    BY</SMALL>, PostgreSQL may be able to evaluate only the first few
-    records requested, or the entire query may have to be evaluated
-    until the desired rows have been generated.</P>
-
-    <H4><A name="4.3">4.3</A>) How do I get a list of tables or other
-    things I can see in <I>psql</I>?</H4>
-
-    <P>You can read the source code for <I>psql</I> in file
-    <I>pgsql/src/bin/psql/describe.c</I>. It contains
-    <SMALL>SQL</SMALL> commands that generate the output for psql's
-    backslash commands. You can also start <I>psql</I> with the
-    <I>-E</I> option so it will print out the queries it uses to
-    execute the commands you give.</P>
-
-    <H4><A name="4.4">4.4</A>) How do you remove a column from a
-    table?</H4>
-
-    <P>We do not support <SMALL>ALTER TABLE DROP COLUMN,</SMALL> but do
-    this:</P>
-<PRE>
-    BEGIN;
-    LOCK TABLE old_table;
-    SELECT ...  -- select all columns but the one you want to remove
-    INTO TABLE new_table
-    FROM old_table;
-    DROP TABLE old_table;
-    ALTER TABLE new_table RENAME TO old_table;
-    COMMIT;
-</PRE>
-
-    <H4><A name="4.5">4.5</A>) What is the maximum size for a row, a
-    table, and a database?</H4>
-
-    <P>These are the limits:</P>
-<PRE>
-    Maximum size for a database?             unlimited (500 GB databases exist)
-    Maximum size for a table?                16 TB
-    Maximum size for a row?                  unlimited in 7.1 and later
-    Maximum size for a field?                1 GB in 7.1 and later
-    Maximum number of rows in a table?       unlimited
-    Maximum number of columns in a table?    250-1600 depending on column types
-    Maximum number of indexes on a table?    unlimited
-</PRE>
-    Of course, these are not actually unlimited, but limited to
-    available disk space and memory/swap space. Performance may suffer
-    when these values get unusually large. 
-
-    <P>The maximum table size of 16 TB does not require large file
-    support from the operating system. Large tables are stored as
-    multiple 1 GB files so file system size limits are not
-    important.</P>
-
-    <P>The maximum table size and maximum number of columns can be
-    increased if the default block size is increased to 32k.</P>
-
-    <H4><A name="4.6">4.6</A>) How much database disk space is required
-    to store data from a typical text file?</H4>
-
-    <P>A PostgreSQL database may require up to five times the disk
-    space to store data from a text file.</P>
-
-    <P>As an example, consider a file of 100,000 lines with an integer
-    and text description on each line. Suppose the text string
-    avergages twenty bytes in length. The flat file would be 2.8 MB.
-    The size of the PostgreSQL database file containing this data can
-    be estimated as 6.4 MB:</P>
-<PRE>
-    36 bytes: each row header (approximate)
-    24 bytes: one int field and one text filed
-   + 4 bytes: pointer on page to tuple
-   ----------------------------------------
-    64 bytes per row
-
-   The data page size in PostgreSQL is 8192 bytes (8 KB), so:
-
-   8192 bytes per page
-   -------------------   =  128 rows per database page (rounded down)
-     64 bytes per row
-
-   100000 data rows
-   --------------------  =  782 database pages (rounded up)
-      128 rows per page
-
-782 database pages * 8192 bytes per page  =  6,406,144 bytes (6.4 MB)
-</PRE>
-
-    <P>Indexes do not require as much overhead, but do contain the data
-    that is being indexed, so they can be large also.</P>
-
-    <H4><A name="4.7">4.7</A>) How do I find out what tables, indexes,
-    databases, and users are defined?</H4>
-
-    <P><I>psql</I> has a variety of backslash commands to show such
-    information. Use \? to see them. There are also system tables
-    beginning with <I>pg_</I> that describe these too. Also, <I>psql
-    -l</I> will list all databases.</P>
-
-    <P>Also try the file <I>pgsql/src/tutorial/syscat.source</I>. It
-    illustrates many of the <SMALL>SELECT</SMALL>s needed to get
-    information from the database system tables.</P>
-
-    <H4><A name="4.8">4.8</A>) My queries are slow or don't make use of
-    the indexes. Why?</H4>
-    Indexes are not automatically used by every query. Indexes are only
-    used if the table is larger than a minimum size, and the query
-    selects only a small percentage of the rows in the table. This is
-    because the random disk access caused by an index scan is sometimes
-    slower than a straight read through the table, or sequential scan. 
-
-    <P>To determine if an index should be used, PostgreSQL must have
-    statistics about the table. These statistics are collected using
-    <SMALL>VACUUM ANALYZE</SMALL>, or simply <SMALL>ANALYZE</SMALL>.
-    Using statistics, the optimizer knows how many rows are in the
-    table, and can better determine if indexes should be used.
-    Statistics are also valuable in determining optimal join order and
-    join methods. Statistics collection should be performed
-    periodically as the contents of the table change.</P>
-
-    <P>Indexes are normally not used for <SMALL>ORDER BY</SMALL> or to
-    perform joins. A sequential scan followed by an explicit sort is
-    usually faster than an index scan of a large table.</P>
-    However, <SMALL>LIMIT</SMALL> combined with <SMALL>ORDER BY</SMALL>
-    often will use an index because only a small portion of the table
-    is returned. 
-
-    <P>When using wild-card operators such as <SMALL>LIKE</SMALL> or
-    <I>~</I>, indexes can only be used if the beginning of the search
-    is anchored to the start of the string. Therefore, to use indexes,
-    <SMALL>LIKE</SMALL> patterns must not start with <I>%</I>, and
-    <I>~</I>(regular expression) patterns must start with <I>^</I>.</P>
-
-    <H4><A name="4.9">4.9</A>) How do I see how the query optimizer is
-    evaluating my query?</H4>
-
-    <P>See the <SMALL>EXPLAIN</SMALL> manual page.</P>
-
-    <H4><A name="4.10">4.10</A>) What is an R-tree index?</H4>
-
-    <P>An R-tree index is used for indexing spatial data. A hash index
-    can't handle range searches. A B-tree index only handles range
-    searches in a single dimension. R-trees can handle
-    multi-dimensional data. For example, if an R-tree index can be
-    built on an attribute of type <I>point</I>, the system can more
-    efficiently answer queries such as "select all points within a
-    bounding rectangle."</P>
-
-    <P>The canonical paper that describes the original R-tree design
-    is:</P>
-
-    <P>Guttman, A. "R-trees: A Dynamic Index Structure for Spatial
-    Searching." Proceedings of the 1984 ACM SIGMOD Int'l Conf on Mgmt
-    of Data, 45-57.</P>
-
-    <P>You can also find this paper in Stonebraker's "Readings in
-    Database Systems".</P>
-
-    <P>Built-in R-trees can handle polygons and boxes. In theory,
-    R-trees can be extended to handle higher number of dimensions. In
-    practice, extending R-trees requires a bit of work and we don't
-    currently have any documentation on how to do it.</P>
-
-    <H4><A name="4.11">4.11</A>) What is the Genetic Query
-    Optimizer?</H4>
-
-    <P>The <SMALL>GEQO</SMALL> module speeds query optimization when
-    joining many tables by means of a Genetic Algorithm (GA). It allows
-    the handling of large join queries through nonexhaustive
-    search.</P>
-
-    <H4><A name="4.12">4.12</A>) How do I perform regular expression
-    searches and case-insensitive regular expression searches? How do I
-    use an index for case-insensitive searches?</H4>
-
-    <P>The <I>~</I> operator does regular expression matching, and
-    <I>~*</I> does case-insensitive regular expression matching. The
-    case-insensitive variant of <SMALL>LIKE</SMALL> is called
-    <SMALL>ILIKE</SMALL> in PostgreSQL 7.1 and later.</P>
-
-    <P>Case-insensitive equality comparisons are normally expressed
-    as:</P>
-<PRE>
-    SELECT *
-    FROM tab
-    WHERE lower(col) = 'abc'
-   
-</PRE>
-    This will not use an standard index. However, if you create a
-    functional index, it will be used: 
-<PRE>
-    CREATE INDEX tabindex on tab (lower(col));
-   
-</PRE>
-
-    <H4><A name="4.13">4.13</A>) In a query, how do I detect if a field
-    is <SMALL>NULL</SMALL>?</H4>
-
-    <P>You test the column with <SMALL>IS NULL</SMALL> and <SMALL>IS
-    NOT NULL</SMALL>.</P>
-
-    <H4><A name="4.14">4.14</A>) What is the difference between the
-    various character types?</H4>
-<PRE>
-Type            Internal Name   Notes
---------------------------------------------------
-"char"          char            1 character
-CHAR(#)         bpchar          blank padded to the specified fixed length
-VARCHAR(#)      varchar         size specifies maximum length, no padding
-TEXT            text            no specific upper limit on length
-BYTEA           bytea           variable-length byte array (null-byte safe)
-</PRE>
-
-    <P>You will see the internal name when examining system catalogs
-    and in some error messages.</P>
-
-    <P>The last four types above are "varlena" types (i.e., the first
-    four bytes on disk are the length, followed by the data). Thus the
-    actual space used is slightly greater than the declared size.
-    However, these data types are also subject to compression or being
-    stored out-of-line by <SMALL>TOAST</SMALL>, so the space on disk
-    might also be less than expected.</P>
-
-    <P><SMALL>CHAR()</SMALL> is best when storing strings that are
-    usually the same length. <SMALL>VARCHAR()</SMALL> is best when
-    storing variable-length strings but it limits how long a string can
-    be. <SMALL>TEXT</SMALL> is for strings of unlimited length, maximum
-    1 gigabyte. <SMALL>BYTEA</SMALL> is for storing binary data,
-    particularly values that include <SMALL>NULL</SMALL> bytes.</P>
-
-    <H4><A name="4.15.1">4.15.1</A>) How do I create a
-    serial/auto-incrementing field?</H4>
-
-    <P>PostgreSQL supports a <SMALL>SERIAL</SMALL> data type. It
-    auto-creates a sequence and index on the column. For example,
-    this:</P>
-<PRE>
-    CREATE TABLE person ( 
-        id   SERIAL, 
-        name TEXT 
-    );
-</PRE>
-    is automatically translated into this: 
-<PRE>
-    CREATE SEQUENCE person_id_seq;
-    CREATE TABLE person ( 
-        id   INT4 NOT NULL DEFAULT nextval('person_id_seq'),
-        name TEXT 
-    );
-    CREATE UNIQUE INDEX person_id_key ON person ( id );
-</PRE>
-    See the <I>create_sequence</I> manual page for more information
-    about sequences. You can also use each row's <I>OID</I> field as a
-    unique value. However, if you need to dump and reload the database,
-    you need to use <I>pg_dump</I>'s <I>-o</I> option or <SMALL>COPY
-    WITH OIDS</SMALL> option to preserve the <SMALL>OID</SMALL>s. 
-
-    <H4><A name="4.15.2">4.15.2</A>) How do I get the value of a
-    <SMALL>SERIAL</SMALL> insert?</H4>
-
-    <P>One approach is to retrieve the next <SMALL>SERIAL</SMALL> value
-    from the sequence object with the <I>nextval()</I> function
-    <I>before</I> inserting and then insert it explicitly. Using the
-    example table in <A href="#4.15.1">4.15.1</A>, that might look like
-    this in Perl:</P>
-<PRE>
-    new_id = output of "SELECT nextval('person_id_seq')"
-    INSERT INTO person (id, name) VALUES (new_id, 'Blaise Pascal');
-</PRE>
-    You would then also have the new value stored in
-    <CODE>new_id</CODE> for use in other queries (e.g., as a foreign
-    key to the <CODE>person</CODE> table). Note that the name of the
-    automatically created <SMALL>SEQUENCE</SMALL> object will be named
-    &lt;<I>table</I>&gt;_&lt;<I>serialcolumn</I>&gt;_<I>seq</I>, where
-    <I>table</I> and <I>serialcolumn</I> are the names of your table
-    and your <SMALL>SERIAL</SMALL> column, respectively. 
-
-    <P>Alternatively, you could retrieve the assigned
-    <SMALL>SERIAL</SMALL> value with the <I>currval</I>() function
-    <I>after</I> it was inserted by default, e.g.,</P>
-<PRE>
-    INSERT INTO person (name) VALUES ('Blaise Pascal');
-    new_id = output of "SELECT currval('person_id_seq')";
-</PRE>
-    Finally, you could use the <A href="#4.16"><SMALL>OID</SMALL></A>
-    returned from the <SMALL>INSERT</SMALL> statement to look up the
-    default value, though this is probably the least portable approach.
-    In Perl, using DBI with Edmund Mergl's DBD::Pg module, the oid
-    value is made available via <I>$sth-&gt;{pg_oid_status}</I> after
-    <I>$sth-&gt;execute()</I>. 
-
-    <H4><A name="4.15.3">4.15.3</A>) Don't <I>currval()</I> and
-    <I>nextval()</I> lead to a race condition with other users?</H4>
-
-    <P>No. Currval() returns the current value assigned by your
-    backend, not by all users.</P>
-
-    <H4><A name="4.15.4">4.15.4</A>) Why aren't my sequence numbers
-    reused on transaction abort? Why are there gaps in the numbering of
-    my sequence/SERIAL column?</H4>
-
-    <P>To improve concurrency, sequence values are given out to running
-    transactions as needed and are not locked until the transaction
-    completes. This causes gaps in numbering from aborted
-    transactions.</P>
-
-    <H4><A name="4.16">4.16</A>) What is an <SMALL>OID</SMALL>? What is
-    a <SMALL>TID</SMALL>?</H4>
-
-    <P><SMALL>OID</SMALL>s are PostgreSQL's answer to unique row ids.
-    Every row that is created in PostgreSQL gets a unique
-    <SMALL>OID</SMALL>. All <SMALL>OID</SMALL>s generated during
-    <I>initdb</I> are less than 16384 (from
-    <I>backend/access/transam.h</I>). All user-created
-    <SMALL>OID</SMALL>s are equal to or greater than this. By default,
-    all these <SMALL>OID</SMALL>s are unique not only within a table or
-    database, but unique within the entire PostgreSQL installation.</P>
-
-    <P>PostgreSQL uses <SMALL>OID</SMALL>s in its internal system
-    tables to link rows between tables. These <SMALL>OID</SMALL>s can
-    be used to identify specific user rows and used in joins. It is
-    recommended you use column type <SMALL>OID</SMALL> to store
-    <SMALL>OID</SMALL> values. You can create an index on the
-    <SMALL>OID</SMALL> field for faster access.</P>
-
-    <P>O<SMALL>ID</SMALL>s are assigned to all new rows from a central
-    area that is used by all databases. If you want to change the
-    <SMALL>OID</SMALL> to something else, or if you want to make a copy
-    of the table, with the original <SMALL>OID</SMALL>s, there is no
-    reason you can't do it:</P>
-<PRE>
-        CREATE TABLE new_table(old_oid oid, mycol int);
-        SELECT old_oid, mycol INTO new FROM old;
-        COPY new TO '/tmp/pgtable';
-        DELETE FROM new;
-        COPY new WITH OIDS FROM '/tmp/pgtable';
-<!--
-    CREATE TABLE new_table (mycol int);
-    INSERT INTO new_table (oid, mycol) SELECT oid, mycol FROM old_table;
--->
-</PRE>
-
-    <P>O<SMALL>ID</SMALL>s are stored as 4-byte integers, and will
-    overflow at 4 billion. No one has reported this ever happening, and
-    we plan to have the limit removed before anyone does.</P>
-
-    <P>T<SMALL>ID</SMALL>s are used to identify specific physical rows
-    with block and offset values. T<SMALL>ID</SMALL>s change after rows
-    are modified or reloaded. They are used by index entries to point
-    to physical rows.</P>
-
-    <H4><A name="4.17">4.17</A>) What is the meaning of some of the
-    terms used in PostgreSQL?</H4>
-
-    <P>Some of the source code and older documentation use terms that
-    have more common usage. Here are some:</P>
-
-    <UL>
-      <LI>table, relation, class</LI>
-
-      <LI>row, record, tuple</LI>
-
-      <LI>column, field, attribute</LI>
-
-      <LI>retrieve, select</LI>
-
-      <LI>replace, update</LI>
-
-      <LI>append, insert</LI>
-
-      <LI><SMALL>OID</SMALL>, serial value</LI>
-
-      <LI>portal, cursor</LI>
-
-      <LI>range variable, table name, table alias</LI>
-    </UL>
-
-    <P>A list of general database terms can be found at: <A href=
-    "http://www.comptechnews.com/~reaster/dbdesign.html">http://www.comptechnews.com/~reaster/dbdesign.html</A></P>
-
-    <H4><A name="4.18">4.18</A>) Why do I get the error <I>"ERROR:
-    Memory exhausted in AllocSetAlloc()"</I>?</H4>
-
-    <P>If you are running a version older than 7.1, an upgrade may fix
-    the problem. Also it is possible you have run out of virtual memory
-    on your system, or your kernel has a low limit for certain
-    resources. Try this before starting <I>postmaster</I>:</P>
-<PRE>
-    ulimit -d 262144
-    limit datasize 256m
-</PRE>
-    Depending on your shell, only one of these may succeed, but it will
-    set your process data segment limit much higher and perhaps allow
-    the query to complete. This command applies to the current process,
-    and all subprocesses created after the command is run. If you are
-    having a problem with the <SMALL>SQL</SMALL> client because the
-    backend is returning too much data, try it before starting the
-    client. 
-
-    <H4><A name="4.19">4.19</A>) How do I tell what PostgreSQL version
-    I am running?</H4>
-
-    <P>From <I>psql</I>, type <CODE>select version();</CODE></P>
-
-    <H4><A name="4.20">4.20</A>) Why does my large-object operations
-    get <I>"invalid large obj descriptor"</I>?</H4>
-
-    <P>You need to put <CODE>BEGIN WORK</CODE> and <CODE>COMMIT</CODE>
-    around any use of a large object handle, that is, surrounding
-    <CODE>lo_open</CODE> ... <CODE>lo_close.</CODE></P>
-
-    <P>Currently PostgreSQL enforces the rule by closing large object
-    handles at transaction commit. So the first attempt to do anything
-    with the handle will draw <I>invalid large obj descriptor</I>. So
-    code that used to work (at least most of the time) will now
-    generate that error message if you fail to use a transaction.</P>
-
-    <P>If you are using a client interface like <SMALL>ODBC</SMALL> you
-    may need to set <CODE>auto-commit off.</CODE></P>
-
-    <H4><A name="4.21">4.21</A>) How do I create a column that will
-    default to the current time?</H4>
-
-    <P>Use <I>CURRENT_TIMESTAMP</I>:</P>
-<PRE>
-<CODE>CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
-</CODE>
-</PRE>
-
-    <H4><A name="4.22">4.22</A>) Why are my subqueries using
-    <CODE><SMALL>IN</SMALL></CODE> so slow?</H4>
-
-    <P>Currently, we join subqueries to outer queries by sequentially
-    scanning the result of the subquery for each row of the outer
-    query. A workaround is to replace <CODE>IN</CODE> with
-    <CODE>EXISTS</CODE>:</P>
-<PRE>
-<CODE>SELECT *
-    FROM tab
-    WHERE col1 IN (SELECT col2 FROM TAB2)
-</CODE>
-</PRE>
-    to: 
-<PRE>
-<CODE>SELECT *
-    FROM tab
-    WHERE EXISTS (SELECT col2 FROM TAB2 WHERE col1 = col2)
-</CODE>
-</PRE>
-    We hope to fix this limitation in a future release. 
-
-    <H4><A name="4.23">4.23</A>) How do I perform an outer join?</H4>
-
-    <P>PostgreSQL 7.1 and later supports outer joins using the SQL
-    standard syntax. Here are two examples:</P>
-<PRE>
-    SELECT *
-    FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
-</PRE>
-    or 
-<PRE>
-    SELECT *
-    FROM t1 LEFT OUTER JOIN t2 USING (col);
-</PRE>
-
-    <P>These identical queries join t1.col to t2.col, and also return
-    any unjoined rows in t1 (those with no match in t2). A
-    <SMALL>RIGHT</SMALL> join would add unjoined rows of t2. A
-    <SMALL>FULL</SMALL> join would return the matched rows plus all
-    unjoined rows from t1 and t2. The word <SMALL>OUTER</SMALL> is
-    optional and is assumed in <SMALL>LEFT</SMALL>,
-    <SMALL>RIGHT</SMALL>, and <SMALL>FULL</SMALL> joins. Ordinary joins
-    are called <SMALL>INNER</SMALL> joins.</P>
-
-    <P>In previous releases, outer joins can be simulated using
-    <SMALL>UNION</SMALL> and <SMALL>NOT IN</SMALL>. For example, when
-    joining <I>tab1</I> and <I>tab2</I>, the following query does an
-    <I>outer</I> join of the two tables:<BR>
-    <BR>
-    </P>
-<PRE>
-    SELECT tab1.col1, tab2.col2
-    FROM tab1, tab2
-    WHERE tab1.col1 = tab2.col1
-    UNION ALL
-    SELECT tab1.col1, NULL
-    FROM tab1
-    WHERE tab1.col1 NOT IN (SELECT tab2.col1 FROM tab2)
-    ORDER BY col1
-</PRE>
-
-    <H4><A name="4.24">4.24</A>) How do I perform queries using
-    multiple databases?</H4>
-
-    <P>There is no way to query any database except the current one.
-    Because PostgreSQL loads database-specific system catalogs, it is
-    uncertain how a cross-database query should even behave.</P>
-
-    <P>Of course, a client can make simultaneous connections to
-    different databases and merge the information that way.</P>
-
-    <H4><A name="4.25">4.25</A>) How do I return multiple rows or
-    columns from a function?</H4>
-
-    <P>You can return result sets from PL/pgSQL functions using
-    <I>refcursors</I>. See <A href=
-    "http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html">
-    http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html,</A>
-    section 23.7.3.3.</P>
-
-    <H4><A name="4.26">4.26</A>) Why can't I reliably create/drop
-    temporary tables in PL/PgSQL functions?</H4>
-    PL/PgSQL caches function contents, and an unfortunate side effect
-    is that if a PL/PgSQL function accesses a temporary table, and that
-    table is later dropped and recreated, and the function called
-    again, the function will fail because the cached function contents
-    still point to the old temporary table. The solution is to use
-    <SMALL>EXECUTE</SMALL> for temporary table access in PL/PgSQL. This
-    will cause the query to be reparsed every time. 
-
-    <HR>
-
-    <H2 align="center">Extending PostgreSQL</H2>
-
-    <H4><A name="5.1">5.1</A>) I wrote a user-defined function. When I
-    run it in <I>psql</I>, why does it dump core?</H4>
-
-    <P>The problem could be a number of things. Try testing your
-    user-defined function in a stand-alone test program first.</P>
-
-    <H4><A name="5.2">5.2</A>) How can I contribute some nifty new
-    types and functions to PostgreSQL?</H4>
-
-    <P>Send your extensions to the <I>pgsql-hackers</I> mailing list,
-    and they will eventually end up in the <I>contrib/</I>
-    subdirectory.</P>
-
-    <H4><A name="5.3">5.3</A>) How do I write a C function to return a
-    tuple?</H4>
-
-    <P>This requires wizardry so extreme that the authors have never
-    tried it, though in principle it can be done.</P>
-
-    <H4><A name="5.4">5.4</A>) I have changed a source file. Why does
-    the recompile not see the change?</H4>
-
-    <P>The <I>Makefiles</I> do not have the proper dependencies for
-    include files. You have to do a <I>make clean</I> and then another
-    <I>make</I>. If you are using <SMALL>GCC</SMALL> you can use the
-    <I>--enable-depend</I> option of <I>configure</I> to have the
-    compiler compute the dependencies automatically.</P>
-  </BODY>
-</HTML>
-
diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html
deleted file mode 100644
index 3116d1169f2..00000000000
--- a/doc/src/FAQ/FAQ_DEV.html
+++ /dev/null
@@ -1,840 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
-
-<HTML>
-  <HEAD>
-    <META name="generator" content="HTML Tidy, see www.w3.org">
-
-    <TITLE>PostgreSQL Developers FAQ</TITLE>
-  </HEAD>
-
-  <BODY bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000"
-  alink="#0000FF">
-    <H1>Developer's Frequently Asked Questions (FAQ) for
-    PostgreSQL</H1>
-
-    <P>Last updated: Wed Apr 17 01:12:20 EDT 2002</P>
-
-    <P>Current maintainer: Bruce Momjian (<A href=
-    "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
-    </P>
-
-    <P>The most recent version of this document can be viewed at the
-    postgreSQL Web site, <A href=
-    "http://www.PostgreSQL.org">http://www.PostgreSQL.org</A>.<BR>
-    </P>
-    <HR>
-    <BR>
-     
-
-    <CENTER>
-      <H2>General Questions</H2>
-    </CENTER>
-     <A href="#1.1">1.1</A>) How do I get involved in PostgreSQL
-    development?<BR>
-     <A href="#1.2">1.2</A>) How do I add a feature or fix a bug?<BR>
-     <A href="#1.3">1.3</A>) How do I download/update the current source
-    tree?<BR>
-     <A href="#1.4">1.4</A>) How do I test my changes?<BR>
-    <A href="#1.5">1.5</A>) What tools are available for developers?<BR>
-     <A href="#1.6">1.6</A>) What books are good for developers?<BR>
-     <A href="#1.7">1.7</A>) What is configure all about?<BR>
-     <A href="#1.8">1.8</A>) How do I add a new port?<BR>
-     <A href="#1.9">1.9</A>) Why don't we use threads in the backend?<BR>
-     <A href="#1.10">1.10</A>) How are RPM's packaged?<BR>
-     <A href="#1.11">1.11</A>) How are CVS branches handled?<BR>
-     <A href="#1.12">1.12</A>) Where can I get a copy of the SQL
-     standards?<BR>
-
-    <CENTER>
-      <H2>Technical Questions</H2>
-    </CENTER>
-     <A href="#2.1">2.1</A>) How do I efficiently access information in
-    tables from the backend code?<BR>
-     <A href="#2.2">2.2</A>) Why are table, column, type, function, view
-    names sometimes referenced as <I>Name</I> or <I>NameData,</I> and
-    sometimes as <I>char *?</I><BR>
-     <A href="#2.3">2.3</A>) Why do we use <I>Node</I> and <I>List</I> to
-    make data structures?<BR>
-     <A href="#2.4">2.4</A>) I just added a field to a structure. What else
-    should I do?<BR>
-     <A href="#2.5">2.5</A>) Why do we use <I>palloc</I>() and
-    <I>pfree</I>() to allocate memory?<BR>
-     <A href="#2.6">2.6</A>) What is elog()?<BR>
-     <A href="#2.7">2.7</A>) What is CommandCounterIncrement()?<BR>
-     <BR>
-     
-    <HR>
-
-    <CENTER>
-      <H2>General Questions</H2>
-    </CENTER>
-
-    <H3><A name="1.1">1.1</A>) How go I get involved in PostgreSQL
-    development?</H3>
-
-    <P>This was written by Lamar Owen:</P>
-
-    <P>2001-06-22</P>
-
-    <B>What open source development process is used by the PostgreSQL
-    team?</B>
-
-    <P>Read HACKERS for six months (or a full release cycle, whichever
-    is longer). Really. HACKERS _is_the process. The process is not
-    well documented (AFAIK -- it may be somewhere that I am not aware
-    of) -- and it changes continually.</P>
-
-    <B>What development environment (OS, system, compilers, etc) is
-    required to develop code?</B>
-
-    <P><A href="http://developers.postgresql.org">Developers Corner</A> on the
-    website has links to this information. The distribution tarball
-    itself includes all the extra tools and documents that go beyond a
-    good Unix-like development environment. In general, a modern unix
-    with a modern gcc, GNU make or equivalent, autoconf (of a
-    particular version), and good working knowledge of those tools are
-    required.</P>
-
-    <B>What areas need support?</B>
-
-    <P>The TODO list.</P>
-
-    <P>You've made the first step, by finding and subscribing to
-    HACKERS. Once you find an area to look at in the TODO, and have
-    read the documentation on the internals, etc, then you check out a
-    current CVS,write what you are going to write (keeping your CVS
-    checkout up to date in the process), and make up a patch (as a
-    context diff only) and send to the PATCHES list, prefereably.</P>
-
-    <P>Discussion on the patch typically happens here. If the patch
-    adds a major feature, it would be a good idea to talk about it
-    first on the HACKERS list, in order to increase the chances of it
-    being accepted, as well as toavoid duplication of effort. Note that
-    experienced developers with a proven track record usually get the
-    big jobs -- for more than one reason. Also note that PostgreSQL is
-    highly portable -- nonportable code will likely be dismissed out of
-    hand.</P>
-
-    <P>Once your contributions get accepted, things move from there.
-    Typically, you would be added as a developer on the list on the
-    website when one of the other developers recommends it. Membership
-    on the steering committee is by invitation only, by the other
-    steering committee members, from what I have gathered watching
-    froma distance.</P>
-
-    <P>I make these statements from having watched the process for over
-    two years.</P>
-
-    <P>To see a good example of how one goes about this, search the
-    archives for the name 'Tom Lane' and see what his first post
-    consisted of, and where he took things. In particular, note that
-    this hasn't been _that_ long ago -- and his bugfixing and general
-    deep knowledge with this codebase is legendary. Take a few days to
-    read after him. And pay special attention to both the sheer
-    quantity as well as the painstaking quality of his work. Both are
-    in high demand.</P>
-
-    <H3><A name="1.2">1.2</A>) How do I add a feature or fix a bug?</H3>
-
-    <P>The source code is over 350,000 lines. Many fixes/features
-    are isolated to one specific area of the code. Others require
-    knowledge of much of the source. If you are confused about where to
-    start, ask the hackers list, and they will be glad to assess the
-    complexity and give pointers on where to start.</P>
-
-    <P>Another thing to keep in mind is that many fixes and features
-    can be added with surprisingly little code. I often start by adding
-    code, then looking at other areas in the code where similar things
-    are done, and by the time I am finished, the patch is quite small
-    and compact.</P>
-
-    <P>When adding code, keep in mind that it should use the existing
-    facilities in the source, for performance reasons and for
-    simplicity. Often a review of existing code doing similar things is
-    helpful.</P>
-
-    <P>The usual process for source additions is:
-    <UL>
-    <LI>Review the TODO list.</LI>
-    <LI>Discuss hackers the desirability of the fix/feature.</LI>
-    <LI>How should it behave in complex circumstances?</LI>
-    <LI>How should it be implemented?</LI>
-    <LI>Submit the patch to the patches list.</LI>
-    <LI>Answer email questions.</LI>
-    <LI>Wait for the patch to be applied.</LI>
-    </UL></P>
-    <H3><A name="1.3">1.3</A>) How do I download/update the current source
-    tree?</H3>
-
-    <P>There are several ways to obtain the source tree. Occasional
-    developers can just get the most recent source tree snapshot from
-    ftp.postgresql.org. For regular developers, you can use CVS. CVS
-    allows you to download the source tree, then occasionally update
-    your copy of the source tree with any new changes. Using CVS, you
-    don't have to download the entire source each time, only the
-    changed files. Anonymous CVS does not allows developers to update
-    the remote source tree, though privileged developers can do this.
-    There is a CVS FAQ on our web site that describes how to use remote
-    CVS. You can also use CVSup, which has similarly functionality, and
-    is available from ftp.postgresql.org.</P>
-
-    <P>To update the source tree, there are two ways. You can generate
-    a patch against your current source tree, perhaps using the
-    make_diff tools mentioned above, and send them to the patches list.
-    They will be reviewed, and applied in a timely manner. If the patch
-    is major, and we are in beta testing, the developers may wait for
-    the final release before applying your patches.</P>
-
-    <P>For hard-core developers, Marc(scrappy@postgresql.org) will give
-    you a Unix shell account on postgresql.org, so you can use CVS to
-    update the main source tree, or you can ftp your files into your
-    account, patch, and cvs install the changes directly into the
-    source tree.</P>
-
-    <H3><A name="1.4">1.4</A>) How do I test my changes?</H3>
-
-    <P>First, use <I>psql</I> to make sure it is working as you expect.
-    Then run <I>src/test/regress</I> and get the output of
-    <I>src/test/regress/checkresults</I> with and without your changes,
-    to see that your patch does not change the regression test in
-    unexpected ways. This practice has saved me many times. The
-    regression tests test the code in ways I would never do, and has
-    caught many bugs in my patches. By finding the problems now, you
-    save yourself a lot of debugging later when things are broken, and
-    you can't figure out when it happened.</P>
-
-    <H3><A name="1.5">1.5</A>) What tools are available for
-    developers?</H3>
-
-    <P>Aside from the User documentation mentioned in the regular FAQ,
-    there are several development tools available. First, all the files
-    in the <I>/tools</I> directory are designed for developers.</P>
-<PRE>
-    RELEASE_CHANGES changes we have to make for each release
-    SQL_keywords    standard SQL'92 keywords
-    backend         description/flowchart of the backend directories
-    ccsym           find standard defines made by your compiler
-    entab           converts tabs to spaces, used by pgindent
-    find_static     finds functions that could be made static
-    find_typedef    finds typedefs in the source code
-    find_badmacros  finds macros that use braces incorrectly
-    make_ctags      make vi 'tags' file in each directory
-    make_diff       make *.orig and diffs of source
-    make_etags      make emacs 'etags' files
-    make_keywords   make comparison of our keywords and SQL'92
-    make_mkid       make mkid ID files
-    mkldexport      create AIX exports file
-    pgindent        indents C source files
-    pgjindent       indents Java source files
-    pginclude       scripts for adding/removing include files
-    unused_oids     in pgsql/src/include/catalog
-</PRE>
-    Let me note some of these. If you point your browser at the
-    <I>file:/usr/local/src/pgsql/src/tools/backend/index.html</I>
-    directory, you will see few paragraphs describing the data flow,
-    the backend components in a flow chart, and a description of the
-    shared memory area. You can click on any flowchart box to see a
-    description. If you then click on the directory name, you will be
-    taken to the source directory, to browse the actual source code
-    behind it. We also have several README files in some source
-    directories to describe the function of the module. The browser
-    will display these when you enter the directory also. The
-    <I>tools/backend</I> directory is also contained on our web page
-    under the title <I>How PostgreSQL Processes a Query.</I> 
-
-    <P>Second, you really should have an editor that can handle tags,
-    so you can tag a function call to see the function definition, and
-    then tag inside that function to see an even lower-level function,
-    and then back out twice to return to the original function. Most
-    editors support this via <I>tags</I> or <I>etags</I> files.</P>
-
-    <P>Third, you need to get <I>id-utils</I> from:</P>
-<PRE>
-    <A href=
-"ftp://alpha.gnu.org/gnu/id-utils-3.2d.tar.gz">ftp://alpha.gnu.org/gnu/id-utils-3.2d.tar.gz</A>
-    <A href=
-"ftp://tug.org/gnu/id-utils-3.2d.tar.gz">ftp://tug.org/gnu/id-utils-3.2d.tar.gz</A>
-    <A href=
-"ftp://ftp.enst.fr/pub/gnu/gnits/id-utils-3.2d.tar.gz">ftp://ftp.enst.fr/pub/gnu/gnits/id-utils-3.2d.tar.gz</A>
-</PRE>
-    By running <I>tools/make_mkid</I>, an archive of source symbols can
-    be created that can be rapidly queried like <I>grep</I> or edited.
-    Others prefer <I>glimpse.</I> 
-
-    <P><I>make_diff</I> has tools to create patch diff files that can
-    be applied to the distribution. This produces context diffs, which
-    is our preferred format.</P>
-
-    <P>Our standard format is to indent each code level with one tab,
-    where each tab is four spaces. You will need to set your editor to
-    display tabs as four spaces:<BR>
-    </P>
-<PRE>
-    vi in ~/.exrc:
-            set tabstop=4
-            set sw=4
-    more:
-            more -x4
-    less:
-            less -x4
-    emacs:
-        M-x set-variable tab-width
-        or
-        ; Cmd to set tab stops &amp; indenting for working with PostgreSQL code
-             (c-add-style "pgsql"
-                      '("bsd"
-                                 (indent-tabs-mode . t)
-                                 (c-basic-offset   . 4)
-                                 (tab-width . 4)
-                                 (c-offsets-alist .
-                                            ((case-label . +))))
-                       t) ; t = set this mode on
-
-        and add this to your autoload list (modify file path in macro):
-
-        (setq auto-mode-alist
-              (cons '("\\`/usr/local/src/pgsql/.*\\.[chyl]\\'" . pgsql-c-mode)
-            auto-mode-alist))
-        or
-            /*
-             * Local variables:
-             *  tab-width: 4
-             *  c-indent-level: 4
-             *  c-basic-offset: 4
-             * End:
-             */
-</PRE>
-    <BR>
-     <I>pgindent</I> will the format code by specifying flags to your
-    operating system's utility <I>indent.</I>  This 
-    <A HREF="http://ezine.daemonnews.org/200112/single_coding_style.html">
-    article</A> describes the value of a constent coding style.
-
-    <P><I>pgindent</I> is run on all source files just before each beta
-    test period. It auto-formats all source files to make them
-    consistent. Comment blocks that need specific line breaks should be
-    formatted as <I>block comments,</I> where the comment starts as
-    <CODE>/*------</CODE>. These comments will not be reformatted in
-    any way.</P>
-
-    <P><I>pginclude</I> contains scripts used to add needed
-    <CODE>#include</CODE>'s to include files, and removed unneeded
-    <CODE>#include</CODE>'s.</P>
-
-    <P>When adding system types, you will need to assign oids to them.
-    There is also a script called <I>unused_oids</I> in
-    <I>pgsql/src/include/catalog</I> that shows the unused oids.</P>
-
-    <H3><A name="1.6">1.6</A>) What books are good for developers?</H3>
-
-    <P>I have four good books, <I>An Introduction to Database
-    Systems,</I> by C.J. Date, Addison, Wesley, <I>A Guide to the SQL
-    Standard,</I> by C.J. Date, et. al, Addison, Wesley,
-    <I>Fundamentals of Database Systems,</I> by Elmasri and Navathe,
-    and <I>Transaction Processing,</I> by Jim Gray, Morgan,
-    Kaufmann</P>
-
-    <P>There is also a database performance site, with a handbook
-    on-line written by Jim Gray at <A href=
-    "http://www.benchmarkresources.com">http://www.benchmarkresources.com.</A></P>
-
-    <H3><A name="1.7">1.7</A>) What is configure all about?</H3>
-
-    <P>The files <I>configure</I> and <I>configure.in</I> are part of
-    the GNU <I>autoconf</I> package. Configure allows us to test for
-    various capabilities of the OS, and to set variables that can then
-    be tested in C programs and Makefiles. Autoconf is installed on the
-    PostgreSQL main server. To add options to configure, edit
-    <I>configure.in,</I> and then run <I>autoconf</I> to generate
-    <I>configure.</I></P>
-
-    <P>When <I>configure</I> is run by the user, it tests various OS
-    capabilities, stores those in <I>config.status</I> and
-    <I>config.cache,</I> and modifies a list of <I>*.in</I> files. For
-    example, if there exists a <I>Makefile.in,</I> configure generates
-    a <I>Makefile</I> that contains substitutions for all @var@
-    parameters found by configure.</P>
-
-    <P>When you need to edit files, make sure you don't waste time
-    modifying files generated by <I>configure.</I> Edit the <I>*.in</I>
-    file, and re-run <I>configure</I> to recreate the needed file. If
-    you run <I>make distclean</I> from the top-level source directory,
-    all files derived by configure are removed, so you see only the
-    file contained in the source distribution.</P>
-
-    <H3><A name="1.8">1.8</A>) How do I add a new port?</H3>
-
-    <P>There are a variety of places that need to be modified to add a
-    new port. First, start in the <I>src/template</I> directory. Add an
-    appropriate entry for your OS. Also, use <I>src/config.guess</I> to
-    add your OS to <I>src/template/.similar.</I> You shouldn't match
-    the OS version exactly. The <I>configure</I> test will look for an
-    exact OS version number, and if not found, find a match without
-    version number. Edit <I>src/configure.in</I> to add your new OS.
-    (See configure item above.) You will need to run autoconf, or patch
-    <I>src/configure</I> too.</P>
-
-    <P>Then, check <I>src/include/port</I> and add your new OS file,
-    with appropriate values. Hopefully, there is already locking code
-    in <I>src/include/storage/s_lock.h</I> for your CPU. There is also
-    a <I>src/makefiles</I> directory for port-specific Makefile
-    handling. There is a <I>backend/port</I> directory if you need
-    special files for your OS.</P>
-
-    <H3><A name="1.9">1.9</A>) Why don't we use threads in the
-    backend?</H3>
-
-    <P>There are several reasons threads are not used:</P>
-
-    <UL>
-      <LI>Historically, threads were unsupported and buggy.</LI>
-
-      <LI>An error in one backend can corrupt other backends.</LI>
-
-      <LI>Speed improvements using threads are small compared to the
-      remaining backend startup time.</LI>
-
-      <LI>The backend code would be more complex.</LI>
-    </UL>
-
-    <H3><A name="1.10">1.10</A>) How are RPM's packaged?</H3>
-
-    <P>This was written by Lamar Owen:</P>
-
-    <P>2001-05-03</P>
-
-    <P>As to how the RPMs are built -- to answer that question sanely
-    requires me to know how much experience you have with the whole RPM
-    paradigm. 'How is the RPM built?' is a multifaceted question. The
-    obvious simple answer is that I maintain:</P>
-
-    <OL>
-      <LI>A set of patches to make certain portions of the source tree
-      'behave' in the different environment of the RPMset;</LI>
-
-      <LI>The initscript;</LI>
-
-      <LI>Any other ancilliary scripts and files;</LI>
-
-      <LI>A README.rpm-dist document that tries to adequately document
-      both the differences between the RPM build and the WHY of the
-      differences, as well as useful RPM environment operations (like,
-      using syslog, upgrading, getting postmaster to start at OS boot,
-      etc);</LI>
-
-      <LI>The spec file that throws it all together. This is not a
-      trivial undertaking in a package of this size.</LI>
-    </OL>
-
-    <P>I then download and build on as many different canonical
-    distributions as I can -- currently I am able to build on Red Hat
-    6.2, 7.0, and 7.1 on my personal hardware. Occasionally I receive
-    opportunity from certain commercial enterprises such as Great
-    Bridge and PostgreSQL, Inc. to build on other distributions.</P>
-
-    <P>I test the build by installing the resulting packages and
-    running the regression tests. Once the build passes these tests, I
-    upload to the postgresql.org ftp server and make a release
-    announcement. I am also responsible for maintaining the RPM
-    download area on the ftp site.</P>
-
-    <P>You'll notice I said 'canonical' distributions above. That
-    simply means that the machine is as stock 'out of the box' as
-    practical -- that is, everything (except select few programs) on
-    these boxen are installed by RPM; only official Red Hat released
-    RPMs are used (except in unusual circumstances involving software
-    that will not alter the build -- for example, installing a newer
-    non-RedHat version of the Dia diagramming package is OK --
-    installing Python 2.1 on the box that has Python 1.5.2 installed is
-    not, as that alters the PostgreSQL build). The RPM as uploaded is
-    built to as close to out-of-the-box pristine as is possible. Only
-    the standard released 'official to that release' compiler is used
-    -- and only the standard official kernel is used as well.</P>
-
-    <P>For a time I built on Mandrake for RedHat consumption -- no
-    more. Nonstandard RPM building systems are worse than useless.
-    Which is not to say that Mandrake is useless! By no means is
-    Mandrake useless -- unless you are building Red Hat RPMs -- and Red
-    Hat is useless if you're trying to build Mandrake or SuSE RPMs, for
-    that matter. But I would be foolish to use 'Lamar Owen's Super
-    Special RPM Blend Distro 0.1.2' to build for public consumption!
-    :-)</P>
-
-    <P>I _do_ attempt to make the _source_ RPM compatible with as many
-    distributions as possible -- however, since I have limited
-    resources (as a volunteer RPM maintainer) I am limited as to the
-    amount of testing said build will get on other distributions,
-    architectures, or systems.</P>
-
-    <P>And, while I understand people's desire to immediately upgrade
-    to the newest version, realize that I do this as a side interest --
-    I have a regular, full-time job as a broadcast
-    engineer/webmaster/sysadmin/Technical Director which occasionally
-    prevents me from making timely RPM releases. This happened during
-    the early part of the 7.1 beta cycle -- but I believe I was pretty
-    much on the ball for the Release Candidates and the final
-    release.</P>
-
-    <P>I am working towards a more open RPM distribution -- I would
-    dearly love to more fully document the process and put everything
-    into CVS -- once I figure out how I want to represent things such
-    as the spec file in a CVS form. It makes no sense to maintain a
-    changelog, for instance, in the spec file in CVS when CVS does a
-    better job of changelogs -- I will need to write a tool to generate
-    a real spec file from a CVS spec-source file that would add version
-    numbers, changelog entries, etc to the result before building the
-    RPM. IOW, I need to rethink the process -- and then go through the
-    motions of putting my long RPM history into CVS one version at a
-    time so that version history information isn't lost.</P>
-
-    <P>As to why all these files aren't part of the source tree, well,
-    unless there was a large cry for it to happen, I don't believe it
-    should. PostgreSQL is very platform-agnostic -- and I like that.
-    Including the RPM stuff as part of the Official Tarball (TM) would,
-    IMHO, slant that agnostic stance in a negative way. But maybe I'm
-    too sensitive to that. I'm not opposed to doing that if that is the
-    consensus of the core group -- and that would be a sneaky way to
-    get the stuff into CVS :-). But if the core group isn't thrilled
-    with the idea (and my instinct says they're not likely to be), I am
-    opposed to the idea -- not to keep the stuff to myself, but to not
-    hinder the platform-neutral stance. IMHO, of course.</P>
-
-    <P>Of course, there are many projects that DO include all the files
-    necessary to build RPMs from their Official Tarball (TM).</P>
-
-    <H3><A name="1.11">1.11</A>) How are CVS branches managed?</H3>
-
-    <P>This was written by Tom Lane:</P>
-
-    <P>2001-05-07</P>
-
-    <P>If you just do basic "cvs checkout", "cvs update", "cvs commit",
-    then you'll always be dealing with the HEAD version of the files in
-    CVS. That's what you want for development, but if you need to patch
-    past stable releases then you have to be able to access and update
-    the "branch" portions of our CVS repository. We normally fork off a
-    branch for a stable release just before starting the development
-    cycle for the next release.</P>
-
-    <P>The first thing you have to know is the branch name for the
-    branch you are interested in getting at. To do this, look at some
-    long-lived file, say the top-level HISTORY file, with "cvs status
-    -v" to see what the branch names are. (Thanks to Ian Lance Taylor
-    for pointing out that this is the easiest way to do it.) Typical
-    branch names are:</P>
-<PRE>
-    REL7_1_STABLE
-    REL7_0_PATCHES
-    REL6_5_PATCHES
-</PRE>
-
-    <P>OK, so how do you do work on a branch? By far the best way is to
-    create a separate checkout tree for the branch and do your work in
-    that. Not only is that the easiest way to deal with CVS, but you
-    really need to have the whole past tree available anyway to test
-    your work. (And you *better* test your work. Never forget that
-    dot-releases tend to go out with very little beta testing --- so
-    whenever you commit an update to a stable branch, you'd better be
-    doubly sure that it's correct.)</P>
-
-    <P>Normally, to checkout the head branch, you just cd to the place
-    you want to contain the toplevel "pgsql" directory and say</P>
-<PRE>
-    cvs ... checkout pgsql
-</PRE>
-
-    <P>To get a past branch, you cd to whereever you want it and
-    say</P>
-<PRE>
-    cvs ... checkout -r BRANCHNAME pgsql
-</PRE>
-
-    <P>For example, just a couple days ago I did</P>
-<PRE>
-    mkdir ~postgres/REL7_1
-    cd ~postgres/REL7_1
-    cvs ... checkout -r REL7_1_STABLE pgsql
-</PRE>
-
-    <P>and now I have a maintenance copy of 7.1.*.</P>
-
-    <P>When you've done a checkout in this way, the branch name is
-    "sticky": CVS automatically knows that this directory tree is for
-    the branch, and whenever you do "cvs update" or "cvs commit" in
-    this tree, you'll fetch or store the latest version in the branch,
-    not the head version. Easy as can be.</P>
-
-    <P>So, if you have a patch that needs to apply to both the head and
-    a recent stable branch, you have to make the edits and do the
-    commit twice, once in your development tree and once in your stable
-    branch tree. This is kind of a pain, which is why we don't normally
-    fork the tree right away after a major release --- we wait for a
-    dot-release or two, so that we won't have to double-patch the first
-    wave of fixes.</P>
-
-    <H3><A name="1.12">1.12</A>) Where can I get a copy of the SQL
-    standards?</H3>
-
-    <P>There are two pertinent standards, SQL92 and SQL99. These
-    standards are endorsed by ANSI and ISO. A draft of the SQL92
-    standard is available at <a
-    href="http://www.contrib.andrew.cmu.edu/~shadow/">
-    http://www.contrib.andrew.cmu.edu/~shadow/</a>. The SQL99 standard
-    must be purchased from ANSI at <a
-    href="http://webstore.ansi.org/ansidocstore/default.asp">
-    http://webstore.ansi.org/ansidocstore/default.asp</a>. The main
-    standards documents are ANSI X3.135-1992 for SQL92 and ANSI/ISO/IEC
-    9075-2-1999 for SQL99.</P>
-
-    <P>A summary of these standards is at <a
-    href="http://dbs.uni-leipzig.de/en/lokal/standards.pdf">
-    http://dbs.uni-leipzig.de/en/lokal/standards.pdf</a> and <a
-    href="http://db.konkuk.ac.kr/present/SQL3.pdf">
-    http://db.konkuk.ac.kr/present/SQL3.pdf</a>.</P>
-
-    <CENTER>
-      <H2>Technical Questions</H2>
-    </CENTER>
-
-    <H3><A name="2.1">2.1</A>) How do I efficiently access information in
-    tables from the backend code?</H3>
-
-    <P>You first need to find the tuples(rows) you are interested in.
-    There are two ways. First, <I>SearchSysCache()</I> and related
-    functions allow you to query the system catalogs. This is the
-    preferred way to access system tables, because the first call to
-    the cache loads the needed rows, and future requests can return the
-    results without accessing the base table. The caches use system
-    table indexes to look up tuples. A list of available caches is
-    located in <I>src/backend/utils/cache/syscache.c.</I>
-    <I>src/backend/utils/cache/lsyscache.c</I> contains many
-    column-specific cache lookup functions.</P>
-
-    <P>The rows returned are cache-owned versions of the heap rows.
-    Therefore, you must not modify or delete the tuple returned by
-    <I>SearchSysCache()</I>. What you <I>should</I> do is release it
-    with <I>ReleaseSysCache()</I> when you are done using it; this
-    informs the cache that it can discard that tuple if necessary. If
-    you neglect to call <I>ReleaseSysCache()</I>, then the cache entry
-    will remain locked in the cache until end of transaction, which is
-    tolerable but not very desirable.</P>
-
-    <P>If you can't use the system cache, you will need to retrieve the
-    data directly from the heap table, using the buffer cache that is
-    shared by all backends. The backend automatically takes care of
-    loading the rows into the buffer cache.</P>
-
-    <P>Open the table with <I>heap_open().</I> You can then start a
-    table scan with <I>heap_beginscan(),</I> then use
-    <I>heap_getnext()</I> and continue as long as
-    <I>HeapTupleIsValid()</I> returns true. Then do a
-    <I>heap_endscan().</I> <I>Keys</I> can be assigned to the
-    <I>scan.</I> No indexes are used, so all rows are going to be
-    compared to the keys, and only the valid rows returned.</P>
-
-    <P>You can also use <I>heap_fetch()</I> to fetch rows by block
-    number/offset. While scans automatically lock/unlock rows from the
-    buffer cache, with <I>heap_fetch(),</I> you must pass a
-    <I>Buffer</I> pointer, and <I>ReleaseBuffer()</I> it when
-    completed.</P>
-
-    <P>Once you have the row, you can get data that is common to all
-    tuples, like <I>t_self</I> and <I>t_oid,</I> by merely accessing
-    the <I>HeapTuple</I> structure entries. If you need a
-    table-specific column, you should take the HeapTuple pointer, and
-    use the <I>GETSTRUCT()</I> macro to access the table-specific start
-    of the tuple. You then cast the pointer as a <I>Form_pg_proc</I>
-    pointer if you are accessing the pg_proc table, or
-    <I>Form_pg_type</I> if you are accessing pg_type. You can then
-    access the columns by using a structure pointer:</P>
-<PRE>
-<CODE>((Form_pg_class) GETSTRUCT(tuple))-&gt;relnatts
-</CODE>
-</PRE>
-    You must not directly change <I>live</I> tuples in this way. The
-    best way is to use <I>heap_modifytuple()</I> and pass it your
-    original tuple, and the values you want changed. It returns a
-    palloc'ed tuple, which you pass to <I>heap_replace().</I> You can
-    delete tuples by passing the tuple's <I>t_self</I> to
-    <I>heap_destroy().</I> You use <I>t_self</I> for
-    <I>heap_update()</I> too. Remember, tuples can be either system
-    cache copies, which may go away after you call
-    <I>ReleaseSysCache()</I>, or read directly from disk buffers, which
-    go away when you <I>heap_getnext()</I>, <I>heap_endscan</I>, or
-    <I>ReleaseBuffer()</I>, in the <I>heap_fetch()</I> case. Or it may
-    be a palloc'ed tuple, that you must <I>pfree()</I> when finished. 
-
-    <H3><A name="2.2">2.2</A>) Why are table, column, type, function, view
-    names sometimes referenced as <I>Name</I> or <I>NameData,</I> and
-    sometimes as <I>char *?</I></H3>
-
-    <P>Table, column, type, function, and view names are stored in
-    system tables in columns of type <I>Name.</I> Name is a
-    fixed-length, null-terminated type of <I>NAMEDATALEN</I> bytes.
-    (The default value for NAMEDATALEN is 32 bytes.)</P>
-<PRE>
-<CODE>typedef struct nameData
-    {
-        char        data[NAMEDATALEN];
-    } NameData;
-    typedef NameData *Name;
-</CODE>
-</PRE>
-    Table, column, type, function, and view names that come into the
-    backend via user queries are stored as variable-length,
-    null-terminated character strings. 
-
-    <P>Many functions are called with both types of names, ie.
-    <I>heap_open().</I> Because the Name type is null-terminated, it is
-    safe to pass it to a function expecting a char *. Because there are
-    many cases where on-disk names(Name) are compared to user-supplied
-    names(char *), there are many cases where Name and char * are used
-    interchangeably.</P>
-
-    <H3><A name="2.3">2.3</A>) Why do we use <I>Node</I> and <I>List</I> to
-    make data structures?</H3>
-
-    <P>We do this because this allows a consistent way to pass data
-    inside the backend in a flexible way. Every node has a
-    <I>NodeTag</I> which specifies what type of data is inside the
-    Node. <I>Lists</I> are groups of <I>Nodes chained together as a
-    forward-linked list.</I></P>
-
-    <P>Here are some of the <I>List</I> manipulation commands:</P>
-
-    <BLOCKQUOTE>
-      <DL>
-        <DT>lfirst(i)</DT>
-
-        <DD>return the data at list element <I>i.</I></DD>
-
-        <DT>lnext(i)</DT>
-
-        <DD>return the next list element after <I>i.</I></DD>
-
-        <DT>foreach(i, list)</DT>
-
-        <DD>
-          loop through <I>list,</I> assigning each list element to
-          <I>i.</I> It is important to note that <I>i</I> is a List *,
-          not the data in the <I>List</I> element. You need to use
-          <I>lfirst(i)</I> to get at the data. Here is a typical code
-          snippet that loops through a List containing <I>Var *'s</I>
-          and processes each one: 
-<PRE>
-<CODE>List *i, *list;
-    
-    foreach(i, list)
-    {
-        Var *var = lfirst(i);
-
-        /* process var here */
-    }
-</CODE>
-</PRE>
-        </DD>
-
-        <DT>lcons(node, list)</DT>
-
-        <DD>add <I>node</I> to the front of <I>list,</I> or create a
-        new list with <I>node</I> if <I>list</I> is <I>NIL.</I></DD>
-
-        <DT>lappend(list, node)</DT>
-
-        <DD>add <I>node</I> to the end of <I>list.</I> This is more
-        expensive that lcons.</DD>
-
-        <DT>nconc(list1, list2)</DT>
-
-        <DD>Concat <I>list2</I> on to the end of <I>list1.</I></DD>
-
-        <DT>length(list)</DT>
-
-        <DD>return the length of the <I>list.</I></DD>
-
-        <DT>nth(i, list)</DT>
-
-        <DD>return the <I>i</I>'th element in <I>list.</I></DD>
-
-        <DT>lconsi, ...</DT>
-
-        <DD>There are integer versions of these: <I>lconsi, lappendi,
-        nthi.</I> <I>List's</I> containing integers instead of Node
-        pointers are used to hold list of relation object id's and
-        other integer quantities.</DD>
-      </DL>
-    </BLOCKQUOTE>
-    You can print nodes easily inside <I>gdb.</I> First, to disable
-    output truncation when you use the gdb <I>print</I> command: 
-<PRE>
-<CODE>(gdb) set print elements 0
-</CODE>
-</PRE>
-    Instead of printing values in gdb format, you can use the next two
-    commands to print out List, Node, and structure contents in a
-    verbose format that is easier to understand. List's are unrolled
-    into nodes, and nodes are printed in detail. The first prints in a
-    short format, and the second in a long format: 
-<PRE>
-<CODE>(gdb) call print(any_pointer)
-    (gdb) call pprint(any_pointer)
-</CODE>
-</PRE>
-    The output appears in the postmaster log file, or on your screen if
-    you are running a backend directly without a postmaster. 
-
-    <H3><A name="2.4">2.4</A>) I just added a field to a structure. What
-    else should I do?</H3>
-
-    <P>The structures passing around from the parser, rewrite,
-    optimizer, and executor require quite a bit of support. Most
-    structures have support routines in <I>src/backend/nodes</I> used
-    to create, copy, read, and output those structures. Make sure you
-    add support for your new field to these files. Find any other
-    places the structure may need code for your new field. <I>mkid</I>
-    is helpful with this (see above).</P>
-
-    <H3><A name="2.5">2.5</A>) Why do we use <I>palloc</I>() and
-    <I>pfree</I>() to allocate memory?</H3>
-
-    <P><I>palloc()</I> and <I>pfree()</I> are used in place of malloc()
-    and free() because we find it easier to automatically free all
-    memory allocated when a query completes. This assures us that all
-    memory that was allocated gets freed even if we have lost track of
-    where we allocated it. There are special non-query contexts that
-    memory can be allocated in. These affect when the allocated memory
-    is freed by the backend.</P>
-
-    <H3><A name="2.6">2.6</A>) What is elog()?</H3>
-
-    <P><I>elog()</I> is used to send messages to the front-end, and
-    optionally terminate the current query being processed. The first
-    parameter is an elog level of <I>DEBUG</I> (levels 1-5), <I>LOG,</I>
-    <I>INFO,</I> <I>NOTICE,</I> <I>ERROR,</I> <I>FATAL,</I> or
-    <I>PANIC.</I> <I>NOTICE</I> prints on the user's terminal and the
-    postmaster logs. <I>INFO</I> prints only to the user's terminal and
-    <I>LOG</I> prints only to the server logs. (These can be changed
-    from <I>postgresql.conf.</I>) <I>ERROR</I> prints in both places,
-    and terminates the current query, never returning from the call.
-    <I>FATAL</I> terminates the backend process. The remaining
-    parameters of <I>elog</I> are a <I>printf</I>-style set of
-    parameters to print.</P>
-
-    <P><I>elog(ERROR)</I> frees most memory and open file descriptors so
-    you don't need to clean these up before the call.</P>
-
-    <H3><A name="2.7">2.7</A>) What is CommandCounterIncrement()?</H3>
-
-    <P>Normally, transactions can not see the rows they modify. This
-    allows <CODE>UPDATE foo SET x = x + 1</CODE> to work correctly.</P>
-
-    <P>However, there are cases where a transactions needs to see rows
-    affected in previous parts of the transaction. This is accomplished
-    using a Command Counter. Incrementing the counter allows
-    transactions to be broken into pieces so each piece can see rows
-    modified by previous pieces. <I>CommandCounterIncrement()</I>
-    increments the Command Counter, creating a new part of the
-    transaction.</P>
-
-  </BODY>
-</HTML>
diff --git a/doc/src/FAQ/FAQ_german.html b/doc/src/FAQ/FAQ_german.html
deleted file mode 100644
index 6c40523afce..00000000000
--- a/doc/src/FAQ/FAQ_german.html
+++ /dev/null
@@ -1,1136 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>PostgreSQL FAQ</title>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#FF0000" VLINK="#A00000" ALINK="#0000FF">
-<H1>
-H&auml;ufig gestellte Fragen (FAQ) zu PostgreSQL
-</H1>
-<P>
-Last updated:		Sat Jul 10 00:37:57 EDT 1999
-<P>
-Current maintainer:	Bruce Momjian (<a
-href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)	<BR>
-<P>
-Deutsche &Uuml;bersetzung von Karsten Schulz (<A HREF="mailto:schulz@linux-systemhaus.de">schulz@linux-systemhaus.de</a>)	<BR>
-<P>
-Letzte Aktualisierung der deutschen &Uuml;bersetzung:	Don, den 05.08.1999, 09:00 CET
-<P>
-Die aktuellste Version dieses Dokuments kann auf der PostgreSQL Website <A HREF="http://www.Postgresql.org">http://www.PostgreSQL.org</A> angesehen werden.
-<P>
-Linux-spezifische Fragen werden in <a href="http://www.PostgreSQL.org/docs/faq-linux.html">http://www.PostgreSQL.org/docs/faq-linux.html</a>
-beantwortet (deutsche &Uuml;bersetzung in Arbeit!).<P>
-
-Irix-spezifische Fragen werden in <a
-href="http://www.PostgreSQL.org/docs/faq-irix.html">http://www.PostgreSQL.org/docs/faq-irix.html</a> beantwortet.
-<P>
-
-HPUX-spezifische Fragen werden in <a
-href="http://www.PostgreSQL.org/docs/faq-hpux.shtml">http://www.PostgreSQL.org/docs/faq-hpux.shtml</a> beantwortet.
-<P>
-
-<HR><P>
-
-<H2><CENTER>Allgemeine Fragen</CENTER></H2>
-
-<a href="#1.1">1.1</a>)	Was ist PostgreSQL?<BR>
-<a href="#1.2">1.2</a>)	Welches Copyright liegt auf PostgreSQL?<BR>
-<a href="#1.3">1.3</a>)	Auf welchen Unix-Plattformen l&auml;uft PostgreSQL?<BR>
-<a href="#1.4">1.4</a>)	Welche Nicht-Unix-Versionen sind verf&uuml;gbar?<BR>
-<a href="#1.5">1.5</a>)	Woher bekomme ich PostgreSQL?<BR>
-<a href="#1.6">1.6</a>)	Wo bekomme ich Support f&uuml;r PostgreSQL?<BR>
-<a href="#1.7">1.7</a>)	Was ist die neueste Version von PostgreSQL?<BR>
-<a href="#1.8">1.8</a>)	Welche Dokumente sind f&uuml;r PostgreSQL verf&uuml;gbar?<BR>
-<a href="#1.9">1.9</a>)	Wie erfahre ich etwas &uuml;ber bekannte Fehler oder fehlende Eigenschaften von PostgreSQL?<BR>
-<a href="#1.10">1.10</a>)	Wie kann ich SQL lernen?<BR>
-<a href="#1.11">1.11</a>)	Ist PostgreSQL Y2K (Jahr 2000) f&auml;hig?<BR>
-<a href="#1.12">1.12</a>)	Wie kann ich am Entwicklerteam teilnehmen?<BR>
-<a href="#1.13">1.13</a>)	Wie sende ich einen Fehler-Bericht?<BR>
-<a href="#1.14">1.14</a>)	Wie l&auml;uft PostgreSQL im Vergleich zu anderen Datenbanksystemen?<BR>
-
-
-<H2><CENTER>Fragen zu Benutzerprogrammen</CENTER></H2>
-
-<a href="#2.1">2.1</a>)	Gibt es ODBC-Treiber f&uuml;r PostgreSQL?<BR>
-<a href="#2.2">2.2</a>)	Welche Werkzeuge gibt es, um PostgreSQL-Datenbanken &uuml;ber Webseiten
-verf&uuml;gbar zu machen?<BR>
-<a href="#2.3">2.3</a>)	Hat PostgreSQL eine grafische Benutzerschnittstelle?
-Einen Report-Generator? Eine eingebaute Query-Schnittstelle?<BR>
-<a href="#2.4">2.4</a>)	Welche Sprachen sind f&uuml;r die Kommunikation mit PostgreSQL verf&uuml;gbar?<BR>
-
-
-<H2><CENTER>Administrative Fragen</CENTER></H2>
-
-<a href="#3.1">3.1</a>)	Warum schl&auml;gt initdb fehl?<BR>
-<a href="#3.2">3.2</a>)	Wie installiere ich PostgreSQL woanders als in /usr/local/pgsql?<BR>
-<a href="#3.3">3.3</a>)	Wenn ich den postmaster starte, bekomme ich einen <I>Bad System Call</I> oder eine <I>core dumped</I> Meldung. Warum?<BR>
-<a href="#3.4">3.4</a>)	Wenn ich versuche, den postmaster zu starten, bekomme ich eine <I>IpcMemoryCreate</I> Fehlermeldungen. Warum?<BR>
-<a href="#3.5">3.5</a>)	Wenn ich versuche, den postmaster zu starten, bekomme ich eine <I>IpcSemaphoreCreate</I> Fehlermeldungen. Warum?<BR>
-<a href="#3.6">3.6</a>)	Wie verhindere ich, da&szlig; andere Hosts auf meine PostgreSQL Datenbanken zugreifen?<BR>
-<a href="#3.7">3.7</a>)	Warum kann ich mich nicht von einer anderen Maschine mit meiner Datenbank verbinden?<BR>
-<a href="#3.8">3.8</a>)	Warum kann ich nicht als <I>root</I> auf die Datenbank zugreifen?<BR>
-<a href="#3.9">3.9</a>)	Alle meine Server st&uuml;rzen bei gleichzeitigem Tabellenzugriff ab. Warum?<BR>
-<a href="#3.10">3.10</a>)	Wie optimiere ich die Datenbankmaschine f&uuml;r bessere Leistung?<BR>
-<a href="#3.11">3.11</a>)	Welche Debugging/Fehlersuch-Hilfsmittel sind f&uuml;r PostgreSQL verf&uuml;gbar?<BR>
-<a href="#3.12">3.12</a>)	Ich bekomme die Meldung "Sorry, too many clients", wenn ich eine Verbindung versuche.  Warum?<BR>
-<a href="#3.13">3.13</a>)	Was sind die pg_psort.XXX Dateien in meinem Datenbank-Verzeichnis?<BR>
-<a href="#3.14">3.14</a>)	Wie richte ich eine Benutzergruppe (pg_group) ein?<BR>
-
-<H2><CENTER>Fragen zum Betrieb</CENTER></H2>
-
-<a href="#4.1">4.1</a>)	Das System scheint Kommata, Dezimalpunkte und Datumsformate durcheinanderzubringen.<BR>
-<a href="#4.2">4.2</a>)	Was ist der genauer Unterschied zwischen Binary Cursors und Normal Cursors?<BR>
-<a href="#4.3">4.3</a>)	Wie w&auml;hle ich per <I>SELECT</I> nur die ersten paar Zeilen in einem Query aus?<BR>
-
-<a href="#4.4">4.4</a>)	Wie bekomme ich eine Liste der Tabellen oder anderen Dingen, die ich in <I>psql</I> sehen kann<BR>
-<a href="#4.5">4.5</a>)	Wie entferne ich eine Spalte von einer Tabelle?<BR>
-
-<a href="#4.6">4.6</a>)	Was ist die Maximalgr&ouml;&szlig;e f&uuml;r eine Zeile, eine Tabelle, eine Datenbank?<BR>
-<a href="#4.7">4.7</a>)	Wieviel Plattenplatz ben&ouml;tigt eine Datenbank zur Speicherung einer Datendatei mit zeilenweisen Datens&auml;tzen?<BR>
-
-<a href="#4.8">4.8</a>)	Wie finde ich heraus, welche Indizes oder Operationen in der Datenbank definiert sind?<BR>
-<a href="#4.9">4.9</a>)	Meine Queries sind langsam oder nutzen die Indizes nicht. Warum?<BR>
-<a href="#4.10">4.10</a>)	Auf welche Weise kann ich sehen, wie der Query-Optimierer meine Abfrage auswertet?<BR>
-<a href="#4.11">4.11</a>)	Was ist ein R-Tree Index?<BR>
-<a href="#4.12">4.12</a>)	Was ist "Genetic Query Optimization"?<BR>
-
-<a href="#4.13">4.13</a>)	Wie verfahre ich bei der Suche mit regul&auml;ren Ausdr&uuml;cken und bei
-							einer Suche mit Ignorierung der Gro&szlig;- und Kleinschreibweisen?<BR>
-<a href="#4.14">4.14</a>)	Wie ermittle ich in einem Query, da&szlig; ein Feld NULL ist?<BR>
-<a href="#4.15">4.15</a>)	Was ist der Unterschied zwischen den verschiedenen CHAR-Typen?<BR>
-<a href="#4.16">4.16</a>)	Wie erzeuge ich ein serielles Feld mit automatischer Erh&ouml;hung des Inhalts?<BR>
-
-<a href="#4.17">4.17</a>)	Was ist ein Oid? Was ist ein Tid?<BR>
-<a href="#4.18">4.18</a>)	Was ist die Bedeutung der verschiedenen Ausdr&uuml;cke, die in PostgreSQL benutzt werden (z.B. attribute, class,...)?<BR>
-
-<a href="#4.19">4.19</a>)	Wieso bekomme ich einen Fehler: "FATAL:  palloc failure: memory exhausted?"<BR>
-<a href="#4.20">4.20</a>)	Wie kann ich feststellen, welche PostgreSQL-Version ich laufen habe?<BR>
-<a href="#4.21">4.21</a>)	Beim Arbeiten mit "Large-Objects" kommt die Fehlermeldung: <I>invalid large obj descriptor.</I>  Warum?<BR>
-
-<H2><CENTER>PostgreSQL erweitern</CENTER></H2>
-
-<a href="#5.1">5.1</a>)	Ich habe eine benutzerdefinierte Funktion geschrieben.  Wenn ich sie in <I>psql</I> aufrufe, kommt ein <I>core dump</I>. Warum?<BR>
-<a href="#5.2">5.2</a>)	Was bedeutet die Meldung: <I>NOTICE:PortalHeapMemoryFree: 0x402251d0 not in alloc set!</I>?<BR>
-<a href="#5.3">5.3</a>)	Wie kann ich ein paar elegante neue Feldtypen und Funktionen zu PostgreSQL beitragen?<BR>
-<a href="#5.4">5.4</a>)	Wie schreibe ich eine Funktion in C, die ein Tuple zur&uuml;ckliefert?<BR>
-<a href="#5.5">5.5</a>)	Ich habe eine der Quellendateien ge&auml;ndert. Warum macht sich die &Auml;nderung beim erneuten Compilerlauf nicht bemerkbar?<BR>
-
-<HR>
-
-<H2><CENTER>Allgemeine Fragen</CENTER></H2>
-<H4><a
-name="1.1">1.1</a>)	Was ist PostgreSQL?</H4><P>
-
-PostgreSQL ist eine Verbesserung des POSTGRES-Datenbank-Managementsystems, ein
-"Next-Generation" DBMS-Forschungsprototyp. W&auml;hrend PostgreSQL das leistungsf&auml;hige Datenmodell und
-die reichhaltigen Datentypen von POSTGRES beibeh&auml;lt, ersetzt es die PostQuel-Abfragesprache durch
-eine ausgedehnte Teilmenge von SQL. PostgreSQL ist frei und der komplette Quellcode ist verf&uuml;gbar. 
-<P>
-
-Die PostgreSQL-Entwicklung wird von einem Team von Internet-Entwickler durchgef&uuml;hrt, die alle an
-der PostgreSQL-Entwicklungs-Mailingliste teilnehmen. Der aktuelle Koordinator ist Marc G. Fournier
-(<a href="mailto:scrappy@postgreSQL.org">scrappy@postgreSQL.org</a>) (siehe unten, wie
-man sich anmelden kann). Dieses Team ist jetzt f&uuml;r alle aktuellen und zuk&uuml;nftigen Entwicklungen von PostgreSQL
-verantwortlich. 
-
-<P>
-
-
-Die Autoren von PostgreSQL 1.01 waren Andrew Yu und Jolly Chen. Viele andere haben zur Portierung,
-zu den Tests, zur Fehlersuche und zur Verbesserung des Codes beigetragen.
-Der urspr&uuml;ngliche Postgres-Code, von dem PostgreSQL abstammt, ist auf die Bem&uuml;hungen von
-vielen Studierenden und Diplomanden, sowie Programmierern, die unter
-der Weisung des Professors Michael Stonebraker an der Universit&auml;t von Kalifornien, Berkeley
-arbeiteteten, zur&uuml;ckzuf&uuml;hren.
-
-<P>
-
-Der urspr&uuml;ngliche Name der Software bei Berkeley war Postgres. Als die SQL-Funktionalit&auml;t 1995
-hinzugef&uuml;gt wurde, wurde sein Name zu Postgres95 ge&auml;ndert. Der Name wurde Ende 1996 zu
-PostgreSQL ge&auml;ndert. 
-<P>
-
-<H4><a name="1.2">1.2</a>)	Welches Copyright liegt auf PostgreSQL?</H4><P>
-
-PostgreSQL steht unter folgendem COPYRIGHT (Originaltext):<P>
-
-PostgreSQL Data Base Management System<P>
-
-Copyright (c) 1994-6 Regents of the University of California<P>
-
-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.<P>
-
-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.<P>
-
-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 "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO
-OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.<P>
-
-Es gilt die Copyright-Klausel im Original! Informativ folgt hier eine
-&Uuml;bersetzung. Die &Uuml;bersetzung besitzt keinerlei rechtlichen Status.
-Insbesondere kann sich niemand auf diese &Uuml;bersetzung berufen:
-<BR><P>
-
-PostgreSQL Datenbank Management System<P> 
-
-Copyright (c) 1994-6 Regents of the University of California<P>
-
-Die Erlaubnis, diese Software und seine Unterlagen f&uuml;r jeden m&ouml;glichen Zweck, ohne Geb&uuml;hr und ohne
-eine schriftliche Vereinbarung zu benutzen, zu kopieren, zu &auml;ndern und zu verteilen wird hiermit
-bewilligt, vorausgesetzt da&szlig; der oben genannte Urheberrechtsvermerk und dieser Paragraph und die
-folgenden zwei Paragraphen in allen Kopien erscheinen. <P>
-
-IN KEINEM FALL IST DIE UNIVERSIT&Auml;T VON KALIFORNIEN GEGEN&Uuml;BER JEDEM M&Ouml;GLICHEN BETEILIGTEN F&Uuml;R DIE DIREKTEN,
-INDIREKTEN, SPEZIELLEN, BEIL&Auml;UFIGEN ODER FOLGESCH&Auml;DEN, EINSCHLIE&szlig;LICH DER VERLORENEN PROFITE
-VERANTWORTLICH, DIE AUS DEM GEBRAUCH VON DIESER SOFTWARE UND SEINEN UNTERLAGEN
-HERAUS ENTSTEHEN, SELBST WENN DIE UNIVERSIT&Auml;T VON KALIFORNIEN VON DER M&Ouml;GLICHKEIT SOLCHEN SCHADENS
-BENACHRICHTIGT WORDEN IST. <P>
-
-DIE UNIVERSIT&Auml;T VON KALIFORNIEN LEHNT SPEZIELL ALLE M&Ouml;GLICHE GARANTIEN AB,
-EINSCHLIESSLICH, ABER NICHT BEGRENZT AUF, DIE IMPLIZIERTEN GARANTIEN VON
-GESCH&Auml;FTSNUTZEN UND EIGNUNG ZU EINEM BESTIMMTEN ZWECK. DIE SOFTWARE, DIE
-NACHSTEHEND BEREITGESTELLT WIRD, BASIERT AUF EINER "SO WIE SIE IST"-GRUNDLAGE, UND DIE UNIVERSIT&Auml;T
-VON KALIFORNIEN HAT KEINE VERPFLICHTUNGEN, WARTUNG, SUPPORT,
-AKTUALISIERUNGSVORG&Auml;NGE, VERBESSERUNGEN ODER &Auml;NDERUNGEN ZUR VERF&Uuml;GUNG
-ZU STELLEN. 
-
-<H4><a name="1.3">1.3</a>)	Auf welchen Unix-Plattformen l&auml;uft PostgreSQL?</H4><P>
-
-Die Autoren haben PostgreSQL auf folgenden Plattformen kompiliert und getestet
-(einige dieser Kompilierungen ben&ouml;tigen den C-Compiler gcc):
-<UL>
-<LI>   aix -           IBM auf AIX 3.2.5 or 4.x
-<LI>   alpha -         DEC Alpha AXP auf Digital Unix 2.0, 3.2, 4.0
-<LI>   BSD44_derived - OS abgeleitet von 4.4-lite BSD (NetBSD, FreeBSD)
-<LI>   bsdi -          BSD/OS 2.x, 3.x, 4.x
-<LI>   dgux -          DG/UX 5.4R4.11
-<LI>   hpux -          HP PA-RISC auf HP-UX 9.*, 10.*
-<LI>   i386_solaris -  i386 Solaris
-<LI>   irix5 -         SGI MIPS auf IRIX 5.3
-<LI>   linux -         Intel i86
-                       Alpha
-                       SPARC
-                       PPC
-                       M68k
-<LI>   sco -           SCO 3.2v5
-					   Unixware
-<LI>   sparc_solaris - SUN SPARC auf Solaris 2.4, 2.5, 2.5.1
-<LI>   sunos4 -        SUN SPARC auf SunOS 4.1.3
-<LI>   svr4 -          Intel x86 auf Intel SVR4 and MIPS
-<LI>   ultrix4 -       DEC MIPS auf Ultrix 4.4
-</UL>
-<P>
-
-<H4><a name="1.4">1.4</a>)	Welche Nicht-Unix-Versionen sind verf&uuml;gbar?</H4><P>
-
-Es ist m&ouml;glich, die libpq C-Bibliothek, psql und andere Schnittstellen und Binaries zu
-kompilieren, um sie auf der MS-Windows-Plattform laufen zu lassen.
-In diesem Fall l&auml;uft der Client auf MS-Windows und steht &uuml;ber TCP/IP mit einem
-Server in Verbindung, der auf einer unserer unterst&uuml;tzten Unixplattformen l&auml;uft. 
-
-Es gibt die Datei <I>win31.mak</I> in der Distribution, um die Win32 libpq-Bibliothek und psql
-zu erzeugen.<P>
-
-Der Datenbankserver arbeitet jetzt auch unter Benutzung der Cygnus Unix/NT-Porting-Bibliotheken
-auf Windows NT. Siehe auch pgsql/doc/README.NT in der Distribution.<P>
-
-Es gibt eine weitere Portierung, die U/Win benutzt bei <A HREF="http://surya.wipro.com/uwin/ported.html">http://surya.wipro.com/uwin/ported.html.</A>
-
-
-<H4><a name="1.5">1.5</a>)	Woher bekomme ich PostgreSQL?</H4><P>
-Die erste Anlaufadresse f&uuml;r PostgreSQL ist der ftp-Server <a href="ftp://ftp.postgreSQL.org/pub">ftp://ftp.postgreSQL.org/pub</a>
-<P>
-
-Die entsprechenden Spiegelserver sind auf der Hauptwebseite aufgelistet.
-
-<H4><a name="1.6">1.6</a>)	Wo bekomme ich Support f&uuml;r PostgreSQL?</H4><P>
-
-Es gibt keinen offiziellen Support f&uuml;r PostgreSQL von der Universit&auml;t von Kalifornien, Berkeley. Der
-Support wird durch freiwilligen Einsatz geleistet.
-<P>
-
-Die Mailing-Liste ist: <a href="mailto:pgsql-general@postgreSQL.org">pgsql-general@postgreSQL.org</a>.
-Die Liste ist f&uuml;r PostgreSQL betreffende Themen vorbehalten. Um sich anzumelden, sende eine
-Email mit folgenden Zeilen im Text (nicht in der Betreffzeile):
-
-<PRE>
-<CODE>
-	subscribe
-	end
-</CODE>
-</PRE><P>
-
-an <a href="mailto:pgsql-general-request@postgreSQL.org">pgsql-general-request@postgreSQL.org</a>.<P>
-
-Es gibt auch eine Digest-Liste (Eine Liste, die Mails zusammengefasst sendet).
-Um sich an dieser Digestliste anzumelden, sende eine Email an:
-<a href="mailto:pgsql-general-digest-request@postgreSQL.org">pgsql-general-digest-request@postgreSQL.org</a>
-mit folgendem Text:
-
-<PRE>
-<CODE>
-	subscribe
-	end
-</CODE>
-</PRE>
-
-Die Digests werden an die Mitglieder der Liste geschickt, wenn ca. 30kB an Mails
-zusammengekommen sind.<P>
-
-Die Bug-Mailingliste ist verf&uuml;bar. Um sich an dieser Liste anzumelden,
-sende eine Email an <a href="mailto:bugs-request@postgreSQL.org">bugs-request@postgreSQL.org</a>
-mit folgendem Text:<P>
-
-<PRE>
-<CODE>
-	subscribe
-	end
-</CODE>
-</PRE>
-
-Es gibt ebenfalls eine Entwickler-Diskussionsliste.  Um sich an dieser Liste anzumelden,
-sende eine Email an <a href="mailto:hackers-request@postgreSQL.org">hackers-request@postgreSQL.org</a>
-mit diesem Text:<P>
-
-<PRE>
-<CODE>
-	subscribe
-	end
-</CODE>
-</PRE><P>
-
-Weitere Mailinglisten und Informationen zu PostgreSQL k&ouml;nnen auf der PostgreSQL-Homepage im WWW
-gefunden werden:
-<BLOCKQUOTE>
-<a href="http://postgreSQL.org">http://postgreSQL.org</a>
-</BLOCKQUOTE><P>
-
-Es gibt au&szlig;erdem einen IRC-Channel im EFNet, Kanal #PostgreSQL.
-Bruce nutzt den Unix-Befehl: <CODE>irc -c '#PostgreSQL' "$USER" irc.phoenix.net</CODE> um teilzunehmen<P> 
-
-Kommerzieller Support f&uuml;r PostgreSQL ist bei <a href="http://www.pgsql.com">http://www.pgsql.com/</a> verf&uuml;gbar<P>
-
-
-<H4><a name="1.7">1.7</a>)	Was ist die neueste Version von PostgreSQL?</H4><P>
-
-Das neueste Release von PostgreSQL ist die Version 6.5.<P>
-
-Wir planen alle 4 Monate Hauptreleases herauszugeben.<P>
-
-
-<H4><a name="1.8">1.8</a>)	Welche Dokumente sind f&uuml;r PostgreSQL verf&uuml;gbar?	</H4><P>
-
-Einige Handb&uuml;cher, Man-Pages und einige kleine Testprogramme sind in der Distribution enthalten.
-Siehe im /doc-Verzeichnis.<P>
-
-<I>psql</I> 
-hat einige nette \d-Befehle, um Informationen &uuml;ber Typen, Operatoren, Funktionen, Aggregate, usw. zu zeigen. <P>
-
-Die Website enth&auml;lt sogar noch mehr Unterlagen.<P>
-
-<H4><a name="1.9">1.9</a>)	Wie erfahre ich etwas &uuml;ber bekannte Fehler oder fehlende Eigenschaften von PostgreSQL?
-</H4><P>
-
-
-PostgreSQL unterst&uuml;tzt eine ausgedehnte Untermenge von SQL-92.
-Siehe unser <a href="http://www.postgreSQL.org/docs/todo.html">TODO</a>
-f&uuml;r eine Auflistung der bekannten Fehler, fehlende Eigenschaften und zuk&uuml;nftige Pl&auml;ne.<P>
-
-
-<H4><a name="1.10">1.10</a>)	Wie kann ich SQL lernen?</H4><P>
-
-Es gibt nette SQL-Tutorials bei <a href="http://w3.one.net/~jhoffman/sqltut.htm">
-http://w3.one.net/~jhoffman/sqltut.htm</a> und bei <a href="http://ourworld.compuserve.com/homepages/Graeme_Birchall/DB2_COOK.HTM">
-http://ourworld.compuserve.com/homepages/Graeme_Birchall/DB2_COOK.HTM.</a><P>
-
-Viele unserer User m&ouml;gen <I>The Practical SQL Handbook</I>, Bowman et al.,
-Addison Wesley.<P>
-
-
-<H4><a name="1.11">1.11</a>)	Ist PostgreSQL Y2K (Jahr 2000) f&auml;hig?</H4><P>
-
-Ja, wir k&ouml;nnen Datumsangaben nach dem Jahr 2000 n.Chr. und vor 2000 v.Chr. leicht 
-verarbeiten.<P>
-
-<H4><a name="1.12">1.12</a>)	Wie kann ich am Entwicklerteam teilnehmen?</H4><P>
-
-Zuerst lade die neuesten Quellen herunter und lies die PostgreSQL-Entwicklerunterlagen
-auf unserer Website oder in der Distribution. Zweitens melde Dich zu den Mailinglisten
-pgsql-hackers und pgsql-patches an. Drittens sende qualitativ hochwertige Programm&auml;nderungen
-an die pgsql-patches Mailingliste.<P>
-
-Es gibt ungef&auml;hr ein Dutzend Leute, die das <I>commit</I>-Recht im PostgreSQL-CVS Archiv haben.
-Alle haben so viele hochwertige Patches eingebracht, da&szlig; es schwer f&uuml;r die 
-CVS-Verwalter war, mitzuhalten. Und wir hatten das Vertrauen, da&szlig;
-die &Auml;nderungen, die sie festlegten, sehr wahrscheinlich von hoher Qualit&auml;t sind. <P>
-
-<H4><a name="1.13">1.13</a>)	Wie sende ich einen Fehler-Bericht?</H4><P>
-
-F&uuml;lle die "Fehler-Vorlage"-Datei (bug.template im doc-Verzeichnis) aus und sende sie an: 
-<a href="mailto:bugs@postgreSQL.org">bugs@postgreSQL.org</a><P>
-
-&Uuml;berpr&uuml;fe auch den ftp-Server <a href="ftp://ftp.postgreSQL.org/pub">ftp://ftp.postgreSQL.org/pub</a>,
-um nachzusehen, ob es eine neuere PostgreSQL-Version oder neue Patches gibt.
-<P>
-
-
-<H4><a name="1.14">1.14</a>)	Wie l&auml;uft PostgreSQL im Vergleich zu anderen Datenbanksystemen?</H4><P>
-
-Es gibt verschiedene Methoden, Software zu messen: Eigenschaften, Leistung,
-Zuverl&auml;ssigkeit, Support und Preis.<P>
-
-<DL>
-<DT> <B>Eigenschaften</B>
-<DD>
-
-PostgreSQL hat die meisten Eigenschaften, die in gro&szlig;en kommerziellen DBMS's, wie
-Transaktionen, Sub-SELECTs, Trigger, Views und verfeinertes Locking, vorhanden sind.
-Wir haben einige Eigenschaften, die andere nicht haben, wie benutzerbestimmte Typen, Vererbung,
-Regeln, und die Multi-Versionen-Steuerung zum Verringern von konkurrierenden Locks.
-Wir haben keine referentielle Integrit&auml;t von externen Schl&uuml;sseln oder Outer Joins,
-aber wir arbeiten an diesen Dingen f&uuml;r unser n&auml;chstes Release.<P>
-
-<DT> <B>Leistung</B>
-<DD>
-
-PostgreSQL l&auml;uft in zwei Modi. Im normalen <I>fsync</I>-Modus wird jede komplette Transaktion
-auf die Platte geschrieben und garantiert, da&szlig;, selbst wenn das Betriebssystem abst&uuml;rzt und
-der Strom ausf&auml;llt, die Daten sicher gespeichert wurden. 
-In diesem Modus sind wir langsamer als die meisten kommerziellen Datenbanken,
-zum Teil, weil wenige von ihnen solch eine konservatives Methode der Datenspeicherung in ihren
-Standardbetriebsmodi betreiben.<P>
-
-Im <I>no-fsync</I>-Modus sind wir normalerweise schneller als kommerzielle Datenbanken. In
-diesem Modus kann ein Betriebssystemabsturz jedoch Datenkorruption zur Folge haben.
-Wir arbeiten daran, einen Zwischenmodus zur Verf&uuml;gung zu stellen, der unter weniger Leistungseinbu&szlig;e
-leidet als der <I>fsync</I>-Modus und die Datenintegrit&auml;t innerhalb 30 Sekunden 
-im Falle eines Betriebssystemabsturzes erlaubt. Der Modus ist durch den Datenbankverwalter
-ausw&auml;hlbar.<P>
-
-Im Vergleich zu MySQL oder schlankeren Datenbanksystemen sind wir hinsichtlich INSERTs/UPDATEs langsamer,
-weil wir einen Transaktions-Overhead haben.
-Selbstverst&auml;ndlich hat MySQL kaum eine der Eigenschaften, die oben im Kapitel <I>Eigenschaften</I> erw&auml;hnt werden.
-PostgreSQL ist f&uuml;r Flexibilit&auml;t und gute Eigenschaften designed, trotzdem fahren wir fort,
-die Leistung durch Profiling und Quellcodeanalyse zu verbessern.<P> 
-
-
-
-<DT> <B>Zuverl&auml;ssigkeit</B>
-<DD>
-
-Wir stellen fest, da&szlig; ein DBMS zuverl&auml;ssig sein mu&szlig;, oder es ist wertlos. Wir bem&uuml;hen uns,
-gut gepr&uuml;ften, best&auml;ndigen Code freizugeben, der nur ein Minimum an Programmfehler hat.
-Jede Freigabe hat mindestens einen Monat Betatestphase hinter sich, und unsere Freigabehistorie zeigt,
-da&szlig; wir stabile, solide Versionen freigeben, die im Produktionsbetrieb
-genutzt werden k&ouml;nnen. Wir glauben, da&szlig; wir im Vergleich mit anderer
-Datenbanksoftware vorteilhaft dastehen.<P>
-
-<DT> <B>Support</B>
-<DD>
-
-Unsere Mailingliste stellt eine gro&szlig;e Gruppe Entwickler und Benutzer zur Behebung aller
-m&ouml;glichen anzutreffenden Probleme zur Verf&uuml;gung.
-
-Wir k&ouml;nnen nicht immer eine Fehlerbehebung garantieren, 
-kommerzielle DBMS's tun dies aber auch nicht. 
-
-Direkter Zugriff zu den Entwicklern, zur Benutzergemeinschaft, zu den Handb&uuml;chern und zum Quellcode bietet h&auml;ufig 
-h&ouml;herwertigen PostgreSQL-Support im Vergleich zu anderen DBMS's. 
-
-Es gibt den kommerziellen "Pro-Ereignis"-Support,
-der f&uuml;r diejenigen bereitgestellt wird, die ihn ben&ouml;tigen. (siehe Support-Faq), <P>
-
-<DT> <B>Preis</B>
-<DD>
-PostgrSQL ist frei verf&uuml;gbar, sowohl f&uuml;r die kommerzielle, wie f&uuml;r die nicht-kommerzielle
-Nutzung. Du kannst Deinen Code fast ohne Beschr&auml;nkungen zu unserem hinzuf&uuml;gen. Die einzigen 
-Beschr&auml;nkungen werden in der BSD-artigen Lizenz weiter oben aufgef&uuml;hrt.
-</DL>
-
-
-<HR>
-
-<H2><CENTER>Fragen zu Benutzerprogrammen</CENTER></H2>
-
-
-
-<H4><a name="2.1">2.1</a>)	Gibt es ODBC-Treiber f&uuml;r PostgreSQL?</H4><P>
-
-Es sind zwei ODBC-Treiber verf&uuml;gbar: PostODBC und OpenLink ODBC.<P>
-
-PostODBC ist in der Distribution enthalten. Mehr Informationen k&ouml;nnen unter
-<a href="http://www.insightdist.com/psqlodbc">http://www.insightdist.com/psqlodbc</a> abgerufen werden.<P>
-
-OpenLink ODBC kann unter <a href="http://www.openlinksw.com/">http://www.openlinksw.com</a>
-geholt werden.
-Die Software arbeitet mit OpenLinks Standard-ODBC-Client, so da&szlig; PostgreSQL-ODBC auf
-jeder Client-Plattform zur Verf&uuml;gung steht, die unterst&uuml;tzt wird (Win, Mac, Unix, VMS).<P>
-
-Sie werden dieses Produkt wahrscheinlich an Leute verkaufen, die kommerziellen Qualit&auml;ts-Support
-brauchen, aber es wird immer eine Freeware-Version verf&uuml;gbar sein.
-Fragen dazu bitte an <a href="mailto:postgres95@openlink.co.uk">postgres95@openlink.co.uk</a>.<P>
-
-
-
-<H4><a name="2.2">2.2</a>)	Welche Werkzeuge gibt es, um PostgreSQL-Datenbanken &uuml;ber Webseiten
-verf&uuml;gbar zu machen?</H4><P>
-
-Eine nette Einf&uuml;hrung zu Datenbank-gest&uuml;tzten Webseiten kann unter 
-<a href="http://www.webtools.com">http://www.webtools.com</a> abgerufen werden.<P>
-
-Eine weitere gibt es bei <a href="http://www.phone.net/home/mwm/hotlist/">
-http://www.phone.net/home/mwm/hotlist/.</a><P>
-
-F&uuml;r die Web-Integration ist PHP eine ausgezeichnete Schnittstelle.
-PHP gibt es bei <a href="http://www.php.net">http://www.php.net</a><P>
-
-PHP ist hervorragend f&uuml;r einfache Anbindungen geeignet. F&uuml;r komplexere
-Aufgaben nutzen viele die Perl-Schnittstelle mit CGI.pm.<P>
-
-Einen WWW-Gateway, basierend auf WDB, kann man bei 
-<a href="http://www.eol.ists.ca/~dunlop/wdb-p95">http://www.eol.ists.ca/~dunlop/wdb-p95</a> herunterladen.
-
-<H4><a name="2.3">2.3</a>)	Hat PostgreSQL eine grafische Benutzerschnittstelle?
-Einen Report-Generator? Eine eingebaute Query-Schnittstelle?</H4><P>
-
-Wir haben eine nette grafische Benutzerschnittstelle mit Namen 
-<I>pgaccess,</I> welche in der Distribution enthalten ist.
-<I>pgaccess</I> hat auch einen Reportgenerator.  Die Webpage liegt hier: 
-<A HREF="http://www.flex.ro/pgaccess">http://www.flex.ro/pgaccess</A><P>
-
-In der Distribution gibt es au&szlig;erdem <I>ecpg,</I>,
-welches eine eingebundene SQL-Query-Schnittstelle f&uuml;r C zur Verf&uuml;gung stellt.
-
-
-<H4><a name="2.4">2.4</a>)	Welche Sprachen sind f&uuml;r die Kommunikation mit PostgreSQL verf&uuml;gbar?</H4><P>
-
-Wir haben:
-<UL>
-<LI>C(libpq)
-<LI>C++(libpq++)
-<LI>Embedded C(ecpg)
-<LI>Java(jdbc)
-<LI>Perl(perl5)
-<LI>ODBC(odbc)
-<LI>Python(PyGreSQL)
-<LI>TCL(libpgtcl)
-<LI>ein rohes C/4GL(contrib/pginterface)
-<LI>Embedded HTML(<a href="http://www.php.net">PHP from http://www.php.net</a>)	
-</UL><P>
-
-<HR>
-
-<H2><CENTER>Administrative Fragen</CENTER></H2><P>
-
-
-<H4><a name="3.1">3.1</a>)	Warum schl&auml;gt initdb fehl?</H4><P>
-
-<UL>
-<LI> 
-&uuml;berpr&uuml;fe, da&szlig; keine Binaries vorheriger Versionen in Deinem Pfad
-(PATH-Variable) sind.
-(Wenn Du die Meldung siehst: <CODE>NOTICE:heap_modifytuple: repl is \  9</CODE>, ist das das Problem.)
-<Li> &uuml;berpr&uuml;fe, da&szlig; der Pfad richtig gesetzt ist
-<LI> &uuml;berpr&uuml;fe, ob der User <I>postgres</I> der Eigent&uuml;mer der entsprechenden Dateien ist
-</UL><P>
-
-
-<H4><a name="3.2">3.2</a>)	Wie installiere ich PostgreSQL woanders als in /usr/local/pgsql?</H4><P>
-
-Der einfachste Weg ist mittels der --prefix Option beim configure den Pfad anzugeben.
-Falls Du das vergessen haben solltest, kannst Du die Datei Makefile.global &auml;ndern und
-POSTGRESDIR entsprechend anpassen, oder Du erzeugst ein Makefile.custom und definierst POSTGRESDIR dort.
-<P>
-
-
-<H4><a name="3.3">3.3</a>)	Wenn ich den postmaster starte, bekomme ich einen <I>Bad System Call</I> oder eine <I>core dumped</I> Meldung. Warum?</H4><P>
-
-Das kann verschiedene Ursachen haben. &Uuml;berpr&uuml;fe zuerst, ob Dein Kernel System V Extensions
-enth&auml;lt. PostgreSQL ben&ouml;tigt die Kernel-Unterst&uuml;tzung f&uuml;r Shared Memory und Semaphoren.
-<P>
-
-
-<H4><a name="3.4">3.4</a>)	Wenn ich versuche, den postmaster zu starten, bekomme ich <I>IpcMemoryCreate</I> Fehlermeldungen. Warum?</H4><P>
-
-Du hast entweder den Kernel nicht f&uuml;r Shared Memory konfiguriert, oder Du mu&szlig;t den
-Shared Memory Bereich vergr&ouml;&szlig;ern.
-Die genaue Gr&ouml;&szlig;e h&auml;ngt von Deiner Systemarchitektur ab und mit wievielen
-Puffern und Serverprozessen Du postmaster konfiguriert hast.
-F&uuml;r die meisten Systeme, mit Standardangaben f&uuml;r Puffer und Prozessen ben&ouml;tigst
-Du ein Minimum von ca. 1 MB.
-
-
-<H4><a name="3.5">3.5</a>)	Wenn ich versuche, den postmaster zu starten, bekomme ich <I>IpcSemaphoreCreate</I> Fehlermeldungen. Warum?</H4><P>
-
-Falls die Fehlermeldung <I>IpcSemaphoreCreate: semget failed (No space
-left on device)</I> lautet, dann ist Dein Kernel mit zu wenig Semaphoren konfiguriert.
-
-Postgres ben&ouml;tigt eine Semaphore pro m&ouml;glichen Backend-Prozess.
-Eine Zwischenl&ouml;sung w&auml;re, postmaster mit einer geringeren Anzahl an Backend-Prozessen zu starten.
-Benutze dazu die <I>-N</I> Option mit einem Wert kleiner als die standardm&auml;&szlig;igen 32.
-
-Eine dauerhafte L&ouml;sung w&auml;re es, die Kernel-Parameter 
-<I>SEMMNS</I> und <I>SEMMNI</I> zu erh&ouml;hen.<P>
-
-Falls die Fehlermeldung anders aussieht, hast Du m&ouml;glicherweise keine Semaphoren-Unterst&uuml;tzung
-in Deinem Kernel aktiviert.<P>
-
-
-<H4><a name="3.6">3.6</a>)	Wie verhindere ich, da&szlig; andere Hosts auf meine PostgreSQL Datenbanken zugreifen?</H4><P>
-
-Die Standardeinstellung ist, da&szlig; PostgreSQL Verbindungen von der lokalen Maschine &uuml;ber
-Unix-Domain-Sockets erlaubt. Andere Maschinen werden keine Verbindung aufbauen k&ouml;nnen, bis
-der <I>postmaster</I> mit der <I>-i</I> Option gestartet ist und die Host-basierte Authentizierung
-in der Datei <I>$PGDATA/pg_hba.conf</I> entsprechend angepasst ist.
-Das erlaubt TCP/IP-Verbindungen.
-<P>
-
-<H4><a name="3.7">3.7</a>)	Warum kann ich mich nicht von einer anderen Maschine mit meiner Datenbank verbinden?</H4><P>
-
-Die Standardeinstellung erlaubt nur Unix-Domain-Socket-Verbindungen der lokalen Maschine.
-Um TCP/IP Verbindungen zu erm&ouml;glichen, stelle sicher, da&szlig; der postmaster
-mit der <I>-i</I> Option gestartet wurde, und f&uuml;ge einen passenden Host-Eintrag in die Datei
-<I>pgsql/data/pg_hba.conf</I> ein.  Siehe auch die <I>pg_hba.conf</I> Man-Page.<P>
-
-
-<H4><a name="3.8">3.8</a>)	Warum kann ich nicht als <I>root</I> auf die Datenbank zugreifen?</H4><P>
-
-Du solltest keine Datenbank-Benutzer mit der User-ID 0 (root) erzeugen.
-Sie werden auf keine Datenbank zugreifen k&ouml;nnen. Das ist eine Sicherheitsma&szlig;nahme,
-wegen der M&ouml;glichkeit Objekt-Module dynamisch in die Datenbank zu linken.
-<P>
-
-
-<H4><a name="3.9">3.9</a>)	Alle meine Server st&uuml;rzen bei gleichzeitigem Tabellenzugriff ab. Warum?</H4><P>
-
-Dieses Problem kann durch einen Kernel verursacht werden, der ohne Support f&uuml;r Semaphoren
-konfiguriert wurde.
-
-
-<H4><a name="3.10">3.10</a>)	Wie optimiere ich die Datenbankmaschine f&uuml;r bessere Leistung?</H4><P>
-
-Sicherlich k&ouml;nnen Indizes Abfragen beschleunigen. Der <I>explain</I> Befehl
-erlaubt Dir zu sehen, wie PostgreSQL Deine Abfrage interpretiert und welche Indizes
-benutzt werden.
-<P>
-
-Wenn Du eine Menge <I>INSERTs</I> machst, &uuml;berpr&uuml;fe, ob Du sie als Stapelverarbeitung
-mit dem <I>copy</I>-Befehl abarbeiten kannst.
-Das ist viel schneller als einzelne <I>INSERTs</I>.
-
-Zweitens, SQL-Statements, die nicht in einem <I>begin work/commit</I> Transaktions-Block eingegeben werden,
-werden als eigene Transaktion behandelt. &Uuml;berpr&uuml;fe, ob die Statements nicht
-in einen einzelnen Transaktions-Block zusammengefasst werden k&ouml;nnen. Das reduziert den Transaktions-Overhead.
-
-Du kannst auch erw&auml;gen, Indizes zu l&ouml;schen und neu zu erstellen, wenn Du gro&szlig;e
-Datenmengen &auml;nderst.<P>
-
-Es gibt verschiedene Tuning-Ma&szlig;nahmen, die man ergreifen kann.
-Du kannst fsync() abschalten, indem Du beim Starten des postmasters die Optionen <I>-o -F</I> angibst.
-Das hindert fsync()´s daran, nach jeder Transaktion die Daten auf die Platte zu schreiben.
-
-Du kannst auch mit der -B Option des postmasters die Anzahl der Shared Memory Puffer f&uuml;r den Backend-Prozess erh&ouml;hen.
-Falls Du diesen Wert zu hoch einstellst, kann es sein, da&szlig; der postmaster nicht startet, weil 
-der Shared Memory Speicherplatz Deines Kernels aufgebraucht wird.
-Jeder Puffer ist 8 kB gro&szlig; und es gibt standardm&auml;&szlig;ig 64 Puffer.<P>
-
-Du kannst ebenfalls die -S Option des Backends nutzen, um die Gr&ouml;&szlig;e des Speicherplatzes f&uuml;r 
-tempor&auml;res Sortieren zu erh&ouml;hen.
-Der -S Wert wird in Kilobyte gemessen und ist standardm&auml;&szlig;ig auf 512 kB festgelegt. Es w&auml;re
-jedoch unklug, den Wert zu hoch anzugeben, da ein Query m&ouml;glicherweise Speicherplatzmangel verursacht,
-wenn es viele gleichzeitige Sortierungen durchf&uuml;hren mu&szlig;.<P>
-
-Der <I>cluster</I> Befehl kann benutzt werden, um Daten in Basistabellen zu gruppieren, so da&szlig; sie 
-auf einen Index zusammengebracht werden. Siehe auch die cluster(l) Man-Page f&uuml;r weitere Details.
-
-
-<H4><a name="3.11">3.11</a>)	Welche Debugging/Fehlersuch-Hilfsmittel sind f&uuml;r PostgreSQL verf&uuml;gbar?</H4><P>
-
-PostgreSQL hat einige M&ouml;glichkeiten, Statusinformationen zu berichten, die 
-n&uuml;tzlich f&uuml;r die Fehlersuche sein k&ouml;nnen.<P>
-
-Erstens, wenn beim configure-Lauf die Option --enable-cassert angegeben wurde,
-verfolgen viele <I>assert()´s</I> den Fortschritt des Backends und halten das Programm
-an, wenn etwas Unerwartetes passiert.
-<P>
-
-Postmaster und postgres, haben mehrere Fehlersuch-Optionen zur Verf&uuml;gung.
-Stelle zuerst sicher, da&szlig; Du den Standard-Output und Fehlerkanal in eine Datei umleitest, wenn Du den postmaster startest, :
-<PRE>
-<CODE>
-	cd /usr/local/pgsql
-	./bin/postmaster &gt;server.log 2&gt;&1 &
-</CODE>
-</PRE><P>
-
-Das erzeugt eine server.log Datei im PostgreSQL-Verzeichnis.
-Diese Datei enth&auml;lt n&uuml;tzliche Informationen &uuml;ber Probleme oder Fehler, die im Server
-aufgetreten sind. Postmaster hat eine -d Option, die noch detailliertere Informationen liefert.
-Zur -d Option wird eine Nummer angegeben, die den Debug-Level - also die Menge der berichteten Information - angibt.
-Achtung, hohe Debug-Level erzeugen schnell gro&szlig;e Logdateien!
-<P>
-
-Du kannst tats&auml;chlich das Postgres-Backend auf der Kommandozeile
-laufen lassen und SQL-Statements direkt eingeben.
-Diese Vorgehensweise wird aber <B>nur</B> zur Fehlersuche empfohlen.
-Beachte, da&szlig; ein Zeilenumbruch das SQL-Statement beendet, nicht das Semikolon.
-Wenn Du PostgreSQL mit Debugging-Symbolen kompiliert hast, kannst Du einen Debugger
-benutzen, um zu beobachten, was passiert.
-Da das Backend nicht vom postmaster gestartet wurde, l&auml;uft es nicht in der
-gleichen Umgebung und deshalb k&ouml;nnen einige locking/backend Operationen 
-nicht reproduziert werden.
-Einige Betriebssysteme k&ouml;nnen sich an einen Backend-Prozess direkt
-anh&auml;ngen, um Probleme zu diagnostizieren.
-<P>
-
-Das Programm postgres hat -s, -A und -t Optionen, die bei der Fehlersuche
-und Leistungsmessung sehr n&uuml;tzlich sein k&ouml;nnen.
-
-Du kannst das Paket auch mit Profiling kompilieren, um zu sehen, welche Funktionen wieviel 
-Ausf&uuml;hrungszeit beanspruchen.
-Das Backend Profil wird im Verzeichnis pgsql/data/base/dbname abgelegt.
-Das Client Profil wird in das aktuelle Verzeichnis abgelegt.
-<P>
-
-
-<H4><a name="3.12">3.12</a>)	Ich bekomme die Meldung "Sorry, too many clients", wenn ich eine Verbindung versuche.  Warum?</H4><P>
-
-Du mu&szlig;t die Grenze des postmasters, die festlegt,
- wieviele gleichzeitige Backend-Prozesse gestartet werden k&ouml;nnen, hochsetzen.<P>
-
-In Postgres 6.5 sind das normalerweise 32 Prozesse. Du kannst diesen Wert dadurch erh&ouml;hen,
-da&szlig; Du den postmaster mit einem entsprechenden <I>-N</I> Wert neu startest.
-In der Standardkonfiguration kannst Du <I>-N</I> auf maximal 1024 setzen.
-Falls Du mehr brauchst, erh&ouml;he <I>MAXBACKENDS</I> in <I>include/pg_config.h</I> und
-kompiliere das Paket neu.
-Du kannst den Standardwert von <I>-N</I> w&auml;hrend der Konfiguration 
-setzen, indem Du <I>--with-maxbackends</I> angibst.
-
-Anmerkung: Falls Du <I>-N</I> gr&ouml;&szlig;er als 32 einstellst, solltest
-Du <I>-B</I> auf einen Wert, h&ouml;her als 64 setzen.
-F&uuml;r eine hohe Anzahl an Backend-Prozessen, solltest Du m&ouml;glicherweise einige
-Unix-Kernel Parameter ebenfalls erh&ouml;hen.
-Folgendes Parameter solltest Du pr&uuml;fen:
-die Maximalgr&ouml;&szlig;e der Shared Memory Blocks <I>SHMMAX,</I>
-die Maximalanzahl der Semaphoren <I>SEMMNS</I> und <I>SEMMNI,
-</I> die maximale Anzahl von Prozessen <I>NPROC,</I> 
-die maximale Anzahl von Prozessen pro User <I>MAXUPRC,</I>
-und die Maximalzahl der ge&ouml;ffneten Dateien <I>NFILE</I> und <I>NINODE.</I>
-
-Der Grund f&uuml;r die Begrenzung der erlaubten Backend-Prozesse liegt darin, da&szlig; 
-verhindert werden soll, da&szlig; das System seine freien Ressourcen aufbraucht.
-<P>
-
-In den Postgres-Versionen vor 6.5 war die maximale Anzahl von Backends auf
-64 festgelegt und eine &Auml;nderung setzte eine erneute Kompilierung voraus,
-bei der die Konstante MaxBackendId in <I>include/storage/sinvaladt.h.</I>
-entsprechend angepasst wurde.<P>
-
-<H4><a name="3.13">3.13</a>)	Was sind die pg_psort.XXX Dateien in meinem Datenbank-Verzeichnis?</H4><P>
-
-Dies sind tempor&auml;re Dateien, die durch den Query-Ausf&uuml;hrer erzeugt werden.
-Wenn zum Beispiel eine Sortierung durchgef&uuml;hrt werden mu&szlig;, um ein <I>ORDER BY</I>
-auszuf&uuml;hren, und diese Sortierung mehr Platz ben&ouml;tigt, als mit dem Backend-Parameter -S
-erlaubt wurde, dann werden diese tempor&auml;ren Dateien erzeugt, um die Daten dort zu halten.
-<P>
-
-Die tempor&auml;ren Dateien sollten automatisch gel&ouml;scht werden, falls das Backend jedoch
-w&auml;hrend einer Sortierung abst&uuml;rzt, bleiben sie erhalten.
-Wenn zu diesem Zeitpunkt keine Transaktion l&auml;uft, kannst Du die
-pg_tempNNN.NN Dateien ohne Gefahr l&ouml;schen.<P>
-
-<H4><a name="3.14">3.14</a>)	Wie richte ich eine Benutzergruppe (pg_group) ein?</H4><P>
-
-Zur Zeit gibt es keine einfache Schnittstelle, um Benutzergruppen einzurichten
-Du mu&szlig;t explizit die pg_group-Tabelle mittels INSERT/UPDATE modifizieren.
-Zum Beispiel:
-
-<PRE>
-<CODE>
-	jolly=&gt; INSERT into pg_group (groname, grosysid, grolist)
-	jolly=&gt;     values ('posthackers', '1234', '{5443, 8261}');
-	INSERT 548224
-	jolly=&gt; grant INSERT on foo to group posthackers;
-	CHANGE
-	jolly=&gt;
-</CODE>
-</PRE><P>
-
-	Die Felder in pg_group sind:
-<UL>
-<LI> groname:  der Gruppenname.  Dieser Name sollte rein alphanumerisch sein. Keine Unterstriche oder andere Punktionen
-<LI>		grosysid: die Gruppen-ID.  Die Gruppen-ID ist ein int4-Feld. Sie sollte eindeutig f&uuml;r jede Gruppe sein.
-<LI>		grolist:   die Liste der pg_user IDs, die zu dieser Gruppe geh&ouml;ren. (int4[].)
-</UL><P>
-
-
-<HR>
-
-<H2><CENTER>Fragen zum Betrieb</CENTER></H2><P>
-
-
-<H4><a name="4.1">4.1</a>)	Das System scheint Kommata, Dezimalpunkte und Datumsformate durcheinanderzubringen.</H4><P>
-
-&Uuml;berpr&uuml;fe die Konfiguration Deiner Locale-Einstellung. PostgreSQL benutzt die 
-Einstellungen des jeweiligen Users und nicht die des postmaster Prozesses.
-Es gibt postgres und psql SET Befehle, um das Datumsformat zu kontrollieren.
-Setzte diese entsprechend Deiner Arbeitsumgebung.
-<P>
-
-
-<H4><a name="4.2">4.2</a>)	Was ist der genauer Unterschied zwischen Binary Cursors und Normal Cursors?</H4><P>
-
-Vgl. die <I>declare</I> Man-Page f&uuml;r eine Beschreibung.<P>
-
-<H4><a name="4.3">4.3</a>)	Wie w&auml;hle ich per <I>SELECT</I> nur die ersten paar Zeilen in einem Query aus?</H4><P>
-
-Vgl. die <I>fetch</I> Man-Page, oder benutze SELECT ... LIMIT....<P>
-
-Das verhindert nur, da&szlig; alle Ergebniszeilen zum Client &uuml;bermittelt werden.
-Die komplette Abfrage mu&szlig; abgearbeitet werden, selbst wenn Du nur die ersten paar Zeilen haben m&ouml;chtest.
-Ziehe ein Query in Erw&auml;gung, das ein <I>ORDER BY</I> benutzt. Es gibt keine M&ouml;glichkeit Zeilen
-zur&uuml;ckzuliefern, bevor nicht die komplette Abfrage abgearbeitet ist.
-<P>
-
-<H4><a name="4.4">4.4</a>)	Wie bekomme ich eine Liste der Tabellen oder anderen Dingen, die ich in <I>psql</I> sehen kann<BR></H4><P>
-
-Du kannst Dir die Datei pgsql/src/bin/psql/psql.c mit dem Quellcode f&uuml;r <I>psql</I> ansehen.
-Sie enth&auml;lt die SQL-Befehle, die die Backslash-Kommandos (\) ausf&uuml;hren.
-Seit Postgres 6.5 kannst Du <I>psql</I> auch mit der <I>-E</I> Option starten. Dadurch gibt
-<I>psql</I> die Queries aus, die es bei der Ausf&uuml;hrung der Befehle benutzt.
-<P>
-
-
-<H4><a name="4.5">4.5</a>)	Wie entferne ich eine Spalte von einer Tabelle?</H4><P>
-
-Wir unterst&uuml;tzen  <I>alter table drop column</I> nicht, aber mache es so:
-<PRE> <CODE>
-	SELECT ...  -- w&auml;hle alle Spalten au&szlig;er die, die Du entfernen willst
-	INTO TABLE new_table
-	FROM old_table;
-	DROP TABLE old_table;
-	ALTER TABLE new_table RENAME TO old_table;
-</CODE>
-</PRE><P>
-
-
-<H4><a name="4.6">4.6</a>)	Was ist die Maximalgr&ouml;&szlig;e f&uuml;r eine Zeile, eine Tabelle, eine Datenbank?</H4><P>
-
-Zeilen sind auf 8 kB begrenzt, aber das kann ge&auml;ndert werden, indem Du in
-<I>include/config.h</I> die Konstante <I>BLCKSZ</I> &auml;nderst.
-Um Attribute mit mehr als 8 kB zu nutzen, kannst Du auch das "Large Object Interface" benutzen.<P>
-Zeilen &uuml;berschreiten keine 8 kB-Grenzen. Eine Zeile mit 5 kB wird 8 kB Speicherplatz ben&ouml;tigen.
-<P>
-
-Tabellen- und Datenbankgr&ouml;&szlig;en haben keine Grenzen. Es gibt viele Datenbanken mit zig Gigabytes und
-wahrscheinlich einige mit hunderten Gigabyte.
-
-<H4><a name="4.7">4.7</a>)	Wieviel Plattenplatz ben&ouml;tigt eine Datenbank zur Speicherung einer Datendatei mit zeilenweisen Datens&auml;tzen?<BR></H4><P>
-
-Eine Postgres Datenbank kann ungef&auml;hr sechseinhalb mal soviel Platz brauchen,
-wie eine einfache Textdatei.<P>
-
-Betrachten wir eine Datei mit 300.000 Zeilen, mit jeweil zwei Integern pro Zeile.
-Die einfache Textdatei ben&ouml;tigt 2,4 MB Speicherplatz.
-Die Gr&ouml;&szlig;e der Postgres Datenbankdatei, die diese Daten enth&auml;lt, liegt 
-ungef&auml;hr bei 14 MB.
-
-<PRE>
-    36 Bytes: jeder Zeilenkopf (ungef&auml;hr)
-   + 8 Bytes: zwei Integer-Felder @ jedes 4 Bytes
-   + 4 Bytes: Zeiger auf den Datensatz
-   -----------------------------------------------
-    48 Bytes pro Zeile
-
-   Die Gr&ouml;&szlig;e einer Datenseite in PostgreSQL ist 8192 Bytes (8 KB), also:
-
-   8192 Bytes pro Seite
-   ---------------------   =  171 Zeilen pro Seite (aufgerundet)
-     48 Bytes pro Zeile
-
-   300000 Datenzeilen
-   -----------------------  =  1755 Datenbankseiten
-      171 Zeilen pro Seite
-
-1755 Datenbankseiten * 8192 Bytes pro Seite  =  14,376,960 Bytes (14MB)
-</PRE></P>
-
-Indizes haben nicht einen solchen Overhead, sie beinhalten jedoch die Daten, die sie
-indizieren und k&ouml;nnen so auch sehr gro&szlig; werden.
-<P>
-
-<H4><a name="4.8">4.8</a>)	Wie finde ich heraus, welche Indizes oder Operationen in der Datenbank definiert sind?</H4><P>
-
-<I>psql</I> hat eine Vielzahl von Backslash Befehlen, um solche Informationen zu zeigen.
-Benutze \?, um sie zu sehen.
-<P>
-
-Schaue Dir auch die Datei <I>pgsql/src/tutorial/syscat.source.</I>  an.
-Sie illustriert viele der <I>SELECT</I>s, die ben&ouml;tigt werden, um diese Informationen
-von der Datenbank-Systemtabelle zu erhalten
-<P>
-
-
-<H4><a name="4.9">4.9</a>)	Meine Queries sind langsam oder nutzen die Indizes nicht. Warum?</H4><P>
-
-PostgeSQL pflegt automatische Statistiken nicht. 
-Um die Statistiken zu aktualisieren, mu&szlig;t Du ein explizites <I>vacuum</I> eingeben.
-Nach dieser Aktualisierung wei&szlig; der Optimierer
-wieviele Zeilen in der Tabelle sind und kann besser entscheiden, ob Indizes benutzt werden sollten.
-Der Optimierer benutzt keine Indizes, wenn die Tabelle klein ist, weil ein sequentieller Suchlauf
-dann schneller sein w&uuml;rde.<P>
-
-Benutze den Befehl <I> vacuum analyze</I> f&uuml;r die spaltenspezifische Optimierung.
- <I>Vacuum analyze</I> ist f&uuml;r komplexe Multi-Join-Abfragen wichtig, damit der Optimierer
-die Anzahl der Zeilen von jeder Tabelle sch&auml;tzen und dann die passende Join-Reihenfolge
-w&auml;hlen kann.
-Das Backend verfolgt die Spaltenstatistik nicht selbst, so da&szlig; <I>vacuum analyze</I>
-regelm&auml;&szlig;ig aufgerufen werden sollte.
-<P>
-
-Indizes werden nicht f&uuml;r <I>ORDER BY</I> Operationen benutzt.<P>
-
-Bei der Nutzung von Wildcard-Operatoren wie <I>LIKE</I> oder <I>~,</I>&nbsp; k&ouml;nnen Indizes
-nur benutzt werden, wenn die Suche mit dem Anfang eines Strings startet.
-Um also Indizes zu nutzen, sollten <I>LIKE</I>-Suchen nicht mit 
-<I>%,</I> und <I>~</I>&nbsp; beginnen (Die Sucheparameter regul&auml;rer Ausdr&uuml;cke sollten
-mit <I>^.</I>&nbsp; beginnen.
-
-<H4><a name="4.10">4.10</a>)	Auf welche Weise kann ich sehen, wie der Query-Optimierer meine Abfrage auswertet?</H4><P>
-
-Vgl. die <I>EXPLAIN</I> Man-Page.<P>
-
-<H4><a name="4.11">4.11</a>)	Was ist ein R-Tree Index?</H4><P>
-
-Ein R-Tree Index wird benutzt, um r&auml;umliche Daten zu indizieren.
-Ein Hash-Index kann nicht f&uuml;r Bereichssuchen genutzt werden.
-Ein B-Tree Index kann nur f&uuml;r Bereichssuchen in eindimensionalen Daten
-genutzt werden. R-Trees k&ouml;nnen multi-dimensionale Daten abhandeln.
-Ein Beispiel: Wenn ein R-Tree Index auf ein Attribut vom Typ <I>POINT</I>
-gebildet wird, dann kann das System Abfragen wie z.B. "Zeige alle Punkte,
-die sich in einem umgebenden Rechteck befinden" effizienter beantworten.
-<P>
-
-Die kanonische Ver&ouml;ffentlichung , die das originale R-Tree Design beschreibt ist:
-<P>
-
-Guttman, A. "R-Trees: A Dynamic Index Structure for Spatial Searching."
-Proc of the 1984 ACM SIGMOD Int'l Conf on Mgmt of Data, 45-57.<P>
-
-Du kannst dieses Werk ebenfalls in Stonebraker's "Readings in Database
-Systems" finden.<P>
-
-Die eingebauten R-Trees k&ouml;nnen Polygone und Rechtecke verarbeiten.
-Theoretisch k&ouml;nnen R-Trees auf eine hohe Anzahl von Dimensionen erweitert werden.
-Praktisch bedingt diese Erweiterung eine Menge Arbeit und wir haben derzeit
-keinerlei Dokumentation dar&uuml;ber, wie das zu machen w&auml;re.
-<P>
-
-
-<H4><a name="4.12">4.12</a>)	Was ist "Genetic Query Optimization"?</H4><P>
-
-Das GEQO-Modul in PostgreSQL soll dazu dienen, das Optimierungsproblem beim
-Joining vieler Tabellen auf der Basis genetischer Algorithmen (GA) zu l&ouml;sen.
-Es erlaubt die Behandlung von gro&szlig;en Join-Queries ohne ersch&ouml;pfende Suche.
-<P>
-F&uuml;r weitere Informationen siehe die Dokumentation.
-
-
-<H4><a name="4.13">4.13</a>)	Wie verfahre ich bei der Suche mit regul&auml;ren Ausdr&uuml;cken und bei einer Suche mit Ignorierung der Gro&szlig;- und Kleinschreibweisen?</H4><P>
-
-<I>~</I> und <I>~*</I>&nbsp; sind wahrscheinlich das, was Du willst.
-Vgl. psql's  <I>\do</I> Befehl. <P>
-
-
-<H4><a name="4.14">4.14</a>)	Wie ermittle ich in einem Query, da&szlig; ein Feld NULL ist?</H4><P>
-
-Du testest die Spalte mit IS NULL und IS NOT NULL.<P>
-
-
-<H4><a name="4.15">4.15</a>)	Was ist der Unterschied zwischen den verschiedenen CHAR-Typen?</H4>
-
-<PRE>
-Typ             interner Name   Bemerkungen
---------------------------------------------------
-CHAR            char            1 Zeichen
-CHAR(#)         bpchar          mit Leerzeichen gef&uuml;llt bis zur angegebenen L&auml;nge
-VARCHAR(#)      varchar         Die Gr&ouml;&szlig;e legt die Maximall&auml;nge fest, kein Ausf&uuml;llen mit Leerzeichen
-TEXT            text            Die L&auml;nge wird nur durch die maximale Zeilenl&auml;nge beschr&auml;nkt
-BYTEA           bytea           Bytearray mit variabler L&auml;nge
-</PRE><P>
-
-Du mu&szlig;t die internen Namen benutzen, wenn Du interne Operationen durchf&uuml;hren willst.
-<P>
-
-Die letzten vier Typen sind "varlena"-Typen (d.h. die ersten vier Bytes geben die L&auml;nge an, gefolgt 
-von den Daten).
-<I>CHAR(#)</I> belegt die maximale Anzahl von Bytes, unabh&auml;ngig davon, wieviele Daten im 
-Feld gespeichert werden.
-<I>TEXT, VARCHAR(#)</I> und <I>BYTEA</I> haben alle eine variable L&auml;nge auf dem Datentr&auml;ger,
-deshalb gibt es einen leichten Geschwindigkeitsnachteil bei der Nutzung dieser Typen.
-Genauer, der Nachteil gilt f&uuml;r den Zugriff auf alle Spalten nach der ersten Spalte dieses Typs.
-<P>
-
-
-<H4><a name="4.16">4.16</a>)	Wie erzeuge ich ein serielles Feld mit automatischer Erh&ouml;hung des Inhalts?</H4><P>
-
-PostgreSQL unterst&uuml;tzt einen <I>SERIAL</I> Datentyp. Er erzeugt automatisch eine
-Sequenz und einen Index auf die Spalte. Siehe die <I>create_sequence</I> Man-Page
-f&uuml;r weitere Informationen &uuml;ber Sequenzen.
-
-Du kannst aber auch das <I>Oid</I> Feld jeder Zeile als eindeutigen Wert nutzen.
-Jedoch mu&szlig;t Du, falls Du Deine Datenbank einmal komplett ausgeben und wieder einlesen willst,
-die <I>pg_dump's -o</I> oder die <I>copy with oids</I> Option benutzen, um die Oids zu retten.<P>
-
-<H4><a name="4.17">4.17</a>)	Was ist ein Oid? Was ist ein Tid?</H4><P>
-
-Oids sind PostgreSQLs Antwort auf eindeutige Zeilen-IDs. Jede Zeile, die in PostgreSQL
-erzeugt wird, bekommt eine eindeutige Oid. Alle Oids, die w&auml;hrend initdb erzeugt werden, sind kleiner
-als 16384 (nach <I>backend/access/transam.h</I>). 
-Alle Oids, die durch den Benutzer erzeugt werden, sind gleich oder gr&ouml;&szlig;er als dieser Wert.
-Standardm&auml;&szlig;ig sind all diese Oids nicht nur innerhalb einer Tabelle oder Datenbank, sondern
-in der gesamten PostgreSQL Installation eindeutig.
-<P>
-PostgreSQL benutzt Oids in seinen internen Systemtabellen, um Zeilen zwischen den Tabellen zu 
-verbinden. Diese Oids k&ouml;nnen zur Identifikation spezifischer Benutzerzeilen und in Joins 
-genutzt werden.
-Es wird empfohlen, den Spaltentyp OID zu nutzen, um Oids-Werte zu speichern.
-Siehe die <I>sql(l)</I> Man-Page, um die anderen internen Spalten kennenzulernen.
-Du kannst einen Index auf ein Oid-Feld erzeugen, um schnelleren Zugriff zu erreichen.
-<P>
-
-Oids werden allen neuen Zeilen von einem zentralen Bereich, der von allen Datenbanken
-genutzt wird, zugewiesen. Es gibt keinen Grund, warum Du nicht die Oid &auml;ndern, oder eine Kopie der 
-Tabelle mit den originalen Oids anlegen k&ouml;nntest. 
-<PRE>
-        CREATE TABLE new_table(old_oid oid, mycol int);
-        SELECT INTO new SELECT old_oid, mycol FROM old;
-        COPY new TO '/tmp/pgtable';
-        DELETE FROM new;
-        COPY new WITH OIDS FROM '/tmp/pgtable';
-<!--
-	CREATE TABLE new_table (mycol int);
-	INSERT INTO new_table (oid, mycol) SELECT oid, mycol FROM old_table;
--->
-</PRE><P>
-
-Tids werden genutzt, um spezifische physische Zeilen mit Block und 
-Versatzwert zu identifizieren. Tids &auml;ndern sich, wenn Zeilen ge&auml;ndert oder
-neu geladen werden. Sie werden von Index-Eintr&auml;gen genutzt, um die 
-Zeilen physisch zu adressieren.
-
-<H4><a name="4.18">4.18</a>)	Was ist die Bedeutung der verschiedenen Ausdr&uuml;cke, die in PostgreSQL benutzt werden (z.B. attribute, class,...)?</H4><P>
-
-Einige der Quelltexte und die &auml;ltere Dokumentation nutzen allgemeine Begriffe.
-Hier sind einige aufgef&uuml;hrt:
-
-<UL>
-<LI> row, record, tuple
-<LI> attribute, field, column
-<LI> table, class
-<LI> retrieve, SELECT
-<LI> replace, UPDATE
-<LI> append, INSERT
-<LI> oid, serial value
-<LI> portal, cursor
-<LI> range variable, table name, table alias
-</UL><P>
-
-<H4><a name="4.19">4.19</a>)	Wieso bekomme ich einen Fehler: "FATAL:  palloc failure: memory exhausted?"<BR></H4><P>
-
-M&ouml;glicherweise ist der virtuelle Speicher verbraucht oder Dein Kernel hat
-eine niedrige Grenze f&uuml;r bestimmte Ressourcen.
-Versuche dieses, bevor Du den postmaster startest:
-
-<PRE>
-<CODE>
-	ulimit -d 65536
-	limit datasize 64m
-</CODE>
-</PRE>
-
-Je nach Deiner eingesetzten Shell mag nur einer dieser Befehle funktionieren.
-Aber es wird die Grenze des Datensegments f&uuml;r Prozesse erh&ouml;hen und vielleicht 
-l&auml;uft so Dein Query durch.
-Dieser Befehl wirkt sich auf den aktuellen Prozess und alle seine Unterprozesse 
-aus, die nach diesem Befehl gestartet werden. Falls Du ein Problem mit dem SQL-CLient hast,
-weil das Backend zu viele Daten zur&uuml;ckliefert, versuche diesen Befehl, bevor Du den 
-SQL-Client startest.
-<P>
-
-<H4><a name="4.20">4.20</a>)	Wie kann ich feststellen, welche PostgreSQL-Version ich laufen habe?<BR></H4><P>
-
-Gib in <I>psql</I> <CODE>SELECT version();</CODE> ein<P>
-
-<H4><a name="4.21">4.21</a>)	Beim Arbeiten mit "large-object" kommt die Fehlermeldung: <I>invalid large obj descriptor.</I>  Warum?<BR></H4><P>
-
-Du solltest die Befehle <CODE>BEGIN WORK</CODE> und <CODE>COMMIT
-</CODE> bei jeden Gebrauch von Large Objects benutzen. Also um
-<CODE>lo_open</CODE> ... <CODE>lo_close.</CODE><P>
-
-Die Dokumentation hat schon immer darauf hingewiesen, da&szlig; 
-<I>lo_open</I> in eine Transaktion eingebunden werden mu&szlig;, aber die PostgreSQL Versionen vor 6.5 
-haben diese Regel nicht erzwungen.
-Statt dessen scheiterten sie gelegentlich, wenn Du diese Regel gebrochen hattest.<P>
-
-Das aktuelle PostgreSQL erzwingt diese Regel, indem es die Handles der Large Objects
-beim COMMIT der Transaktion schlie&szlig;t, was sofort nach dem <I>lo_open</I> passiert,
-wenn Du nicht innerhalb einer Transaktion bist.
-So f&uuml;hrt der erste Versuch, etwas mit dem Large Object zu machen zu einem
-<I>invalid large obj descriptor</I>.
-Also wird der Code, der bisher benutzt wurde, nun diese Fehlermeldung erzeugen, wenn Du
-keine Transaktionen benutzt hast.
-<P>
-Falls Du eine Client-Schnittstelle wie ODBC benutzt, kann es sein, da&szlig; Du 
-<CODE>auto-commit off</CODE> setzen mu&szlig;t.<P>
-
-<HR>
-
-<H2><CENTER>PostgreSQL erweitern</CENTER></H2><P>
-
-
-<H4><a name="5.1">5.1</a>)	Ich habe eine benutzerdefinierte Funktion geschrieben.  Wenn ich sie in <I>psql</I> aufrufe, kommt ein <I>core dump</I>. Warum?</H4><P>
-
-Dieses Problem kann viele Ursachen haben. Teste deine Funktion zuerst in einem 
-Extra-Testprogramm. Stelle au&szlig;erdem sicher, da&szlig; Deine Funktion nicht etwa elog-Nachrichten sendet, wenn der Client Daten erwartet,
-wie in den type_in() oder type_out() Funktionen<P>
-
-
-<H4><a name="5.2">5.2</a>)	Was bedeutet die Meldung: <I>NOTICE:PortalHeapMemoryFree: 0x402251d0 not in alloc set!</I>?</H4><P>
-
-Du <I>pfree</I>st etwas, das Du nicht <I>palloc</I>t hast!
-Stelle sicher, da&szlig; Du nicht <I>malloc/free</I> und <I>palloc/pfree</I> durcheinanderw&uuml;rfelst.
-
-
-<H4><a name="5.3">5.3</a>)	Wie kann ich ein paar elegante neue Feldtypen und Funktionen zu PostgreSQL beitragen?
-</H4><P>
-
-Sende Deine Erweiterungen zur pgsql-hackers Mailing Liste, 
-und sie werden eventuell im <I>contrib/</I> Verzeichnis enden.<P>
-
-
-<H4><a name="5.4">5.4</a>)	Wie schreibe ich eine Funktion in C, die einen Tuple zur&uuml;ckliefert?</H4><P>
-
-Das erfordert derart extreme Genialit&auml;t, da&szlig; die Autoren es niemals versucht haben,
-obwohl es im Prinzip zu machen w&auml;re.<P>
-
-<H4><a name="5.5">5.5</a>)	Ich habe eine der Quellendateien ge&auml;ndert. Warum macht sich die &Auml;nderung beim erneuten Compilerlauf nicht bemerkbar?</H4><P>
-
-Die Makefiles finden nicht die richtigen Abh&auml;ngigkeiten. Du mu&szlig;t ein <I>make clean</I> und dann ein weiteres <I>make</I> machen.
-
-
-</BODY>
-</HTML>
-
-
diff --git a/doc/src/FAQ/FAQ_japanese.html b/doc/src/FAQ/FAQ_japanese.html
deleted file mode 100644
index 644995069ac..00000000000
--- a/doc/src/FAQ/FAQ_japanese.html
+++ /dev/null
@@ -1,1418 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>PostgreSQL FAQ in Japanese</TITLE>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#FF0000" VLINK="#A00000" ALINK="#0000FF">
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=x-euc-jp">
-<H1>
-PostgreSQL(¥Ý¥¹¥È¥°¥ì¥¹¡¦¥­¥å¡¼¡¦¥¨¥ë)¤Ë¤Ä¤¤¤Æ¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤Î²òÅú(FAQ)</H1>
-<P>
-¸¶Ê¸ºÇ½ª¹¹¿·Æü:		Fri Apr 26 23:03:46 EDT 2002
-<P>
-¸½ºß¤Î°Ý»ý´ÉÍý¼Ô:	Bruce Momjian (<A
-HREF="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
-Maintainer of Japanese Translation:	Jun Kuwamura (<A
-HREF="mailto:juk@postgresql.jp">juk@postgresql.jp</A>)<BR><P>
-<P>
-¤³¤Îʸ½ñ¤ÎºÇ¿·ÈǤÏ
-<A HREF="http://www.PostgreSQL.org/docs/faq-english.html">
-http://www.PostgreSQL.org/docs/faq-english.html</A>
-¤Ç¸«¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-<P>
-
-¥×¥é¥Ã¥È¥Û¡¼¥à¤ËÆÃÍ­¤Î¼ÁÌä¤Ë¤Ä¤¤¤Æ¤Ï:
- <A HREF="http://www.PostgreSQL.org/docs/">
- http://www.PostgreSQL.org/users-lounge/docs/faq.html</A>
-<BR>¤Ë²óÅú¤¬¤¢¤ê¤Þ¤¹¡£
-<P>
-
-<P>
-<small><PRE>
-(°Ê²¼¡¢Ìõ¼Ô¤Ë¤è¤ëÃí¼á¤ò [ÌõÃí¡§ ¤È ] ¤È¤Ç°Ï¤ó¤Çµ­¤·¤Þ¤¹¡£)
-[ÌõÃí¡§
-	ÆüËܸìÈÇÀ½ºî¤Ë¤Ä¤¤¤Æ¤Î¥á¥â¤ÏºÇ¸åÈø¤Ø°ÜÆ°¤·¤Þ¤·¤¿¡£
-
-	ÆüËܸìÈǤΤ³¤Îʸ½ñ¤Ï ËÜ²È "User's Lounge" ¤Î "Collection of FAQs" ¤Î
-	"Japanese" ¤È¤¤¤¦¸«½Ð¤·¤Î¤È¤³¤í¤Ë¤¢¤ê¤Þ¤¹¡£¤Þ¤¿¡¢°Ê²¼¤Î¥µ¥¤¥È¤Ë¤â
-	¤¢¤ê¤Þ¤¹¡£
-		<A HREF="http://www.rccm.co.jp/~juk/pgsql/">http://www.rccm.co.jp/~juk/pgsql/</A>
-		<A HREF="http://www.linux.or.jp/JF/">http://www.linux.or.jp/JF/</A>
-
-	¤³¤ÎÏÂÌõ¤Ë¤Ä¤¤¤Æ¤ªµ¤¤Å¤­¤ÎÅÀ¤Ï(<A HREF="mailto:juk@postgresql.jp">juk@postgresql.jp</A>)¤Þ¤Ç¥á¡¼¥ë¤Ç¤ª´ó¤»²¼¤µ¤¤¡£
-]
-</PRE></small>
-
-<P>
-<HR>
-<P>
-
-<H2><CENTER> °ìÈÌŪ¤Ê¼ÁÌä</CENTER></H2>
-
-<A HREF="#1.1">1.1</A>)	PostgreSQL¤È¤Ï²¿¤Ç¤¹¤«¡© ²¿¤ÈÆɤߤޤ¹¤«¡©<BR>
-<A HREF="#1.2">1.2</A>)	PostgreSQL¤ÎÃøºî¸¢¤Ï¤É¤¦¤Ê¤Ã¤Æ¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.3">1.3</A>)	PostgreSQL¤ÎÆ°ºî¤¹¤ëUnix¥×¥é¥Ã¥È¥Û¡¼¥à¤Ï¡©<BR>
-<A HREF="#1.4">1.4</A>)	Unix°Ê³°¤Î°Ü¿¢ÈǤǻȤ¨¤ë¤â¤Î¤Ï¡©<BR>
-<A HREF="#1.5">1.5</A>)	PostgreSQL¤Ï¤É¤³¤«¤éÆþ¼ê¤Ç¤­¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.6">1.6</A>)	¥µ¥Ý¡¼¥È¤Ï¤É¤³¤Ç¼õ¤±¤é¤ì¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.7">1.7</A>)	ºÇ¿·ÈǤϤɤì¤Ç¤¹¤«<BR>
-<A HREF="#1.8">1.8</A>)	¤É¤Î¤è¤¦¤Êʸ½ñ¤¬¤¢¤ê¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.9">1.9</A>)	´ûÃΤΥХ°¤ä̤¤À̵¤¤µ¡Ç½¤Ï¤É¤¦¤ä¤Ã¤Æ¸«¤Ä¤±¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.10">1.10</A>)	<small>SQL</small>¤Ï¤É¤¦¤¹¤ì¤Ð³Ø¤Ù¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.11">1.11</A>)	PostgreSQL¤ÏÀ¾Îñ2000ǯÌäÂê(Y2K)¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.12">1.12</A>)	³«È¯¥Á¡¼¥à¤Ë¤Ï¤É¤Î¤è¤¦¤Ë»²²Ã¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.13">1.13</A>)	¥Ð¥°¥ì¥Ý¡¼¥È¤Ï¤É¤Î¤è¤¦¤Ëȯ¿®¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#1.14">1.14</A>)	¾¤Î<small>DBMS</small>¤Î¤ÈÈæ¤Ù¤ÆPostgreSQL¤Ï¤É¤¦¤Ê¤Î¤Ç¤¹¤«¡©<BR>
-<A HREF="#1.15">1.15</A>)	PostgreSQL¤ò»ñ¶âÌ̤DZç½õ¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Ç¤¹¤«¡©<BR>
-
-
-<H2><CENTER>¥æ¡¼¥¶¡¼¡¦¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÁÌä</CENTER></H2>
-
-<A HREF="#2.1">2.1</A>)	PostgreSQL ¤Î <small>ODBC</small> ¥É¥é¥¤¥Ð¡¼¤Ï¤¢¤ê¤Þ¤¹¤«¡©<BR>
-<A HREF="#2.2">2.2</A>)	PostgreSQL ¤ò Web ¥Ú¡¼¥¸¤ÈÏ¢·È¤µ¤»¤ë¤Ë¤Ï¤É¤ó¤Ê¥Ä¡¼¥ë¤¬¤¢¤ê¤Þ¤¹¤«¡©<BR>
-<A HREF="#2.3">2.3</A>)	PostgreSQL ¤Ë¥°¥é¥Õ¥£¥«¥ë¡¦¥æ¡¼¥¶¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Ï¤¢¤ê¤Þ¤¹¤«¡©
-¥ì¥Ý¡¼¥È¥¸¥§¥Í¥ì¡¼¥¿¤äËä¤á¹þ¤ßÌ䤤¹ç¤ï¤»¸À¸ì¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Ï¤¢¤ê¤Þ¤¹¤«¡©<BR>
-<A HREF="#2.4">2.4</A>)	PostgreSQL ¤ÈÄÌ¿®¤¹¤ë¤Ë¤Ï¤É¤ó¤Ê¸À¸ì¤¬»È¤¨¤Þ¤¹¤«¡©<BR>
-
-
-<H2><CENTER>´ÉÍý¾å¤Î¼ÁÌä</CENTER></H2>
-
-<A HREF="#3.1">3.1</A>)	¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð <I>/usr/local/pgsql</I> °Ê³°¤Î¾ì½ê¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¤«¡©<BR>
-<A HREF="#3.2">3.2</A>)	postmaster ¤òÁö¤é¤»¤ë¤È¡¢
-<I>Bad System Call</I> ¤È¤«¥³¥¢¡¦¥À¥ó¥×¤·¤¿¤È¤Î¥á¥Ã¥»¡¼¥¸¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#3.3">3.3</A>)	<I>postmaster</I> ¤òÁö¤é¤»¤è¤¦¤È¤¹¤ë¤È¡¢
-<I>IpcMemoryCreate</I> ¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#3.4">3.4</A>)	<I>postmaster¤ò</I>Áö¤é¤»¤è¤¦¤È¤¹¤ë¤È¡¢
-<I>IpcSemaphoreCreate</I> ¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#3.5">3.5</A>)	¾¤Î¥Û¥¹¥È¤«¤é¤ÎÀܳ¤Ï¤É¤Î¤è¤¦¤ËÀ©¸æ¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#3.6">3.6</A>)	¤è¤êÎɤ¤À­Ç½¤òÆÀ¤ë¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥¨¥ó¥¸¥ó¤ò¤É¤Î¤è¤¦¤ËÄ´À°¤¹¤ì¤ÐÎɤ¤¤Ç¤¹¤«¡©<BR>
-<A HREF="#3.7">3.7</A>)	¤É¤Î¤è¤¦¤Ê¥Ç¥Ð¥°µ¡Ç½¤¬»È¤¨¤Þ¤¹¤«¡©<BR>
-<A HREF="#3.8">3.8</A>)	Àܳ¤·¤è¤¦¤È¤¹¤ë¤È¤­¤Ë <I>'Sorry, too many clients'</I> ¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#3.9">3.9</A>)	¼«Ê¬¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë <I>pg_sorttemp.XXX</I> ¥Õ¥¡¥¤¥ë¤Ï²¿¤Ç¤¹¤«¡©<BR>
-
-
-
-<H2><CENTER>Áàºî¾å¤Î¼ÁÌä</CENTER></H2>
-
-<A HREF="#4.1">4.1</A>)	¥Ð¥¤¥Ê¥ê¡¦¥«¡¼¥½¥ë¤ÈÄ̾參¡¼¥½¥ë¤È¤Î°ã¤¤¤Ï²¿¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.2">4.2</A>)	ºÇ½é¤Î¿ô¥í¥¦¤Î¤ß¤ò <small>select</small> ¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.3">4.3</A>)	¥Æ¡¼¥Ö¥ë¤ä¤½¤Î¾¤Î¾ðÊó¤Î¥ê¥¹¥È¤ò <I>psql</I> ¤Ç¸«¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.4">4.4</A>)	¥Æ¡¼¥Ö¥ë¤«¤é¥«¥é¥à¤Îºï½ü¤Ï¤É¤Î¤è¤¦¤Ë¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.5">4.5</A>)	¥í¥¦¡¢¥Æ¡¼¥Ö¥ë¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎºÇÂ祵¥¤¥º¤Ï¡©<BR>
-<A HREF="#4.6">4.6</A>)	°ìÈÌŪ¤Ê¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤«¤é¥Ç¡¼¥¿¤òÊݸ¤¹¤ë¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Ç¥£¥¹¥¯ÍÆÎ̤ϤɤΤ¯¤é¤¤É¬ÍפǤ¹¤«¡©<BR>
-<A HREF="#4.7">4.7</A>)	ÄêµÁ¤µ¤ì¤¿¥Æ¡¼¥Ö¥ë¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¢¤ª¤è¤Ó¡¢¥æ¡¼¥¶¤ò¤É¤Î¤è¤¦¤Ë¤·¤Æ¸«¤Ä¤±½Ð¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.8">4.8</A>)	Ì䤤¹ç¤ï¤»¤¬ÃÙ¤¤¤¦¤¨¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤Ã¤Æ¤¤¤ëÍͻҤ¬¤¢¤ê¤Þ¤»¤ó¡£¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.9">4.9</A>)	Ì䤤¹ç¤ï¤»¥ª¥Ö¥Æ¥£¥Þ¥¤¥¶¤¬¤É¤Î¤è¤¦¤ËÌ䤤¹ç¤ï¤»¤òɾ²Á¤¹¤ë¤«¤ò¸«¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.10">4.10</A>) R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤È¤Ï²¿¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.11">4.11</A>) °äÅÁŪÌ䤤¹ç¤ï¤»ºÇŬ²½¤È¤Ï²¿¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.12">4.12</A>) Àµµ¬É½¸½¤Ç¤Î¸¡º÷¤äÂçʸ»ú¤È¾®Ê¸»ú¤È¤ò¶èÊ̤·¤Ê¤¤Àµµ¬É½¸½¸¡º÷¤Ï¤É¤Î¤è¤¦¤Ë¼Â¸½¤·¤Þ¤¹¤«¡©Âçʸ»ú¤È¾®Ê¸»ú¤È¤ò¶èÊ̤·¤Ê¤¤¸¡º÷¤Î¤¿¤á¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¤É¤Î¤è¤¦¤Ë»È¤¤¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.13">4.13</A>) Ì䤤¹ç¤ï¤»¤ÎÃæ¤Ç¡¢¥Õ¥£¡¼¥ë¥É¤¬ <small>NULL</small> ¤Ç¤¢¤ë¤³¤È¤ò¸¡½Ð¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.14">4.14</A>) ¿§¡¹¤Êʸ»ú·¿¤Î¤½¤ì¤¾¤ì¤Î°ã¤¤¤Ï²¿¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.15.1">4.15.1</A>) ÄÌÈÖ(serial)¡¿¼«Æ°Áýʬ¥Õ¥£¡¼¥ë¥É¤Ï¤É¤Î¤è¤¦¤Ë¤Ä¤¯¤ê¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.15.2">4.15.2</A>) <small>SERIAL</small>¥Ç¡¼¥¿·¿¤ËÁÞÆþ¤µ¤ì¤ëÃͤϡ¢¤É¤¦¤¹¤ì¤ÐÆÀ¤é¤ì¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.15.3">4.15.3</A>) ¾¤Î¥æ¡¼¥¶¤È¤Î¶¥¹ç¾õÂÖ¤òÈò¤±¤ë¤¿¤á¤Ë¤Ï¡¢<I>currval()</I> ¤È <I>nextval()</I> ¤Ï»È¤ï¤Ê¤¤¤Û¤¦¤¬¤è¤¤¤Î¤Ç¤·¤ç¤¦¤«¡©<BR>
-<A HREF="#4.15.4">4.15.4</A>) ¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤¬ÃæÃǤ·¤¿¤È¤­¤Ë¤â¤¦¤¤¤Á¤É¥·¡¼¥±¥ó¥¹Èֹ椬»È¤ï¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©¥·¡¼¥±¥ó¥¹¡¿SERIAL¥«¥é¥à¤Ë¶õ¤­¤¬¤¢¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.15">4.16</A>) <small>OID</small> ¤È¤Ï²¿¤Ç¤¹¤«¡© <small>TID</small> ¤È¤Ï²¿¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.17">4.17</A>) PostgreSQL ¤Ç»È¤ï¤ì¤ë¤¤¤¯¤Ä¤«¤ÎÍѸì¤Î°ÕÌ£¤Ï²¿¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.18">4.18</A>) ¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸ <I>"ERROR: Memory exhausted in AllocSetAlloc()"</I>¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.19">4.19</A>) ¤É¤Î¥Ð¡¼¥¸¥ç¥ó¤Î PostgreSQL ¤òÁö¤é¤»¤Æ¤¤¤ë¤Î¤«¤òÄ´¤Ù¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.20">4.20</A>) ¥é¡¼¥¸¥ª¥Ö¥¸¥§¥¯¥È¤ÎÁàºî¤Ç¡¢<I>invalid large obj descriptor</I>¤È½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.21">4.21</A>) ¸½ºß¤Î»þ¹ï¤¬¥Ç¥Õ¥©¥ë¥È¤È¤Ê¤ë¤è¤¦¤Ê¥«¥é¥à¤Ï¤É¤Î¤è¤¦¤Ë¤Ä¤¯¤ê¤Þ¤¹¤«¡©<BR>
-<A HREF="#4.22">4.22</A>) ¤Ê¤¼¡¢<small>IN</small>¤ò»È¤¦ÉûÌ䤤¹ç¤ï¤»¤¬¤È¤Æ¤âÃÙ¤¤¤Î¤Ç¤¹¤«¡©<BR>
-<A HREF="#4.23">4.23</A>) <i>³°Éô</i>·ë¹ç(<i>outer</i> join)¤Ï¤É¤Î¤è¤¦¤Ë¼Â¸½¤·¤Þ¤¹¤«?<BR>
-<A HREF="#4.24">4.24</A>) Ê£¿ô¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»È¤¦Ì䤤¹ç¤ï¤»¤Ï¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð¤Ç¤­¤Þ¤¹¤«¡©<br>
-<A HREF="#4.25">4.25</A>) ´Ø¿ô¤ÇÊ£¿ô¤Î¥í¥¦¤Þ¤¿¤Ï¥«¥é¥à¤òÊÖ¤¹¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<br>
-
-<H2><CENTER>PostgreSQL¤Î³ÈÄ¥¤Ë¤Ä¤¤¤Æ¤Î¼ÁÌä</CENTER></H2>
-
-<A HREF="#5.1">5.1</A>)	¼«Ê¬¤Ç½ñ¤¤¤¿¥æ¡¼¥¶ÄêµÁ´Ø¿ô¤ò psql ¤ÎÃæ¤Ç¼Â¹Ô¤¹¤ë¤È¥³¥¢¡¦¥À¥ó¥×¤·¤Æ¤·¤Þ¤¦¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<A HREF="#5.2">5.2</A>)	PostgreSQL ÍѤ˽ñ¤¤¤¿¤Á¤ç¤Ã¤ÈÁÇŨ¤Ê¿·¤·¤¤·¿¤ä´Ø¿ô¤òÄ󶡤·¤Æ¥×¥í¥¸¥§¥¯¥È¤Ë¹×¸¥¤·¤¿¤¤¤Î¤Ç¤¹¤¬¡©<BR>
-<A HREF="#5.3">5.3</A>)	¥¿¥×¥ë¤òÊÖ¤¹ C¸À¸ì¤Î´Ø¿ô¤Ï¤É¤Î¤è¤¦¤Ë½ñ¤­¤Þ¤¹¤«¡©<BR>
-<A HREF="#5.4">5.4</A>)	¥½¡¼¥¹¡¦¥Õ¥¡¥¤¥ë¤òÊѹ¹¤·¤Þ¤·¤¿¡£ºÆ¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤âÊѲ½¤¬¸«¤é¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©<BR>
-<P>
-<HR>
-<H2><CENTER>°ìÈÌŪ¤Ê¼ÁÌä</CENTER></H2>
-<P>
-
-<H4><A NAME="1.1">1.1</A>)	PostgreSQL ¤È¤Ï²¿¤Ç¤¹¤«¡©</H4>
-
-<P><I>Post-Gres-Q-L.</I>(¥Ý¥¹¥È - ¥°¥ì¥¹ - ¥­¥å¡¼ - ¥¨¥ë) ¤Èȯ²»¤·¤Þ¤¹¡£</P>
-<P>PostgreSQL ¤Ï¼¡À¤Âå <small>DBMS</small> ¸¦µæÍѤΥץí¥È¥¿¥¤¥×¤Ç¤¢¤Ã¤¿ POSTGRES ¥Ç¡¼¥¿¥Ù¡¼¥¹´ÉÍý¥·¥¹¥Æ¥à¤Î²þÎÉÈǤǤ¹¡£PostgreSQL ¤Ï POSTGRES ¤Î¶¯ÎϤʥǡ¼¥¿¡¦¥â¥Ç¥ë¤ÈË­É٤ʥǡ¼¥¿¡¦¥¿¥¤¥×(·¿)¤òÊÝ»ý¤·¤Ê¤¬¤é¡¢POSTGRES ¤Ç»È¤ï¤ì¤¿ PostQuel Ì䤤¹ç¤ï¤»¸À¸ì¤ò¡¢³ÈÄ¥¤·¤¿ <small>SQL</small> ¤Î¥µ¥Ö¥»¥Ã¥È¤ËÃÖ¤­´¹¤¨¤Æ¤¤¤Þ¤¹¡£PostgreSQL ¤Ï̵ÎÁ¤Ç´°Á´¤Ê¥½¡¼¥¹¤òÍøÍѤǤ­¤Þ¤¹¡£
-
-<P>PostgreSQL ¤Î³«È¯¤Ï¡¢PostgreSQL ³«È¯¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ë»²²Ã¤·¤Æ¤¤¤ë¥¤¥ó¥¿¡¼¥Í¥Ã¥È¾å¤Î³«È¯¼Ô¥Á¡¼¥à¤Ç¤¹¤Ù¤Æ¹Ô¤Ê¤ï¤ì¤Æ¤¤¤Þ¤¹¡£¸½ºß¤ÎºÂĹ¤Ï Marc G. Fournier ( <A HREF="mailto:scrappy@PostgreSQL.org">scrappy@PostgreSQL.org</A> )¤Ç¤¹¡£(°Ê²¼¤Ë»²²Ã¤Î»ÅÊý¤¬¤¢¤ê¤Þ¤¹¡£)¸½ºß¡¢¤³¤Î¥Á¡¼¥à¤¬ PostgreSQL ³«È¯¤Î¤¹¤Ù¤Æ¤ÎÌÌÅݤò¤ß¤Æ¤¤¤Þ¤¹¡£
-
-<P>Postgres95-1.01 ¤ÎÃ濴Ū¤Ê³«È¯¼Ô¤Ï Andrew Yu ¤È Jolly Chen ¤Ç¤·¤¿¤¬¡¢¤½¤Î¾ÂçÀª¤Î¿Í¡¹¤¬¤³¤Î¥³¡¼¥É¤Î°Ü¿¢¡¢¥Æ¥¹¥È¡¢¥Ç¥Ð¥°¡¢¤ª¤è¤Ó¡¢²þÎɤ˻²²Ã¤·¤Þ¤·¤¿¡£PostgreSQL ¤ÎÇÉÀ¸¸µ¥³¡¼¥É¤Ç¤¢¤ë POSTGRES ¤Ï¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³Ø¥Ð¡¼¥¯¥ì¥¤¹»¤Ë¤ª¤¤¤Æ¡¢ Michael Stonebraker ¶µ¼ø¤Î»Ø´ø¤Î¤â¤È¡¢Â¿¤¯¤Î³ØÀ¸¡¢Â´¶ÈÀ¸¡¢ËÜ¿¦¤Î¥×¥í¥°¥é¥Þ¤¿¤Á¤ÎÅØÎϤˤè¤êºî¤é¤ì¤Þ¤·¤¿¡£
-
-<P>¥Ð¡¼¥¯¥ì¥¤¤Ë¤ª¤±¤ë¤³¤Î¥½¥Õ¥È¥¦¥§¥¢¤Î¤â¤È¤Î̾Á°¤Ï Postgres ¤Ç¤·¤¿¤¬¡¢<SMALL>SQL</small> ¤Îµ¡Ç½¤¬Äɲ䵤줿 1995 ǯ¤Ë¤½¤Î̾Á°¤Ï Postgres95 ¤ËÊѹ¹¤µ¤ì¡¢1996 ǯ¤Î½ª¤ê¤Ë¤½¤Î̾Á°¤Ï PostgreSQL ¤ËÊѹ¹¤µ¤ì¤Þ¤·¤¿¡£
-
-<P>
-<H4><A NAME="1.2">1.2</A>)	PostgreSQL ¤ÎÃøºî¸¢¤Ï¤É¤¦¤Ê¤Ã¤Æ¤Þ¤¹¤«¡©</H4>
-
-<P> PostgreSQL ¤Ï²¼µ­¤ÎÃøºî¸¢¤Ë½¾¤¤¤Þ¤¹¡£
-<small><PRE>
-    [ÌõÃí¡§
-        ÀµÊ¸¤Ï±Ñ¸ì¤Ç¤¹¡£»²¹Í¤È¤·¤Æ¡¢Ìõʸ¤òÊ»µ­·ÇºÜ¤·¤Þ¤¹¡£
-    ]
-</PRE></small>
-<P>
-PostgreSQL Data Base Management System<P>
-
-Portions Copyright (c) 1996-2002, PostgreSQL Global Development Group
-Portions Copyright (c) 1994-6 Regents of the University of California<P>
-
-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.
-<P>
-<STRONG>
-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.
-<P>
-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 "AS IS" BASIS, AND THE UNIVERSITY OF CALIFORNIA HAS NO
-OBLIGATIONS TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR
-MODIFICATIONS.
-</STRONG>
-<P>
-
-<small><PRE>
-	POSTGRESQL ¥Ç¡¼¥¿¥Ù¡¼¥¹´ÉÍý¥·¥¹¥Æ¥à
-
-	ÉôʬŪÃøºî¸¢ (c) 1996-2002, PostgreSQL¹ñºÝ³«È¯¥Á¡¼¥à
-	ÉôʬŪÃøºî¸¢ (c) 1994-6 ¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³ØËܹ»
-
-
-	  ËÜ¥½¥Õ¥È¥¦¥§¥¢¤ª¤è¤Ó¤½¤Îʸ½ñ°ì¼°¤Ï¾åµ­¤ÎÃøºî¸¢É½¼¨¤È¡¢¤³¤Îʸ¾Ï
-	¤ª¤è¤Ó¤³¤ì¤Ë³¤¯Æó¤Ä¤ÎÃÊÍÁ´¤Æ¤ÎÊ£À½¤ËźÉÕ¤µ¤ì¤Æ¤¤¤ë¸Â¤ê¤Ë¤ª¤¤
-	¤Æ¡¢»ÈÍÑ¡¢Ê£À½¡¢½¤Àµ¤ª¤è¤ÓÇÛÉդεö²Ä¤ò¡¢¤¤¤«¤Ê¤ëÌÜŪ¤Ç¤¢¤Ã¤â¡¢Ìµ
-	½þ¤Ç¤«¤ÄƱ°Õ½ñ̵¤·¤Ë¹Ô¤Ê¤¨¤ë¤³¤È¤ò¤³¤³¤Ëǧ¤á¤Þ¤¹¡£
-	
-	  ¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³Ø¤Ï¡¢¤¤¤«¤Ê¤ëÅö»ö¼Ô¤Ë¤¿¤¤¤·¤Æ¤â¡¢Íø±×¤Î²õ¼º¤ò
-	´Þ¤à¡¢Ä¾ÀÜŪ¡¢´ÖÀÜŪ¡¢ÆÃÊÌ¡¢¶öÁ³¤¢¤ë¤¤¤ÏɬÁ³Åª¤Ë¤«¤«¤ï¤é¤ºÀ¸¤¸¤¿
-	»³²¤Ë¤Ä¤¤¤Æ¡¢¤¿¤È¤¨¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³Ø¤¬¤³¤ì¤é¤Î»³²¤Ë¤Ä¤¤¤ÆÁÊÄÉ
-	¤ò¼õ¤±¤Æ¤¤¤¿¤È¤·¤Æ¤â¡¢°ìÀÚ¤ÎÀÕǤ¤òÉ餤¤Þ¤»¤ó¡£
-	
-	  ¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³Ø¤Ï¡¢¾¦ÍÑÌÜŪ¤Ë¤ª¤±¤ë°ÅÌÛ¤ÎÊݾڤȡ¢ÆÃÄêÌÜŪ¤Ç
-	¤ÎŬ¹çÀ­¤Ë´Ø¤·¤Æ¤Ï¤â¤È¤è¤ê¡¢¤³¤ì¤é¤Ë¸Â¤é¤º¡¢¤¤¤«¤Ê¤ëÊݾڤâÊü´þ¤¹
-	¤ë¤³¤È¤òÌÀ¸À¤·¤Þ¤¹¡£°Ê²¼¤ËÍÑ°Õ¤µ¤ì¤¿¥½¥Õ¥È¥¦¥§¥¢¤Ï¡Ö¤½¤Î¤Þ¤Þ¡×¤ò
-	´ðËܸ¶Íý¤È¤·¡¢¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³Ø¤Ï¤½¤ì¤ò°Ý»ý¡¢»Ù±ç¡¢¹¹¿·¡¢²þÎɤ¢
-	¤ë¤¤¤Ï½¤Àµ¤¹¤ëµÁ̳¤òÉ餤¤Þ¤»¤ó¡£
-
-    [ÌõÃí¡§
-	Ãøºî¸¢¤Ë´Ø¤¹¤ëÀµÊ¸¤Ï¾åµ­¤Î±Ñ¸ì¤Ë¤è¤ëɽµ­¤Ç¤¹¡£ÆüËܸìÌõ¤Ï¤¢¤¯¤Þ¤Ç
-	»²¹Í¤Ç¤¹¡£
-    ]
-</PRE></small>
-
-<p>¾åµ­¤ÏBSD¥é¥¤¥»¥ó¥¹¤Ç¸Å¤­¥ª¡¼¥×¥ó¥½¡¼¥¹¤Î¥é¥¤¥»¥ó¥¹¤Ç¤¹¡£¥½¡¼¥¹¥³¡¼¥É
-¤¬¤É¤Î¤è¤¦¤Ë»È¤ï¤ì¤è¤¦¤È¤âÀ©¸Â¤·¤Þ¤»¤ó¡£¹¥¤Þ¤·¤¤¤³¤È¤Ê¤Î¤Ç¡¢²æ¡¹¤â¤½¤ì¤ò
-ÊѤ¨¤ë¤Ä¤â¤ê¤Ï¤¢¤ê¤Þ¤»¤ó¡£</p>
-
-<P>
-<H4><A NAME="1.3">1.3</A>)	PostgreSQL ¤ÎÆ°ºî´Ä¶­¤Ï¡©</H4>
-
-<P>Ãø¼Ô¤é¤Ï PostgreSQL ¤Î¥³¥ó¥Ñ¥¤¥ë¤È¥Æ¥¹¥È¤ò¼¡¤Î¥×¥é¥Ã¥È¥Û¡¼¥à¾å¤Ç¹Ô¤Ê¤¤¤Þ¤·¤¿¡£(¤³¤ì¤é¤Î¤¦¤Á¤Î¤¤¤¯¤Ä¤«¤Ï¥³¥ó¥Ñ¥¤¥ë¤Ë gcc ¤¬É¬ÍפǤ¹)¡§
-<P>°ìÈÌŪ¤Ë¡¢ºÇ¶á¤ÎUnix¸ß´¹¥×¥é¥Ã¥È¥Û¡¼¥à¤Ê¤é¤ÐPostgreSQL¤ò¤Ï¤·¤é¤»¤é¤ì¤ë¤Ï¤º¤Ç¤¹¡£¥ê¥ê¡¼¥¹¤Î»þÅÀ¤Ç¼ÂºÝ¤Ë¥Æ¥¹¥È¤ò¹Ô¤Ê¤Ã¤¿¤³¤È¤ÎÊó¹ð¤¬¤Ê¤µ¤ì¤¿¥×¥é¥Ã¥È¥Û¡¼¥à¤Ë¤Ä¤¤¤Æ¤Ï¥¤¥ó¥¹¥È¡¼¥ë¼ê°ú½ñ¤ËÎóµó¤·¤Æ¤¢¤ê¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="1.4">1.4</A>)	Unix°Ê³°¤Î°Ü¿¢ÈǤǻȤ¨¤ë¤â¤Î¤Ï¡©</H4>
-
-<h6>
-¥¯¥é¥¤¥¢¥ó¥È</h6>
-<P> MS Windows ¥×¥é¥Ã¥È¥Û¡¼¥à¾å¤Ç¡¢<I>libpq</I> C ¥é¥¤¥Ö¥é¥ê¡¢psql¡¢¤½¤ì¤È¤½¤Î¾¤Î¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Ï ¥³¥ó¥Ñ¥¤¥ë²Äǽ¤Ç¡¢¥Ð¥¤¥Ê¥ê¡¼¤¬Áö¤ê¤Þ¤¹¡£¤³¤Î¾ì¹ç¡¢¥¯¥é¥¤¥¢¥ó¥È¤ò MS Windows ¾å¤ÇÁö¤é¤»¤Æ¡¢TCP/IP ·Ðͳ¤Ç¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë Unix ¥×¥é¥Ã¥È¥Û¡¼¥à¾å¤ÇÁö¤ë¥µ¡¼¥Ð¤ÈÄÌ¿®¤·¤Þ¤¹¡£
-<P> Win32 <I>libpq</I> ¥é¥¤¥Ö¥é¥ê¤È psql ¤òºî¤ë¤¿¤á¤Ë¡¢<I>win31.mak</I> ¤¬ÇÛÉۤ˴ޤޤì¤Æ¤Þ¤¹¡£PostgreSQL¤Ï <small>ODBC</small> ¥¯¥é¥¤¥¢¥ó¥È¤È¤âÄÌ¿®¤Ç¤­¤Þ¤¹¡£
-
-<h6>
-¥µ¡¼¥Ð</h6>
-<P> ¸½ºß¡¢Cygnus Unix/NT °Ü¿¢¥é¥¤¥Ö¥é¥ê¤Î Cygwin ¤ò»È¤Ã¤Æ¡¢PostgreSQL ¥Ç¡¼¥¿¥Ù¡¼¥¹¥µ¡¼¥Ð¤Ï Windows NT ¤È Win2k ¾å¤Ç²ÔƯ¤·¤Æ¤¤¤Þ¤¹¡£ÇÛÉۤ˴ޤޤì¤ë<I>pgsql/doc/FAQ_MSWIN</I>¤¢¤ë¤¤¤Ï¥¦¥§¥Ö¥µ¥¤¥È¤Ë¤¢¤ë MS Windows FAQ ¤ò¤´Í÷²¼¤µ¤¤¡£Microsoft ¤ÎÁǤΥץé¥Ã¥È¥Û¡¼¥à¤Ë°Ü¿¢¤¹¤ë·×²è¤Ï¤¢¤ê¤Þ¤»¤ó¡£<P>
-
-<br>
-[ÌõÃí¡§
-<br>
-<h6><font color="orange">
-Win32¥Í¥¤¥Æ¥£¡¼¥ÖÈÇ(Win32 Native version)
-</font></h6>
-<pre>
-	  Windows-Native ¥µ¡¼¥Ð¡¼ & ¥¯¥é¥¤¥¢¥ó¥È¥Ñ¥Ã¥±¡¼¥¸¤¬ÀÆÆ£¤µ¤ó¤Ë¤è¤ê
-	°Ý»ý´ÉÍý¤µ¤ì¤Æ¤¤¤Þ¤¹¡£
-	    <a href="http://hp.vector.co.jp/authors/VA023283/PostgreSQL.html">http://hp.vector.co.jp/authors/VA023283/PostgreSQL.html</a>
-	(Windows-Native Server&Client Package for PostgreSQL by Hiroshi Saito)
-	    <a href="http://hp.vector.co.jp/authors/VA023283/PostgreSQLe.html">http://hp.vector.co.jp/authors/VA023283/PostgreSQLe.html</a>
-
-</pre>
-<br>
-]
-<br>
-
-
-<P>
-<H4><A NAME="1.5">1.5</A>)	PostgreSQL ¤Ï¤É¤³¤«¤éÆþ¼ê¤Ç¤­¤Þ¤¹¤«¡©</H4>
-<P> PostgreSQL ¤Î¸µ¤Î anonymous ftp ¥µ¥¤¥È¤Ç¤¹¡§
-
-<UL>
-	<LI>	<A HREF="ftp://ftp.PostgreSQL.org/pub/">ftp://ftp.PostgreSQL.org/pub/</A>
-</UL>
-
-<P> ¥ß¥é¡¼¥µ¥¤¥È¤Ë¤Ä¤¤¤Æ¤Ï¡¢²æ¡¹¤Î¥á¥¤¥ó Web ¥Ú¡¼¥¸¤ò¤´Í÷²¼¤µ¤¤¡£
-
-<small><PRE>
-    [ÌõÃí:
-
-	°Ê²¼¤ÏÆüËܤΥߥ顼¥µ¥¤¥È¤Ç¤¹:
-
-       Japan: <A HREF="ftp://mirror.nucba.ac.jp/mirror/postgresql/pub/">ftp://mirror.nucba.ac.jp/mirror/postgresql/pub/</A>
-       Japan: <A HREF="ftp://ring.ip-kyoto.ad.jp/pub/misc/db/postgresql/">ftp://ring.ip-kyoto.ad.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.crl.go.jp/pub/misc/db/postgresql/">ftp://ring.crl.go.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.saitama-u.ac.jp/pub/misc/db/postgresql/">ftp://ring.saitama-u.ac.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.astem.or.jp/pub/misc/db/postgresql/">ftp://ring.astem.or.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.exp.fujixerox.co.jp/pub/misc/db/postgresql/">ftp://ring.exp.fujixerox.co.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.jah.ne.jp/pub/misc/db/postgresql/">ftp://ring.jah.ne.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.etl.go.jp.jp/pub/misc/db/postgresql/">ftp://ring.etl.go.jp.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.asahi-net.or.jp/pub/misc/db/postgresql/">ftp://ring.asahi-net.or.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.so-net.ne.jp/pub/misc/db/postgresql/">ftp://ring.so-net.ne.jp/pub/misc/db/postgresql/</A>
-       Japan: <A HREF="ftp://ring.aist.go.jp/pub/misc/db/postgresql/">ftp://ring.aist.go.jp/pub/misc/db/postgresql/</A>
-    ]
-</PRE></small>
-
-<P>
-
-<H4><A NAME="1.6">1.6</A>)	¥µ¥Ý¡¼¥È¤Ï¤É¤³¤Ç¼õ¤±¤é¤ì¤Þ¤¹¤«¡©</H4>
-
-<P> ¼çÍפʥ᡼¥ê¥ó¥°¡¦¥ê¥¹¥È¤Ï: <A HREF="mailto:pgsql-general@PostgreSQL.org">pgsql-general@PostgreSQL.org</A>¤Ç¤¹¡£PostgreSQL ¤Ë´Ø¤¹¤ë¤³¤È¤Ç¤¢¤ì¤ÐµÄÏÀ¤¬¤Ç¤­¤Þ¤¹¡£¤³¤Î¥ê¥¹¥È¤Ø¤Î»²²Ã¤Î¤Ï¡¢ÅŻҥ᡼¥ë¤ÎËÜʸ(Subject ¹Ô¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó)¤Ë¼¡¤Î£²¹Ô¤ò½ñ¤¤¤Æ¡¢
-
-<PRE>
-	subscribe
-	end
-</PRE>
-
-<P> <A HREF="mailto:pgsql-general-request@PostgreSQL.org">pgsql-general-request@PostgreSQL.org</A> ¤ØÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
-
-<P> ¥À¥¤¥¸¥§¥¹¥ÈÈǤΥ᡼¥ê¥ó¥°¡¦¥ê¥¹¥È¤â¤¢¤ê¤Þ¤¹¡£¤³¤Î¥ê¥¹¥È¤Ø¤Î»²²Ã¤Ï "ËÜʸ"¤Ë¡§
-
-<PRE>
-	subscribe
-	end
-</PRE>
-
-¤È½ñ¤¤¤Æ <A HREF="mailto:pgsql-general-digest-request@PostgreSQL.org"> pgsql-general-digest-request@PostgreSQL.org</A> ¤ØÅŻҥ᡼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
-
-<P> ¥À¥¤¥¸¥§¥¹¥ÈÈǤϡ¢¥á¥¤¥ó¥ê¥¹¥È¤Ç¼õ¿®¤¹¤ë¥á¥Ã¥»¡¼¥¸¤¬ 30k ÄøÅÙί¤ëËè¤Ë¥À¥¤¥¸¥§¥¹¥ÈÈǥꥹ¥È¤Î¥á¥ó¥Ð¡¼¤ËÁ÷ÉÕ¤µ¤ì¤Þ¤¹¡£
-
-<P> ¥Ð¥°¥ì¥Ý¡¼¥ÈÍѤΥ᡼¥ê¥ó¥°¥ê¥¹¥È¤â¤¢¤ê¤Þ¤¹¡£¤³¤Î¥ê¥¹¥È¤Ø¤Î»²²Ã¤Ï "ËÜʸ"¤È¤¤¤Ã¤·¤ç¤Ë¡§
-<A
-HREF="mailto:bugs-request@PostgreSQL.org">bugs-request@PostgreSQL.org</A>
-
-¤ØÅŻҥ᡼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
-
-<P> ³«È¯¼Ô¤ÎµÄÏÀ¤Î¤¿¤á¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤âÍøÍѤǤ­¤Þ¤¹¡£¤³¤Î¥ê¥¹¥È¤Ø¤Î»²²Ã¤ÏÅŻҥ᡼¥ë¤ÎËÜʸ¤Ë¡§
-
-<P>
-<PRE>
-	subscribe
-	end
-</PRE>
-
-<P> ¤È½ñ¤¤¤Æ¡¢<A HREF="mailto:pgsql-hackers-request@PostgreSQL.org">pgsql-hackers-request@PostgreSQL.org</A>¤ØÅŻҥ᡼¥ë¤òÁ÷¤Ã¤Æ²¼¤µ¤¤¡£
-
-<P> PostgreSQL ¤Ë¤Ä¤¤¤Æ¤â¤Ã¤È¾Ü¤·¤¯ÃΤꤿ¤±¤ì¤Ð¡¢¼¡¤Î postgreSQL WWW¥Û¡¼¥à¥Ú¡¼¥¸¤«¤é¤¿¤É¤ì¤Þ¤¹¡§
-
-<BLOCKQUOTE>
-		<A HREF="http://www.PostgreSQL.org">http://www.PostgreSQL.org</A>
-</BLOCKQUOTE>
-<P>
-
- EFNet ¤Ë <I>#PostgreSQL</I> ¤È¤¤¤¦ IRC ¥Á¥ã¥ó¥Í¥ë¤â¤¢¤ê¤Þ¤¹¡£
-UNIX ¥³¥Þ¥ó¥É¤Ç<tt>irc -c '#PostgreSQL' "$USER" <A HREF="http://irc.phoenix.net">irc.phoenix.net</A> ¤ò»È¤¤¤Þ¤¹¡£<P>
-
-<small><PRE>
-    [ÌõÃí:
-	  1999ǯ7·î23Æü¡¢ÆüËÜPostgreSQL¥æ¡¼¥¶¡¼²ñ(¤Ë¤Û¤ó ¤Ý¤¹¤È¤°¤ì¤¹ ¤æ¡¼¤¶¡¼ ¤«¤¤)¡¢Î¬¾ÎJPUG¤¬ÀßΩ¤µ¤ì¤Þ¤·¤¿¡£
-	JPUG ¤ÏÈó±ÄÍøÁÈ¿¥¤Ç¡¢PostgreSQL¤òÍøÍѤ¹¤ë¿Íã¤ÎÁê¸ß¶¨ÎϤξì¤Ç¤¹¡£
-	Àµ²ñ°÷¤Î²ñÈñ¤Ï̵ÎÁ¤Ç¤¹¤¬¡¢¶¨»¿²ñ°÷¤Î²ñÈñ¤È²ñ°÷¤ÎÀѶËŪ¤Ê¹×¸¥¤¬²ñ¤Î±¿±Ä¤ò½õ¤±¤Æ¤¤¤Þ¤¹¡£
-	¾Ü¤·¤¯¤Ï¡¢JPUG ¤ÎWeb ¥µ¥¤¥È:
-		<A HREF="http://www.postgresql.jp/">http://www.postgresql.jp/</A>
-	¤ò¤´Í÷¤¯¤À¤µ¤¤¡£²ñ°÷ÅÐÏ¿¤â²Äǽ¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
-	  1990ǯÂåÃ椴¤í¤è¤ê¡¢¥Ý¥¹¥È¥°¥ì¥¹¤ÎÆüËܸì¥á¡¼¥ê¥ó¥°¡¦¥ê¥¹¥È¤òÀаæ ãÉפµ¤ó¤¬¼çºÅ¤·¤Æ¤¤¤Þ¤¹¡£¾ÜºÙ¤Ï¡¢
-		<A HREF="http://www.sra.co.jp/people/t-ishii/PostgreSQL/ML/info.html">http://www.sra.co.jp/people/t-ishii/PostgreSQL/ML/info.html</A>
-	¤ò¤´Í÷²¼¤µ¤¤¡£¥¢¡¼¥«¥¤¥Ö¤ò¡¢¤¤¤ï¤­¤ê¤µ¤ó¤Îpgsql-jp ML¸¡º÷¥·¥¹¥Æ¥à
-		<A HREF="http://datula.mio.org/~iwakiri/pgsql_jp/">http://datula.mio.org/~iwakiri/pgsql_jp/</A>
-	¤Ç¸¡º÷¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
-	]
-</PRE></small>
-
-
-<P>¾¦ÍÑ¥µ¥Ý¡¼¥È²ñ¼Ò¤Î¥ê¥¹¥È¤Ï<a href="http://www.postgresql.org/users-lounge/commercial-support.html">http://www.postgresql.org/users-lounge/commercial-support.html</a>¤Ë¤¢¤ê¤Þ¤¹¡£
-
-<small><PRE>
-    [ÌõÃí:
-	 ÆüËܤǤϡ¢<A HREF="http://osb.sra.co.jp/">SRA Inc. ¥ª¡¼¥×¥ó¥·¥¹¥Æ¥à»ö¶ÈÉô</A> ¤Ë¤Æ¾¦ÍÑ¥µ¥Ý¡¼¥È¤¬¹Ô¤Ê¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
-	<A HREF="http://www.miraclelinux.co.jp/">¥ß¥é¥¯¥ë¡¦¥ê¥Ê¥Ã¥¯¥¹³ô¼°²ñ¼Ò</A> ¤Ç "Miracle Linux for PostgreSQL" ¤ÎÈÎÇä¤È¥µ¥Ý¡¼¥È¤¬
-	³«»Ï¤µ¤ì¤Þ¤·¤¿¡£
-    ]
-</PRE></small>
-
-<P>
-
-<H4><A NAME="1.7">1.7</A>)	ºÇ¿·ÈǤϤɤì¤Ç¤¹¤«</H4>
-
-<P> PostgreSQL ¤ÎºÇ¿·ÈǤϥС¼¥¸¥ç¥ó 7.2.1 ¤Ç¤¹¡£
-<P>
-²æ¡¹¤Ï¡¢4¥«·îËè¤Ë¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤ò¹Ô¤Ê¤¦¤³¤È¤ò·×²è¤·¤Æ¤¤¤Þ¤¹¡£
-<P>
-
-<H4><A NAME="1.8">1.8</A>)	¤É¤Î¤è¤¦¤Êʸ½ñ¤¬¤¢¤ê¤Þ¤¹¤«¡©</H4>
-
-<P> ÇÛÉÕ¤ÎÃæ¤Ë¡¢¤¤¤¯¤Ä¤«¤Î¥Þ¥Ë¥å¥¢¥ë¤È¥ª¥ó¥é¥¤¥ó¡¦¥Þ¥Ë¥å¥¢¥ë(¥Þ¥Ë¥å¥¢¥ë¡¦¥Ú¡¼¥¸)¤ª¤è¤Ó¤¤¤¯¤Ä¤«¤Î¾®¤µ¤Ê¥Æ¥¹¥ÈÎãÂ꤬´Þ¤Þ¤ì¤Þ¤¹¡£<I>/doc</I> ¥Ç¥£¥ì¥¯¥È¥ê¤ò¤´Í÷²¼¤µ¤¤¡£¤Þ¤¿¡¢¥Þ¥Ë¥å¥¢¥ë¤Ï¡¢<A
-HREF="http://www.PostgreSQL.org/users-lounge/docs/">
-http://www.PostgreSQL.org/users-lounge/docs/</A>
-¤Ç¥ª¥ó¥é¥¤¥ó¤Ç¤â±ÜÍ÷¤Ç¤­¤Þ¤¹¡£
-
-<small><PRE>
-    [ÌõÃí:
-	¡Ê³ô¡ËSRA¤ÈÆüËܥݥ¹¥È¥°¥ì¥¹¥æ¡¼¥¶¡¼²ñ¤ÇËÝÌõ¤µ¤ì¡¢
-	<A HREF="http://osb.sra.co.jp/PostgreSQL/Manual/">¡ÖPostgreSQL ¥ª¥Õ¥£¥·¥ã¥ë¥Þ¥Ë¥å¥¢¥ë¡×</A>
-	¤È¤·¤Æ½ÐÈǤµ¤ì¤Æ¤¤¤Þ¤¹¡£
-    ]
-</PRE></small>
-
-
-<P>  ¥ª¥ó¥é¥¤¥ó¤Ç»²¾È¤Ç¤­¤ë PostgreSQL ¤ÎËܤâ2ºý¤¢¤ê¤Þ¤¹¡£<A href=
-    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
-<small><PRE>
-    [ÌõÃí:
-	ÆüËܥݥ¹¥È¥°¥ì¥¹¥æ¡¼¥¶¡¼²ñ¤Î<A HREF="http://www.postgresql.jp/subcommittee/psqltrans/">	¡ÖPostgreSQL BookËÝÌõʬ²Ê²ñ¡×</A>
-	¤Ë¤ÆËÝÌõ¤µ¤ì¤Þ¤·¤¿¡£
-    ]
-</PRE></small>
-
-    ¤ª¤è¤Ó¡¢ <A href=
-    "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook/</A>
-¤Ç¤¹¡£
-  
-
-    ¹ØÆþ²Äǽ¤Ê½ñÀÒ¤ÎÌÜÏ¿¤Ï¡¢<A href=
-    "http://www.postgresql.org/books/">http://www.postgresql.org/books/</A>
-    ¤Ë¤¢¤ê¤Þ¤¹¡£
-
-    PostgreSQL µ»½Ñ¾ðÊóµ­»ö¤â¡¢<A href=
-    "http://techdocs.postgresql.org/">http://techdocs.postgresql.org/</A>
-    ¤Ë¤¢¤ê¤Þ¤¹¡£</P>
-
-
-<P> <I>psql</I> ¤â¡¢·¿¡¢±é»»»Ò¡¢´Ø¿ô¡¢½¸Ì󡢤½¤Î¾¤Î¾ðÊó¤ò¤ª¸«¤»¤¹¤ë¡¢¤¤¤¯¤Ä¤«¤ÎÁÇÀ²¤é¤·¤¤ \d ¥³¥Þ¥ó¥É¤ò»ý¤Á¤Þ¤¹¡£
-
-<P> ²æ¡¹¤Î Web ¥µ¥¤¥È¤Ë¤Ï¡¢¤â¤Ã¤ÈÂô»³¤Îʸ½ñ¤¬¤¢¤ê¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="1.9">1.9</A>)	´ûÃΤΥХ°¤ä̤¤À̵¤¤µ¡Ç½¤Ï¤É¤¦¤ä¤Ã¤Æ¸«¤Ä¤±¤Þ¤¹¤«¡©
-</H4><P>
-
-PostgreSQL¤Ï³ÈÄ¥¤µ¤ì¤¿SQL-92¤Î¥µ¥Ö¥»¥Ã¥È¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£
-²æ¡¹¤Î¥Ú¡¼¥¸¤Î
-<A HREF="http://www.PostgreSQL.org/docs/todo.html">
-TODO</A> ¥ê¥¹¥È¤Ë¡¢´ûÃΤΥХ°¤ä·çÍǽ¤ä¾­Íè·×²è¤Ë¤Ä¤¤¤Æ¤Îµ­½Ò¤¬¤¢¤ê¤Þ¤¹¡£
-
-<P> 
-<H3><A NAME="1.10">1.10</A>)	<small>SQL</small> ¤Ï¤É¤¦¤¹¤ì¤Ð³Ø¤Ù¤Þ¤¹¤«¡©</H3>
-<P>
-<A HREF="http://www.PostgreSQL.org/docs/awbook.html">
-http://www.PostgreSQL.org/docs/awbook.html</A>
-¤Ë¤¢¤ëPostgreSQLËÜ¤Ç <small>SQL</small> ¤ò¶µ¤¨¤Æ¤¤¤Þ¤¹¡£
-
-<small><PRE>
-    [ÌõÃí:
-	ÆüËܥݥ¹¥È¥°¥ì¥¹¥æ¡¼¥¶¡¼²ñ¤Î<A HREF="http://www.postgresql.jp/subcommittee/psqltrans/">	¡ÖPostgreSQL BookËÝÌõʬ²Ê²ñ¡×</A>
-	¤Ë¤ÆËÝÌõ¤µ¤ì½ÐÈǤµ¤ì¤Æ¤¤¤Þ¤¹¡£
-    ]
-</PRE></small>
-
-<P>
-¤½¤Î¾¤Ë¤â PostgreSQLËܤȤ·¤Æ¡¢<A href=
-    "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook</A>
-¤¬¤¢¤ê¤Þ¤¹¡£
-
-ÁÇÀ²¤é¤·¤¤¼ê°ú½ñ¤Ï¡¢<A href=
-    "http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A>
-    <A href=
-    "http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM">
-    http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM,</A>
-    ¤½¤·¤Æ¡¢<A href=
-    "http://sqlcourse.com/">http://sqlcourse.com</A>
-¤Ë¤¢¤ê¤Þ¤¹¡£</P>
-
-
-    <P>¤½¤Î¾¤Ç¤Ï¡¢ "Teach Yourself SQL in 21 Days, Second Edition" ¤¬ <A href=
-    "http://members.tripod.com/er4ebus/sql/index.htm">http://members.tripod.com/er4ebus/sql/index.htm</A>¤Ë¤¢¤ê¤Þ¤¹¡£</P>
-
-<P>
-¿¤¯¤Î¥æ¡¼¥¶¤Ë¡¢
-<I>The Practical SQL Handbook</I>, Bowman Judith S. et al., Addison-Wesley
-¤¬¹¥É¾¤Ç¤¹¡£
-¤½¤Î¾¤Ë¡¢<I>The Complete Reference SQL</I>, Groff et al., McGraw-Hill 
-¤Î¤è¤¦¤Ê¤Î¤â¤¢¤ê¤Þ¤¹¡£
-</P>
-
-<P>
-<small><PRE>
-    [ÌõÃí:
-	 ÀаæãÉ×»á¤Ë¤è¤ëÆüËܸì¤Î»²¹Íʸ¸¥¤Î¾Ò²ð¥Ú¡¼¥¸
-		<A HREF="http://www.SRA.co.jp/people/t-ishii/PostgreSQL/doc-jp/index.html">http://www.SRA.co.jp/people/t-ishii/PostgreSQL/doc-jp/index.html</A>
-	¤¬¤¢¤ê¤Þ¤¹¡£
-	 ¶áƣľʸ»á¤Î¡Ö½é¿´¼Ô¸þ¤Î£Ä£ÂÀß·×ÆþÌ硦£Ó£Ñ£ÌÆþÌ绲¹Í½ñ¾Ò²ð¡×¤Î¥³¡¼¥Ê¡¼
-		<A HREF="http://www.shonan.ne.jp/~nkon/ipsql/books_SQL.html">http://www.shonan.ne.jp/~nkon/ipsql/books_SQL.html</A>
-	¤¬¤¢¤ê¤Þ¤¹¡£
-	 ËÙÅÄÎѱѻá¤Î¡ÖPostgreSQLÆüËܸì¥Þ¥Ë¥å¥¢¥ë¡×
-		<A HREF="http://www.net-newbie.com/">http://www.net-newbie.com/</A>
-	¤Ç¤Ï¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Î¸¡º÷¤¬¤Ç¤­¤Þ¤¹¡£
-	 ´Ý»³ÉÔÆóÉ×»á¤ÎUNIX ¥Ç¡¼¥¿¥Ù¡¼¥¹ÆþÌç
-		<A HREF="http://www.wakhok.ac.jp/DB/DB.html">http://www.wakhok.ac.jp/DB/DB.html</A>
-	¤â¥ª¥ó¥é¥¤¥ó¤ÇÆɤळ¤È¤¬¤Ç¤­¤Þ¤¹¡£
-    ]
-</PRE></small>
-
-<H4><A NAME="1.11">1.11</A>)	PostgreSQL¤ÏÀ¾Îñ2000ǯÌäÂê(Y2K)¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¤«¡©
-</H4><P>
- 
-Âбþ¤·¤Æ¤Þ¤¹¡£À¾Îñ2000ǯ¤è¤ê¸å¤ÎÆüÉդ⡢µª¸µÁ°2000ǯ¤è¤êÁ°¤ÎÆüÉդ⡢´Êñ¤Ë°·¤¨¤Þ¤¹¡£
-<P>
-<H4><A NAME="1.12">1.12</A>)	³«È¯¥Á¡¼¥à¤Ë¤Ï¤É¤Î¤è¤¦¤Ë»²²Ã¤·¤Þ¤¹¤«¡©<BR>
-</H4><P>
-
-¤Þ¤ººÇ½é(£±ÈÖÌÜ)¤Ë¡¢ºÇ¿·¤Î¥½¡¼¥¹¤ò¥À¥¦¥ó¥í¡¼¥É¤·¡¢²æ¡¹¤Î Web ¥µ¥¤¥È¤«ÇÛÉۤ˴ޤޤì¤Æ¤¤¤ë
-PostgreSQL Developers¤Îʸ½ñ¤òÆɤߤޤ¹¡£
-£²ÈÖÌܤˡ¢<I>pgsql-hackers</I> ¤È <I>pgsql-patches</I> ¥á¡¼¥ê¥ó¥°¡¦¥ê¥¹¥È¤ò¹ØÆÉ(subscribe)¤·¤Þ¤¹¡£
-£³ÈÖÌܤˡ¢¹âÉʼÁ¤Î¥Ñ¥Ã¥Á¤òpgsql-patches¤Ëȯ¿®¤·¤Þ¤¹¡£
-
-¤ª¤è¤½½½¿Í¤Á¤ç¤Ã¤È¤Î¿Í㤬¡¢PostgreSQL <small>CVS</small>¥¢¡¼¥«¥¤¥Ö¤Ë¥³¥ß¥Ã¥È¤¹¤ë¸¢¸Â¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£
-¤½¤Î¤½¤ì¤¾¤ì¤Î¿Í㤬Âô»³¤Î¹âÉʼÁ¤Ê¥Ñ¥Ã¥Á¤òȯ¿®¤¹¤ë¤Î¤Ç¡¢¸½ºß¥³¥ß¥Ã¥¿¡¼¤È¤Ê¤Ã¤Æ¤¤¤ë¿Íã¤Ï¤½¤ì¤ËÄɤ¤ÉÕ¤¯¤Î¤¬ÂçÊѤǤ¹¤¬¡¢²æ¡¹¤ÏÈà¤é¤¬¥³¥ß¥Ã¥È¤·¤¿¥Ñ¥Ã¥Á¤Ï¹âÉʼÁ¤Ç¤¢¤ë¤È³Î¿®¤·¤Æ¤¤¤Þ¤¹¡£
-<P>
-<H4><A NAME="1.13">1.13</A>)	¥Ð¥°¥ì¥Ý¡¼¥È¤Ï¤É¤Î¤è¤¦¤Ëȯ¿®¤·¤Þ¤¹¤«¡©
-</H4>
-
-    <P>¥Ð¥°¤òÊó¹ð¤¹¤ë»ÅÊý¤Ë¤Ä¤¤¤Æ¤Î¥¬¥¤¥É¥é¥¤¥ó¤ÈÊý¸þ¤Å¤±¤¬¤¢¤ë<A href=
-    "http://www.postgresql.org/bugs/bugs.php">PostgreSQL BugTool</A>
-    (¥Ð¥°¥Ä¡¼¥ë)¤Î¥Ú¡¼¥¸¤òˬ¤ì¤Æ¤ß¤Æ²¼¤µ¤¤¡£ </P>
-
-<P> ¤½¤ÎÁ°¤Ë <A HREF="http://postgreSQL.org">http://postgreSQL.org</A>¤Ë¤¢¤ëºÇ¿·¤Î FAQ ¤ò¥Á¥§¥Ã¥¯¤·¤Æ²¼¤µ¤¤¡£
-
-<P> ¤½¤ì¤ÈƱ»þ¤Ë ftp ¥µ¥¤¥È <A HREF="ftp://ftp.postgreSQL.org/pub/">ftp://ftp.postgreSQL.org/pub/</A>¤Ç¡¢¤â¤Ã¤È¿·¤·¤¤¥Ð¡¼¥¸¥ç¥ó¤Î PostgreSQL ¤¢¤ë¤¤¤Ï¥Ñ¥Ã¥Á¤ò¤µ¤¬¤·¤Æ¤ß¤Æ²¼¤µ¤¤¡£
-
-<P>
-<H4><A NAME="1.14">1.14</A>)	¾¤Î<small>DBMS</small>¤Î¤ÈÈæ¤Ù¤ÆPostgreSQL¤Ï¤É¤¦¤Ê¤Î¤Ç¤¹¤«¡©
-</H4><P>
-
-¥½¥Õ¥È¥¦¥§¥¢¤ò·×¤ëÊýË¡¤Ë¤Ï¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹¡£µ¡Ç½¤ÈÀ­Ç½¤È¿®ÍêÀ­¤È¥µ¥Ý¡¼¥È¤È²Á³Ê¤Ç¤¹¡£
-
-<DL>
-<DT> <B>µ¡Ç½(Features)</B>
-<DD>
-PostgreSQL¤Ï¡¢¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¡¢ÉûÌ䤤¹ç¤ï¤»¡¢¥È¥ê¥¬¡¼¡¢¥Ó¥å¡¼¡¢³°Éô¥­¡¼
-À°¹çÀ­»²¾È¡¢¤ª¤è¤Ó¡¢ÀöÎý¤µ¤ì¤¿¥í¥Ã¥¯µ¡¹½¤Ê¤É¡¢Â絬ÌϾ¦ÍÑ<small>
-DBMS</small>¤¬»ý¤Äµ¡Ç½¤ò¤Û¤È¤ó¤É»ý¤Ã¤Æ¤¤¤Þ¤¹¡£¤µ¤é¤Ë PostgreSQL¤Ï¡¢¥æ¡¼¥¶
-ÄêµÁ·¿¡¢·Ñ¾µ¡¢¥ë¡¼¥ë¡¢¤½¤ì¤«¤é¡¢¥í¥Ã¥¯¶¥¹ç¤ò½Ì¾®¤¹¤ë¥Þ¥ë¥Á¥Ð¡¼¥¸¥ç¥óƱ»þ
-À­À©¸æ¤Ê¤É¡¢¾¦ÍÑ<small>DBMS</small>¤â»ý¤Á¹ç¤ï¤»¤Ê¤¤¤è¤¦¤Êµ¡Ç½¤ò¤¤
-¤¯¤Ä¤«»ý¤Á¹ç¤ï¤»¤Æ¤¤¤Þ¤¹¡£<BR>
-<BR>
-
-<DT> <B>À­Ç½(Performance)</B>
-<DD>
-
-PostgreSQL¤ÏÆó¤Ä¤Î¥â¡¼¥É¤ÇÁö¤ê¤Þ¤¹¡£ÉáÄ̤Î<I>fsync</I>¥â¡¼¥É¤Ï¡¢OS¤¬¥¯
-¥é¥Ã¥·¥å¤·¤¿¤ê¡¢¿ôÉøå¤ËÅŸ»¤¬Íî¤Á¤¿¤ê¤·¤¿¤È¤­¤Î¤¿¤á¤Ë¡¢¥È¥é¥ó¥¶¥¯¥·¥ç
-¥ó¤¬´°Î»¤¹¤ëËè¤Ë¥Ç¥£¥¹¥¯¤Ë½ñ¤­¹þ¤ß¡¢¤¹¤Ù¤Æ¤Î¥Ç¡¼¥¿¤ò¥Ç¥£¥¹¥¯¤ËÊݸ¤·¤Þ
-¤¹¡£¤³¤Î¥â¡¼¥É¤Ç¤Ï¡¢¤Û¤È¤ó¤É¤Î¾¦Íѥǡ¼¥¿¥Ù¡¼¥¹¤è¤ê¤âÃÙ¤¯¤Ê¤ê¤Þ¤¹¤¬¡¢¤½
-¤ÎÉôʬŪ¤ÊÍýͳ¤È¤·¤Æ¡¢¾¦ÍѤΥǡ¼¥¿¥Ù¡¼¥¹¤ÎÃæ¤Ë¤Ï¤³¤Î¤è¤¦¤ËÊݼéŪ¤Ê¥Ç¥£
-¥¹¥¯½ñ¤­¹þ¤ß¤ò¥Ç¥Õ¥©¥ë¥È¤È¤·¤Æ¤¤¤ë¤â¤Î¤¬¾¯¤Ê¤¤¤È¤¤¤¦¤³¤È¤â¤¢¤ê¤Þ¤¹¡£
-<I>no-fsync</I>¥â¡¼¥É¤Ç¡¢ÉáÄÌ¡¢PostgreSQL¤Ï¾¦Íѥǡ¼¥¿¥Ù¡¼¥¹¤è¤ê¤â®¤¯
-¤Ê¤ê¤Þ¤¹¤¬¡¢¤·¤«¤·¤Ê¤¬¤é¡¢OS¤Î¥¯¥é¥Ã¥·¥å¤Ç¥Ç¡¼¥¿¤¬Ç˲õ¤µ¤ì¤ë¤«¤â¤·¤ì¤Þ
-¤»¤ó¡£²æ¡¹¤Ï¡¢¤½¤ÎÃæ´Ö¥â¡¼¥É¤ò³«È¯Ãæ¤Ç¡¢¤½¤ì¤¬¤¦¤Þ¤¯¤æ¤¯¤È¡¢´°Á´fsync
-¥â¡¼¥É¤Û¤ÉÀ­Ç½¤òµ¾À·¤Ë¤¹¤ë¤³¤È¤Ê¤¯¡¢OS¤¬¥¯¥é¥Ã¥·¥å¤¹¤ë30ÉÃÁ°¤Þ¤Ç¤Î¥Ç¡¼
-¥¿À°¹çÀ­¤òÊݤƤë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
-<BR><BR>
-
-MySQL¤Ê¤É¤ÎÆò½·¿¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥·¥¹¥Æ¥à¤Ë¤¯¤é¤Ù¤Æ¡¢PostgreSQL¤ÎÁÞÆþ¡¿
-¹¹¿·¤¬ÃÙ¤¤¤Î¤Ï¡¢¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤Ë¤è¤ë¥ª¡¼¥Ð¡¼¥Ø¥Ã¥É¤¬¤¢¤ë¤«¤é¤Ç¤¹¡£¤â
-¤Á¤í¤ó¡¢MySQL¤Ë¤Ï¾åµ­¤Î<I>Features</I>¤ÎÀá¤Ë¼¨¤¹¤è¤¦¤Êµ¡Ç½¤Ï¤Þ¤Ã¤¿¤¯¤¢
-¤ê¤Þ¤»¤ó¡£²æ¡¹¤Ï¡¢PostgreSQL¤Ë½ÀÆðÀ­¤Èµ¡Ç½À­¤òÁȤ߹þ¤ß¤Ê¤¬¤é¤â¡¢À䤨¤º¡¢
-¥×¥í¥Õ¥¡¥¤¥é¡¼¤Ë³Ý¤±¤¿¤ê¥½¡¼¥¹¥³¡¼¥É¤ò²òÀϤ·¤¿¤ê¤·¤Æ¡¢À­Ç½¤Î²þÁ±¤ò³¤±
-¤Æ¤¤¤Þ¤¹¡£PostgreSQL ¤È MySQL ¤È¤òÈæ³Ó¤·¤Æ¤¤¤ëÌÌÇò¤¤ Web ¥Ú¡¼¥¸¤¬
-<a href="http://openacs.org/why-not-mysql.html">
-http://openacs.org/why-not-mysql.html</a>
-¤Ë¤¢¤ê¤Þ¤¹¡£
-<BR><BR>
-
-PostgreSQL¤Ï¡¢Unix¥×¥í¥»¥¹¤òµ¯Æ°¤¹¤ë¤³¤È¤Ë¤è¤ê¥æ¡¼¥¶¡¼Àܳ¤òÁàºî¤·¤Þ¤¹¡£
-Ê£¿ô¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¡¦¥×¥í¥»¥¹¤¬¾ðÊó¤ò¥í¥Ã¥¯¤·¤Ê¤¬¤é¥Ç¡¼¥¿¡¦¥Ð¥Ã¥Õ¥¡¡¼¤ò
-¶¦Í­¤·¤Þ¤¹¡£¥Þ¥ë¥ÁCPU¤Ç¤Ï¡¢´Êñ¤ËÊ£¿ô¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¤ò¤½¤ì¤¾¤ì¤ÎCPU¤ÇÁö
-¤é¤»¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£<BR><BR>
-
-
-<DT> <B>¿®ÍêÀ­(Reliability)</B>
-<DD>
-
-²æ¡¹¤Ï¡¢<small>DBMS</small>¤Î¿®ÍêÀ­¤¬¹â¤¯¤Ê¤¯¤Æ¤Ï¤½¤Î²ÁÃͤ¬Ìµ¤¤¤³¤È¤òÍý²ò¤·¤Æ¤Þ¤¹¡£½½
-ʬ¥Æ¥¹¥È¤·¤Æ¡¢°ÂÄꤷ¤¿¥³¡¼¥É¤ò¥Ð¥°¤òºÇ¾®¤Ë¤·¤Æ¤«¤é¥ê¥ê¡¼¥¹¤¹¤ë¤è¤¦¤Ë¶Ð
-¤á¤Æ¤Þ¤¹¡£¤½¤ì¤¾¤ì¤Î¥ê¥ê¡¼¥¹¤Ï¾¯¤Ê¤¯¤È¤â1¥«·î°Ê¾å¤Î¥Ù¡¼¥¿¡¦¥Æ¥¹¥È¤ò¹Ô
-¤Ê¤¤¡¢¤³¤ì¤Þ¤Ç¤Î¥ê¥ê¡¼¥¹¤ÎÍúÎò¤¬¡¢À½ÉÊÈǤȤ·¤Æ°ÂÄꤷ¤¿·ø¸Ç¤Ê¥ê¥ê¡¼¥¹¤Ç
-¤¢¤ë¤³¤È¤òʪ¸ì¤Ã¤Æ¤¤¤Þ¤¹¡£¤³¤ÎʬÌî¤Ç¤Ï¡¢Â¾¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÈÈæ¤Ù¤Æ¤â½¿§
-¤¬¤Ê¤¤¤³¤È¤Ë¼«¿®¤ò»ý¤Ã¤Æ¤¤¤Þ¤¹¡£
-
-<DT> <B>¥µ¥Ý¡¼¥È(Support)</B>
-<DD>
-
-    ²æ¡¹¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ï¡¢Áø¶ø¤¹¤ë¤¤¤«¤Ê¤ëÌäÂê¤Ë¤Ä¤¤¤Æ¤â²ò·è¤Ø¤Î¼ê
-½õ¤±¤ò¤·¤Æ¤¯¤ì¤ë¡¢³«È¯¼Ô¤ä¥æ¡¼¥¶¤ÎÂ礭¤Ê½¸¤Þ¤ê¤òÄ󶡤·¤Æ¤¤¤Þ¤¹¡£²æ¡¹¤Ï
-ÌäÂê¤Î²ò·è¤òÊݾڤ¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤»¤ó¤¬¡¢¾¦Íѥǡ¼¥¿¥Ù¡¼¥¹¤Ç¤¢¤Ã¤Æ¤â¾ï¤Ë
-²ò·è¤µ¤ì¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£³«È¯¼Ô¤ä¡¢¥æ¡¼¥¶¡¦¥³¥ß¥å¥Ë¥Æ¥£¡¢¥Þ¥Ë¥å¥¢
-¥ëÎà¡¢¤½¤ì¤Ë¡¢¥½¡¼¥¹¥³¡¼¥É¤Ê¤É¤ØľÀÜ¥¢¥¯¥»¥¹¤Ç¤­¤ë¤³¤È¤è¤Ã¤Æ¡¢
-PostgreSQL¤Î¥µ¥Ý¡¼¥È¤Ï¡¢Â¾¤Î<small>DBMS</small>¥µ¥Ý¡¼¥È¤è¤ê¤âÍ¥¤ì¤¿¤â¤Î¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£
-¸æÍ×˾¤ËÅú¤¨¤Æ¡¢»öÊÁËè¤Î¾¦ÍÑ¥µ¥Ý¡¼¥È¤Ê¤É¤â¤¢¤ê¤Þ¤¹¡Ê¥µ¥Ý¡¼¥ÈFAQ¹àÌܤò¤´Í÷
-²¼¤µ¤¤¡Ë¡£
-
-<DT> <B>²Á³Ê(Price)</B>
-<DD>
-
-PostgreSQL¤ÎÍøÍѤϡ¢¾¦ÍѤǤâÈó¾¦ÍѤǤ⡢¤¹¤Ù¤Æ̵ÎÁ¤Ç¤¹¡£¾åµ­¤Ë¼¨¤·¤Æ¤¢
-¤ëBSD¥¹¥¿¥¤¥ë¤Î»ÈÍѵöÂú¤Ë³°¤ì¤Ê¤¤¸Â¤ê¡¢PostgreSQL¤Î¥³¡¼¥É¤òÀ©¸Â̵¤·¤Ç
-¾¦ÉʤËÁȤ߹þ¤à¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-<BR><BR>
-</DL>
-<P>
-
-<H4><A name="1.15">1.15</A>) PostgreSQL¤ò»ñ¶âÌ̤DZç½õ¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Ç¤¹¤«¡©
-</H4>
-
-    <P>PostgreSQL¤Ï¡¢²æ¡¹¤¬6ǯÁ°¤Ë»Ï¤á¤¿¤È¤­°ÊÍè¡¢ºÇ¹â¥¯¥é¥¹¤Î´ðÈפò
-»ý¤Ã¤Æ¤¤¤Þ¤¹¡£¤³¤ì¤Ï¤¹¤Ù¤Æ¡¢Marc Fournie¤µ¤ó¤Î¤ª¤«¤²¤Ç¡¢Èà¤Ï¤³¤Î´ðÈ×
-¤ò²¿Ç¯¤Ë¤â¤ï¤¿¤Ã¤ÆÁϤ¤·´ÉÍý¤·¤Æ¤­¤Þ¤·¤¿¡£</P>
-
-    <P>¼Á¤ÎÎɤ¤´ðÈפϥª¡¼¥×¥ó¥½¡¼¥¹¡¦¥×¥í¥¸¥§¥¯¥È¤Ë¤È¤Ã¤Æ¤Ï¤È¤Æ¤âÂçÀÚ¤Ê
-¤â¤Î¤Ç¡¢Á°¿Ê¤¹¤ëÀª¤¤¤ò¼º¤¦¥×¥í¥¸¥§¥¯¥È¤ÎʬÎö¤ò²óÈò¤·¤Þ¤¹¡£
-</P>
-
-    <P>¤â¤Á¤í¤ó¡¢¤³¤Î´ðÈפϰ¤¤¤â¤Î¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£°Ý»ý¤·Â³¤±¤ë¤¿¤á¤Ë¤Ï
-Ëè·î¤¢¤ë¤¤¤Ï°ì»þ¤Î·ÐÈñ¤¬¤«¤«¤ê¤Þ¤¹¡£¤â¤·¡¢¤¢¤Ê¤¿¤ä¤¢¤Ê¤¿¤Î²ñ¼Ò¤Ë¡¢¤³¤¦¤·
-¤¿ÅØÎϤΤ¿¤á¤Î»ñ¶â¤ò½õ¤±¤ë¤¿¤á¤Ë»Ü¤¹¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ç¤·¤¿¤é¡¢<A
-href=
-"http://www.pgsql.com/pg_goodies">http://www.pgsql.com/pg_goodies</A>
-¤«¤é´óÉÕ¤ò¤ª´ê¤¤¤·¤Þ¤¹¡£
-
-    <P>¤Þ¤¿¡¢Web¥Ú¡¼¥¸¤Ë¤Ï PostgreSQL,Inc ¤È¤¢¤ê¤Þ¤¹¤¬¡¢¤½¤³¤Î"µÁ±ç
-(contributions)"¥¢¥¤¥Æ¥à¤Ï PostgreSQL ¥×¥í¥¸¥§¥¯¥È¤ò¥µ¥Ý¡¼¥È¤¹¤ë¤¿¤á¤À¤±
-¤Î¤¿¤á¤Ç¡¢·è¤·¤ÆÆÃÄê¤Î²ñ¼Ò¤Î¤¿¤á¤Î»ñ¶â¤Î¤¿¤á¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤â¤·¡¢¼ê·Á
-(check)¤ÎÊý¤¬ÅԹ礬¤è¤±¤ì¤ÐÏ¢ÍíÀè¤Î½»½ê¤Ø¤ªÁ÷¤ê²¼¤µ¤¤¡£</P>
-
-
-<HR>
-
-<H2><CENTER>¥æ¡¼¥¶¡¼¡¦¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÁÌä</CENTER></H2>
-<P>
-
-<H4><A NAME="2.1">2.1</A>)	PostgreSQL ¤Î¤¿¤á¤Î <small>ODBC</small> ¥É¥é¥¤¥Ð¡¼¤Ï¤¢¤ê¤Þ¤¹¤«¡©
-</H4>
-
-<P> PsqlODBC ¤È OpenLink <small>ODBC</small> ¤ÎÆó¤Ä¤Î <small>ODBC</small> ¥É¥é¥¤¥Ð¡¼¤¬ÍøÍѲÄǽ¤Ç¤¹¡£
-
-<P> PsqlODBC ¤Ï PostgreSQL ¤ÎÇÛÉۤ˴ޤޤì¤Æ¤¤¤Þ¤¹¡£¤½¤ì¤Ë¤Ä¤¤¤Æ¤Î¤µ¤é¤Ë¾ÜºÙ¤Ê¾ðÊó¤Ï 
-<A HREF="ftp://ftp.PostgreSQL.org/pub/odbc/">ftp://ftp.PostgreSQL.org/pub/odbc/</A>
-¤«¤é¼èÆÀ¤Ç¤­¤Þ¤¹¡£<P>
-
-<small><PRE>
-    [ÌõÃí:
-	PsqlODBC ¤Î ÆüËܸì¥Ñ¥Ã¥Á¤òÊÒ²¬ÍµÀ¸¤µ¤ó(kataoka@interwiz.koganei.tokyo.jp)¤¬ºî¤é¤ì¤Þ¤·¤¿:
-	¡ü<A HREF="http://www.interwiz.koganei.tokyo.jp/software/PsqlODBC/index.html">http://www.interwiz.koganei.tokyo.jp/software/PsqlODBC/index.html</A>
-    ]
-</PRE></small>
-
-<P> OpenLink <small>ODBC</small> ¤Ï <A HREF="http://www.openlinksw.com/">http://www.openlinksw.com/</A>¤«¤éÆþ¼ê¤Ç¤­¤Þ¤¹¡£É¸½àŪ¤Ê <small>ODBC</small> ¥¯¥é¥¤¥¢¥ó¥È¡¦¥½¥Õ¥È¥¦¥§¥¢¤Ç»È¤¨¤Þ¤¹¤Î¤Ç¡¢»Ù±ç¤·¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¥×¥é¥Ã¥È¥Û¡¼¥à(Win, Mac, Unix, <STRONG>VMS</STRONG>)¤«¤é PostgreSQL ¤Î <small>ODBC</small> ¤¬ÍøÍѤǤ­¤Þ¤¹¡£
-
-<P> ¤¿¤Ö¤óÈà¤é¤Ï¡¢¾¦ÍÑÉʼÁ¤Î¥µ¥Ý¡¼¥È¤ÎɬÍפʿ͡¹¤ËÇä¤Ã¤Æ¤¤¤ë¤È»×¤¤¤Þ¤¹¤¬¡¢
-    ¥Õ¥ê¡¼¥¦¥§¥¢ÈǤϤ¤¤Ä¤Ç¤âÆþ¼ê²Äǽ¤Î¤è¤¦¤Ç¤¹¡£¼ÁÌä¤Ï¡¢<A href=
-    "mailto:postgres95@openlink.co.uk">postgres95@openlink.co.uk</A>
-    ¤ØÁ÷¤Ã¤Æ²¼¤µ¤¤¡£</P>
-
-<A HREF="http://www.postgresql.org/docs/programmer/odbc.html">
-Programmer's Guide</A>
-¤Î <small>ODBC</small> ¤Î¾Ï¤â¤´Í÷¤¯¤À¤µ¤¤¡£
-
-
-<P>
-<H4><A NAME="2.2">2.2</A>)	PostgreSQL ¤ò Web ¥Ú¡¼¥¸¤ÈÏ¢·È¤µ¤»¤ë¤Ë¤Ï¤É¤ó¤Ê¥Ä¡¼¥ë¤¬¤¢¤ê¤Þ¤¹¤«¡©
-</H4>
-
-<P> ¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò΢¤Ë»ý¤Ä Web ¥Ú¡¼¥¸¤Ë¤Ä¤¤¤Æ¤ÎÁÇÀ²¤é¤·¤¤¾Ò²ð¤¬¡¢<BR>
-    <A href="http://www.webreview.com">http://www.webreview.com</A>¤Ë¤¢¤ê¤Þ¤¹¡£</P>
-<P><A HREF="http://www.phone.net/home/mwm/hotlist/">http://www.phone.net/home/mwm/hotlist/</A>¤Ë¤â¡¢¤â¤¦°ì¤Ä¤¢¤ê¤Þ¤¹¡£
-<P> Web ¤Ø¤Î³ÈÄ¥¤Î¤¿¤á¤Ë¤Ï¡¢PHP ¤¬Âî±Û¤·¤¿¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤È¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£<A HREF="http://www.php.net">http://www.php.net/</A>¤Ë¤¢¤ê¤Þ¤¹¡£
-
-<small><PRE>
-    [ÌõÃí:
-	  PHP¤Ë´Ø¤¹¤ëÆüËܸì¤Î¾ðÊó¤Ï¡¢2000ǯ4·î19Æü¤Ëȯ­¤·¤¿ÆüËÜPHP¥æ¡¼¥¶²ñ¤Î¥µ¥¤¥È
-		<A HREF="http://www.php.gr.jp/">http://www.php.gr.jp/</A>
-	¤¢¤ë¤¤¤Ï¡¢×¢Àî Îव¤ó¤Î¥µ¥¤¥È
-		<A HREF="http://www.geocities.jp/rui_hirokawa/php/">http://www.geocities.jp/rui_hirokawa/php/</A>
-	¤Ë¤«¤Ê¤ê¤Þ¤È¤á¤é¤ì¤Æ¤¤¤Þ¤¹¡£
-	  Á°ÅÄ ½¼¹¨¤µ¤ó¤Ë¤è¤êºî¤é¤ì¤¿<A HREF="http://pg.cni.co.jp/">PHP/FI¤ÎÆüËܸì¥Ñ¥Ã¥Á</A>¤¬ÍÍ¡¹¤Ê¿Í¤Î¼ê¤ò·Ð¤ÆPHP3.0.7¤ËŬÍѤµ¤ì¤Þ¤·¤¿¡£
-	¸½ºß¤ÏPHPJ-DEV¤Ë¤Æ¡¢
-		<A HREF="http://php.jpnnet.com/">http://php.jpnnet.com/</A>
-	º´Æ£¤µ¤ó¤òÃæ¿´¤Ë¥Þ¥ë¥Á¥Ð¥¤¥È³ÈÄ¥¤È¤·¤Æºî¤êľ¤µ¤ì¡¢ºÇ¿·ÈǤÏPHP-3.0.18¤ËÂбþ¤·¤Æ¤¤¤Þ¤¹¡£
-	  ÄÍÅÄ ÂîÌ餵¤ó¤Ï¡¢PHP4 ÍѤÎÆüËܸì´Ø·¸¤Î³ÈÄ¥¥â¥¸¥å¡¼¥ë
-		<A HREF="ftp://night.fminn.nagano.nagano.jp/php4/">ftp://night.fminn.nagano.nagano.jp/php4/</A>
-	¤òÍÑ°Õ¤·¤Æ²¼¤µ¤Ã¤Æ¤Þ¤¹¡£
-	  ËܲȤÎÊý¤Ç¹ñºÝ²½¤ÎML¤âΩ¤Á¾å¤¬¤Ã¤Æ¤¤¤Þ¤¹¡£
-    ]
-</PRE></small>
-
-<P> ½èÍý¤¬Ê£»¨¤Ê¾ì¹ç¡¢Â¿¤¯¤Î¿Í¤Ï Perl ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤È CGI.pm ¤ò»È¤¤¤Þ¤¹¡£
-
-<small><PRE>
-    [ÌõÃí:
-	WDB ¤Ï¡¢Web ¤«¤é DataBase ¤Ø¤Î Perl ¤Î Interface ¤Ç¤¹¡£
-	wdb-p95 ¤Ø¤Î¥ê¥ó¥¯¤ÏÀÚ¤ì¤Æ¤·¤Þ¤Ã¤Æ¤¤¤Þ¤¹¡£¤ª¤½¤é¤¯¡¢Perl DBI ·Ðͳ¤Ç DBD::Pg ¤ÎÍøÍѤ¬²Äǽ¤È»×¤ï¤ì¤Þ¤¹¡£
-	¸½ºß¡¢WDBI ¤È¤¤¤¦Ì¾Á°¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤â¤Î
-		<A HREF="http://www.egroups.com/list/wdb-users/">http://www.egroups.com/list/wdb-users/</A>
-	¤È¡¢WDB¤Î̾Á°¤Î¤Þ¤Þ¤Î¤â¤Î
-		<A HREF="http://www.i-con.dk/wdb/">http://www.i-con.dk/wdb/</A>
-	¤È¤¬¤¢¤ê¤Þ¤¹¡£¤½¤Î·Ð°Þ¤Ï¤è¤¯¤ï¤«¤ê¤Þ¤»¤ó¡£
-    ]
-</PRE></small>
-
-<P>
-<H4><A NAME="2.3">2.3</A>)	PostgreSQL ¤Ë¥°¥é¥Õ¥£¥«¥ë¡¦¥æ¡¼¥¶¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Ï¤¢¤ê¤Þ¤¹¤«¡©
-¥ì¥Ý¡¼¥È¥¸¥§¥Í¥ì¡¼¥¿¤äËä¤á¹þ¤ßÌ䤤¹ç¤ï¤»¸À¸ì¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Ï¤¢¤ê¤Þ¤¹¤«¡©
-</H4>
-
-<P> <I>pgaccess</I> ¤È¸Æ¤Ð¤ì¤ëÁÇÀ²¤é¤·¤¤¥°¥é¥Õ¥£¥«¥ë¡¦¥æ¡¼¥¶¡¦¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤¬¤¢¤ê¡¢¤³¤ÎÇÛÉۤȶ¦¤Ë½Ð²Ù¤µ¤ì¤Þ¤¹¡£<I>Pgaccess</I> ¤Ë¤Ï¥ì¥Ý¡¼¥È¡¦¥¸¥§¥Í¥ì¡¼¥¿¤â¤¢¤ê¤Þ¤¹¡£Web ¥Ú¡¼¥¸¤Ï<A HREF="http://www.flex.ro/pgaccess">http://www.flex.ro/pgaccess</A>¤Ç¤¹¡£
-
-<P> <I>ecpg</I> ¤È¤¤¤¦ C ¸À¸ì¤Î¤¿¤á¤ÎËä¤á¹þ¤ß <small>SQL</small> Ì䤤¹ç¤ï¤»¸À¸ì¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤â¤¢¤ê¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="2.4">2.4</A>)	PostgreSQL ¤ÈÄÌ¿®¤¹¤ë¤Ë¤Ï¤É¤ó¤Ê¸À¸ì¤¬»È¤¨¤Þ¤¹¤«¡©
-</H4>
-
-<P>°Ê²¼¤Î¤â¤Î¤¬¤¢¤ê¤Þ¤¹:
-
-<UL>
-<LI>C (libpq)
-<LI>C++ (libpq++)
-<LI>Ëä¤á¹þ¤ßC (ecpg)
-<LI>Java (jdbc)
-<LI>Perl (perl5)
-<LI>ODBC (odbc)
-<LI>Python (<A HREF="http://www.druid.net/pygresql/">PyGreSQL</A>)
-<LI>TCL (libpgtcl)
-<LI>C Easy API (libpgeasy)
-<LI>Ëä¤á¹þ¤ß<small>HTML</small> (<A HREF="http://www.php.net">PHP from http://www.php.net</A>)
-</UL>
-<P>
-
-<small><PRE>
-    [ÌõÃí¡§
-	<A HREF="http://www.netlab.co.jp/ruby/jp/">ruby</A>¤Îºî¼Ô¤Ç¤¢¤ë¤Þ¤Ä¤â¤È ¤æ¤­¤Ò¤í(matz@ZetaBITS.COM)¤µ¤ó¤È¡¢¤Þ¤Ä¤â¤È ¤¨¤¤¤¸(ematsu@pfu.co.jp)¤µ¤ó¤¬
-	ruby ¤Î PostgreSQL ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤òºî¤ê¤Þ¤·¤¿¡£¸½ºß¤Î°Ý»ý´ÉÍý¤ÏÀÆÆ£ ÅФµ¤ó¤¬¤·¤Æ¤¤¤Þ¤¹¡£
-		<A HREF="http://webclub.kcom.ne.jp/mb/noborus/ruby/">http://webclub.kcom.ne.jp/mb/noborus/ruby/</A>
-        PgBash ¤Ï ¶­ÅÄ ²íÌÀ ¤µ¤ó¤¬ºî¤Ã¤¿ bash ¤Î PostgreSQL ¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤Ç¤¹¡£
-		<A HREF="http://www.psn.co.jp/PostgreSQL/pgbash/">http://www.psn.co.jp/PostgreSQL/pgbash/</A>
-	Bash¥³¥Þ¥ó¥É¥é¥¤¥ó¤Çpostgres ¤ËÌ䤤¹ç¤ï¤»¤Ç¤­¤Þ¤¹¡£
-	Perl ¤Î¥â¥¸¥å¡¼¥ë¤Ï¸Å¤¯¤«¤é¤¢¤ë Pg ¤È DBI ¥É¥é¥¤¥Ð¤Î DBD::Pg ¤È¤¬¤¢¤ê¡¢
-	¤¤¤º¤ì¤â Edmund Mergl »á¤Ë¤è¤ë¤â¤Î¤Ç <A HREF="http://www.cpan.org/">CPAN ¥µ¥¤¥È</A>¤Ë¤¢¤ê¤Þ¤¹¡£
-    ]
-</PRE></small>
-
-<P>
-<P>
-<HR>
-<H2><CENTER>´ÉÍý¾å¤Î¼ÁÌä</CENTER></H2>
-<P>
-
-<H4><A NAME="3.1">3.1</A>)	¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð <I>/usr/local/pgsql</I> °Ê³°¤Î¾ì½ê¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¤«¡©</H4>
-
-<P> ´Êñ¤ÊÊýË¡¤Ï¡¢ <I>configure</I> ¤òÁö¤é¤»¤ë¤È¤­¤Ë --prefix ¥ª¥×¥·¥ç¥ó¤ò»ØÄꤹ¤ë¤³¤È¤Ç¤¹¡£
-
-<P>
-<H4><A NAME="3.2">3.2</A>)	postmaster ¤òÁö¤é¤»¤ë¤È¡¢<I>Bad System Call</I> ¤È¤«¥³¥¢¡¦¥À¥ó¥×¤·¤¿¤È¤Î¥á¥Ã¥»¡¼¥¸¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-
-<P> ¤µ¤Þ¤¶¤Þ¤ÊÌäÂ꤬¹Í¤¨¤é¤ì¤Þ¤¹¤¬¡¢¤Þ¤ººÇ½é¤Ë¤¢¤Ê¤¿¤Î¥«¡¼¥Í¥ë¤Ë System V IPC ¤Î³ÈÄ¥¤¬¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤«¤ò³Îǧ¤·¤Æ¸«¤Æ¤¯¤À¤µ¤¤¡£PostgreSQL ¤Ï¥«¡¼¥Í¥ë¤Ë¤è¤ë¶¦Í­¥á¥â¥ê¡¼¤È¥»¥Þ¥Õ¥©¤Î¥µ¥Ý¡¼¥È¤òɬÍפȤ·¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="3.3">3.3</A>)	<I>postmaster</I> ¤òÁö¤é¤»¤è¤¦¤È¤¹¤ë¤È¡¢<I>IpcMemoryCreate</I> ¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-
-<P> ¥«¡¼¥Í¥ë¤¬¶¦Í­¥á¥â¥ê¡¼¤ò»ý¤ÄÀßÄê¤Ë¤Ê¤Ã¤Æ¤¤¤Ê¤«¤Ã¤¿¤«¡¢¤Ç¤Ê¤±¤ì¤Ð¡¢¥«¡¼¥Í¥ë¤ËÂФ·¤Æ»È¤¨¤ë¶¦Í­¥á¥â¥ê¡¼¤ÎÂ礭¤µ¤òÂ礭¤¯ÀßÄꤹ¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¶ñÂÎŪ¤ÊÂ礭¤µ¤Ï¡¢»È¤Ã¤Æ¤¤¤ë¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤È<I>postmaster</I> ¤òÁö¤é¤»¤ë¤È¤­¤ËÀßÄꤹ¤ë¥Ð¥Ã¥Õ¥¡¤Î¿ô¤È¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹¤Ë°Í¸¤·¤Þ¤¹¡£¤Û¤È¤ó¤É¤Î¥·¥¹¥Æ¥à¤Ç¤Ï¡¢´ûÄêÃͤΥХåե¡¥µ¥¤¥º¤Î¤Þ¤Þ¤Ç¡¢¾¯¤Ê¤¯¤È¤âÌó1MB¤¬É¬ÍפǤ¹¡£
-PostgreSQL Administrator's Gide ¤Ë¶¦Í­¥á¥â¥ê¡¼¤È¥»¥Þ¥Õ¥©¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤Î¾ÜºÙ¤¬¤¢¤ê¤Þ¤¹¡£</P>
-
-<P>
-<H4><A NAME="3.4">3.4</A>)	<I>postmaster¤ò</I>Áö¤é¤»¤è¤¦¤È¤¹¤ë¤È¡¢<I>IpcSemaphoreCreate</I> ¥¨¥é¡¼¤¬½Ð¤Þ¤¹¡£¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-
-<P>¤â¤·¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤¬<I>IpcSemaphoreCreate: semget failed (No space left on device)</I>¤Ç¤¢¤ì¤Ð¡¢¥«¡¼¥Í¥ë¤¬½½Ê¬¤Ê¥»¥Þ¥Õ¥©¤ò»È¤¨¤ë¤è¤¦¤Ë¹½À®¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£Postgres¤ÏÀøºßŪ¤Ê¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹Ëè¤Ë°ì¤Ä¤Î¥»¥Þ¥Õ¥©¤òɬÍפȤ·¤Þ¤¹¡£¤È¤ê¤¢¤¨¤º¤Î²ò·èºö¤Ï<I>postmaster</I>¤òµ¯Æ°¤¹¤ë¤È¤­¤Ë¡¢¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹¤Î¿ô¤ò¤è¤ê¾¯¤Ê¤¯À©¸Â¤ò¤¹¤ë¤³¤È¤Ç¤¹¡£´ûÄêÃͤÎ32¤è¤ê¾®¤µ¤Ê¿ô¤Î¥Ñ¥é¥á¡¼¥¿¤ò<I>-N</I>¤Ç»È¤¤¤Þ¤¹¡£¤è¤ê¹±µ×Ū¤Ê²ò·èºö¤Ï¡¢¥«¡¼¥Í¥ë¤Î<small>SEMMNS</small> ¤È <small>SEMMNI</small> ¥Ñ¥é¥á¡¼¥¿¤òÁý¤ä¤¹¤³¤È¤Ç¤¹¡£
-
-    <P>ÁàºîÉÔǽ¤Î¥»¥Þ¥Õ¥©¤â²áÅ٤ʥǡ¼¥¿¥Ù¡¼¥¹¥¢¥¯¥»¥¹¤Î´Ö¤Ë¥¯¥é¥Ã¥·¥å¤ò
-µ¯¤³¤¹²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
-</P>
-
-<P>¤â¤·¡¢¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤¬¤Ê¤Ë¤«Â¾¤Î¤â¤Î¤Ç¤¢¤ì¤Ð¡¢¥«¡¼¥Í¥ë¤Î¹½À®¤Ç¤Þ¤Ã¤¿¤¯¥»¥Þ¥Õ¥©¤Î¥µ¥Ý¡¼¥È¤ò¤·¤Æ¤¤¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
-PostgreSQL Administrator's Gide ¤Ë¶¦Í­¥á¥â¥ê¡¼¤È¥»¥Þ¥Õ¥©¤Ë¤Ä¤¤¤Æ¤Î¾ðÊó¤Î¾ÜºÙ¤¬¤¢¤ê¤Þ¤¹¡£</P>
-
-<P>
-
-<H4><A NAME="3.5">3.5</A>)	¾¤Î¥Û¥¹¥È¤«¤é¤ÎÀܳ¤Ï¤É¤Î¤è¤¦¤ËÀ©¸æ¤·¤Þ¤¹¤«¡©
-</H4>
-
-<P>	´ûÄêÃͤǤϡ¢PostgreSQL ¤Ï unix ¥É¥á¥¤¥ó¥½¥±¥Ã¥È¤ò»È¤¦¥í¡¼¥«¥ë¥Þ¥·¥ó¤«¤é¤ÎÀܳ¤·¤«µö¤·¤Þ¤»¤ó¡£<I>postmaster</I> µ¯Æ°¤Ë <I>-i</I> ¥Õ¥é¥Ã¥°¤ò²Ã¤¨¡¢<I>$PGDATA/pg_hba.conf</I> ¥Õ¥¡¥¤¥ë¤òŬÀڤ˾¤·¤Æ¡¢¥Û¥¹¥È¼çƳ·¿¤Îǧ¾Ú¤ò»È¤ï¤Ê¤¤¤«¤®¤ê¤Ï¾¤Î¥Þ¥·¥ó¤«¤é¤ÏÀܳ¤Ç¤­¤Ê¤¤¤Ç¤·¤ç¤¦¡£¤³¤ì¤Ë¤è¤êTCP/IP¤ÎÀܳ¤¬²Äǽ¤Ë¤Ê¤ê¤Þ¤¹¡£
-<p>ÁàºîÉÔǽ¤Ê¥»¥Þ¥Õ¥©¤â²áÅ٤Υǡ¼¥¿¥Ù¡¼¥¹¥¢¥¯¥»¥¹Ãæ¤Ë¥¯¥é¥Ã¥·¥å¤ò°ú¤­µ¯¤³¤¹¤³¤È¤¬¤¢¤ê¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="3.6">3.6</A>)	¤è¤êÎɤ¤À­Ç½¤òÆÀ¤ë¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥¨¥ó¥¸¥ó¤ò¤É¤Î¤è¤¦¤ËÄ´À°¤¹¤ì¤ÐÎɤ¤¤Ç¤¹¤«¡©
-</H4>
-
-<P> ³Î¤«¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹¤ÏÌ䤤¹ç¤ï¤»¤Î®ÅÙ¤òÁý¤·¤Þ¤¹¡£<small>EXPLAIN</small>¥³¥Þ¥ó¥É¤Ç PostgreSQL ¤¬¤É¤Î¤è¤¦¤Ë¤¢¤Ê¤¿¤ÎÌ䤤¹ç¤ï¤»¤òËÝÌõ¤·¤Æ¤¤¤ë¤«¤ò¸«¤ë¤³¤È¤¬¤Ç¤­¡¢¤½¤·¤Æ¡¢¤É¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤¬»È¤ï¤ì¤Æ¤¤¤ë¤«¤ò¸«¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-<P>¤â¤· <small>INSERT</small> ¤ò¿ÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢<small>COPY</small> ¥³¥Þ¥ó¥É¤ò»È¤Ã¤ÆÂ礭¤Ê¥Ð¥Ã¥Á½èÍý¤Ç¤½¤ì¤ò¹Ô¤Ê¤¦¤³¤È¤ò¸¡Æ¤¤·¤Æ²¼¤µ¤¤¡£¤³¤ì¤Ï¡¢<small>INSERT</small> ¤òÊÌ¡¹¤Ë¹Ô¤Ê¤¦¤è¤ê¤â¤Ã¤È¹â®¤Ç¤¹¡£¼¡¤Ë¡¢<small>BEGIN WORK/COMMIT</small> ¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¡¦¥Ö¥í¥Ã¥¯¤ÎÃæ¤Ë̵¤¤Ê¸¤Ï¡¢¤½¤ì¤é¼«¿È¤¬¤½¤ì¤¾¤ì¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤ËÆþ¤Ã¤Æ¤¤¤ë¤È¸«¤Ê¤µ¤ì¤Þ¤¹¡£¤¤¤¯¤Ä¤«¤Îʸ¤ò°ì¤Ä¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¡¦¥Ö¥í¥Ã¥¯¤ÎÃæ¤Ç¹Ô¤Ê¤¦¤³¤È¤ò¹Í¤¨¤Æ²¼¤µ¤¤¡£¤³¤ì¤Ë¤è¤ê¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤Î¥ª¡¼¥Ð¡¼¥Ø¥Ã¥É¤¬¸º¤ê¤Þ¤¹¡£¤Þ¤¿¡¢Â礭¤Ê¥Ç¡¼¥¿¤ÎÊѹ¹¤ò¹Ô¤Ê¤¦ºÝ¤Ï¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò°ìÅÙ³°¤·¤Æ¡¢ºî¤êľ¤¹¤³¤È¤ò¹Í¤¨¤Æ¤ß¤Æ²¼¤µ¤¤¡£
-
-<P> ¥Á¥å¡¼¥Ë¥ó¥°¤Î¥ª¥×¥·¥ç¥ó¤¬¤¤¤¯¤Ä¤«¤¢¤ê¤Þ¤¹¡£<I>postmaster</I> ¤ò <I>-o -F</I> ¥ª¥×¥·¥ç¥ó¤Çµ¯Æ°¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢<I>fsync()</I> ¤ò̵¸ú¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤ì¤Ë¤è¤Ã¤Æ¡¢³Æ¥È¥é¥ó¥¶¥¯¥·¥ç¥óËè¤Ë <I>fsync()</I> ¤Ç¥Ç¥£¥¹¥¯¤ò¹¹¿·¤¹¤ë¤Î¤ò»ß¤á¤µ¤»¤Þ¤¹¡£
-
-<P> <I>postmaster</I> <I>-B</I> ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¥Ð¥Ã¥¯¥¨¥ó¥É¡¦¥×¥í¥»¥¹¤Ë¤è¤ê»È¤ï¤ì¤ë¶¦Í­¥á¥â¥ê¡¼¡¦¥Ð¥Ã¥Õ¥¡¤òÂ礭¤¯¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤â¤·¡¢¤³¤Î¥Ñ¥é¥á¡¼¥¿¤ò¹â¤¯¤·¤¹¤®¤ë¤È¡¢¥«¡¼¥Í¥ë¤Î¶¦Í­¥á¥â¥ê¡¼¶õ´Ö¤ÎÀ©¸ÂÃͤò±Û¤¨¤Æ¤·¤Þ¤Ã¤¦¤¿¤á¤Ë <I>postmaster</I> ¤¬Áö¤é¤Ê¤¯¤Ê¤ë¤Ç¤·¤ç¤¦¡£´ûÄêÃͤǤϡ¢¤½¤ì¤¾¤ì¤Î¥Ð¥Ã¥Õ¥¡¤ÎÂ礭¤µ¤Ï 8K ¤Ç¡¢¥Ð¥Ã¥Õ¥¡¿ô¤Ï 64 ¤Ç¤¹¡£
-
-<P> ¥Ð¥Ã¥¯¥¨¥ó¥É¤ò <I>-S</I> ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¡¢¤½¤ì¤¾¤ì¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¡¦¥×¥í¥»¥¹¤¬°ì»þŪ¤ÊʤÙÂؤ¨¤Ë¤è¤Ã¤Æ»È¤¦¥á¥â¥ê¡¼¤ÎºÇÂ祵¥¤¥º¤òÁý¤ä¤¹¤³¤È¤â¤Ç¤­¤Þ¤¹¡£ ¤½¤Î <I>-S</I> ¤ÎÃͤϥ­¥í¥Ð¥¤¥Èñ°Ì¤Ç¡¢´ûÄêÃÍ¤Ï 512 (¤¹¤Ê¤ï¤Á¡¢512K)¤Ç¤¹¡£
-
-<P> ¤Þ¤¿¡¢<small>CLUSTER</small> ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¡¢¥Æ¡¼¥Ö¥ë¤Î¥Ç¡¼¥¿¤ò¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ë¹ç¤ï¤»¤ë¤¿¤á¤Ë¥°¥ë¡¼¥×²½¤¹¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¾Ü¤·¤¯¤Ï¡¢¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç <I>CLUSTER</I> ¤ò¸«¤Æ²¼¤µ¤¤¡£
-
-<P>
-<H4><A NAME="3.7">3.7</A>)	¤É¤Î¤è¤¦¤Ê¥Ç¥Ð¥°µ¡Ç½¤¬»È¤¨¤Þ¤¹¤«¡©</H4>
-
-<P> PostgreSQL ¤Ï¡¢¥Ç¥Ð¥°¤Î¤¿¤á¤Ë°ÕÌ£¤Î¤¢¤ë¡¢¾õÂÖ¾ðÊó¤òÊó¹ð¤¹¤ë¤¤¤¯¤Ä¤«¤Îµ¡Ç½¤ò»ý¤Á¤Þ¤¹¡£
-
-<P> ¤Þ¤º¡¢--enable-cassert ¥ª¥×¥·¥ç¥ó¤Ç <I>configure</I> ¤òÁö¤é¤»¤Þ¤¹¡£¤½¤¦¤·¤Æ¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢Âô»³¤Î <I>assert()</I> ¤¬¡¢¥Ð¥Ã¥¯¥¨¥ó¥É¤Î¿ÊĽ¾õ¶·¤ò´Æ»ë¤·¡¢²¿¤«Í½´ü¤»¤Ì¤³¤È¤¬µ¯¤­¤ë¤È¥×¥í¥°¥é¥à¤òÄä»ß¤¹¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
-
-<P> <I>postmaster</I> ¤È <I>postgres</I> ¤ÎξÊý¤Ç¤¤¤¯¤Ä¤«¤Î¥Ç¥Ð¥°¡¦¥ª¥×¥·¥ç¥ó¤ÎÍøÍѤ¬¤Ç¤­¤Þ¤¹¡£¤Þ¤º¡¢¼¡¤Î¤è¤¦¤Ë  <I>postmaster</I> ¤òµ¯Æ°¤¹¤ë¤È¤­¤Ï¤¤¤Ä¤Ç¤â¡¢É¸½à½ÐÎϤȥ¨¥é¡¼½ÐÎϤò¥í¥°¡¦¥Õ¥¡¥¤¥ë¤ËÁ÷¤ë¤è¤¦¤Ë¤·¤Æ¤¢¤ë¤³¤È¤ò³Î¤«¤á¤Æ²¼¤µ¤¤¡£
-
-<PRE>
-	cd /usr/local/pgsql
-	./bin/postmaster &gt;server.log 2&gt;&1 &
-</PRE>
-
-<P> ¤³¤ì¤Ë¤è¤ê PostgreSQL ¤ÎºÇ¾åÉô¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Ë server.log ¥Õ¥¡¥¤¥ë¤¬ÃÖ¤«¤ì¤Þ¤¹¡£¤³¤Î¥Õ¥¡¥¤¥ë¤Ï¥µ¡¼¥Ð¡¼¤¬Áø¶ø¤·¤¿ÌäÂê¤ä¥¨¥é¡¼¤Ë¤Ä¤¤¤ÆÍ­ÍѤʾðÊó¤ò´Þ¤ß¤Þ¤¹¡£<I>Postmaster</I> ¤Ï¹¹¤Ë¾ÜºÙ¤Ê¾ðÊó¤òÊó¹ð¤¹¤ë¤¿¤á¤Î <I>-d</I> ¥ª¥×¥·¥ç¥ó¤ò»ý¤Á¤Þ¤¹¡£¤½¤Î <I>-d</I> ¥ª¥×¥·¥ç¥ó¤Ï¡¢¥Ç¥Ð¥°¡¦¥ì¥Ù¥ë¤ò»ØÄꤷ¤Þ¤¹¡£¹â¤¤¥Ç¥Ð¥°¡¦¥ì¥Ù¥ë¤Ç¤Ï¡¢Â礭¤Ê¥í¥°¥Õ¥¡¥¤¥ë¤òÀ¸À®¤¹¤ë¤³¤È¤ËÃí°Õ¤·¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
-
-<P>¤â¤·¡¢<i>postmaster</i>¤¬Áö¤Ã¤Æ¤¤¤Ê¤±¤ì¤Ð¡¢<I>postgres</I>¥Ð¥Ã¥¯¥¨¥ó¥É¤ò¥³¥Þ¥ó¥É¹Ô¤«¤éÁö¤é¤»¤ë¤³¤È¤¬¤Ç¤­¡¢Ä¾ÀÜ<small>SQL</small>ʸ¤ò¥¿¥¤¥×¤¹¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£¤³¤Î¤ä¤ê¤«¤¿¤Ï¡¢¥Ç¥Ð¥°ÌÜŪ¤Î¤È¤­<B>¤À¤±</B>¤ª¾©¤á¤·¤Þ¤¹¡£¥»¥ß¥³¥í¥ó¤Ç¤Ï¤Ê¤¯¡¢²þ¹Ô¤¬Ì䤤¹ç¤ï¤»¤Î½ª¤ê¤Ë¤Ê¤ë¤³¤È¤ËÃí°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£¤â¤·¡¢¥Ç¥Ð¥°¥·¥ó¥Ü¥ë¤òÆþ¤ì¤Æ¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤¤¤ì¤Ð¡¢¥Ç¥Ð¥Ã¥¬¤ò»È¤Ã¤Æ²¿¤¬µ¯¤­¤Æ¤¤¤ë¤«¤ò¸«¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£postmaster ¤«¤é¥Ð¥Ã¥¯¥¨¥ó¥É¤ò³«»Ï¤·¤¿¤ï¤±¤Ç¤Ï¤Ê¤¤¤Î¤Ç¡¢ÆÈΩ¤Ê´Ä¶­¤ÇÁö¤Ã¤Æ¤¤¤ë¤Î¤Ç¤Ï¤Ê¤¯¥í¥Ã¥¯¡¿¥Ð¥Ã¥¯¥¨¥ó¥É¤È¤ÎÂÐÏäÎÌäÂ꤬½ÅÊ£¤¹¤ë¤³¤È¤Ï¤¢¤ê¤Þ¤»¤ó¡£
-
-	<P> ¤â¤·¡¢<i>postmaster</i>¤¬Áö¤Ã¤Æ¤¤¤ì¤Ð¡¢¤¢¤ë¥¦¥£¥ó¥É¥¦¤Ç
-<I>psql</I>¤ò³«»Ï¤¹¤ë¤È¡¢<i>psql</i> ¤Ç»È¤ï¤ì¤ë <i>postgres</i> ¥×¥í¥»¥¹
-¤Î<small>PID</small>¤¬¸«¤Ä¤«¤ê¤Þ¤¹¡£¥Ç¥Ð¥Ã¥¬¤ò»È¤Ã¤Æ
-<i>postgres</i>¤Î<small>PID</small>¤Ë¥¢¥¿¥Ã¥Á(attach)¤·¤Þ¤¹¡£¥Ç¥Ð¥Ã
-¥¬¤ÎÃ椫¤é¥Ö¥ì¡¼¥¯¡¦¥Ý¥¤¥ó¥È¤ò¥»¥Ã¥È¤·¡¢<i>psql</i> ¤«¤éÌ䤤¹ç¤ï¤»¤òȯ¹Ô
-¤·¤Þ¤¹¡£¥Ç¥Ð¥°¤Î¤¿¤á¤Ë<i>postgres</i>¤ò»ÏÆ°¤¹¤ë¾ì¹ç¤Ï¡¢PGOPTIONS="-W n" 
-¤òÀßÄê¤Ç¤­¡¢¤½¤ì¤«¤é¡¢<i>psql</i> ¤ò³«»Ï¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢<i>n</i> ÉÃ
-³«»Ï¤òÃ٤餻¤ë¤Ï¤º¤Ê¤Î¤Ç¡¢¥Ç¥Ð¥Ã¥¬¤Ç¥×¥í¥»¥¹¤Ë¥¢¥¿¥Ã¥Á¤·¤Æ¡¢¥Ö¥ì¡¼¥¯¥Ý¥¤
-¥ó¥È¤òÀßÄꤷ¡¢³«»Ï¤«¤é½ç¤òÄɤäƸ«¤Æ¤æ¤¯¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-
-<P> postgreSQL ¥×¥í¥°¥é¥à¤Ë¤Ï¡¢¥Ç¥Ð¥°¤ÈÀ­Ç½Â¬Äê¤Ë¤È¤Æ¤âÌò¤ËΩ¤Ä <I>-s</I>¤ä <I>-A</I>¤ä <I>-t</I> Åù¤Î¥ª¥×¥·¥ç¥ó¤¬¤¢¤ê¤Þ¤¹¡£
-
-<P> ²¿¤È¤¤¤¦´Ø¿ô¤¬¤É¤Î¤¯¤é¤¤¼Â¹Ô»þ´Ö¤ò¿©¤Ã¤Æ¤¤¤ë¤«¤ò¸«¤ë¤¿¤á¤Ë¡¢¥×¥í¥Õ¥¡¥¤¥ê¥ó¥°¡Ê¥×¥í¥Õ¥£¡¼¥ëÉÕ¤­¡Ë¤Ç¥³¥ó¥Ñ¥¤¥ë¤¹¤ë¤³¤È¤â²Äǽ¤Ç¤¹¡£¤½¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¤Î¥×¥í¥Õ¥£¡¼¥ë¡¦¥Õ¥¡¥¤¥ë¤Ï <I>pgsql/data/base/dbname</I> ¥Ç¥£¥ì¥¯¥È¥ê¤Ë³ÊǼ¤µ¤ì¤ë¤Ç¤·¤ç¤¦¡£¥¯¥é¥¤¥¢¥ó¥È¤Î¥×¥í¥Õ¥£¡¼¥ë¤Ï¥¯¥é¥¤¥¢¥ó¥È¤Î¸½¹Ô¥Ç¥£¥ì¥¯¥È¥ê¤ËÃÖ¤«¤ì¤ë¤Ç¤·¤ç¤¦¡£Linux ¤Ç¤Þ¤È¤â¤Ê¥×¥í¥Õ¥¡¥¤¥ê¥ó¥°¤ò¹Ô¤¦¤Ë¤Ï <I>-DLINUX_PROFILE</I> ¤Ç¥³¥ó¥Ñ¥¤¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£
-
-
-<P>
-<H4><A NAME="3.8">3.8</A>)	Àܳ¤·¤è¤¦¤È¤¹¤ë¤È¤­¤Ë <I>'Sorry, too many clients'</I> ¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-
-<P> <I>postmaster¤¬</I>Ʊ»þ»ÏÆ°¤Ç¤­¤ë¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹¤ËÂФ¹¤ëÀ©¸Â¿ô¤òÁý¤ä¤¹É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
-<P>´ûÄê¤ÎºÇÂç¥×¥í¥»¥¹¤Ï32¥×¥í¥»¥¹¤Ç¤¹¡£<I>-N</I>¤ËŬÀÚ¤ÊÃͤò°ú¿ô¤Ë¤·¤Æ<I>postmaster</I>¤òºÆµ¯Æ°¤¹¤ë¤«¡¢postgresql.conf ¤ò½¤Àµ¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢¤½¤ÎÃͤòÁý¤ä¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-
-¡£´ûÄê¤Î¹½À®¤Ç¤Ï<I>-N</I>¤ÏºÇÂç1024¤Þ¤ÇÀßÄê¤Ç¤­¤Þ¤¹¡£¤â¤·¡¢¤â¤Ã¤ÈɬÍפǤ¢¤ì¤Ð<I>include/config.h</I>¤ÎÃæ¤Î<small>MAXBACKENDS</small>¤òÁý²Ã¤µ¤»¡¢ºÆ¹½ÃÛ¤·¤Þ¤¹¡£¤â¤·¡¢Ë¾¤à¤Ê¤é<I>configure</I>¤Î <I>--with-maxbackends</I>ÀÚÂؤò»È¤Ã¤Æ¡¢<I>-N</I>¤Î´ûÄêÃͤò¹½À®»þ¤ËÀßÄê¤Ç¤­¤Þ¤¹¡£
-
-<P>¤â¤·¡¢<I>-N</I> ¤ò 32¤è¤ê¤âÂ礭¤¯¤¹¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢<I>-B</I>¤â´ûÄê¤Î64¤è¤êÂ礭¤¤ÃͤËÁý²Ã¤µ¤»¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤¤·¡¢<I>-B</I> ¤Ï¾¯¤Ê¤¯¤È¤â <I>-N</I> ¤Î2ÇܤϤʤ¯¤Æ¤Ï¤Ê¤é¤º¡¢¤ª¤½¤é¤¯ºÇ¹âÀ­Ç½¤ò˾¤à¤Ê¤é¤Ð¤½¤ì¤è¤êÂ礭¤¤Ãͤ¬É¬ÍפʤϤº¤Ç¤¹¡£¥Ð¥Ã¥¯¥¨¥ó¥É¥×¥í¥»¥¹¤ò¤¿¤¯¤µ¤ó¤Ë¤¹¤ë¤È¡¢¤¤¤í¤¤¤í¤ÊUnix¥«¡¼¥Í¥ë¹½À®¥Ñ¥é¥á¡¼¥¿¤âÁý¤ä¤¹¤³¤È¤¬É¬Íפˤʤ뤫¤â¤·¤ì¤Þ¤»¤ó¡£
-¶¦Í­¥á¥â¥ê¡¼¡¦¥Ö¥í¥Ã¥¯¤ÎºÇÂçÃÍ(<small>SHMMAX</small>)¡¢
-¥»¥Þ¥Õ¥©¤ÎºÇÂç¿ô(<small>SEMMNS</small>¤È<small>SEMMNI</small>)¡¢
-¥×¥í¥»¥¹¤ÎºÇÂç¿ô(<small>NPROC</small>)¡¢
-¥æ¡¼¥¶Ëè¤ÎºÇÂç¥×¥í¥»¥¹¿ô(<small>MAXUPRC</small>)¡¢
-³«¤¯¥Õ¥¡¥¤¥ë¤ÎºÇÂç¿ô(<small>NFILE</small>¤È<small>NINODE</small>
-¤â³Îǧ»ö¹à¤Ë´Þ¤Þ¤ì¤Þ¤¹¡£
-PostgreSQL¤Ëµö¤µ¤ì¤ë¥Ð¥Ã¥¯¥¨¥ó¥É¤Î¥×¥í¥»¥¹¿ô¤¬À©¸Â¤µ¤ì¤Æ¤¤¤ë¤Î¤Ï¡¢
-¥·¥¹¥Æ¥à¤Î¥ê¥½¡¼¥¹¤ò»È¤¤²Ì¤·¤Æ¤·¤Þ¤¦¤³¤È¤òÈò¤±¤ë¤¿¤á¤Ç¤¹¡£
-
-<P>6.5¤è¤êÁ°¤Î¥Ð¡¼¥¸¥ç¥ó¤ÎPostgreSQL¤Ç¤Ï¥Ð¥Ã¥¯¥¨¥ó¥É¤ÎºÇÂç¿ô¤Ï64¤Ç¤·¤¿¤¬¡¢Êѹ¹¤¹¤ë¤Ë¤Ï¡¢<I>include/storage/sinvaladt.h</I>¤ÎÃæ¤ÎMaxBackendIdÄê¿ô¤ò½¤Àµ¤·¤¿¸å¤ËºÆ¹½ÃÛ¤¬É¬ÍפǤ·¤¿¡£
-
-<P>
-<H4><A NAME="3.9">3.9</A>)	¼«Ê¬¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë <I>pg_sorttemp.XXX</I>¥Õ¥¡¥¤¥ë¤Ï²¿¤Ç¤¹¤«¡©
-</H4>
-
-<P> Ì䤤¹ç¤ï¤»¼Â¹Ô¥â¥¸¥å¡¼¥ë¤Ë¤è¤Ã¤ÆÀ¸À®¤µ¤ì¤¿°ì»þŪ¤Ê¥Õ¥¡¥¤¥ë¤Ç¤¹¡£Î㤨¤Ð¡¢¤â¤· <small>ORDER BY</small> ¶ç¤òËþ¤¿¤¹¤¿¤á¤Ë¥Ð¥Ã¥¯¥¨¥ó¥É¤Î <I>-S</I> ¥Ñ¥é¥á¡¼¥¿¤Çµö²Ä¤·¤¿Ãͤè¤ê¤âÂ礭¤Ê¥¹¥Ú¡¼¥¹¤¬¥½¡¼¥È¤ÎºÝ¤ËɬÍפÀ¤È¤¹¤ë¤È¡¢°î¤ì¤¿¥Ç¡¼¥¿¤òÊÝ»ý¤¹¤ë¤¿¤á¤Ë°ì»þŪ¤Ê¥Õ¥¡¥¤¥ë¤¬¤¤¤¯¤Ä¤«À¸À®¤µ¤ì¤Þ¤¹¡£
-<P>
-°ì»þŪ¤Ê¥Õ¥¡¥¤¥ë¤Ï¼«Æ°Åª¤Ë¾Ã¤·µî¤é¤ì¤ë¤Ï¤º¤Ç¤¹¤¬¡¢¤â¤·¡¢¥½¡¼¥È¤ÎÅÓÃæ¤Ç¥Ð¥Ã¥¯¥¨¥ó¥É¤¬¥¯¥é¥Ã¥·¥å¤·¤Æ¤·¤Þ¤¦¤È¤½¤¦¤Ï¤Ê¤ê¤Þ¤»¤ó¡£¤½¤Î¤È¤­¥Ð¥Ã¥¯¥¨¥ó¥É¤¬¤Ò¤È¤Ä¤âÁö¤Ã¤Æ¤Ê¤±¤ì¤Ð¡¢pg_tempNNN.NN¥Õ¥¡¥¤¥ë¤ò¾Ã¤·¤Æ¤âÂç¾æÉפǤ¹¡£
-
-
-<small><PRE>
-    [ÌõÃí¡§
-	 SYSLOGD ·Ðͳ¤Ç¥í¥°¤ò½ÐÎϤ¹¤ë¤Ë¤Ï¡¢¤Þ¤º¡¢configure ¤ò --enable-syslog 
-	ÉÕ¤­¤ÇÁö¤é¤»¤¿¸å¡¢¥³¥ó¥Ñ¥¤¥ë¤È¥¤¥ó¥¹¥È¡¼¥ë¤ò¹Ô¤Ê¤¤¤Þ¤¹¡£
-	 ¼¡¤Ë¡¢syslog.conf ¤Ë local0.* ¤Î ½ÐÎÏÀè¤ò»ØÄꤷ(´Ä¶­ÊÑ¿ô¤ÇÊѹ¹²Äǽ)¡¢
-	syslogd ¤Ë HUP ¥·¥°¥Ê¥ë¤òÁ÷¤Ã¤Æ½é´ü²½¤·¤Æ¤ª¤­¤Þ¤¹¡£¤½¤·¤Æ¡¢
-	$PGDATA/pg_options ¤Ë syslog=2 ¤ò²Ã¤¨¤Æ¡¢ postmaster ¤ò -S 
-	¥ª¥×¥·¥ç¥óÉÕ¤­¤Ë¤Æ¥µ¡¼¥Ð¥â¡¼¥É¤Çµ¯Æ°¤·¤Þ¤¹¡£(¥Ð¡¼¥¸¥ç¥ó 7.1 ¤«¤é¤Ï 
-	pg_options ¤Ï postgresql.conf ¤Ë¤Ê¤Ã¤Æ¤¤¤Þ¤¹¡£)
-    ]
-</PRE></small>
-
-
-<P>
-<P>
-<HR>
-<H2><CENTER>Áàºî¾å¤Î¼ÁÌä</CENTER></H2>
-<P>
-
-<H4><A NAME="4.1">4.1</A>)	¥Ð¥¤¥Ê¥ê¡¦¥«¡¼¥½¥ë¤ÈÄ̾參¡¼¥½¥ë¤È¤Î¸·Ì©¤Ê°ã¤¤¤Ï²¿¤Ç¤¹¤«¡©
-</H4>
-
-<P> ¾Ü½Ò¤Ï¡¢¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç <small>DECLARE</small> ¤ò¸«¤Æ²¼¤µ¤¤¡£
-
-<P>
-<H4><A NAME="4.2">4.2</A>)	ºÇ½é¤Î¿ô¥í¥¦¤Î¤ß¤ò <small>SELECT</small> ¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
-</H4>
-
-<P> ¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç<small>FETCH</small>¤ò¸«¤Æ¤¯¤À¤µ¤¤¡£¤¢¤ë¤¤¤Ï¡¢SELECT ... LIMIT....¤ò»È¤Ã¤Æ¤ß¤Æ²¼¤µ¤¤¡£
-
-<P>¤¿¤È¤¨¡¢Íߤ·¤¤¤Î¤ÏºÇ½é¤Î¿ô¥í¥¦¤À¤±¤Ç¤â¡¢¤¹¤Ù¤Æ¤ÎÌ䤤¹ç¤ï¤»¤òɾ²Á¤·¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£<small>ORDER BY</small> ¤ò»ý¤Ã¤¿Ì䤤¹ç¤ï¤»¤ò¹Í¤¨¤Æ¤ß¤Æ²¼¤µ¤¤¡£
-¤â¤·¡¢<small>ORDER BY</small>¤Ë¹ç¤Ã¤¿¥¤¥ó¥Ç¥Ã¥¯¥¹¤¬¤¢¤ë¤È¤¹¤ë¤È PostgreSQL¤ÏÍ׵ᤵ¤ì¤¿ºÇ½é¤Î¿ô¥í¥¦¤À¤±¤Çɾ²Á¤Ç¤­¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¤¬¡¢¤Ç¤Ê¤ì¤Ð¡¢PostgreSQL ¤Ï°Õ¿Þ¤·¤¿¥í¥¦¤¬À¸À®¤µ¤ì¤ë¤Þ¤Ç¤¹¤Ù¤Æ¤Î¥í¥¦¤òɾ²Á¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤«¤â¤·¤ì¤Þ¤»¤ó¡£
-
-<P>
-<H4><A NAME="4.3">4.3</A>)	¥Æ¡¼¥Ö¥ë¤ä¤½¤Î¾¤Î¾ðÊó¤Î¥ê¥¹¥È¤ò <I>psql</I> ¤Ç¸«¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
-</H4>
-
-<P>
-  <I>psql</I>¤Î¥½¡¼¥¹¥³¡¼¥É¤È¤·¤Æ½ñ¤«¤ì¤¿ <I>pgsql/src/bin/psql/describe.c</I> ¥Õ¥¡¥¤¥ë¤òÆɤळ¤È¤¬¤½¤ÎÅú¤¨¤Ç¤¹¡£
-¤½¤³¤Ë¤Ï¡¢psql¤Î¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¥³¥Þ¥ó¥É¤Ë¤è¤ë½ÐÎϤΤ¿¤á¤Î<small>SQL</small>¥³¥Þ¥ó¥É¤¬´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£ <I>psql</I> ¤Ë <I>-E</I> ¥ª¥×¥·¥ç¥ó¤ò¤Ä¤±¤Æµ¯Æ°¤¹¤ì¤Ð¡¢Í¿¤¨¤¿¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë¤¿¤á¤ÎÌ䤤¹ç¤ï¤»¤¬½ÐÎϤµ¤ì¤Þ¤¹¡£
-<P>
-
-
-<H4><A NAME="4.4">4.4</A>)	¥Æ¡¼¥Ö¥ë¤«¤é¥«¥é¥à¤Îºï½ü¤Ï¤É¤Î¤è¤¦¤Ë¤·¤Þ¤¹¤«¡©
-</H4>
-
-<P> <small>ALTER TABLE DROP COLUMN</small> ¤Ï¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤Þ¤»¤ó¤¬¡¢¤½¤ÎÂå¤ï¤ê¤Ë¤³¤¦¤·¤Þ¤¹:
-
-<PRE>
-	BEGIN;
-	LOCK TABLE old_table;
-	SELECT ...  -- ºï½ü¤·¤¿¤¤¥«¥é¥à°Ê³°¤Î¥«¥é¥à¤ò¤¹¤Ù¤ÆÁªÂò¤·¤Þ¤¹¡£
-	INTO TABLE new_table
-	FROM old_table;
-	DROP TABLE old_table;
-	ALTER TABLE new_table RENAME TO old_table;
-	COMMIT;
-</PRE>
-
-[ÌõÃí¡§¥«¥é¥à¤ÎÄÉ²Ã¤Ï ALTER TABLE ADD COLUMN ¤Ç¹Ô¤¨¤Þ¤¹¡£]
-
-
-<P>
-<H4><A NAME="4.5">4.5</A>)	¥í¥¦¡¢¥Æ¡¼¥Ö¥ë¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎºÇÂ祵¥¤¥º¤Ï¡©
-</H4>
-
-<P> À©¸Â¤Ï°Ê²¼¤Î¤È¤ª¤ê¤Ç¤¹¡£
-<PRE>
-¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎºÇÂ祵¥¤¥º? 	À©¸Â̵¤· (500GB ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤â¸ºß¤·¤Þ¤¹)
-¥Æ¡¼¥Ö¥ë¤ÎºÇÂ祵¥¤¥º?           16TB
-¥í¥¦¤ÎºÇÂ祵¥¤¥º?                 7.1°Ê¹ß¤ÇÀ©¸Â̵¤·
-¥Õ¥£¡¼¥ë¥É¤ÎºÇÂ祵¥¤¥º?         7.1°Ê¹ß¤Ç1GB
-¥Æ¡¼¥Ö¥ëÆâ¤Ç¤ÎºÇÂç¥í¥¦¿ô?       À©¸Â̵¤·
-¥Æ¡¼¥Ö¥ëÆâ¤Ç¤ÎºÇÂ祫¥é¥à¿ô?     ¥«¥é¥à¤Î·¿¤Ë¤è¤ê250-1600
-¥Æ¡¼¥Ö¥ëÆâ¤Ç¤ÎºÇÂ祤¥ó¥Ç¥¯¥¹¿ô? À©¸Â̵¤·
-</PRE>
-
-<P> ¤â¤Á¤í¤ó¡¢¤³¤ì¤é¤Ï¼ÂºÝ¤Ï̵À©¸Â¤Ç¤Ï¤Ê¤¯¡¢¥Ç¥£¥¹¥¯ÍÆÎ̤ȥá¥â¥ê¡¼¤ä¥¹¥ï¥Ã¥×¥¹¥Ú¡¼¥¹¤ÎÂ礭¤µ¤Ë¤è¤êÀ©¸Â¤µ¤ì¤Þ¤¹¡£À­Ç½¤Ï¤³¤ì¤é¤ÎÃͤ¬¤³¤È¤Î¤Û¤«Â礭¤Ê»þ¤ËÀú¤ê¤ò¼õ¤±¤Þ¤¹¡£
-
-<P> ºÇÂç¥Æ¡¼¥Ö¥ë¥µ¥¤¥º¤Î16TB¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Ë¤è¤ëµðÂç¥Õ¥¡¥¤¥ë¤Î¥µ¥Ý¡¼¥È¤ÏɬÍפȤ·¤Þ¤»¤ó¡£µðÂç¤Ê¥Æ¡¼¥Ö¥ë¤ÏÊ£¿ô¤Î1GB¤Î¥Õ¥¡¥¤¥ë¤Ëʬ¤±¤ÆÊݸ¤µ¤ì¤Þ¤¹¤Î¤Ç¡¢¥Õ¥¡¥¤¥ë¥·¥¹¥Æ¥à¤ÎÀ©¸Â¤Ï½ÅÍפǤϤ¢¤ê¤Þ¤»¤ó¡£
-
-<P> ¥Ç¥Õ¥©¥ë¥È¤Î¥Ö¥í¥Ã¥¯¥µ¥¤¥º¤ò32k¤Ë¤¹¤ë¤ÈºÇÂç¥Æ¡¼¥Ö¥ë¥µ¥¤¥º¤ÈºÇÂ祫¥é¥à¿ô¤È¤¬Áý²Ã¤·¤Þ¤¹¡£
-
-
-<P>
-<H4><A NAME="4.6">4.6</A>)	°ìÈÌŪ¤Ê¥Æ¥­¥¹¥È¥Õ¥¡¥¤¥ë¤«¤é¥Ç¡¼¥¿¤òÊݸ¤¹¤ë¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Ç¥£¥¹¥¯ÍÆÎ̤ϤɤΤ¯¤é¤¤É¬ÍפǤ¹¡©
-</H4>
-
-ÉáÄ̤Υƥ­¥¹¥È¥Õ¥¡¥¤¥ë¤ò PostgreSQL ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÊݸ¤¹¤ë¤Ë¤Ï¡¢ºÇÂç¤ÇÌó5ÇܤΥǥ£¥¹¥¯ÍÆÎ̤òɬÍפȤ·¤Þ¤¹¡£<P>
-
-<P> ÎãÂê¤È¤·¤Æ¡¢³Æ¹Ô¤ËÀ°¿ô¤È¥Æ¥­¥¹¥Èµ­½Ò¤ò»ý¤Ä 100,000¹Ô¤Î¥Õ¥¡¥¤¥ë¤ò¹Í¤¨
-¤Æ¤ß¤Þ¤·¤ç¤¦¡£¥Æ¥­¥¹¥È¤Îʸ»úÎó¤ÎÊ¿¶ÑŤµ¤ò20¥Ð¥¤¥È¤È²¾Äꤹ¤ë¤È¡¢¥Õ¥é¥Ã¥È
-¥Õ¥¡¥¤¥ë¤ÎÂ礭¤µ¤ÏÌó2.8MB ¤Ç¤¹¡£¤³¤Î¥Ç¡¼¥¿¤ò´Þ¤à PostgreSQL ¥Ç¡¼¥¿¥Ù¡¼¥¹
-¥Õ¥¡¥¤¥ë¤ÎÂ礭¤µ¤Ï¼¡¤Î¤è¤¦¤ËÌó6.4MB¤È¸«ÀѤâ¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡§
-
-<PRE>
-    36 bytes: ³Æ¥í¥¦¤Î¥Ø¥Ã¥À(³µ»»)
-    24 bytes: À°¿ô(int)¥Õ¥£¡¼¥ë¥É¤È¥Æ¥­¥¹¥È(text)¥Õ¥£¡¼¥ë¥É
-   + 4 bytes: ¥Ú¡¼¥¸¾å¤Î¥¿¥Ã¥×¥ë¤Ø¤Î¥Ý¥¤¥ó¥¿
-   ----------------------------------------
-   64 bytes per row
-
-   PostgreSQL ¤Î¥Ç¡¼¥¿¥Ú¡¼¥¸¥µ¥¤¥º¤Ï 8192¥Ð¥¤¥È(8KB)¤Ê¤Î¤Ç:
-
-   8192 bytes per page
-   -------------------   =  128 rows per database page (ÀÚ¤ê¾å¤²)
-     64 bytes per row
-
-   100000 data rows
-   --------------------  =  782 database pages
-      128 rows per page
- 
-782 database pages * 8192 bytes per page  =  6,406,144 bytes (6.4 MB)
-</PRE>
-
-<P>
-¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¡¢¤³¤ì¤Û¤É¤Î¥ª¡¼¥Ð¥Ø¥Ã¥É¤ÏÍ׵ᤷ¤Þ¤»¤ó¤¬¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹ÉÕ¤±¤µ¤ì¤ë¥Ç¡¼¥¿¤ò´Þ¤à°Ê¾å¡¢¤½¤ì¤Ê¤ê¤ËÂ礭¤¯¤Ê¤ê¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="4.7">4.7</A>)	ÄêµÁ¤µ¤ì¤¿¥Æ¡¼¥Ö¥ë¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¢¤ª¤è¤Ó¡¢¥æ¡¼¥¶¤ò¤É¤Î¤è¤¦¤Ë¤·¤Æ¸«¤Ä¤±½Ð¤·¤Þ¤¹¤«¡©
-</H4>
-
-<P> <I>psql</I> ¤Ë¤Ï¤¤¤í¤¤¤í¤Ê¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¡¦¥³¥Þ¥ó¥É¤¬¤¢¤ê¡¢¤³¤¦¤·¤¿¾ðÊó¤òɽ¼¨¤·¤Þ¤¹¡£¥Ð¥Ã¥¯¥¹¥é¥Ã¥·¥å¡¦¥³¥Þ¥ó¥É¤Î¼ïÎà¤ò¸«¤ë¤Ë¤Ï \? ¤ò»È¤Ã¤Æ²¼¤µ¤¤¡£
-<P> ¤Þ¤¿¡¢<I>pgsql/src/tutorial/syscat.source</I> ¥Õ¥¡¥¤¥ë¤òÁö¤é¤»¤Æ¤ß¤Æ²¼¤µ¤¤¡£¤½¤ì¤Ï¡¢Âô»³¤Î <small>SELECT</small> ʸ¤Ë¤è¤êɬÍפʾðÊó¤ò¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥·¥¹¥Æ¥à¡¦¥Æ¡¼¥Ö¥ë¤«¤é¼è¤ê½Ð¤·¤ÆÎ㼨¤·¤Æ¤¯¤ì¤Þ¤¹¡£¤Þ¤¿¡¢<i>pg_</i> ¤Ç»Ï¤Þ¤ë¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ë¤Ë¤âµ­½Ò¤µ¤ì¤Æ¤¤¤Þ¤¹¡£¤µ¤é¤Ë¡¢<i>psql -l</i> ¤Ï¤¹¤Ù¤Æ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò¥ê¥¹¥Èɽ¼¨¤·¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="4.8">4.8</A>)	Ì䤤¹ç¤ï¤»¤¬ÃÙ¤¤¤¦¤¨¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤Ã¤Æ¤¤¤ëÍͻҤ¬¤¢¤ê¤Þ¤»¤ó¡£¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-
-¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¼«Æ°Åª¤Ë¤¹¤Ù¤Æ¤ÎÌ䤤¹ç¤ï¤»¤Ç»È¤ï¤ì¤ë¤ï¤±¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¡£¥Æ¡¼
-¥Ö¥ë¤¬ºÇ¾®¥µ¥¤¥º¤è¤êÂ礭¤¯¡¢Ì䤤¹ç¤ï¤»¤Ç¤½¤Î¤ï¤º¤«¤Ê¥Ñ¡¼¥»¥ó¥Æ¡¼¥¸¤Î¥í¥¦¤ò
-ÁªÂò¤¹¤ë»þ¤À¤±¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï»È¤ï¤ì¤Þ¤¹¡£¤³¤ì¤Ï¥¤¥ó¥Ç¥Ã¥¯¥¹¥¹¥­¥ã¥ó¤Ë¤è
-¤êµ¯¤³¤µ¤ì¤ë¥é¥ó¥À¥à¤Ê¥Ç¥£¥¹¥¯¥¢¥¯¥»¥¹¤Ï¡¢¥Æ¡¼¥Ö¥ë¤ò¥¹¥È¥ì¡¼¥È¤ËÆɤà½ç¼¡
-Áöºº¤è¤ê¤âÃÙ¤¯¤Ê¤ë¤³¤È¤¬¤È¤­¤É¤­¤¢¤ë¤«¤é¤Ç¤¹¡£
-
-    <P>¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤¦¤«¤ò·èÄꤹ¤ë¤¿¤á¤Ë¡¢PostgreSQL ¤Ï¥Æ¡¼¥Ö¥ë¤Ë¤Ä¤¤
-¤Æ¤ÎÅý·×¾ðÊó¤ò»ý¤¿¤Ê¤±¤ì¤Ð¤Ê¤ê¤Þ¤»¤ó¡£¤³¤ÎÅý·×¾ðÊó¤Ï¡¢<SMALL>VACUUM
-ANALYZE</SMALL>¤Þ¤¿¤Ï¡¢Ã±¤Ë <SMALL>ANALYZE</SMALL> ¤ò»È¤Ã¤Æ¼ý½¸¤¹¤ë¤³¤È
-¤¬¤Ç¤­¤Þ¤¹¡£Åý·×¾ðÊó¤ò»È¤Ã¤Æ¥ª¥Ö¥Æ¥£¥Þ¥¤¥¶¤Ï¥Æ¡¼¥Ö¥ë¤ÎÃæ¤Ë¤¢¤ë¥í¥¦¿ô¤òÃÎ
-¤ê¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤¦¤Ù¤­¤«¤Î¤Î·èÄê¤ò¤è¤êÀµ¤·¤¯¤Ç¤­¤Þ¤¹¡£Åý·×¾ðÊó¤ÏºÇŬ
-¤Ê·ë¹ç½ç¤ä·ë¹çÊýË¡¤ò·è¤á¤ë¾å¤Ç¤âµ®½Å¤Ê¤â¤Î¤â¤¢¤ê¤Þ¤¹¡£Åý·×¾ðÊó¤Î¼ý½¸¤Ï¡¢
-¥Æ¡¼¥Ö¥ë¤ÎÆâÍƤ¬¤«¤ï¤ë¤ÈËè¤Ë·«ÊÖ¤·¤Ê¤µ¤ì¤ë¤Ù¤­¤Ç¤¹¡£</P>
-
-    <P> ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¡¢Ä̾ï <SMALL>ORDER BY</SMALL> ¤ä·ë¹ç¤ò¹Ô¤Ê
-¤¦¤¿¤á¤Ë¤Ï»È¤ï¤ì¤Þ¤»¤ó¡£½ç¼¡¥¹¥­¥ã¥ó¤Ë³¤¯ÌÀ¼¨Åª¥½¡¼¥È¤Ï¡¢µðÂç¤Ê¥Æ¡¼¥Ö¥ë
-¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¥¹¥­¥ã¥ó¤è¤ê¤âÉáÄ̤Ϲ⮤Ǥ¹¡£</P>
-    ¤·¤«¤·¡¢<SMALL>ORDER BY</SMALL>¤ÈÁȤ߹ç¤ï¤µ¤ì¤¿<SMALL>LIMIT</SMALL> 
-¤Ï¡¢¥Æ¡¼¥Ö¥ë¤Î¾®¤µ¤ÊÉôʬ¤òÊÖ¤¹¤¿¤á¤Ë¤¿¤Ó¤¿¤Ó¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤¦¤Ç¤·¤ç¤¦¡£
-
-    <P> <SMALL>LIKE</SMALL> ¤¢¤ë¤¤¤Ï <I>~</I> ¤Î¤è¤¦¤Ê¥ï¥¤¥ë¥É¥«¡¼¥É±é»»
-»Ò¤ò»È¤¦¤È¤­¡¢¸¡º÷¤Î³«»Ï¤¬Ê¸»úÎó¤Î»Ï¤á¤ÎÉôʬ¤Ë¸ÇÄꤵ¤ì¤Æ¤¤¤ë¤È¤­¤Ë¤Î¤ß¡¢
-¥¤¥ó¥Ç¥Ã¥¯¥¹¤¬»È¤ï¤ì¤Þ¤¹¡£¤½¤¦¤¤¤¦¤ï¤±¤Ç¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤¦¤¿¤á¤Ë¤Ï¡¢
-<SMALL>LIKE</SMALL> ¥Ñ¥¿¡¼¥ó¤Ï<I>%</I>¤Ç»Ï¤á¤Ê¤¤¤è¤¦¤Ë¤·¤Æ¡¢¤Þ¤¿¡¢
-<I>~</I>(Àµµ¬É½¸½)¥Ñ¥¿¡¼¥ó¤Ï<I>^</I> ¤Ç»Ï¤á¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£
-
-[ÌõÃí¡§
-	¶¯À©Åª¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò»È¤¦¤Ë¤Ï SET enable_seqscan = off ¤ò¼Â¹Ô¤·¤Þ¤¹
-]
-
-
-<P>
-<H4><A NAME="4.9">4.9</A>)	Ì䤤¹ç¤ï¤»¥ª¥Ö¥Æ¥£¥Þ¥¤¥¶¤¬¤É¤Î¤è¤¦¤ËÌ䤤¹ç¤ï¤»¤òɾ²Á¤¹¤ë¤Î¤«¤ò¸«¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
-</H4>
-
-<P> ¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç <small>EXPLAIN</small> ¤ò¸«¤Æ²¼¤µ¤¤¡£
-
-<P>
-<H3><A NAME="4.10">4.10</A>)	R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤È¤Ï²¿¤Ç¤¹¤«¡©</H3>
-
-<P> R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¶õ´ÖŪ¤Ê¥Ç¡¼¥¿¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹¤òÉÕ¤±¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£¥Ï¥Ã¥·¥å¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¤ÏÈϰϤθ¡º÷¤¬¤Ç¤­¤Þ¤»¤ó¡£¤Þ¤¿¡¢B-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¤Ï¡¢£±¼¡¸µ¤Ç¤·¤«ÈϰϤθ¡º÷¤¬¤Ç¤­¤Þ¤»¤ó¡£R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¤¢¤ì¤Ð¿¼¡¸µ¤Î¥Ç¡¼¥¿¤ò°·¤¨¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢¤â¤· R-tree ¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò <I>point</I> ·¿¤Î°À­¤ËÉÕ¤±¤ë¤³¤È¤¬¤Ç¤­¤ë¤È¤¹¤ë¤È¥·¥¹¥Æ¥à¤Ï¡¢¡ÖĹÊý·Á¤Ë°Ï¤Þ¤ì¤¿ÅÀ¤ò¤¹¤Ù¤ÆÁªÂò¤¹¤ë¡×¤È¤¤¤¦¤è¤¦¤ÊÌ䤤¹ç¤ï¤»¤Ë¡¢¤è¤ê¸úΨÎɤ¯Åú¤¨¤é¤ì¤Þ¤¹¡£
-
-<P> R-Tree ¤ÎÀ߷פθ¶Åµ¤È¤Ê¤ë¸¢°Ò¤¢¤ëÏÀʸ¤Ï:
-
-<P> Guttman, A. "R-Trees: A Dynamic Index Structure for Spatial Searching."
-Proceedings of the 1984 ACM SIGMOD Int'l Conf on Mgmt of Data, 45-57.
-
-<P> ¤³¤ÎÏÀʸ¤Ï¡¢Stonebraker ¶µ¼ø¤Î "Readings in Database Systems"
-¤Ç¤â¼è¤ê¾å¤²¤é¤ì¤Æ¤¤¤Þ¤¹¡£
-
-<P>
-<small><PRE>
-    [ÌõÃí¡§
-	  ÆàÎÉÀèüÂç¤ÎÀÐÀî²Â¼£¤µ¤ó¤è¤êR-Tree´Ø·¸¤Îʸ¸¥¤ò¾Ò²ð¤·¤Æ夭¤Þ¤·¤¿¡£
-	ÆüËܸì Postgres ML ¤Î¥¢¡¼¥«¥¤¥Ö¤«¤é "Subject: [postgres95 801] spatial data structures" 
-		<A HREF="http://www.sra.co.jp/people/t-ishii/PostgreSQL/mhonarc/pgsql-jp/1996Oct/msg00007.html">http://www.sra.co.jp/people/t-ishii/PostgreSQL/mhonarc/pgsql-jp/1996Oct/msg00007.html</A>
-	¤ò¤´Í÷²¼¤µ¤¤¡£
-    ]
-</PRE></small>
-
-<P> Áȹþ¤ß¤Î R-Tree ¤Ç¥Ý¥ê¥´¥ó¤ä¥Ü¥Ã¥¯¥¹¤òÁàºî¤Ç¤­¤Þ¤¹¡£ÍýÏÀŪ¤Ë¤ÏR-Tree ¤Ï¤â¤Ã¤È¹â¤¤¼¡¸µ¤òÁàºî¤¹¤ë¤è¤¦¤Ë¤â³ÈÄ¥¤Ç¤­¤Þ¤¹¡£¼Â¼ÁŪ¤Ë¤Ï¡¢R-Tree ¤Î³ÈÄ¥¤Ë¤Ï¤Á¤ç¤Ã¤È¤·¤¿ºî¶È¤¬É¬ÍפǤ·¤Æ¡¢¸½ºß¡¢²æ¡¹¤Ï¤½¤ì¤ò¤É¤Î¤è¤¦¤Ë¤¹¤ë¤«¤Ë¤Ä¤¤¤Æ¤Îʸ½ñ¤ò»ý¤Ã¤Æ¤¤¤Þ¤»¤ó¡£
-
-<P>
-<small><PRE>
-    [ÌõÃí¡§
-	  ¥¤¥ó¥¿¡¼¥¦¥£¥º¤ÎÊÒ²¬¤µ¤ó¤¬Â¿¼¡¸µ´ö²¿¥ª¥Ö¥¸¥§¥¯¥È¤Ø¤Î³ÈÄ¥ºî¶ÈÃæ¤Ç¤¹¡£¾Ü¤·¤¯¤Ï¡¢
-	<A HREF="http://www.interwiz.koganei.tokyo.jp/software/geometric/index.html">http://www.interwiz.koganei.tokyo.jp/software/geometric/index.html</A>
-	¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
-    ]
-</PRE></small>
-
-
-<P>
-<H4><A NAME="4.11">4.11</A>)	°äÅÁŪÌ䤤¹ç¤ï¤»ºÇŬ²½¤È¤Ï²¿¤Ç¤¹¤«¡©
-</H4>
-
-<P> GEQO ¥â¥¸¥å¡¼¥ë¤Ï¡¢Âô»³¤Î¥Æ¡¼¥Ö¥ë¤ò·ë¹ç¤¹¤ë¤È¤­¤Ë¡¢°äÅÁŪ¥¢¥ë¥´¥ê¥º¥à(GA)¤ÇÌä¹ç¤ï¤»¤ò¹â®²½¤·¤Þ¤¹¡£¤³¤ì¤Ë¤è¤ê¡¢¤·¤é¤ß¤Ä¤Ö¤·¤Ëõº÷¤ò¹Ô¤Ê¤ï¤Ê¤¯¤Æ¤â¡¢Â礭¤Ê·ë¹ç(join queries)¤ò°·¤¦¤³¤È¤¬¤Ç¤­¤ë¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="4.12">4.12</A>)	Àµµ¬É½¸½¤Ç¤Î¸¡º÷¤äÂçʸ»ú¤È¾®Ê¸»ú¤È¤ò¶èÊ̤·¤Ê¤¤Àµµ¬É½¸½¸¡º÷¤Ï¤É¤Î¤è¤¦¤Ë¼Â¸½¤·¤Þ¤¹¤«¡©Âçʸ»ú¤È¾®Ê¸»ú¤È¤ò¶èÊ̤·¤Ê¤¤¸¡º÷¤Î¤¿¤á¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¤É¤Î¤è¤¦¤Ë»È¤¤¤Þ¤¹¤«¡©
-</H4>
-
-<P>
-<I>~</I>±é»»»Ò¤ÏÀµµ¬É½¸½¾È¹ç¤ò¹Ô¤Ê¤¤¡¢<I>~*</I> ¤ÏÂçʸ»ú¤È¾®Ê¸»ú¤ò¶èÊ̤·¤Ê¤¤(case-insensitive)Àµµ¬É½¸½¾È¹ç¤ò¹Ô¤¤¤Þ¤¹¡£ PostgreSQL 7.1 °Ê¹ß¤Ç¤Ï¡¢Âçʸ»ú¤È¾®Ê¸»ú¤ò¶èÊ̤·¤Ê¤¤ <small>LIKE</small> ±é»»»Ò¤ò <small>ILIKE</small> ¤È¤¤¤¤¤Þ¤¹¡£
-
-
-<P>Âçʸ»ú¤È¾®Ê¸»ú¤ò¶èÊ̤·¤Ê¤¤ÅùÃÍÈæ³Ó¼¡¤Î¤è¤¦¤Ëɽ¸½¤Ç¤­¤ë¡§
-   
-    <PRE>
-    <STRONG>SELECT *</STRONG>
-    FROM tab
-    WHERE lower(col) = 'abc'
-    </PRE>
-
-ɸ½à¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ç¤Ï»È¤ï¤ì¤º¡¢¤·¤«¤·¤Ê¤¬¤é¡¢¤â¤·´Ø¿ô¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò
-ºî¤Ã¤¿¤Ê¤é¤½¤ì¤¬»È¤ï¤ì¤ë¤Ç¤·¤ç¤¦¡£
-
-   <PRE>
-   CREATE INDEX tabindex on tab (lower(col));
-   </PRE>
-
-
-
-
-<PRE>
-	WHERE lower(textfield) LIKE lower(pattern)
-</PRE>
-
-
-<P>
-<H4><A NAME="4.13">4.13</A>)	Ì䤤¹ç¤ï¤»¤ÎÃæ¤Ç¡¢¥Õ¥£¡¼¥ë¥É¤¬ <small>NULL</small> ¤Ç¤¢¤ë¤³¤È¤ò¸¡½Ð¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
-</H4>
-
-    <P>¥«¥é¥à¤ò <SMALL>IS NULL</SMALL> ¤È <SMALL>IS NOT NULL</SMALL>
-¤È¤Ç»î¤·¤Æ¤ß¤Þ¤¹¡£</P>
-
-<P>
-<H4><A NAME="4.14">4.14</A>)	ÍÍ¡¹¤Êʸ»ú·¿¤Î¤½¤ì¤¾¤ì¤Î°ã¤¤¤Ï²¿¤Ç¤¹¤«¡©
-</H4>
-
-<PRE>
-Type            Internal Name   Notes
---------------------------------------------------
-"char"          char            1 character
-CHAR(#)         bpchar          »ØÄꤵ¤ì¤¿¸ÇÄêĹ¤È¤Ê¤ë¤è¤¦¤Ë¶õÇò¤¬µÍ¤á¤é¤ì¤ë
-VARCHAR(#)      varchar         Ťµ¤Î¾å¸Â¤Î̵¤¤¥Æ¥­¥¹¥È
-TEXT            text            Ťµ¤ÎÀ©¸Â¤ÏºÇÂç¥í¥¦Ä¹¤Ë¤è¤ë
-BYTEA           bytea           ²ÄÊÑĹ¤Î¥Ð¥¤¥ÈÇÛÎó(null-byte safe)
-</PRE>
-
-<P> ÆâÉô̾¤Ë¤ªÌܤˤ«¤«¤ë¤Î¤Ï¡¢¥·¥¹¥Æ¥à¡¦¥«¥¿¥í¥°¤òÄ´¤Ù¤ë¤È¤­¤ä¡¢¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò¼õ¤±¼è¤ë¤È¤­¤Ç¤¹¡£
-
-
-<P> ¾åµ­¤Î·¿¤Î¤¦¤Á¸å¤Î£´¤Ä¤Î·¿¤Ï "varlena" ·¿¤Ç¤¹(¤¹¤Ê¤ï¤Á¡¢¥Ç¥£¥¹¥¯¤ÎºÇ½é¤Î£´¥Ð¥¤¥È¤¬¥Ç¡¼¥¿Ä¹¤Ç¡¢¤½¤ì¤Î¸å¤Ë¼ÂºÝ¤Î¥Ç¡¼¥¿¤¬Â³¤­¤Þ¤¹)¡£¤³¤Î¤è¤¦¤Ë¼ÂºÝ¤Î¶õ´Ö¤ÏÀë¸À¤µ¤ì¤¿Â礭¤µ¤è¤ê¤â¾¯¤·Â礭¤¯¤Ê¤ê¤Þ¤¹¡£¤·¤«¤·¡¢¤³¤ì¤é¤Î¥Ç¡¼¥¿·¿¤Ï<small>TOAST</small>¤Ë¤è¤ê°µ½Ì¤µ¤ì¤¿¤êÊ£¿ô¥í¥¦¤ËÅϤäÆÊݸ¤µ¤ì¤¿¤ê¤·¤Æ¡¢¥Ç¥£¥¹¥¯¾å¤Î¶õ´Ö¤Ï»×¤Ã¤¿¤è¤ê¾®¤µ¤¯¤Ê¤ê¤Þ¤¹¡£
-
-    <P><SMALL>CHAR()</SMALL>¤Ï¤¤¤Ä¤âŤµ¤¬Æ±¤¸Ê¸»úÎó¤òÊݸ¤¹¤ë¤Î¤ËºÇŬ¤Ç
-¤¹¡£<SMALL>VARCHAR()</SMALL> ¤Ï²ÄÊÑŤÎʸ»úÎó¤òÊݸ¤¹¤ë¤Î¤ËºÇŬ¤Ç¤¹¤¬¡¢
-Êݸ¤Ç¤­¤ëʸ»úÎó¤ÎŤµ¤ËÀ©¸Â¤¬¤¢¤ê¤Þ¤¹¡£<SMALL>TEXT</SMALL> ¤ÏŤµ¤ËÀ©¸Â
-¤Î̵¤¤Ê¸»úÎó¤ÎÊݸ¤¿¤á¤Î¤â¤Î¤Ç¡¢ºÇÂç1¥®¥¬¥Ð¥¤¥È¤Ç¤¹¡£
-<SMALL>BYTEA</SMALL>¤Ï¡¢ÉôʬŪ¤Ë<SMALL>NULL</SMALL> ¤Î¥Ð¥¤¥È¤ò´Þ¤à¥Ð¥¤¥Ê
-¥ê¥Ç¡¼¥¿¤òÊݸ¤¹¤ë¤¿¤á¤Î¤â¤Î¤Ç¤¹¡£</P>
-
-
-<P>
-<H4><A NAME="4.15.1">4.15.1</A>)	ÄÌÈÖ(serial)¡¿¼«Æ°Áýʬ¥Õ¥£¡¼¥ë¥É¤Ï¤É¤Î¤è¤¦¤Ë¤Ä¤¯¤ê¤Þ¤¹¤«¡©
-</H4>
-
-<P> PostgreSQL ¤Ï <small>SERIAL</small> ¥Ç¡¼¥¿·¿¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£¥«¥é¥à¾å¤ËÄÌÈ֤ȥ¤¥ó¥Ç¥Ã¥¯¥¹¤ò¼«Æ°ºîÀ®¤·¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢
-
-<PRE>
-	CREATE TABLE person ( 
-		id   SERIAL, 
-		name TEXT 
-	);
-</PRE>
-¤Ï¼«Æ°Åª¤Ë¼¡¤Î¤è¤¦¤ËËÝÌõ¤µ¤ì¤Þ¤¹:
-<PRE>
-	CREATE SEQUENCE person_id_seq;
-	CREATE TABLE person ( 
-		id   INT4 NOT NULL DEFAULT nextval('person_id_seq'),
-		name TEXT 
-	);
-	CREATE UNIQUE INDEX person_id_key ON person ( id );
-</PRE>
-ÄÌÈ֤ˤĤ¤¤Æ¤Î¤â¤Ã¤È¾Ü¤·¤¤¾ðÊó¤Ï¡¢¥ª¥ó¥é¥¤¥ó¥Þ¥Ë¥å¥¢¥ë¤Ç <I>create_sequence</I> ¤ò¤´Í÷²¼¤µ¤¤¡£
-<P> ¤Þ¤¿¡¢³Æ¥í¥¦¤Î<I>OID</I>¥Õ¥£¡¼¥ë¥É¤ò°ì°ÕÃͤȤ·¤Æ»È¤¦¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤·¤«¤·¤Ê¤¬¤é¡¢¤â¤·¤â¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò¥À¥ó¥×¤·¤Æ¤ê¥í¡¼¥É¤¹¤ëɬÍפ¬¤¢¤ë¾ì¹ç¤Ï¡¢<small>OID</small>¤ò²¹Â¸¤¹¤ë¤¿¤á¤Ë<I>pg_dump</I> ¤Ç <I>-o</I>¥ª¥×¥·¥ç¥ó¤ò»È¤¦¤«¡¢¤Þ¤¿¤Ï¡¢<small>COPY WITH OIDS</I>¥ª¥×¥·¥ç¥ó¤ò»È¤¦É¬Íפ¬¤¢¤ê¤Þ¤¹¡£
-
- Bruce Momjian ¤Î<A HREF="http://www.PostgreSQL.org/docs/aw_pgsql_book">(http://www.PostgreSQL.org/docs/aw_pgsql_book)¤Î Numbering Rows</A>¤Î¾Ï¤Ë¤¢¤ê¤¢¤Þ¤¹¡£
-
-
-<H4><A NAME="4.15.2">4.15.2</A>)	<small>SERIAL</small>¥Ç¡¼¥¿·¿¤ËÁÞÆþ¤µ¤ì¤ëÃͤϡ¢¤É¤¦¤¹¤ì¤ÐÆÀ¤é¤ì¤Þ¤¹¤«¡©
-</H4>
-    <P>¤Ò¤È¤Ä¤ÎÊýË¡¤Ï¡¢<I>nextval()</I> ´Ø¿ô¤ò»È¤Ã¤Æ¤½¤ÎÃͤòÁÞÆþ¤¹¤ë<I>
-Á°(before)¤Ë</I> SEQUENCE ¥ª¥Ö¥¸¥§¥¯¥È¤«¤é¼¡¤Î <small>SERIAL</small> Ãͤò¼è¤ê½Ð¤·¡¢¤½¤ì¤«¤é¼ÂºÝ¤ËÁÞÆþ¤ò¤¹¤ë¤³¤È¤Ç¤¹¡£<A
-HREF="#4.16.1">4.16.1</A> ¤ÎÎã¤Ç»È¤Ã¤¿¥Æ¡¼¥Ö¥ë¤ò»È¤¦¤È¤¹¤ë¤È¡¢Perl ¤Ç¤Ï
-¼¡¤Î¤è¤¦¤Ë¤Ê¤ê¤Þ¤¹¡£
-
-<PRE>
-	new_id = output of "SELECT nextval('person_id_seq')"
-	INSERT INTO person (id, name) VALUES (new_id, 'Blaise Pascal');
-</PRE>
-
-¤½¤¦¤·¤Æ¡¢<tt>new_id</tt> ¤ËÊݸ¤·¤¿¿·¤·¤¤Ãͤò¾¤ÎÌ䤤¹ç¤ï¤»¤Ë(¤¿¤È¤¨¤Ð¡¢<tt>person</tt> ¥Æ¡¼¥Ö¥ë¤ËÂФ¹¤ë³°Éô¥­¡¼(foreign key)¤Î¤è¤¦¤Ë)»È¤¦¤È¤è¤¤¤Ç¤·¤ç¤¦¡£¼«Æ°Åª¤Ëºî¤é¤ì¤¿<small>SEQUENCE</small>¥ª¥Ö¥¸¥§¥¯¥È¤Î̾Á°¤Ï¡¢&lt;<I>table</I>&gt;_&lt;<I>serialcolumn</I>&gt;_<I>seq</I> ¤Î¤è¤¦¤Ë¤Ê¤ê¡¢¤³¤Î¤¦¤Á¡¢<I>table</I> ¤È <I>serialcolumn</I> ¤Ï¤½¤ì¤¾¤ì¥Æ¡¼¥Ö¥ë¤Î̾Á°¤È<small>SERIAL</small>¥«¥é¥à¤Î̾Á°¤Ç¤¹¡£
-<P>
-
-¤¢¤ë¤¤¤Ï¡¢Í¿¤¨¤é¤ì¤¿<small>SERIAL</small>Ãͤò¡¢¤½¤ì¤¬´ûÄêÃͤȤ·¤ÆÁÞÆþ¤µ¤ì¤¿<I>¸å¤Ç(after)</I>¡¢ <I>currval</I>() ´Ø¿ô¤ò»È¤Ã¤Æ¼è¤ê½Ð¤¹¤³¤È¤â¤Ç¤­¤Þ¤¹¡£¤¿¤È¤¨¤Ð¡¢
-
-<PRE>
-	INSERT INTO person (name) VALUES ('Blaise Pascal');
-	new_id = currval('person_id_seq');
-</PRE>
-
-ºÇ¸å¤Ë¡¢<small>INSERT</small>ʸ¤«¤éÊÖ¤ë<A HREF="#4.17"><small>OID</small></A>¤ò»È¤Ã¤Æ¡¢´ûÄêÃͤò¤ß¤Ä¤±¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¤¬¡¢¤·¤«¤·¡¢¤³¤ì¤ÏºÇ¤â°Ü¿¢À­¤ÎÄ㤤¤ä¤êÊý¤Ç¤·¤ç¤¦¡£Perl¤ÎDBI¤Ç Edmund Mergl ¤Îºî¤Ã¤¿ DBD::Pg ¥â¥¸¥å¡¼¥ë¤ò»È¤¨¤Ð¡¢$sth->execute() ¤Î¸å¤Ë $sth-&gt{pg_oid_status} ¤ò·Ðͳ¤·¤Æ¤½¤Î OID Ãͤò»È¤¨¤ë¤è¤¦¤Ë¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤¹¡£
-
-<P> 
-<H4><A NAME="4.15.3">4.15.3</A>)	¾¤Î¥æ¡¼¥¶¤È¤Î¶¥¹ç¾õÂÖ¤òÈò¤±¤ë¤¿¤á¤Ë¤Ï¡¢<I>currval()</I> ¤È <I>nextval()</I> ¤Ï»È¤ï¤Ê¤¤¤Û¤¦¤¬¤è¤¤¤Î¤Ç¤·¤ç¤¦¤«¡©
-</H4>
-
-    <P>¤½¤ì¤Ï¤¢¤ê¤Þ¤»¤ó¡£Currval() ¤Ï¡¢¤¹¤Ù¤Æ¤Î¥æ¡¼¥¶¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó¤¬¡¢¤¢¤Ê¤¿¤Î¥Ð¥Ã¥¯¥¨¥ó¥É¤ËÍ¿¤¨¤é¤ì¤¿¸½ºß¤ÎÃͤòÊÖ¤·¤Þ¤¹¡£
-
-
-<H4><A name="4.15.4">4.15.4</A>) ¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤¬ÃæÃǤ·¤¿¤È¤­¤Ë¤â¤¦¤¤
-¤Á¤É¥·¡¼¥±¥ó¥¹Èֹ椬»È¤ï¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©¥·¡¼¥±¥ó¥¹¡¿SERIAL¥«¥é¥à¤Ë
-¶õ¤­¤¬¤¢¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-
-    <P>Ʊ»þÀ­¤ò²þÁ±¤¹¤ë¤¿¤á¤Ë¡¢¼Â¹ÔÃæ¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤Ë¡¢É¬ÍפǥÈ
-¥é¥ó¥¶¥¯¥·¥ç¥ó¤¬½ªÎ»¤¹¤ë¤Þ¤Ç¥í¥Ã¥¯¤µ¤ì¤Ê¤¤¥·¡¼¥±¥ó¥¹ÃͤòÍ¿¤¨¤Æ¤¤¤Þ¤¹¡£
-¤³¤Î¤¿¤á¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤¬ÃæÃǤµ¤ì¤ë¤ÈÈÖ¹æ³ä¤êÅö¤Æ¤Ë¥®¥ã¥Ã¥×¤òÀ¸¤¸¤Þ¤¹¡£
-</P>
-
-<P> 
-<H4><A NAME="4.16">4.16</A>)	<small>OID</small> ¤È¤Ï²¿¤Ç¤¹¤«¡© <small>TID</small> ¤È¤Ï²¿¤Ç¤¹¤«¡©
-</H4>
-
-<P> <small>OID</small> ¤È¤Ï°ì°Õ¤Î¥í¥¦ID ¤ËÂФ¹¤ë PostgreSQL ¤ÎÅú¤¨¤Ç¤¹¡£PostgreSQL ¤ÎÃæ¤Ç¤Ä¤¯¤é¤ì¤ë¤¹¤Ù¤Æ¤Î¥í¥¦¤Ï°ì°Õ¤Î <small>OID</small> ¤òÆÀ¤Þ¤¹¡£<I>initdb</I> ¤ÇȯÀ¸¤µ¤ì¤ë <small>OID</small> ¤Ï¤¹¤Ù¤Æ 16384 (<I>backend/access/transam.h</I> ¤«¤é)¤è¤ê¾®¤µ¤ÊÃͤǤ¹¡£<I>initdb</I> ¸å¤Î¤¹¤Ù¤Æ¤Î <small>OID</small> (¥æ¡¼¥¶ºîÀ®)¤Ï¤½¤ì°Ê¾å¤ÎÃͤˤʤê¤Þ¤¹¡£
-´ûÄê¤Ç¤Ï¡¢¤³¤ì¤é¤¹¤Ù¤Æ¤Î <small>OID</small>¤Ï°ì¤Ä¤Î¥Ç¡¼¥Ö¥ë¤ä¥Ç¡¼¥¿¥Ù¡¼¥¹Æâ¤Ëα¤Þ¤é¤º¡¢PostgreSQL ¥¤¥ó¥¹¥È¥ì¡¼¥·¥ç¥óÁ´ÂΤÎÃæ¤Ç°ì°Õ¤Ç¤¹¡£
-
-<P> PostgreSQL ¤Ï¥Æ¡¼¥Ö¥ë´Ö¤Î¥í¥¦¤ò·ë¤Ó¤Ä¤±¤ë¤¿¤á¤Ë¡¢¤½¤Î¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ëÆâ¤Ë <small>OID</small> ¤ò»È¤¤¤Þ¤¹¡£¤³¤Î <small>OID</small> ¤ÏÆÃÄê¤Î¥æ¡¼¥¶¤Î¥í¥¦¤ò¼±Ê̤¹¤ë¤¿¤á¤ä·ë¹ç¤ÎÃæ¤Ç»È¤ï¤ì¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£<small>OID</small> ¤ÎÃͤòÊݸ¤¹¤ë¤¿¤á¤Ë¤Ï <I>OID</I> ·¿¤ò¥«¥é¥à¤Ë»È¤¦¤³¤È¤ò¾©¤á¤Þ¤¹¡£¤è¤ê®¤¯¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë <I>OID</I> ¥Õ¥£¡¼¥ë¥É¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹¤òºî¤ë¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£
-
-  O<small>ID</small> ¤Ï¡¢Á´¤Æ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ç»È¤ï¤ì¤ëÃæ±ûÎΰ褫¤é¡¢Á´¤Æ¤Î¿·¤·¤¤¥í¥¦¤Ë³ä¤êÅö¤Æ¤é¤ì¤Þ¤¹¡£<small>OID</small> ¤ò¾¤Î²¿¤«¤ËÊѤ¨¤¿¤¤¡¢¤¢¤ë¤¤¤Ï¸µ¤Î <small>OID</small> ¤â¥Æ¡¼¥Ö¥ë¤È°ì½ï¤Ë¥³¥Ô¡¼¤·¤¿¤¤¤Î¤Ê¤é¡¢¤Ç¤­¤Ê¤¯¤Ï¤¢¤ê¤Þ¤»¤ó¡£
-
-
-<PRE>
-        CREATE TABLE new (old_oid oid, mycol int);
-        SELECT old_oid, mycol INTO new FROM old;
-        COPY new TO '/tmp/pgtable';
-        DELETE FROM new;
-        COPY new WITH OIDS FROM '/tmp/pgtable';
-<!--
-	CREATE TABLE new_table (mycol int);
-	INSERT INTO new_table (oid, mycol) SELECT oid, mycol FROM old_table;
--->
-</PRE>
-
-<P> O<small>ID</small> ¤Ï¡¢4¥Ð¥¤¥È¤ÎÀ°¿ô¤È¤·¤ÆÊݸ¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢40²¯¤ò±Û¤¨¤ë¤È°î¤ì¤Æ¤·¤Þ¤¦¤Ç¤·¤ç¤¦¡£Ã¯¤â¤³¤ì¤¬µ¯¤­¤¿¤ÈÊó¹ð¤·¤Æ¤¯¤ë¿Í¤Ï¤¤¤Þ¤»¤ó¤Ç¤·¤¿¤¬¡¢¤½¤¦¤Ê¤ëÁ°¤Ë¤³¤ÎÀ©¸Â¤ò¼è¤ê½ü¤¯¤³¤È¤ò·×²è¤·¤Æ¤¤¤Þ¤¹¡£
-
-<P> T<small>ID</small> ¤ÏÆÃÄê¤ÎʪÍý¥í¥¦¤ò¤½¤Î¥Ö¥í¥Ã¥¯¤È¥ª¥Õ¥»¥Ã¥ÈÃͤǼ±Ê̤¹¤ë¤¿¤á¤Ë»È¤ï¤ì¤Þ¤¹¡£<small>TID</small> ¤Ï¥í¥¦¤¬½¤Àµ¤µ¤ì¤¿¤êºÆ¥í¡¼¥É¤µ¤ì¤ë¤ÈÊѤï¤ê¤Þ¤¹¡£¤½¤ì¤é¤Î <small>TID</small> ¤Ï¡¢ÊªÍý¥í¥¦¤ò»Ø¤¹¤¿¤á¤Ë¥¤¥ó¥Ç¥Ã¥¯¥¹µ­ºÜ¤Ç»È¤ï¤ì¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="4.17">4.17</A>)	PostgreSQL ¤Ç»È¤ï¤ì¤ë¤¤¤¯¤Ä¤«¤ÎÍѸì¤Î°ÕÌ£¤Ï²¿¤Ç¤¹¤«¡©
-</H4>
-
-<P> ¤¤¤¯¤Ä¤«¤Î¥½¡¼¥¹¥³¡¼¥É¤ä¸Å¤¤Ê¸½ñ¤ÎÃæ¤Ë¤Ï¡¢¤½¤ì¤¾¤ÎÀìÌçʬÌî¤ÎÃæ¤Ç¤â¤Ã¤È°ìÈÌŪ¤Ë»È¤ï¤ì¤ëÀìÌçÍѸ줬»È¤ï¤ì¤Æ¤¤¤Þ¤¹¡£
-
-<UL>
-<LI> ¥Æ¡¼¥Ö¥ë(table)¡¢´Ø·¸(relation)¡¢¥¯¥é¥¹(class)
-<LI> ¥í¥¦(row)¡¢¥ì¥³¡¼¥É(record)¡¢¥¿¥Ã¥×¥ë(tuple)
-<LI> ¥«¥é¥à(column)¡¢¥Õ¥£¡¼¥ë¥É(field)¡¢Â°À­(attribute)
-<LI> ¼èÆÀ(retrieve)¡¢ÁªÂò(select)
-<LI> ÃÖ´¹(replace)¡¢¹¹¿·(update)
-<LI> ÄɲÃ(append)¡¢ÁÞÆþ(insert)
-<LI> <small>OID</small>, Ï¢ÈÖ(serial value)
-<LI> ¥Ý¡¼¥¿¥ë(portal), ¥«¡¼¥½¥ë(cursor)
-<LI> ÎΰèÊÑ¿ô(range variable)¡¢¥Æ¡¼¥Ö¥ë̾(table name)¡¢¥Æ¡¼¥Ö¥ëÊÌ̾(table alias)
-</UL>
-<P>°ìÈÌŪ¤Ê¥Ç¡¼¥¿¥Ù¡¼¥¹ÍѸì¤Î¥ê¥¹¥È¤Ï¡§<a
-href="http://www.comptechnews.com/~reaster/dbdesign.html">
-http://www.comptechnews.com/~reaster/dbdesign.html</a>
-¤Ç¸«¤Ä¤±¤é¤ì¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="4.18">4.18</A>) ¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸ <I>"ERROR: Memory exhausted in AllocSetAlloc()"</I>¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-<P>
-¤â¤·¡¢7.1 ¤è¤ê¤â¸Å¤¤¥Ð¡¼¥¸¥ç¥ó¤ò¤ª»È¤¤¤Î¾ì¹ç¤Ï¡¢¥¢¥Ã¥×¥Ç¡¼¥È¤Ë¤è¤Ã¤Æ¤³¤ÎÌäÂê¤ò
-²ò·è¤Ç¤­¤ë¤Ç¤·¤ç¤¦¡£¤½¤ì¤È¡¢¥·¥¹¥Æ¥à¤Î²¾ÁÛ¥á¥â¥ê¡¼¤òÁ´¤Æ»È¤¤²Ì¤¿¤·¤Æ¤·¤Þ¤Ã¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ë¤«¡¢¥«¡¼¥Í¥ë¤¬¤¢¤ë¥ê¥½¡¼¥¹¤Ë¤Ä¤¤¤Æ¤â¤ÄÀ©¸ÂÃͤ¬Ä㤹¤®¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£
-<I>postmaster</I> ¤ò»ÏÆ°¤¹¤ëÁ°¤Ë¤³¤ì¤ò»î¤·¤Æ¤ß¤Æ²¼¤µ¤¤¡§
-
-<PRE>
-	ulimit -d 262144
-	limit datasize 256m
-</PRE>
-
-<P> 
-¥·¥§¥ë¤Ë¤è¤Ã¤Æ¡¢¤É¤Á¤é¤«¤Ò¤È¤Ä¤¬À®¸ù¤¹¤ë¤Ç¤·¤ç¤¦¤¬¡¢¤³¤ì¤Ï¥×¥í¥»¥¹¤Î¥Ç¡¼¥¿¥»¥°¥á¥ó¥ÈÀ©¸Â¤ò¤è¤ê¹â¤¯ÀßÄꤷ¡¢¤¿¤Ö¤óÌ䤤¹ç¤ï¤»¤¬´°·ë¤¹¤ë¤è¤¦¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£¤³¤Î¥³¥Þ¥ó¥É¤Ï¸½¹Ô¤Î¥×¥í¥»¥¹¤È¡¢¤³¤Î¥³¥Þ¥ó¥É¤òÁö¤é¤»¤¿¸å¤Ëºî¤é¤ì¤ëÁ´¤Æ¤Î¥µ¥Ö¥×¥í¥»¥¹¤Ë¤Ä¤¤¤ÆŬÍѤµ¤ì¤Þ¤¹¡£¥Ð¥Ã¥¯¥¨¥ó¥É¤¬¤È¤Æ¤â¿¤¯¤Î¥Ç¡¼¥¿¤òÊÖ¤¹¤¿¤á¤Ë<small>SQL</small> ¥¯¥é¥¤¥¢¥ó¥È¤ÇÌäÂ꤬³¤¤¤Æ¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢¥¯¥é¥¤¥¢¥ó¥È¤ò³«»Ï¤¹¤ëÁ°¤Ë¤³¤ì¤ò»î¤·¤Æ¤ß¤Æ¤¯¤À¤µ¤¤¡£
-
-<P>
-<H4><A NAME="4.19">4.19</A>) ¤É¤Î¥Ð¡¼¥¸¥ç¥ó¤Î PostgreSQL ¤òÁö¤é¤»¤Æ¤¤¤ë¤«¤òÄ´¤Ù¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<BR>
-</H4>
-<P>
-<I>psql</I> ¤«¤é <tt>select version();</tt> ¤ò¥¿¥¤¥×¤·¤Þ¤¹¡£
-<P>
-
-
-<H4><A NAME="4.20">4.20</A>)	¥é¡¼¥¸¡¦¥ª¥Ö¥¸¥§¥¯¥È¤ÎÁàºî¤Ç<I>invalid large obj descriptor</I> ¤ò¼õ¤±¼è¤ê¤Þ¤·¤¿¡£¤Ê¤¼¤Ç¤·¤ç¤¦¤«¡©
-</H4>
-
-<P>¥é¡¼¥¸¡¦¥ª¥Ö¥¸¥§¥¯¥ÈÁàºî¤ò¤¹¤ë¤È¤­¤Ï¡¢Á°¸å¤Ë<tt>BEGIN WORK</tt>¤È<tt>COMMIT</tt>¤òÉÕ¤±¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£¤¹¤Ê¤ï¤Á¡¢<tt>lo_open</tt> ... <tt>lo_close</tt>¤ò¤Ï¤µ¤ß¹þ¤ß¤Þ¤¹¡£
-
-<P>¸½ºß¤Ï¡¢PostgreSQL¤Î¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤Î¥³¥ß¥Ã¥È»þ¤Ë¥é¡¼¥¸¡¦¥ª¥Ö¥¸¥§¥¯¥È¡¦¥Ï¥ó¥É¥ë¤òÊĤ¸¤ë¤³¤È¤Ë¤è¤ê¡¢<I>lo_open</I>¥³¥Þ¥ó¥É¤¬´°Î»¤·¤¿Ä¾¸å¤Ë¶¯À©Åª¤Ë¥ë¡¼¥ë¤ò¼Â¹Ô¤·¤Þ¤¹¡£¤³¤Î¤¿¤á¡¢ºÇ½é¤Ë¥Ï¥ó¥É¥ë¤ËÂФ·¤Æ²¿¤«¤ò¤·¤è¤¦¤È¤¹¤ë¤È¡¢<I>invalid large obj descriptor(¥é¡¼¥¸¡¦¥ª¥Ö¥¸¥§¥¯¥È¤Îµ­½Ò»Ò¤¬ÉÔÀµ)</I>¤È¤Ê¤ê¤Þ¤¹¡£¤½¤ì¤Ç¡¢¤â¤·¡¢¥È¥é¥ó¥¶¥¯¥·¥ç¥ó¤ò»È¤¦¤Î¤ò˺¤ì¤ë¤È¡¢¡Ê¾¯¤Ê¤¯¤È¤â¤Û¤È¤ó¤É¤Î»þ´Ö¡ËƯ¤¤¤Æ¤¤¤¿¥³¡¼¥É¤¬¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤ò½Ð¤¹¤Î¤Ç¤¹¡£
-
-<P>¤â¤·¡¢<small>ODBC</small>¤Î¤è¤¦¤Ê¥¯¥é¥¤¥¢¥ó¥È¥¤¥ó¥¿¡¼¥Õ¥§¡¼¥¹¤ò¤ª»È¤¤¤Ê¤é¡¢<tt>auto-commit off</tt>¤òÀßÄꤹ¤ëɬÍפ¬¤¢¤ë¤«¤â¤·¤ì¤Þ¤»¤ó¡£
-<P>
-
-
-<H4><A NAME="4.21">4.21</A>) ¸½ºß¤Î»þ¹ï¤¬¥Ç¥Õ¥©¥ë¥È¤È¤Ê¤ë¤è¤¦¤Ê¥«¥é¥à¤Ï¤É¤Î¤è¤¦¤Ë¤Ä¤¯¤ê¤Þ¤¹¤«¡©<BR></H4>
-
-<P><i>CURRENT_TIMESTAMP</i>¤ò»È¤¤¤Þ¤¹:
-<PRE>
-	CREATE TABLE test (x int, modtime timestamp DEFAULT >CURRENT_TIMESTAMP );
-</PRE>
-<P>
-
-
-<H4><A NAME="4.22">4.22</A>)	¤Ê¤¼¡¢<small>IN</small>¤ò»È¤¦ÉûÌ䤤¹ç¤ï¤»¤¬¤È¤Æ¤âÃÙ¤¤¤Î¤Ç¤¹¤«¡©
-</H4>
-<P>
-¸½ºß¡¢³°ÉôÌ䤤¹ç¤ï¤»¤Î³Æ¥í¥¦¤Ë¤Ä¤¤¤ÆÉûÌ䤤¹ç¤ï¤»¤Î·ë²Ì¤ò½çÈ֤˥¹¥­¥ã¥ó¤¹¤ë¤³¤È¤Ë¤è¤ê¡¢ÉûÌ䤤¹ç¤ï¤»¤ò³°ÉôÌ䤤¹ç¤ï¤»¤Ë·ë¹ç¤·¤Æ¤¤¤Þ¤¹¡£ÅöÌ̤Ï<small>IN</small>¤ò<small>EXIST</small>S¤ÇÃÖ¤­´¹¤¨¤ë¤³¤È¤Ç¤¹¡§
-<PRE>
-	<STRONG>SELECT *</STRONG>
-	FROM tab
-	WHERE col1 IN (SELECT col2 FROM TAB2)
-</PRE>
-¤ò¡¢ÃÖ¤­´¹¤¨¤Æ¡§
-<PRE>
-	SELECT *
-	FROM tab
-	WHERE EXISTS (SELECT col2 FROM TAB2 WHERE col1 = col2)
-</PRE>
-¤È¤·¤Þ¤¹¡£
-¤³¤ÎÀ©¸Â¤Ï¾­Íè¤Î¥ê¥ê¡¼¥¹¤Çľ¤·¤¿¤¤¤È»×¤Ã¤Æ¤¤¤Þ¤¹¡£
-<P>
-
-<H4><A NAME="4.23">4.23</A>) <i>³°Éô</i>·ë¹ç(<i>outer</i> join)¤Ï¤É¤Î¤è¤¦¤Ë¼Â¸½¤·¤Þ¤¹¤«?<BR></H4>
-<P>
-PostgreSQL 7.1 °Ê¹ß¤Ç¤Ï<small>SQL</small>ɸ½à¹½Ê¸¤ò»È¤¦³°Éô·ë¹ç(¥¢¥¦¥¿¡¼¥¸¥ç¥¤¥ó)¤ò¥µ¥Ý¡¼¥È¤·¤Þ¤¹¡£¤³¤³¤Ë¡¢ÎãÂ꤬2¤Ä¤¢¤ê¤Þ¤¹¡£
-
-<pre>
-<STRONG>SELECT *</STRONG>
- FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);</pre>
-¤¢¤ë¤¤¤Ï
-<pre>
-<STRONG>SELECT *</STRONG>
- FROM t1 LEFT OUTER JOIN t2 USING (col);</pre>
-
-¤³¤ì¤é¤Î¾ÝħŪ¤ÊÌ䤤¹ç¤ï¤»¤Ç¤Ï t1.col ¤ò t2.col ¤È·ë¹ç¤·¤Æ¡¢t1 ¤Î·ë¹ç¤µ¤ì¤Ê¤«¤Ã¤¿¥í¥¦(t2 ¤È°ìÃפ·¤Ê¤«¤Ã¤¿¥í¥¦)¤âÊÖ¤·¤Æ¤¤¤Þ¤¹¡£<small>RIGHT</small> ·ë¹ç¤Ï t2 ¤Î·ë¹ç¤µ¤ì¤Ê¤«¤Ã¤¿¥í¥¦¤ò²Ã¤¨¤ë¤Ç¤·¤ç¤¦¡£<small>FULL</small> ·ë¹ç¤Ï¡¢°ìÃפ·¤¿¥í¥¦¤Ë t1 ¤È t2 ¤«¤é¤Ï·ë¹ç¤µ¤ì¤Ê¤«¤Ã¤¿¥í¥¦¤òÊÖ¤¹¤Ç¤·¤ç¤¦¡£<small>OUTER</small> ¤È¤¤¤¦¸ÀÍդϥª¥×¥·¥ç¥ó¤Ç <small>LEFT</small>, <small>RIGHT</small>, ¤Þ¤¿¤Ï <small>FULL</small> ¤Ê¤É¤Î·ë¹ç¤ò²¾Äꤵ¤ì¤Æ¤¤¤Þ¤¹¡£
-
-°ÊÁ°¤Î¥ê¥ê¡¼¥¹¤Ç¤Ï³°Éô·ë¹ç(outer join)¤ò<small>UNION</small> ¤È <small>NOT IN</small> ¤ò»È¤Ã¤Æ¥·¥ß¥å¥ì¡¼¥È¤Ç¤­¤Þ¤¹¡£
-¤¿¤È¤¨¤Ð¡¢<i>tab1</i> ¤È <i>tab2</i> ¤ò·ë¹ç¤¹¤ë¤È¤­¤Ï¡¢¼¡¤ÎÌ䤤¹ç¤ï¤»¤ÇÆó¤Ä¤Î¥Æ¡¼¥Ö¥ë¤ò<i>³°Éô</i>·ë¹ç¤·¤Þ¤¹¡£
-
-<PRE>
-	SELECT tab1.col1, tab2.col2
-	FROM tab1, tab2
-	WHERE tab1.col1 = tab2.col1
-<STRONG>UNION ALL</STRONG>
-	SELECT tab1.col1, NULL
-	FROM tab1
-	WHERE tab1.col1 NOT IN (SELECT tab2.col1 FROM tab2)
-	ORDER BY col1
-</PRE>
-
-<P>
-<H4><A NAME="4.24">4.24</A>)  Ê£¿ô¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»È¤¦Ì䤤¹ç¤ï¤»¤Ï¤É¤Î¤è¤¦¤Ë¤¹¤ì¤Ð¤Ç¤­¤Þ¤¹¤«¡©<BR></H4>
-
-<P>
-¸½¹Ô(current)¤ò½ü¤¤¤Æ¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ø¤ÎÌ䤤¹ç¤ï¤»ÊýË¡¤Ï¤¢¤ê¤Þ¤»¤ó¡£¤È¤¤¤¦¤Î¤âPostgreSQL¤¬¥Ç¡¼¥¿¥Ù¡¼¥¹»ÅÍͤΥ·¥¹¥Æ¥à¥«¥¿¥í¥°¤òÆɤ߹þ¤à¤¿¤á¤Ç¡¢¤½¤³¤Ë¤Ï¡¢¤¿¤È¤¨¤½¤Î¤Õ¤ê¤ò¤¹¤ë¤À¤±¤Ë¤·¤í¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò±Û¤¨¤ÆÌ䤤¹ç¤ï¤»¤ò¤¹¤ë¤¹¤Ù¤¬¤¢¤ê¤Þ¤»¤ó¡£
-<P>
-¤â¤Á¤í¤ó¡¢¥¯¥é¥¤¥¢¥ó¥È¤ÏƱ»þ¤Ë°Û¤Ê¤ëÊ£¿ô¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ØÀܳ¤·¤Æ¤½¤³¤Ë¤¢¤ë¾ðÊó¤ò¥Þ¡¼¥¸¤¹¤ë¤³¤È¤Ï¤Ç¤­¤Þ¤¹¡£
-
-<P>
-<H4><A NAME="4.25">4.25</A>) ´Ø¿ô¤ÇÊ£¿ô¤Î¥í¥¦¤Þ¤¿¤Ï¥«¥é¥à¤òÊÖ¤¹¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<BR></H4>
-
-     <P>¤â¤·¡¢PL/pgSQL ´Ø¿ô¤Ç<i>refcursors</i>¤ò»È¤¦¤È·ë²Ì¤ÎÁȤòÊÖ¤¹¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£<a
-href="http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html">
-http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html</a> ¤Î
-23.7.3.3 Àá¤ò¤´Í÷²¼¤µ¤¤¡£</P>
-
-
-<P>
-<HR>
-<H2><CENTER>PostgreSQL¤Î³ÈÄ¥¤Ë¤Ä¤¤¤Æ¤Î¼ÁÌä</CENTER></H2>
-<P>
-
-<H4><A NAME="5.1">5.1</A>)	¼«Ê¬¤Ç½ñ¤¤¤¿¥æ¡¼¥¶ÄêµÁ´Ø¿ô¤ò psql ¤ÎÃæ¤Ç¼Â¹Ô¤¹¤ë¤È¥³¥¢¡¦¥À¥ó¥×¤·¤Æ¤·¤Þ¤¦¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-
-<P> ÌäÂê¤Ï¿§¡¹¤È¹Í¤¨¤é¤ì¤Þ¤¹¤¬¡¢¤Þ¤ººÇ½é¤Ë¡¢ºîÀ®¤·¤¿¥æ¡¼¥¶ÄêµÁ´Ø¿ô¤òñÆȤΥƥ¹¥È¥×¥í¥°¥é¥à¤Ë¤·¤Æ»î¤·¤Æ¤ß¤Æ²¼¤µ¤¤¡£
-
-
-<P>
-<H4><A NAME="5.2">5.2</A>)	PostgreSQL ÍѤ˽ñ¤¤¤¿¤Á¤ç¤Ã¤ÈÁÇŨ¤Ê¿·¤·¤¤·¿¤ä´Ø¿ô¤òÄ󶡤·¤Æ¥×¥í¥¸¥§¥¯¥È¤Ë¹×¸¥¤·¤¿¤¤¤Î¤Ç¤¹¤¬¡©
-</H4>
-
-<P> ³§¤µ¤ó¤Î¹Ô¤Ê¤Ã¤¿³ÈÄ¥¤ò¡¢<I>pgsql-hackers</I> ¥á¡¼¥ê¥ó¥°¡¦¥ê¥¹¥È¤ËÁ÷¤Ã¤Æ¤¯¤À¤µ¤¤¡£¤½¤·¤Æ¡¢¤æ¤¯¤æ¤¯¤Ï¤½¤¦¤·¤¿³ÈÄ¥¤¬ <I>contrib/</I> ¥µ¥Ö¥Ç¥£¥ì¥¯¥È¥ê¤ÎÃæ¤ËÆþ¤ë¤³¤È¤Ë¤Ê¤ë¤Ç¤·¤ç¤¦¡£
-
-<P>
-<H4><A NAME="5.3">5.3</A>)	¥¿¥×¥ë¤òÊÖ¤¹ C¸À¸ì¤Î´Ø¿ô¤Ï¤É¤Î¤è¤¦¤Ë½ñ¤­¤Þ¤¹¤«¡©
-</H4>
-
-<P> ¸¶ÍýŪ¤Ë¤Ï²Äǽ¤Ç¤¹¤¬¡¢¤³¤ì¤Ë¤Ïµæ¶Ë¤Î̯µ»¤òÍפ·¤Þ¤¹¤Î¤Ç¡¢Ãø¼Ô¤Î¤Þ¤ï¤ê¤Ç¤Ï̤¤Àï¤â¤ä¤Ã¤¿¤³¤È¤¬¤¢¤ê¤Þ¤»¤ó¡£
-
-<P><H4><A NAME="5.4">5.4</A>)	¥½¡¼¥¹¡¦¥Õ¥¡¥¤¥ë¤òÊѹ¹¤·¤Þ¤·¤¿¡£ºÆ¥³¥ó¥Ñ¥¤¥ë¤·¤Æ¤âÊѲ½¤¬¸«¤é¤ì¤Ê¤¤¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
-</H4>
-
-<P> ¤¤¤¯¤Ä¤«¤Î <I>Makefile</I> ¤¬¥¤¥ó¥¯¥ë¡¼¥É¡¦¥Õ¥¡¥¤¥ë¤ËÂФ·¤ÆŬÀڤʰ͸´Ø·¸¤ò»ý¤Ã¤Æ¤¤¤Þ¤»¤ó¡£<I>make clean</I> ¤ò¤·¤Æ¤«¤é¤â¤¦°ìÅÙ <I>make</I> ¤ò¹Ô¤Ê¤ï¤Ê¤¯¤Æ¤Ï¤Ê¤ê¤Þ¤»¤ó¡£¤â¤·¡¢<small>GCC</small> ¤ò¤ª»È¤¤¤Ç¤¢¤ì¤Ð <i>configure</i> ¤Î <i>--enable-depend</i> ¥ª¥×¥·¥ç¥ó¤ò»È¤Ã¤Æ¡¢¥³¥ó¥Ñ¥¤¥é¤Ë°Í¸´Ø·¸¤ò¼«Æ°Åª¤ËÄ´¤Ù¤µ¤»¤ë¤³¤È¤â¤Ç¤­¤Þ¤¹¡£
-
-
-<HR>
-
-<small><PRE>
-[ÌõÃí¡§
-  ÆüËܸìÈǤÎÀ½ºî¤Ë¤Ä¤¤¤Æ¤Ï°Ê²¼¤ÎÄ̤ê¤Ç¤¹¡£
-
-  ºÇ½ª¹¹¿·Æü:	2002ǯ05·î08Æü
-  ËÝÌõ¼Ô:	·¬Â¼ ½á (<A HREF="mailto:juk@postgresql.jp">Jun Kuwamura &lt;juk@postgresql.jp&gt;</A>)
-
-  ¤³¤ÎFAQ¤ÎÏÂÌõ¤ÎºîÀ®¤Ë¤¢¤¿¤ê¶¨ÎϤò¤·¤Æ¤¯¤À¤µ¤Ã¤¿Êý¡¹(·É¾Î¤Ïά¤µ¤»¤Æ¤¤¤¿¤À¤­¤Þ¤¹):
-
-		ÅÄÃç Ì­(<A HREF="mailto:Tanaka.Minoru@keiken.co.jp">Minoru Tanaka &lt;Tanaka.Minoru@keiken.co.jp&gt;</A>)
-		Àаæ ãÉ×(<A HREF="mailto:t-ishii@sra.co.jp">Tatsuo Ishii &lt;t-ishii@sra.co.jp&gt;</A>)
-		óîÆ£ ÃοÍ(<A HREF="mailto:tomos@elelab.nsc.co.jp">Tomohito Saitoh &lt;tomos@elelab.nsc.co.jp&gt;</A>)
-		ÇÏ¾ì  È¥(<A HREF="mailto:baba@kusastro.kyoto-u.ac.jp">Hajime Baba &lt;baba@kusastro.kyoto-u.ac.jp&gt;</A>)
-		²¬ËÜ °ì¹¬(<A HREF="mailto:kokamoto@itg.hitachi.co.jp">Kazuyuki Okamoto &lt;kokamoto@itg.hitachi.co.jp&gt;</A>)
-		¾®¿û ¾¼°ì(<A HREF="mailto:s-kosuge@str.hitachi.co.jp">Shoichi Kosuge &lt;s-kosuge@str.hitachi.co.jp&gt;</A>)
-		»³²¼ µÁÇ·(<A HREF="mailto:dica@eurus.dti.ne.jp">Yoshiyuki Yamashita &lt;dica@eurus.dti.ne.jp&gt;</A>)
-		¶­ ¿¿ÂÀϺ(<A HREF="mailto:s_sakai@mxn.mesh.ne.jp">Sintaro Sakai &lt;s_sakai@mxn.mesh.ne.jp&gt;</A>)
-		À¸±Û ¾»¸Ê(<A HREF="mailto:ogochan@zetabits.com">Masami Ogoshi &lt;ogochan@zetabits.com&gt;</A>)
-		ÀÐÀî ½Ó¹Ô(<A HREF="mailto:tosiyuki@gol.com">Toshiyuki Ishikawa &lt;tosiyuki@gol.com&gt;</A>)
-		ËÜÅÄ Ìй­(<A HREF="mailto:fwif0083@mb.infoweb.ne.jp">Shigehiro Honda &lt;fwif0083@mb.infoweb.ne.jp&gt;</A>)
-		¤»¤» ¤¸¤å¤ó(<A HREF="mailto:sesejun@linet.gr.jp">Jun Sese &lt;sesejun@linet.gr.jp&gt;</A>)
-		¿Àë ±Ñ¹§(<A HREF="mailto:hkamiya@catvmics.ne.jp">Hidetaka Kamiya &lt;hkamiya@catvmics.ne.jp&gt;</A>)
-
-  ¤ò¤Ï¤¸¤á¡¢¥Ý¥¹¥È¥°¥ì¥¹¤Ë´Ø¤¹¤ëÏÃÂêË­ÉÙ¤Ê<A HREF="http://www.sra.co.jp/people/t-ishii/PostgreSQL/ML/info.html">ÆüËܸì¥Ý¥¹¥È¥°¥ì¥¹¡¦¥á¡¼¥ê¥ó¥°¥ê¥¹¥È</A>¡¢
-  ÏÂÌõ¤Î¤­¤Ã¤«¤±¤òºî¤Ã¤Æ¤¯¤ì¤¿ <A HREF="http://jf.linux.or.jp/">JF(Linux Japanese FAQ Mailing List)¥×¥í¥¸¥§¥¯¥È</A>¡¢¤½¤Î¾¡¢
-  ľÀܤ¢¤ë¤¤¤Ï´ÖÀÜŪ¤Ë¤«¤«¤ï¤Ã¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î¥ª¡¼¥×¥ó¥½¡¼¥¹¥³¥ß¥å¥Ë¥Æ¥£¡¼¤Î
-  ³§¤µ¤ó¤Ë´¶¼Õ¤·¤Þ¤¹¡£
-
-
-  ÆüËܸìÈǤΤ³¤Îʸ½ñ¤Ï¡¢°Ê²¼¤«¤é¤â¤¿¤É¤ì¤Þ¤¹¡£
-	<A HREF="http://www.rccm.co.jp/~juk/pgsql/">http://www.rccm.co.jp/~juk/pgsql/</A>(FAQÏÂÌõ PostgreSQL ¤Ë¤Ä¤¤¤Æ¤è¤¯¤¢¤ë¼ÁÌä)
-	<A HREF="http://www.linux.or.jp/JF/">http://www.linux.or.jp/JF/</A>(PostgreSQL-FAQ.j)
-	<A HREF="http://www.sra.co.jp/people/t-ishii/PostgreSQL/doc-jp/">http://www.sra.co.jp/people/t-ishii/PostgreSQL/doc-jp/</A>
-
-  ¤Ê¤ª¡¢¤³¤ÎÏÂÌõ¤Ë´Ø¤¹¤ë¤´°Õ¸«¤Ï(<A HREF="mailto:juk@postgresql.jp">juk@postgresql.jp</A>)¤Þ¤Ç¤ª´ó¤»²¼¤µ¤¤¡£
-]
-</PRE></small>
-
-</BODY>
-</HTML>
diff --git a/doc/src/FAQ/FAQ_polish.html b/doc/src/FAQ/FAQ_polish.html
deleted file mode 100644
index 56a052cf66f..00000000000
--- a/doc/src/FAQ/FAQ_polish.html
+++ /dev/null
@@ -1,1448 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD html 4.01 transitional//EN">
-
-<HTML>
-  <!-- DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN" -->
-  <!-- HTML -->
-
-  <HEAD>
-    <META name="generator" content="HTML Tidy, see www.w3.org">
-	 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2">
-    <TITLE>PostgreSQL FAQ</TITLE>
-  </HEAD>
-
-  <BODY bgcolor="#ffffff" text="#000000" link="#ff0000" vlink="#a00000"
-  alink="#0000ff">
-
-	<H1>Frequently Asked Questions (FAQ) o PostgreSQL</H1>
-
-    <P>Ostatnia aktualizacja: Thu Apr 18 00:44:51 EDT 2002</P>
-
-    <P>Obecny maintainer: Bruce Momjian (<A href=
-    "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
-    </P>
-    <P>T³umaczenie: Marcin Mazurek (<A href=
-    "mailto:m.mazurek@netsync.pl">m.mazurek@netsync.pl</A>)<BR>
-    </P>
-
-
-    <P>Najbardziej aktualn± wersjê tego dokumentu mo¿na znale¼æ pod
-	 adresem:
-	 <A href=
-    "http://www.Postgresql.org/docs/faq-english.html">http://www.PostgreSQL.org/docs/faq-english.html</A>.</P>
-
-    <P>Odpowiedzi na pytania dotycz±ce konkretnych systemów operacyjnych
-	 mo¿na znale¼æ pod adresem: 
-	 <A href=
-    "http://www.PostgreSQL.org/users-lounge/docs/faq.html">http://www.PostgreSQL.org/users-lounge/docs/faq.html</A>.</P>
-    <HR>
-
-    <H2 align="center">Pytania ogólne</H2>
-    <A href="#1.1">1.1</A>) Co to jest PostgreSQL? Jak to wymawiaæ?<BR>
-     <A href="#1.2">1.2</A>) Jak± licencj± chroniony jest PostgreSQL?<BR>
-     <A href="#1.3">1.3</A>) Na jakich systemach Unixowych dzia³a
-	  PostreSQL?<BR>
-     <A href="#1.4">1.4</A>) Na jakich nie-Unixowych systemach dzia³a
-	  PostgreSQL?<BR>
-     <A href="#1.5">1.5</A>) Sk±d mogê ¶ci±gn±æ PostgreSQL?<BR>
-     <A href="#1.6">1.6</A>) Gdzie mo¿na szukaæ wsparcia technicznego?<BR>
-     <A href="#1.7">1.7</A>) Jaka jest ostatnia dostêpna wersja?<BR>
-     <A href="#1.8">1.8</A>) Jaka dokumentacja jest dostêpna?<BR>
-     <A href="#1.9">1.9</A>) Gdzie mogê znale¼æ informacjê o znanych
-	  b³êdach czy brakuj±cych rozwi±zanich?<BR>
-     <A href="#1.10">1.10</A>) Jak mogê siê nauczyæ <SMALL>SQL</SMALL>?<BR>
-     <A href="#1.11">1.11</A>) Czy PostgreSQL ma rozwi±zany problem Y2K?<BR>
-     <A href="#1.12">1.12</A>) Jak mogê siê przy³±czyæ do grupy osób
-	  bezpo¶rednio pracuj±cych nad rozwojem PostgreSQL?<BR>
-     <A href="#1.13">1.13</A>) Jak mogê zg³aszaæ b³êdy?<BR>
-     <A href="#1.14">1.14</A>) Jak mo¿na porównaæ PostgreSQL w stosunku
-	  do innych <SMALL>DBMS</SMALL>?<BR>
-     <A href="#1.15">1.15</A>) W jaki sposób mogê wesprzeæ finansowo
-    PostgreSQL?<BR>
-    
-	 <H2 align="center">Pytania u¿ytkowników</H2>
-    <A href="#2.1">2.1</A>) Czy s± jakie¶ driwery <SMALL>ODBC</SMALL> dla
-    PostgreSQL?<BR>
-     <A href="#2.2">2.2</A>) Jakie istniej± narzêdzia pozwalaj±ce na dostêp do
-	  PostgreSQL przez www?<BR>
-     <A href="#2.3">2.3</A>) Czy istnieje jakie¶ GUI dla PostgreSQL?
-    Narzêdzie do raportowania? Interfejs dla "embedded query language"?<BR>
-     <A href="#2.4">2.4</A>) Za pomoc± jakich jêzyków programowania mo¿na
-	  siê komunikowaæ z PostgreSQL?<BR>
-     
-
-    <H2 align="center">Pytania administratora</H2>
-    <A href="#3.1">3.1</A>) Jak mogê zainstalowaæ PostgreSQL w innej 
-	 		lokalizacji ni¿ <I>/usr/local/pgsql</I>?<BR>
-     <A href="#3.2">3.2</A>) Podczas startu <I>postmaster'a</I>,
-	  otrzymujê komunikat:
-    <I>Bad System Call</I> lub "core dumped". Dlaczego?<BR>
-     <A href="#3.3">3.3</A>) Podczas startu <I>postmaster'a</I>, 
-     otrzymujê komunikato b³êdzie: <I>IpcMemoryCreate</I>. Dlaczego?<BR>
-     <A href="#3.4">3.4</A>) Podczas startu <I>postmaster'a</I>,
-     otrzymujê komunikat o b³êdzie: <I>IpcSemaphoreCreate</I>. Dlaczego?<BR>
-     <A href="#3.5">3.5</A>) W jaki sposób mogê kontrolowaæ po³±czenia z
-	  innych hostów?<BR>
-     <A href="#3.6">3.6</A>) Jak powinienem skonfigurowaæ system baz
-	  danych aby uzyskaæ lepsz± wydajno¶æ?<BR>
-     <A href="#3.7">3.7</A>) Jakie s± mo¿liwo¶ci wyszukiwania b³êdów?<BR>
-     <A href="#3.8">3.8</A>) Sk±d siê bierze komunikat: <I>"Sorry, too many
-    clients"</I> podczas próby po³±czenia siê z baz± danych?<BR>
-     <A href="#3.9">3.9</A>) Co to za pliki typu <I>pg_sorttempNNN.NN</I>
-    , które znajduj± siê w katalogu z plikami bazy danych?<BR>
-     
-
-    <H2 align="center">Pytania dotycz±ce u¿ytkowania</H2>
-    <A href="#4.1">4.1</A>) Jaka jest ró¿nica pomiêdzy kursorami
-	 binarnymi (binary cursors) i zwyk³ymi kursorami (normal cursors)?<BR>
-     <A href="#4.2">4.2</A>) Jak mogê pobraæ za pomoc± <SMALL>SELECT</SMALL>
-	  jedynie kilka pierwszych wyników zapytania?<BR>
-     <A href="#4.3">4.3</A>) Jak mogê uzyskaæ listê wszystkich tabel czy
-	  innych rzeczy pod <I>psql</I>?<BR>
-     <A href="#4.4">4.4</A>) Jak usun±æ kolumnê z tabeli?<BR>
-     <A href="#4.5">4.5</A>) Jaki jest maksymalny rozmiar dla rzêdu,
-	  tabeli i bazy danych?<BR>
-     <A href="#4.6">4.6</A>) Jak du¿o miejsca w bazie danych jest
-	  potrzebne aby przechowaæ dane ze zwyczajnego pliku tekstowego?<BR>
-     <A href="#4.7">4.7</A>) Jak mogê sprawdziæ jakie tabele, klucze,
-	  bazy danych i u¿ytkownicy s± utworzeni?<BR>
-     <A href="#4.8">4.8</A>) Moje zapytania s± wolne lub nie u¿ywaj±
-	  kluczy. Dlaczego?<BR>
-     <A href="#4.9">4.9</A>) Jak mogê sprawdziæ w jakis sposób "query
-	  optimizer" wykonuje moje zapytanie?<BR>
-     <A href="#4.10">4.10</A>) Co to jest "R-tree index"?<BR>
-     <A href="#4.11">4.11</A>) Co to jest "Genetic Query Optimizer"?<BR>
-     <A href="#4.12">4.12</A>) Jak mogê u¿ywaæ wyra¿eñ regularnych w
-	  zapytaniach i zapytañ case-insensitive w wyra¿eniach regularnych?
-	  Jak korzystaæ z indeksów dla zapytañ case-insensitive?<BR>
-     <A href="#4.13">4.13</A>) Jak sprawdziæ w zapytaniu czy pole ma
-	  warto¶æ <SMALL>NULL</SMALL>?<BR>
-     <A href="#4.14">4.14</A>) Jaka jest ró¿nica pomiêdzy ró¿nymi typami
-	  tekstowymi (character types)?<BR>
-     <A href="#4.15.1">4.15.1</A>) Jak mogê utworzyæ pole typu int, które samo
-	  zwiêksza swoj± warto¶æ?<BR>
-     <A href="#4.15.2">4.15.2</A>) Jak pobraæ warto¶æ pola typu 
-    <SMALL>SERIAL</SMALL> po wykonaniu insert'u?<BR>
-     <A href="#4.15.3">4.15.3</A>) Czy u¿ycie <I>currval()</I> i
-    <I>nextval()</I> nie doprowadzi do "race condition" z innymi
-	 u¿ytkownikami?<BR>
-     <A href="#4.15.4">4.15.4</A>) Dlaczego numery sekwencji nie s±
-	  ponownie u¿ywane przy przerwaniu transakcji?
-    Sk±d siê bior± luki w numerowaniu kolumny tabeli sekwencjami/SERIALem?<BR>
-     <A href="#4.16">4.16</A>) Co to jest <SMALL>OID</SMALL>? Co to jest
-    <SMALL>TID</SMALL>?<BR>
-     <A href="#4.17">4.17</A>) Jakie jest znaczenie niektórych terminów w 
-    PostgreSQL?<BR>
-     <A href="#4.18">4.18</A>) Sk±d bierze siê ten b³±d: <I>"ERROR: Memory
-    exhausted in AllocSetAlloc()"</I>?<BR>
-     <A href="#4.19">4.19</A>) Jak sprawdziæ jakiej wersji PostgreSQL
-    u¿ywam?<BR>
-     <A href="#4.20">4.20</A>) Dlaczego operacje, które wykonujê na
-	  du¿ych obiektach "large-object" zwracaj± komunikat:
-    <I>"invalid large obj descriptor"</I>?<BR>
-     <A href="#4.21">4.21</A>) Jak stworzyæ kolumnê której domy¶ln±
-	  warto¶ci± bêdzie bie¿±cy czas?<BR>
-     <A href="#4.22">4.22</A>) Dlaczego zapytania u¿ywaj±ce
-    <CODE><SMALL>IN</SMALL></CODE> s± takie wolne?<BR>
-     <A href="#4.23">4.23</A>) Jak wykonaæ "outer join"?<BR>
-     <A href="#4.24">4.24</A>) Jak wykonywaæ zapytanie u¿ywaj±ce kilku
-	  baz danych jednocze¶nie?<BR>
-     <A href="#4.25">4.25</A>) Jak zwróciæ w funkcji wiele rzêdów lub
-	  kolumn?<BR>
-     
-
-    <H2 align="center">Rozwijanie PostgreSQL</H2>
-    <A href="#5.1">5.1</A>) Napisa³em w³asn± funkcjê. Kiedy u¿yjê jej w
-	 <I>psql</I>, program zrzuca pamiêæ (dump core)?<BR>
-     <A href="#5.2">5.2</A>) Jak mogê dodaæ/zg³osiæ nowe typy czy funkcje
-	  do PostgreSQL?<BR>
-     <A href="#5.3">5.3</A>) Jak napisaæ funkcjê C zwracaj±c± krotkê
-	  (tuple)?<BR>
-     <A href="#5.4">5.4</A>) Zmieni³em plik ¼ród³owy. Dlaczego po
-	  rekompilacji nie widaæ zmiany?<BR>
-     
-    <HR>
-
-    <H2 align="center">Pytania ogólne</H2>
-
-    <H4><A name="1.1">1.1</A>) Co to jest PostgreSQL? Jak to wymawiaæ?</H4>
-
-    <P>PostgreSQL wymawia siê <I>Post-Gres-kju-el</I>.</P>
-
-    <P>PostgreSQL jest rozszerzeniem systemu zarz±dzania bazami danych -
-	 POSTGRES, kolejn± generacj± rozwojowego prototypu <SMALL>DBMS</SMALL>.
-    Mimo, ¿e PostgreSQL zachowa³ bardzo dobrze zbudowany model danych
-	 (data model) i bogaty zestaw typów danych POSTGRES'a, zast±pi³
-	 PostQuel'owy jêzyk zapytañ z rozbudowanym podzbiorem jêzyka 
-	 <SMALL>SQL</SMALL>. PostgreSQL jest oprogramowaniem darmowym 
-	 z dostêpnymi ca³ymi ¼ród³ami.
-	 </P>
-
-    <P>Rozwój PostgreSQL jest prowadzony przez grupê ludzi z Internetu,
-	 komunikuj±cych siê poprzez mailowe listy dyskusyjne PostgreSQL.
-    Obecnym koordynatorem jest Marc G. Fournier (<A href=
-    "mailto:scrappy@PostgreSQL.org">scrappy@PostgreSQL.org</A>). (Zobacz
-	 poni¿ej jak siê przy³±czyæ). Ta grupa ludzi jest odpowiedzialna za
-	 ca³y rozwój PostgreSQL.</P>
-
-    <P>Autorami PostgreSQL 1.01 byli Andrew Yu and Jolly Chen.
-	 Wiele innych osób pomog³o przy portowaniu, testowaniu, debugowaniu, i
-	 rozwijaniu kodu. Oryginalny kod Postgresa, na którym zosta³ oparty
-	 PostgreSQL, by³ wysi³kiem studentów oraz pracowników pracuj±cych pod
-	 kierownictwem profesora Michael'a Stonebraker'a z University of
-	 California w Berkeley.</P>
-
-    <P>Oryginaln± nazw± oprogramowania w Berkeley by³ Postgres.  Po
-	 dodaniu obs³ugi <SMALL>SQL</SMALL> w 1995, nazwa zosta³a zmieniona
-    na Postgres95. Pod koniec roku 1996 nazwa zosta³a zmieniona na
-    PostgreSQL.</P>
-
-    <H4><A name="1.2">1.2</A>) Jak± licencj± chroniony jest
-    PostgreSQL?</H4>
-
-    <P>PostgreSQL objêty jest nastêpuj±c± licencj±:</P>
-
-    <P>PostgreSQL Data Base Management System</P>
-
-    <P>Portions copyright (c) 1996-2002, PostgreSQL Global Development
-    Group Portions Copyright (c) 1994-6 Regents of the University of
-    California</P>
-
-    <P>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.</P>
-
-    <P>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.</P>
-
-    <P>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 "AS IS" BASIS, AND THE
-    UNIVERSITY OF CALIFORNIA HAS NO OBLIGATIONS TO PROVIDE MAINTENANCE,
-    SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.</P>
-
-    <P>Tekst powy¿ej, jest klasyczn± licencj± BSD.
-    Nie posiada ona ¿adnych restrykcji co do u¿ywania kodu ¼ród³owego.
-	 Podoba nam siê i nie zamierzamy jej zmieniaæ.
-
-    <H4><A name="1.3">1.3</A>) Na jakich systemach Unixowych dzia³a
-	      PostreSQL?</H4>
-
-    <P>PostgreSQL powinien dzia³aæ na wszystkich nowych Unix-podobnych
-	 systemach. Platformy, które zosta³y szczegó³owo przetestowane podczas
-	 publikowania PostgreSQL s± wymienione w dokumentacji opisuj±cej
-	 instalacjê.</P>
-
-    <H4><A name="1.4">1.4</A>) Na jakich nie-Unixowych systemach dzia³a
-	      PostgreSQL?</H4>
-
-    <P><STRONG>Klient</STRONG></P>
-
-    <P>Mo¿liwa jest kompilacja bibliteki C <I>libpq</I> C, psql oraz
-	 innych interfejsów i uruchamianie ich na platformie MS Windows. W tym
-	 wypadku klient jest uruchamiany na MS Windows a z serwerem komunikuje siê
-	 poprzez TCP/IP. Serwer mo¿e dzia³aæ na dowolnej wspieranej platformie 
-	 Unixowej. Plik <I>win31.mak</I> jest do³±czony
-	 do ¼róde³, aby mo¿na by³o stworzyæ bibliotekê <I>libpq</I> oraz
-	 program <I>psql</I> dzia³aj±ce w ¶rodowisku Win32. PostgreSQL mo¿e siê 
-	 tak¿e komunikowaæ z klientami <SMALL>ODBC</SMALL>.</P>
-
-    <P><STRONG>Serwer</STRONG></P>
-
-    <P>Serwer mo¿e byæ uruchamiany na Windows NT i Win2k u¿ywaj±c
-	 bibliotek Cygwin, Cygnus Unix/NT. W pliku <I>pgsql/doc/FAQ_MSWIN</I>
-	 znajduj±cym siê w ¼ród³ach lub pod adresem: <A href=
-    "http://www.postgresql.org/docs/faq-mswin.html">MS Windows FAQ</A>
-    na naszych stronach. Nie planujemy tworzyæ portu przeznaczonego
-	 docelowo dla platformy Microsoft.</P>
-
-    <H4><A name="1.5">1.5</A>) Sk±d mo¿na ¶ci±gn±æ PostgreSQL?</H4>
-
-    <P>G³ówny serwer ftp z dostêpem "anonymous" dla PostgreSQL znajduje
-	 siê <A href="ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub</A>.
-	 je¶li szukasz mirrorów sprawd¼ nasz± g³ówn± stronê www.<P>
-
-    <H4><A name="1.6">1.6</A>) Gdzie mo¿na szukaæ wsparcia technicznego?</H4>
-
-    <P>Adres g³ównej listy mailowej: <A href=
-    "mailto:pgsql-general@PostgreSQL.org">pgsql-general@PostgreSQL.org</A>.
-    Jest ona przeznaczona dyskusjom dotycz±cym spraw zwi±zanych z PostgreSQL.
-    ¯eby zapisac siê na listê, wy¶lij email z nastêpuj±cymi liniami w
-	 tre¶ci maila (nie w temacie):</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-
-    <P>na adres: <A href=
-    "mailto:pgsql-general-request@PostgreSQL.org">pgsql-general-request@PostgreSQL.org</A>.</P>
-
-    <P>Dostêpna jest tak¿e lista wysy³aj±ca digesty. Aby zapisaæ siê na
-	 ni±, wy¶lij email na adres:
-    <A href=
-    "mailto:pgsql-general-digest-request@PostgreSQL.org">pgsql-general-digest-request@PostgreSQL.org</A>
-    z tre¶ci± maila zawieraj±c±:</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-	Digesty s± wysy³ane do cz³onków listy, kiedy na g³ówn± listê dotrze ok
-	30k wiadomo¶ci.
-
-    <P>Dostêpna jest tak¿e lista po¶wiêcona b³êdom znalezionym w
-	 PostgreSQL. Aby zapisaæ siê na ni± wy¶lij email na adres:
-    <A href=
-    "mailto:pgsql-bugs-request@PostgreSQL.org">pgsql-bugs-request@PostgreSQL.org</A>
-    z tre¶ci± maila zawieraj±c±:</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-    Lista po¶wiêcona dyskusjom developerów jest dostêpna pod adresem:
-    <A href=
-    "mailto:pgsql-hackers-request@PostgreSQL.org">pgsql-hackers-request@PostgreSQL.org</A>
-	 Aby siê na ni± zapisaæ wy¶lij na jej adres mail z tre¶ci±:
-<PRE>
-    subscribe
-    end
-</PRE>
-
-    <P>Dodatkowe informacje o listach mailowych dotycz±cych PostgreSQL
-	 mo¿na znale¼æ na stronach WWW PostgreSQL pod adresem:</P>
-
-    <BLOCKQUOTE>
-      <A href="http://www.PostgreSQL.org">http://www.PostgreSQL.org</A>
-    </BLOCKQUOTE>
-
-    <P>W sieci EFNet istnieje kana³ IRC <I>#PostgreSQL</I>. Ja, do
-	 po³±czenia siê z kana³em u¿ywam Unixowego polecenia <CODE>irc -c
-    '#PostgreSQL' "$USER" irc.phoenix.net.</CODE></P>
-
-    <P>Lista firm oferuj±cych wsparcie na zasadach komercyjnych znajduje
-	 siê pod adresem: <A href=
-    "http://www.postgresql.org/users-lounge/commercial-support.html">http://www.postgresql.org/users-lounge/commercial-support.html</A>.</P>
-
-    <H4><A name="1.7">1.7</A>) Jaka jest ostatnia dostêpna wersja?</H4>
-
-    <P>Ostatnia dostêpna wersja PostgreSQL to 7.2.1.</P>
-
-    <P>Planujemy publikowanie kolejnych wersji co cztery miesi±ce.</P>
-
-    <H4><A name="1.8">1.8</A>) Jaka dokumentacja jest dostêpna?</H4>
-
-    <P>Kilka manuali, stron podêcznika man, oraz kilka przyk³adów do
-	 testowania s± za³±czone w samej dystrybucji. Znajduj± siê one w
-	 katalogu <I>/doc</I>. Manual mo¿e byæ tak¿e przegl±dany poprzez
-	 strony www pod adresem <A href=
-    "http://www.PostgreSQL.org/users-lounge/docs/">http://www.PostgreSQL.org/users-lounge/docs/</A>.</P>
-
-    <P>Istniej± tak¿e dwie ksi±¿ki dostêpne online pod adresami
-	 <A href=
-    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
-    i <A href=
-    "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook/</A>.
-    Lista ksi±¿ek o PostgreSQL, które mo¿na kupiæ znajduje siê pod adresem
-	 <A href=
-    "http://www.postgresql.org/books/">http://www.postgresql.org/books/</A>.
-    Zbiór technicznych artyku³ów o PostgreSQL znajduje siê pod adresem <A
-    href=
-    "http://techdocs.postgresql.org/">http://techdocs.postgresql.org/</A>.</P>
-
-    <P><I>psql</I> posiada kilka wbudowanych poleceñ \d, za pomoca których
-	 mo¿na sprawdziæ informacje dotycz±ce typów, operatorów, funkcji,
-	 aggregatów itd.</P>
-
-    <P>Na naszej stronie mo¿na znale¼æ du¿o wiêcej dokumentacji.</P>
-
-    <H4><A name="1.9">1.9</A>) Gdzie mo¿na znale¼æ informacjê o znanych
-	      b³êdach czy brakuj±cych rozwi±zanich?</H4>
-
-    <P>PostgreSQL wspiera rozszerzony podzbiór standardu <SMALL>SQL</SMALL>-92.
-    Sprawd¼ nasz± listê <A href="http://developer.PostgreSQL.org/todo.php">TODO</A>
-    aby znale¼æ informacjê o znanych problemach, brakuj±cych
-	 rozwi±zaniach czy przysz³ych planach.</P>
-
-    <H4><A name="1.10">1.10</A>) Jak mogê siê nauczyæ
-    <SMALL>SQL</SMALL>?</H4>
-
-    <P>Ksi±¿ka o PostgreSQL <A href=
-    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
-    uczy <SMALL>SQL</SMALL>. Jest jeszcze inna ksi±zka o PostgreSQL
-	 dostêpna pod adresem: <A href=
-    "http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook.</A>
-    Dobry tutorial mo¿esz znale¼æ pod adresem: <A href=
-    "http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A>
-    oraz <A href=
-    "http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM">
-    http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM,</A>
-    i <A href=
-    "http://sqlcourse.com/">http://sqlcourse.com.</A></P>
-
-    <P>Jeszcze inny to "Teach Yourself SQL in 21 Days, Second Edition"
-    pod adresem: <A href=
-    "http://members.tripod.com/er4ebus/sql/index.htm">http://members.tripod.com/er4ebus/sql/index.htm</A></P>
-
-    <P>Wielu z naszych u¿ytkowników poleca <I>The Practical SQL Handbook</I>,
-    Bowman, Judith S., et al., Addison-Wesley. Inni polecaj± <I>The
-    Complete Reference SQL</I>, Groff et al., McGraw-Hill.</P>
-
-    <H4><A name="1.11">1.11</A>) Czy PostgreSQL ma rozwi±zany problem Y2K?</H4>
-
-    <P>Tak, bez problemu radzimy sobie z datami po roku 2000 AD, oraz
-	 przed rokiem 2000 BC.</P>
-
-    <H4><A name="1.12">1.12</A>) Jak mogê siê przy³±czyæ do grupy osób
-	      bezpo¶rednio pracuj±cych nad rozwojem PostgreSQL?</H4>
-
-    <P>Przede wszystkim ¶ci±gnij ostatnie dostêpne ¼ród³a i przeczytaj
-	 dokumentacjê przeznaczon± dla developerów na naszej stronie www lub
-	 dostêpn± tak¿e w ¼ród³ach PostgreSQL. Nastêpnie zapisz siê na listy
-	 mailowe <I>pgsql-hackers</I> i
-    <I>pgsql-patches</I>. I na koniec, wysy³aj nam wysokiej jako¶ci
-	 patch'e na listê pgsql-patches.</P>
-
-    <P>Jest oko³o 12 osób, które maj± uprawnienia do commit'owania w
-    <SMALL>CVS</SMALL> PostgreSQL'a. Ka¿dy z nich submitowa³ tak wiele
-	 wysokiej jako¶ci patchy, ¿e sta³o siê niemo¿liwe dla obecnych
-	 commiterów byæ z nimi na bie¿±co, maj±c pewno¶æ ¿e s± to poprawki
-	 wysokiej jako¶ci.</P>
-
-    <H4><A name="1.13">1.13</A>) Jak mogê zg³aszaæ b³êdy?</H4>
-
-    <P>Zajrzyj na stronê <A href=
-    "http://www.postgresql.org/bugs/bugs.php">PostgreSQL BugTool</A>, na
-	 której opisane s± wskazówki jak zg³aszaæ informacje o b³êdach.</P>
-
-    <P>Zajrzyj tak¿e na nasz ftp <A href=
-    "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub</A>, aby
-	 sprawdziæ czy nie ma nowszych wersji PostgreSQL czy patchy.</P>
-
-    <H4><A name="1.14">1.14</A>) Jak mo¿na porównaæ PostgreSQL w stosunku
-	      do innych <SMALL>DBMS</SMALL>?</H4>
-
-    <P>Jest kilka sposobów oceny softwaru: mo¿liwo¶ci,
-    wydajno¶æ, stabilno¶æ, wsparcie i cena.</P>
-
-    <DL>
-      <DT><B>Mo¿liwo¶ci</B></DT>
-
-      <DD>PostgreSQL posiada mo¿liwo¶ci dostêpne w du¿ych, komercyjnych
-		systemach <SMALL>DBMS</SMALL>, takie jak transakcje, podzapytania
-		(subselects), triggery, widoki, klucze obce, referential integrity,
-		oraz wyrafinowany system blokowania. Mamy tak¿e w³a¶ciow¶ci których
-		inni nie posiadaj±, jak typy definiowane przez u¿ytkownika,
-		dziedziczenie, rules, multi-version concurrency control, która
-		redukuje problemy z blokowaiem (lock contention).<BR>
-      <BR>
-      </DD>
-
-      <DT><B>Wydajno¶æ</B></DT>
-
-      <DD>PostgreSQL dzia³a w dwóch trybach. Standardowy tryb <I>fsync</I>
-      zrzuca ka¿d± zakoñczon± transakcjê na dysk, gwarantuj±c w ten
-		sposób to, ¿e je¶li system operacyjny siê zawiesi lub straci
-		zasilanie wci±gu kilku nastepnych sekund, wszystkie Twoje dane
-		zostan± bezpiecznie zapisane na dysku. W tym trybie, jeste¶my
-		wolniejsi ni¿ wiêkszo¶æ komercyjnych baz danych, czê¶ciowo dlatego
-		¿e niewiele z nich wykonuje taki sposób zapisywania danych jako
-		domy¶lne ustawienie.
-      W trybie <I>no-fsync</I> z regu³y jeste¶my szybsi ni¿ komercyjne
-		bazy danych, chocia¿ w tym wypadku zawieszenie siê systemu mo¿e
-		spowodowaæ uszkodzenie danych. Pracujemy nad tym, aby stworzyæ
-		po¶redni tryb, który powoduje mniejsz± redukcjê wydajno¶ci ni¿ tryb
-		fsync i pozwoli na integralno¶æ danych w przeci±gu 30 sekund do
-		za³amania siê systemu operacyjnego.<BR>
-      <BR>
-       Porównuj±c do MySQL czy innych prostych baz danych, jeste¶my
-		 wolniejsi przy wykonywaniu insertów/updatów przez narzut
-		 spowodowany przez transakcje. Oczywi¶cie MySQL nie posiada ¿adnej z
-		 wymienionych wy¿ej <I>mo¿liwo¶ci</I>. PostgreSQL zosta³ zbudowany
-		 aby byæ DBMS elastycznym i bogatym z ró¿norakie mo¿liwo¶ci,
-		 aczkolwiek dbamy, aby poprawiaæ jego wydajno¶æ poprzez analizê
-		 kodu ¼ród³owego i profilowanie. Ciekawe porównanie PostgreSQL i MySQL
-		 mo¿na znale¼æ pod adresem <A href=
-      "http://openacs.org/why-not-mysql.html">http://openacs.org/why-not-mysql.html</A><BR>
-
-      <BR>
-		 Ka¿de po³±czenie klienta jest obs³ugiwane przez nas poprzez
-		 stworzenie nowego procesu Unixowego. Procesy backendu dziel±
-		 bufory danych oraz informacjê o blokadach. U¿ywaj±c wielu
-		 procesorów, ró¿ne backendy mog± bez problemu dzia³aæ na ró¿nych
-		 procesorach.<BR>
-      <BR>
-      </DD>
-
-      <DT><B>Stabilno¶æ</B></DT>
-
-      <DD>Zdajemy sobie sprawê, ¿e <SMALL>DBMS</SMALL> musi byæ stabilny,
-		w przeciwnym wypadku jest bez warto¶ci. Staramy siê publikowaæ kod
-		stabilny, dobrze przetestowany, z minimum mo¿liwych b³êdów. Ka¿de
-		wydanie poprzedza conajmniej miesi±c testów wersji beta. Patrz±c na
-		historiê wydañ PostgreSQL widaæ, ¿e dostarczamy stabilne, dobrze
-		sprawdzone wersje, które s± gotowe do u¿ycia w ¶rodowisku
-		produkcyjnym. My¶limy, ¿e proces publikowania kolejnych wersji
-		opracowany przez nas jest jednym z lepszych w¶ród innych twórców
-		oprogramowania bazodanowego.<BR>
-      <BR>
-      </DD>
-
-      <DT><B>Wsparcie</B></DT>
-
-      <DD>Dziêki naszym listom mailowym masz dostêp do du¿ej liczby
-		programistów i u¿ytkowników, którzy pomagaj± rozwi±zaæ ka¿dy
-		napotkany problem. Chocia¿ nie mo¿emy gwarantowaæ znalezienia
-		rozwi±zania danego problemu, nie ró¿nimy siê w tym od innych
-		komercyjnych systemów <SMALL>DBMS</SMALL>. Bezpo¶redni kontakt z
-		programistami, u¿ytkownikami, dokumentacj± i kodem ¼ród³owym
-		sprawiaj±, ¿e wsparcie oferowane PostgreSQL niejednokrotnie jest
-		lepsze ni¿ w innych systemach <SMALL>DBMS</SMALL>. Istnieje tak¿e
-		mo¿liwo¶æ skorzystania z komercyjnego wsparcia dla tych, których
-		takiego rozwi±zania potrzebuj±.
-      (Sprawd¼ <A href="#1.6">ten punkt FAQ</A>.)<BR>
-      <BR>
-      </DD>
-
-      <DT><B>Cena</B></DT>
-
-      <DD>Korzystanie z PostgreSQL jest darmowe, zarówno w przypadku
-		komercyjnym jak i niekomercyjnym. Mo¿esz korzystaæ z naszego kodu
-		¼ród³owego w Twoim produkcie bez ¿adnych ograniczeñ, poza tymi
-		wymienionymi w licencji BSD przytoczonej powy¿ej.<BR>
-      <BR>
-      </DD>
-    </DL>
-
-    <H4><A name="1.15">1.15</A>) W jaki sposób mogê wesprzeæ finansowo
-	     PostgreSQL?</H4>
-
-    <P>PostgreSQL korzysta z najlepszej infrastruktury od samego pocz±tku
-	 istnienia projektu, tzn. sze¶ciu lat. Wszystko to zawdziêczamy Marc'owi
-	 Fournier'owi, który stworzy³ t± infrastrukturê i zarz±dza ni± od
-	 lat.</P>
-
-    <P>Wysokiej jako¶ci infrastruktura jest bardzo wa¿na dla ka¿dego
-	 projektu open-source. Zapobiega przerwom w rozwoju projektu i
-	 jakimkolwiek przestojom.</P>
-
-    <P>Oczywi¶cie korzystanie z wysokiej jako¶ci infrastruktury nie jest
-	 tanie. Istnieje wiele róznych miesiêcznych, czy jednorazowych
-	 wydatków, które trzeba ponosiæ aby wszystko dzia³a³o jak nale¿y.
-	 Je¶li Ty, b±d¼ Twoja firma mo¿e wspomóc finansowo rozwój PostgreSQL
-	 odwied¼ adres: <A href=
-    "http://www.pgsql.com/pg_goodies">http://www.pgsql.com/pg_goodies</A>
- 	 gdzie opisane jest jak to zrobiæ.</P>
-
-    <P>Chocia¿ na stronie wspomniana jest nazwa PostgreSQL Inc, "datki"
-	 s± przeznaczone jedynie na rozwój projektu PostgreSQL i nie s±
-	 przeznaczane na finansowanie jakiejkolwiek firmy. Je¶li wolisz, 
-	 mo¿esz wys³aæ czek na adres kontaktowy.</P>
-    <HR>
-
-    <H2 align="center">User Client Questions</H2>
-
-    <H4><A name="2.1">2.1</A>) Czy s± jakie¶ driwery <SMALL>ODBC</SMALL> dla
-	     PostgreSQL?</H4>
-
-    <P>Dostêpne s± dwa driwery <SMALL>ODBC</SMALL>: PsqlODBC
-    i OpenLink <SMALL>ODBC</SMALL>.</P>
-
-    <P>PsqlODBC jest do³±czony do ¼róde³. Wiêcej informacji na jego temat
-	 mo¿esz znale¼æ pod adresem: <A href=
-    "ftp://ftp.PostgreSQL.org/pub/odbc/">ftp://ftp.PostgreSQL.org/pub/odbc/</A>.</P>
-
-    <P>OpenLink <SMALL>ODBC</SMALL> mo¿e byæ pobrany z adresu: <A href=
-    "http://www.openlinksw.com/">http://www.openlinksw.com</A>.
-	 Wspó³pracuje ze standardowym oprogramowaniem klienckim <SMALL>ODBC</SMALL>
-	 wiêc w ten sposób mo¿esz korzystaæ z PostgreSQL <SMALL>ODBC</SMALL>
-	 dostêpnego na ka¿dej plaformie któr± wspiera (Win, Mac, Unix, VMS).</P>
-
-    <P>Autorzy bêd± prawdopodobnie sprzedawaæ ten produkt osobom które
-	 wymagaj± komercyjnego wsparcia, ale wersja darmowa bêdzie zawsze
-	 dostêpna. Wszystkie pytania mo¿esz wysy³aæ na adres: <A href=
-    "mailto:postgres95@openlink.co.uk">postgres95@openlink.co.uk</A>.</P>
-
-    <P>Sprawd¼ tak¿e rozdzia³ o  <A href=
-    "http://www.postgresql.org/devel-corner/docs/programmer/odbc.html">ODBC
-    w "Programmer's Guide"</A>.</P>
-
-    <H4><A name="2.2">2.2</A>) Jakie istniej± narzêdzia pozwalaj±ce na dostêp do
-	      PostgreSQL przez www?</H4>
-
-    <P>Dobry podrêcznik dla pocz±tkuj±cych o dostêpie do bazy danych
-	 przez www mo¿esz znale¼æ pod adresem:
-    <A href="http://www.webreview.com">http://www.webreview.com</A></P>
-
-    <P>Inny znajduje siê pod adresem: <A href=
-    "http://www.phone.net/home/mwm/hotlist/">http://www.phone.net/home/mwm/hotlist/.</A></P>
-
-    <P>Do integracji z www, ¶wietnym rozwi±zaniem jest PHP. Mo¿esz
-	 znale¼æ wiêcej informacji na ten temat pod adresem
-    <A href="http://www.php.net">http://www.php.net</A>.</P>
-
-    <P>Wiele osób w przypadku skomplikowanych rozwi±zañ uzywa Perl'a i
-	 modu³u CGI.pl.</P>
-
-    <H4><A name="2.3">2.3</A>)  Czy istnieje jakie¶ GUI dla PostgreSQL?
-	     Narzêdzie do raportowania? Interfejs dla "embedded query
-		  language"?</H4>
-
-    <P>Mamy ca³kiem mi³y interfejs graficzny, który zosta³ nazwany
-	 <I>pgaccess</I> i jest on dostarczany jako czê¶æ ¼róde³.
-	 <I>pgaccess</I> posiada tak¿e generator raportów. Mo¿na go znale¼æ
-	 pod adresem <A href=
-    "http://www.flex.ro/pgaccess">http://www.flex.ro/pgaccess</A></P>
-
-    <P>Udostêpnili¶my tak¿e <I>ecpg</I>, który jest "embedded SQL query
-    language interface" dla jêzyka C.</P>
-
-    <H4><A name="2.4">2.4</A>) Za pomoc± jakich jêzyków programowania
-	 mo¿na siê komunikowaæ z PostgreSQL?</H4>
-	 
-    <P>Mamy wsparcie dla:</P>
-
-    <UL>
-      <LI>C (libpq)</LI>
-
-      <LI>C++ (libpq++)</LI>
-
-      <LI>Embedded C (ecpg)</LI>
-
-      <LI>Java (jdbc)</LI>
-
-      <LI>Perl (perl5)</LI>
-
-      <LI>ODBC (odbc)</LI>
-
-      <LI>Python (PyGreSQL)</LI>
-
-      <LI>TCL (libpgtcl)</LI>
-
-      <LI>C Easy API (libpgeasy)</LI>
-
-      <LI>Embedded <SMALL>HTML</SMALL> (<A href=
-      "http://www.php.net">PHP z http://www.php.net</A>)</LI>
-    </UL>
-    <HR>
-
-    <H2 align="center">Pytania administratora</H2>
-
-    <H4><A name="3.1">3.1</A>) Jak mogê zainstalowaæ PostgreSQL w innej
-	          lokalizacji ni¿ <I>/usr/local/pgsql</I>?</H4>
-
-    <P>U¿yj opcji <I>--prefix</I> podczas uruchamiania skryptu
-    <I>configure</I>.</P>
-
-    <H4><A name="3.2">3.2</A>) Podczas startu <I>postmaster'a</I>,
-	      otrzymujê komunikat o b³êdzie: <I>Bad System Call</I> lub "core dumped".
-			Dlaczego?</H4>
-
-
-    <P>Ten b³±d mo¿e byæ wynikiem wielu problemów, ale na pocz±tek
-	 sprawd¼ czy masz zainstalowane rozszerzenia systemu V w j±drze
-	 systemu. PostgreSQL wymaga do pracy zainstalowanej obs³ugi pamiêci
-	 dzielonej i semaforów.</P>
-
-    <H4><A name="3.3">3.3</A>) Podczas startu <I>postmaster'a</I>,
-	      otrzymujê komunikat o b³êdzie: <I>IpcMemoryCreate</I>.
-			Dlaczego?</H4>
-
-    <P>Albo nie masz poprawnie skonfigurowanej obs³ugi pamiêci dzielonej
-	 w j±drze systemu, albo musisz zwiêkszyæ jej dostêpny rozmiar.
-    Dok³adna ilo¶æ jak± potrzebujesz jest zale¿na od architektury systemu
-	 na jakim pracujesz, jak du¿o buforów oraz jak du¿o procesów backendu
-	 skonfigurowa³e¶ dla <I>postmaster'a</I>. Dla wiêkszo¶ci systemów, z
-	 domy¶ln± liczb± buforów i procesów potrzebujesz minimum w
-	 przybli¿eniu 1MB. Zobacz  <A href=
-    "http://www.postgresql.org/idocs/index.php?kernel-resources.html">PostgreSQL
-    Administrator's Guide</A> gdzie szczegó³owo zosta³o opisane
-	 wykorzystanie pamiêci dzielonej i semaforów.</P>
-
-    <H4><A name="3.4">3.4</A>) Podczas startu <I>postmaster'a</I>,
-	      otrzymujê komunikat o b³êdzie: <I>IpcSemaphoreCreate</I>.
-			Dlaczego?</H4>
-			
-    <P>Je¶li tre¶æ b³êdu brzmi: <I>IpcSemaphoreCreate: semget failed
-	 (No space left on device)</I> oznacza to, ¿e j±dro systemu nie jest
-	 skonfigurowane do obs³ugi wystarczaj±cej liczby semaforów.
-	 Postgres wymaga jednego semafor'a na potencjalny jeden proces backend.
-	 Tymczasowym rozwi±zaniem jest uruchomienie programu <I>postmaster</I>
-	 z mniejsz±  maksymaln± liczb± procesów backend.
-	 U¿yj opcji <I>-N</i> z parameterem mniejszym od domy¶lnego - 32.   
-	 Bardziej trwa³ym rozwi±zaniem jest zwiêkszenie parametrów
-	 <SMALL>SEMMNS</SMALL> i <SMALL>SEMMNI</SMALL> j±dra twojego systemu.</P>
-
-	 <P>Niedzia³aj±ce semafory mog± spowodowaæ niepoprawne zamkniêcie
-	 systemu w czasie intensywnego  korzystania  z bazy.</P>
-	 <P>Je¶li tre¶æ b³êdu jest inna, mo¿e to oznaczaæ, ¿e obs³uga semaforów 
-	 nie zosta³a w³±czona do j±dra wcale. Zobacz PostgreSQL 
-	 Administrator's Guide po bardziej szczegó³owe informacje o pamiêci 
-	 dzielonej i semaforach.</P>
-
-    <H4><A name="3.5">3.5</A>) W jaki sposób mogê kontrolowaæ po³±czenia
-	 z innych hostów?</H4>
-
-    <P>Domy¶lnie PostgreSQL pozwala jedynie na po³±czenia za pomoc±
-	 socketów Unixowych z lokalnego hosta. Inne hosty nie bêd±  mog³y siê
-	 po³±czyæ z serwerem dopóki nie zostanie dodana opcja <I>-i</I> do
-	 <I>postmaster'a</I>,
-    <B>oraz</B> nie umo¿liwi siê autoryzacji na podstawie adresu hostów
-	 modyfikuj±c odpowiednio plik
-    <I>$PGDATA/pg_hba.conf</I>. To zmiany pozwol± na
-	 po³±czenia TCP/IP.</P>
-
-    <H4><A name="3.6">3.6</A>) Jak powinienem skonfigurowaæ system baz
-	      danych aby uzyskaæ lepsz± wydajno¶æ?</H4>
-
-    <P>Indeksy bez w±tpienia mog± przyspieszyæ wykonywanie zapytañ.
-    Polecenie <SMALL>EXPLAIN</SMALL> pozwala zobaczyæ jak PostgreSQL
-	 interpretuje Twoje zapytanie i które indeksy s± u¿ywane.</P>
-
-    <P>Je¶li wykonujesz bardzo du¿o <SMALL>INSERTów</SMALL>, mo¿e warto
-	 je wykonaæ za pomoc± jednego du¿ego pliku u¿ywaj±c polecenia
-	<SMALL>COPY</SMALL>. Jest to du¿o szybsze ni¿ pojedyncze
-    <SMALL>INSERTy.</SMALL> Po drugie polecenia SQL nie zawarte w bloku
-	 okre¶laj±cym transakcjê - <SMALL>BEGIN WORK/COMMIT</SMALL>, s±
-	 traktowane jako pojedyncza transakcja. Rozwa¿ wykonanie kilku
-	 poleceñ/zdañ SQL w jednym bloku transakcji. To redukuje narzut
-	 powodowany przez transakcjê. Przy du¿ych zmianach w danych, warto
-	 usun±æ i stworzyæ na nowo indeksy.</P>
-
-    <P>Jest kilka opcji pozwalaj±cych na poprawienie wydajno¶ci.
-	 Mo¿esz wy³±czyæ <I>fsync()</I> poprzez uruchomienie <I>postmaster'a</I>
-	 z opcjami <I>-o -F</I>. To spowoduje, ¿e
-    <I>fsync()</I> nie bêdzie zrzuca³ danych na dysk po ka¿dej
-	 transakcji.</P>
-
-    <P>Mo¿esz tak¿e uruchomiæ <I>postmaster'a</I> z opcj± <I>-B</I>
-	 aby zwiêkszyæ wielko¶æ pamiêci dzielonej u¿ywanej przez procesy
-	 backendów. Je¶li ustawisz t± warto¶æ zbyt wysoko i przekroczysz limity
-	 ustawione przez kernel na pamiêæ dzielon±, <I>postmaster</I>  mo¿e siê
-	 nie uruchomiæ. Ka¿dy bufor zajmuje 8K a domy¶lna ilo¶æ buforów to 64.</P>
-
-    <P>Mo¿esz tak¿e u¿yæ opcji <I>-S</I> dla backendu aby zwiêkszyæ
-	 maksymaln± warto¶æ pamiêci u¿ywan± przez proces backendu podczas
-	 sortowania. Opcja <I>-S</I> jest ustawiana warto¶ci± podawan± w
-	 kilobajtach, domy¶lna warto¶æ to 512K.</P>
-
-    <P>Mo¿esz tak¿e u¿yæ polecenia <SMALL>CLUSTER</SMALL> aby pogrupowaæ
-	 dane w tabelach wg indeksu. Zobacz opis polecenia <SMALL>CLUSTER</SMALL>
-    w manualu ¿eby dowiedzieæ siê wiêcej.</P>
-
-    <H4><A name="3.7">3.7</A>) Jakie s± mo¿liwo¶ci wyszukiwania
-	 b³êdów?</H4>
-
-    <P>PostgreSQL ma kilka mo¿liwo¶ci na raportowanie informacji o
-	 jego statusie, które mog± byæ przydatne przy debugowaniu procesu.</P>
-
-    <P>Przede wszystkim uruchom skrypt <I>configure</I> z opcj±
-	 --enable-cassert, wiele funkcji <I>assert()</I> monitoruj± postêp
-	 procesu backend i zatrzymuj± program kiedy wydarzy siê co¶
-	 nieoczekiwanego.</P>
-
-    <P>Zarówno <I>postmaster</I> jak i <I>postgres</I> maj± kilka opcji
-	 do debugowania. Za ka¿dym razem kiedy uruchamiasz <I>postmaster'a</I>,
-    upewnij siê, ¿e wysy³asz standardowe wyj¶cie i error do pliku z
-	 logami, np. w ten sposób:</P>
-<PRE>
-    cd /usr/local/pgsql
-    ./bin/postmaster &gt;server.log 2&gt;&amp;1 &amp;
-</PRE>
-
-    <P>To utworzy plik server.log w g³ównym katalogu PostgreSQL.
-	 Ten plik zawiera po¿yteczne informacje o problemach i b³êdach, które
-	 wydarzy³y siê podczas pracy serwera. <I>Postmaster</I> posiada opcjê
-	 <I>-d</I>, która pozwala na raportowanie bardzo szczególowych
-	 informacji. Do opcji <I>-d</I> podajemy liczbê, która okre¶la
-	 szczegó³owo¶æ wysy³anych informacji. Musisz mieæ ¶wiadomo¶æ, ¿e
-	 wysoki poziom logowania bêdzie powodowa³ tworzenie bardzo duzych
-	 plików z logami.</P>
-
-    <P>Je¶li <I>postmaster</I> nie zosta³ uruchomiony, mo¿esz uruchomiæ
-    <I>postgres'owy</I> backend z linii poleceñ, i uruchomiæ Twoje
-	 polecenie <SMALL>SQL</SMALL> bezpo¶rednio na nim.
-	 Taki sposób jest polecany <B>jedynie</B> w przypadku debugowania.
-	 Zwróæ uwagê, ¿e w tym wypadku zapytanie koñczy znak nowej linii a nie
-	 ¶rednik. Je¶li skompilowa³e¶ z opcjami debugowania mozesz u¿yæ
-	 debuggera aby sprawdziæ co siê dzieje. Poniew¿ backend nie zosta³
-	 uruchomiony przez <I>postmaster'a</I>, nie dzia³a w identycznym
-	 ¶rodowisku, co oznacza ¿e powtórzenie warunków w jakich wyst±pi³y
-	 problemy moze byæ problemem.</P>
-
-    <P>Je¶li <I>postmaster</I> dzia³a, uruchom <I>psql</I> w jednym z
-	 okien, nastêpnie znajd¼ <SMALL>PID</SMALL> procesu <I>postgres</I>
-    u¿ywanego przez <I>psql</I>. U¿yj debuggera aby do
-	 <SMALL>PID'u</SMALL> <I>postgres'a</I>. Mo¿esz ustawiaæ pu³apki
-	 (breakpoints) w debuggerze i wykonywaæ zapytania z <I>psql</I>. 
-	 Je¶li debugujesz uruchamianie <I>postgres'a</I>, mo¿esz ustawiæ zmienn±
-	 PGOPTIONS="-W n", nastêpnie uruchomiæ <I>psql</I>. 
-	 Opcja ta pozwoli spowolniæ uruchomienie na	 
-	 <I>n</I> sekund aby¶ móg³ siê po³±czyæ z procesem za pomoc±
-	 debugera, ustawiæ jakiekolwiek pu³apki i kontynuowaæ proces
-	 uruchamiania.</P>
-
-    <P><I>postgres</I> mo¿e byæ uruchamiany z opcjami <I>-s, -A</I> i
-	 <I>-t</I>, które mog± byæ bardzo przydatne przy debuggowaniu i ocenie
-	 wydajno¶ci.</P>
-
-    <P>Mo¿esz tak¿e skompilowaæ z profilingiem aby zobaczyæ jakie funkcje
-	 ile czasu wykonuj± siê. Pliki profilowane dla backendu zostan±
-	 umieszczone w katalogu
-    <I>pgsql/data/base/dbname</I>. Pliki profilu klienta zostan±
-	 umieszczone w bie¿±cym katalogu klienta. Linux wymaga aby kompilowaæ
-	 z opcj± <I>-DLINUX_PROFILE</I> aby profilowanie odbywa³o siê
-	 poprawnie.</P>
-
-    <H4><A name="3.8">3.8</A>) Sk±d siê bierze komunikat: <I>"Sorry, too
-	 many clients"</I> podczas próby po³±czenia siê z baz± danych?</H4>
-
-    <P>Musisz zwiêkszyæ limit ilo¶ci jednoczesnych procesów bacekendu
-	 dla procesu <I>postmaster'a</I>.</P>
-
-    <P>Domy¶lny limit to 32 procesy. Mo¿esz go zwiêkszyæ przez restart
-    <I>postmaster</I> z odpowiedni± warto¶ci± ustawian± opcjê <I>-N</I> w
-	 pliku <I>postgresql.conf</I>.</P>
-
-    <P>We¼ pod uwagê, ¿e je¶li zwiêkszysz warto¶æ podan± w opcji
-	 <I>-N</I> na wiêcej ni¿ 32 musisz tak¿e zwiêkszyæ warto¶æ w opcji
-    <I>-B</I> ponad jej domy¶ln± warto¶æ 64; warto¶æ <I>-B</I> musi byæ
-	 co najmniej dwa razy wiêksza od warto¶ci podanej w opcji 
-    <I>-N</I>, a prawdopodobnie powinna byæ w rzeczywisto¶ci jeszcze
-	 wiêksza dla optymalnej wydajno¶ci.
-    Dla du¿ej liczby procesów backendu na pewno zauwa¿ysz, ¿e trzeba
-	 zwiêkszyæ ró¿ne parametry j±dra Unixa. Rzeczy, które powniene¶
-	 sprawdziæ to maksymalna liczba bloków pamiêci dzielonej, 
-	 <SMALL>SHMMAX;</SMALL> maksymalna liczba semaforów, <SMALL>SEMMNS</SMALL>
-	 oraz <SMALL>SEMMNI;</SMALL> 
-    maksymalna liczba procesów, <SMALL>NPROC;</SMALL> maksymalna liczba
-	 procesów na jednego u¿ytkownika, <SMALL>MAXUPRC;</SMALL> i maksymalna
-	 liczba otwartych plików, <SMALL>NFILE</SMALL> oraz
-    <SMALL>NINODE.</SMALL> Powód dla którego PostgreSQL ma limit na
-	 maksymaln± liczbê procesów backendu to obawa o wyczerpanie zasobów
-	 systemu.</P>
-
-    <P>W wersjach PostgreSQL wcze¶niejszych ni¿ 6.5, maksymalna liczba
-	 backendów by³a ustawiona na 64, a zmiana tej warto¶ci wymaga
-	 rekompliacji po zmianie sta³ej MaxBackendId w pliku
-    <I>include/storage/sinvaladt.h</I>.</P>
-
-    <H4><A name="3.9">3.9</A>)  Co to s± za pliki typu: 
-	 <I>pg_sorttempNNN.NN</I>, 
-	 które znajduj± siê w katalogu z plikami bazy danych?</H4>
-
-    <P>S± to tymczasowe pliki utworzone przez executor. Dla przyk³adu,
-	 je¶li jaka¶ operacja sortowania jest wymagana do wykonania
-    <SMALL>ORDER BY,</SMALL> a samo sortowanie wymaga wiêcej  miejsca ni¿
-	 paratmetr backendu
-    <I>-S</I> ustawi³ do wykorzystania, wtedy tymczasowe pliki s± u¿ywane
-	 do przechowywania tych danych.</P>
-
-    <P>Pliki tymczasowe powinny byæ usuniête automatycznie, ale mog³o siê
-	 to nie staæ je¶li proces backendu w miêdzyczasie nie zakoñczy³ siê
-	 poprawnie podczas operacji sortowania. Je¶li w danym momencie nie
-	 dzia³aj± ¿adne procesy backendów mozesz spokojnie usun±æ pliki
-    pg_tempNNN.NN.</P>
-    <HR>
-
-    <H2 align="center">Pytania dotycz±ce u¿ywania</H2>
-
-    <H4><A name="4.1">4.1</A>) Jaka jest ró¿nica pomiêdzy kursorami
-	     binarnymi (binary cursors) i zwyk³ymi kursorami (normal
-		  cursors)?</H4>
-
-    <P>Zobacz w manualu opis polecenia <SMALL>DECLARE</SMALL>.</P>
-
-    <H4><A name="4.2">4.2</A>) Jak mogê pobraæ za pomoc±
-	 <SMALL>SELECT</SMALL> jedynie kilka pierwszych wyników
-	 zapytania?</H4>
-	 
-    <P>Zobacz w manualu opis polecenia <SMALL>FETCH</SMALL> lub u¿yj
-    polecenia <SMALL>SELECT</SMALL> ... <SMALL>LIMIT</SMALL>....</P>
-
-    <P>Nawet je¶li chesz pobraæ kilka pierwszych rzêdów z wyniku
-	 zapytania, ca³e zapytanie musi zostaæ wykonane. Byc mo¿e powiniene¶
-	 skorzystaæ z polecenia <SMALL>ORDER BY.</SMALL>
-	 Je¶li istnieje indeks który odpowiada polom okre¶lonym przez
-	 <SMALL>ORDER BY</SMALL>, PostgreSQL mo¿e wykorzystaæ jedynie kilka
-	 pierwszych rzêdów, byæ mo¿e bêdzie konieczno¶æ wykonania zapytania do
-	 momentu a¿ zostan± znalezione po¿±dane wyniki.</P>
-
-    <H4><A name="4.3">4.3</A>) Jak mogê uzyskaæ listê wszystkich tabel
-	 czy  innych rzeczy pod <I>psql</I>?</H4>
-	 
-    <P>Mo¿esz sprawdziæ zawarto¶æ ¼róde³ <I>psql</I>, a konkretnie plik
-    <I>pgsql/src/bin/psql/describe.c</I>. Zawiera on polecenia
-    <SMALL>SQL</SMALL> które generuja wyniki komend z backslashem.
-    Mo¿esz tak¿e uruchomiæ <I>psql</I> z opcj±
-    <I>-E</I> wtedy po wykonaniu polecenia z backslashem wy¶wietlane
-	 bêdzie zapytanie, które w rzeczywisto¶ci jest wykonywane.</P>
-
-    <H4><A name="4.4">4.4</A>) Jak usun±æ kolumnê z tabeli?</H4>
-	 
-    <P>Nie mamy zaimplementowanego <SMALL>ALTER TABLE DROP
-	 COLUMN,</SMALL> ale mo¿esz zrobiæ tak:</P>
-<PRE>
-    SELECT ...  -- wybierz zawarto¶æ wszystkich kolumn poza t± jedn± której chcesz siê pozbyæ
-    INTO TABLE new_table
-    FROM old_table;
-    DROP TABLE old_table;
-    ALTER TABLE new_table RENAME TO old_table;
-</PRE>
-
-    <H4><A name="4.5">4.5</A>) Jaki jest maksymalny rozmiar dla rzêdu,
-	      tabeli i bazy danych?</H4>
-	 
-    <P>Oto wszystkie ograniczenia:</P>
-<PRE>
-    Maksymalny rozmiar dla bazdy danych?     nieograniczony ( istniej± bazy danych o wielko¶ci 500 GB databases )
-    Maksymalny rozmiar dla tabeli?           16 TB
-    Maksymalny rozmiar dla rzêdu?            nieograniczony w 7.1 i pó¼niejszych
-    Maksymalny rozmiar pola?                 1 GB w 7.1 and later
-    Maksymalna liczba rzêdów w tabeli?       nieograniczona
-    Maksymalna liczba kolumn w tabeli?    250-1600 w zale¿ono¶ci od typów kolumn
-    Makasymalna liczba indeksów na tabeli?    nieograniczona
-</PRE>
-
-	Oczywi¶cie "nieograniczony" nie jest prawd± tak do koñca, istniej±
-	ograniczenia wynikaj±ce z dostêpnego miejsca na dysku, pamiêci/swapa.
-	Kiedy wielko¶ci te bêd± bardzo du¿e mo¿e odbiæ siê to na wydajno¶ci.
-
-    <P>Maksymalny rozmiar tabeli, czyli 16 TB nie wymaga od systemu
-	 operacyjnego wsparcia dla du¿ych plików. Du¿e tabele s± przechowywane
-	 jako pliki o rozmiarze 1 GB, wiêc ograniczenia co do wielko¶ci plików
-	 narzucone przez system plików nie s± istotne.</P>
-
-    <P>Masymalny rozmiar tabeli i maksymalna liczba kolumn mo¿e byæ
-	 zwiêkszona je¶li zwiêkszymy domy¶lny rozmiar bloku (block size) do
-	 32k.</P>
-
-    <H4><A name="4.6">4.6</A>) Jak du¿o miejsca w bazie danych jest
-	      konieczne aby przechowywaæ dane ze zwyczajnego pliku
-			tekstowego?</H4>
-
-    <P>Baza danych PostgreSQL mo¿e potrzebowaæ do piêciu razy wiêcej
-	 miejsca na przechowywanie danych z plików tekstowych ni¿ ich
-	 objêto¶æ.</P>
-
-    <P>Jako przyk³ad mo¿emy rozwa¿yæ plik sk³adaj±cy siê z 100,000 linii
-	 zbudowanych z liczby ca³kowitej oraz opisu tekstowego w ka¿dej.
-	 Za³ó¿my, ¿e ¶rednio ka¿dy ³añcuch tekstu w linii zajmuje 20
-	 bajtów. Ca³y plik powinien zajmowaæ ok. 2.8 MB. Rozmiar pliku bazy danych w
-	 PostgreSQL zawieraj±cego te dane mozna oszacowaæ na oko³o 6.4MB:</P>
-
-<PRE>
-    36 bajtów: nag³ówek ka¿dego rzêdu w przybli¿eniu)
-    24 bajty:  jedno pole int i jedno pole typu text
-   + 4 bajty:  wka¼nik na stronie do krotki
-   --------------------------------------------------
-    64 bajty w jednym rzêdzie
-
-	Strona danych w PostgreSQL zajmuje 8192 bajtów (8 KB), wiêc:
-
-   8192 bajtów na stronê
-   ---------------------   =  128 rzêdów na jedn± strone w bazie (zaokr±glone w dó³)
-     64 bajtów na rz±d
-
-   100000 rzêdów danych
-   -----------------------  =  782 stron w bazie danych (zaokr±glone w górê)
-      128 rzêdów na stronê
-
-782 stron w bazie * 8192 bajtów na stronê  =  6,406,144 bajtów (6.4 MB)
-</PRE>
-
-    <P>Indeksy nie powoduj± du¿ego narzutu na zajmowane miejsce, 
-	 ale zawieraj± pewne dane,
-	 wiêc w pewnych przypadkach moga byæ ca³kiem du¿e.</P>
-
-    <H4><A name="4.7">4.7</A>) Jak mogê sprawdziæ jakie tabele, klucze,
-	      bazy danych i u¿ytkownicy s± utworzeni?</H4>
-	 
-    <P><I>psql</I> ma ca³kiem du¿± ilo¶æ poleceñ z backslashem aby
-	 wydobyæ takie informacje. Wprowad¼ \? aby zobaczyæ ich spis. Istniej±
-	 tak¿e tablice systemowe rozpoczynaj±ce siê od <i>pg_</i>, zawieraj±ce
-	 interesuj±ce Ciebie informacje. Wykonanie <i>psql -l</i> poka¿e spis
-	 wszystkich baz danych.</P>
-
-    <P>Obejrzyj tak¿e plik <I>pgsql/src/tutorial/syscat.source</I>.
-	 Zawiera on wiele z zapytañ typu <SMALL>SELECT</SMALL>, które s±
-	 potrzebne aby wydobyæ informacje z tablic systemowych.</P>
-
-    <H4><A name="4.8">4.8</A>) Moje zapytania s± wolne lub nie u¿ywaj±
-	      kluczy. Dlaczego?</H4>
-			
-	Indeksy nie s± u¿ywane automatycznie przez k±¿de z zapytañ. Ideksy s±
-	u¿ywane jedynie gdy tabela jest odpowiedniego rozmiaru, wiêkszego ni¿
-	wymagany minimalny, a zapytanie wybiera jedynie ma³y procent
-	zawarto¶ci tabeli. Wynika to z tego, ¿e losowy dostep do dysku
-	powodowany przez ideksowane poszukiwanie jest czasami wolniejsze ni¿
-	poszukiwanie sekwencyjne bez u¿ycia kluczy.
-	
-    <P>¯eby zdecydowaæ czy indeks powinien byc u¿ywany, PostgreSQL musi
-	 mieæ statystyki dotycz±ce danej tabeli. S± one gromadzone przez
-	 u¿ycie polecenia <SMALL>VACUUM ANALYZE</SMALL>, lub poprostu
-	 <SMALL>ANALYZE</SMALL>. u¿ywaj±c statystyk, optymalizator wie ile
-	 rzêdów jest w tabeli i mo¿e lepiej okre¶liæ czy indeksy powinny byæ
-	 u¿yte. Statystyki mog± byæ tak¿e pomocne w okre¶leniu najlepszej
-	 kolejno¶ci wykonania z³±czenia (join) i jego sposobu. Gromadzenie
-	 statystyk powinno siê odbywaæ w okre¶lonych interwa³ach czasu
-	 poniewa¿ dane w tabelach zmieniaj± siê.</P>
-
-    <P>Indeksy nie s± zazwyczaj u¿ywane przez <SMALL>ORDER BY</SMALL> lub
-	 przy wykonywaniu z³±czeñ (join). Sekwencyjne przeszukiwanie po którym
-	 nastêpuje sortowanie jest zazwyczaj szybsze niê wyszukiwanie za
-	 pomoc± indeksu na du¿ej tabeli.</P>
-	 Jakkolwiek <SMALL>LIMIT</SMALL> w po³±czeniu z <SMALL>ORDER BY</SMALL>
-	czêsto bêdzie wykorzystywa³ indeksów poniew±z jedynie ma³a czê¶c z
-	tabeli jest zwracana.
-
-    <P>Kiedy u¿ywa siê operatorów dopasuj±cych takich jak
-	 <SMALL>LIKE</SMALL> lub <I>~</I>, indeksy bêd± u¿ywane jedynie je¶li 
-	 pocz±tek wyszukiwania jest oparty na pocz±tku ³añcucha tekstu.
-	 Dlatego, aby u¿ywac indeksów,
-    dopasowania operatorem <SMALL>LIKE</SMALL> nie mog± siê zaczynaæ
-	 <I>%</I>, a dopasowania operatorem <I>~</I> (dopasowania regularne)
-	 musz± siê zaczynaæ znakiem specjalnym <I>^</I>.</P>
-
-    <H4><A name="4.9">4.9</A>) Jak mogê sprawdziæ w jakis sposób "query
-	 optimizer" wykonuje moje zapytanie?</H4>
-
-    <P>Zobacz manual dla polecenia <SMALL>EXPLAIN</SMALL>.</P>
-
-    <H4><A name="4.10">4.10</A>) Co to jest "R-tree index"?</H4>
-
-    <P>Indeks R-tree jest u¿ywany do indeksowania danych przestrzennych.
-	 Indeks hasuuj±cy nie nadaje siê do wyszukiwania odleg³o¶ci.
-    Natomiast indeks typu B-tree mo¿e wyszukiwaæ odleglo¶ci jedynie w
-	 jednowymiarowych przestrzeniach. R-tree indeks radzi sobie z
-	 przestrzeniami wielo-wymiarowymi. Dla przyk³adu, je¶li zostanie
-	 za³o¿ony indeks typu R-tree na polu typu <I>point</I>, system mo¿e
-	 bardziej wydajnie odpowiadaæ na zapytania typu
-    "select all points within a bounding rectangle."</P>
-
-    <P>¬ród³owym dokumentem opisuj±cym oryginalnie projektowanie R-tree
-	 indeksów jest:</P>
-
-    <P>Guttman, A. "R-trees: A Dynamic Index Structure for Spatial
-    Searching." Proceedings of the 1984 ACM SIGMOD Int'l Conf on Mgmt
-    of Data, 45-57.</P>
-
-    <P>Ten dokument mo¿esz znale¼æ tak¿e w pracy Stonebraker'a "Readings in
-    Database Systems".</P>
-
-    <P>Wbudowane indeksy R-trees radz± sobie w wielobokami i boxes.
-	 Teoretycznie, indeksy R-tree mog± byæ rozszerzone o mo¿liwo¶ci
-	 indeksowania w wiêcej wymiarowych przestrzeniach. W praktyce,
-	 rozbudowa indeksów R-tree wymaga trochê pracy, a w tej chwili nie
-	 dysponujemy jak±kolwiek dokumentacj± jak to zrobiæ.</P>
-
-    <H4><A name="4.11">4.11</A>) Co to jest "Genetic Query
-	 Optimizer"?</H4>
-
-    <P>Modu³ <SMALL>GEQO</SMALL> ma za zadanie przyspieszenie
-	 optymalizacji zapytañ ³±cz±c wiele tabel za pomoc± algorytmów
-	 genetycznych (Genetic Algorithm (GA)). Pozwala na u¿ywanie du¿ych
-	 zapytañ ³±cz±cych tabele (join queries) bez wykorzystywania
-	 zasobo¿ernego wyszukiwania.</P>
-
-    <H4><A name="4.12">4.12</A>) Jak mogê u¿ywaæ wyra¿eñ regularnych w
-	      zapytaniach i zapytañ case-insensitive w wyra¿eniach
-			regularnych?
-			     jak korzystaæ z indeksów dla zapytañ case-insensitive?</H4>
-
-    <P>Operator <I>~</I> moze byæ wykorzystywany do wyszukiwania za
-	 pomoc± wyra¿eñ regularnych, a 
-    <I>~*</I> do wyszukiwania case-insensitive z wyra¿eniami
-	 regularnymi. 
-    Wariant case-insensitive dla <SMALL>LIKE</SMALL> zosta³ nazwany
-    <SMALL>ILIKE</SMALL> i jest dostêpny w PostgreSQL 7.1 i pó¼niejszych
-	 wersjach.</P>
-
-    <P>Porównania case-insensitive s± zazwyczaj wykonywane w nastêpuj±cy
-	 sposób:</P>
-<PRE>
-    SELECT *
-    FROM tab
-    WHERE lower(col) = 'abc'
-   
-</PRE>
-	W tym wypadku standardowe indeksy nie bêd± u¿ywane. Mo¿esz utworzyæ
-	indeks funkcyjny, poprzez:
-<PRE>
-    CREATE INDEX tabindex on tab (lower(col));
-   
-</PRE>
-
-    <H4><A name="4.13">4.13</A>) Jak sprawdziæ w zapytaniu czy pole ma
-	      warto¶æ <SMALL>NULL</SMALL>?</H4>
-
-    <P>Mo¿esz to sprawdziæ, testuj±c warto¶æ kolumny warunkiem 
-	 <SMALL>IS NULL</SMALL> albo <SMALL>IS NOT NULL</SMALL>.</P>
-
-    <H4><A name="4.14">4.14</A>) Jaka jest ró¿nica pomiêdzy ró¿nymi
-	 typami tekstowymi (character types)?</H4>
-<PRE>
-Type            Nazwa wewnêtrzna   Uwagi
---------------------------------------------------
-"char"          char            	  1 znak
-CHAR(#)         bpchar             wype³niane pustymi znakami do podanej d³ugo¶ci
-VARCHAR(#)      varchar            rozmiar okre¶la maksymaln± d³ugo¶æ, nie ma tutaj wype³niania
-TEXT            text               bez limitu na d³ugo¶æ ³añcucha
-BYTEA           bytea              zmiennej d³ugo¶ci tablica bajtów (null-byte safe)
-</PRE>
-
-    <P>Je¶li bêdziesz przegl±daæ katalogi systemowe lub komunikaty o
-	 b³êdach czêsto spotkasz siê z podanymi powy¿ej nazwami
-	 wewnêtrznymi.</P>
-
-    <P>Ostatnie cztery typy powy¿ej to tzw typy "varlena" (np. pierwsze
-	 cztery bajty na dysku to d³ugo¶æ, po których jest data). Dlatego
-	 faktyczna d³ugo¶c takiego ³añcucha jest trochê wiêksza ni¿
-	 zadeklarowany rozmiar. Te typy tak¿e podlegaj± kompresji lub mog± byæ
-	 przechowywane out-of-line jako <SMALL>TOAST</SMALL>, wiêc faktyczne
-	 zu¿ycie miejsca na dysku mo¿e byæ mniejsze ni¿ oczekiwane.</P>
-
-    <P><SMALL>CHAR()</SMALL> jast najlepszym typem do przechowywania
-	 ³añcuchów o tej samej d³ugo¶ci. <SMALL>VARCHAR()</SMALL> jest
-	 najodpowiedniejszy do przechowywania ³añcuchów o ró¿nej d³ugo¶ci
-	 ale okre¶la on maksymaln± jego d³ugo¶æ. <SMALL>TEXT</SMALL> jest
-	 najlepszy dla ³añcuchów o dowolnej d³ugo¶ci, nie przekraczaj±cej 1GB.
-    <SMALL>BYTEA</SMALL> s³u¿y do przechowywania danych binarnych,
-	 w szczególno¶ci dla danych zawieraj±cych <SMALL>NULL</SMALL> bajty.</P>
-
-    <H4><A name="4.15.1">4.15.1</A>) Jak mogê utworzyæ pole które samo
-	      zwiêksza swoj± warto¶æ?</H4>
-
-    <P>PostgreSQL ma zaimplementowany typ <SMALL>SERIAL</SMALL>.
-	 Automatycznie tworzy sekwencjê i indeks na tej kolumnie. Dla
-	 przykladu:</P>
-<PRE>
-    CREATE TABLE person ( 
-        id   SERIAL, 
-        name TEXT 
-    );
-</PRE>
-    zostanie automatycznie przt³umaczone na:
-<PRE>
-    CREATE SEQUENCE person_id_seq;
-    CREATE TABLE person ( 
-        id   INT4 NOT NULL DEFAULT nextval('person_id_seq'),
-        name TEXT 
-    );
-    CREATE UNIQUE INDEX person_id_key ON person ( id );
-</PRE>
-    Wiêcej informacji o sekwencjach znajdziesz w manualu o
-	 <I>create_sequence</I>. Mo¿esz tak¿e u¿yæ  pola <I>OID</I> jako
-	 unikalnej warto¶ci dla ka¿dego rzêdu danych. Je¶li bêdziesz
-	 potrzebowa³ z backupowaæ dane robi±c dump bazy i odtworzyæ j±, musisz
-	 u¿yc <I>pg_dump</I> z opcj± <I>-o</I> lub polecenia <SMALL>COPY
-	     WITH OIDS</SMALL> aby zachowaæ <SMALL>OIDy</SMALL>.
-	 
-    <H4><A name="4.15.2">4.15.2</A>) Jak pobraæ warto¶æ pola typu
-	     <SMALL>SERIAL</SMALL> po wykonaniu insert'u?</H4>
-
-    <P>Jednym z podej¶æ jest pobranie kolejnej warto¶ci typu 
-	 <SMALL>SERIAL</SMALL> z sekwencji za pomoc± funkcji <I>nextval()</I>
-    <I>zanim</I> zostanie wstawiona, a pó¼niej nale¿y jej u¿yæ. U¿ywaj±c
-	 przyk³adu z tabeli z punktu <A href="#4.15.1">4.15.1</A>, mo¿e to
-	 wygl±daæ w Perlu na przyk³ad w ten sposób:</P>
-
-<PRE>
-    new_id = output of "SELECT nextval('person_id_seq')"
-    INSERT INTO person (id, name) VALUES (new_id, 'Blaise Pascal');
-</PRE>
-	Bêdziesz mia³ wtedy t± warto¶æ przechowan± w zmiennej 
-    <CODE>new_id</CODE> do u¿ytku w innych zapytaniach (np. jako klucz
-	 obcy do tabeli <CODE>person</CODE>). Warto zwróciæ uwagê, ¿e nazwa
-	 automatycznie utworzonej sekwencji
-    <SMALL>SEQUENCE</SMALL> bêdzie nastêpuj±ca:
-    &lt;<I>tabela</I>&gt;_&lt;<I>kolumnatypuserial</I>&gt;_<I>seq</I>,
-	 gdzie 
-    <I>tabela</I> i <I>kolumnatypuserial</I> s± nazwami Twojej tabeli i
-	 Twojej kolumny typu <SMALL>SERIAL</SMALL>. 
-
-    <P>Inne rozwi±zanie to u¿ycie funkcji <I>currval</I>() na pola typu
-    <SMALL>SERIAL</SMALL> po dodaniu nowej warto¶ci do rzêdu zawieraj±cego
-	 kolumnê typu <SMALL>SERIAL</SMALL> z wstawion± domy¶lnie warto¶ci±,
-	 np.</P>
-<PRE>
-    INSERT INTO person (name) VALUES ('Blaise Pascal');
-    new_id = output of "SELECT currval('person_id_seq')";
-</PRE>
-	Ostatecznie mo¿esz u¿yæ <A href="#4.16"><SMALL>OID</SMALL></A>
-	zwracanej po wykonaniu <SMALL>INSERT</SMALL>, chocia¿ to jest najmniej
-	przeno¶ne rozwi±zanie.
-   W Perlu, wykorzystuj±c bibliotekê DBI z modu³em Edmunda Mergla
-	DBD::Pg, oid jest dostêpny poprzez <I>$sth-&gt;{pg_oid_status}</I> po
-	wykonaniu <I>$sth-&gt;execute()</I>. 
-
-    <H4><A name="4.15.3">4.15.3</A>) Czy u¿ycie <I>currval()</I> i
-	     <I>nextval()</I> nie doprowadzi do race condition z innymi
-		      u¿ytkownikami?</H4>
-
-    <P>Nie. currval() zwraca bie¿±c± warto¶æ przypisan± przez Twój
-	 backend, a nie przez wszystkich u¿ytkowników.</P>
-
-    <H4><A name="4.15.4">4.15.4</A>) Dlaczego numery sekwencji nie s±
-	      ponownie u¿ywane przy przerwaniu transakcji?
-			    Sk±d siê bior± luki w numerowaniu kolumny tabeli
-				     sekwancjami/SERIALem?</H4>
-
-    <P>Aby poprawiæ zbie¿no¶æ (concurrency), warto¶ci sekwencji s±
-	 podawane dzia³aj±cym transakcjom kiedy tego potrzebuj± i nie s±
-	 blokowane dopóki transakcja siê nie zakoñczy. To spowoduje przerwy w
-	 numerowaniu z przerwanych transakcji.</P>
-
-    <H4><A name="4.16">4.16</A>) Co to jest <SMALL>OID</SMALL>? Co to
-	 jest
-	     <SMALL>TID</SMALL>?</H4>
-
-    <P><SMALL>OID</SMALL> s± PostgreSQL'owym rozwi±zaniem problemu
-	 unikalnych numerów rzêdów. Ka¿dy rz±d tworzony przez PostgreSQL
-	 otrzymuje unikalny <SMALL>OID</SMALL>. Wszystkie <SMALL>OID</SMALL>y
-	 generowane podczas procesu uruchamianego przez skrypt
-    <I>initdb</I> maj± mniejsz± warto¶æ ni¿ 16384 (na podstawie pliku
-    <I>backend/access/transam.h</I>). Wszystkie 
-    <SMALL>OID</SMALL>y tworzone przez u¿ytkownika sa równe lub wiêksze
-	 podanej wcze¶niej warto¶ci. Domy¶lnie
-    wszystkie <SMALL>OID</SMALL>y s± unikalne nie tylko w pojedyñczej
-	 tabeli czy bazie danych ale w ca³ej instalacji PostgreSQL.</P>
-
-    <P>PostgreSQL u¿ywa <SMALL>OIDów</SMALL> w swoim wewnêtrznym systemie
-	 tabel, aby mo¿na by³o je ³±czyæ.
-    Te <SMALL>OIDy</SMALL> mog± byc u¿ywane aby identyfikowac rzêdy w
-	 tabelach i wykorzystywaæ je w z³±czeniach tych tabel. Zaleca siê aby¶
-	 u¿ywa³ typu <SMALL>OID</SMALL> aby przechowywaæ warto¶ci
-    <SMALL>OID</SMALL>. Mo¿esz utworzyæ indeks na polu 
-    <SMALL>OID</SMALL> aby dostêp do niego by³ szybszy.</P>
-
-    <P><SMALL>OID</SMALL> s± przypisane do wszystkich rzêdów z jednego
-	 g³ównego miejsca i u¿ywane sa przez wszystkie bazy danych. Je¶li
-	 chcia³by¶ zmieniæ <SMALL>OID</SMALL> na co¶ innego, lub je¶li
-	 chcia³by¶ zrobiæ kopiê tabeli, z orginalnymi <SMALL>OIDami</SMALL>
-	 nie ma ¿adnego przeciwwskazania aby¶ to zrobi³:</P>
-	 
-<PRE>
-        CREATE TABLE new_table(old_oid oid, mycol int);
-        SELECT old_oid, mycol INTO new FROM old;
-        COPY new TO '/tmp/pgtable';
-        DELETE FROM new;
-        COPY new WITH OIDS FROM '/tmp/pgtable';
-<!--
-    CREATE TABLE new_table (mycol int);
-    INSERT INTO new_table (oid, mycol) SELECT oid, mycol FROM old_table;
--->
-</PRE>
-
-    <P><SMALL>OIDy</SMALL> s± przechowywane jako cztero-bajtowe liczby
-	 ca³kowite i skoñcz± siê po osi±gniêciu czterech miliardów. Nikt jak
-	 dot±d nie zg³osi³ aby co¶ takiego siê stalo, ale mamy zamiar pozbyæ
-	 siê tego ograniczenia zanim kto¶ to zg³osi.</P>
-
-    <P><SMALL>TID</SMALL> s± u¿ywane aby zidentyfikowaæ konkretne rzêdy z
-	 blokami i warto¶ci± ofsetów. <SMALL>TIDy</SMALL> zmieniaj± siê wraz
-	 ze zmianami rzêdów. Sa u¿ywane przez indeksy, aby wskazywaæ do
-	 fizycznych rzêdów.</P>
-
-    <H4><A name="4.17">4.17</A>) Jakie jest znaczenie niektórych terminów
-	 w PostgreSQL?</H4>
-
-    <P>W czê¶ci kodu ¼ród³owego i starszej dokumentacji u¿ywamy terminów,
-	 które maj± bardziej ogólne znaczenie. Oto niektóre z nich:</P>
-
-    <UL>
-      <LI>table, relation, class</LI>
-
-      <LI>row, record, tuple</LI>
-
-      <LI>column, field, attribute</LI>
-
-      <LI>retrieve, select</LI>
-
-      <LI>replace, update</LI>
-
-      <LI>append, insert</LI>
-
-      <LI><SMALL>OID</SMALL>, serial value</LI>
-
-      <LI>portal, cursor</LI>
-
-      <LI>range variable, table name, table alias</LI>
-    </UL>
-
-    <P>Listê terminów zwi±zanych z bazami danych mo¿esz znale¼æ pod tym
-	 adresem:<A href=
-    "http://www.comptechnews.com/~reaster/dbdesign.html">http://www.comptechnews.com/~reaster/dbdesign.html</A></P>
-
-    <H4><A name="4.18">4.18</A>) Sk±d bierze siê ten b³±d <I>"ERROR:
-	 Memory exhausted in AllocSetAlloc()"</I>?</H4>
-
-    <P>Je¶li u¿ywasz wersji starszej ni¿ 7.1, upgrade mo¿e rozwi±zaæ ten
-	 problem. Jest tak¿e mozliwe, ¿e po prostu wyczerpa³a Ci siê pamiêæ
-	 wirtualna (virtual memory) w systemie lub Twój kernel ma zbyt nisko
-	 ustawione limity dla pewnych zasobów. Spróbuj wykonaæ nastêpuj±ce
-	 polecenia zanim uruchomisz <I>postmaster'a</I>:</P>
-<PRE>
-    ulimit -d 262144
-    limit datasize 256m
-</PRE>
-	W zale¿no¶ci od shell'a jakiego u¿ywasz jedno z tych poleceñ mo¿e nie
-	zadzia³aæ, ale to ustawienie pozwoli ustawiæ segment danych dla
-	procesu znacznie wiêkszy i byæ mo¿e pozwoli wykonaæ zapytanie.
-	To polecenie zadzia³a dla bie¿±cego procesu oraz wszytkich podprocesów
-	utworzonych po wykonaniu polecenia. Je¶li ten problem wystêpuje z
-	klientem <SMALL>SQL</SMALL>, poniewa¿ backend zwraca zbyt du¿o danych,
-	spróbuj wykonaæ to polecenie przed uruchomieniem klienta.
-
-    <H4><A name="4.19">4.19</A>) Jak sprawdziæ jakiej wersji PostgreSQL
-	     u¿ywam?</H4>
-
-    <P>W <I>psql</I>, wpisz <CODE>select version();</CODE></P>
-
-    <H4><A name="4.20">4.20</A>) Dlaczego operacje, które wykonujê na
-	      du¿ych obiektach "large-object" zwracaj± komunikat:
-			    <I>"invalid large obj descriptor"</I>?</H4>
-
-    <P>Musisz u¿yæ <CODE>BEGIN WORK</CODE> i <CODE>COMMIT</CODE>
-    przed i po u¿yciu uchwytu do du¿ego obiektu, tzn. musisz nimi otoczyæ
-    funkcje <CODE>lo_open</CODE> ... <CODE>lo_close.</CODE></P>
-
-    <P>Obecnie PostgreSQL u¿ywj±c "rule" zamyka uchwyt do du¿ego obiektu
-	 przy ka¿dym wywo³aniu "commit". Wiêc pierwsze próba zrobienia
-	 czegokolwiek z uchwytem spowoduje wypisanie: <I>invalid large obj 
-	 descriptor</I>. Kod, który do tej pory dzia³a³ (przynajmniej
-	 wiêkszo¶æ razy) bêdzie teraz generowa³ informacjê o b³êdzie je¶li nie
-	 bêdziesz korzysta³ z transakcji.</P>
-
-    <P>Je¶li u¿ywasz interfejsu klienta jak <SMALL>ODBC</SMALL>  byæ mo¿e
-	 bêdziesz musia³ ustawiæ <CODE>auto-commit off.</CODE></P>
-
-    <H4><A name="4.21">4.21</A>) Jak stworzyæ kolumnê której domy¶ln±
-	      warto¶ci± bêdzie bie¿±cy czas?</H4>
-
-    <P>U¿yj <I>CURRENT_TIMESTAMP</I>:</P>
-<PRE>
-<CODE>CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
-</CODE>
-</PRE>
-
-    <H4><A name="4.22">4.22</A>) Dlaczego zapytania u¿ywaj±ce
-	     <CODE><SMALL>IN</SMALL></CODE> sa takie wolne?</H4>
-
-    <P>Obecnie ³±czymy podzapytania w outer queries poprzez sekwencyjne
-	 przeszukiwanie wyników podzapytania dla ka¿dego rzêdu z outer query. 
-	 Mo¿na to omin±æ zastêpuj±c <CODE>IN</CODE> przez 
-    <CODE>EXISTS</CODE>:</P>
-<PRE>
-<CODE>SELECT *
-    FROM tab
-    WHERE col1 IN (SELECT col2 FROM TAB2)
-</CODE>
-</PRE>
-    na: 
-<PRE>
-<CODE>SELECT *
-    FROM tab
-    WHERE EXISTS (SELECT col2 FROM TAB2 WHERE col1 = col2)
-</CODE>
-</PRE>
-	Mamy zamiar poprawiæ to ograniczenie w przysz³ych wydaniach.
-
-    <H4><A name="4.23">4.23</A>) Jak wykonaæ "outer join"?</H4>
-
-    <P>PostgreSQL 7.1 i pó¼niejsze wersje maj± zaimplementowane outer join
-	 wykorzystuj±c standardow± sk³adnie SQL. Poni¿ej dwa przyk³ady:</P>
-	 
-<PRE>
-    SELECT *
-    FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
-</PRE>
-    or 
-<PRE>
-    SELECT *
-    FROM t1 LEFT OUTER JOIN t2 USING (col);
-</PRE>
-
-    <P>Te dwa identyczne zapytania ³±cz± kolumnê t1.col z kolumn± t2.col,
-	 ale tak¿e zwróc± niepo³±czone rzêdy w t1 (te które nie pasuj± w t2).
-    <SMALL>RIGHT</SMALL> join doda³by niepo³±czone rzêdy z tabeli t2.
-    <SMALL>FULL</SMALL> join zwróci³by rzêdy plus dodatkowo wszystkie
-	 rzêdy z tabel t1 i t2. S³owo <SMALL>OUTER</SMALL> jest opcjonalne i
-	 jest dodawane domy¶lnie przy
-    <SMALL>LEFT</SMALL>, <SMALL>RIGHT</SMALL>, i <SMALL>FULL</SMALL>
-	 join'ach. Zwyk³e join'y s± nazywane <SMALL>INNER</SMALL> joins.</P>
-
-    <P>W poprzednich wersjach "outer joins" mog± byæ zasymulowane poprzez
-	 u¿ycie slowa kluczowego
-    <SMALL>UNION</SMALL> i <SMALL>NOT IN</SMALL>. Dla przyk³adu, ³±cz±c
-	 tabele <I>tab1</I> i <I>tab2</I>, nastêpuj±ce zapytanie wykonuje
-	 <I>outer</I> join:<BR>
-    <BR>
-    </P>
-<PRE>
-    SELECT tab1.col1, tab2.col2
-    FROM tab1, tab2
-    WHERE tab1.col1 = tab2.col1
-    UNION ALL
-    SELECT tab1.col1, NULL
-    FROM tab1
-    WHERE tab1.col1 NOT IN (SELECT tab2.col1 FROM tab2)
-    ORDER BY col1
-</PRE>
-
-    <H4><A name="4.24">4.24</A>) Jak wykonywaæ zapytanie u¿ywaj±ce kilku
-	      baz danych jednocze¶nie?</H4>
-
-    <P>Nie ma takiej mo¿liwo¶ci aby w zapytaniu odpytawaæ inn± baze danych
-	 poza bie¿±c±. Poniewa¿ PostgreSQL ³aduje specyficzne dla bazy danych
-	 katalogi systemowe, nie jest do koñca jasne jak zapytanie pomiêdzy
-	 ró¿nymi bazami danych powinno siê zachowywaæ.</P>
-	 
-    <P>Oczywi¶cie klient mo¿e ³±czyæ siê z ró¿nymi bazami danych i ³±czyæ
-	 informacjê w ten sposób uzyskan±.</P>
-
-    <H4><A name="4.25">4.25</A>) Jak zwróciæ w funkcji wiele rzêdów lub
-	      kolumn?</H4>
-
-     <P>Mo¿esz zwracaæ zbiory z funkcji PL/pgSQL u¿ywaj±c 
-     <i>refcursors</i>. Zobacz <a
-     href="http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html">
-     http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html,</a>
-     sekcjê 23.7.3.3.</P>
-
-     
-    <H2 align="center">Rozwijanie PostgreSQL</H2>
-
-    <H4><A name="5.1">5.1</A>) Napisa³em w³asn± funkcjê. Kiedy u¿yjê jej
-	 w <I>psql</I>, program zrzuca pamiêæ (dump core)?</H4>
-
-    <P>Problem mo¿e byæ spowodowany przez bardzo wiele rzeczy. Spróbuj
-	 najpierw przetestowaæ Twoj± funkcjê w samodzielnie dzia³aj±cym programie.
-	 </P>
-
-    <H4><A name="5.2">5.2</A>) Jak mogê dodaæ/zg³osiæ nowe typy czy
-	 funkcje do PostgreSQL?</H4>
-
-    <P>Wy¶lij Twoje propozycje na listê mailow± <I>pgsql-hackers</I>,
-    wtedy prawdopodobnie Twój kod znajdzie siê w katalogu <I>contrib/</I>.</P>
-
-    <H4><A name="5.3">5.3</A>) Jak napisaæ funkcjê C zwracaj±c± krotkê
-	      (tuple)?</H4>
-
-    <P>To wymaga wysi³ku tak olbrzymiego, ¿e nawet autorzy nigdy tego nie
-	 prubowali, chocia¿ z zalo¿eñ wynika, ¿e jest to mo¿liwe.</P>
-
-    <H4><A name="5.4">5.4</A>)  Zmieni³em plik ¼ród³owy. Dlaczego po
-	      rekompilacji nie widaæ zmiany?</H4>
-
-    <P>Pliki <I>Makefiles</I> nie maj± dorzuconych odpowiednich
-	 zale¿no¶ci dla plików nag³ówkowych (include files). Wykonaj najpierw
-	 <I>make clean</I>, a nastêpnie ponownie <I>make</I>.
-    Je¶li u¿ywasz <SMALL>GCC</SMALL> mo¿esz u¿yæ opcji
-    <I>--enable-depend</I> przy wykonywaniu <I>configure</I> aby
-  </BODY>
-</HTML>
-
diff --git a/doc/src/FAQ/FAQ_russian.html b/doc/src/FAQ/FAQ_russian.html
deleted file mode 100644
index de99068802b..00000000000
--- a/doc/src/FAQ/FAQ_russian.html
+++ /dev/null
@@ -1,1387 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD html 4.01 transitional//EN">
-
-<HTML>
-  <!-- DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN" -->
-  <!-- HTML -->
-
-  <HEAD>
-    <META name="generator" content="HTML Tidy, see www.w3.org">
-
-    <TITLE>PostgreSQL FAQ</TITLE>
-  </HEAD>
-
-  <BODY bgcolor="#ffffff" text="#000000" link="#ff0000" vlink="#a00000"
-  alink="#0000ff">
-    <H1>ïÔ×ÅÔÙ ÎÁ ÞÁÓÔÏ ÚÁÄÁ×ÁÅÍÙÅ ×ÏÐÒÏÓÙ ÐÏ PostgreSQL</H1>
-
-    <P>äÁÔÁ ÐÏÓÌÅÄÎÅÇÏ ÏÂÎÏ×ÌÅÎÉÑ: þÅÔ×ÅÒÇ 11 éÀÎÑ 06:36:10 EDT 2002</P>
-
-    <P>áÎÇÌÉÊÓËÉÊ ×ÁÒÉÁÎÔ ÓÏÐÒÏ×ÏÖÄÁÅÔ: âÒÀÓ íÏÍØÑÎ (Bruce Momjian) (<A href=
-    "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
-    </P>
-    <P>ðÅÒÅ×ÅÌ ÎÁ ÒÕÓÓËÉÊ: ÷ÉËÔÏÒ ÷ÉÓÌÏÂÏËÏ× (<A href=
-    "mailto:pgman@candle.pha.pa.us">victor_v@permonline.ru</A>)<BR>
-    </P>
-
-    <P>óÁÍÕÀ Ó×ÅÖÕÀ ÁÎÇÌÉÊÓËÕÀ ×ÅÒÓÉÀ ÄÏËÕÍÅÎÔÁ ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ <A
-    href=
-    "http://www.postgresql.org/docs/faq-english.html">http://www.PostgreSQL.org/docs/faq-english.html</A>.</P>
-
-    <P>ïÔ×ÅÔÙ ÎÁ ×ÏÐÒÏÓÙ ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ ËÏÎËÒÅÔÎÙÈ ÐÌÁÔÆÏÒÍ ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ <A href=
-    "http://www.postgresql.org/users-lounge/docs/faq.html">http://www.PostgreSQL.org/users-lounge/docs/faq.html</A>.</P>
-    <HR>
-
-    <H2 align="center">ïÂÝÉÅ ×ÏÐÒÏÓÙ</H2>
-    <A href="#1.1">1.1</A>) þÔÏ ÔÁËÏÅ PostgreSQL? ëÁË ÐÒÏÉÚÎÏÓÉÔÓÑ ÜÔÏ
-    ÎÁÚ×ÁÎÉÅ?<BR>
-     <A href="#1.2">1.2</A>) ëÁËÏ×Ù Á×ÔÏÒÓËÉÅ ÐÒÁ×Á ÎÁ PostgreSQL?<BR>
-     <A href="#1.3">1.3</A>) îÁ ËÁËÉÈ Unix ÐÌÁÔÆÏÒÍÁÈ ÒÁÂÏÔÁÅÔ PostgreSQL?<BR>
-     <A href="#1.4">1.4</A>) óÕÝÅÓÔ×ÕÀÔ ÌÉ ×ÅÒÓÉÉ ÐÏÒÔÉÒÏ×ÁÎÎÙÅ ÎÅ ÎÁ Unix ÓÉÓÔÅÍÙ?<BR>
-     <A href="#1.5">1.5</A>) çÄÅ ÍÏÖÎÏ ×ÚÑÔØ PostgreSQL?<BR>
-     <A href="#1.6">1.6</A>) çÄÅ ÐÏÌÕÞÉÔØ ÐÏÄÄÅÒÖËÕ?<BR>
-     <A href="#1.7">1.7</A>) ëÁËÁÑ ÐÏÓÌÅÄÎÑÑ ×ÅÒÓÉÑ?<BR>
-     <A href="#1.8">1.8</A>) ëÁËÁÑ ÄÏËÕÍÅÎÔÁÃÉÑ ÉÍÅÅÔÓÑ × ÎÁÌÉÞÉÉ?<BR>
-     <A href="#1.9">1.9</A>) ëÁË ÎÁÊÔÉ ÉÎÆÏÒÍÁÃÉÀ Ï ÉÚ×ÅÓÔÎÙÈ ÏÛÉÂËÁÈ ÉÌÉ ÏÔÓÕÔÓÔ×ÕÀÝÉÈ
-    ×ÏÚÍÏÖÎÏÓÔÑÈ?<BR>
-     <A href="#1.10">1.10</A>) ëÁË ÎÁÕÞÉÔØÓÑ <SMALL>SQL</SMALL>?<BR>
-     <A href="#1.11">1.11</A>) òÅÛÅÎÁ ÌÉ × PostgreSQL ÐÒÏÂÌÅÍÁ 2000-ÇÏ ÇÏÄÁ (Y2K)?<BR>
-     <A href="#1.12">1.12</A>) ëÁË ÐÒÉÓÏÅÄÉÎÉÔÓÑ Ë ËÏÍÁÎÄÅ ÒÁÚÒÁÂÏÔÞÉËÏ×?<BR>
-     <A href="#1.13">1.13</A>) ëÁË ÏÔÒÁ×ÉÔØ ÓÏÏÂÝÅÎÉÅ Ï ÏÛÉÂËÅ?<BR>
-     <A href="#1.14">1.14</A>) ëÁË ÓÒÁ×ÎÉ×ÁÔØ PostgreSQL Ó ÄÒÕÇÉÍÉ
-    <SMALL>óõâä</SMALL>?<BR>
-     <A href="#1.15">1.15</A>) ëÁË ÏËÁÚÁÔØ ÆÉÎÁÎÓÏ×ÕÀ ÐÏÍÏÝØ PostgreSQL?<BR>
-     
-
-    <H2 align="center">÷ÏÐÒÏÓÙ ÐÏÌØÚÏ×ÁÔÅÌÅÊ ÐÏ ËÌÉÅÎÔÓËÏÊ ÞÁÓÔÉ</H2>
-    <A href="#2.1">2.1</A>) óÕÝÅÓÔ×ÕÀÔ ÌÉ <SMALL>ODBC</SMALL> ÄÒÁÊ×ÅÒÁ ÄÌÑ
-    PostgreSQL?<BR>
-     <A href="#2.2">2.2</A>) ëÁËÉÅ ÉÎÓÔÒÕÍÅÎÔÙ ÓÕÝÅÓÔ×ÕÀÔ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ
-    PostgreSQL ÞÅÒÅÚ Web?<BR>
-     <A href="#2.3">2.3</A>) åÓÔØ ÌÉ Õ PostgreSQL ÇÒÁÆÉÞÅÓËÉÊ ÉÎÔÅÒÆÅÊÓ
-    ÐÏÌØÚÏ×ÁÔÅÌÑ? çÅÎÅÒÁÔÏÒ ÏÔÞÅÔÏ×? ÷ÓÔÒÏÅÎÎÙÊ ÉÎÔÅÒÆÅÊÓ ÄÌÑ ÑÚÙËÁ
-    ÚÁÐÒÏÓÏ×?<BR>
-     <A href="#2.4">2.4</A>) ëÁËÉÅ ÑÚÙËÉ ÍÏÇÕÔ ×ÚÁÉÍÏÄÅÊÓÔ×Ï×ÁÔØ Ó
-    PostgreSQL?<BR>
-     
-
-    <H2 align="center">÷ÏÐÒÏÓÙ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ</H2>
-    <A href="#3.1">3.1</A>) ëÁË ÍÎÅ ÕÓÔÁÎÏ×ÉÔØ PostgreSQL × ÍÅÓÔÏ ÏÔÌÉÞÎÏÅ
-    ÏÔ <I>/usr/local/pgsql</I>?<BR>
-     <A href="#3.2">3.2</A>) ëÏÇÄÁ Ñ ÚÁÐÕÓËÁÀ <I>postmaster</I>, Ñ ÐÏÌÕÞÁÀ
-     ÓÏÏÂÝÅÎÉÅ <I>Bad System Call</I> ÉÌÉ ÓÏÏÂÝÅÎÉÅ core dumped. ðÏÞÅÍÕ?<BR>
-     <A href="#3.3">3.3</A>) ëÏÇÄÁ Ñ ÐÙÔÁÀÓØ ÚÁÐÕÓÔÉÔØ <I>postmaster</I>, Ñ
-    ÐÏÌÕÞÁÀ ÏÛÉÂËÉ <I>IpcMemoryCreate</I>. ðÏÞÅÍÕ?<BR>
-     <A href="#3.4">3.4</A>) ëÏÇÄÁ Ñ ÐÙÔÁÀÓØ ÚÁÐÕÓÔÉÔØ <I>postmaster</I>, Ñ
-    ÐÏÌÕÞÁÀ ÏÛÉÂËÉ <I>IpcSemaphoreCreate</I>. ðÏÞÅÍÕ?<BR>
-     <A href="#3.5">3.5</A>) ëÁË ÍÎÅ ÕÐÒÁ×ÌÑÔØ ÓÏÅÄÉÎÅÎÉÑÍÉ Ó ÄÒÕÇÉÈ
-    ËÏÍÐØÀÔÅÒÏ×?<BR>
-     <A href="#3.6">3.6</A>) ëÁËÉÅ ÎÁÓÔÒÏÊËÉ ÍÎÅ ÎÕÖÎÏ ÓÄÅÌÁÔØ ÄÌÑ ÕÌÕÞÛÅÎÉÑ
-     ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ?<BR>
-     <A href="#3.7">3.7</A>) ëÁËÉÅ ×ÏÚÍÏÖÎÏÓÔÉ ÄÌÑ ÏÔÌÁÄËÉ ÅÓÔØ × ÎÁÌÉÞÉÉ?<BR>
-     <A href="#3.8">3.8</A>) ðÏÞÅÍÕ Ñ ÐÏÌÕÞÁÀ ÓÏÏÂÝÅÎÉÅ <I>"Sorry, too many
-    clients"</I> ËÏÇÄÁ ÐÙÔÁÀÓØ ÐÏÄËÌÀÞÉÔØÓÑ Ë ÂÁÚÅ?<BR>
-     <A href="#3.9">3.9</A>) þÔÏ ÜÔÏ ÚÁ ÆÁÊÌÙ <I>pg_sorttempNNN.NN</I>
-    × ÍÏÅÍ ËÁÔÁÌÏÇÅ Ó ÂÁÚÏÊ ÄÁÎÎÙÈ?<BR>
-     
-
-    <H2 align="center">÷ÏÐÒÏÓÙ ÜËÓÐÌÕÁÔÁÃÉÉ</H2>
-    <A href="#4.1">4.1</A>) ÷ ÞÅÍ ÏÔÌÉÞÉÅ ÍÅÖÄÕ ÂÉÎÁÒÎÙÍ É ÎÏÒÍÁÌØÎÙÍ
-    ËÕÒÓÏÒÏÍ?<BR>
-     <A href="#4.2">4.2</A>) ëÁË ×ÙÐÏÌÎÉÔØ <SMALL>SELECT</SMALL> ÔÏÌØËÏ
-     ÄÌÑ ÎÅÓËÏÌØËÉÈ ÐÅÒ×ÙÈ ÓÔÒÏÞÅË ÚÁÐÒÏÓÁ?<BR>
-     <A href="#4.3">4.3</A>) ëÁË ÐÏÌÕÞÉÔØ ÓÐÉÓÏË ÔÁÂÌÉà ÉÌÉ ÄÒÕÇÉÈ
-     ËÏÍÐÏÎÅÎÔÏ× × <I>psql</I>?<BR>
-     <A href="#4.4">4.4</A>) ëÁË ÕÄÁÌÉÔØ ËÏÌÏÎËÕ ÉÚ ÔÁÂÌÉÃÙ?<BR>
-     <A href="#4.5">4.5</A>) ëÁËÏ×Ù ÍÁËÓÉÍÁÌØÎÙÅ ÒÁÚÍÅÒÙ ÄÌÑ ÚÁÐÉÓÅÊ,
-    ÔÁÂÌÉÃ É ÂÁÚÙ ÄÁÎÎÙÈ?<BR>
-     <A href="#4.6">4.6</A>) ëÁË ÍÎÏÇÏ ÄÉÓËÏ×ÏÇÏ ÐÒÏÓÔÒÁÎÓÔ×Á × ÂÁÚÅ ÄÁÎÎÙÈ
-     ÎÕÖÎÏ ÄÌÑ ÓÏÈÒÁÎÅÎÉÑ ÄÁÎÎÙÈ ÉÚ ÏÂÙÞÎÏÇÏ ÔÅËÓÔÏ×ÏÇÏ ÆÁÊÌÁ?<BR>
-     <A href="#4.7">4.7</A>) ëÁË ÍÎÅ ÕÂÅÄÉÔØÓÑ, ÞÔÏ ÓÕÝÅÓÔ×ÕÀÔ ÎÕÖÎÙÅ ÍÎÅ
-     ÔÁÂÌÉÃÙ, ÉÎÄÅËÓÙ, ÂÁÚÙ ÄÁÎÎÙÈ É ÐÏÌØÚÏ×ÁÔÅÌÉ?<BR>
-     <A href="#4.8">4.8</A>) õ ÍÅÎÑ ÍÅÄÌÅÎÎÏ ÒÁÂÏÔÁÀÔ ÚÁÐÒÏÓÙ ÉÌÉ ÎÅ
-     ÐÒÏÉÓÈÏÄÉÔ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÉÎÄÅËÓÏ×. ðÏÞÅÍÕ?<BR>
-     <A href="#4.9">4.9</A>) ëÁË ÐÏÓÍÏÔÒÅÔØ ÎÁ ÔÏ, ËÁË ÏÐÔÉÍÉÚÁÔÏÒ ×ÙÐÏÌÎÑÅÔ
-     ÍÏÊ ÚÁÐÒÏÓ?<BR>
-     <A href="#4.10">4.10</A>) þÔÏ ÔÁËÏÅ R-tree ÉÎÄÅËÓ?<BR>
-     <A href="#4.11">4.11</A>) þÔÏ ÔÁËÏÅ Genetic Query Optimizer?<BR>
-     <A href="#4.12">4.12</A>) ëÁË ÍÎÅ ×ÙÐÏÌÎÉÔØ ÐÏÉÓË ÒÅÇÕÌÑÒÎÏÇÏ ×ÙÒÁÖÅÎÉÑ
-     É ÐÏÉÓË ÎÅÚÁ×ÉÓÉÍÙÊ ÏÔ ÒÅÇÉÓÔÒÁ ÂÕË× ÐÏÉÓË ÒÅÇÕÌÑÒÎÏÇÏ ×ÙÒÁÖÅÎÉÑ?
-     ëÁË ÍÎÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÉÎÄÅËÓ ÄÌÑ ÐÏÉÓËÁ ÎÅÚÁ×ÉÓÉÍÏÇÏ ÏÔ ÒÅÇÉÓÔÒÁ ÂÕË×?<BR>
-     <A href="#4.13">4.13</A>) ëÁË Ñ ÍÏÇÕ ÏÐÒÅÄÅÌÉÔØ, ÞÔÏ ÚÎÁÞÅÎÉÅ ÐÏÌÑ ÒÁ×ÎÏ
-     <SMALL>NULL</SMALL> × ËÁËÏÍ-ÌÉÂÏ ÚÁÐÒÏÓÅ?<BR>
-     <A href="#4.14">4.14</A>) ëÁËÏ×Ù ÏÔÌÉÞÉÑ ÍÅÖÄÕ ÒÁÚÎÙÍÉ ÓÉÍ×ÏÌØÎÙÍÉ
-     ÔÉÐÁÍÉ?<BR>
-     <A href="#4.15.1">4.15.1</A>) ëÁË ÍÎÅ ÓÏÚÄÁÔØ ÐÏÌÅ serial/Ó-Á×ÔÏ-Õ×ÅÌÉÞÅÎÉÅÍ?<BR>
-     <A href="#4.15.2">4.15.2</A>) ëÁË ÍÎÅ ÐÏÌÕÞÉÔØ ÚÎÁÞÅÎÉÅ ÐÒÉ ×ÓÔÁ×ËÅ
-    <SMALL>SERIAL</SMALL>?<BR>
-     <A href="#4.15.3">4.15.3</A>) îÅ ÍÏÖÅÔ ÌÉ ÐÏÌÕÞÉÔØÓÑ ÔÁË, ÞÔÏ
-    ÉÓÐÏÌØÚÏ×ÁÎÉÅ <I>currval()</I> É <I>nextval()</I> ÐÒÉ×ÅÄÅÔ Ë
-    ÚÁÃÉËÌÉÒÏ×ÁÎÉÀ Ó ÄÒÕÇÉÍÉ ÐÏÌØÚÏ×ÁÔÅÌÑÍÉ?<BR>
-     <A href="#4.15.4">4.15.4</A>) ðÏÞÅÍÕ ÞÉÓÌÁ ÉÚ ÍÏÅÊ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÉ
-    ÎÅ ÉÓÐÏÌØÚÕÀÔÓÑ ÓÎÏ×Á ÐÒÉ ÏÔÍÅÎÅ ÔÒÁÎÚÁËÃÉÉ? ðÏÞÅÍÕ ÓÏÚÄÁÀÔÓÑ ÒÁÚÒÙ×Ù
-    ÐÒÉ ÎÕÍÅÒÁÃÉÉ × ËÏÌÏÎËÅ, ÇÄÅ Ñ ÉÓÐÏÌØÚÕÀ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ/SERIAL?<BR>
-     <A href="#4.16">4.16</A>) þÔÏ ÔÁËÏÅ <SMALL>OID</SMALL>? þÔÏ ÔÁËÏÅ
-    <SMALL>TID</SMALL>?<BR>
-     <A href="#4.17">4.17</A>) þÔÏ ÏÚÎÁÞÁÀÔ ÎÅËÏÔÏÒÙÅ ÔÅÒÍÉÎÙ ÉÓÐÏÌØÚÕÅÍÙÅ ×
-    PostgreSQL?<BR>
-     <A href="#4.18">4.18</A>) ðÏÞÅÍÕ Ñ ÐÏÌÕÞÁÀ ÏÛÉÂËÕ <I>"ERROR: Memory
-    exhausted in AllocSetAlloc()"</I>?<BR>
-     <A href="#4.19">4.19</A>) ëÁË ÍÎÅ ÕÚÎÁÔØ, ËÁËÁÑ ×ÅÒÓÉÑ PostgreSQL
-    ÚÁÐÕÝÅÎÁ?<BR>
-     <A href="#4.20">4.20</A>) ðÏÞÅÍÕ ÐÒÉ ÒÁÂÏÔÅ Ó ÍÏÉÍ ÂÏÌØÛÉÍ ÏÂßÅËÔÏÍ
-     Ñ ÐÏÌÕÞÁÀ ÏÛÉÂËÕ <I>"invalid large obj descriptor"</I>?<BR>
-     <A href="#4.21">4.21</A>) ëÁË ÍÎÅ ÓÏÚÄÁÔØ ËÏÌÏÎËÕ ËÏÔÏÒÁÑ ÐÏ ÕÍÏÌÞÁÎÉÀ
-     ÂÕÄÅÔ ÓÏÄÅÒÖÁÔØ ÔÅËÕÝÅÅ ×ÒÅÍÑ?<BR>
-     <A href="#4.22">4.22</A>) ðÏÞÅÍÕ ÍÏÉ ÐÏÄÚÁÐÒÏÓÙ, ÉÓÐÏÌØÚÕÀÝÉÅ
-    <CODE><SMALL>IN</SMALL></CODE> ÔÁË ÍÅÄÌÅÎÎÏ ÒÁÂÏÔÁÅÀÔ?<BR>
-     <A href="#4.23">4.23</A>) ëÁË ×ÙÐÏÌÎÉÔØ ×ÎÅÛÎÅÅ Ó×ÑÚÙ×ÁÎÉÅ?<BR>
-     <A href="#4.24">4.24</A>) ëÁË ×ÙÐÏÌÎÑÔØ ÚÁÐÒÏÓÙ, ÉÓÐÏÌØÚÕÀÝÉÅ ÎÅÓËÏÌØËÏ
-     ÂÁÚ ÄÁÎÎÙÈ?<BR>
-     <A href="#4.25">4.25</A>) ëÁË ÍÎÅ ×ÅÒÎÕÔØ ÉÚ ÆÕÎËÃÉÉ ÎÅÓËÏÌØËÏ ÚÁÐÉÓÅÊ?<BR>
-     <A href="#4.26">4.26</A>) ðÏÞÅÍÕ Ñ ÎÅ ÍÏÇÕ ÎÁÄÅÖÎÏ ÓÏÚÄÁ×ÁÔØ/ÕÄÁÌÑÔØ
-     ×ÒÅÍÅÎÎÙÅ ÔÁÂÌÉÃÙ × ÆÕÎËÃÉÑÈ PL/PgSQL?<BR>
-
-    <H2 align="center">òÁÓÛÉÒÅÎÉÑ PostgreSQL</H2>
-    <A href="#5.1">5.1</A>) ñ ÎÁÐÉÓÁÌ ÆÕÎËÃÉÀ ÏÐÒÅÄÅÌÑÅÍÕÀ ÐÏÌØÚÏ×ÁÔÅÌÅÍ.
-    ëÏÇÄÁ Ñ ÚÁÐÕÓËÁÀ ÅÅ × <I>psql</I>, ÐÏÞÅÍÕ Ñ ÐÏÌÕÞÁÀ dump core?<BR>
-     <A href="#5.2">5.2</A>) ëÁË Ñ ÍÏÇÕ ×ÎÅÓÔÉ ÎÅËÏÔÏÒÙÅ ËÌÁÓÓÎÙÅ ÎÏ×ÙÅ
-     ÔÉÐÙ É ÆÕÎËÃÉÉ × PostgreSQL?<BR>
-     <A href="#5.3">5.3</A>) ëÁË ÍÎÅ ÎÁÐÉÓÁÔØ C ÆÕÎËÃÉÀ, ×ÏÚ×ÒÁÝÁÀÝÕÀ
-    ÚÁÐÉÓØ?<BR>
-     <A href="#5.4">5.4</A>) ñ ÉÚÍÅÎÉÌ ÉÓÈÏÄÎÙÊ ÆÁÊÌ. ðÏÞÅÍÕ ÐÏÓÌÅ
-     ÐÅÒÅËÏÍÐÉÌÑÃÉÉ Ñ ÎÅ ×ÉÖÕ ÉÚÍÅÎÅÎÉÊ?<BR>
-     
-    <HR>
-
-    <H2 align="center">ïÂÝÉÅ ×ÏÐÒÏÓÙ</H2>
-
-    <H4><A name="1.1">1.1</A>) þÔÏ ÔÁËÏÅ PostgreSQL?</H4>
-
-    <P>PostgreSQL ÐÒÏÉÚÎÏÓÉÔÓÑ <I>Post-Gres-Q-L (ðÏÓÔ-çÒÅÓ-ëØÀ-üÌ)</I>.</P>
-
-    <P>PostgreSQL - ÜÔÏ ÒÁÓÛÉÒÅÎÉÅ óõâä POSTGRES, ÉÓÓÌÅÄÏ×ÁÔÅÌØÓËÉÊ
-    ÐÒÏÔÏÔÉÐ ÎÏ×ÏÇÏ ÐÏËÏÌÅÎÉÑ <SMALL>óõâä</SMALL>.
-    PostgreSQL ÏÄÎÏ×ÒÅÍÅÎÎÏ ÓÏÈÒÁÎÑÅÔ ÍÏÝÎÕÀ ÍÏÄÅÌØ ÄÁÎÎÙÈ É ÏÂÝÉÒÎÏÅ
-    ËÏÌÉÞÅÓÔ×Ï ÔÉÐÏ× POSTGRES, É ÚÁÍÅÝÁÅÔ ÑÚÙË ÚÁÐÒÏÓÏ× PostQuel ÎÁ
-    ÒÁÓÛÉÒÅÎÎÏÅ ÐÏÄÍÎÏÖÅÓÔ×Ï <SMALL>SQL</SMALL>. PostgreSQL - ÜÔÏ
-    Ó×ÏÂÏÄÎÏÅ É ÐÏÌÎÏÓÔØÀ ÏÔËÒÙÔÏÅ ÐÒÏÇÒÁÍÍÎÏÅ ÏÂÅÓÐÅÞÅÎÉÅ.</P>
-
-    <P>òÁÚÒÁÂÏÔËÕ PostgreSQL ×ÙÐÏÌÎÑÅÔ ËÏÍÁÎÄÁ,
-    Ó×ÑÚÁÎÎÁÑ ÞÅÒÅÚ Internet, ×ÓÅ ÕÞÁÓÔÎÉËÉ ËÏÔÏÒÏÊ ÐÏÄÐÉÓÁÎÙ ÎÁ ÓÐÉÓÏË
-    ÒÁÓÓÙÌËÉ ÒÁÚÒÁÂÏÔÞÉËÏ×. ÷ ÎÁÓÔÏÑÝÅÅ ×ÒÅÍÑ, ÉÈ ËÏÏÒÄÉÎÁÔÏÒÏÍ
-    Ñ×ÌÑÅÔÓÑ íÁÒË æÏÒÎÁÊ (Marc G. Fournier) (<A href=
-    "mailto:scrappy@PostgreSQL.org">scrappy@PostgreSQL.org</A>). (óÍ.
-    ÎÉÖÅ Ï ÔÏÍ, ËÁË ÐÏÄËÌÀÞÉÔØÓÑ Ë ÒÁÚÒÁÂÏÔËÅ). üÔÁ ËÏÍÁÎÄÁ ÔÅÐÅÒØ
-    ÏÔ×ÅÞÁÅÔ ÚÁ ×ÓÀ ÒÁÚÒÁÂÏÔËÕ PostgreSQL.</P>
-
-    <P>á×ÔÏÒÁÍÉ PostgreSQL 1.01 Ñ×ÌÑÀÔÓÑ üÎÄÒÀ à (Andrew Yu) É äÖÏÌÉ þÅÎ 
-    (Jolly Chen). íÎÏÇÉÅ ÄÒÕÇÉÅ ×ÎÅÓÌÉ Ó×ÏÊ ×ËÌÁÄ × ÐÅÒÅÎÏÓ ÎÁ ÄÒÕÇÉÅ
-    ÐÌÁÔÆÏÒÍÙ, ÔÅÓÔÉÒÏ×ÁÎÉÅ, ÏÔÌÁÄËÕ É ÒÁÓÛÉÒÅÎÉÅ ÜÔÏÇÏ ËÏÄÁ. ðÅÒ×ÏÎÁÞÁÌØÎÙÊ
-    ËÏÄ Postgres,  ÉÚ ËÏÔÏÒÏÇÏ ÐÏÑ×ÉÌÓÑ PostgreSQL, ÂÙÌ ÉÔÏÇÏÍ ÕÓÉÌÉÊ ÍÎÏÇÉÈ
-    ÁËÁÄÅÍÉÞÅÓËÉÈ ÓÔÕÄÅÎÔÏ×, ÎÅÁËÁÄÅÍÉÞÅÓËÉÈ ÓÔÕÄÅÎÔÏ× É ÍÎÏÖÅÓÔ×Á
-    ÒÁÚÎÙÈ ÐÒÏÇÒÁÍÍÉÓÔÏ×, ÒÁÂÏÔÁ×ÛÉÈ ÐÏÄ ÒÕËÏ×ÏÄÓÔ×ÏÍ ÐÒÏÆÅÓÓÏÒÁ
-    íÁÊËÌÁ óÔÏÕÎÂÒÅÊËÅÒÁ (Michael Stonebraker) × ëÁÌÉÆÏÒÎÉÊÓËÏÍ ÕÎÉ×ÅÒÓÉÔÅÔÅ,
-    âÅÒËÌÉ.</P>
-
-    <P>ðÅÒ×ÏÎÁÞÁÌØÎÏÅ ÉÍÑ, ÄÁÎÎÏÅ × âÅÒËÌÉ, ÂÙÌÏ Postgres. ëÏÇÄÁ
-    × 1995 ÇÏÄÕ ÂÙÌÁ ÄÏÂÁ×ÌÅÎÁ ÆÕÎËÃÉÏÎÁÌØÎÏÓÔØ <SMALL>SQL</SMALL>,
-    ÜÔÏ ÉÍÑ ÂÙÌÏ ÉÚÍÅÎÅÎÏ ÎÁ Postgres95. îÏ É ÜÔÏ ÉÍÑ ÂÙÌÏ ÉÚÍÅÎÅÎÏ
-    × ËÏÎÃÅ 1996 ÎÁ PostgreSQL.</P>
-
-    <H4><A name="1.2">1.2</A>) ëÁËÏ×Ù Á×ÔÏÒÓËÉÅ ÐÒÁ×Á ÎÁ PostgreSQL?</H4>
-
-    <P>PostgreSQL ÐÏÐÁÄÁÅÔ ÐÏÄ ÄÅÊÓÔ×ÉÅ ÓÌÅÄÕÀÝÅÇÏ COPYRIGHT:</P>
-
-    <P>óÉÓÔÅÍÁ õÐÒÁ×ÌÅÎÉÑ âÁÚÁÍÉ äÁÎÎÙÈ PostgreSQL</P>
-
-    <P>Portion copyright (c) 1996-2002, PostgreSQL Global Development
-    Group Portions Copyright (c) 1994-6 Regents of the University of
-    California</P>
-
-    <P>ðÒÅÄÏÓÔÁ×ÌÑÀÔÓÑ ÐÒÁ×Á ÎÁ ÉÓÐÏÌØÚÏ×ÁÎÉÅ, ËÏÐÉÒÏ×ÁÎÉÅ, ÉÚÍÅÎÅÎÉÅ
-    É ÒÁÓÐÒÏÓÔÒÁÎÅÎÉÅ ÄÁÎÎÏÇÏ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ É ÅÇÏ ÄÏËÕÍÅÎÔÁÃÉÉ
-    ÄÌÑ ÌÀÂÙÈ ÃÅÌÅÊ, ÂÅÓÐÌÁÔÎÏ É ÂÅÚ ÐÏÄÐÉÓÁÎÉÑ ËÁËÏÇÏ-ÌÉÂÏ ÓÏÇÌÁÛÅÎÉÑ,
-    ÐÒÉ ÕÓÌÏ×ÉÉ ÞÔÏ ÄÌÑ ËÁÖÄÏÊ ËÏÐÉÉ ÂÕÄÕÔ ÐÒÅÄÏÓÔÁ×ÌÅÎÙ ÄÁÎÎÏÅ ×ÙÛÅ
-    ÚÁÍÅÞÁÎÉÅ Ï Á×ÔÏÒÓËÉÈ ÐÒÁ×ÁÈ, ÔÅËÕÝÉÊ ÐÁÒÁÇÒÁÆ É Ä×Á ÓÌÅÄÕÀÝÉÈ
-    ÐÁÒÁÇÒÁÆÁ.</P>
-
-    <P>ëáìéæïòîéêóëéê õîé÷åòóéôåô îå îåóåô îéëáëïê ïô÷åôóô÷åîîïóôé
-    úá ìàâùå ðï÷òåöäåîéñ, ÷ëìàþáñ ðïôåòà äïèïäá, îáîåóåîîùå ðòñíùí
-    éìé îåðòñíùí, óðåãéáìøîùí éìé óìõþáêîùí éóðïìøúï÷áîéåí äáîîïçï
-    ðòïçòáííîïçï ïâåóðåþåîéñ éìé åçï äïëõíåîôáãéé, äáöå åóìé
-    ëáìéæïòîéêóëéê õîé÷åòóéôåô âùì éú÷åýåî ï ÷ïúíïöîïóôé ôáëéè
-    ðï÷òåöäåîéê.</P>
-
-    <P>ëáìéæïòîéêóëéê õîé÷åòóéôåô óðåãéáìøîï ïôëáúù÷áúù÷áåôóñ ðòåäïóôá÷ìñôø
-    ìàâùå çáòáîôéé, ÷ëìàþáñ, îï îå ïçòáîéþé÷áñóø ôïìøëï üôéíé çáòáîôéñíé:
-    îåñ÷îùå çáòáîôéé ðòéçïäîïóôé ôï÷áòá éìé ðòéçïäîïóôé äìñ ïôäåìøîïê ãåìé.
-    äáîîïå ðòïçòáííîïå ïâåóðåþåîéå ðòåäïóôá÷ìñåôóñ îá ïóîï÷å ðòéãéðá
-    "ëáë åóôø" é ëáìéæïòîéêóëéê õîé÷åòóéôåô îå ïâñúáî ðòåäïóôá÷ìñôø
-    óïðòï÷ïöäåîéå, ðïääåòöëõ, ïâîï÷ìåîéñ, òáóûéòåîéñ éìé éúíåîåîéñ.</P>
-
-    <P>÷ÙÛÅÉÚÌÏÖÅÎÎÏÅ Ñ×ÌÑÅÔÓÑ BSD ÌÉÃÅÎÚÉÅÊ, ËÌÁÓÓÉÞÅÓËÏÊ ÌÉÃÅÎÚÉÅÊ
-    ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ Ó ÏÔËÒÙÔÙÍ ËÏÄÏÍ. üÔÁ ÌÉÃÅÎÚÉÑ ÎÅ ÎÁËÌÁÄÙ×ÁÅÔ
-    ÏÇÒÁÎÉÞÅÎÉÊ ÎÁ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÉÓÈÏÄÎÏÇÏ ËÏÄÁ. îÁÍ ÎÒÁ×ÉÔÓÑ ÜÔÁ ÌÉÃÅÎÚÉÑ
-    É ÍÙ ÎÅ ÓÏÂÉÒÁÅÍÓÑ Å£ ÍÅÎÑÔØ.</P>
-
-    <H4><A name="1.3">1.3</A>) îÁ ËÁËÉÈ Unix ÐÌÁÔÆÏÒÍÁÈ ÒÁÂÏÔÁÅÔ PostgreSQL?</H4>
-
-    <P>ïÂÙÞÎÏ, PostgreSQL ÍÏÖÅÔ ÒÁÂÏÔÁÔØ ÎÁ ÌÀÂÏÊ ÓÏ×ÒÅÍÅÎÎÏÊ ÐÌÁÔÆÏÒÍÅ
-    ÓÏ×ÍÅÓÔÉÍÏÊ Ó Unix. ÷ ÉÎÓÔÒÕËÃÉÉ ÐÏ ÕÓÔÁÎÏ×ËÅ, ×Ù ÎÁÊÄÅÔÅ ÓÐÉÓÏË
-    ÔÅÈ ÐÌÁÔÆÏÒÍ, ÎÁ ËÏÔÏÒÙÈ ÂÙÌÉ ÐÒÏ×ÅÄÅÎÙ ÔÅÓÔÏ×ÙÅ ÚÁÐÕÓËÉ PostgreSQL
-    Ë ÍÏÍÅÎÔÕ ×ÙÈÏÄÁ ÄÁÎÎÏÊ ×ÅÒÓÉÉ.</P>
-
-    <H4><A name="1.4">1.4</A>) óÕÝÅÓÔ×ÕÀÔ ÌÉ ×ÅÒÓÉÉ ÐÅÒÅÎÅÓÅÎÎÙÅ ÎÅ ÎÁ Unix
-    ÓÉÓÔÅÍÙ?</H4>
-
-    <P><STRONG>ëÌÉÅÎÔ</STRONG></P>
-
-    <P>äÌÑ ÚÁÐÕÓËÁ ÎÁ ÐÌÁÔÆÏÒÍÁÈ MS Windows ×ÏÚÍÏÖÎÁ ËÏÍÐÉÌÑÃÉÑ C
-    ÂÉÂÌÉÏÔÅËÉ <I>libpq</I>, psql É ÄÒÕÇÉÈ ÉÎÔÅÒÆÅÓÏ× É ÂÉÎÁÒÎÙÈ ÆÁÊÌÏ×.
-    ÷ ÜÔÏÍ ÓÌÕÞÁÅ, ËÌÉÅÎÔ ÚÁÐÕÓËÁÅÔÓÑ ÎÁ MS Windows É Ó×ÑÚÙ×ÁÅÔÓÑ ÐÏ
-    TCP/IP Ó ÓÅÒ×ÅÒÏÍ, ÚÁÐÕÝÅÎÎÙÍ ÎÁ ÏÄÎÏÊ ÉÚ ÐÏÄÄÅÒÖÉ×ÁÅÍÙÈ Unix
-    ÐÌÁÔÆÏÒÍ. ÷ ÄÉÓÔÒÉÂÕÔÉ× ×ËÌÀÞÁÅÔÓÑ ÆÁÊÌ <I>win31.mak</I> ÄÌÑ ÔÏÇÏ,
-    ÞÔÏÂÙ ÍÏÖÎÏ ÂÙÌÏ ÐÒÏ×ÅÓÔÉ ÓÂÏÒËÕ ÂÉÂÌÉÏÔÅËÉ <I>libpq</I> É
-    <I>psql</I> ÄÌÑ Win32. PostgreSQL ÔÁËÖÅ ÒÁÂÏÔÁÅÔ ÞÅÒÅÚ
-    <SMALL>ODBC</SMALL>.</P>
-
-    <P><STRONG>óÅÒ×ÅÒ</STRONG></P>
-
-    <P>óÅÒ×ÅÒ âä ÍÏÖÅÔ ÂÙÔØ ÚÁÐÕÝÅÎ ÎÁ Windows NT É Win2k, ÉÓÐÏÌØÚÕÑ
-    ÂÉÂÌÉÏÔÅËÕ Cygwin, ÒÁÚÒÁÂÏÔÁÎÎÕÀ ÄÌÑ ÐÅÒÅÎÏÓÁ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ Unix
-    × NT. óÍÏÔÒÉÔÅ <I>pgsql/doc/FAQ_MSWIN</I> × ÄÉÓÔÒÉÂÕÔÉ×Å ÉÌÉ <A href=
-    "http://www.postgresql.org/docs/faq-mswin.html">MS Windows FAQ</A>
-    ÎÁ ÎÁÛÅÍ ÓÁÊÔÅ. íÙ ÎÅ ÐÌÁÎÉÒÕÅÍ ÓÐÅÃÉÁÌØÎÏ ÐÅÒÅÎÏÓÉÔØ PostgreSQL
-    ÎÁ ËÁËÕÀ-ÌÉÂÏ ÐÌÁÔÆÏÒÍÕ Microsoft.</P>
-
-    <H4><A name="1.5">1.5</A>) çÄÅ ÍÏÖÎÏ ×ÚÑÔØ PostgreSQL?</H4>
-
-    <P>îÁÐÒÉÍÅÒ, ×ÏÓÐÏÌØÚÏ×Á×ÛÉÓØ ÁÎÏÎÉÍÎÙÍ ÄÏÓÔÕÐÏÍ ÎÁ ftp ÓÁÊÔ
-    PostgreSQL <A href=
-    "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub</A>.
-    óÐÉÓÏË ÚÅÒËÁÌ ×Ù ÎÁÊÄÅÔÅ ÎÁ ÎÁÛÅÍ ÏÓÎÏ×ÎÏÍ ÓÁÊÔÅ.</P>
-
-    <H4><A name="1.6">1.6</A>) çÄÅ ÐÏÌÕÞÉÔØ ÐÏÄÄÅÒÖËÕ?</H4>
-
-    <P>ïÓÎÏ×ÎÏÊ ÓÐÉÓÏË ÒÁÓÓÙÌËÉ: <A href=
-    "mailto:pgsql-general@PostgreSQL.org">pgsql-general@PostgreSQL.org</A>.
-    ÷ ÎÅÍ ÍÏÖÎÏ ÏÂÓÕÖÄÁÔØ ÌÀÂÙÅ ÔÅÍÙ, ËÁÓÁÀÝÉÅÓÑ PostgreSQL. þÔÏÂÙ
-    ÐÏÄÐÉÓÁÔØÓÑ, ÏÔÐÒÁ×ØÔÅ ÐÉÓØÍÏ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ, × ËÏÔÏÒÏÍ ×
-    ÔÅÌÅ ÐÉÓØÍÁ (ÎÅ × ÔÅÍÅ) ÎÁÐÉÛÉÔÅ ÓÌÅÄÕÀÝÉÅ ÓÔÒÏËÉ:</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-
-    <P>ÎÁ ÁÄÒÅÓ <A href=
-    "mailto:pgsql-general-request@PostgreSQL.org">pgsql-general-request@PostgreSQL.org</A>.</P>
-
-    <P>óÕÝÅÓÔ×ÕÅÔ ÄÁÊÖÅÓÔ ÓÐÉÓÏË. þÔÏÂÙ ÐÏÄÐÉÓÁÔØÓÑ ÎÁ ÎÅÇÏ, ÏÔÐÒÁ×ØÔÅ
-    ÐÉÓØÍÏ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ ÎÁ ÁÄÒÅÓ: <A href=
-    "mailto:pgsql-general-digest-request@PostgreSQL.org">pgsql-general-digest-request@PostgreSQL.org</A>
-    É × ÔÅÌÅ ÐÉÓØÍÁ ÎÁÐÉÛÉÔÅ ÓÔÒÏÞËÉ ÓÔÒÏÞËÉ:</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-    äÁÊÖÅÓÔÙ ÏÔÐÒÁ×ÌÑÀÔÓÑ ÐÏÄÐÉÓÞÉËÁÍ, ËÏÇÄÁ × ÏÓÎÏ×ÎÏÍ ÓÐÉÓËÅ ÒÁÓÓÙÌËÉ
-    ÎÁËÏÐÉÔÓÑ ÏËÏÌÏ 30 ËÉÌÏÂÁÊÔ ÓÏÏÂÝÅÎÉÊ.
-
-    <P>äÏÓÔÕÐÅÎ É ÓÐÉÓÏË ÒÁÓÓÙÌËÉ ÓÏÏÂÝÅÎÉÊ Ï ÏÛÉÂËÁÈ. þÔÏÂÙ ÐÏÄÐÉÓÁÔØÓÑ ÎÁ ÜÔÏÔ
-    ÓÐÉÓÏË, ÏÔÐÒÁ×ØÔÅ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ ÐÉÓØÍÏ ÎÁ ÁÄÒÅÓ <A href=
-    "mailto:pgsql-bugs-request@PostgreSQL.org">pgsql-bugs-request@PostgreSQL.org</A>
-    É × ÔÅÌÅ ÐÉÓØÍÁ ÎÁÐÉÛÉÔÅ ÓÔÒÏÞËÉ ÓÔÒÏÞËÉ:</P>
-<PRE>
-    subscribe
-    end
-</PRE>
-    ôÁËÖÅ ÉÍÅÅÔÓÑ ÓÐÉÓÏË ÒÁÓÓÙÌËÉ Ó ÄÉÓËÕÓÓÉÑÍÉ ÒÁÚÒÁÂÏÔÞÉËÏ×. þÔÏÂÙ ÐÏÄÐÉÓÁÔØÓÑ
-    ÎÁ ÜÔÏÔ ÓÐÉÓÏË, ÏÔÐÒÁ×ØÔÅ ÐÏ ÜÌÅËÔÒÏÎÎÏÊ ÐÏÞÔÅ ÐÉÓØÍÏ ÎÁ ÁÄÒÅÓ
-     <A href=
-    "mailto:pgsql-hackers-request@PostgreSQL.org">pgsql-hackers-request@PostgreSQL.org</A>
-    É × ÔÅÌÅ ÐÉÓØÍÁ ÎÁÐÉÛÉÔÅ ÓÔÒÏÞËÉ ÓÔÒÏÞËÉ:
-<PRE>
-    subscribe
-    end
-</PRE>
-
-    <P>äÏÐÏÌÎÉÔÅÌØÎÙÅ ÓÐÉÓËÉ ÒÁÓÓÙÌËÉ É ÉÎÆÏÍÁÃÉÀ Ï PostgreSQL ÍÏÖÎÏ ÎÁÊÔÉ
-    ÎÁ ÄÏÍÁÛÎÅÊ ÓÔÒÁÎÉÞËÅ PostgreSQL ÐÏ ÁÄÒÅÓÕ:</P>
-
-    <BLOCKQUOTE>
-      <A href="http://www.PostgreSQL.org">http://www.PostgreSQL.org</A>
-    </BLOCKQUOTE>
-
-    <P>åÝÅ ÓÕÝÅÓÔ×ÕÅÔ IRC ËÁÎÁÌ ÎÁ EFNet, Ó ÎÁÚ×ÁÎÉÅÍ
-    <I>#PostgreSQL</I>. ñ ÉÓÐÏÌØÚÕÀ ÄÌÑ ÐÏÄËÌÀÞÅÎÉÑ Ë ÜÔÏÍÕ ËÁÎÁÌÕ ËÏÍÁÎÄÕ Unix
-    <CODE>irc -c '#PostgreSQL' "$USER" irc.phoenix.net.</CODE></P>
-
-    <P>óÐÉÓÏË ËÏÍÍÅÒÞÅÓËÏÊ ÐÏÄÄÅÒÖËÉ ËÏÍÐÁÎÉÊ ÄÏÓÔÕÐÅÎ ÎÁ
-    <A href=
-    "http://www.postgresql.org/users-lounge/commercial-support.html">http://www.postgresql.org/users-lounge/commercial-support.html</A>.</P>
-
-    <H4><A name="1.7">1.7</A>) ëÁËÁÑ ÐÏÓÌÅÄÎÑÑ ×ÅÒÓÉÑ?</H4>
-
-    <P>ðÏÓÌÅÄÎÉÊ ×ÙÐÕÓË PostgreSQL - ÜÔÏ ×ÅÒÓÉÑ 7.2.</P>
-
-    <P>íÙ ÐÌÁÎÉÒÕÅÍ ×ÙÐÕÓËÁÔØ ÎÏ×ÙÅ ×ÅÒÓÉÉ ËÁÖÄÙÅ ÞÅÔÙÒÅ ÍÅÓÑÃÁ.</P>
-
-    <H4><A name="1.8">1.8</A>) ëÁËÁÑ ÄÏËÕÍÅÎÔÁÃÉÑ ÉÍÅÅÔÓÑ × ÎÁÌÉÞÉÉ?</H4>
-
-    <P>÷ ÄÉÓÔÒÉÂÕÔÉ× ×ËÌÀÞÁÀÔÓÑ ÒÁÚÌÉÞÎÙÅ ÒÕËÏ×ÏÄÓÔ×Á, ÓÔÒÁÎÉÃÙ
-    ÜÌÅËÔÒÏÎÎÏÇÏ ÒÕËÏ×ÏÄÓÔ×Á man É ÎÅËÏÔÏÒÙÅ ÍÁÌÅÎØËÉÅ ÔÅÓÔÏ×ÙÅ ÐÒÉÍÅÒÙ.
-    óÍÏÔÒÉÔÅ × ËÁÔÁÌÏÇ <I>/doc</I>. ÷Ù ÔÁËÖÅ ÍÏÖÅÔÅ ÐÒÏÓÍÁÔÒÉ×ÁÔØ
-    ÄÏËÕÍÅÎÔÁÃÉÀ × éÎÔÅÒÎÅÔ ÐÏ ÁÄÒÅÓÕ <A href=
-    "http://www.PostgreSQL.org/users-lounge/docs/">http://www.PostgreSQL.org/users-lounge/docs/</A>.</P>
-
-    <P>óÕÝÅÓÔ×ÕÅÔ Ä×Å ËÎÉÇÉ ÐÏ PostgreSQL ÄÏÓÔÕÐÎÙÅ ÐÏ ÁÄÒÅÓÁÍ <A href=
-    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
-     É <a href="http://www.commandprompt.com/ppbook/">http://www.commandprompt.com/ppbook/</a>.
-     óÐÉÓÏË ËÎÉÇ ÐÏ PostgreSQL, ËÏÔÏÒÙÅ ÍÏÖÎÏ ËÕÐÉÔØ ÄÏÓÔÕÐÅÎ ÐÏ ÁÄÒÅÓÕ
-     <a href="http://www.postgresql.org/books/">http://www.postgresql.org/books/</a>.
-     ëÒÏÍÅ ÔÏÇÏ, ÐÏ ÁÄÒÅÓÕ <a href="http://techdocs.postgresql.org">http://techdocs.postgresql.org/</a>
-     ×Ù ÍÏÖÅÔÅ ÎÁÊÔÉ ËÏÌÌÅËÃÉÀ ÔÅÈÎÉÞÅÓËÉÈ ÓÔÁÔÅÊ ÐÏÓ×ÑÝÅÎÎÙÈ PostgreSQL.</p>
-
-
-    <P><I>psql</I> ÉÍÅÅÔ ÎÅÓËÏÌØËÏ ÐÒÅËÒÁÓÎÙÈ ËÏÍÁÎÄ \d ÄÌÑ ÏÔÏÂÒÁÖÅÎÉÑ
-    ÉÎÆÏÒÍÁÃÉÉ ÐÏ ÔÉÐÁÍ, ÏÐÅÒÁÔÏÒÁÍ, ÆÕÎËÃÉÑÍ, ÁÇÒÅÇÁÔÁÍ É Ô.Ä.</P>
-
-    <P>îÁÛ ÓÁÊÔ ÓÏÄÅÒÖÉÔ ÅÝÅ ÂÏÌØÛÅ ÉÎÆÏÒÍÁÃÉÉ.</P>
-
-    <H4><A name="1.9">1.9</A>) ëÁË ÎÁÊÔÉ ÉÎÆÏÒÍÁÃÉÀ Ï ÉÚ×ÅÓÔÎÙÈ ÏÛÉÂËÁÈ
-    ÉÌÉ ÏÔÓÕÔÓÔ×ÕÀÝÉÈ ×ÏÚÍÏÖÎÏÓÔÑÈ?</H4>
-
-    <P>PostgreSQL ÐÏÄÄÅÒÖÉ×ÁÅÔ ÒÁÓÛÉÒÅÎÎÙÊ ÐÏÄËÌÁÓÓ <SMALL>SQL</SMALL>-92.
-    óÍÏÔÒÉÔÅ ÎÁÛ ÓÐÉÓÏË <A href="http://developer.postgresql.org/todo.php">TODO</A>
-    ÎÁ ÐÒÅÄÍÅÔ ÉÚ×ÅÓÔÎÙÈ ÏÛÉÂÏË, ÏÔÓÕÔÓÔ×ÕÀÝÉÈ ÏÓÏÂÅÎÎÏÓÔÑÈ É ÂÕÄÕÝÉÈ
-    ÐÌÁÎÏ×.</P>
-
-    <H4><A name="1.10">1.10</A>) ëÁË ÍÎÅ ÎÁÕÞÉÔØÓÑ <SMALL>SQL</SMALL>?</H4>
-
-    <P>ëÎÉÇÁ ÐÏ PostgreSQL ÎÁ <A href=
-    "http://www.PostgreSQL.org/docs/awbook.html">http://www.PostgreSQL.org/docs/awbook.html</A>
-    ÎÁÕÞÉÔ <SMALL>SQL</SMALL>. óÕÝÅÓÔ×ÕÅÔ ÄÒÕÇÁÑ ËÎÉÇÁ ÐÏ PostgreSQL ÎÁ
-    <A href="http://www.commandprompt.com/ppbook/">
-    http://www.commandprompt.com/ppbook.</A>
-    åÓÔØ ÐÒÅËÒÁÓÎÙÊ ÕÞÅÂÎÉË ÎÁ <A href=
-    "http://www.intermedia.net/support/sql/sqltut.shtm">http://www.intermedia.net/support/sql/sqltut.shtm,</A>
-    ÎÁ <A href=
-    "http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM">
-    http://ourworld.compuserve.com/homepages/graeme_birchall/HTM_COOK.HTM,</A>
-    É ÎÁ <A href=
-    "http://sqlcourse.com/">http://sqlcourse.com.</A></P>
-
-    <P>åÝÅ ÏÄÉÎ ÕÞÅÂÎÉË - ÜÔÏ ËÎÉÇÁ "Teach Yourself SQL in 21 Days, Second Edition"
-    (ïÓ×ÏÊ ÓÁÍÏÓÔÏÑÔÅÌØÎÏ SQL ÚÁ 21 ÄÅÎØ, ÷ÔÏÒÁÑ ÒÅÄÁËÃÉÑ)
-    ÎÁ <A href=
-    "http://members.tripod.com/er4ebus/sql/index.htm">http://members.tripod.com/er4ebus/sql/index.htm</A></P>
-
-    <P>íÎÏÇÉÍ ÉÚ ÎÁÛÉÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ ÎÒÁ×ÉÔÓÑ ËÎÉÇÁ
-    <I>The Practical SQL Handbook</I>,
-    Bowman, Judith S., et al., Addison-Wesley. äÒÕÇÉÍ ÎÒÁ×ÉÔÓÑ <I>The
-    Complete Reference SQL</I>, Groff et al., McGraw-Hill.</P>
-
-    <H4><A name="1.11">1.11</A>) òÅÛÅÎÁ ÌÉ × PostgreSQL ÐÒÏÂÌÅÍÁ 2000-ÇÏ ÇÏÄÁ (Y2K)?</H4>
-
-    <P>äÁ, ÍÙ ÌÅÇËÏ ÍÁÎÉÐÕÌÉÒÕÅÍ ÄÁÔÁÍÉ ÐÏÓÌÅ 2000 ÇÏÄÁ É ÐÅÒÅÄ 2000 ÇÏÄÏÍ.</P>
-
-    <H4><A name="1.12">1.12</A>) ëÁË ÐÒÉÓÏÅÄÉÎÉÔÓÑ Ë ËÏÍÁÎÄÅ ÒÁÚÒÁÂÏÔÞÉËÏ×?</H4>
-
-    <P>äÌÑ ÎÁÞÁÌÁ, ÓËÁÞÁÊÔÅ ÐÏÓÌÅÄÎÀÀ ×ÅÒÓÉÀ ÉÓÈÏÄÎÙÈ ÔÅËÓÔÏ× É ÐÒÏÞÔÉÔÅ
-    ÄÏËÕÍÅÎÔÁÃÉÀ ÒÁÚÒÁÂÏÔÞÉËÏ× PostgreSQL ÎÁ ÎÁÛÅÍ ÓÁÊÔÅ ÉÌÉ × ÄÉÓÔÒÉÂÕÔÉ×Å.
-    úÁÔÅÍ, ÐÏÄÐÉÛÉÔÅÓØ ÎÁ ÓÐÉÓËÉ ÒÁÓÓÙÌËÉ <I>pgsql-hackers</I> É
-    <I>pgsql-patches</I>. äÁÌÅÅ, ÏÔÐÒÁ×ÌÑÊÔÅ ÉÓÐÒÁ×ÌÅÎÉÑ (patches) ×ÙÓÏËÏÇÏ
-    ËÁÞÅÓÔ×Á × ÓÐÉÓÏË pgsql-patches.</P>
-
-    <P>óÕÝÅÓÔ×ÕÅÔ ÏÇÒÁÎÉÞÅÎÎÙÊ ÓÐÉÓÏË ÌÀÄÅÊ, ËÏÔÏÒÙÊ ÉÍÅÀÔ ÐÒÉ×ÅÌÅÇÉÀ
-    ×ÎÏÓÉÔØ ÉÚÍÅÎÅÎÉÑ × <SMALL>CVS</SMALL> ÁÒÈÉ× PostgreSQL. ëÁÖÄÙÊ
-    ÉÚ ÜÔÉÈ ÌÀÄÅÊ × Ó×ÏÅ ×ÒÅÍÑ ÏÔÐÒÁ×ÉÌ ÔÁË ÍÎÏÇÏ ×ÙÓÏËÏËÁÞÅÓÔ×ÅÎÎÙÈ ÉÓÐÒÁ×ÌÅÎÉÊ,
-    ÞÔÏ ÉÈ ÂÙÌÏ ÎÅ×ÏÚÍÏÖÎÏ ÏÓÔÁ×ÉÔØ ÂÅÚ ×ÎÉÍÁÎÉÑ É ÏÎÉ ÂÙÌÉ ÕÄÏÓÔÏÅÎÙ
-    ÐÒÅ×ÉÌÅÇÉÉ ×ÎÏÓÉÔØ ÉÚÍÅÎÅÎÉÑ, É ÍÙ Õ×ÅÒÅÎÙ, ÞÔÏ ÔÅ ÉÓÐÒÁ×ÌÅÎÉÑ, ËÏÔÏÒÙÅ
-    ÏÎÉ ×ÎÅÓÕÔ ÂÕÄÕÔ ×ÙÓÏËÏÇÏ ËÁÞÅÓÔ×Á.</P>
-
-    <H4><A name="1.13">1.13</A>) ëÁË ÏÔÒÁ×ÉÔØ ÓÏÏÂÝÅÎÉÅ Ï ÏÛÉÂËÅ??</H4>
-
-    <P>ðÏÖÁÌÕÊÓÔÁ ÐÏÓÅÔÉÔÅ ÓÔÒÁÎÉÞËÕ <A href=
-    "http://www.postgresql.org/bugs/bugs.php">PostgreSQL BugTool</A>,
-    ÎÁ ËÏÔÏÒÏÊ ÐÒÅÄÏÓÔÁ×ÌÅÎÙ ÄÅÔÁÌØÎÙÅ ÉÎÓÔÒÕËÃÉÉ Ï ÔÏÍ ËÁË ÏÔÐÒÁ×ÉÔØ
-    ÓÏÏÂÝÅÎÉÅ ÏÂ ÏÛÉÂËÅ.</P>
-
-    <P>ôÁËÖÅ ÎÅ ÚÁÂÕÄØÔÅ ÐÏÓÍÏÔÒÅÔØ ÎÁ <A href=
-    "ftp://ftp.PostgreSQL.org/pub">ftp://ftp.PostgreSQL.org/pub</A>
-    ÎÁ ÐÒÅÄÍÅÔ ÂÏÌÅÅ Ó×ÅÖÉÈ ×ÅÒÓÉÊ PostgreSQL ÉÌÉ ÚÁÐÌÁÔ.</P>
-
-    <H4><A name="1.14">1.14</A>) ëÁË ÓÒÁ×ÎÉ×ÁÔØ PostgreSQL Ó ÄÒÕÇÉÍÉ
-    <SMALL>óõâä</SMALL>?</H4>
-
-    <P>
-    óÕÝÅÓÔ×ÕÅÔ ÎÅÓËÏÌØËÏ ÍÅÔÏÄÏ× ÓÒÁ×ÎÅÎÉÑ ÐÒÏÇÒÁÍÍÎÏÇÏ ÏÂÅÓÐÅÞÅÎÉÑ:
-    ×ÏÚÍÏÖÎÏÓÔÉ, ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ, ÎÁÄÅÖÎÏÓÔØ, ÐÏÄÄÅÒÖËÁ É ÃÅÎÁ.</P>
-
-    <DL>
-      <DT><B>÷ÏÚÍÏÖÎÏÓÔÉ</B></DT>
-
-      <DD>PostgreSQL ÉÍÅÅÔ ÂÏÌØÛÉÎÓÔ×Ï ×ÏÚÍÏÖÎÏÓÔÅÊ ÐÒÅÄÓÔÁ×ÌÅÎÎÙÈ
-      × ÂÏÌØÛÉÈ ËÏÍÍÅÒÞÅÓËÉÈ <SMALL>óõâä</SMALL>, ÔÁËÉÅ ËÁË: ÔÒÁÎÚÁËÃÉÉ,
-      ÐÏÄÚÁÐÒÏÓÙ, ÔÒÉÇÇÅÒÙ, ÏÂÚÏÒÙ (views), ×ÎÅÛÎÉÊ ËÌÀÞ ÓÓÙÌÏÞÎÏÊ
-      ÃÅÌÏÓÔÎÏÓÔÉ É ÒÁÚÎÙÅ ÂÌÏËÉÒÏ×ËÉ. õ ÎÁÓ ÅÓÔØ ÎÅËÏÔÏÒÙÅ ×ÏÚÍÏÖÎÏÓÔÉ,
-      ËÏÔÏÒÙÈ ÎÅÔ Õ ÎÉÈ: ÔÉÐÙ, ÏÐÒÅÄÅÌÑÅÍÙÅ ÐÏÌØÚÏ×ÁÔÅÌÅÍ, ÍÅÈÁÎÉÚÍ
-      ÎÁÓÌÅÄÏ×ÁÎÉÑ, ÐÒÁ×ÉÌÁ É ËÏÎËÕÒÅÔÎÏÅ ÍÎÏÇÏ×ÅÒÓÉÏÎÎÏÅ ÕÐÒÁ×ÌÅÎÉÅ
-      ÄÌÑ ÒÁÂÏÔÙ Ó ÓÏÄÅÒÖÉÍÙÍ ÂÌÏËÉÒÏ×ÏË.<BR>
-      <BR>
-      </DD>
-
-      <DT><B>ðÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ</B></DT>
-
-      <DD>PostgreSQL ÉÍÅÅÔ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ ÓÈÏÖÕÀ Ó ÄÒÕÇÉÍÉ ËÏÍÍÅÒÞÅÓËÉÍÉ
-      óõâä É Ó óõâä Ó ÏÔËÒÙÔÙÍ ÉÓÈÏÄÎÙÍ ËÏÄÏÍ, × ËÁËÉÈ-ÔÏ ÁÓÐÅËÔÁÈ ÒÁÂÏÔÁÑ
-      ÂÙÓÔÒÅÅ ÞÅÍ ÏÎÉ, × ËÁËÉÈ-ÔÏ ÍÅÄÌÅÎÅÅ. ÷ ÓÒÁ×ÎÅÎÉÉ Ó MySQL ÉÌÉ ÌÉÎÅÊÎÙÍÉ
-      óõâä, ÍÙ ÍÅÄÌÅÎÅÅ ÐÒÉ ÏÐÅÒÁÃÉÑÈ ×ÓÔÁ×ËÉ/ÏÂÎÏ×ÌÅÎÉÑ, ÐÏÔÏÍÕ ÞÔÏ ÕÐÒÁ×ÌÑÅÍ
-      ÔÒÁÎÚÁËÃÉÑÍÉ. é ÒÁÚÕÍÅÅÔÓÑ, MySQL ÎÅ ÉÍÅÅÔ ËÁËÉÈ-ÌÉÂÏ ×ÏÚÍÏÖÎÏÓÔÅÊ ÉÚ
-      ÐÅÒÅÞÉÓÌÅÎÙÈ ×ÙÛÅ, × ÓÅËÃÉÉ <I>÷ÏÚÍÏÖÎÏÓÔÉ</I>. 
-      íÙ ÄÅÌÁÅÍ ÕÐÏÒ ÎÁ ÎÁÄÅÖÎÏÓÔØ É ÒÁÓÛÉÒÅÎÎÙÅ ×ÏÚÍÏÖÎÏÓÔÉ, ÎÏ ÍÙ ÔÁËÖÅ
-      ÐÒÏÄÏÌÖÁÅÍ Õ×ÅÌÉÞÉ×ÁÔØ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ Ó ËÁÖÄÙÍ ×ÙÐÕÓËÏÍ. óÕÝÅÓÔ×ÕÅÔ
-      ÉÎÔÅÒÅÓÎÁÑ ÓÔÒÁÎÉÞËÁ × éÎÔÅÒÎÅÔ, ÓÒÁ×ÎÉ×ÁÀÝÁÑ PostgreSQL É MySQL ÎÁ
-      <A href="http://openacs.org/why-not-mysql.html">
-      
-      http://openacs.org/why-not-mysql.html</A><BR>
-
-      <BR>
-      </DD>
-
-      <DT><B>îÁÄÅÖÎÏÓÔØ</B></DT>
-
-      <DD>íÙ ÐÏÎÉÍÁÌÉ, ÞÔÏ ÎÁÛÁ <SMALL>óõâä</SMALL> ÄÏÌÖÎÁ ÂÙÔØ ÎÁÄÅÖÎÏÊ
-      ÉÌÉ ÏÎÁ ÎÉÞÅÇÏ ÎÅ ÂÕÄÅÔ ÓÔÏÉÔØ. íÙ ÓÔÁÒÁÅÍÓÑ ×ÙÐÕÓËÁÔØ ÈÏÒÏÛÏ ÐÒÏ×ÅÒÅÎÎÙÊ,
-      ÓÔÁÂÉÌØÎÙÊ ËÏÄ, ËÏÔÏÒÙÊ ÓÏÄÅÒÖÉÔ ÍÉÎÉÍÕÍ ÏÛÉÂÏË. ëÁÖÄÙÊ ×ÙÐÕÓË
-      ÐÒÏÈÏÄÉÔ ÓÔÁÄÉÀ ÂÅÔÁ-ÔÅÓÔÉÒÏ×ÁÎÉÑ ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ × ÔÅÞÅÎÉÉ ÏÄÎÏÇÏ
-      ÍÅÓÑÃÁ É ÎÁÛÁ ÉÓÔÏÒÉÑ ×ÙÐÕÓËÏ× ÐÏËÁÚÙ×ÁÅÔ ÞÔÏ ÍÙ ÍÏÖÅÍ ÐÒÅÄÏÓÔÁ×ÌÑÔØ
-      ÓÔÁÂÉÌØÎÙÅ, ÍÏÎÏÌÉÔÎÙÅ ×ÙÐÕÓËÉ, ËÏÔÏÒÙÅ ÇÏÔÏ×Ù Ë ÐÒÏÄÕËÔÉ×ÎÏÍÕ
-      ÉÓÐÏÌØÚÏ×ÁÎÉÀ. íÙ ×ÅÒÉÍ, ÞÔÏ ÍÙ ÐÒÏÉÚ×ÏÄÉÍ ÐÒÏ×ÅÒËÕ ÎÅ ÈÕÖÅ,
-      ÞÅÍ Õ ÄÒÕÇÉÈ óõâä.<BR>
-      <BR>
-      </DD>
-
-      <DT><B>ðÏÄÄÅÒÖËÁ</B></DT>
-
-      <DD>îÁÛ ÓÐÉÓÏË ÒÁÓÓÙÌËÉ ÐÒÅÄÓÔÁ×ÌÅÎ ÂÏÌØÛÏÊ ÇÒÕÐÐÏÊ ÒÁÚÒÁÂÏÔÞÉËÏ×
-      É ÐÏÌØÚÏ×ÁÔÅÌÅÊ, ËÏÔÏÒÙÅ ÍÏÇÕÔ ÐÏÍÏÞØ ÒÅÛÉÔØ ÌÀÂÙÅ ×ÏÚÎÉËÛÉÅ
-      ÐÒÏÂÌÅÍÙ. ÷ ÔÏ ÖÅ ×ÒÅÍÑ, ÍÙ ÎÅ ÇÁÒÁÎÔÉÒÕÅÍ ËÁËÉÅ-ÌÉÂÏ ÉÓÐÒÁ×ÌÅÎÉÑ,
-      ÎÏ É ÒÁÚÒÁÂÏÔÞÉËÉ ËÏÍÍÅÒÞÅÓËÉÈ <SMALL>óõâä</SMALL> ÎÅ ×ÓÅÇÄÁ ÄÅÌÁÀÔ
-      ÉÓÐÒÁ×ÌÅÎÉÑ. ðÒÑÍÏÊ ÄÏÓÔÕÐ Ë ÒÁÚÒÁÂÏÔÞÉËÁÍ, ÓÏÏÂÝÅÓÔ×Õ ÐÏÌØÚÏ×ÁÔÅÌÅÊ,
-      ÒÕËÏ×ÏÄÓÔ×ÁÍ É ÉÓÈÏÄÎÙÍ ÔÅËÓÔÁÍ ÞÁÓÔÏ ÄÅÌÁÀÔ ÐÏÄÄÅÒÖËÕ PostgreSQL
-      ÐÒÅ×ÏÓÈÏÄÑÝÅÊ ÄÒÕÇÉÅ <SMALL>óõâä</SMALL>. óÕÝÅÓÔ×ÕÅÔ ËÏÍÍÅÒÞÅÓËÁÑ
-      ÐÏÄÄÅÒÖËÁ ÐÏ ÒÅÚÕÌØÔÁÍ ×ÏÚÎÉËÛÉÈ ÉÎÃÉÄÅÎÔÏ×, ËÏÔÏÒÁÑ ÄÏÓÔÕÐÎÁ ÄÌÑ
-      ÔÅÈ ËÏÍÕ ÏÎÁ ÎÕÖÎÁ. (óÍÏÔÒÉÔÅ <A href="#1.6">ëÁË ÐÏÌÕÞÉÔØ ÐÏÄÄÅÒÖËÕ?</A>.)<BR>
-      <BR>
-      </DD>
-
-      <DT><B>ãÅÎÁ</B></DT>
-
-      <DD>îÁÛ ÐÒÏÄÕËÔ ÂÅÓÐÌÁÔÅÎ ËÁË ÄÌÑ ËÏÍÍÅÒÞÅÓËÏÇÏ ÔÁË, É ÎÅ ÄÌÑ
-      ËÏÍÍÅÒÞÅÓËÏÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ. ÷Ù ÍÏÖÅÔÅ ÄÏÂÁ×ÌÑÔØ Ó×ÏÊ ËÏÄ × ÎÁÛ
-      ÐÒÏÄÕËÔ ÂÅÚ ÏÇÒÁÎÉÞÅÎÉÊ, ÚÁ ÉÓËÌÀÞÅÎÉÅÍ ÔÅÈ, ÞÔÏ ÏÐÉÓÙ×ÁÀÔÓÑ ×
-      ÎÁÛÅÊ ÌÉÃÅÎÚÉÉ ÓÔÉÌÑ BSD, ËÏÔÏÒÁÑ ÐÒÉ×ÅÄÅÎÁ ×ÙÛÅ.<BR>
-      <BR>
-      </DD>
-    </DL>
-
-    <H4><A name="1.15">1.15</A>) ëÁË ÏËÁÚÁÔØ ÆÉÎÁÎÓÏ×ÕÀ ÐÏÍÏÝØ
-    PostgreSQL?</H4>
-
-    <P>PostgreSQL ÉÍÅÅÔ ÏÄÎÏÒÁÎÇÏ×ÕÀ ÉÎÆÒÁÓÔÒÕËÔÕÒÕ Ó ÔÏÇÏ ÓÁÍÏÇÏ ×ÒÅÍÅÎÉ
-    ËÁË ÍÙ ÎÁÞÁÌÉ ÒÁÚÒÁÂÏÔËÕ 6 ÌÅÔ ÎÁÚÁÄ. íÙ ÄÏÌÖÎÙ ÂÌÁÇÏÄÁÒÉÔØ ÚÁ
-    ÜÔÏ íÁÒËÁ æÏÎÁÑ (Marc Fournier), ËÏÔÏÒÙÊ ÓÏÚÄÁÌ ÜÔÕ ÉÎÆÒÁÓÔÒÕËÔÕÒÕ É
-    ÕÐÒÁ×ÌÑÅÔ ÅÊ ÎÁ ÐÒÏÔÑÖÅÎÉÉ ÜÔÉÈ ÌÅÔ.</P>
-
-    <P>ëÁÞÅÓÔ×ÅÎÎÁÑ ÉÎÆÒÁÓÔÒÕËÔÕÒÁ ÏÞÅÎØ ×ÁÖÎÁ ÄÌÑ ÐÒÏÅËÔÏ× Ó ÏÔËÒÙÔÙÍ
-    ÉÓÈÏÄÎÙÍ ËÏÄÏÍ. ïÎÁ ÐÒÅÄÏÔ×ÒÁÝÁÅÔ ÒÁÓËÏÌÙ, ËÏÔÏÒÙÅ ÍÏÇÕÔ ÓÉÌØÎÏ
-    ÚÁÄÅÒÖÁÔØ ÐÏÓÔÕÐÁÔÅÌØÎÏÅ Ä×ÉÖÅÎÉÅ ÐÒÏÅËÔÁ.</P>
-
-    <P>òÁÚÕÍÅÅÔÓÑ, ÜÔÁ ÉÎÆÒÁÓÔÒÕËÔÕÒÁ ÎÅ Ñ×ÌÑÅÔÓÑ ÄÅÛÅ×ÏÊ. óÕÝÅÓÔ×ÕÅÔ
-    ÎÅËÏÔÏÒÏÅ ËÏÌÉÞÅÓÔ×Ï ÅÖÅÍÅÓÑÞÎÙÈ É ÏÄÎÏÒÁÚÏ×ÙÈ ÒÁÓÈÏÄÏ×, ËÏÔÏÒÙÅ
-    ÔÒÅÂÕÀÔ ÄÅÎÅÇ. åÓÌÉ ×Ù ÉÌÉ ×ÁÛÁ ËÏÍÐÁÎÉÑ ÉÍÅÅÔ ÄÅÎØÇÉ, ËÏÔÏÒÙÅ
-    ÍÏÖÎÏ ÐÅÒÅÄÁÔØ × ÐÏÍÏÝØ ÎÁÛÉÍ ÕÓÉÌÉÑÍ, ÐÏÖÁÌÕÊÓÔÁ ÐÏÓÅÔÉÔÅ ÓÔÒÁÎÉÞËÕ
-    <A href=
-    "http://www.pgsql.com/pg_goodies">http://www.pgsql.com/pg_goodies</A>
-    É ÓÄÅÌÁÊÔÅ Ó×ÏÊ ×ËÌÁÄ.</P>
-
-    <P>èÏÔÑ ÎÁ ÓÔÒÁÎÉÞËÅ ÇÏ×ÏÒÉÔÓÑ Ï PostgreSQL, Inc, ÐÕÎËÔ
-    "contributions" ÐÒÅÄÎÁÚÎÁÞÅÎ ÉÓËÌÀÞÉÔÅÌØÎÏ ÄÌÑ ÐÏÄÄÅÒÖËÉ ÐÒÏÅËÔÁ
-    PostgreSQL É ÎÅ ÐÅÒÅÄÁÅÔÓÑ ËÁËÏÊ-ÌÉÂÏ ËÏÎËÒÅÔÎÏÊ ËÏÍÐÁÎÉÉ.
-    åÓÌÉ ÈÏÔÉÔÅ, ÔÏ ÍÏÖÅÔÅ ÜÔÏ ÐÒÏ×ÅÒÉÔØ, ÎÁÐÉÓÁ× ÐÉÓØÍÏ ÎÁ ËÏÎÔÁËÔÎÙÊ ÁÄÒÅÓ.</P>
-    <HR>
-
-    <H2 align="center">÷ÏÐÒÏÓÙ ÐÏÌØÚÏ×ÁÔÅÌÅÊ ÐÏ ËÌÉÅÎÔÓËÏÊ ÞÁÓÔÉ</H2>
-
-    <H4><A name="2.1">2.1</A>) óÕÝÅÓÔ×ÕÀÔ ÌÉ <SMALL>ODBC</SMALL> ÄÒÁÊ×ÅÒÁ
-    ÄÌÑ PostgreSQL?</H4>
-
-    <P>óÕÝÅÓÔ×ÕÅÔ Ä×Á <SMALL>ODBC</SMALL> ÄÒÁÊ×ÅÒÁ, PsqlODBC
-    É OpenLink <SMALL>ODBC</SMALL>.</P>
-
-    <P>PsqlODBC ×ËÌÀÞÁÅÔÓÑ × ÄÉÓÔÒÉÂÕÔÉ×. âÏÌØÛÅ ÉÎÆÏÒÍÁÃÉÉ Ï ÜÔÏÍ ÄÒÁÊ×ÅÒÅ
-    ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ <A href=
-    "ftp://ftp.PostgreSQL.org/pub/odbc/">ftp://ftp.PostgreSQL.org/pub/odbc/</A>.</P>
-
-    <P>OpenLink <SMALL>ODBC</SMALL> ÍÏÖÎÏ ×ÚÑÔØ ÎÁ <A href=
-    "http://www.openlinksw.com/">http://www.openlinksw.com</A>. üÔÏÔ
-    ÄÒÁÊ×ÅÒ ÒÁÂÏÔÁÅÔ Ó ÉÈ ÓÔÁÎÄÁÒÔÎÙÍ ËÌÉÅÎÔÓËÉÍ ÐÒÏÇÒÁÍÍÎÙÍ ÏÂÅÓÐÅÞÅÎÉÅÍ,
-    ÉÓÐÏÌØÚÕÀÝÉÍ <SMALL>ODBC</SMALL>, É ÔÁËÉÍ ÏÂÒÁÚÏÍ, <SMALL>ODBC</SMALL>
-    ÄÒÁÊ×ÅÒÙ ÄÌÑ PostgreSQL ÄÏÓÔÕÐÎÙ ÄÌÑ ËÁÖÄÏÊ ÉÚ ÐÏÄÄÅÒÖÉ×ÁÅÍÙÈ ÉÍÉ
-    ÐÌÁÔÆÏÒÍ (Win, Mac, Unix, VMS).</P>
-
-    <P>÷ÏÚÍÏÖÎÏ ÏÎÉ ÂÕÄÕÔ ÐÒÏÄÁ×ÁÔØ Ó×ÏÊ ÐÒÏÄÕËÔ ÔÅÍ ËÏÍÕ ÎÕÖÎÁ ËÏÍÍÅÒÞÅÓËÁÑ
-    ÐÏÄÄÅÒÖËÁ, ÎÏ ÂÅÓÐÌÁÔÎÁÑ ×ÅÒÓÉÑ ×ÓÅÇÄÁ ÂÕÄÅÔ ÄÏÓÔÕÐÎÁ. ðÏÖÁÌÕÊÓÔÁ,
-    ÎÁÐÒÁ×ÌÑÊÔÅ ×ÏÐÒÏÓÙ ÎÁ ÁÄÒÅÓ <A href=
-    "mailto:postgres95@openlink.co.uk">postgres95@openlink.co.uk</A>.</P>
-
-    <P>ôÁËÖÅ ÐÏÓÍÏÔÒÉÔÅ <A href=
-    "http://www.postgresql.org/devel-corner/docs/programmer/odbc.html">ODBC
-    ÒÁÚÄÅÌ × ÒÕËÏ×ÏÄÓÔ×Å ÐÒÏÇÒÁÍÍÉÓÔÁ</A>.</P>
-
-    <H4><A name="2.2">2.2</A>) ëÁËÉÅ ÉÎÓÔÒÕÍÅÎÔÙ ÓÕÝÅÓÔ×ÕÀÔ ÄÌÑ ÉÓÐÏÌØÚÏ×ÁÎÉÑ
-    PostgreSQL ÞÅÒÅÚ Web?</H4>
-
-    <P>ðÒÅËÒÁÓÎÏÅ ××ÅÄÅÎÉÅ ×Ï ×ÚÁÉÍÏÄÅÊÓÔ×ÉÅ ÂÁÚ ÄÁÎÎÙÈ É Web ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ:
-    <A href="http://www.webreview.com">http://www.webreview.com</A></P>
-
-    <P>ôÁËÖÅ ÚÁÇÌÑÎÉÔÅ ÎÁ <A href=
-    "http://www.phone.net/home/mwm/hotlist/">http://www.phone.net/home/mwm/hotlist/.</A></P>
-
-    <P>äÌÑ ÉÎÔÅÇÒÁÃÉÉ Ó Web, ÏÄÎÉÍ ÉÚ ÐÒÅ×ÏÓÈÏÄÎÙÈ ÉÎÓÔÒÕÍÅÎÔÏ× Ñ×ÌÑÅÔÓÑ PHP.
-    äÏÍÁÛÎÑÑ ÓÔÁÎÉÞËÁ <A
-    href="http://www.php.net">http://www.php.net</A>.</P>
-
-    <P>äÌÑ ËÏÍÐÌÅËÓÎÙÈ ÒÅÛÅÎÉÊ, ÍÎÏÇÉÅ ÐÏÌØÚÕÀÔÓÑ Perl ÉÎÔÅÒÆÅÊÓÏÍ É CGI.pm.</P>
-
-    <H4><A name="2.3">2.3</A>) åÓÔØ ÌÉ Õ PostgreSQL ÇÒÁÆÉÞÅÓËÉÊ ÉÎÔÅÒÆÅÊÓ
-    ÐÏÌØÚÏ×ÁÔÅÌÑ? çÅÎÅÒÁÔÏÒ ÏÔÞÅÔÏ×? ÷ÓÔÒÏÅÎÎÙÊ ÉÎÔÅÒÆÅÊÓ ÄÌÑ ÑÚÙËÁ
-    ÚÁÐÒÏÓÏ×?</H4>
-
-    <P>õ ÎÁÓ ÅÓÔØ ÐÒÅËÒÁÓÎÙÊ ÇÏÒÁÆÉÞÅÓËÉÊ ÉÎÔÅÒÆÅÊÓ, ÎÁÚÙ×ÁÅÍÙÊ
-    <I>pgaccess</I>, ËÏÔÏÒÙÊ Ñ×ÌÑÅÔÓÑ ÞÁÓÔØÀ ÄÉÓÔÒÉÂÕÔÉ×Á. <I>pgaccess</I>
-    ÔÁËÖÅ ÅÍÅÅÔ ÇÅÎÅÒÁÔÏÒ ÏÔÞÅÔÏ×. åÇÏ ÓÔÒÁÎÉÞËÁ <A href=
-    "http://www.flex.ro/pgaccess">http://www.flex.ro/pgaccess</A></P>
-
-    <P>íÙ ÔÁËÖÅ ×ËÌÀÞÁÅÍ <I>ecpg</I>, ËÏÔÏÒÙÊ ÐÒÅÄÏÓÔÁ×ÌÑÅÔ ×ÓÔÒÏÅÎÎÙÊ
-    ÉÎÔÅÒÆÅÊÓ Ë ÑÚÙËÕ ÚÁÐÒÏÓÏ× SQL ÉÚ C.</P>
-
-    <H4><A name="2.4">2.4</A>) ëÁËÉÅ ÑÚÙËÉ ÍÏÇÕÔ ×ÚÁÉÍÏÄÅÊÓÔ×Ï×ÁÔØ Ó
-    PostgreSQL?</H4>
-
-    <P>÷ÏÔ ÜÔÉ:</P>
-
-    <UL>
-      <LI>C (libpq)</LI>
-
-      <LI>C++ (libpq++)</LI>
-
-      <LI>Embedded C (ecpg)</LI>
-
-      <LI>Java (jdbc)</LI>
-
-      <LI>Perl (perl5)</LI>
-
-      <LI>ODBC (odbc)</LI>
-
-      <LI>Python (PyGreSQL)</LI>
-
-      <LI>TCL (libpgtcl)</LI>
-
-      <LI>C Easy API (libpgeasy)</LI>
-
-      <LI>Embedded <SMALL>HTML</SMALL> (<A href=
-      "http://www.php.net">PHP from http://www.php.net</A>)</LI>
-    </UL>
-    <HR>
-
-    <H2 align="center">÷ÏÐÒÏÓÙ ÁÄÍÉÎÉÓÔÒÉÒÏ×ÁÎÉÑ</H2>
-
-    <H4><A name="3.1">3.1</A>) ëÁË ÍÎÅ ÕÓÔÁÎÏ×ÉÔØ PostgreSQL × ÍÅÓÔÏ ÏÔÌÉÞÎÏÅ
-    ÏÔ <I>/usr/local/pgsql</I>?</H4>
-
-    <P>úÁÄÁÊÔÅ ÏÐÃÉÀ <I>--prefix</I> ËÏÇÄÁ ÚÁÐÕÓËÁÅÔÅ <I>configure</I>.</P>
-
-    <H4><A name="3.2">3.2</A>) ëÏÇÄÁ Ñ ÚÁÐÕÓËÁÀ <I>postmaster</I>, Ñ ÐÏÌÕÞÁÀ
-     ÓÏÏÂÝÅÎÉÅ <I>Bad System Call</I> ÉÌÉ ÓÏÏÂÝÅÎÉÅ core dumped. ðÏÞÅÍÕ?</H4>
-
-    <P>üÔÏ ÍÏÖÅÔ ÂÙÔØ ×ÙÚ×ÁÎÏ ÒÁÚÎÙÍÉ ÐÒÏÂÌÅÍÁÍÉ, ÎÏ ÐÅÒ×ÏÅ, ÞÔÏ
-    ÎÕÖÎÏ ÓÄÅÌÁÔØ - ÜÔÏ ÕÂÅÄÉÔØÓÑ × ÔÏÍ, ÞÔÏ × ×ÁÛÅÍ ÑÄÒÅ ÕÓÔÁÎÏ×ÌÅÎÏ
-    ÒÁÓÛÉÒÅÎÉÅ System V. PostgreSQL ÔÒÅÂÕÅÔ, ÞÔÏÂÙ ÑÄÒÏ ÐÏÄÄÅÒÖÉ×ÁÌÏ
-    ÒÁÚÄÅÌÑÅÍÕÀ ÐÁÍÑÔØ É ÓÅÍÁÆÏÒÙ.</P>
-
-    <H4><A name="3.3">3.3</A>) ëÏÇÄÁ Ñ ÐÙÔÁÀÓØ ÚÁÐÕÓÔÉÔØ <I>postmaster</I>, Ñ
-    ÐÏÌÕÞÁÀ ÏÛÉÂËÉ <I>IpcMemoryCreate</I>. ðÏÞÅÍÕ?</H4>
-
-    <P>ìÉÂÏ Õ ×ÁÓ × ÑÄÒÅ ÎÅÐÒÁ×ÉÌØÎÙÅ ÎÁÓÔÒÏÊËÉ ÒÁÚÄÅÌÑÅÍÏÊ ÐÁÍÑÔÉ, ÌÉÂÏ
-    ×ÁÛÅÍÕ ÑÄÒÕ ÎÕÖÎÏ ÂÏÌØÛÅÅ ËÏÌÉÞÅÓÔ×Ï ÄÏÓÔÕÐÎÏÊ ÒÁÚÄÅÌÑÅÍÏÊ ÐÁÍÑÔÉ.
-    ôÅ ËÏÎËÒÅÔÎÙÅ ÄÅÊÓÔ×ÉÑ, ËÏÔÏÒÙÅ ×ÁÍ ÎÕÖÎÏ ÐÒÏÉÚ×ÅÓÔÉ ÚÁ×ÉÓÑÔ ÏÔ
-    ÁÒÈÉÔÅËÔÕÒÙ ×ÁÛÅÊ ÍÁÛÉÎÙ É ÏÔ ÔÏÇÏ ËÁË ÍÎÏÇÏ ÂÕÆÅÒÏ× É backend
-    ÐÒÏÃÅÓÓÏ× ×Ù ÎÁÓÔÒÏÉÌÉ ÄÌÑ <I>postmaster</I>. äÌÑ ÂÏÌØÛÉÎÓÔ×Á ÓÉÓÔÅÍ,
-    Ó ËÏÌÉÞÅÓÔ×ÏÍ ÂÕÆÅÒÏ× É ÐÒÏÃÅÓÓÏ× ÐÏ ÕÍÏÌÞÁÎÉÀ, ÎÅÏÂÈÏÄÉÍÙÊ ÍÉÎÉÍÕÍ -
-    ÜÔÏ ÏËÏÌÏ 1 ÍÅÇÁÂÁÊÔÁ. ðÏÄÒÏÂÎÏÓÔÉ Ï ÒÁÚÄÅÌÑÅÍÏÊ ÐÁÍÑÔÉ É ÓÅÍÁÆÏÒÁÈ
-    ÓÍÏÔÒÉÔÅ × <A href=
-    "http://www.postgresql.org/idocs/index.php?kernel-resources.html">òÕËÏ×ÏÄÓÔ×Å
-    ÁÄÍÉÎÉÓÔÒÁÔÏÒÁ PostgreSQL</A>.</P>
-
-    <H4><A name="3.4">3.4</A>) ëÏÇÄÁ Ñ ÐÙÔÁÀÓØ ÚÁÐÕÓÔÉÔØ <I>postmaster</I>, Ñ
-    ÐÏÌÕÞÁÀ ÏÛÉÂËÉ <I>IpcSemaphoreCreate</I>. ðÏÞÅÍÕ?</H4>
-
-    <P>åÓÌÉ ÜÔÏ ÓÏÏÂÝÅÎÉÅ <I>IpcSemaphoreCreate: semget failed (No
-    space left on device)</I> ÔÏ ÎÁÓÔÒÏÊËÉ ×ÁÛÅÇÏ ÑÄÒÁ ÔÁËÏ×Ù, ÞÔÏ ÅÍÕ ÎÅ
-    È×ÁÔÁÅÔ ÓÅÍÁÆÏÒÏ×. Postgres ÔÒÅÂÕÅÔ ÏÄÉÎ ÓÅÍÁÆÏÒ ÎÁ ÐÏÔÅÎÃÉÁÌØÎÙÊ
-    backend ÐÒÏÃÅÓÓ. ÷ÒÅÍÅÎÎÙÍ ÒÅÛÅÎÉÅÍ Ñ×ÌÑÅÔÓÑ ÚÁÐÕÓË <I>postmaster</I>
-    Ó ÎÁÓÔÒÏÊËÁÍÉ ÎÁ ÍÅÛØÛÅÅ ËÏÌÉÞÅÓÔ×Ï backend ÐÒÏÃÅÓÓÏ×. éÓÐÏÌØÚÕÊÔÅ
-    <I>-N</I> Ó ÚÎÁÞÅÎÉÅÍ ÍÅÎØÛÉÍ ÞÅÍ 32, ËÏÔÏÒÏÅ ÐÒÉÎÑÔÏ ÐÏ ÕÍÏÌÞÁÎÉÀ.
-    âÏÌÅÅ ÐÒÁ×ÉÌØÎÏÅ ÒÅÛÅÎÉÅ - ÜÔÏ Õ×ÅÌÉÞÉÔØ ÚÎÁÞÅÎÉÑ <SMALL>SEMMNS</SMALL>
-    É <SMALL>SEMMNI</SMALL> × ÎÁÓÔÒÊËÁÈ ÑÄÒÁ.</P>
-
-    <P>îÅÉÓÐÒÁ×ÎÙÅ ÓÅÍÁÆÏÒÙ ÔÁËÖÅ ÍÏÇÕÔ ÐÒÉ×ÅÓÔÉ Ë ÐÁÄÅÎÉÀ óõâä ×Ï ×ÒÅÍÑ
-    ÄÏÓÔÕÐÁ Ë ÂÁÚÅ ÄÁÎÎÙÈ.</P>
-
-    <P>åÓÌÉ ×Ù ÐÏÌÕÞÉÌÉ ËÁËÏÅ-ÌÉÂÏ ÄÒÕÇÏÅ ÓÏÏÂÝÅÎÉÅ Ï ÏÛÉÂËÅ, ÔÏ ×ÐÏÌÎÅ
-    ×ÏÚÍÏÖÎÏ, ÞÔÏ × ×ÁÛÅÍ ÑÄÒÅ ×ÏÏÂÝÅ ÎÅ ÎÁÓÔÒÏÅÎÁ ÐÏÄÄÅÒÖËÁ ÓÅÍÁÆÏÒÏ×.
-    óÍÏÔÒÉÔÅ ÐÏÄÒÏÂÎÏÓÔÉ Ï ÒÁÚÄÅÌÑÅÍÏÊ ÐÁÍÑÔÉ É ÓÅÍÁÆÏÒÁÈ × òÕËÏ×ÏÄÓÔ×Å
-    áÄÍÉÎÉÓÔÒÁÔÏÒÁ PostgreSQL.</P>
-
-    <H4><A name="3.5">3.5</A>) ëÁË ÍÎÅ ÕÐÒÁ×ÌÑÔØ ÓÏÅÄÉÎÅÎÉÑÍÉ Ó ÄÒÕÇÉÈ
-    ËÏÍÐØÀÔÅÒÏ×?</H4>
-
-    <P>ðÏ ÕÍÏÌÞÁÎÉÀ, PostgreSQL ÒÁÚÒÅÛÁÅÔ ÔÏÌØËÏ ÓÏÅÄÉÎÅÎÉÑ ÎÁ ÌÏËÁÌØÎÏÊ
-    ÍÁÛÉÎÅ ÞÅÒÅÚ ÓÏËÅÔÙ ÄÏÍÅÎÁ Unix. äÒÕÇÉÅ ÍÁÛÉÎÙ ÎÅ ÓÍÏÇÕÔ ÐÏÄËÌÀÞÉÔØÓÑ Ë
-    ÂÁÚÅ ÐÏËÁ ÄÌÑ <I>postmaster</I> ÎÅ ÂÕÄÅÔ ÚÁÄÁÎ ÆÌÁÇ <I>-i</I>
-    <B>É</B> ÐÏËÁ ÎÅ ÂÕÄÅÔ ÒÁÚÒÅÛÅÎÁ host-Á×ÔÏÒÉÚÁÃÉÑ × ÆÁÊÌÅ
-    <I>$PGDATA/pg_hba.conf</I>. üÔÉ ÄÅÊÓÔ×ÉÑ ÄÅÌÁÀÔ ×ÏÚÍÏÖÎÙÍÉ TCP/IP
-    ÓÏÅÄÉÎÅÎÉÑ.</P>
-
-    <H4><A name="3.6">3.6</A>) ëÁËÉÅ ÎÁÓÔÒÏÊËÉ ÍÎÅ ÎÕÖÎÏ ÓÄÅÌÁÔØ ÄÌÑ ÕÌÕÞÛÅÎÉÑ
-     ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ?</H4>
-
-    <P>îÅÓÏÍÎÅÎÎÏ, ÉÎÄÅËÓÙ ÍÏÇÕÔ Õ×ÅÌÉÞÉÔØ ÓËÏÒÏÓÔØ ×ÙÐÏÌÎÅÎÉÑ ÚÁÐÒÏÓÏ×. ëÏÍÁÎÄÁ
-    <SMALL>EXPLAIN</SMALL> ÐÏÚ×ÏÌÑÅÔ ×ÁÍ ÐÏÓÍÏÔÒÅÔØ ËÁË PostgreSQL
-    ÉÎÔÅÒÐÒÅÔÉÒÕÅÔ ×ÁÛ ÚÁÐÒÏÓ É ËÁËÉÅ ÉÎÄÅËÓÙ ÉÓÐÏÌØÚÕÀÔÓÑ.</P>
-
-    <P>åÓÌÉ ×Ù ×ÙÐÏÌÎÑÅÔÅ ÍÎÏÇÏ ÏÐÅÒÁÔÏÒÏ× <SMALL>INSERT</SMALL>,
-    ÒÁÓÓÍÏÔÒÉÔÅ ×ÏÚÍÏÖÎÏÓÔØ ×ÙÐÏÌÎÑÔØ ÉÈ × ÂÏÌØÛÏÊ ÐÁÞËÅ, ÉÓÐÏÌØÚÕÑ
-    ËÏÍÁÎÄÕ <SMALL>COPY</SMALL>. üÔÏ ÚÎÁÞÉÔÅÌØÎÏ ÂÙÓÔÒÅÅ, ÞÅÍ ÏÔÄÅÌØÎÙÅ
-    <SMALL>INSERT.</SMALL> ÷Ï-×ÔÏÒÙÈ, ÏÐÅÒÁÔÏÒÙ ×ÎÅ ÂÌÏËÁ ÔÒÁÎÚÁËÃÉÉ
-    <SMALL>BEGIN WORK/COMMIT</SMALL> ÓÁÍÉ ×ÙÐÏÌÎÑÀÔ ÔÒÁÎÚÁËÃÉÀ. ðÏÄÕÍÁÊÔÅ
-    ÎÁÄ ×ÙÐÏÌÎÅÎÉÅÍ ÎÅÓËÏÌØËÉÈ ÏÐÅÒÁÔÏÒÏ× × ÏÄÎÏÍ ÂÌÏËÅ ÔÒÁÎÚÁËÃÉÉ.
-    üÔÏ ÕÍÅÎØÛÉÔ ËÏÌÉÞÅÓÔ×Ï ÔÒÁÎÚÁËÃÉÊ. ôÁËÖÅ, ÚÁÄÕÍÁÊÔÅÓØ ÎÁÄ ÕÄÁÌÅÎÉÅÍ
-    É ÐÅÒÅÓÏÚÄÁÎÉÅÍ ÉÎÄÅËÓÏ×, ËÏÇÄÁ ×Ù ×ÙÐÏÌÎÑÅÔÅ ÂÏÌØÛÉÅ ÉÚÍÅÎÅÎÉÑ
-    ÄÁÎÎÙÈ.</P>
-
-    <P>óÕÝÅÓÔ×ÕÅÔ ÎÅÓËÏÌØËÏ ÏÐÃÉÊ ÎÁÓÔÒÏÊËÉ. ÷Ù ÍÏÖÅÔÅ ÚÁÐÒÅÔÉÔØ
-    <I>fsync()</I> ÐÒÉ ÓÔÁÒÔÅ <I>postmaster</I> Ó ÏÐÃÉÅÊ <I>-o -F</I>.
-    üÔÏ ÐÒÅÄÏÔ×ÒÁÔÉÔ ×ÙÚÏ×Ù <I>fsync()</I>, ËÏÔÏÒÙÅ ÐÒÉ×ÏÄÑÔ Ë ÓÂÒÏÓÕ
-    ÄÁÎÎÙÈ ÎÁ ÄÉÓË ÐÏÓÌÅ ËÁÖÄÏÊ ÔÒÁÎÚÁËÃÉÉ.</P>
-
-    <P>÷Ù ÍÏÖÅÔÅ ÔÁËÖÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÄÌÑ <I>postmaster</I> ÏÐÃÉÀ <I>-B</I>
-    ÄÌÑ Õ×ÅÌÉÞÅÎÉÑ ËÏÌÉÞÅÓÔ×Á ÂÕÆÅÒÏ× ÒÁÚÄÅÌÑÅÍÏÊ ÐÁÍÑÔÉ, ËÏÔÏÒÁÑ
-    ÉÓÐÏÌØÚÕÅÔÓÑ backend ÐÒÏÃÅÓÓÁÍÉ. åÓÌÉ ×Ù ÓÄÅÌÁÅÔÅ ÚÎÁÞÅÎÉÅ ÜÔÏÇÏ ÐÁÒÁÍÅÔÒÁ
-    ÓÌÉÛËÏÍ ÂÏÌØÛÉÍ, ÔÏ <I>postmaster</I> ÍÏÖÅÔ ÎÅ ÚÁÐÕÓÔÉÔÓÑ ÐÏÔÏÍÕ ÞÔÏ
-    ×Ù ÉÓÞÅÒÐÁÅÔÅ ÏÇÒÁÎÉÞÅÎÉÅ ÑÄÒÁ ÎÁ ÏÂßÅÍ ÒÁÚÄÅÌÑÅÍÏÊ ÐÁÍÑÔÉ. ëÁÖÄÙÊ
-    ÂÕÆÅÒ ÉÍÅÅÔ ÒÁÚÍÅÒ × 8 ËÉÌÏÂÁÊÔ É ÐÏ ÕÍÏÌÞÁÎÉÀ ×ÙÄÅÌÑÅÔÓÑ 64 ÂÕÆÅÒÁ.</P>
-
-    <P>÷Ù ÍÏÖÅÔÅ ÔÁËÖÅ ÉÓÐÏÌØÚÏ×ÁÔØ backend ÏÐÃÉÀ <I>-S</I> ÄÌÑ Õ×ÅÌÉÞÅÎÉÑ
-    ÍÁËÓÉÍÁÌØÎÏÇÏ ËÏÌÉÞÅÓÔ×Á ÐÁÍÑÔÉ, ËÏÔÏÒÏÅ ÉÓÐÏÌØÚÕÅÔÓÑ backend ÐÒÏÃÅÓÓÏÍ
-    ÄÌÑ ×ÒÅÍÅÎÎÙÈ ÓÏÒÔÉÒÏ×ÏË. úÎÁÞÅÎÉÅ ÄÌÑ ÏÐÃÉÉ <I>-S</I> ÚÁÄÁÅÔÓÑ ×
-    ËÉÌÏÂÁÊÔÁÈ É ÐÏ ÕÍÏÌÞÁÎÉÀ ÒÁ×ÎÏ 512 (Ô.Å. 512K).</P>
-
-    <P>÷Ù ÔÁËÖÅ ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ËÏÍÁÎÄÕ <SMALL>CLUSTER</SMALL> ÄÌÑ
-    ÇÒÕÐÐÉÒÏ×ËÉ ÄÁÎÎÙÈ × ÔÁÂÌÉÃÁÈ ÎÁ ÓÏ×ÐÁÄÁÀÝÉÊ ÉÎÄÅËÓ. ðÏÄÒÏÂÎÏÓÔÉ ÓÍÏÔÒÉÔÅ
-    ÎÁ ÓÔÒÁÎÉÃÅ ÒÕËÏ×ÏÄÓÔ×Á ÐÏ ËÏÍÁÎÄÅ <SMALL>CLUSTER</SMALL>.</P>
-
-    <H4><A name="3.7">3.7</A>) ëÁËÉÅ ×ÏÚÍÏÖÎÏÓÔÉ ÄÌÑ ÏÔÌÁÄËÉ ÅÓÔØ ×
-    ÎÁÌÉÞÉÉ?</H4>
-
-    <P>PostgreSQL ÉÍÅÅÔ ÎÅÓËÏÌØËÏ ×ÏÚÍÏÖÎÏÓÔÅÊ, ÐÏÚ×ÏÌÑÀÝÉÅ ÐÏÌÕÞÉÔØ
-    ÉÎÆÏÒÍÁÃÉÀ Ï ÓÏÓÔÏÑÎÉÉ, ËÏÔÏÒÁÑ ÍÏÖÅÔ ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÁ × ÏÔÌÁÄÏÞÎÙÈ
-    ÃÅÌÑÈ.</P>
-
-    <P>÷Ï-ÐÅÒ×ÙÈ, ÐÒÉ ÚÁÐÕÓËÅ <I>configure</I> Ó ÏÐÃÉÅÊ --enable-cassert,
-    ÍÎÏÇÉÅ ×ÙÚÏ×Ù <I>assert()</I> ÐÏÚ×ÏÌÑÀÔ ÏÔÓÌÅÖÉ×ÁÔØ ÒÁÂÏÔÕ backend
-    ÐÒÏÃÅÓÓÁ É ÏÓÔÁÎÏ×ËÕ ÐÒÏÇÒÁÍÍÙ ÐÒÉ ×ÏÚÎÉËÎÏ×ÅÎÉÉ ËÁËÉÈ-ÌÉÂÏ
-    ÎÅÏÖÉÄÁÎÎÏÓÔÅÊ.</P>
-
-    <P>é <I>postmaster</I>, É <I>postgres</I> ÉÍÅÀÔ ÎÅÓËÏÌØËÏ ÏÔÌÁÄÏÞÎÙÈ
-    ÏÐÃÉÊ. ÷Ï-ÐÅÒ×ÙÈ, ÐÒÉ ÚÁÐÕÓËÅ <I>postmaster</I>, ÕÂÅÄÉÔÅÓØ, ÞÔÏ
-    ÓÔÁÎÄÁÒÔÎÙÊ ×Ù×ÏÄ É ×Ù×ÏÄ ÏÛÉÂÏË ÏÓÕÝÅÓÔ×ÌÑÀÔÓÑ × ÆÁÊÌ ÖÕÒÎÁÌÁ:</P>
-<PRE>
-    cd /usr/local/pgsql
-    ./bin/postmaster &gt;server.log 2&gt;&amp;1 &amp;
-</PRE>
-
-    <P>üÔÏ ÐÒÉ×ÅÄÅÔ Ë ÐÏÑ×ÌÅÎÉÀ ÆÁÊÌÁ server.log × ÇÌÁ×ÎÏÍ ËÁÔÁÌÏÇÅ
-    PostgreSQL. üÔÏÔ ÆÁÊÌ ÓÏÄÅÒÖÉÔ ÐÏÌÅÚÎÕÀ ÉÎÆÏÒÍÁÃÉÀ Ï ÐÒÏÂÌÅÍÁÈ ÉÌÉ
-    ÏÛÉÂËÁÈ, ×ÏÚÎÉËÛÉÈ ÎÁ ÓÅÒ×ÅÒÅ. <I>Postmaster</I> ÉÍÅÅÔ ÏÐÃÉÀ <I>-d</I>,
-    ËÏÔÏÒÁÑ ÐÏÚ×ÏÌÑÅÔ ÐÏÌÕÞÁÔØ ÐÒÉ ÐÒÏÔÏËÏÌÉÒÏ×ÁÎÉÉ ÂÏÌÅÅ ÄÅÔÁÌØÎÕÀ
-    ÉÎÆÒÍÁÃÉÀ. äÌÑ ÏÐÃÉÉ <I>-d</I> ÕËÁÚÙ×ÁÅÔÓÑ ÞÉÓÌÏ, ËÏÔÏÒÏÅ ÚÁÄÁÅÔ ÕÒÏ×ÅÎØ
-    ÏÔÌÁÄËÉ. âÕÄØÔÅ ÏÓÔÏÒÏÖÎÙ, ÔÁË ËÁË ×ÙÓÏËÉÊ ÕÒÏ×ÅÎØ ÏÔÌÁÄËÉ ÐÒÉ×ÏÄÉÔ
-    Ë ÇÅÎÅÒÁÃÉÉ ÆÁÊÌÏ× ÖÕÒÎÁÌÁ ÂÏÌØÛÏÇÏ ÒÁÚÍÅÒÁ.</P>
-
-    <P>åÓÌÉ <I>postmaster</I> ÎÅ ÚÁÐÕÝÅÎ, ×Ù ÍÏÖÅÔÅ ÚÁÐÕÓÔÉÔØ
-    <I>postgres</I> backend ÉÚ ËÏÍÁÎÄÎÏÊ ÓÔÒÏËÉ É ××ÅÓÔÉ ×ÁÛ ÏÐÅÒÁÔÏÒ
-    <SMALL>SQL</SMALL> ÎÁÐÒÑÍÕÀ. üÔÏ ÒÅËÏÍÅÎÄÕÅÔÓÑ <B>ÔÏÌØËÏ</B> ÄÌÑ
-    ÃÅÌÅÊ ÏÔÌÁÄËÉ. úÁÍÅÔÉÍ, ÞÔÏ × ÜÔÏÍ ÒÅÖÉÍÅ, ÚÁÐÒÏÓ ÚÁ×ÅÒÛÁÅÔÓÑ ÓÉÍ×ÏÌÏÍ
-    ÎÏ×ÏÊ ÓÔÒÏËÉ, Á ÎÅ ÔÏÞËÏÊ Ó ÚÁÐÑÔÏÊ. åÓÌÉ ×Ù ÐÒÏÉÚ×ÏÄÉÌÉ ËÏÍÐÉÌÑÃÉÀ
-    Ó ÏÔÌÁÄÏÞÎÙÍÉ ÓÉÍ×ÏÌÏÁÍÉ, ×Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÌÀÂÏÊ ÏÔÌÁÄÞÉË, ÞÔÏÂÙ
-    ÐÏÓÍÏÔÒÅÔØ, ÞÔÏ ÓÌÕÞÉÌÏÓØ. ðÏÓËÏÌØËÕ backend ÚÁÐÕÓËÁÅÔÓÑ ÎÅ ÉÚ
-    <I>postmaster</I>, ÏÎ ÎÅ ÚÁÐÕÓËÁÅÔÓÑ × ÉÄÅÎÔÉÞÎÏÍ ÏËÒÕÖÅÎÉÉ É ÚÎÁÞÉÔ
-    ÐÒÏÂÌÅÍÙ ÉÔÅÒÁÃÉÊ ÂÌÏËÉÒÏ×ÏË/backend ÎÅ ÍÏÇÕÔ ÂÙÔØ ×ÏÓÐÒÏÉÚ×ÅÄÅÎÙ.</P>
-
-    <P>åÓÌÉ <I>postmaster</I> ÚÁÐÕÝÅÎ, ÚÁÐÕÓÔÉÔÅ <I>psql</I> × ÏÄÎÏÍ
-    ÏËÎÅ, ÚÁÔÅÍ ÎÁÊÄÉÔÅ <SMALL>PID</SMALL> ÐÒÏÃÅÓÓÁ <I>postgres</I>,
-    ÉÓÐÏÌØÚÕÅÍÙÊ <I>psql</I>. éÓÐÏÌØÚÕÊÔÅ ÏÔÄÁÄÞÉË ÄÌÑ ÐÏÄËÌÀÞÅÎÉÑ Ë
-    <I>postgres</I> <SMALL>PID.</SMALL> ÷Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ ÔÏÞËÉ
-    ÐÒÅÒÙ×ÁÎÉÑ × ÏÔÌÁÄÞÉËÅ É ÚÁÐÕÓÔÉÔØ ÚÁÐÒÏÓ ÉÚ <I>psql</I>. åÓÌÉ
-    ×Ù ÐÒÏÉÚ×ÏÄÉÔÅ ÏÔÌÁÄËÕ ÚÁÐÕÓËÁ <I>postgres</I>, ×Ù ÍÏÖÅÔÅ ÕÓÔÁÎÏ×ÉÔØ
-    PGOPTIONS="-W n", É ÚÁÔÅÍ ÚÁÐÕÓÔÉÔØ <I>psql</I>. üÔÁ ÏÐÃÉÑ ÐÒÉ×ÏÄÉÔ
-    Ë ÚÁÄÅÒÖËÅ ÐÒÏÃÅÓÓÁ ÚÁÐÕÓËÁ ÎÁ <I>n</I> ÓÅËÕÎÄ, × ÔÅÞÅÎÉÅ ËÏÔÏÒÙÈ
-    ×Ù ÍÏÖÅÔÅ ÐÏÄËÌÀÞÉÔØ Ë ÐÒÏÃÅÓÓÕ ÏÔÌÁÄÞÉË, ÕÓÔÁÎÏ×ÉÔØ ÌÀÂÙÅ ÔÏÞËÉ
-    ÐÒÅÒÙ×ÁÎÉÑ É ÐÒÏÄÏÌÖÉÔØ ÚÁÐÕÓË.</P>
-
-    <P>ðÒÏÇÒÁÍÍÁ <I>postgres</I> ÉÍÅÅÔ ÏÐÃÉÉ <I>-s, -A</I>, É <I>-t</I>
-    ËÏÔÏÒÙÅ ÍÏÇÕÔ ÂÙÔØ ÏÞÅÎØ ÐÏÌÅÚÎÙÍÉ ÄÌÑ ÏÔÌÁÄËÉ É ÉÚÍÅÒÅÎÉÑ
-    ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ.</P>
-
-    <P>÷Ù ÔÁËÖÅ ÍÏÖÅÔÅ ÓËÏÍÐÉÌÉÒÏ×ÁÔØ PostgreSQL Ó ÐÒÏÆÉÌÉÒÏ×ÁÎÉÅÍ ÄÌÑ
-    ÔÏÇÏ, ÞÔÏÂÙ Õ×ÉÄÅÔØ ËÁËÉÅ ÆÕÎËÃÉÉ ÓËÏÌØËÏ ×ÒÅÍÅÎÉ ×ÙÐÏÌÎÑÀÔÓÑ.
-    æÁÊÌÙ ÐÒÏÆÉÌÉÒÏ×ÁÎÉÑ backend'Á ÎÁÈÏÄÑÔÓÑ × ËÁÔÁÌÏÇÅ
-    <I>pgsql/data/base/dbname</I>. æÁÊÌ ÐÒÏÆÉÌÉÒÏ×ÁÎÉÑ ËÌÉÅÎÔÁ
-    ÂÕÄÅÔ ÐÏÍÅÝÅÎ × ÔÅËÕÝÉÊ ËÁÔÁÌÏÇ ËÌÉÅÎÔÁ. ÷ Linux ÄÌÑ ×ÙÐÏÌÎÅÎÉÑ
-    ÐÒÏÆÉÌÉÒÏ×ÁÎÉÑ ÔÒÅÂÕÅÔÓÑ ËÏÍÐÉÌÑÃÉÉ Ó <I>-DLINUX_PROFILE</I>.</P>
-
-    <H4><A name="3.8">3.8</A>) ðÏÞÅÍÕ Ñ ÐÏÌÕÞÁÀ ÓÏÏÂÝÅÎÉÅ <I>"Sorry, too
-    many clients"</I> ËÏÇÄÁ ÐÙÔÁÀÓØ ÐÏÄËÌÀÞÉÔØÓÑ Ë ÂÁÚÅ?</H4>
-
-    <P>÷ÁÍ ÎÕÖÎÏ Õ×ÅÌÉÞÉÔØ ÏÇÒÁÎÉÞÅÎÉÅ ÎÁ ËÏÌÉÞÅÓÔ×Ï ËÏÎËÕÒÅÔÎÙÈ
-    backend ÐÒÏÃÅÓÓÏ× ÐÒÉ ÚÁÐÕÓËÅ <I>postmaster</I>.</P>
-
-    <P>ðÏ ÕÍÏÌÞÁÎÉÀ ÕÓÔÁÎÏ×ÌÅÎ ÌÉÍÉÔ ÎÁ 32 ÐÒÏÃÅÓÓÁ. ÷Ù ÍÏÖÅÔÅ
-    Õ×ÅÌÉÞÉÔØ ÜÔÏÔ ÌÉÍÉÔ ÐÅÒÅÚÁÐÕÓÔÉ× <I>postmaster</I> Ó ÎÕÖÎÙÍ
-    ÚÎÁÞÅÎÉÅÍ ÐÒÏÃÅÓÓÏ×, ËÏÔÏÒÏÅ ÕËÁÚÙ×ÁÅÔÓÑ × ÏÐÃÉÉ  <I>-N</I> ÉÌÉ
-    ÉÚÍÅÎÉ× ÆÁÊÌ <I>postgresql.conf</I>.</P>
-
-    <P>úÁÍÅÔÉÍ, ÞÔÏ ÅÓÌÉ ×Ù ÚÁÄÁÄÉÔÅ × ÏÐÃÉÉ <I>-N</I> ÚÎÁÞÅÎÉÅ ÂÏÌØÛÅ
-    32, ÔÏ ×Ù ÔÁËÖÅ ÄÏÌÖÎÙ Õ×ÅÌÉÞÉÔØ ÚÎÁÞÅÎÉÅ × ÏÐÃÉÉ <I>-B</I> ËÏÔÏÒÏÅ
-    ÐÏ ÕÍÏÌÞÁÎÉÀ ÕÓÔÁÎÏ×ÌÅÎÏ × 64; úÎÁÞÅÎÉÅ ÏÐÃÉÉ <I>-B</I> ÄÏÌÖÎÏ ÂÙÔØ
-    ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ ×Ä×ÏÅ ÂÏÌØÛÅ ÚÎÁÞÅÎÉÑ ÏÐÃÉÉ <I>-N</I>, É ×ÏÚÍÏÖÎÏ
-    ÅÝ£ ÂÏÌØÛÅ ÄÌÑ ÌÕÞÛÅÊ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔÉ. äÌÑ ÂÏÌØÛÅÇÏ ËÏÌÉÞÅÓÔ×Á
-    backend ÐÒÏÃÅÓÓÏ×, ×ÁÍ ÔÁËÖÅ ÎÅÐÌÏÈÏ ÂÙÌÏ ÂÙ Õ×ÅÌÉÞÉÔØ ÎÅËÏÔÏÒÙÅ
-    ÐÁÒÁÍÅÔÒÙ ÑÄÒÁ Unix. üÔÏ ÔÁËÉÅ ÐÁÒÁÍÅÔÒÙ, ËÁË ÍÁËÓÉÍÁÌØÎÏÅ ËÏÌÉÞÅÓÔ×Ï
-    ÂÌÏËÏ× ÒÁÚÄÅÌÑÅÍÏÊ ÐÁÍÑÔÉ, <SMALL>SHMMAX;</SMALL> ÍÁËÓÉÍÁÌØÎÏÅ ËÏÌÉÞÅÓÔ×Ï
-    ÓÅÍÁÆÏÒÏ×, <SMALL>SEMMNS</SMALL> É <SMALL>SEMMNI;</SMALL> ÍÁËÓÉÍÁÌØÎÏÅ
-    ËÏÌÉÞÅÓÔ×Ï ÐÒÏÃÅÓÓÏ×, <SMALL>NPROC;</SMALL> ÍÁËÓÉÍÁÌØÎÏÅ ËÏÌÉÞÅÓÔ×Ï
-    ÐÒÏÃÅÓÓÏ× ÎÁ ÐÏÌØÚÏ×ÁÔÅÌÑ, <SMALL>MAXUPRC;</SMALL> É ÍÁËÓÉÍÁÌØÎÏÅ
-    ËÏÌÉÞÅÓÔ×Ï ÏÔËÒÙÔÙÈ ÆÁÊÌÏ×, <SMALL>NFILE</SMALL> É <SMALL>NINODE.</SMALL>
-    ðÒÉÞÉÎÁ ÓÏÚÄÁÎÉÑ ÏÇÒÁÎÉÞÅÎÉÑ ÎÁ ËÏÌÉÞÅÓÔ×Ï backend ÐÒÏÃÅÓÓÏ× ËÁË
-    ÒÁÚ É ÓÏÓÔÏÉÔ × ÔÏÍ, ÞÔÏÂÙ ×ÁÛÅÊ ÓÉÓÔÅÍÅ È×ÁÔÉÌÏ ÒÅÓÕÒÓÏ×.</P>
-
-    <P>÷ PostgreSQL ÄÏ ×ÅÒÓÉÉ 6.5, ÍÁËÓÉÍÁÌØÎÏÅ ËÏÌÉÞÅÓÔ×Ï backend ÐÒÏÃÅÓÓÏ×
-    ÂÙÌÏ 64, É ÉÚÍÅÎÅÎÉÅ ÜÔÏÇÏ ËÏÌÉÞÅÓÔ×Á ÔÒÅÂÏ×ÁÌÏ ÐÅÒÅËÏÍÐÉÌÑÃÉÉ ÐÏÓÌÅ
-    ÕÓÔÁÎÏ×ËÉ ËÏÎÓÔÁÎÔÙ MaxBackendId × <I>include/storage/sinvaladt.h</I>.</P>
-
-    <H4><A name="3.9">3.9</A>) þÔÏ ÜÔÏ ÚÁ ÆÁÊÌÙ <I>pg_sorttempNNN.NN</I>
-    × ÍÏÅÍ ËÁÔÁÌÏÇÅ Ó ÂÁÚÏÊ ÄÁÎÎÙÈ?</H4>
-
-    <P>üÔÏ ×ÒÅÍÅÎÎÙÅ ÆÁÊÌÙ, ÇÅÎÅÒÉÒÕÅÍÙÅ ×Ï ×ÒÅÍÑ ×ÙÐÏÌÎÅÎÉÑ ÚÁÐÒÏÓÁ.
-    îÁÐÒÉÍÅÒ, ÅÓÌÉ ÄÌÑ ÏÐÅÒÁÔÏÒÁ <SMALL>ORDER BY</SMALL> ÄÏÌÖÎÁ ÂÙÔØ
-    ×ÙÐÏÌÎÅÎÁ ÓÏÒÔÉÒÏ×ËÁ, ËÏÔÏÒÁÑ ÔÒÅÂÕÅÔ ÂÏÌØÛÅ ÍÅÓÔÁ ÞÅÍ ×ÙÄÅÌÅÎÎÏ
-    ÄÌÑ backend ÐÒÏÃÅÓÓÁ × ÏÐÃÉÉ <I>-S</I>, ÔÏ ÓÏÚÄÁÅÔÓÑ ×ÒÅÍÅÎÎÙÊ ÆÁÊÌ ÄÌÑ
-    ÈÒÁÎÅÎÉÑ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÄÁÎÎÙÈ.</P>
-
-    <P>÷ÒÅÍÅÎÎÙÅ ÆÁÊÌÙ ÄÏÌÖÎÙ ÕÄÁÌÑÔØÓÑ Á×ÔÏÍÁÔÉÞÅÓËÉ, ÎÏ ÜÔÏÇÏ ÍÏÖÅÔ
-    ÎÅ ÐÒÏÉÓÈÏÄÉÔØ, ÅÓÌÉ backend ÐÒÏÃÅÓÓ ÐÁÄÁÅÔ ×Ï ×ÒÅÍÑ ÓÏÒÔÉÒÏ×ËÉ.
-    åÓÌÉ Õ ×ÁÓ ÎÅ ÚÁÐÕÝÅÎÏ ÎÉ ÏÄÎÏÇÏ backend ÐÒÏÃÅÓÓÁ, ÔÏ ×Ù ÍÏÖÅÔÅ
-    ÓÐÏËÏÊÎÏ ÕÄÁÌÉÔØ ÆÁÊÌÙ pg_tempNNN.NN.</P>
-    <HR>
-
-    <H2 align="center">÷ÏÐÒÏÓÙ ÜËÓÐÌÕÁÔÁÃÉÉ</H2>
-
-    <H4><A name="4.1">4.1</A>) ÷ ÞÅÍ ÏÔÌÉÞÉÅ ÍÅÖÄÕ ÂÉÎÁÒÎÙÍ É ÎÏÒÍÁÌØÎÙÍ
-    ËÕÒÓÏÒÏÍ?</H4>
-
-    <P>óÍÏÔÒÉÔÅ ÏÐÉÓÁÎÉÅ ÎÁ ÓÔÒÁÎÉÃÁÈ ÒÕËÏ×ÏÄÓÔ×Á ÐÏÓ×ÑÝÅÎÎÙÍ
-    <SMALL>DECLARE</SMALL>.</P>
-
-    <H4><A name="4.2">4.2</A>) ëÁË ×ÙÐÏÌÎÉÔØ <SMALL>SELECT</SMALL> ÔÏÌØËÏ
-     ÄÌÑ ÎÅÓËÏÌØËÉÈ ÐÅÒ×ÙÈ ÓÔÒÏÞÅË ÚÁÐÒÏÓÁ?</H4>
-
-    <P>óÍÏÔÒÉÔÅ ÓÔÁÎÉÃÕ ÒÕËÏ×ÏÄÓÔ×Á ÐÏÓ×ÑÝÅÎÎÕÀ <SMALL>FETCH</SMALL>
-    ÉÌÉ ÉÓÐÏÌØÚÕÊÔÅ <SMALL>SELECT</SMALL> ... <SMALL>LIMIT</SMALL>....</P>
-
-    <P>äÁÖÅ ÅÓÌÉ ×Ù ÈÏÔÉÔÅ ÐÏÌÕÞÉÔØ ÔÏÌØËÏ ÐÅÒ×ÙÅ ÎÅÓËÏÌØËÏ ÚÁÐÉÓÅÊ,
-    ÂÕÄÅÔ ×ÙÐÏÌÎÅÎ ×ÅÓØ ÚÁÐÒÏÓ. òÁÓÓÍÏÔÒÉÍ ÚÁÐÒÏÓ, ËÏÔÏÒÙÊ ÉÍÅÅÔ
-    <SMALL>ORDER BY.</SMALL> åÓÌÉ ÅÓÔØ ËÁËÏÊ-ÌÉÂÏ ÉÎÄÅËÓ, ËÏÔÏÒÙÊ
-    ÓÏ×ÐÁÄÁÅÔ Ó <SMALL>ORDER BY</SMALL>, PostgreSQL ÍÏÖÅÔ
-    ×ÙÄÁÔØ ÔÏÌØËÏ ÎÅÓËÏÌØËÏ ÐÅÒ×ÙÈ ÚÁÐÒÏÛÅÎÎÙÈ ÚÁÐÉÓÅÊ ÉÌÉ ÍÏÖÅÔ
-    ×ÙÐÏÌÎÑÔØ ÚÁÐÒÏÓ ÐÏËÁ ÎÅ ÂÕÄÕÔ ×ÙÄÁÎÙ ÖÅÌÁÅÍÙÅ ÚÁÐÉÓÉ.</P>
-
-    <H4><A name="4.3">4.3</A>) ëÁË ÐÏÌÕÞÉÔØ ÓÐÉÓÏË ÔÁÂÌÉà ÉÌÉ ÄÒÕÇÉÈ
-     ËÏÍÐÏÎÅÎÔÏ× × <I>psql</I>?</H4>
-
-    <P>÷Ù ÍÏÖÅÔÅ ÐÏÓÍÏÔÒÅÔØ ÉÓÈÏÄÎÙÊ ËÏÄ <I>psql</I> × ÆÁÊÌÅ
-    <I>pgsql/src/bin/psql/describe.c</I>. ïÎ ÓÏÄÅÒÖÉÔ ËÏÍÁÎÄÙ
-    <SMALL>SQL</SMALL> ËÏÔÏÒÙÅ ÇÅÎÅÒÉÒÕÀÔÓÑ ÐÒÉ ××ÏÄÅ × psql ËÏÍÁÎÄ,
-    ÎÁÞÉÎÁÀÝÉÈÓÑ Ó ÏÂÒÁÔÎÏÊ ËÏÓÏÊ ÞÅÒÔÙ. ÷Ù ÔÁËÖÅ ÍÏÅÖÅÔÅ ÚÁÐÕÓÔÉÔØ
-    <I>psql</I> Ó ÏÐÃÉÅÊ <I>-E</I> ÔÁË, ÞÔÏÂÙ ÜÔÁ ÐÒÏÇÒÁÍÍÁ ×ÙÄÁ×ÁÌÁ
-    ÚÁÐÒÏÓÙ, ËÏÔÏÒÙÅ ÏÎÁ ÉÓÐÏÌØÚÕÅÔ ÄÌÑ ×ÙÐÏÌÎÅÎÉÑ ÚÁÄÁÎÎÙÈ ×ÁÍÉ
-    ËÏÍÁÎÄ.</P>
-
-    <H4><A name="4.4">4.4</A>) ëÁË ÕÄÁÌÉÔØ ËÏÌÏÎËÕ ÉÚ ÔÁÂÌÉÃÙ?</H4>
-
-    <P>íÙ ÎÅ ÐÏÄÄÅÒÖÉ×ÁÅÍ <SMALL>ALTER TABLE DROP COLUMN,</SMALL> ÎÏ
-    ÍÏÖÎÏ ÓÄÅÌÁÔØ ÔÁË:</P>
-<PRE>
-    BEGIN;
-    LOCK TABLE old_table;
-    SELECT ...  -- ×ÙÂÏÒËÁ ×ÓÅÈ ËÏÌÏÎÏË ÚÁ ÉÓËÌÀÞÅÎÉÅÍ ÔÏÊ, ËÏÔÏÒÕÀ ÈÏÔÉÔÅ ÕÄÁÌÉÔØ
-    INTO TABLE new_table
-    FROM old_table;
-    DROP TABLE old_table;
-    ALTER TABLE new_table RENAME TO old_table;
-    COMMIT;
-</PRE>
-
-    <H4><A name="4.5">4.5</A>) ëÁËÏ×Ù ÍÁËÓÉÍÁÌØÎÙÅ ÒÁÚÍÅÒÙ ÄÌÑ ÚÁÐÉÓÅÊ,
-    ÔÁÂÌÉÃ É ÂÁÚÙ ÄÁÎÎÙÈ?</H4>
-
-    <P>óÕÝÅÓÔ×ÕÀÔ ÓÌÅÄÕÀÝÉÅ ÏÇÒÁÎÉÞÅÎÉÑ:</P>
-<PRE>
-    íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÂÁÚÙ?              ÎÅÏÇÒÁÎÉÞÅÎ (ÓÕÝÅÓÔ×ÕÀÔ ÂÁÚÙ ÎÁ 60 GB)
-    íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÔÁÂÌÉÃÙ?           16 TB
-    íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÚÁÐÉÓÉ?            ÎÅÏÇÒÁÎÉÞÅÎ ÎÁÞÉÎÁÑ Ó ×ÅÒÓÉÉ 7.1
-    íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÐÏÌÑ?              1 GB ÎÁÞÉÎÁÑ Ó ×ÅÒÓÉÉ 7.1
-    íÁËÓÉÍÁÌØÎÏÅ ËÏÌÉÞÅÓÔ×Ï ÚÁÐÉÓÅÊ × ÔÁÂÌÉÃÅ?      ÎÅÏÇÒÁÎÉÞÅÎÏ
-    íÁËÓÉÍÁÌØÎÏÅ ËÏÌÉÞÅÓÔ×Ï ËÏÌÏÎÏË × ÔÁÂÌÉÃÅ?    250-1600 × ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ÔÉÐÁ
-    íÁËÓÉÍÁÌØÎÏÅ ËÏÌÉÞÅÓÔ×Ï ÉÎÄÅËÓÏ× × ÔÁÂÌÉÃÅ?   ÎÅÏÇÒÁÎÉÞÅÎÏ
-</PRE>
-    òÁÚÕÍÅÅÔÓÑ, ÐÏÎÑÔÉÅ "ÎÅÏÇÒÁÎÉÞÅÎÏ" ÎÁ ÓÁÍÏÍ ÄÅÌÅ ÏÇÒÁÎÉÞÉ×ÁÅÔÓÑ
-    ÄÏÓÔÕÐÎÙÍ ÄÉÓËÏ×ÙÍ ÐÒÏÓÔÒÁÎÉÓÔ×ÏÍ É ÒÁÚÍÅÒÁÍÉ ÐÁÍÑÔÉ/Ó×ÏÐÐÉÎÇÁ.
-    ëÏÇÄÁ ÚÎÁÞÅÎÉÑ ÐÅÒÅÞÉÓÌÅÎÎÙÅ ×ÙÛÅ ÎÅÏÐÒÁ×ÄÁÎÏ ÂÏÌØÛÉÅ, ÍÏÖÅÔ
-    ÐÏÓÔÒÁÄÁÔØ ÐÒÏÉÚ×ÏÄÉÔÅÌØÎÏÓÔØ.
-
-    <P>íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÔÁÂÌÉÃÙ × 16 TB ÎÅ ÔÒÅÂÕÅÔ ÞÔÏÂÙ ÏÐÅÒÁÃÉÏÎÎÁÑ
-    ÓÉÓÔÅÍÁ ÐÏÄÄÅÒÖÉ×ÁÌÁ ÆÁÊÌÙ ÂÏÌØÛÉÈ ÒÁÚÍÅÒÏ×. âÏÌØÛÉÅ ÔÁÂÌÉÃÙ ÈÒÁÎÑÔÓÑ
-    ËÁË ÍÎÏÖÅÓÔ×Ï ÆÁÊÌÏ× ÒÁÚÍÅÒÏÍ × 1 GB, ÔÁË ÞÔÏ ÏÇÒÁÎÉÞÅÎÉÑ, ËÏÔÏÒÙÅ
-    ÎÁËÌÁÄÙ×ÁÅÔ ÆÁÊÌÏ×ÁÑ ÓÉÓÔÅÍÁ ÎÅ ×ÁÖÎÙ.</P>
-
-    <P>íÁËÓÉÍÁÌØÎÙÊ ÒÁÚÍÅÒ ÔÁÂÌÉÃÙ É ÍÁËÓÉÍÁÌØÎÏÅ ËÏÌÉÞÅÓÔ×Ï ËÏÌÏÎÏË
-    ÍÏÇÕÔ ÂÙÔØ Õ×ÅÌÉÞÅÎÙ, ÅÓÌÉ ÒÁÚÍÅÒ ÂÌÏËÁ ÐÏ ÕÍÏÌÞÁÎÉÀ ÂÕÄÅÔ Õ×ÅÌÉÞÅÎ
-    ÄÏ 32k.</P>
-
-    <H4><A name="4.6">4.6</A>) ëÁË ÍÎÏÇÏ ÄÉÓËÏ×ÏÇÏ ÐÒÏÓÔÒÁÎÓÔ×Á × ÂÁÚÅ ÄÁÎÎÙÈ
-     ÎÕÖÎÏ ÄÌÑ ÓÏÈÒÁÎÅÎÉÑ ÄÁÎÎÙÈ ÉÚ ÏÂÙÞÎÏÇÏ ÔÅËÓÔÏ×ÏÇÏ ÆÁÊÌÁ?</H4>
-
-    <P>óõâä PostgreSQL ÍÏÖÅÔ ÐÏÔÒÅÂÏ×ÁÔØÓÑ ÄÉÓËÏ×ÏÇÏ ÐÒÏÓÔÒÁÎÓÔ×Á ÄÏ 5 ÒÁÚ
-    ÂÏÌØÛÅ ÄÌÑ ÓÏÈÒÁÎÅÎÉÑ ÄÁÎÎÙÈ ÉÚ ÐÒÏÓÔÏÇÏ ÔÅËÓÔÏ×ÏÇÏ ÆÁÊÌÁ.</P>
-
-    <P>÷ ËÁÞÅÓÔ×Å ÐÒÉÍÅÒÁ, ÒÁÓÓÍÏÔÒÉÍ ÆÁÊÌ × 100,000 ÓÔÒÏË × ËÁÖÄÏÊ, ÉÚ
-    ËÏÔÏÒÙÈ ÃÅÌÏÅ ÞÉÓÌÏ É ÔÅËÓÔÏ×ÏÅ ÏÐÉÓÁÎÉÅ. ðÒÉ ÜÔÏÍ ÄÌÉÎÁ ÔÅËÓÔÁ,
-    × ÓÒÅÄÎÅÍ, ÓÏÓÔÁ×ÌÑÅÔ 20 ÂÁÊÔ. òÁÚÍÅÒ ÐÒÏÓÔÏÇÏ ÆÁÊÌÁ ÓÏÓÔÁ×ÉÔ 2.8 MB.
-    òÁÚÍÅÒ ÂÁÚÙ PostgreSQL, ÓÏÄÅÒÖÁÝÅÊ ÜÔÉ ÖÅ ÄÁÎÎÙÅ ÓÏÓÔÁ×ÉÔ ÐÒÉÂÌÉÚÉÔÅÌØÎÏ
-    6.4 MB ÉÚ ËÏÔÏÒÙÈ:</P>
-<PRE>
-    36 ÂÁÊÔ: ÎÁ ËÁÖÄÙÊ ÚÁÇÏÌÏ×ÏË ÚÁÐÉÓÉ (ÐÒÉÂÌÉÚÉÔÅÌØÎÏ)
-  + 24 ÂÁÊÔÁ: ÏÄÎÏ ÐÏÌÅ Ó ÃÅÌÏÞÉÓÌÅÎÎÙÍ ÔÉÐÏÍ É ÏÄÎÏ ÔÅËÓÔÏ×ÏÅ ÐÏÌÅ
-   + 4 ÂÁÊÔÁ: ÕËÁÚÁÔÅÌØ ÎÁ ÓÔÒÁÎÉÃÅ ÄÌÑ ×ÓÅÊ ÚÁÐÉÓÉ
-   ----------------------------------------
-    64 ÂÁÊÔ ÎÁ ÚÁÐÉÓØ
-
-   òÁÚÍÅÒ ÓÔÒÁÎÉÃÙ ÄÁÎÎÙÈ × PostgreSQL ÓÏÓÔÁ×ÌÑÅÔ 8192 ÂÁÊÔ (8 KB), ÔÁË ÞÔÏ:
-
-   8192 ÂÁÊÔ ÎÁ ÓÔÒÁÎÉÃÕ
-   -------------------   =  128 ÚÁÐÉÓÅÊ ÎÁ ÓÔÒÁÎÉÃÕ âä (Ó ÏËÒÕÇÌÅÎÉÅÍ)
-     64 ÂÁÊÔ ÎÁ ÚÁÐÉÓØ
-
-   100000 ÓÔÒÏË ÄÁÎÎÙÈ
-   --------------------  =  782 ÓÔÒÁÎÉÃÙ × âä
-  128 ÚÁÐÉÓÅÊ ÎÁ ÓÔÒÁÎÉÃÕ
-
-782 ÓÔÒÁÎÉÃÙ âä * 8192 ÂÁÊÔ ÎÁ ÓÔÒÁÎÉÃÕ  =  6,406,144 ÂÁÊÔ (6.4 MB)
-</PRE>
-
-    <P>éÎÄÅËÓÙ ÎÅ ÔÒÅÂÕÀÔ ÔÁË ÍÎÏÇÏ, ÎÏ ÐÏÓËÏÌØËÕ ÏÎÉ ÓÏÚÄÁÀÔÓÑ ÄÌÑ
-    ÂÏÌØÛÏÇÏ ËÏÌÉÞÅÓÔ×Á ÄÁÎÎÙÈ, ÏÎÉ ÔÁËÖÅ ÍÏÇÕÔ ÂÙÔØ ×ÅÌÉËÉ.</P>
-
-    <H4><A name="4.7">4.7</A>) ëÁË ÍÎÅ ÕÂÅÄÉÔØÓÑ, ÞÔÏ ÓÕÝÅÓÔ×ÕÀÔ ÎÕÖÎÙÅ ÍÎÅ
-     ÔÁÂÌÉÃÙ, ÉÎÄÅËÓÙ, ÂÁÚÙ ÄÁÎÎÙÈ É ÐÏÌØÚÏ×ÁÔÅÌÉ?</H4>
-
-    <P><I>psql</I> ÉÍÅÅÔ ÎÅÓËÏÌØËÏ ËÏÍÁÎÄ, ÎÁÞÉÎÁÀÝÉÈÓÑ Ó ÏÂÒÁÔÎÏÊ ËÏÓÏÊ
-    ÞÅÒÔÙ, ÄÌÑ ÔÏÇÏ ÞÔÏÂÙ ÐÒÏÓÍÁÔÒÉ×ÁÔØ ÔÁËÕÀ ÉÎÆÏÒÍÁÃÉÀ. éÓÐÏÌØÚÕÊÔÅ
-    \? ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ Õ×ÉÄÅÔØ ÜÔÉ ËÏÍÁÎÄÙ. ôÁËÖÅ ÓÕÝÅÓÔ×ÕÀÔ ÓÉÓÔÅÍÎÙÅ
-    ÔÁÂÌÉÃÙ, ÉÍÑ ËÏÔÏÒÙÈ ÎÁÞÉÎÁÅÔÓÑ ÎÁ <i>pg_</i> É × ËÏÔÏÒÙÈ ÔÁËÖÅ ÓÏÄÅÒÖÉÔÓÑ
-    ÜÔÁ ÉÎÆÏÒÍÁÃÉÑ. åÝ£, <i>psql -l</i> ÐÏËÁÖÅÔ ÓÐÉÓÏË ×ÓÅÈ ÂÁÚ ÄÁÎÎÙÈ.</P>
-
-    <P>ôÁËÖÅ ÓÍÏÔÒÉÔÅ ÆÁÊÌ <I>pgsql/src/tutorial/syscat.source</I>. ÷ ÎÅÍ
-    ÐÒÅÄÓÔÁ×ÌÅÎÙ ÍÎÏÇÉÅ ÏÐÅÒÁÔÏÒÙ <SMALL>SELECT</SMALL> ËÏÔÏÒÙÅ ÎÕÖÎÙ
-    ÄÌÑ ÐÏÌÕÞÅÎÉÑ ÉÎÆÏÒÍÁÃÉÉ ÉÚ ÓÉÓÔÅÍÎÙÈ ÔÁÂÌÉÃ ÂÁÚÙ ÄÁÎÎÙÈ.</P>
-
-    <H4><A name="4.8">4.8</A>) õ ÍÅÎÑ ÍÅÄÌÅÎÎÏ ÒÁÂÏÔÁÀÔ ÚÁÐÒÏÓÙ ÉÌÉ ÎÅ
-     ÐÒÏÉÓÈÏÄÉÔ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÉÎÄÅËÓÏ×. ðÏÞÅÍÕ?</H4>
-
-    <P>éÎÄÅËÓÙ ÎÅ ÉÓÐÏÌØÚÕÀÔÓÑ ÄÌÑ ËÁÖÄÏÇÏ ÚÁÐÒÏÓÁ Á×ÔÏÍÁÔÉÞÅÓËÉ. ïÎÉ
-    ÉÓÐÏÌØÚÕÀÔÓÑ ÔÏÌØËÏ ÅÓÌÉ ÔÁÂÌÉÃÁ ÂÏÌØÛÅ ÍÉÎÉÍÁÌØÎÏÇÏ ÒÁÚÍÅÒÁ É ÚÁÐÒÏÓ
-    ×ÙÂÉÒÁÅÔ ÔÏÌØËÏ ÍÁÌÅÎØËÉÊ ÐÒÏÃÅÎÔ ÚÁÐÉÓÅÊ × ÔÁÂÌÉÃÅ. ôÁË ÕÓÔÒÏÅÎÏ,
-    ÐÏÔÏÍÕ ÞÔÏ ÄÏÓÔÕÐ Ë ÄÉÓËÕ Ó ÐÒÉÍÅÎÅÎÉÅÍ ÒÁÎÄÏÍÉÚÁÃÉÉ ÐÒÉ ÓËÁÎÉÒÏ×ÁÎÉÉ
-    ÉÎÄÅËÓÏ× ÉÎÏÇÄÁ ÍÅÄÌÅÎÎÅÅ, ÞÅÍ ÐÒÏÓÔÏÅ ÞÔÅÎÉÅ ÔÁÂÌÉÃÙ ÉÌÉ ÅÅ
-    ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÅ ÓËÁÎÉÒÏ×ÁÎÉÅ.</P>
-    
-    <P>þÔÏÂÙ ÏÐÒÅÄÅÌÉÔØ ÎÅÏÂÈÏÄÉÍÏÓÔØ ÉÓÐÏÌØÚÏ×ÁÎÉÑ ÉÎÄÅËÓÁ ÄÌÑ ËÁËÏÊ-ÌÉÂÏ
-    ÔÁÂÌÉÃÙ, PostgreSQL ÄÏÌÖÅÎ ÉÍÅÔØ ÓÔÁÔÉÓÔÉËÕ ÐÏ ÜÔÏÊ ÔÁÂÌÉÃÅ. üÔÁ
-    ÓÔÁÔÉÓÔÉËÁ ÓÏÂÉÒÁÅÔÓÑ ÐÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ <SMALL>VACUUM ANALYZE</SMALL>
-    ÉÌÉ ÐÒÏÓÔÏ <SMALL>ANALYZE</SMALL>. éÓÐÏÌØÚÕÑ ÓÔÁÔÉÓÔÉËÕ, ÏÐÔÉÍÉÚÁÔÏÒ
-    ÕÚÎÁÅÔ Ï ÔÏÍ ËÁË ÍÎÏÇÏ ÚÁÐÉÓÅÊ × ÔÁÂÌÉÃÅ É ÅÓÌÉ ÏÎ ÄÏÌÖÅÎ ÉÓÐÏÌØÚÏ×ÁÔØ
-    ÉÎÄÅËÓÙ, ÔÏ ÏÎ ÍÏÖÅÔ ÐÒÉÎÉÍÁÔØ ÌÕÞÛÉÅ ÒÅÛÅÎÉÑ. óÔÁÔÉÓÔÉËÁ ÔÁËÖÅ
-    ×ÌÉÑÅÔ ÎÁ ÏÐÒÅÄÅÌÅÎÉÅ ÏÐÔÉÍÁÌØÎÏÇÏ ÐÏÒÑÄËÁ Ó×ÑÚÙ×ÁÎÉÑ É ÍÅÔÏÄÁ Ó×ÑÚÙ×ÁÎÉÑ.
-    óÂÏÒ ÓÔÁÔÉÓÔÉËÉ ÄÏÌÖÅÎ ÐÅÒÉÏÄÉÞÅÓËÉ ×ÙÐÏÌÎÑÔÓÑ ÐÒÉ ÉÚÍÅÎÅÎÉÉ ÓÏÄÅÒÖÉÍÏÇÏ
-    ÔÁÂÌÉÃÙ.</P>
-    
-    <P>ïÂÙÞÎÏ ÉÎÄÅËÓÙ ÎÅ ÉÓÐÏÌØÚÕÀÔÓÑ ÄÌÑ <SMALL>ORDER BY</SMALL> ÉÌÉ ÄÌÑ
-    ×ÙÐÏÌÎÅÎÉÑ Ó×ÑÚÙ×ÁÎÉÊ. ðÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÐÅÒÅÂÏÒ ÓÌÅÄÕÀÝÉÊ ÚÁ Ñ×ÎÏÊ
-    ÓÏÒÔÉÒÏ×ËÏÊ ÏÂÙÞÎÏ ÂÙÓÔÒÅÅ, ÞÅÍ ÐÏÉÓË ÐÏ ÉÎÄÅËÓÁÍ × ÂÏÌØÛÏÊ ÔÁÂÌÉÃÅ.
-    ïÄÎÁËÏ, <SMALL>ORDER BY</SMALL> ÞÁÓÔÏ ËÏÍÂÉÎÉÒÕÅÔÓÑ Ó <SMALL>LIMIT</SMALL>
-    É × ÜÔÏÍ ÓÌÕÞÁÅ ÉÎÄÅËÓ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ, ÐÏÓËÏÌØËÕ ÐÒÉ ×ÙÐÏÌÎÅÎÉÉ
-    ÂÕÄÅÔ ×ÏÚ×ÒÁÝÁÔØÓÑ ÎÅÂÏÌØÛÁÑ ÞÁÓÔØ ÔÁÂÌÉÃÙ.</P>
-
-    <P>ëÏÇÄÁ ÉÓÐÏÌØÚÕÀÔÓÑ ÏÐÅÒÁÃÉÉ Ó ÛÁÂÌÏÎÁÍÉ, ÎÁÐÒÉÍÅÒ <SMALL>LIKE</SMALL>
-    ÉÌÉ <I>~</I>, ÉÎÄÅËÓÙ ÍÏÇÕÔ ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÙ ÔÏÌØËÏ ÅÓÌÉ ÎÁÞÁÌÏ
-    ÓÔÒÏËÉ-ÛÁÂÌÏÎÁ ÄÌÑ ÐÏÉÓËÁ, ÓÏÏÔ×ÅÔÓÔ×ÕÅÔ ÎÁÞÁÌÕ ÉÓËÏÍÏÊ ÓÔÒÏËÉ.
-    óÌÅÄÏ×ÁÔÅÌØÎÏ, ÄÌÑ ÔÏÇÏ, ÞÔÏÂÙ ÉÓÐÏÌØÚÏ×ÁÔØ ÉÎÄÅËÓÙ, ÛÁÂÌÏÎ ×
-    <SMALL>LIKE</SMALL> ÎÅ ÄÏÌÖÅÎ ÎÁÞÉÎÁÔØÓÑ ÎÁ <I>%</I>, Á × <I>~</I>
-    (ÐÏÉÓË ÒÅÇÕÌÑÒÎÏÇÏ ×ÙÒÁÖÅÎÉÑ) ÄÏÌÖÅÎ ÎÁÞÉÎÁÔØÓÑ ÎÁ <I>^</I>.</P>
-
-    <H4><A name="4.9">4.9</A>) ëÁË ÐÏÓÍÏÔÒÅÔØ ÎÁ ÔÏ, ËÁË ÏÐÔÉÍÉÚÁÔÏÒ ×ÙÐÏÌÎÑÅÔ
-     ÍÏÊ ÚÁÐÒÏÓ?</H4>
-
-    <P>óÍÏÔÒÉÔÅ ÓÔÒÁÎÉÃÕ ÒÕËÏ×ÏÄÓÔ×Á ÐÏÓ×ÑÝÅÎÎÕÀ <SMALL>EXPLAIN</SMALL>.</P>
-
-    <H4><A name="4.10">4.10</A>) þÔÏ ÔÁËÏÅ R-tree ÉÎÄÅËÓ?</H4>
-
-    <P>R-tree ÉÎÄÅËÓ ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÉÎÄÅËÓÉÒÏ×ÁÎÉÑ ÐÒÏÓÔÒÁÎÓÔ×ÅÎÎÙÈ ÄÁÎÎÙÈ.
-    éÎÄÅËÓ ÈÜÛÁ ÎÅ ÍÏÖÅÔ ÕÐÒÁ×ÌÑÔØ ÐÏÉÓËÁÍÉ ÄÉÁÐÁÚÏÎÁ. B-tree ÉÎÄÅËÓ
-    ÕÐÒÁ×ÌÑÅÔ ÔÏÌØËÏ ÐÏÉÓËÁÍÉ ÄÉÁÐÁÚÏÎÁ × ÏÄÎÏÍ ÉÚÍÅÒÅÎÉÉ. R-tree ÉÎÄÅËÓ
-    ÍÏÖÅÔ ÕÐÒÁ×ÌÑÔØ ÍÎÏÇÏÒÁÚÍÅÒÎÙÍÉ ÄÁÎÎÙÍÉ. îÁÐÒÉÍÅÒ, ÅÓÌÉ R-tree ÉÎÄÅËÓ
-    ÍÏÖÅÔ ÂÙÔØ ×ÓÔÒÏÅÎ × ÁÔÒÉÂÕÔ ÔÉÐÁ <I>point</I>, ÔÏ ÓÉÓÔÅÍÁ ÍÏÖÅÔ
-    ÂÏÌÅÅ ÜÆÆÅËÔÉ×ÎÏ ÏÔ×ÅÔÉÔØ ÎÁ ÚÁÐÒÏÓ ÔÉÐÁ "×ÙÂÒÁÔØ ×ÓÅ ÔÏÞËÉ ×ÎÕÔÒÉ
-    ÚÁÄÁÎÎÏÇÏ ÞÅÔÙÒÅÈÕÇÏÌØÎÉËÁ."</P>
-
-    <P>ëÁÎÏÎÉÞÅÓËÉÊ ÉÓÔÏÞÎÉË, ÏÐÉÓÙ×ÁÀÝÉÊ ÐÅÒ×ÏÎÁÞÁÌØÎÏÅ ÓÏÚÄÁÎÉÅ R-tree
-    ÜÔÏ:</P>
-
-    <P>Guttman, A. "R-trees: A Dynamic Index Structure for Spatial
-    Searching." Proceedings of the 1984 ACM SIGMOD Int'l Conf on Mgmt
-    of Data, 45-57.</P>
-
-    <P>÷Ù ÍÏÖÅÔÅ ÎÁÊÔÉ ÜÔÏÔ ÄÏËÕÍÅÎÔ × ËÎÉÇÅ Stonebraker'Á "Readings in
-    Database Systems".</P>
-
-    <P>÷ÓÔÒÏÅÎÎÎÙÅ R-tree ÍÏÇÕÔ ÕÐÒÁ×ÌÑÔØ ÐÏÌÉÇÏÎÁÍÉ É ÂÏËÓÁÍÉ. ÷ ÔÅÏÒÉÉ,
-    R-tree ÍÏÇÕÔ ÂÙÔØ ÒÁÓÛÉÒÅÎÙ ÄÌÑ ÕÐÒÁ×ÌÅÎÉÑ ÂÏÌØÛÉÍ ËÏÌÉÞÅÓÔ×ÏÍ
-    ÉÚÍÅÒÅÎÉÊ. îÁ ÐÒÁËÔÉËÅ, ÒÁÓÛÉÒÅÎÉÅ R-tree ÔÒÅÂÕÅÔ ÎÅËÏÔÏÒÙÈ ÕÓÉÌÉÊ É
-    Õ ÎÁÓ, × ÄÁÎÎÙÊ ÍÏÍÅÎÔ, ÎÅÔ ËÁËÏÊ-ÌÉÂÏ ÄÏËÕÍÅÎÔÁÃÉÉ Ï ÔÏÍ, ËÁË ÜÔÏ
-    ÓÄÅÌÁÔØ.</P>
-
-    <H4><A name="4.11">4.11</A>) þÔÏ ÔÁËÏÅ Genetic Query
-    Optimizer?</H4>
-
-    <P>íÏÄÕÌØ <SMALL>GEQO</SMALL> ÐÒÏÉÚ×ÏÄÉÔ ÂÙÓÔÒÕÀ ÏÐÔÉÍÉÚÁÃÉÀ ÚÁÐÒÏÓÁ,
-    ËÏÇÄÁ ÐÒÏÉÓÈÏÄÉÔ Ó×ÑÚÙ×ÁÎÉÅ ÍÎÏÇÉÈ ÔÁÂÌÉà ÞÅÒÅÚ Genetic Algorithm (GA).
-    üÔÏ ÐÏÚ×ÏÌÑÅÔ ÕÐÒÁ×ÌÑÔØ ÂÏÌØÛÉÍÉ ÚÁÐÒÏÓÁÍÉ ÎÁ Ó×ÑÚÙ×ÁÎÉÅ ÞÅÒÅÚ
-    ÎÅÉÓÔÏÝÁÀÝÉÊ ÐÏÉÓË.</P>
-
-    <H4><A name="4.12">4.12</A>) ëÁË ÍÎÅ ×ÙÐÏÌÎÉÔØ ÐÏÉÓË ÒÅÇÕÌÑÒÎÏÇÏ ×ÙÒÁÖÅÎÉÑ
-     É ÐÏÉÓË ÎÅÚÁ×ÉÓÉÍÙÊ ÏÔ ÒÅÇÉÓÔÒÁ ÂÕË× ÐÏÉÓË ÒÅÇÕÌÑÒÎÏÇÏ ×ÙÒÁÖÅÎÉÑ?
-     ëÁË ÍÎÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÉÎÄÅËÓ ÄÌÑ ÐÏÉÓËÁ ÎÅÚÁ×ÉÓÉÍÏÇÏ ÏÔ ÒÅÇÉÓÔÒÁ ÂÕË×?</H4>
-
-    <P>ïÐÅÒÁÔÏÒ <I>~</I> ÐÒÏÉÚ×ÏÄÉÔ ÐÏÉÓË ÒÅÇÕÌÑÒÎÏÇÏ ×ÙÒÁÖÅÎÉÑ, Á ÏÐÅÒÁÔÏÒ
-    <I>~*</I> ÐÒÏÉÚ×ÏÄÉÔ ÎÅÚÁ×ÉÓÉÍÙÊ ÏÔ ÒÅÇÉÓÔÒÁ ÂÕË× ÐÏÉÓË ÒÅÇÕÌÑÒÎÏÇÏ
-    ×ÙÒÁÖÅÎÉÑ. îÅÚÁ×ÉÓÉÍÙÊ ÏÔ ÒÅÇÉÓÔÒÁ ×ÁÒÉÁÎÔ <SMALL>LIKE</SMALL> ÎÁÚÙ×ÁÅÔÓÑ
-    <SMALL>ILIKE</SMALL> × PostgreSQL ÎÁÞÉÎÁÑ Ó ×ÅÒÓÉÉ 7.1.</P>
-
-    <P>îÅÚÁ×ÉÓÉÍÏÅ ÏÔ ÒÅÇÉÓÔÒÁ ÓÒÁ×ÎÅÎÉÅ ÏÂÙÞÎÏ ×ÙÒÁÖÁÅÔÓÑ ÔÁË:</P>
-<PRE>
-    SELECT *
-    FROM tab
-    WHERE lower(col) = 'abc'
-   
-</PRE>
-    üÔÁ ËÏÎÓÔÒÕËÃÉÑ ÎÅ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÔØ ÓÔÁÎÄÁÒÔÎÙÊ ÉÎÄÅËÓ. ïÄÎÁËÏ, ÅÓÌÉ
-    ×Ù ÓÏÚÄÁÄÉÔÅ ÆÕÎËÃÉÏÎÁÌØÎÙÊ ÉÎÄÅËÓ, ÏÎ ÂÕÄÅÔ ÉÓÐÏÌØÚÏ×ÁÎ:
-<PRE>
-    CREATE INDEX tabindex on tab (lower(col));
-   
-</PRE>
-
-    <H4><A name="4.13">4.13</A>) ëÁË Ñ ÍÏÇÕ ÏÐÒÅÄÅÌÉÔØ, ÞÔÏ ÚÎÁÞÅÎÉÅ ÐÏÌÑ
-    ÒÁ×ÎÏ <SMALL>NULL</SMALL> × ËÁËÏÍ-ÌÉÂÏ ÚÁÐÒÏÓÅ?</H4>
-
-    <P>÷Ù ÐÒÏÓÔÏ ÓÒÁ×ÎÉ×ÁÅÔÅ ÚÎÁÞÅÎÉÅ Ó <SMALL>IS NULL</SMALL> É
-    <SMALL>IS NOT NULL</SMALL>.</P>
-
-    <H4><A name="4.14">4.14</A>) ëÁËÏ×Ù ÏÔÌÉÞÉÑ ÍÅÖÄÕ ÒÁÚÎÙÍÉ ÓÉÍ×ÏÌØÎÙÍÉ
-     ÔÉÐÁÍÉ?</H4>
-<PRE>
-ôÉÐ            ÷ÎÕÔÒÅÎÎÅÅ ÉÍÑ   úÁÍÅÞÁÎÉÑ
---------------------------------------------------
-"char"          char            1 ÓÉÍ×ÏÌ
-CHAR(#)         bpchar          ÚÁÐÏÌÎÑÅÔÓÑ ÐÕÓÔÏÔÏÊ ÄÏ ÆÉËÓÉÒÏ×ÁÎÎÏÊ ÄÌÉÎÙ
-VARCHAR(#)      varchar         ÒÁÚÍÅÒ ÚÁÄÁÅÔ ÍÁËÓÉÍÁÌØÎÕÀ ÄÌÉÎÕ, ÎÅÔ ÚÁÐÏÌÎÅÎÉÑ
-TEXT            text            ÎÅÔ ÚÁÄÁ×ÁÅÍÏÇÏ ×ÅÒÈÎÅÇÏ ÏÇÒÁÎÉÞÅÎÉÑ ÉÌÉ ÄÌÉÎÙ
-BYTEA           bytea           ÍÁÓÓÉ× ÂÁÊÔ ÐÅÒÅÍÅÎÎÏÊ ÄÌÉÎÙ (ÍÏÖÎÏ ÉÓÐÏÌØÚÏ×ÁÔØ null-ÂÁÊÔ ÂÅÚ ÏÐÁÓËÉ)
-</PRE>
-
-    <P>÷ÎÕÔÒÅÎÎÅÅ ÉÍÑ ×Ù ÍÏÖÅÔÅ Õ×ÉÄÅÔØ, ËÏÇÄÁ ÓÍÏÔÒÉÔÅ ÓÉÓÔÅÍÎÙÅ ËÁÔÁÌÏÇÉ
-    É × ÎÅËÏÔÏÒÙÈ ÓÏÏÂÝÅÎÉÑÈ ÏÂ ÏÛÉÂËÁÈ.</P>
-
-    <P>ðÏÓÌÅÄÎÉÅ ÞÅÔÙÒÅ ÔÉÐÁ Ñ×ÌÑÀÔÓÑ "varlena" ÔÉÐÁÍÉ (Ô.Å., ÐÅÒ×ÙÅ
-    ÞÅÔÙÒÅ ÂÁÊÔÁ ÎÁ ÄÉÓËÅ Ñ×ÌÑÀÔÓÑ ÄÌÉÎÎÏÊ, ÚÁ ËÏÔÏÒÏÊ ÓÌÅÄÕÀÔ ÄÁÎÎÙÅ).
-    ôÁËÉÍ ÏÂÒÁÚÏÍ, ÆÁËÔÉÞÅÓËÉ ÉÓÐÏÌØÚÕÅÍÏÅ ÐÒÏÓÔÒÁÎÓÔ×Ï ÂÏÌØÛÅ, ÞÅÍ
-    ÏÂÏÚÎÁÞÅÎÎÙÊ ÒÁÚÍÅÒ. ïÄÎÁËÏ, ÜÔÉ ÔÉÐÙ ÄÁÎÎÙÈ ÔÁËÖÅ ÐÏÄÄÁÀÔÓÑ ÓÖÁÔÉÀ
-    ÉÌÉ ÍÏÇÕÔ ÂÙÔØ ÓÏÈÒÁÎÅÎÙ ÎÅ × ÓÔÒÏËÏÍ ×ÉÄÅ ÞÅÒÅÚ <SMALL>TOAST</SMALL>,
-    ÔÁË ÞÔÏ ÚÁÎÉÍÁÅÍÏÅ ÄÉÓËÏ×ÏÅ ÐÒÏÓÔÒÁÎÓÔ×Ï ÍÏÖÅÔ ÔÁËÖÅ ÂÙÔØ É ÍÅÎØÛÅ,
-    ÞÅÍ ÏÖÉÄÁÌÏÓØ.</P>
-
-    <P><SMALL>CHAR()</SMALL> - ÜÔÏ ÌÕÞÛÅÅ ÒÅÛÅÎÉÅ ÄÌÑ ÈÒÁÎÅÎÉÑ ÓÔÒÏË, ËÏÔÏÒÙÅ
-    ÏÂÙÞÎÏ ÉÍÅÀÔ ÏÄÉÎÁËÏ×ÕÀ ÄÌÉÎÕ. <SMALL>VARCHAR()</SMALL> - ÜÔÏ ÌÕÞÛÅÅ
-    ÒÅÛÅÎÉÅ, ËÏÇÄÁ ÎÕÖÎÏ ÈÒÁÎÉÔØ ÓÔÒÏËÉ ÐÅÒÅÍÅÎÎÏÊ ÄÌÉÎÙ, ÎÏ ÎÅ ÐÒÅ×ÙÛÁÀÝÉÅ
-    ÏÐÒÅÄÅÌÅÎÎÏÇÏ ÒÁÚÍÅÒÁ. <SMALL>TEXT</SMALL> - ÜÔÏ ÌÕÞÛÅÅ ÒÅÛÅÎÉÅ ÄÌÑ ÓÔÒÏË
-    ÎÅÏÇÒÁÎÉÞÅÎÎÏÊ ÄÌÉÎÙ, Ó ÍÁËÓÉÍÁÌØÎÏ ÄÏÐÕÓÔÉÍÏÊ ÄÌÉÎÏÊ × 1 ÇÉÇÁÂÁÊÔ.
-    <SMALL>BYTEA</SMALL> ÄÌÑ ÈÒÁÎÅÎÉÑ ÂÉÎÁÒÎÙÈ ÄÁÎÎÙÈ, ÚÎÁÞÅÎÉÑ ËÏÔÏÒÙÈ
-    ÍÏÇÕÔ ×ËÌÀÞÁÔØ <SMALL>NULL</SMALL> ÂÁÊÔÙ.</P>
-
-    <H4><A name="4.15.1">4.15.1</A>) ëÁË ÍÎÅ ÓÏÚÄÁÔØ ÐÏÌÅ
-    serial/Ó-Á×ÔÏ-Õ×ÅÌÉÞÅÎÉÅÍ?</H4>
-
-    <P>PostgreSQL ÐÏÄÄÅÒÖÉ×ÁÅÔ ÔÉÐ ÄÁÎÎÙÈ <SMALL>SERIAL</SMALL>. ïÎ
-    Á×ÔÏÍÁÔÉÞÅÓËÉ ÓÏÚÄÁÅÔ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ É ÉÎÄÅËÓ ÄÌÑ ËÏÌÏÎËÉ.
-    îÁÐÒÉÍÅÒ:</P>
-<PRE>
-    CREATE TABLE person ( 
-        id   SERIAL, 
-        name TEXT 
-    );
-</PRE>
-    Á×ÔÏÍÁÔÉÞÅÓËÉ ÔÒÁÎÓÌÉÒÕÅÔÓÑ ×: 
-<PRE>
-    CREATE SEQUENCE person_id_seq;
-    CREATE TABLE person ( 
-        id   INT4 NOT NULL DEFAULT nextval('person_id_seq'),
-        name TEXT 
-    );
-    CREATE UNIQUE INDEX person_id_key ON person ( id );
-</PRE>
-    óÍÏÔÒÉÔÅ ÐÏÄÒÏÂÎÏÓÔÉ Ï ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÑÈ ÎÁ ÓÔÒÁÎÉÃÅ ÒÕËÏ×ÏÄÓÔ×Á
-    ÐÏÓ×ÑÝÅÎÎÏÊ <I>create_sequence</I>. ÷Ù ÔÁËÖÅ ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ
-    ËÁÖÄÏÅ ÐÏÌÅ <I>OID</I> × ÚÁÐÉÓÉ ËÁË ÕÎÉËÁÌØÎÏÅ ÚÎÁÞÅÎÉÅ. ïÄÎÁËÏ,
-    ÅÓÌÉ ×ÁÍ ÎÕÖÅÎ ÄÁÍÐ É ÐÅÒÅÚÁÇÒÕÚËÁ ÂÁÚÙ ÄÁÎÎÙÈ, ×ÁÍ ÎÅÏÂÈÏÄÉÍÏ
-    ÉÓÐÏÌØÚÏ×ÁÔØ ËÏÍÁÎÄÕ <I>pg_dump</I> Ó ÏÐÃÉÅÊ <I>-o</I> ÉÌÉ ÏÐÃÉÀ
-    <SMALL>COPY WITH OIDS</SMALL> ÄÌÑ ÓÏÈÒÁÎÅÎÉÑ ÚÎÁÞÅÎÉÊ ÐÏÌÑ
-    <SMALL>OID</SMALL>.
-
-    <H4><A name="4.15.2">4.15.2</A>) ëÁË ÍÎÅ ÐÏÌÕÞÉÔØ ÚÎÁÞÅÎÉÅ ÐÒÉ ×ÓÔÁ×ËÅ
-    <SMALL>SERIAL</SMALL>?</H4>
-
-    <P>ïÄÉÎ ÉÚ ÓÐÏÓÏÂÏ× ÓÏÓÔÏÉÔ × ÐÏÌÕÞÅÎÉÉ ÓÌÅÄÕÀÝÅÇÏ ÚÎÁÞÅÎÉÑ
-    <SMALL>SERIAL</SMALL> ÉÚ ÏÂßÅËÔÁ sequence Ó ÐÏÍÏÝØÀ ÆÕÎËÃÉÉ
-    <I>nextval()</I> <I>ÐÅÒÅÄ</I> ×ÓÔÁ×ËÏÊ É ÚÁÔÅÍ ×ÓÔÁ×ÌÑÔØ ÜÔÏ ÚÎÁÞÅÎÉÅ
-    Ñ×ÎÏ. éÓÐÏÌØÚÕÊÔÅ ÔÁÂÌÉÃÕ-ÐÒÉÍÅÒ × <A href="#4.15.1">4.15.1</A>, ÞÔÏÂÙ
-    Õ×ÉÄÅÔØ ËÁË ÜÔÏ ÄÅÌÁÅÔÓÑ × Perl:</P>
-<PRE>
-    new_id = output of "SELECT nextval('person_id_seq')"
-    INSERT INTO person (id, name) VALUES (new_id, 'Blaise Pascal');
-</PRE>
-    úÁÔÅÍ ×Ù ÄÏÌÖÎÙ ÔÁËÖÅ ÓÏÈÒÁÎÉÔØ ÎÏ×ÏÅ ÚÎÁÞÅÎÉÅ × ÐÅÒÅÍÅÎÎÏÊ
-    <CODE>new_id</CODE> ÄÌÑ ÅÇÏ ÉÓÐÏÌØÚÏ×ÁÎÉÑ × ÄÒÕÇÉÈ ÚÁÐÒÏÓÁÈ (ÎÁÐÒÉÍÅÒ
-    ÔÁËÉÈ ËÁË ×ÎÅÛÎÉÊ ËÌÀÞ ÄÌÑ ÔÁÂÌÉÃÙ <CODE>person</CODE>). úÁÍÅÔÉÍ,
-    ÞÔÏ ÉÍÑ Á×ÔÏÍÁÔÉÞÅÓËÉ ÓÏÚÄÁÎÎÏÇÏ ÏÂßÅËÔÁ <SMALL>SEQUENCE</SMALL> 
-    ÂÕÄÅÔ &lt;<I>table</I>&gt;_&lt;<I>serialcolumn</I>&gt;_<I>seq</I>,
-    ÇÄÅ <I>table</I> É <I>serialcolumn</I> Ñ×ÌÑÀÔÓÑ ÓÏÏÔ×ÅÔÓÔ×ÅÎÎÏ
-    ÉÍÅÎÁÍÉ ×ÁÛÅÊ ÔÁÂÌÉÃÙ É ×ÁÛÅÊ ËÏÌÏÎËÉ <SMALL>SERIAL</SMALL>. 
-
-    <P>÷ ËÁÞÅÓÔ×Å ÁÌØÔÅÒÎÁÔÉ×Ù, ×Ù ÍÏÖÅÔÅ ÐÏÌÕÞÉÔØ ÎÁÚÎÁÞÅÎÎÏÅ ÚÎÁÞÅÎÉÅ
-    <SMALL>SERIAL</SMALL> Ó ÐÏÍÏÝØÀ ÆÕÎËÃÉÉ <I>currval</I>()
-    <I>ÐÏÓÌÅ</I> ÐÒÏ×ÅÄÅÎÉÑ ÏÂÙÞÎÏÊ ÏÐÅÒÁÃÉÉ ×ÓÔÁ×ËÉ, ÎÁÐÒÉÍÅÒ</P>
-<PRE>
-    INSERT INTO person (name) VALUES ('Blaise Pascal');
-    new_id = output of "SELECT currval('person_id_seq')";
-</PRE>
-    é ÎÁËÏÎÅÃ, ×Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÚÎÁÞÅÎÉÅ
-    <A href="#4.16"><SMALL>OID</SMALL></A>, ×ÏÚÒÁÝÁÅÍÏÅ ÉÚ ÏÐÅÒÔÏÒÁ
-    <SMALL>INSERT</SMALL> ÞÔÏÂÙ Õ×ÉÄÅÔØ ÚÎÁÞÅÎÉÅ ÐÏ ÕÍÏÌÞÁÎÉÀ, ÞÔÏ
-    ÐÒÅÄÐÏÌÏÖÉÔÅÌØÎÏ Ñ×ÌÑÅÔÓÑ ÎÁÉÍÅÎÅÅ ÐÅÒÅÎÏÓÉÍÙÍ ÎÁ ÄÒÕÇÉÅ ÐÌÁÔÆÏÒÍÙ
-    ÒÅÛÅÎÉÅÍ. ÷ Perl, ÉÓÐÏÌØÚÕÑ DBI Ó ÍÏÄÕÌÅÉ Edmund Mergl'Ñ DBD::Pg,
-    ÚÎÁÞÅÎÉÅ oid ÓÔÁÎÏ×ÉÔÓÑ ÄÏÓÔÕÐÎÙÍ ÞÅÒÅÚ <I>$sth-&gt;{pg_oid_status}</I>
-    ÐÏÓÌÅ <I>$sth-&gt;execute()</I>. 
-
-    <H4><A name="4.15.3">4.15.3</A>) îÅ ÍÏÖÅÔ ÌÉ ÐÏÌÕÞÉÔØÓÑ ÔÁË, ÞÔÏ
-    ÉÓÐÏÌØÚÏ×ÁÎÉÅ <I>currval()</I> É <I>nextval()</I> ÐÒÉ×ÅÄÅÔ Ë
-    ÚÁÃÉËÌÉÒÏ×ÁÎÉÀ Ó ÄÒÕÇÉÍÉ ÐÏÌØÚÏ×ÁÔÅÌÑÍÉ?</H4>
-
-    <P>îÅÔ. Currval() ×ÏÚ×ÒÁÝÁÅÔ ÔÅËÕÝÅÅ ÚÎÁÞÅÎÉÅ, ÎÁÚÎÁÞÅÎÎÏÅ ×ÁÛÅÍ
-    backend'ÏÍ, Á ÎÅ ÄÒÕÇÉÍÉ ÐÏÌØÚÏ×ÁÔÅÌÑÍÉ.</P>
-
-    <H4><A name="4.15.4">4.15.4</A>) ðÏÞÅÍÕ ÞÉÓÌÁ ÉÚ ÍÏÅÊ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÉ
-    ÎÅ ÉÓÐÏÌØÚÕÀÔÓÑ ÓÎÏ×Á ÐÒÉ ÏÔÍÅÎÅ ÔÒÁÎÚÁËÃÉÉ? ðÏÞÅÍÕ ÓÏÚÄÁÀÔÓÑ ÒÁÚÒÙ×Ù
-    ÐÒÉ ÎÕÍÅÒÁÃÉÉ × ËÏÌÏÎËÅ, ÇÄÅ Ñ ÉÓÐÏÌØÚÕÀ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔØ/SERIAL?</H4>
-
-    <P>äÌÑ ÒÅÁÌÉÚÁÃÉÉ ËÏÎËÕÒÅÔÎÏÓÔÉ, ÚÎÁÞÅÎÉÑ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÏÓÔÅÊ, ÐÒÉ
-    ÎÅÏÂÈÏÄÉÍÏÓÔÉ ×ÙÄÁÀÔÓÑ ×Ï ×ÒÅÍÑ ÚÁÐÕÓËÁ ÔÒÁÎÚÁËÃÉÊ É ÎÅ ÂÌÏËÉÒÕÀÔÓÑ
-    ÄÏ ÐÏÌÎÏÇÏ ×ÙÐÏÌÎÅÎÉÑ ÔÒÁÎÚÁËÃÉÊ. üÔÏ ÍÏÖÅÔ ×ÙÚÙ×ÁÔØ ÒÁÚÒÙ×Ù ×
-    ÎÕÍÅÒÁÃÉÉ ÐÒÉ ÏÔÍÅÎÅ ÔÒÁÎÚÁËÃÉÊ.</P>
-
-
-    <H4><A name="4.16">4.16</A>) þÔÏ ÔÁËÏÅ <SMALL>OID</SMALL>? þÔÏ ÔÁËÏÅ
-    <SMALL>TID</SMALL>?</H4>
-
-    <P>ðÏÌÑ <SMALL>OID</SMALL> ÓÌÕÖÁÔ ÕÎÉËÁÌØÎÙÍÉ ÉÄÅÔÉÆÉËÁÔÏÒÁÍÉ ÚÁÐÉÓÅÊ
-    × PostgreSQL. ëÁÖÄÁÑ ÚÁÐÉÓØ, ËÏÔÏÒÁÑ ÓÏÚÄÁ£ÔÓÑ × PostgreSQL ÐÏÌÕÞÁÅÔ
-    ÕÎÉËÁÌØÎÙÊ <SMALL>OID</SMALL>. ÷ÓÅ ÚÎÁÞÅÎÉÑ <SMALL>OID</SMALL>
-    ÇÅÎÅÒÉÒÕÅÍÙÅ ×Ï ×ÒÅÍÑ <I>initdb</I> ÉÍÅÀÔ ÚÎÁÞÅÎÉÑ ÍÅÎØÛÅ 16384 (ÉÚ
-    <I>backend/access/transam.h</I>). ÷ÓÅ ÓÏÚÄÁÎÎÙÅ ÐÏÌØÚÏ×ÁÔÅÌÅÍ
-    <SMALL>OID</SMALL> ÉÍÅÀÔ ÂïÌØÛÉÅ ÚÎÁÞÅÎÉÅ. ðÏ ÕÍÏÌÞÁÎÉÀ, ×ÓÅ ÜÔÉ
-    <SMALL>OID</SMALL> Ñ×ÌÑÀÔÓÑ ÕÎÉËÁÌØÎÙÍÉ ÎÅ ÔÏÌØËÏ ×ÎÕÔÒÉ ËÁËÏÊ-ÌÉÂÏ
-    ÔÁÂÌÉÃÙ ÉÌÉ ÂÁÚÙ ÄÁÎÎÙÈ, ÎÏ É ×ÎÕÔÒÉ ×ÓÅÊ óõâä PostgreSQL.</P>
-
-    <P>PostgreSQL ÉÓÐÏÌØÚÕÅÔ <SMALL>OID</SMALL> × Ó×ÏÉÈ ×ÎÕÔÒÅÎÎÉÈ ÓÉÓÔÅÍÎÙÈ
-    ÔÁÂÌÉÃÁÈ ÄÌÑ Ó×ÑÚÉ ÚÁÐÉÓÅÊ É ÔÁÂÌÉÃ. úÎÁÞÅÎÉÑ <SMALL>OID</SMALL> ÍÏÇÕÔ
-    ÂÙÔØ ÉÓÐÏÌØÚÏ×ÁÎÙ ÄÌÑ ÉÄÅÎÔÉÆÉËÁÃÉÉ ÚÁÄÁÎÎÙÈ ÐÏÌØÚÏ×ÁÔÅÌÅÍ ÚÁÐÉÓÅÊ,
-    Á ÔÁËÖÅ ÉÓÐÏÌØÚÏ×ÁÔØÓÑ ÐÒÉ Ó×ÑÚÙ×ÁÎÉÑÈ. òÅËÏÍÅÎÄÕÅÔÓÑ ÉÓÐÏÌØÚÏ×ÁÔØ
-    ÔÉÐ ËÏÌÏÎËÉ <SMALL>OID</SMALL> ÄÌÑ ÈÒÁÎÅÎÉÑ ÚÎÁÞÅÎÉÊ <SMALL>OID</SMALL>
-    ÷Ù ÍÏÖÅÔÅ ÓÏÚÄÁÔØ ÉÎÄÅËÓ ÎÁ ÐÏÌÅ <SMALL>OID</SMALL> ÄÌÑ ÂÏÌÅÅ ÂÙÓÔÒÏÇÏ
-    ÄÏÓÔÕÐÁ.</P>
-
-    <P>úÎÁÞÅÎÉÑ <SMALL>OID</SMALL> ÎÁÚÎÁÞÁÀÔÓÑ ÄÌÑ ×ÓÅÈ ÎÏ×ÙÈ ÚÁÐÉÓÅÊ ÉÚ
-    ÃÅÎÔÒÁÌØÎÏÊ ÏÂÌÁÓÔÉ, ËÏÔÏÒÙÅ ÉÓÐÏÌØÚÕÀÔÓÑ ×ÓÅÍÉ ×ÓÅÍÉ ÂÁÚÁÍÉ ÄÁÎÎÙÈ.
-    åÓÌÉ ×Ù ÈÏÔÉÔÅ ÉÚÍÅÎÉÔØ <SMALL>OID</SMALL> ÎÁ ËÁËÏÅ-ÌÉÂÏ ÄÒÕÇÏÅ
-    ÚÎÁÞÅÎÉÅ ÉÌÉ ÅÓÌÉ ×Ù ÈÏÔÉÔÅ ÓÏÚÄÁÔØ ËÏÐÉÀ ÔÁÂÌÉÃÙ Ó ÔÁËÉÍÉÖÅ
-    <SMALL>OID</SMALL>, ÔÏ ÜÔÏ ÍÏÖÎÏ ÓÄÅÌÁÔØ ÔÁË:</P>
-<PRE>
-        CREATE TABLE new_table(old_oid oid, mycol int);
-        SELECT old_oid, mycol INTO new FROM old;
-        COPY new TO '/tmp/pgtable';
-        DELETE FROM new;
-        COPY new WITH OIDS FROM '/tmp/pgtable';
-<!--
-    CREATE TABLE new_table (mycol int);
-    INSERT INTO new_table (oid, mycol) SELECT oid, mycol FROM old_table;
--->
-</PRE>
-
-    <P><SMALL>OID</SMALL> ÈÒÁÎÉÔÓÑ ËÁË 4-È ÂÁÊÔÎÏÅ ÃÅÌÏÅ É ÎÅ ÍÏÖÅÔ ÐÒÅ×ÙÛÁÔØ
-    ÚÎÁÞÅÎÉÅ × 4 ÍÉÌÌÉÁÒÄÁ. ïÄÎÁËÏ, ÅÝÅ ÎÉËÔÏ ÎÅ ÓÏÏÂÝÉÌ Ï ÔÏÍ, ÞÔÏ ÔÁËÏÅ
-    ÐÒÏÉÚÏÛÌÏ, ÎÏ ÍÙ ÐÌÁÎÉÒÕÅÍ ÄÏ ÔÏÇÏ ËÁË ÜÔÏ ÓÌÕÞÉÔØÓÑ ÉÚÂÁ×ÉÔÓÑ ÏÔ
-    ÜÔÏÇÏ ÏÇÒÁÎÉÞÅÎÉÑ.</P>
-
-    <P>T<SMALL>ID</SMALL> ÉÓÐÏÌØÚÕÅÔÓÑ ÄÌÑ ÉÄÅÎÔÉÆÉËÁÃÉÉ ÓÐÅÃÉÁÌØÎÙÈ
-    ÆÉÚÉÞÅÓËÉÈ ÚÁÐÉÓÅÊ Ó ÂÌÏÞÎÙÍÉ É offset ÚÎÁÞÅÎÉÑÍÉ. T<SMALL>ID</SMALL>
-    ÉÚÍÅÎÑÅÔÓÑ ÐÏÓÌÅ ÔÏÇÏ ËÁË ÚÁÐÉÓÉ ÂÙÌÉ ÉÚÍÅÎÅÎÙ ÉÌÉ ÐÅÒÅÇÒÕÖÅÎÙ.
-    <P>T<SMALL>ID</SMALL> ÉÓÐÏÌØÚÕÅÔÓÑ ÉÎÄÅËÓÎÙÍÉ ÚÁÐÉÓÑÍÉ × ËÁÞÅÓÔ×Å
-    ÕËÁÚÁÔÅÌÑ ÎÁ ÆÉÚÉÞÅÓËÉÅ ÚÁÐÉÓÉ.</P>
-
-    <H4><A name="4.17">4.17</A>) þÔÏ ÏÚÎÁÞÁÀÔ ÎÅËÏÔÏÒÙÅ ÔÅÒÍÉÎÙ ÉÓÐÏÌØÚÕÅÍÙÅ ×
-    PostgreSQL?</H4>
-
-    <P>îÅËÏÔÏÒÙÊ ÉÓÈÏÄÎÙÊ ËÏÄ É ÓÔÁÒÁÑ ÄÏËÕÍÅÎÔÁÃÉÑ ÉÓÐÏÌØÚÕÀÔ
-    ÏÂÝÅÕÐÏÔÒÅÂÉÔÅÌØÎÙÅ ÔÅÒÍÉÎÙ. ÷ÏÔ ÎÅËÏÔÏÒÙÅ ÉÚ ÎÉÈ:</P>
-
-    <UL>
-      <LI>table, relation, class</LI>
-
-      <LI>row, record, tuple</LI>
-
-      <LI>column, field, attribute</LI>
-
-      <LI>retrieve, select</LI>
-
-      <LI>replace, update</LI>
-
-      <LI>append, insert</LI>
-
-      <LI><SMALL>OID</SMALL>, serial value</LI>
-
-      <LI>portal, cursor</LI>
-
-      <LI>range variable, table name, table alias</LI>
-    </UL>
-
-    <P>óÐÉÓÏË ÏÂÝÉÈ ÔÅÒÍÉÎÏ× ÐÏ ÂÁÚÁÍ ÄÁÎÎÙÈ ÍÏÖÎÏ ÎÁÊÔÉ ÎÁ <A href=
-    "http://www.comptechnews.com/~reaster/dbdesign.html">http://www.comptechnews.com/~reaster/dbdesign.html</A></P>
-
-    <H4><A name="4.18">4.18</A>) ðÏÞÅÍÕ Ñ ÐÏÌÕÞÁÀ ÏÛÉÂËÕ <I>"ERROR: Memory
-    exhausted in AllocSetAlloc()"</I>?</H4>
-
-    <P>åÓÌÉ Õ ×ÁÓ ×ÅÒÓÉÑ ÎÉÖÅ 7.1, ÔÏ ÏÂÎÏ×ÌÅÎÉÅ ×ÅÒÓÉÉ ÍÏÖÅÔ ÒÅÛÉÔØ ÜÔÕ
-    ÐÒÏÂÌÅÍÕ. ôÁËÖÅ ×ÏÚÍÏÖÎÏ, ÞÔÏ Õ ×ÁÓ ÚÁËÏÎÞÉÌÁÓØ ×ÉÒÔÕÁÌØÎÁÑ ÐÁÍÑÔØ
-    ÉÌÉ ÞÔÏ ×ÁÛÅ ÑÄÒÏ ÉÍÅÅÔ ÍÁÌÅÎØËÉÊ ÌÉÍÉÔ ÎÁ ÏÐÒÅÄÅÌÅÎÎÙÅ ÒÅÓÕÒÓÙ.
-    ðÏÐÙÔÁÊÔÅÓØ ÐÅÒÅÄ ÚÁÐÕÓËÏÍ <I>postmaster</I> ×ÙÐÏÌÎÉÔØ ÓÌÅÄÕÀÝÉÅ
-    ËÏÍÁÎÄÙ:</P>
-<PRE>
-    ulimit -d 262144
-    limit datasize 256m
-</PRE>
-    ÷ ÚÁ×ÉÓÉÍÏÓÔÉ ÏÔ ËÏÍÁÎÄÎÏÇÏ ÉÎÔÅÒÐÒÅÔÁÔÏÒÁ shell, ÔÏÌØËÏ ÏÄÎÁ ÉÚ ÄÁÎÎÙÈ
-    ËÏÍÁÎÄ ×ÙÐÏÌÎÉÔÓÑ ÕÓÐÅÛÎÏ, ÎÏ ÏÎÁ ÐÏÚ×ÏÌÉÔ ×ÁÍ ÕÓÔÁÎÏ×ÉÔØ ÂÏÌØÛÉÊ
-    ÓÅÇÍÅÎÔ ÄÁÎÎÙÈ ÐÒÏÃÅÓÓÁ É ×ÏÚÍÏÖÎÏ ÒÅÛÉÔ ÐÒÏÂÌÅÍÕ. üÔÁ ËÏÍÁÎÄÁ
-    ÉÚÍÅÎÑÅÔ ÐÁÒÁÍÅÔÒÙ ÔÅËÕÝÅÇÏ ÐÒÏÃÅÓÓÁ É ×ÓÅÈ ÅÇÏ ÐÏÔÏÍËÏ×, ÓÏÚÄÁÎÎÙÈ
-    ÐÏÓÌŠţ ÚÁÐÕÓËÁ. åÓÌÉ Õ ×ÁÓ ×ÏÚÎÉËÌÁ ÐÒÏÂÌÅÍÁ Ó <SMALL>SQL</SMALL>
-    ËÌÉÅÎÔÏÍ, ÐÏÔÏÍÕ ÞÔÏ backend ×ÏÚ×ÒÁÝÁÅÔ ÓÌÉÛËÏÍ ÂÏÌØÛÏÊ ÏÂßÅÍ ÄÁÎÎÙÈ,
-    ÐÏÐÙÔÁÊÔÅÓØ ×ÙÐÏÌÎÉÔØ ÜÔÕ ËÏÍÁÎÄÕ ÐÅÒÅÄ ÚÁÐÕÓËÏÍ ËÌÉÅÎÔÁ.
-
-    <H4><A name="4.19">4.19</A>) ëÁË ÍÎÅ ÕÚÎÁÔØ, ËÁËÁÑ ×ÅÒÓÉÑ PostgreSQL
-    ÚÁÐÕÝÅÎÁ?</H4>
-
-    <P>éÚ <I>psql</I>, ÎÁÂÅÒÉÔÅ <CODE>select version();</CODE></P>
-
-    <H4><A name="4.20">4.20</A>) ðÏÞÅÍÕ ÐÒÉ ÒÁÂÏÔÅ Ó ÍÏÉÍ ÂÏÌØÛÉÍ ÏÂßÅËÔÏÍ
-     Ñ ÐÏÌÕÞÁÀ ÏÛÉÂËÕ <I>"invalid large obj descriptor"</I>?</H4>
-
-    <P>÷ÁÍ ÎÕÖÎÏ ÐÒÉ ÉÓÐÏÌØÚÏ×ÁÎÉÉ ÂÏÌØÛÏÇÏ ÏÂßÅËÔÁ ÐÏÍÅÓÔÉÔØ × ÎÁÞÁÌÅ
-    <CODE>BEGIN WORK</CODE> É × ËÏÎÃÅ <CODE>COMMIT</CODE>, Á ×ÎÕÔÒÉ
-    ÐÏÌÕÞÉ×ÛÅÇÏÓÑ ÂÌÏËÁ <CODE>lo_open</CODE> ... <CODE>lo_close.</CODE></P>
-
-    <P>÷ ÎÁÓÔÏÑÝÉÊ ÍÏÍÅÎÔ PostgreSQL ÔÒÅÂÕÅÔ, ÞÔÏÂÙ ÐÒÉ ÚÁËÒÙÔÉÉ ÂÏÌØÛÏÇÏ
-    ÏÂßÅËÔÁ ÐÒÏÉÓÈÏÄÉÌÏ ×ÙÐÏÌÎÅÎÉÅ ÔÒÁÎÚÁËÃÉÉ. ôÁËÉÍ ÏÂÒÁÚÏÍ, ÐÅÒ×ÁÑ ÖÅ
-    ÐÏÐÙÔËÁ ÓÄÅÌÁÔØ ÞÔÏ-ÌÉÂÏ Ó ÂÏÌØÛÉÍ ÏÂßÅËÔÏÍ, ÎÅ ÓÏÂÌÀÄÁÑ ÄÁÎÎÏÇÏ ÐÒÁ×ÉÌÁ
-    ÐÒÉ×ÅÄÅÔ Ë ÓÏÏÂÝÅÎÉÀ <I>invalid large obj descriptor</I>, ÔÁË ËÁË
-    ËÏÄ ×ÙÐÏÌÎÑÀÝÉÊ ÒÁÂÏÔÕ ÎÁÄ ÂÏÌØÛÉÍ ÏÂßÅËÔÏÍ (ÐÏ ËÒÁÊÎÅÊ ÍÅÒÅ ×
-    ÎÁÓÔÏÑÝÉÊ ÍÏÍÅÎÔ) ÂÕÄÅÔ ÇÅÎÅÒÉÒÏ×ÁÔØ ÓÏÏÂÝÅÎÉÅ Ï ÏÛÉÂËÅ ÅÓÌÉ ×Ù ÎÅ
-    ÉÓÐÏÌØÚÕÅÔÅ ÔÒÁÎÚÁËÃÉÀ.</P>
-
-    <P>åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ ÔÁËÏÊ ÉÎÔÅÒÆÅÊÓ ËÌÉÅÎÔÁ ËÁË <SMALL>ODBC</SMALL>,
-    ×ÁÍ ×ÏÚÍÏÖÎÏ ÐÏÎÁÄÏÂÉÔÓÑ ÕÓÔÁÎÏ×ÉÔØ <CODE>auto-commit off.</CODE></P>
-
-    <H4><A name="4.21">4.21</A>) ëÁË ÍÎÅ ÓÏÚÄÁÔØ ËÏÌÏÎËÕ ËÏÔÏÒÁÑ ÐÏ ÕÍÏÌÞÁÎÉÀ
-     ÂÕÄÅÔ ÓÏÄÅÒÖÁÔØ ÔÅËÕÝÅÅ ×ÒÅÍÑ?</H4>
-
-    <P>éÓÐÏÌØÚÕÊÔÅ <I>CURRENT_TIMESTAMP</I>:</P>
-<PRE>
-<CODE>CREATE TABLE test (x int, modtime timestamp DEFAULT CURRENT_TIMESTAMP );
-</CODE>
-</PRE>
-
-    <H4><A name="4.22">4.22</A>) ðÏÞÅÍÕ ÍÏÉ ÐÏÄÚÁÐÒÏÓÙ, ÉÓÐÏÌØÚÕÀÝÉÅ
-    <CODE><SMALL>IN</SMALL></CODE> ÔÁË ÍÅÄÌÅÎÎÏ ÒÁÂÏÔÁÅÀÔ?</H4>
-
-    <P>÷ ÎÁÓÔÏÑÝÉÊ ÍÏÍÅÎÔ, ÍÙ Ó×ÑÚÙ×ÁÅÍ ÐÏÚÁÐÒÏÓÙ ÄÌÑ ×ÎÅÛÎÉÈ ÚÁÐÒÏÓÏ×
-    ÞÅÒÅÚ ÐÏÓÌÅÄÏ×ÁÔÅÌØÎÙÊ ÐÅÒÅÂÏÒ ÒÅÚÕÌØÔÁÔÁ ÐÏÄÚÁÐÒÏÓÁ ÄÌÑ ËÁÖÄÏÊ
-    ÚÁÐÉÓÉ ×ÎÅÛÎÅÇÏ ÚÁÐÒÏÓÁ. ðÏÐÒÏÂÕÊÔÅ ÚÁÍÅÎÉÔØ <CODE>IN</CODE> ÎÁ
-    <CODE>EXISTS</CODE>:</P>
-<PRE>
-<CODE>SELECT *
-    FROM tab
-    WHERE col1 IN (SELECT col2 FROM TAB2)
-</CODE>
-</PRE>
-    ÎÁ: 
-<PRE>
-<CODE>SELECT *
-    FROM tab
-    WHERE EXISTS (SELECT col2 FROM TAB2 WHERE col1 = col2)
-</CODE>
-</PRE>
-    íÙ ÎÁÄÅÅÍÓÑ ÕÂÒÁÔØ ÜÔÏ ÏÇÒÁÎÉÞÅÎÉÅ × ÂÕÄÕÝÅÍ ×ÙÐÕÓËÅ.
-
-    <H4><A name="4.23">4.23</A>) ëÁË ÍÎÅ ×ÙÐÏÌÎÉÔØ ×ÎÅÛÎÅÅ Ó×ÑÚÙ×ÁÎÉÅ?</H4>
-
-    <P>PostgreSQL ÎÁÞÉÎÁÑ Ó ×ÅÒÓÉÉ 7.1 ÐÏÄÄÅÒÖÉ×ÁÅÔ ×ÎÅÛÎÅÅ Ó×ÑÚÙ×ÁÎÉÅ,
-    ÉÓÐÏÌØÚÕÑ ÓÔÁÎÄÁÒÔÎÙÊ ÓÉÎÔÁËÓÉÓ SQL. ÷ÏÔ Ä×Á ÐÒÉÍÅÒÁ:</P>
-<PRE>
-    SELECT *
-    FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
-</PRE>
-    or 
-<PRE>
-    SELECT *
-    FROM t1 LEFT OUTER JOIN t2 USING (col);
-</PRE>
-
-    <P>üÔÏ ÉÄÅÎÔÉÞÎÙÅ ÚÁÐÒÏÓÙ Ó×ÑÚÙ×ÁÎÉÑ t1.col É t2.col, ÔÁËÖÅ ×ÏÚ×ÒÁÝÁÀÔ
-    ÌÀÂÙÅ ÎÅÓ×ÑÚÁÎÎÙÅ ÚÁÐÉÓÉ × t1 (ËÏÔÏÒÙÅ ÎÅ ÓÏ×ÐÁÄÁÀÔ Ó t2). 
-    <SMALL>RIGHT</SMALL> Ó×ÑÚÙ×ÁÎÉÅ ÄÏÌÖÎÏ ÄÏÂÁ×ÉÔØ ÎÅÓ×ÑÚÁÎÎÙÅ ÚÁÐÉÓÉ
-    t2. <SMALL>FULL</SMALL> Ó×ÑÚÙ×ÁÎÉÅ ÄÏÌÖÎÏ ×ÏÚ×ÒÁÔÉÔØ ÓÏ×ÐÁ×ÛÉÅ
-    ÚÁÐÉÓÉ ÐÌÀÓ ×ÓÅ ÎÅÓ×ÑÚÁÎÎÙÅ ÚÁÐÉÓÉ ÉÚ t1 É t2. óÌÏ×Ï <SMALL>OUTER</SMALL>
-    Ñ×ÌÑÅÔÓÑ ÎÅÏÂÑÚÁÔÅÌØÎÙÍ É ÎÁÚÎÁÞÁÅÔÓÑ × <SMALL>LEFT</SMALL>,
-    <SMALL>RIGHT</SMALL> É <SMALL>FULL</SMALL> Ó×ÑÚÙ×ÁÎÉÑÈ. ïÂÙÞÎÙÅ
-    Ó×ÑÚÙ×ÁÎÉÑ ÎÁÚÙ×ÁÀÔÓÑ <SMALL>INNER</SMALL> Ó×ÑÚÙ×ÁÎÉÑ.</P>
-
-    <P>÷ ÐÒÅÄÙÄÕÝÉÈ ×ÅÒÓÉÑÈ, ×ÎÅÛÎÉÅ Ó×ÑÚÙ×ÁÎÉÑ ÍÏÇÌÉ ÂÙÔØ ÜÍÕÌÉÒÏ×ÁÎÙ
-    ÉÓÐÏÌØÚÕÑ <SMALL>UNION</SMALL> É <SMALL>NOT IN</SMALL>. îÁÐÒÉÍÅÒ,
-    ËÏÇÄÁ ÐÒÏÉÓÈÏÄÉÔ Ó×ÑÚÙ×ÁÎÉÅ <I>tab1</I> É <I>tab2</I>, ÓÌÅÄÕÀÝÉÊ
-    ÚÁÐÒÏÓ ×ÙÐÏÌÎÑÅÔ <I>×ÎÅÛÎÅÅ</I> Ó×ÑÚÙ×ÁÎÉÅ Ä×ÕÈ ÔÁÂÌÉÃ:<BR>
-    <BR>
-    </P>
-<PRE>
-    SELECT tab1.col1, tab2.col2
-    FROM tab1, tab2
-    WHERE tab1.col1 = tab2.col1
-    UNION ALL
-    SELECT tab1.col1, NULL
-    FROM tab1
-    WHERE tab1.col1 NOT IN (SELECT tab2.col1 FROM tab2)
-    ORDER BY col1
-</PRE>
-
-    <H4><A name="4.24">4.24</A>) ëÁË ×ÙÐÏÌÎÑÔØ ÚÁÐÒÏÓÙ, ÉÓÐÏÌØÚÕÀÝÉÅ ÎÅÓËÏÌØËÏ
-     ÂÁÚ ÄÁÎÎÙÈ?</H4>
-
-    <P>îÅ ÓÕÝÅÓÔ×ÕÅÔ ÓÐÏÓÏÂÁ ÓÏÚÄÁÔØ ÚÁÐÒÏÓ Ë ÂÁÚÁÍ ÄÁÎÎÙÈ ÏÔÌÉÞÎÙÍ ÏÔ ÔÅËÕÝÅÊ.
-    ðÏÓËÏÌØËÕ PostgreSQL ÚÁÇÒÕÖÁÅÔ ÓÉÓÔÅÍÎÙÅ ËÁÔÁÌÏÇÉ ÓÐÅÃÉÆÉÞÎÙÅ ÄÌÑ ÂÁÚÙ
-    ÄÁÎÎÙÈ, ÎÅÐÏÎÑÔÎÏ ÄÁÖÅ, ËÁË ÄÏÌÖÅÎ ÓÅÂÑ ×ÅÓÔÉ ÔÁËÏÊ ÍÅÖÂÁÚÏ×ÙÊ ÚÁÐÒÏÓ.</P>
-
-    <P>òÁÚÕÍÅÅÔÓÑ, ËÌÉÅÎÔ ÍÏÖÅÔ ÏÄÎÏ×ÒÅÍÅÎÎÏ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ ÓÏÅÄÉÅÎÅÎÉÑ Ó
-    ÒÁÚÌÉÞÎÙÍÉ ÂÁÚÁÍÉ ÄÁÎÎÙÈ É ÔÁËÉÈ ÏÂÒÁÚÏÍ ÏÂßÅÄÉÎÑÔØ ÉÎÆÏÒÍÁÃÉÀ ÉÚ ÎÉÈ.</P>
-
-    <H4><A name="4.25">4.25</A>) ëÁË ÍÎÅ ×ÅÒÎÕÔØ ÉÚ ÆÕÎËÃÉÉ ÎÅÓËÏÌØËÏ ÚÁÐÉÓÅÊ?</H4>
-
-    <P>÷Ù ÍÏÖÅÔÅ ×ÏÚ×ÒÁÝÁÔØ ÉÚ ÆÕÎËÃÉÊ PL/pgSQL ÓÐÉÓËÉ ÒÅÚÕÌØÔÁÔÏ×, ÉÓÐÏÌØÚÕÑ
-    <i>refcursors</i>. óÍÏÔÒÉÔÅ <A
-     href="http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html">
-     http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html,</a>
-     ÓÅËÃÉÀ 23.7.3.3.</P>
-
-    <H4><A name="4.26">4.26</A>) ðÏÞÅÍÕ Ñ ÎÅ ÍÏÇÕ ÎÁÄÅÖÎÏ ÓÏÚÄÁ×ÁÔØ/ÕÄÁÌÑÔØ
-    ×ÒÅÍÅÎÎÙÅ ÔÁÂÌÉÃÙ × ÆÕÎËÃÉÑÈ PL/PgSQL?</H4>
-    PL/PgSQL ËÜÛÉÒÕÅÔ ÓÏÄÅÒÖÉÍÏÅ ÆÕÎËÃÉÉ É ÏÄÉÎ ÉÚ ÎÅÇÁÔÉ×ÎÙÈ ÜÆÆÅËÔÏ× ÜÔÏÇÏ
-    ÓÏÓÔÏÉÔ × ÔÏÍ, ÞÔÏ ÅÓÌÉ ÆÕÎËÃÉÑ PL/PgSQL ÏÂÒÁÝÁÅÔÓÑ Ë ×ÒÅÍÅÎÎÏÊ ÔÁÂÌÉÃÅ
-    É ÜÔÁ ÔÁÂÌÉÃÁ ÐÏÚÄÎÅÅ ÕÄÁÌÑÅÔÓÑ É ÐÅÒÅÓÏÚÄÁÅÔÓÑ, Á ÆÕÎËÃÉÑ ÚÁÔÅÍ ×ÙÚÙ×ÁÅÔÓÑ
-    ÓÎÏ×Á, ÔÏ ÅÅ ×ÙÚÏ× ÐÒÉ×ÅÄÅÔ Ë ÏÛÉÂËÅ, ÐÏÔÏÍÕ ÞÔÏ ÓËÜÛÉÒÏ×ÁÎÎÏÅ ÓÏÄÅÒÖÉÍÏÅ
-    ÆÕÎËÃÉÉ ÓÏÄÅÒÖÉÔ ÕËÁÚÁÔÅÌØ ÎÁ ÓÔÁÒÕÀ ×ÒÅÍÅÎÎÕÀ ÔÁÂÌÉÃÕ. þÔÏÂÙ ÒÅÛÉÔØ ÜÔÕ
-    ÐÒÏÂÌÅÍÕ, ÉÓÐÏÌØÚÕÊÔÅ <SMALL>EXECUTE</SMALL> ÄÌÑ ÄÏÓÔÕÐÁ Ë ×ÒÅÍÅÎÎÙÍ
-    ÔÁÂÌÉÃÁÍ × PL/PgSQL. éÓÐÏÌØÚÏ×ÁÎÉÅ ÜÔÏÇÏ ÏÐÅÒÁÔÏÒÁ ÚÁÓÔÁ×ÉÔ ÚÁÐÒÏÓ
-    ÐÅÒÅÇÅÎÅÒÉÒÏ×ÁÔØÓÑ ËÁÖÄÙÊ ÒÁÚ.
-    <HR>     
-
-    <H2 align="center">òÁÓÛÉÒÅÎÉÑ PostgreSQL</H2>
-
-    <H4><A name="5.1">5.1</A>) ñ ÎÁÐÉÓÁÌ ÆÕÎËÃÉÀ ÏÐÒÅÄÅÌÑÅÍÕÀ ÐÏÌØÚÏ×ÁÔÅÌÅÍ.
-    ëÏÇÄÁ Ñ ÚÁÐÕÓËÁÀ ÅÅ × <I>psql</I>, ÐÏÞÅÍÕ Ñ ÐÏÌÕÞÁÀ dump core?</H4>
-
-    <P>ðÒÏÂÌÅÍÁ ÍÏÖÅÔ ÚÁËÌÀÞÁÔØÓÑ × ÎÅÓËÏÌØËÉÈ ×ÅÝÁÈ. ðÏÐÙÔÁÊÔÅÓØ ÓÐÅÒ×Á
-    ÐÒÏÔÅÓÔÉÒÏ×ÁÔØ ×ÁÛÕ ÆÕÎËÃÉÀ × ÏÔÄÅÌØÎÏÊ ÓÁÍÏÓÔÏÑÔÅÌØÎÏÊ ÐÒÏÇÒÁÍÍÅ.</P>
-
-    <H4><A name="5.2">5.2</A>) ëÁË Ñ ÍÏÇÕ ×ÎÅÓÔÉ ÎÅËÏÔÏÒÙÅ ËÌÁÓÓÎÙÅ ÎÏ×ÙÅ
-     ÔÉÐÙ É ÆÕÎËÃÉÉ × PostgreSQL?</H4>
-
-    <P>ïÔÐÒÁ×ØÔÅ ×ÁÛÉ ÒÁÓÛÉÒÅÎÉÑ × ÓÐÉÓÏË ÒÁÓÓÙÌËÉ <I>pgsql-hackers</I>
-    É ÏÎÉ ÐÏ ×ÏÚÍÏÖÎÏÓÔÉ ÂÕÄÕÔ ÐÏÍÅÝÅÎÙ × ÐÏÄËÁÔÁÌÏÇ <I>contrib/</I>.</P>
-
-    <H4><A name="5.3">5.3</A>) ëÁË ÍÎÅ ÎÁÐÉÓÁÔØ C ÆÕÎËÃÉÀ, ×ÏÚ×ÒÁÝÁÀÝÕÀ
-    ÚÁÐÉÓØ?</H4>
-
-    <P>üÔÏ ÔÒÅÂÕÅÔ ÎÅËÏÅÇÏ ÛÁÍÁÎÓÔ×Á ÔÁË ËÁË Á×ÔÏÒÙ ÎÉËÏÇÄÁ ÎÅ ÐÒÏÂÏ×ÁÌÉ
-    ÄÅÌÁÔØ ÜÔÏ, ÈÏÔÑ × ÐÒÉÎÉÃÐÅ ÜÔÏ ×ÏÚÍÏÖÎÏ.</P>
-
-    <H4><A name="5.4">5.4</A>) ñ ÉÚÍÅÎÉÌ ÉÓÈÏÄÎÙÊ ÆÁÊÌ. ðÏÞÅÍÕ ÐÏÓÌÅ
-     ÐÅÒÅËÏÍÐÉÌÑÃÉÉ Ñ ÎÅ ×ÉÖÕ ÉÚÍÅÎÅÎÉÊ?</H4>
-
-    <P>æÁÊÌÙ <I>Makefile</I> ÎÅ ÉÍÅÀÔ ÐÒÁ×ÉÌØÎÙÈ ÚÁ×ÉÓÉÍÏÓÔÅÊ ÄÌÑ include
-    ÆÁÊÌÏ×. ÷Ù ÄÏÌÖÎÙ ×ÙÐÏÌÎÉÔØ <I>make clean</I> É ÚÁÔÅÍ <I>make</I>. 
-    åÓÌÉ ×Ù ÉÓÐÏÌØÚÕÅÔÅ <SMALL>GCC</SMALL> ×Ù ÍÏÖÅÔÅ ÉÓÐÏÌØÚÏ×ÁÔØ ÏÐÃÉÀ
-    <I>--enable-depend</I> × <I>configure</I> ÞÔÏÂÙ ÐÏÒÕÞÉÔØ ËÏÍÐÉÌÑÔÏÒÕ
-    Á×ÔÏÍÁÔÉÞÅÓËÉ ÏÔÓÌÅÖÉ×ÁÔØ ÚÁ×ÉÓÉÍÏÓÔÉ.</P>
-  </BODY>
-</HTML>
-
diff --git a/doc/src/Makefile b/doc/src/Makefile
deleted file mode 100644
index 955892404b7..00000000000
--- a/doc/src/Makefile
+++ /dev/null
@@ -1,44 +0,0 @@
-# Postgres documentation makefile
-# $Header: /cvsroot/pgsql/doc/src/Makefile,v 1.28 2001/11/25 22:17:27 petere Exp $
-
-subdir = doc/src
-top_builddir = ../..
-include $(top_builddir)/src/Makefile.global
-
-ZIPSUFFIX= gz
-
-BOOKS = admin developer reference programmer tutorial user  postgres
-
-TARGETS= $(BOOKS:%=%.tar.$(ZIPSUFFIX))
-
-.PRECIOUS:
-.PHONY: install all sources clean distclean
-
-install:
-	$(MAKE) all
-	(mv -f *.$(ZIPSUFFIX) ..)
-
-clean:
-	$(MAKE) -C sgml clean
-
-distclean:
-	$(MAKE) -C sgml distclean
-
-all: $(TARGETS)
-
-sources:
-	$(MAKE) sources.tar.$(ZIPSUFFIX)
-
-sources.tar:
-	$(TAR) -cf $@ sgml graphics
-
-# Build twice to resolve index entries
-$(addsuffix .tar, $(BOOKS)):
-	$(MAKE) -C sgml clean
-	$(MAKE) -C sgml $(basename $@).html
-	$(MAKE) -C sgml $(basename $@).html JADEFLAGS='-V html-manifest'
-	cd sgml && $(TAR) -cf ../$@ `cat HTML.manifest` `echo *.gif | grep -v '\*'` *.css
-
-man.tar:
-	$(MAKE) -C sgml man
-	$(TAR) -cf $@ -C sgml man1 man$(sqlmansect_dummy)
diff --git a/doc/src/graphics/catalogs.ag b/doc/src/graphics/catalogs.ag
deleted file mode 100644
index b4816d11a9a..00000000000
--- a/doc/src/graphics/catalogs.ag
+++ /dev/null
@@ -1,1220 +0,0 @@
-*BEGIN GRAPHICS VERSION=442/420 ENCODING=7BIT
-
-FONT
-"times"
-END FONT
-
-SESSION
- WIN_SIZE <9627 5760>
- VIEW <0 0 0 0 0 0>
- REZ <0 4000 4000 -456 5637>
-END SESSION
-
-SLIDE_INFO
- SLIDE_STYLE <0 0 1>
-END SLIDE_INFO
-PICTURE
-.POL AT (987,3296)
- THICKNESS 11
- PNTS (0,0)(401,0)(401,333)(494,333)
-.LINE AT (987,1795)
- PNTS (0,0)(494,0)
-.POL AT (1019,961)
- PNTS (369,0)(245,0)(245,2168)(0,2168)
-.POL AT (1141,294)
- PNTS (247,0)(0,0)(0,2793)
-.LINE AT (1019,3087)
- PNTS (0,0)(122,0)
-.POL AT (1019,1962)
- PNTS (493,0)(369,0)(369,1208)(0,1208)
-.LINE AT (895,1795)
- PNTS (0,0)(124,0)
-.POL AT (895,461)
- PNTS (493,0)(124,0)(124,1167)(0,1167)
-.LINE AT (2127,2295)
- PNTS (0,0)(122,0)
-.POL AT (2157,1837)
- PNTS (0,0)(462,0)(462,2292)(709,2292)
-.LINE AT (2619,3963)
- PNTS (0,0)(247,0)
-.LINE AT (2127,2129)
- PNTS (0,0)(830,0)
-.LINE AT (2127,3796)
- PNTS (0,0)(370,0)
-.LINE AT (2127,3963)
- PNTS (0,0)(370,0)
-.LINE AT (2127,4129)
- PNTS (0,0)(370,0)
-.LINE AT (2127,4296)
- PNTS (0,0)(370,0)
-.LINE AT (2127,4463)
- PNTS (0,0)(370,0)
-.LINE AT (2127,4629)
- PNTS (0,0)(370,0)
-.LINE AT (2127,4796)
- PNTS (0,0)(370,0)
-.LINE AT (2127,4963)
- PNTS (0,0)(370,0)
-.LINE AT (2127,5130)
- PNTS (0,0)(370,0)
-.LINE AT (2127,5296)
- PNTS (0,0)(370,0)
-.LINE AT (2497,2170)
- PNTS (0,0)(460,0)
-.LINE AT (2466,3504)
- PNTS (0,0)(62,84)
-.LINE AT (2280,2087)
- PNTS (0,0)(62,83)
-.LINE AT (2589,3504)
- PNTS (0,0)(61,84)
-.LINE AT (3605,5130)
- PNTS (0,0)(246,0)
-.LINE AT (3697,4171)
- PNTS (0,0)(61,83)
-.LINE AT (3820,4671)
- PNTS (0,0)(62,84)
-.LINE AT (2866,3963)
- PNTS (0,0)(123,0)
-.LINE AT (2866,4129)
- PNTS (0,0)(123,0)
-.POL AT (2957,503)
- PNTS (525,208)(0,208)(0,0)(525,0)(525,208)
-.POL AT (2957,711)
- PNTS (678,167)(0,167)(0,0)(678,0)(678,167)
-.LINE AT (2619,4296)
- PNTS (0,0)(247,0)
-.LINE AT (2866,4296)
- PNTS (0,0)(123,0)
-.LINE AT (2619,4129)
- PNTS (0,167)(0,0)
-.POL AT (2157,1753)
- PNTS (0,0)(709,0)(709,709)(832,709)
-.POL AT (3605,794)
- PNTS (30,0)(123,0)(123,2001)(0,2001)
-.POL AT (2157,3296)
- PNTS (0,333)(216,333)(216,0)(2187,0)
-.POL AT (2157,294)
- PNTS (0,3294)(92,3294)(92,2876)(1941,2876)(1941,0)(2187,0)
-.POL AT (3635,628)
- PNTS (0,2960)(585,2960)(585,0)(709,0)
-.LINE AT (3943,1170)
- PNTS (0,0)(62,83)
-.POL AT (4959,461)
- PNTS (0,0)(123,0)(123,1459)(30,1459)
-.POL AT (4959,1962)
- PNTS (30,0)(123,0)(123,1500)(0,1500)
-.POL AT (3635,794)
- PNTS (0,1293)(338,1293)(338,0)(709,0)
-.POL AT (3635,2129)
- PNTS (0,0)(338,0)(338,1667)(709,1667)
-.POL AT (2957,2212)
- PNTS (44,0)(23,8)(8,29)(0,58)
-.LINE AT (2957,2270)
- PNTS (0,0)(0,550)
-.POL AT (2963,2996)
- PNTS (0,0)(8,30)(23,51)(44,59)
-.POL AT (2998,3062)
- PNTS (0,0)(591,0)
-.POL AT (3585,3004)
- PNTS (0,59)(22,51)(38,30)(43,0)
-.LINE AT (3635,2270)
- PNTS (0,550)(0,0)
-.POL AT (3592,2212)
- PNTS (43,58)(38,29)(22,8)(0,0)
-.LINE AT (3001,2212)
- PNTS (591,0)(0,0)
-.POL AT (248,4671)
- PNTS (647,209)(0,209)(0,0)(647,0)(647,209)
-.POL AT (248,5505)
- PNTS (678,208)(0,208)(0,0)(678,0)(678,208)
-.POL AT (248,4880)
- PNTS (44,0)(23,8)(7,28)(0,58)
-.LINE AT (248,4938)
- PNTS (0,0)(0,50)
-.POL AT (248,4988)
- PNTS (0,0)(7,30)(23,50)(44,59)
-.LINE AT (292,5047)
- PNTS (0,0)(591,0)
-.POL AT (883,4988)
- PNTS (0,59)(22,50)(37,30)(43,0)
-.LINE AT (926,4938)
- PNTS (0,50)(0,0)
-.POL AT (883,4880)
- PNTS (43,58)(37,28)(22,8)(0,0)
-.LINE AT (292,4880)
- PNTS (591,0)(0,0)
-.POL AT (248,5713)
- PNTS (678,167)(0,167)(0,0)(678,0)(678,167)
-.POL AT (895,4963)
- PNTS (0,0)(124,0)(124,834)(31,834)
-.POL AT (248,5880)
- PNTS (678,334)(0,334)(0,0)(678,0)(678,334)
-.POL AT (248,6214)
- PNTS (678,166)(0,166)(0,0)(678,0)(678,166)
-.POL AT (248,5880)
- PNTS (44,0)(23,8)(7,29)(0,58)
-.LINE AT (248,5938)
- PNTS (0,0)(0,384)
-.POL AT (248,6322)
- PNTS (0,0)(7,29)(23,50)(44,58)
-.LINE AT (292,6380)
- PNTS (0,0)(591,0)
-.POL AT (883,6322)
- PNTS (0,58)(22,50)(37,29)(43,0)
-.LINE AT (926,5938)
- PNTS (0,384)(0,0)
-.POL AT (883,5880)
- PNTS (43,58)(37,29)(22,8)(0,0)
-.LINE AT (292,5880)
- PNTS (591,0)(0,0)
-.POL AT (773,6547)
- PNTS (43,0)(20,8)(5,29)(0,58)
-.LINE AT (773,6605)
- PNTS (0,0)(0,9)
-.POL AT (773,6614)
- PNTS (0,0)(5,29)(20,50)(43,58)
-.LINE AT (816,6672)
- PNTS (0,0)(36,0)
-.POL AT (852,6614)
- PNTS (0,58)(22,50)(37,29)(43,0)
-.LINE AT (895,6605)
- PNTS (0,9)(0,0)
-.POL AT (852,6547)
- PNTS (43,58)(37,29)(22,8)(0,0)
-.LINE AT (816,6547)
- PNTS (36,0)(0,0)
-.LINE AT (2497,2170)
- PNTS (0,3126)(0,0)
-.POL AT (2003,628)
- PNTS (0,0)(370,0)(370,1459)(954,1459)
-.POL AT (2157,1795)
- PNTS (0,0)(586,0)(586,834)(832,834)
-.LINE AT (1264,6005)
- PNTS (0,0)(248,0)
-.LINE AT (1264,6172)
- PNTS (0,0)(248,0)
-.LINE AT (2127,2462)
- PNTS (0,0)(122,0)
-.LINE AT (2127,2629)
- PNTS (0,0)(122,0)
-.LINE AT (2249,2295)
- PNTS (0,0)(0,334)
-.LINE AT (2249,2129)
- PNTS (0,0)(0,166)
-.LINE AT (3605,4963)
- PNTS (0,0)(123,0)
-.LINE AT (3605,4796)
- PNTS (0,0)(123,0)
-.POL AT (2957,3712)
- PNTS (44,0)(23,8)(8,29)(0,59)
-.LINE AT (2957,3771)
- PNTS (0,0)(0,1717)
-.POL AT (2957,5488)
- PNTS (0,0)(8,29)(23,51)(44,58)
-.LINE AT (3001,5546)
- PNTS (0,0)(591,0)
-.POL AT (3592,5488)
- PNTS (0,58)(22,51)(38,29)(43,0)
-.LINE AT (3635,3771)
- PNTS (0,1717)(0,0)
-.POL AT (3592,3712)
- PNTS (43,59)(38,29)(22,8)(0,0)
-.LINE AT (3001,3712)
- PNTS (591,0)(0,0)
-.LINE AT (3728,4796)
- PNTS (0,0)(0,167)
-.LINE AT (3605,4629)
- PNTS (0,0)(123,0)
-.LINE AT (3605,4463)
- PNTS (0,0)(123,0)
-.POL AT (3635,3629)
- PNTS (0,0)(93,0)(93,1167)
-.LINE AT (3605,5296)
- PNTS (0,0)(246,0)
-.LINE AT (3605,5463)
- PNTS (0,0)(246,0)
-.LINE AT (3851,5296)
- PNTS (0,167)(0,0)
-.POL AT (3635,2170)
- PNTS (0,0)(216,0)(216,2960)
-.LINE AT (3851,5130)
- PNTS (0,0)(0,166)
-.POL AT (218,1170)
- PNTS (523,208)(0,208)(0,0)(523,0)(523,208)
-.POL AT (218,1378)
- PNTS (44,0)(21,8)(6,29)(0,58)
-.LINE AT (218,1436)
- PNTS (0,0)(0,384)
-.POL AT (218,1820)
- PNTS (0,0)(6,29)(21,50)(44,58)
-.LINE AT (262,1878)
- PNTS (0,0)(590,0)
-.POL AT (852,1820)
- PNTS (0,58)(22,50)(37,29)(43,0)
-.LINE AT (895,1436)
- PNTS (0,384)(0,0)
-.POL AT (852,1378)
- PNTS (43,58)(37,29)(22,8)(0,0)
-.LINE AT (262,1378)
- PNTS (590,0)(0,0)
-.LINE AT (218,1712)
- PNTS (0,0)(677,0)
-.LINE AT (865,3296)
- PNTS (0,0)(122,0)
-.LINE AT (895,3170)
- PNTS (0,0)(124,0)
-.LINE AT (895,3129)
- PNTS (0,0)(124,0)
-.LINE AT (895,3087)
- PNTS (0,0)(124,0)
-.POL AT (218,3046)
- PNTS (677,166)(0,166)(0,0)(677,0)(677,166)
-.POL AT (218,2837)
- PNTS (523,209)(0,209)(0,0)(523,0)(523,209)
-.POL AT (218,3212)
- PNTS (677,167)(0,167)(0,0)(677,0)(677,167)
-.POL AT (1481,1503)
- PNTS (522,209)(0,209)(0,0)(522,0)(522,209)
-.POL AT (1481,1712)
- PNTS (676,166)(0,166)(0,0)(676,0)(676,166)
-.POL AT (1481,1878)
- PNTS (676,834)(0,834)(0,0)(676,0)(676,834)
-.POL AT (1357,3)
- PNTS (524,208)(0,208)(0,0)(524,0)(524,208)
-.POL AT (1357,211)
- PNTS (43,0)(22,8)(5,29)(0,58)
-.LINE AT (1357,269)
- PNTS (0,0)(0,717)
-.POL AT (1357,986)
- PNTS (0,0)(5,30)(22,51)(43,59)
-.LINE AT (1400,1045)
- PNTS (0,0)(592,0)
-.POL AT (1992,986)
- PNTS (0,59)(20,51)(37,30)(43,0)
-.LINE AT (2035,269)
- PNTS (0,717)(0,0)
-.POL AT (1992,211)
- PNTS (43,58)(37,29)(20,8)(0,0)
-.LINE AT (1400,211)
- PNTS (592,0)(0,0)
-.LINE AT (1357,878)
- PNTS (0,0)(678,0)
-.POL AT (4312,3)
- PNTS (524,208)(0,208)(0,0)(524,0)(524,208)
-.POL AT (4312,211)
- PNTS (44,0)(22,8)(7,29)(0,58)
-.LINE AT (4309,218)
- PNTS (0,0)(0,691)
-.POL AT (4309,909)
- PNTS (0,0)(7,30)(22,51)(44,59)
-.LINE AT (4353,968)
- PNTS (0,0)(591,0)
-.POL AT (4944,909)
- PNTS (0,59)(22,51)(37,30)(42,0)
-.LINE AT (4986,259)
- PNTS (0,650)(0,0)
-.POL AT (4947,211)
- PNTS (42,58)(37,29)(22,8)(0,0)
-.LINE AT (4356,211)
- PNTS (591,0)(0,0)
-.LINE AT (4312,711)
- PNTS (0,0)(677,0)
-.POL AT (4312,1670)
- PNTS (524,208)(0,208)(0,0)(524,0)(524,208)
-.POL AT (4312,1878)
- PNTS (677,167)(0,167)(0,0)(677,0)(677,167)
-.POL AT (2957,1837)
- PNTS (525,208)(0,208)(0,0)(525,0)(525,208)
-.POL AT (2957,2045)
- PNTS (678,167)(0,167)(0,0)(678,0)(678,167)
-.POL AT (2957,2212)
- PNTS (678,854)(0,854)(0,0)(678,0)(678,854)
-.LINE AT (2957,2712)
- PNTS (0,0)(678,0)
-.POL AT (4312,3004)
- PNTS (524,208)(0,208)(0,0)(524,0)(524,208)
-.POL AT (4312,3212)
- PNTS (44,0)(22,8)(7,29)(0,59)
-.LINE AT (4312,3271)
- PNTS (0,0)(0,550)
-.POL AT (4312,3821)
- PNTS (0,0)(7,29)(22,50)(44,58)
-.LINE AT (4356,3879)
- PNTS (0,0)(591,0)
-.POL AT (4947,3821)
- PNTS (0,58)(22,50)(37,29)(42,0)
-.LINE AT (4989,3271)
- PNTS (0,550)(0,0)
-.POL AT (4947,3212)
- PNTS (42,59)(37,29)(22,8)(0,0)
-.LINE AT (4356,3212)
- PNTS (591,0)(0,0)
-.LINE AT (4312,3712)
- PNTS (0,0)(677,0)
-.POL AT (2957,3337)
- PNTS (525,209)(0,209)(0,0)(525,0)(525,209)
-.POL AT (2957,3546)
- PNTS (678,166)(0,166)(0,0)(678,0)(678,166)
-.POL AT (2957,3712)
- PNTS (678,667)(0,667)(0,0)(678,0)(678,667)
-.POL AT (2957,4379)
- PNTS (678,1167)(0,1167)(0,0)(678,0)(678,1167)
-.POL AT (1481,3546)
- PNTS (676,166)(0,166)(0,0)(676,0)(676,166)
-.POL AT (1481,3337)
- PNTS (522,209)(0,209)(0,0)(522,0)(522,209)
-.POL AT (1481,3712)
- PNTS (676,2130)(0,2130)(0,0)(676,0)(676,2130)
-.POL AT (1141,6339)
- PNTS (0,166)(4,87)(4,35)(0,0)
-.POL AT (1080,6172)
- PNTS (61,167)(48,111)(25,49)(0,0)
-.POL AT (926,6047)
- PNTS (154,125)(124,91)(76,52)(0,0)
-.POL AT (926,6047)
- PNTS (39,44)(0,0)(50,14)
-.TXT AT (3426,2635)
- BACKFILL <1 0 5 1000 0 0 0>
- VER_JUST BASELINE MARGINS <0 0 0 0> FLD_XYSCALE <7432 10000>
- TXTXYOFF <-6 66>
- T_PNTS (0,66)(0,0)(73,0)(73,82)(0,82)(0,66)(73,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "[8]"
-.TXT AT (1641,467)
- SIZE 180000 FLD_XYSCALE <7330 10000>
- T_PNTS (0,66)(0,0)(73,0)(73,82)(0,82)(0,66)(73,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "[8]"
-.TXT AT (527,5302)
- SIZE 180000 FLD_XYSCALE <7339 10000>
- TXTXYOFF <-1 66>
- T_PNTS (0,66)(0,0)(381,0)(381,68)(0,68)(0,66)(381,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "REFERS-TO"
-.TXT AT (281,6303)
- SIZE 180000 FLD_XYSCALE <7346 10000>
- T_PNTS (0,66)(0,0)(234,0)(234,88)(0,88)(0,66)(234,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "non-key"
-.TXT AT (1334,3635)
- SIZE 180000 FLD_XYSCALE <7172 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(21,0)(21,67)(0,67)(0,66)(21,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.POL AT (157,1462)
- BACKFILL <1 0 0 0 0 0 0>
- SIZE 180000 MARGINS <125 125 250 62>
- PNTS (91,0)(0,0)(0,1667)(61,1667)
-.TXT AT (928,3385)
- BACKFILL <1 0 5 1000 0 0 0>
- MARGINS <0 0 0 0> FLD_XYSCALE <7277 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(104,0)(104,68)(0,68)(0,66)(104,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (958,6969)
- SIZE 180000 FLD_XYSCALE <7338 10000>
- TXTXYOFF <-1 66>
- T_PNTS (0,66)(0,0)(1617,0)(1617,88)(0,88)(0,66)(1617,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "identified by the non-oid primary key in other contexts)."
-.TXT AT (103,3134)
- SIZE 180000 FLD_XYSCALE <7172 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(21,0)(21,67)(0,67)(0,66)(21,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (11,1384)
- SIZE 180000 FLD_XYSCALE <7325 10000>
- T_PNTS (0,66)(0,0)(135,0)(135,68)(0,68)(0,66)(135,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "13:N"
-.TXT AT (1427,1717)
- SIZE 180000 FLD_XYSCALE <7186 10000>
- T_PNTS (0,66)(0,0)(21,0)(21,67)(0,67)(0,66)(21,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (928,1717)
- SIZE 180000 FLD_XYSCALE <7277 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(104,0)(104,68)(0,68)(0,66)(104,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (934,1551)
- SIZE 180000 FLD_XYSCALE <7565 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(22,0)(22,67)(0,67)(0,66)(22,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (1205,550)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (1088,2968)
- SIZE 180000 FLD_XYSCALE <7380 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(93,0)(93,67)(0,67)(0,66)(93,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "111"
-.TXT AT (1205,884)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (1205,217)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (2198,3468)
- SIZE 180000 FLD_XYSCALE <7142 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(55,0)(55,67)(0,67)(0,66)(55,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "11"
-.TXT AT (2192,2718)
- SIZE 180000 FLD_XYSCALE <7417 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(106,0)(106,68)(0,68)(0,66)(106,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (2905,2009)
- SIZE 180000 FLD_XYSCALE <7565 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(22,0)(22,67)(0,67)(0,66)(22,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (2806,2718)
- SIZE 180000 FLD_XYSCALE <7417 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(106,0)(106,68)(0,68)(0,66)(106,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (2806,2551)
- SIZE 180000 FLD_XYSCALE <7417 10000>
- T_PNTS (0,66)(0,0)(106,0)(106,68)(0,68)(0,66)(106,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (2197,1676)
- SIZE 180000 FLD_XYSCALE <6831 10000>
- TXTXYOFF <-7 66>
- T_PNTS (0,66)(0,0)(20,0)(20,67)(0,67)(0,66)(20,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (3668,2884)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (3674,717)
- SIZE 180000 FLD_XYSCALE <7528 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(22,0)(22,67)(0,67)(0,66)(22,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (2437,5386)
- SIZE 180000 FLD_XYSCALE <7277 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(104,0)(104,68)(0,68)(0,66)(104,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (2905,2259)
- SIZE 180000 FLD_XYSCALE <7565 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(22,0)(22,67)(0,67)(0,66)(22,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (2067,550)
- SIZE 180000 FLD_XYSCALE <7417 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(106,0)(106,68)(0,68)(0,66)(106,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (2688,1926)
- SIZE 180000 FLD_XYSCALE <7172 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(21,0)(21,67)(0,67)(0,66)(21,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (2192,1926)
- SIZE 180000 FLD_XYSCALE <7432 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(83,0)(83,68)(0,68)(0,66)(83,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:1"
-.TXT AT (1544,5969)
- SIZE 180000 FLD_XYSCALE <7338 10000>
- T_PNTS (0,66)(0,0)(233,0)(233,88)(0,88)(0,66)(233,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "optional"
-.TXT AT (1543,6136)
- SIZE 180000 FLD_XYSCALE <7359 10000>
- TXTXYOFF <-1 66>
- T_PNTS (0,66)(0,0)(306,0)(306,88)(0,88)(0,66)(306,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "mandatory"
-.TXT AT (2406,1426)
- SIZE 180000 FLD_XYSCALE <7344 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(83,0)(83,68)(0,68)(0,66)(83,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:1"
-.TXT AT (4161,217)
- SIZE 180000 FLD_XYSCALE <7417 10000>
- T_PNTS (0,66)(0,0)(106,0)(106,68)(0,68)(0,66)(106,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (4161,550)
- SIZE 180000 FLD_XYSCALE <7417 10000>
- T_PNTS (0,66)(0,0)(106,0)(106,68)(0,68)(0,66)(106,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (3674,3510)
- SIZE 180000 FLD_XYSCALE <7528 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(22,0)(22,67)(0,67)(0,66)(22,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (3674,3718)
- SIZE 180000 FLD_XYSCALE <7528 10000>
- T_PNTS (0,66)(0,0)(22,0)(22,67)(0,67)(0,66)(22,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (3668,5052)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (3884,5135)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (3797,2259)
- SIZE 180000 FLD_XYSCALE <7186 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(21,0)(21,67)(0,67)(0,66)(21,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (3674,2009)
- SIZE 180000 FLD_XYSCALE <7528 10000>
- T_PNTS (0,66)(0,0)(22,0)(22,67)(0,67)(0,66)(22,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (3921,2301)
- SIZE 180000 FLD_XYSCALE <7909 10000>
- TXTXYOFF <-9 66>
- T_PNTS (0,66)(0,0)(22,0)(22,67)(0,67)(0,66)(22,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (4161,3885)
- SIZE 180000 FLD_XYSCALE <7417 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(106,0)(106,68)(0,68)(0,66)(106,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (4037,3385)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (5022,3552)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (5022,383)
- SIZE 180000 FLD_XYSCALE <7347 10000>
- T_PNTS (0,66)(0,0)(105,0)(105,68)(0,68)(0,66)(105,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (5028,1842)
- SIZE 180000 FLD_XYSCALE <7186 10000>
- TXTXYOFF <-8 66>
- T_PNTS (0,66)(0,0)(21,0)(21,67)(0,67)(0,66)(21,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (5028,2051)
- SIZE 180000 FLD_XYSCALE <7186 10000>
- T_PNTS (0,66)(0,0)(21,0)(21,67)(0,67)(0,66)(21,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "1"
-.TXT AT (3822,925)
- SIZE 180000 FLD_XYSCALE <7417 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(106,0)(106,68)(0,68)(0,66)(106,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "0:N"
-.TXT AT (36,4526)
- SIZE 180000 FLD_XYSCALE <7341 10000>
- TXTXYOFF <-3 92>
- T_PNTS (0,92)(0,0)(228,0)(228,95)(0,95)(0,92)(228,92)
- .STR
-  SIZE 100000 FLD_XYSCALE <10000 10000>
-  "KEY:"
-.TXT AT (251,1801)
- SIZE 180000 FLD_XYSCALE <7339 10000>
- TXTXYOFF <-3 66>
- T_PNTS (0,66)(0,0)(217,0)(217,88)(0,88)(0,66)(217,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "atttypid"
-.TXT AT (1513,1967)
- SIZE 180000 FLD_XYSCALE <7310 10000>
- TXTXYOFF <-1 66>
- T_PNTS (0,66)(0,0)(223,0)(223,88)(0,88)(0,66)(223,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "typrelid"
-.TXT AT (1513,2134)
- SIZE 180000 FLD_XYSCALE <7324 10000>
- T_PNTS (0,66)(0,0)(240,0)(240,88)(0,88)(0,66)(240,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "typinput"
-.TXT AT (1513,2311)
- SIZE 180000 FLD_XYSCALE <7325 10000>
- TXTXYOFF <-1 56>
- T_PNTS (0,56)(0,0)(276,0)(276,78)(0,78)(0,56)(276,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "typoutput"
-.TXT AT (1513,2468)
- SIZE 180000 FLD_XYSCALE <7294 10000>
- TXTXYOFF <-1 66>
- T_PNTS (0,66)(0,0)(295,0)(295,88)(0,88)(0,66)(295,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "typreceive"
-.TXT AT (1513,2635)
- SIZE 180000 FLD_XYSCALE <7318 10000>
- T_PNTS (0,66)(0,0)(223,0)(223,88)(0,88)(0,66)(223,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "typsend"
-.TXT AT (1389,967)
- SIZE 180000 FLD_XYSCALE <7352 10000>
- T_PNTS (0,66)(0,0)(291,0)(291,68)(0,68)(0,66)(291,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "indexrelid"
-.TXT AT (4346,810)
- SIZE 180000 FLD_XYSCALE <7307 10000>
- TXTXYOFF <-2 56>
- T_PNTS (0,56)(0,0)(380,0)(380,78)(0,78)(0,56)(380,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amopstrategy"
-.TXT AT (2998,2775)
- SIZE 180000 FLD_XYSCALE <7327 10000>
- TXTXYOFF <0 66>
- T_PNTS (0,66)(0,0)(218,0)(218,88)(0,88)(0,66)(218,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "prolang"
-.TXT AT (4347,3823)
- SIZE 180000 FLD_XYSCALE <7306 10000>
- TXTXYOFF <-3 45>
- T_PNTS (0,45)(0,0)(208,0)(208,67)(0,67)(0,45)(208,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amproc"
-.TXT AT (2991,4490)
- SIZE 180000 FLD_XYSCALE <7290 10000>
- TXTXYOFF <-2 45>
- T_PNTS (0,45)(0,0)(215,0)(215,67)(0,67)(0,45)(215,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprcom"
-.TXT AT (2991,4645)
- SIZE 180000 FLD_XYSCALE <7312 10000>
- TXTXYOFF <-2 56>
- T_PNTS (0,56)(0,0)(281,0)(281,78)(0,78)(0,56)(281,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprnegate"
-.TXT AT (2991,4802)
- SIZE 180000 FLD_XYSCALE <7315 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(292,0)(292,88)(0,88)(0,66)(292,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprlsortop"
-.TXT AT (2991,4979)
- SIZE 180000 FLD_XYSCALE <7329 10000>
- TXTXYOFF <-2 56>
- T_PNTS (0,56)(0,0)(296,0)(296,78)(0,78)(0,56)(296,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprrsortop"
-.TXT AT (2991,5135)
- SIZE 180000 FLD_XYSCALE <7322 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(229,0)(229,88)(0,88)(0,66)(229,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprcode"
-.TXT AT (2991,5312)
- SIZE 180000 FLD_XYSCALE <7316 10000>
- TXTXYOFF <-2 56>
- T_PNTS (0,56)(0,0)(199,0)(199,78)(0,78)(0,56)(199,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprrest"
-.TXT AT (2991,5469)
- SIZE 180000 FLD_XYSCALE <7337 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(206,0)(206,88)(0,88)(0,66)(206,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprjoin"
-.TXT AT (1515,3802)
- SIZE 180000 FLD_XYSCALE <7331 10000>
- TXTXYOFF <-3 66>
- T_PNTS (0,66)(0,0)(315,0)(315,88)(0,88)(0,66)(315,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amgettuple"
-.TXT AT (1515,3968)
- SIZE 180000 FLD_XYSCALE <7345 10000>
- T_PNTS (0,66)(0,0)(246,0)(246,68)(0,68)(0,66)(246,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "aminsert"
-.TXT AT (1515,4135)
- SIZE 180000 FLD_XYSCALE <7337 10000>
- T_PNTS (0,66)(0,0)(256,0)(256,68)(0,68)(0,66)(256,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amdelete"
-.TXT AT (1515,4312)
- SIZE 180000 FLD_XYSCALE <7331 10000>
- TXTXYOFF <-3 56>
- T_PNTS (0,56)(0,0)(269,0)(269,78)(0,78)(0,56)(269,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amgetattr"
-.TXT AT (1515,4469)
- SIZE 180000 FLD_XYSCALE <7335 10000>
- TXTXYOFF <-3 66>
- T_PNTS (0,66)(0,0)(373,0)(373,88)(0,88)(0,66)(373,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "ambeginscan"
-.TXT AT (1515,4656)
- SIZE 180000 FLD_XYSCALE <7321 10000>
- TXTXYOFF <-3 45>
- T_PNTS (0,45)(0,0)(268,0)(268,47)(0,47)(0,45)(268,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amrescan"
-.TXT AT (1515,4802)
- SIZE 180000 FLD_XYSCALE <7333 10000>
- TXTXYOFF <-3 66>
- T_PNTS (0,66)(0,0)(317,0)(317,68)(0,68)(0,66)(317,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amendscan"
-.TXT AT (1515,4969)
- SIZE 180000 FLD_XYSCALE <7339 10000>
- T_PNTS (0,66)(0,0)(331,0)(331,88)(0,88)(0,66)(331,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "ammarkpos"
-.TXT AT (1515,5145)
- SIZE 180000 FLD_XYSCALE <7332 10000>
- TXTXYOFF <-3 56>
- T_PNTS (0,56)(0,0)(310,0)(310,78)(0,78)(0,56)(310,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amrestrpos"
-.TXT AT (1514,5302)
- SIZE 180000 FLD_XYSCALE <7334 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(232,0)(232,68)(0,68)(0,66)(232,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "ambuild"
-.TXT AT (281,4804)
- SIZE 180000 FLD_XYSCALE <7350 10000>
- TXTXYOFF <-1 64>
- T_PNTS (0,64)(0,0)(422,0)(422,66)(0,66)(0,64)(422,64)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "DEPENDENT"
-.TXT AT (281,5638)
- SIZE 180000 FLD_XYSCALE <7337 10000>
- T_PNTS (0,64)(0,0)(498,0)(498,66)(0,66)(0,64)(498,64)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "INDEPENDENT"
-.TXT AT (248,1300)
- SIZE 180000 FLD_XYSCALE <7372 10000>
- TXTXYOFF <0 66>
- T_PNTS (0,66)(0,0)(347,0)(347,88)(0,88)(0,66)(347,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_attribute"
-.TXT AT (248,2968)
- SIZE 180000 FLD_XYSCALE <7378 10000>
- T_PNTS (0,66)(0,0)(246,0)(246,88)(0,88)(0,66)(246,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_class"
-.TXT AT (1388,133)
- SIZE 180000 FLD_XYSCALE <7343 10000>
- T_PNTS (0,66)(0,0)(267,0)(267,88)(0,88)(0,66)(267,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_index"
-.TXT AT (1512,1644)
- SIZE 180000 FLD_XYSCALE <7321 10000>
- TXTXYOFF <0 56>
- T_PNTS (0,56)(0,0)(231,0)(231,78)(0,78)(0,56)(231,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_type"
-.TXT AT (1512,3489)
- SIZE 180000 FLD_XYSCALE <7329 10000>
- TXTXYOFF <0 45>
- T_PNTS (0,45)(0,0)(196,0)(196,67)(0,67)(0,45)(196,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_am"
-.TXT AT (2989,1988)
- SIZE 180000 FLD_XYSCALE <7323 10000>
- T_PNTS (0,45)(0,0)(234,0)(234,67)(0,67)(0,45)(234,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_proc"
-.TXT AT (2989,634)
- SIZE 180000 FLD_XYSCALE <7341 10000>
- TXTXYOFF <0 66>
- T_PNTS (0,66)(0,0)(367,0)(367,88)(0,88)(0,66)(367,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_language"
-.TXT AT (4344,154)
- SIZE 180000 FLD_XYSCALE <7337 10000>
- TXTXYOFF <0 45>
- T_PNTS (0,45)(0,0)(267,0)(267,67)(0,67)(0,45)(267,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_amop"
-.TXT AT (4344,1801)
- SIZE 180000 FLD_XYSCALE <7326 10000>
- TXTXYOFF <0 66>
- T_PNTS (0,66)(0,0)(318,0)(318,88)(0,88)(0,66)(318,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_opclass"
-.TXT AT (4344,3156)
- SIZE 180000 FLD_XYSCALE <7338 10000>
- TXTXYOFF <0 45>
- T_PNTS (0,45)(0,0)(322,0)(322,67)(0,67)(0,45)(322,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_amproc"
-.TXT AT (2989,3478)
- SIZE 180000 FLD_XYSCALE <7329 10000>
- TXTXYOFF <0 56>
- T_PNTS (0,56)(0,0)(349,0)(349,78)(0,78)(0,56)(349,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "pg_operator"
-.TXT AT (251,1467)
- SIZE 180000 FLD_XYSCALE <7371 10000>
- TXTXYOFF <-3 66>
- T_PNTS (0,66)(0,0)(201,0)(201,68)(0,68)(0,66)(201,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "attrelid"
-.TXT AT (251,1644)
- SIZE 180000 FLD_XYSCALE <7340 10000>
- TXTXYOFF <-3 56>
- T_PNTS (0,56)(0,0)(197,0)(197,58)(0,58)(0,56)(197,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "attnum"
-.TXT AT (248,3301)
- SIZE 180000 FLD_XYSCALE <7387 10000>
- TXTXYOFF <0 66>
- T_PNTS (0,66)(0,0)(165,0)(165,68)(0,68)(0,66)(165,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "relam"
-.TXT AT (250,3135)
- SIZE 180000 FLD_XYSCALE <7287 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(89,0)(89,68)(0,68)(0,66)(89,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oid"
-.TXT AT (1389,300)
- SIZE 180000 FLD_XYSCALE <7341 10000>
- TXTXYOFF <-1 66>
- T_PNTS (0,66)(0,0)(223,0)(223,68)(0,68)(0,66)(223,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "indrelid"
-.TXT AT (1389,467)
- SIZE 180000 FLD_XYSCALE <7368 10000>
- T_PNTS (0,66)(0,0)(194,0)(194,88)(0,88)(0,66)(194,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "indkey"
-.TXT AT (1389,634)
- SIZE 180000 FLD_XYSCALE <7349 10000>
- T_PNTS (0,66)(0,0)(217,0)(217,88)(0,88)(0,66)(217,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "indproc"
-.TXT AT (1389,800)
- SIZE 180000 FLD_XYSCALE <7364 10000>
- T_PNTS (0,66)(0,0)(219,0)(219,88)(0,88)(0,66)(219,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "indpred"
-.TXT AT (1514,1801)
- SIZE 180000 FLD_XYSCALE <7287 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(89,0)(89,68)(0,68)(0,66)(89,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oid"
-.TXT AT (1514,3635)
- SIZE 180000 FLD_XYSCALE <7287 10000>
- T_PNTS (0,66)(0,0)(89,0)(89,68)(0,68)(0,66)(89,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oid"
-.TXT AT (2991,2134)
- SIZE 180000 FLD_XYSCALE <7287 10000>
- T_PNTS (0,66)(0,0)(89,0)(89,68)(0,68)(0,66)(89,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oid"
-.TXT AT (2991,800)
- SIZE 180000 FLD_XYSCALE <7287 10000>
- T_PNTS (0,66)(0,0)(89,0)(89,68)(0,68)(0,66)(89,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oid"
-.TXT AT (4347,300)
- SIZE 180000 FLD_XYSCALE <7328 10000>
- TXTXYOFF <-3 66>
- T_PNTS (0,66)(0,0)(212,0)(212,88)(0,88)(0,66)(212,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amopid"
-.TXT AT (4347,467)
- SIZE 180000 FLD_XYSCALE <7329 10000>
- T_PNTS (0,66)(0,0)(296,0)(296,88)(0,88)(0,66)(296,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amopclaid"
-.TXT AT (4347,655)
- SIZE 180000 FLD_XYSCALE <7300 10000>
- TXTXYOFF <-3 45>
- T_PNTS (0,45)(0,0)(249,0)(249,67)(0,67)(0,45)(249,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amopopr"
-.TXT AT (4346,1967)
- SIZE 180000 FLD_XYSCALE <7287 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(89,0)(89,68)(0,68)(0,66)(89,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oid"
-.TXT AT (4347,3301)
- SIZE 180000 FLD_XYSCALE <7277 10000>
- TXTXYOFF <-3 66>
- T_PNTS (0,66)(0,0)(139,0)(139,68)(0,68)(0,66)(139,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amid"
-.TXT AT (4347,3468)
- SIZE 180000 FLD_XYSCALE <7329 10000>
- T_PNTS (0,66)(0,0)(296,0)(296,88)(0,88)(0,66)(296,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amopclaid"
-.TXT AT (4347,3656)
- SIZE 180000 FLD_XYSCALE <7336 10000>
- TXTXYOFF <-3 45>
- T_PNTS (0,45)(0,0)(341,0)(341,67)(0,67)(0,45)(341,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amprocnum"
-.TXT AT (2991,3635)
- SIZE 180000 FLD_XYSCALE <7287 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(89,0)(89,68)(0,68)(0,66)(89,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oid"
-.TXT AT (280,5802)
- SIZE 180000 FLD_XYSCALE <7326 10000>
- TXTXYOFF <0 66>
- T_PNTS (0,66)(0,0)(348,0)(348,88)(0,88)(0,66)(348,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "primary key"
-.TXT AT (281,4969)
- SIZE 180000 FLD_XYSCALE <7331 10000>
- TXTXYOFF <-1 66>
- T_PNTS (0,66)(0,0)(328,0)(328,88)(0,88)(0,66)(328,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "foreign key"
-.TXT AT (281,5969)
- SIZE 180000 FLD_XYSCALE <7343 10000>
- T_PNTS (0,66)(0,0)(468,0)(468,88)(0,88)(0,66)(468,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "non-oid primary"
-.TXT AT (310,6136)
- SIZE 180000 FLD_XYSCALE <7328 10000>
- TXTXYOFF <0 66>
- T_PNTS (0,66)(0,0)(333,0)(333,88)(0,88)(0,66)(333,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "key (if any)"
-.TXT AT (2991,3823)
- SIZE 180000 FLD_XYSCALE <7299 10000>
- TXTXYOFF <-2 45>
- T_PNTS (0,45)(0,0)(245,0)(245,67)(0,67)(0,45)(245,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprname"
-.TXT AT (2991,3968)
- SIZE 180000 FLD_XYSCALE <7314 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(191,0)(191,88)(0,88)(0,66)(191,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprleft"
-.TXT AT (2991,4135)
- SIZE 180000 FLD_XYSCALE <7339 10000>
- T_PNTS (0,66)(0,0)(231,0)(231,88)(0,88)(0,66)(231,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprright"
-.TXT AT (2991,4302)
- SIZE 180000 FLD_XYSCALE <7293 10000>
- T_PNTS (0,66)(0,0)(252,0)(252,88)(0,88)(0,66)(252,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "oprresult"
-.TXT AT (2989,2322)
- SIZE 180000 FLD_XYSCALE <7320 10000>
- TXTXYOFF <0 45>
- T_PNTS (0,45)(0,0)(250,0)(250,67)(0,67)(0,45)(250,45)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "proname"
-.TXT AT (2989,2478)
- SIZE 180000 FLD_XYSCALE <7317 10000>
- TXTXYOFF <0 56>
- T_PNTS (0,56)(0,0)(295,0)(295,78)(0,78)(0,56)(295,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "prorettype"
-.TXT AT (2989,2645)
- SIZE 180000 FLD_XYSCALE <7328 10000>
- T_PNTS (0,56)(0,0)(338,0)(338,78)(0,78)(0,56)(338,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "proargtypes"
-.TXT AT (958,6636)
- SIZE 180000 FLD_XYSCALE <7338 10000>
- TXTXYOFF <-1 66>
- T_PNTS (0,66)(0,0)(1511,0)(1511,88)(0,88)(0,66)(1511,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "indicates these key values are alternate primary keys"
-.TXT AT (960,6803)
- SIZE 180000 FLD_XYSCALE <7333 10000>
- TXTXYOFF <-3 66>
- T_PNTS (0,66)(0,0)(1590,0)(1590,88)(0,88)(0,66)(1590,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "(i.e., this class is generally identified by oid but may be"
-.TXT AT (1513,5443)
- SIZE 180000 FLD_XYSCALE <7334 10000>
- TXTXYOFF <-2 56>
- T_PNTS (0,56)(0,0)(255,0)(255,58)(0,58)(0,56)(255,56)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amcreate"
-.TXT AT (1510,5563)
- SIZE 180000 FLD_XYSCALE <7334 10000>
- TXTXYOFF <-2 66>
- T_PNTS (0,66)(0,0)(294,0)(294,88)(0,88)(0,66)(294,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amdestroy"
-.TXT AT (1510,5703)
- SIZE 180000 FLD_XYSCALE <7334 10000>
- T_PNTS (0,66)(0,0)(437,0)(437,68)(0,68)(0,66)(437,66)
- .STR
-  SIZE 70000 FLD_XYSCALE <10000 10000>
-  "amcostestimate"
-END PICTURE
-
-*END GRAPHICS
diff --git a/doc/src/graphics/catalogs.cgm b/doc/src/graphics/catalogs.cgm
deleted file mode 100644
index 42315017c50..00000000000
Binary files a/doc/src/graphics/catalogs.cgm and /dev/null differ
diff --git a/doc/src/graphics/catalogs.gif b/doc/src/graphics/catalogs.gif
deleted file mode 100644
index 24e3187e6c6..00000000000
Binary files a/doc/src/graphics/catalogs.gif and /dev/null differ
diff --git a/doc/src/graphics/catalogs.ps b/doc/src/graphics/catalogs.ps
deleted file mode 100644
index 21ef9fdcf03..00000000000
--- a/doc/src/graphics/catalogs.ps
+++ /dev/null
@@ -1,1018 +0,0 @@
-%!PS-Adobe-3.0
-%%Creator: groff version 1.09
-%%CreationDate: Sat Feb 24 21:37:20 1996
-%%DocumentNeededResources: font Times-Bold
-%%+ font Times-Italic
-%%+ font Times-Roman
-%%+ font Courier
-%%+ font Symbol
-%%DocumentSuppliedResources: file manual-er.eps
-%%+ file manual-files.eps
-%%+ file manual-arch.eps
-%%+ procset grops 1.09 0
-%%Pages: 1
-%%PageOrder: Ascend
-%%Orientation: Portrait
-%%EndComments
-%%BeginProlog
-%%BeginResource: procset grops 1.09 0
-/setpacking where{
-pop
-currentpacking
-true setpacking
-}if
-/grops 120 dict dup begin
-/SC 32 def
-/A/show load def
-/B{0 SC 3 -1 roll widthshow}bind def
-/C{0 exch ashow}bind def
-/D{0 exch 0 SC 5 2 roll awidthshow}bind def
-/E{0 rmoveto show}bind def
-/F{0 rmoveto 0 SC 3 -1 roll widthshow}bind def
-/G{0 rmoveto 0 exch ashow}bind def
-/H{0 rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
-/I{0 exch rmoveto show}bind def
-/J{0 exch rmoveto 0 SC 3 -1 roll widthshow}bind def
-/K{0 exch rmoveto 0 exch ashow}bind def
-/L{0 exch rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
-/M{rmoveto show}bind def
-/N{rmoveto 0 SC 3 -1 roll widthshow}bind def
-/O{rmoveto 0 exch ashow}bind def
-/P{rmoveto 0 exch 0 SC 5 2 roll awidthshow}bind def
-/Q{moveto show}bind def
-/R{moveto 0 SC 3 -1 roll widthshow}bind def
-/S{moveto 0 exch ashow}bind def
-/T{moveto 0 exch 0 SC 5 2 roll awidthshow}bind def
-/SF{
-findfont exch
-[exch dup 0 exch 0 exch neg 0 0]makefont
-dup setfont
-[exch/setfont cvx]cvx bind def
-}bind def
-/MF{
-findfont
-[5 2 roll
-0 3 1 roll 
-neg 0 0]makefont
-dup setfont
-[exch/setfont cvx]cvx bind def
-}bind def
-/level0 0 def
-/RES 0 def
-/PL 0 def
-/LS 0 def
-/PLG{
-gsave newpath clippath pathbbox grestore
-exch pop add exch pop
-}bind def
-/BP{
-/level0 save def
-1 setlinecap
-1 setlinejoin
-72 RES div dup scale
-LS{
-90 rotate
-}{
-0 PL translate
-}ifelse
-1 -1 scale
-}bind def
-/EP{
-level0 restore
-showpage
-}bind def
-/DA{
-newpath arcn stroke
-}bind def
-/SN{
-transform
-.25 sub exch .25 sub exch
-round .25 add exch round .25 add exch
-itransform
-}bind def
-/DL{
-SN
-moveto
-SN
-lineto stroke
-}bind def
-/DC{
-newpath 0 360 arc closepath
-}bind def
-/TM matrix def
-/DE{
-TM currentmatrix pop
-translate scale newpath 0 0 .5 0 360 arc closepath
-TM setmatrix
-}bind def
-/RC/rcurveto load def
-/RL/rlineto load def
-/ST/stroke load def
-/MT/moveto load def
-/CL/closepath load def
-/FL{
-currentgray exch setgray fill setgray
-}bind def
-/BL/fill load def
-/LW/setlinewidth load def
-/RE{
-findfont
-dup maxlength 1 index/FontName known not{1 add}if dict begin
-{
-1 index/FID ne{def}{ pop pop}ifelse
-}forall
-/Encoding exch def
-dup/FontName exch def
-currentdict end definefont pop
-}bind def
-/DEFS 0 def
-/EBEGIN{
-moveto
-DEFS begin
-}bind def
-/EEND/end load def
-/CNT 0 def
-/level1 0 def
-/PBEGIN{
-/level1 save def
-translate
-div 3 1 roll div exch scale
-neg exch neg exch translate
-0 setgray
-0 setlinecap
-1 setlinewidth
-0 setlinejoin
-10 setmiterlimit
-[] 0 setdash
-/setstrokeadjust where{
-pop
-false setstrokeadjust
-}if
-/setoverprint where{
-pop
-false setoverprint
-}if
-newpath
-/CNT countdictstack def
-userdict begin
-/showpage{} def
-}bind def
-/PEND{
-clear
-countdictstack CNT sub{end}repeat
-level1 restore
-}bind def
-end def
-/setpacking where{
-pop
-setpacking
-}if
-%%EndResource
-%%IncludeResource: font Times-Bold
-%%IncludeResource: font Times-Italic
-%%IncludeResource: font Times-Roman
-%%IncludeResource: font Courier
-%%IncludeResource: font Symbol
-grops begin/DEFS 1 dict def DEFS begin/u{.001 mul}bind def end/RES 72
-def/PL 792 def/LS false def/ENC0[/asciicircum/asciitilde/Scaron/Zcaron
-/scaron/zcaron/Ydieresis/trademark/quotesingle/.notdef/.notdef/.notdef
-/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef
-/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef/.notdef
-/.notdef/.notdef/space/exclam/quotedbl/numbersign/dollar/percent
-/ampersand/quoteright/parenleft/parenright/asterisk/plus/comma/hyphen
-/period/slash/zero/one/two/three/four/five/six/seven/eight/nine/colon
-/semicolon/less/equal/greater/question/at/A/B/C/D/E/F/G/H/I/J/K/L/M/N/O
-/P/Q/R/S/T/U/V/W/X/Y/Z/bracketleft/backslash/bracketright/circumflex
-/underscore/quoteleft/a/b/c/d/e/f/g/h/i/j/k/l/m/n/o/p/q/r/s/t/u/v/w/x/y
-/z/braceleft/bar/braceright/tilde/.notdef/quotesinglbase/guillemotleft
-/guillemotright/bullet/florin/fraction/perthousand/dagger/daggerdbl
-/endash/emdash/ff/fi/fl/ffi/ffl/dotlessi/dotlessj/grave/hungarumlaut
-/dotaccent/breve/caron/ring/ogonek/quotedblleft/quotedblright/oe/lslash
-/quotedblbase/OE/Lslash/.notdef/exclamdown/cent/sterling/currency/yen
-/brokenbar/section/dieresis/copyright/ordfeminine/guilsinglleft
-/logicalnot/minus/registered/macron/degree/plusminus/twosuperior
-/threesuperior/acute/mu/paragraph/periodcentered/cedilla/onesuperior
-/ordmasculine/guilsinglright/onequarter/onehalf/threequarters
-/questiondown/Agrave/Aacute/Acircumflex/Atilde/Adieresis/Aring/AE
-/Ccedilla/Egrave/Eacute/Ecircumflex/Edieresis/Igrave/Iacute/Icircumflex
-/Idieresis/Eth/Ntilde/Ograve/Oacute/Ocircumflex/Otilde/Odieresis
-/multiply/Oslash/Ugrave/Uacute/Ucircumflex/Udieresis/Yacute/Thorn
-/germandbls/agrave/aacute/acircumflex/atilde/adieresis/aring/ae/ccedilla
-/egrave/eacute/ecircumflex/edieresis/igrave/iacute/icircumflex/idieresis
-/eth/ntilde/ograve/oacute/ocircumflex/otilde/odieresis/divide/oslash
-/ugrave/uacute/ucircumflex/udieresis/yacute/thorn/ydieresis]def
-/Courier@0 ENC0/Courier RE/Times-Roman@0 ENC0/Times-Roman RE
-/Times-Italic@0 ENC0/Times-Italic RE/Times-Bold@0 ENC0/Times-Bold RE
-%%EndProlog
-%%Page: 23 1
-%%BeginPageSetup
-BP
-%%EndPageSetup
-.44 LW 77.5 109.2 72 109.2 DL 80.5 109.2 75 109.2 DL 86 109.2 80.5 109.2
-DL 91.5 109.2 86 109.2 DL 97 109.2 91.5 109.2 DL 102.5 109.2 97 109.2 DL
-108 109.2 102.5 109.2 DL 113.5 109.2 108 109.2 DL 119 109.2 113.5 109.2
-DL 124.5 109.2 119 109.2 DL 130 109.2 124.5 109.2 DL 135.5 109.2 130
-109.2 DL 141 109.2 135.5 109.2 DL 146.5 109.2 141 109.2 DL 152 109.2
-146.5 109.2 DL 157.5 109.2 152 109.2 DL 163 109.2 157.5 109.2 DL 168.5
-109.2 163 109.2 DL 174 109.2 168.5 109.2 DL 179.5 109.2 174 109.2 DL 185
-109.2 179.5 109.2 DL 190.5 109.2 185 109.2 DL 196 109.2 190.5 109.2 DL
-201.5 109.2 196 109.2 DL 207 109.2 201.5 109.2 DL 212.5 109.2 207 109.2
-DL 218 109.2 212.5 109.2 DL 223.5 109.2 218 109.2 DL 229 109.2 223.5
-109.2 DL 234.5 109.2 229 109.2 DL 240 109.2 234.5 109.2 DL 245.5 109.2
-240 109.2 DL 251 109.2 245.5 109.2 DL 256.5 109.2 251 109.2 DL 262 109.2
-256.5 109.2 DL 267.5 109.2 262 109.2 DL 273 109.2 267.5 109.2 DL 278.5
-109.2 273 109.2 DL 284 109.2 278.5 109.2 DL 289.5 109.2 284 109.2 DL 295
-109.2 289.5 109.2 DL 300.5 109.2 295 109.2 DL 306 109.2 300.5 109.2 DL
-311.5 109.2 306 109.2 DL 317 109.2 311.5 109.2 DL 322.5 109.2 317 109.2
-DL 328 109.2 322.5 109.2 DL 333.5 109.2 328 109.2 DL 339 109.2 333.5
-109.2 DL 344.5 109.2 339 109.2 DL 350 109.2 344.5 109.2 DL 355.5 109.2
-350 109.2 DL 361 109.2 355.5 109.2 DL 366.5 109.2 361 109.2 DL 372 109.2
-366.5 109.2 DL 377.5 109.2 372 109.2 DL 383 109.2 377.5 109.2 DL 388.5
-109.2 383 109.2 DL 394 109.2 388.5 109.2 DL 399.5 109.2 394 109.2 DL 405
-109.2 399.5 109.2 DL 410.5 109.2 405 109.2 DL 416 109.2 410.5 109.2 DL
-421.5 109.2 416 109.2 DL 427 109.2 421.5 109.2 DL 432.5 109.2 427 109.2
-DL 438 109.2 432.5 109.2 DL 443.5 109.2 438 109.2 DL 449 109.2 443.5
-109.2 DL 454.5 109.2 449 109.2 DL 460 109.2 454.5 109.2 DL 465.5 109.2
-460 109.2 DL 471 109.2 465.5 109.2 DL 476.5 109.2 471 109.2 DL 482 109.2
-476.5 109.2 DL 487.5 109.2 482 109.2 DL 493 109.2 487.5 109.2 DL 498.5
-109.2 493 109.2 DL 504 109.2 498.5 109.2 DL 0 0 432 754 -433.278 761 72
-568.878 PBEGIN
-%%BeginDocument: manual-er.eps
-%%Title: stdin
-%%Creator: fig2dev Version 3.1 Patchlevel 0
-%%CreationDate: Sat Feb 24 21:36:26 1996
-%%For: jolly@arcadia.CS.Berkeley.EDU (Jolly Chen,421 Soda,(510) 6421863,540-5955)
-%%Orientation: Portrait
-%%BoundingBox: 0 0 754 761
-%%Pages: 0
-%%BeginSetup
-%%IncludeFeature: *PageSize Letter
-%%EndSetup
-%%EndComments
-/$F2psDict 200 dict def
-$F2psDict begin
-$F2psDict /mtrx matrix put
-/col-1 {} def
-/col0 {0.000 0.000 0.000 srgb} bind def
-/col1 {0.000 0.000 1.000 srgb} bind def
-/col2 {0.000 1.000 0.000 srgb} bind def
-/col3 {0.000 1.000 1.000 srgb} bind def
-/col4 {1.000 0.000 0.000 srgb} bind def
-/col5 {1.000 0.000 1.000 srgb} bind def
-/col6 {1.000 1.000 0.000 srgb} bind def
-/col7 {1.000 1.000 1.000 srgb} bind def
-/col8 {0.000 0.000 0.560 srgb} bind def
-/col9 {0.000 0.000 0.690 srgb} bind def
-/col10 {0.000 0.000 0.820 srgb} bind def
-/col11 {0.530 0.810 1.000 srgb} bind def
-/col12 {0.000 0.560 0.000 srgb} bind def
-/col13 {0.000 0.690 0.000 srgb} bind def
-/col14 {0.000 0.820 0.000 srgb} bind def
-/col15 {0.000 0.560 0.560 srgb} bind def
-/col16 {0.000 0.690 0.690 srgb} bind def
-/col17 {0.000 0.820 0.820 srgb} bind def
-/col18 {0.560 0.000 0.000 srgb} bind def
-/col19 {0.690 0.000 0.000 srgb} bind def
-/col20 {0.820 0.000 0.000 srgb} bind def
-/col21 {0.560 0.000 0.560 srgb} bind def
-/col22 {0.690 0.000 0.690 srgb} bind def
-/col23 {0.820 0.000 0.820 srgb} bind def
-/col24 {0.500 0.190 0.000 srgb} bind def
-/col25 {0.630 0.250 0.000 srgb} bind def
-/col26 {0.750 0.380 0.000 srgb} bind def
-/col27 {1.000 0.500 0.500 srgb} bind def
-/col28 {1.000 0.630 0.630 srgb} bind def
-/col29 {1.000 0.750 0.750 srgb} bind def
-/col30 {1.000 0.880 0.880 srgb} bind def
-/col31 {1.000 0.840 0.000 srgb} bind def
-
-end
-save
--30.0 776.0 translate
-1 -1 scale
-
-/clp {closepath} bind def
-/ef {eofill} bind def
-/gr {grestore} bind def
-/gs {gsave} bind def
-/l {lineto} bind def
-/m {moveto} bind def
-/n {newpath} bind def
-/s {stroke} bind def
-/slc {setlinecap} bind def
-/slj {setlinejoin} bind def
-/slw {setlinewidth} bind def
-/srgb {setrgbcolor} bind def
-/rot {rotate} bind def
-/sc {scale} bind def
-/tr {translate} bind def
-/tnt {dup dup currentrgbcolor
-  4 -2 roll dup 1 exch sub 3 -1 roll mul add
-  4 -2 roll dup 1 exch sub 3 -1 roll mul add
-  4 -2 roll dup 1 exch sub 3 -1 roll mul add srgb}
-  bind def
-/shd {dup dup currentrgbcolor 4 -2 roll mul 4 -2 roll mul
-  4 -2 roll mul srgb} bind def
-/$F2psBegin {$F2psDict begin /$F2psEnteredState save def} def
-/$F2psEnd {$F2psEnteredState restore end} def
-
-$F2psBegin
-10 setmiterlimit
- 0.90000 0.90000 sc
-0.500 slw
-% Polyline
-n 194 414 m 259 414 l  259 454 l  274 454 l  gs col-1 s gr 
-% Polyline
-n 194 234 m 274 234 l  gs col-1 s gr 
-% Polyline
-n 259 134 m 239 134 l  239 394 l  199 394 l  gs col-1 s gr 
-% Polyline
-n 259 54 m 219 54 l  219 389 l  gs col-1 s gr 
-% Polyline
-n 199 389 m 219 389 l  gs col-1 s gr 
-% Polyline
-n 279 254 m 259 254 l  259 399 l  199 399 l  gs col-1 s gr 
-% Polyline
-n 179 234 m 199 234 l  gs col-1 s gr 
-% Polyline
-n 259 74 m 199 74 l  199 214 l  179 214 l  gs col-1 s gr 
-% Polyline
-n 379 294 m 399 294 l  gs col-1 s gr 
-% Polyline
-n 384 239 m 459 239 l  459 514 l  499 514 l  gs col-1 s gr 
-% Polyline
-n 459 494 m 499 494 l  gs col-1 s gr 
-% Polyline
-n 379 274 m 514 274 l  gs col-1 s gr 
-% Polyline
-n 379 474 m 439 474 l  gs col-1 s gr 
-% Polyline
-n 379 494 m 439 494 l  gs col-1 s gr 
-% Polyline
-n 379 514 m 439 514 l  gs col-1 s gr 
-% Polyline
-n 379 534 m 439 534 l  gs col-1 s gr 
-% Polyline
-n 379 554 m 439 554 l  gs col-1 s gr 
-% Polyline
-n 379 574 m 439 574 l  gs col-1 s gr 
-% Polyline
-n 379 594 m 439 594 l  gs col-1 s gr 
-% Polyline
-n 379 614 m 439 614 l  gs col-1 s gr 
-% Polyline
-n 379 634 m 439 634 l  gs col-1 s gr 
-% Polyline
-n 379 654 m 439 654 l  gs col-1 s gr 
-% Polyline
-n 439 279 m 514 279 l  gs col-1 s gr 
-% Polyline
-n 434 439 m 444 449 l  gs col-1 s gr 
-% Polyline
-n 404 269 m 414 279 l  gs col-1 s gr 
-% Polyline
-n 454 439 m 464 449 l  gs col-1 s gr 
-% Polyline
-n 619 634 m 659 634 l  gs col-1 s gr 
-% Polyline
-n 634 519 m 644 529 l  gs col-1 s gr 
-% Polyline
-n 654 579 m 664 589 l  gs col-1 s gr 
-% Polyline
-n 499 494 m 519 494 l  gs col-1 s gr 
-% Polyline
-n 499 514 m 519 514 l  gs col-1 s gr 
-% Polyline
-n 599 104 m 599 79 l  514 79 l  514 104 l  clp  gs col-1 s gr 
-% Polyline
-n 624 124 m 624 104 l  514 104 l  514 124 l  clp  gs col-1 s gr 
-% Polyline
-n 459 534 m 499 534 l  gs col-1 s gr 
-% Polyline
-n 499 534 m 519 534 l  gs col-1 s gr 
-% Polyline
-n 459 534 m 459 514 l  gs col-1 s gr 
-% Polyline
-n 384 229 m 499 229 l  499 314 l  519 314 l  gs col-1 s gr 
-% Polyline
-n 624 114 m 639 114 l  639 354 l  619 354 l  gs col-1 s gr 
-% Polyline
-n 384 454 m 419 454 l  419 414 l  739 414 l  gs col-1 s gr 
-% Polyline
-n 384 449 m 399 449 l  399 399 l  699 399 l  699 54 l  739 54 l  gs col-1 s gr 
-% Polyline
-n 624 449 m 719 449 l  719 94 l  739 94 l  gs col-1 s gr 
-% Polyline
-n 679 134 m 744 134 l  gs col-1 s gr 
-% Polyline
-n 674 159 m 684 169 l  gs col-1 s gr 
-% Polyline
-n 839 74 m 859 74 l  859 249 l  844 249 l  gs col-1 s gr 
-% Polyline
-n 844 254 m 859 254 l  859 434 l  839 434 l  gs col-1 s gr 
-% Polyline
-n 624 269 m 679 269 l  679 114 l  739 114 l  gs col-1 s gr 
-% Polyline
-n 624 274 m 679 274 l  679 474 l  739 474 l  gs col-1 s gr 
-% Polyline
-n 521 284 m 514 284 514 357 7 arcto 4 {pop} repeat 514 364 617 364 7 arcto 4 {pop} repeat 624 364 624 291 7 arcto 4 {pop} repeat 624 284 521 284 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-n 179 604 m 179 579 l  74 579 l  74 604 l  clp  gs col-1 s gr 
-% Polyline
-n 184 704 m 184 679 l  74 679 l  74 704 l  clp  gs col-1 s gr 
-% Polyline
-n 81 604 m 74 604 74 617 7 arcto 4 {pop} repeat 74 624 177 624 7 arcto 4 {pop} repeat 184 624 184 611 7 arcto 4 {pop} repeat 184 604 81 604 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-n 184 724 m 184 704 l  74 704 l  74 724 l  clp  gs col-1 s gr 
-% Polyline
-n 179 614 m 199 614 l  199 714 l  184 714 l  gs col-1 s gr 
-% Polyline
-n 184 764 m 184 724 l  74 724 l  74 764 l  clp  gs col-1 s gr 
-% Polyline
-n 184 784 m 184 764 l  74 764 l  74 784 l  clp  gs col-1 s gr 
-% Polyline
-n 81 724 m 74 724 74 777 7 arcto 4 {pop} repeat 74 784 177 784 7 arcto 4 {pop} repeat 184 784 184 731 7 arcto 4 {pop} repeat 184 724 81 724 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-n 166 804 m 159 804 159 812 7 arcto 4 {pop} repeat 159 819 172 819 7 arcto 4 {pop} repeat 179 819 179 811 7 arcto 4 {pop} repeat 179 804 166 804 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-n 439 654 m 439 279 l  gs col-1 s gr 
-% Polyline
-	[4.4] 0 setdash
-n 359 94 m 419 94 l  419 269 l  514 269 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 384 234 m 479 234 l  479 334 l  519 334 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 239 739 m 279 739 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-n 239 759 m 279 759 l  gs col-1 s gr 
-% Polyline
-	[4.4] 0 setdash
-n 379 314 m 399 314 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 379 334 m 399 334 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 399 294 m 399 334 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-n 399 274 m 399 294 l  gs col-1 s gr 
-% Polyline
-	[4.4] 0 setdash
-n 619 614 m 639 614 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 619 594 m 639 594 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-n 521 464 m 514 464 514 677 7 arcto 4 {pop} repeat 514 684 617 684 7 arcto 4 {pop} repeat 624 684 624 471 7 arcto 4 {pop} repeat 624 464 521 464 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-	[4.4] 0 setdash
-n 639 594 m 639 614 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 619 574 m 639 574 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 619 554 m 639 554 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 624 454 m 639 454 l  639 594 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 619 654 m 659 654 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 619 674 m 659 674 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-	[4.4] 0 setdash
-n 659 674 m 659 654 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-n 624 279 m 659 279 l  659 634 l  gs col-1 s gr 
-% Polyline
-	[4.4] 0 setdash
-n 659 634 m 659 654 l  gs col-1 s gr 	[] 0 setdash
-% Polyline
-n 154 184 m 154 159 l  69 159 l  69 184 l  clp  gs col-1 s gr 
-% Polyline
-n 76 184 m 69 184 69 237 7 arcto 4 {pop} repeat 69 244 172 244 7 arcto 4 {pop} repeat 179 244 179 191 7 arcto 4 {pop} repeat 179 184 76 184 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-n 69 224 m 179 224 l  gs col-1 s gr 
-% Polyline
-n 174 414 m 194 414 l  gs col-1 s gr 
-% Polyline
-n 179 399 m 199 399 l  gs col-1 s gr 
-% Polyline
-n 179 394 m 199 394 l  gs col-1 s gr 
-% Polyline
-n 179 389 m 199 389 l  gs col-1 s gr 
-% Polyline
-n 179 404 m 179 384 l  69 384 l  69 404 l  clp  gs col-1 s gr 
-% Polyline
-n 154 384 m 154 359 l  69 359 l  69 384 l  clp  gs col-1 s gr 
-% Polyline
-n 179 424 m 179 404 l  69 404 l  69 424 l  clp  gs col-1 s gr 
-% Polyline
-n 359 224 m 359 199 l  274 199 l  274 224 l  clp  gs col-1 s gr 
-% Polyline
-n 384 244 m 384 224 l  274 224 l  274 244 l  clp  gs col-1 s gr 
-% Polyline
-n 384 344 m 384 244 l  274 244 l  274 344 l  clp  gs col-1 s gr 
-% Polyline
-n 339 44 m 339 19 l  254 19 l  254 44 l  clp  gs col-1 s gr 
-% Polyline
-n 261 44 m 254 44 254 137 7 arcto 4 {pop} repeat 254 144 357 144 7 arcto 4 {pop} repeat 364 144 364 51 7 arcto 4 {pop} repeat 364 44 261 44 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-n 254 124 m 364 124 l  gs col-1 s gr 
-% Polyline
-n 819 44 m 819 19 l  734 19 l  734 44 l  clp  gs col-1 s gr 
-% Polyline
-n 741 44 m 734 44 734 137 7 arcto 4 {pop} repeat 734 144 837 144 7 arcto 4 {pop} repeat 844 144 844 51 7 arcto 4 {pop} repeat 844 44 741 44 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-n 734 104 m 844 104 l  gs col-1 s gr 
-% Polyline
-n 819 244 m 819 219 l  734 219 l  734 244 l  clp  gs col-1 s gr 
-% Polyline
-n 844 264 m 844 244 l  734 244 l  734 264 l  clp  gs col-1 s gr 
-% Polyline
-n 599 264 m 599 239 l  514 239 l  514 264 l  clp  gs col-1 s gr 
-% Polyline
-n 624 284 m 624 264 l  514 264 l  514 284 l  clp  gs col-1 s gr 
-% Polyline
-n 624 364 m 624 284 l  514 284 l  514 364 l  clp  gs col-1 s gr 
-% Polyline
-n 514 344 m 624 344 l  gs col-1 s gr 
-% Polyline
-n 819 404 m 819 379 l  734 379 l  734 404 l  clp  gs col-1 s gr 
-% Polyline
-n 741 404 m 734 404 734 477 7 arcto 4 {pop} repeat 734 484 837 484 7 arcto 4 {pop} repeat 844 484 844 411 7 arcto 4 {pop} repeat 844 404 741 404 7 arcto 4 {pop} repeat clp  gs col-1 s gr 
-% Polyline
-n 734 464 m 844 464 l  gs col-1 s gr 
-% Polyline
-n 599 444 m 599 419 l  514 419 l  514 444 l  clp  gs col-1 s gr 
-% Polyline
-n 624 464 m 624 444 l  514 444 l  514 464 l  clp  gs col-1 s gr 
-% Polyline
-n 624 544 m 624 464 l  514 464 l  514 544 l  clp  gs col-1 s gr 
-% Polyline
-n 624 684 m 624 544 l  514 544 l  514 684 l  clp  gs col-1 s gr 
-% Polyline
-n 384 464 m 384 444 l  274 444 l  274 464 l  clp  gs col-1 s gr 
-% Polyline
-n 359 444 m 359 419 l  274 419 l  274 444 l  clp  gs col-1 s gr 
-% Polyline
-n 384 664 m 384 464 l  274 464 l  274 664 l  clp  gs col-1 s gr 
-% Interp Spline
-n 219 799 m
-	219.84 787.54 219.84 782.54 219 779 curveto
-	217.75 773.72 212.79 763.10 209 759 curveto
-	205.29 754.99 199.04 751.24 184 744 curveto
- gs col-1 s gr
-
-n 190.34 749.27 m 184.00 744.00 l 192.08 745.67 l gs col-1 s gr
-/Times-Roman findfont 14.00 scalefont setfont
-589 339 m
-gs 1 -1 sc ([8]) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-299 79 m
-gs 1 -1 sc ([8]) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-119 659 m
-gs 1 -1 sc (REFERS-TO) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-79 779 m
-gs 1 -1 sc (non-key) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-249 459 m
-gs 1 -1 sc (1) col-1 show gr
-% Polyline
-n 74 194 m 59 194 l  59 394 l  69 394 l  gs col-1 s gr 
-/Times-Roman findfont 14.00 scalefont setfont
-184 429 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-189 859 m
-gs 1 -1 sc (identified by the non-oid primary key in other contexts\).) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-49 399 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-34 189 m
-gs 1 -1 sc (13:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-264 229 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-184 229 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-184 209 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-229 89 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-209 379 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-229 379 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-249 379 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-229 129 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-229 49 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-389 439 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-409 439 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-389 349 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-504 264 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-489 349 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-489 329 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-389 224 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-629 369 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-629 109 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-429 669 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-504 294 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-369 89 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-469 254 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-389 254 m
-gs 1 -1 sc (0:1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-284 739 m
-gs 1 -1 sc (optional) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-284 759 m
-gs 1 -1 sc (mandatory) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-424 194 m
-gs 1 -1 sc (0:1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-709 49 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-709 89 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-629 444 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-629 469 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-629 629 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-664 639 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-649 294 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-629 264 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-669 299 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-709 489 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-689 429 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-849 449 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-849 69 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-849 244 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-849 269 m
-gs 1 -1 sc (1) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-654 134 m
-gs 1 -1 sc (0:N) col-1 show gr
-/Times-Roman findfont 18.00 scalefont setfont
-39 569 m
-gs 1 -1 sc (KEY:) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-74 239 m
-gs 1 -1 sc (atttypid) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 259 m
-gs 1 -1 sc (typrelid) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 279 m
-gs 1 -1 sc (typinput) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 299 m
-gs 1 -1 sc (typoutput) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 319 m
-gs 1 -1 sc (typreceive) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 339 m
-gs 1 -1 sc (typsend) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-259 139 m
-gs 1 -1 sc (indexrelid) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-739 119 m
-gs 1 -1 sc (amopselect) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-739 139 m
-gs 1 -1 sc (amopnpages) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-519 359 m
-gs 1 -1 sc (prolang) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-739 479 m
-gs 1 -1 sc (amproc) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-519 559 m
-gs 1 -1 sc (oprcom) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-519 579 m
-gs 1 -1 sc (oprnegate) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-519 599 m
-gs 1 -1 sc (oprlsortop) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-519 619 m
-gs 1 -1 sc (oprrsortop) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-519 639 m
-gs 1 -1 sc (oprcode) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-519 659 m
-gs 1 -1 sc (oprrest) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-519 679 m
-gs 1 -1 sc (oprjoin) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 479 m
-gs 1 -1 sc (amgettuple) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 499 m
-gs 1 -1 sc (aminsert) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 519 m
-gs 1 -1 sc (amdelete) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 539 m
-gs 1 -1 sc (amgetattr) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 559 m
-gs 1 -1 sc (ambeginscan) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 579 m
-gs 1 -1 sc (amrescan) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 599 m
-gs 1 -1 sc (amendscan) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 619 m
-gs 1 -1 sc (ammarkpos) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 639 m
-gs 1 -1 sc (amrestrpos) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-279 659 m
-gs 1 -1 sc (ambuild) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-79 599 m
-gs 1 -1 sc (DEPENDENT) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-79 699 m
-gs 1 -1 sc (INDEPENDENT) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-74 179 m
-gs 1 -1 sc (pg_attribute) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-74 379 m
-gs 1 -1 sc (pg_class) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-259 39 m
-gs 1 -1 sc (pg_index) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-279 219 m
-gs 1 -1 sc (pg_type) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-279 439 m
-gs 1 -1 sc (pg_am) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-519 259 m
-gs 1 -1 sc (pg_proc) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-519 99 m
-gs 1 -1 sc (pg_language) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-739 39 m
-gs 1 -1 sc (pg_amop) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-739 239 m
-gs 1 -1 sc (pg_opclass) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-739 399 m
-gs 1 -1 sc (pg_amproc) col-1 show gr
-/Times-Bold findfont 14.00 scalefont setfont
-519 439 m
-gs 1 -1 sc (pg_operator) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-74 199 m
-gs 1 -1 sc (attrelid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-74 219 m
-gs 1 -1 sc (attnum) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-74 419 m
-gs 1 -1 sc (relam) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-74 399 m
-gs 1 -1 sc (oid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-259 59 m
-gs 1 -1 sc (indrelid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-259 79 m
-gs 1 -1 sc (indkey) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-259 99 m
-gs 1 -1 sc (indproc) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-259 119 m
-gs 1 -1 sc (indpred) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-279 239 m
-gs 1 -1 sc (oid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-279 459 m
-gs 1 -1 sc (oid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-519 279 m
-gs 1 -1 sc (oid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-519 119 m
-gs 1 -1 sc (oid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-739 59 m
-gs 1 -1 sc (amopid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-739 79 m
-gs 1 -1 sc (amopclaid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-739 99 m
-gs 1 -1 sc (amopopr) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-739 259 m
-gs 1 -1 sc (oid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-739 419 m
-gs 1 -1 sc (amid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-739 439 m
-gs 1 -1 sc (amopclaid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-739 459 m
-gs 1 -1 sc (amprocnum) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-519 459 m
-gs 1 -1 sc (oid) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-79 719 m
-gs 1 -1 sc (primary key) col-1 show gr
-/Times-BoldItalic findfont 14.00 scalefont setfont
-79 619 m
-gs 1 -1 sc (foreign key) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-79 739 m
-gs 1 -1 sc (non-oid primary) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-84 759 m
-gs 1 -1 sc (key \(if any\)) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-519 479 m
-gs 1 -1 sc (oprname) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-519 499 m
-gs 1 -1 sc (oprleft) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-519 519 m
-gs 1 -1 sc (oprright) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-519 539 m
-gs 1 -1 sc (oprresult) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-519 299 m
-gs 1 -1 sc (proname) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-519 319 m
-gs 1 -1 sc (prorettype) col-1 show gr
-/Times-Italic findfont 14.00 scalefont setfont
-519 339 m
-gs 1 -1 sc (proargtypes) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-189 819 m
-gs 1 -1 sc (indicates these key values are alternate primary keys) col-1 show gr
-/Times-Roman findfont 14.00 scalefont setfont
-189 839 m
-gs 1 -1 sc (\(i.e., this class is generally identified by oid but may be) col-1 show gr
-$F2psEnd
-restore
-%%EndDocument
-end PEND/F0 11/Times-Bold@0 SF(Figur)177.701 595.278 Q 2.75(e3)-.198 G
-/F1 11/Times-Roman@0 SF 5.5(.T)-2.75 G(he major)-5.5 E/F2 10
-/Times-Roman@0 SF(POSTGRES)2.75 E F1(system catalogs.)2.75 E 77.5
-608.478 72 608.478 DL 80.5 608.478 75 608.478 DL 86 608.478 80.5 608.478
-DL 91.5 608.478 86 608.478 DL 97 608.478 91.5 608.478 DL 102.5 608.478
-97 608.478 DL 108 608.478 102.5 608.478 DL 113.5 608.478 108 608.478 DL
-119 608.478 113.5 608.478 DL 124.5 608.478 119 608.478 DL 130 608.478
-124.5 608.478 DL 135.5 608.478 130 608.478 DL 141 608.478 135.5 608.478
-DL 146.5 608.478 141 608.478 DL 152 608.478 146.5 608.478 DL 157.5
-608.478 152 608.478 DL 163 608.478 157.5 608.478 DL 168.5 608.478 163
-608.478 DL 174 608.478 168.5 608.478 DL 179.5 608.478 174 608.478 DL 185
-608.478 179.5 608.478 DL 190.5 608.478 185 608.478 DL 196 608.478 190.5
-608.478 DL 201.5 608.478 196 608.478 DL 207 608.478 201.5 608.478 DL
-212.5 608.478 207 608.478 DL 218 608.478 212.5 608.478 DL 223.5 608.478
-218 608.478 DL 229 608.478 223.5 608.478 DL 234.5 608.478 229 608.478 DL
-240 608.478 234.5 608.478 DL 245.5 608.478 240 608.478 DL 251 608.478
-245.5 608.478 DL 256.5 608.478 251 608.478 DL 262 608.478 256.5 608.478
-DL 267.5 608.478 262 608.478 DL 273 608.478 267.5 608.478 DL 278.5
-608.478 273 608.478 DL 284 608.478 278.5 608.478 DL 289.5 608.478 284
-608.478 DL 295 608.478 289.5 608.478 DL 300.5 608.478 295 608.478 DL 306
-608.478 300.5 608.478 DL 311.5 608.478 306 608.478 DL 317 608.478 311.5
-608.478 DL 322.5 608.478 317 608.478 DL 328 608.478 322.5 608.478 DL
-333.5 608.478 328 608.478 DL 339 608.478 333.5 608.478 DL 344.5 608.478
-339 608.478 DL 350 608.478 344.5 608.478 DL 355.5 608.478 350 608.478 DL
-361 608.478 355.5 608.478 DL 366.5 608.478 361 608.478 DL 372 608.478
-366.5 608.478 DL 377.5 608.478 372 608.478 DL 383 608.478 377.5 608.478
-DL 388.5 608.478 383 608.478 DL 394 608.478 388.5 608.478 DL 399.5
-608.478 394 608.478 DL 405 608.478 399.5 608.478 DL 410.5 608.478 405
-608.478 DL 416 608.478 410.5 608.478 DL 421.5 608.478 416 608.478 DL 427
-608.478 421.5 608.478 DL 432.5 608.478 427 608.478 DL 438 608.478 432.5
-608.478 DL 443.5 608.478 438 608.478 DL 449 608.478 443.5 608.478 DL
-454.5 608.478 449 608.478 DL 460 608.478 454.5 608.478 DL 465.5 608.478
-460 608.478 DL 471 608.478 465.5 608.478 DL 476.5 608.478 471 608.478 DL
-482 608.478 476.5 608.478 DL 487.5 608.478 482 608.478 DL 493 608.478
-487.5 608.478 DL 498.5 608.478 493 608.478 DL 504 608.478 498.5 608.478
-DL 13.75(\(3\) T)113.5 649.078 R .962(ypes and procedures)-.88 F/F3 8
-/Times-Roman@0 SF(6)-4.4 I F1 .961(are central to the schema.)3.712 4.4
-N .961(Nearly e)6.461 F -.165(ve)-.275 G .961(ry catalog contains).165 F
-.739(some reference to instances in one or both of these classes.)
-142.826 662.278 R -.165(Fo)6.239 G 3.489(re).165 G(xample,)-3.654 E F2
-(POST)3.489 E(-)-.92 E(GRES)142.826 675.478 Q F1 .182(frequently uses t\
-ype signatures \(e.g., of functions and operators\) to identify)2.933 F
-.32 LW 76 685.078 72 685.078 DL 80 685.078 76 685.078 DL 84 685.078 80
-685.078 DL 88 685.078 84 685.078 DL 92 685.078 88 685.078 DL 96 685.078
-92 685.078 DL 100 685.078 96 685.078 DL 104 685.078 100 685.078 DL 108
-685.078 104 685.078 DL 112 685.078 108 685.078 DL 116 685.078 112
-685.078 DL 120 685.078 116 685.078 DL 124 685.078 120 685.078 DL 128
-685.078 124 685.078 DL 132 685.078 128 685.078 DL 136 685.078 132
-685.078 DL 140 685.078 136 685.078 DL 144 685.078 140 685.078 DL 148
-685.078 144 685.078 DL 152 685.078 148 685.078 DL 156 685.078 152
-685.078 DL 160 685.078 156 685.078 DL 164 685.078 160 685.078 DL 168
-685.078 164 685.078 DL 172 685.078 168 685.078 DL 176 685.078 172
-685.078 DL 180 685.078 176 685.078 DL 184 685.078 180 685.078 DL 188
-685.078 184 685.078 DL 192 685.078 188 685.078 DL 196 685.078 192
-685.078 DL 200 685.078 196 685.078 DL 204 685.078 200 685.078 DL 208
-685.078 204 685.078 DL 212 685.078 208 685.078 DL 216 685.078 212
-685.078 DL/F4 5/Times-Roman@0 SF(6)93.6 695.478 Q F3 1.28 -.64(We u)2
-3.2 P(se the w).64 E(ords)-.08 E/F5 8/Times-Italic@0 SF(pr)2 E(ocedur)
--.36 E(e)-.296 E F3(and)2 E F5(function)2 E F3(more or less interchang)2
-E(ably)-.04 E(.)-.52 E F0(23)282.5 756 Q EP
-%%Trailer
-end
-%%EOF
diff --git a/doc/src/graphics/clientserver.ag b/doc/src/graphics/clientserver.ag
deleted file mode 100644
index 74e8f07cee0..00000000000
--- a/doc/src/graphics/clientserver.ag
+++ /dev/null
@@ -1,99 +0,0 @@
-*BEGIN GRAPHICS VERSION=430/420 ENCODING=7BIT
-** "Creator" tgl
-** "Creation Date" Tue Feb 10 03:30:09 1998
-** "Revisor" tgl
-** "Last Modified" Thu Feb 19 16:51:48 1998
-
-SESSION
- WIN_SIZE <7500 5500>
- SLIDE_STYLE <0 -1 1>
- R_ARROW 1
- REZ <0 2000 2000 0 0>
-END SESSION
-
-SLIDE_INFO
- SLIDE_STYLE <0 -1 1>
-END SLIDE_INFO
-PICTURE
-.ELL AT (2526,191)
- R_ARROW 0
- V_SPACE <0 139 0>
- SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
- PNTS (1594,1154)(0,1154)(0,0)(1594,0)(1594,1154)
-.RECT AT (2766,453)
- XYRAD <220 68>
- PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-.TXT AT (2887,548)
- BACKFILL <1 0 5 1000 0 0 0>
- THICKNESS 0 MARGINS <0 0 0 0>
- TXTXYOFF <-2 94>
- T_PNTS (0,94)(0,0)(900,0)(900,97)(0,97)(0,94)(900,94)
- .STR
-  L_SPACE 250
-  "POSTMASTER"
-.RECT AT (2774,832)
- BACKFILL <1 0 0 0 0 0 0>
- THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
- PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-.TXT AT (3074,919)
- BACKFILL <1 0 5 1000 0 0 0>
- THICKNESS 0 MARGINS <0 0 0 0>
- TXTXYOFF <-6 94>
- T_PNTS (0,94)(0,0)(527,0)(527,97)(0,97)(0,94)(527,94)
- .STR
-  L_SPACE 250
-  "SERVER"
-.ELL AT (2509,533)
- BACKFILL <1 0 0 0 0 0 0>
- THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
- PNTS (0,0)(119,0)(119,119)(0,119)(0,0)
-.LINE AT (2615,593)
- PNTS (146,0)(0,0)
-.TXT AT (3040,1164)
- BACKFILL <1 0 5 1000 0 0 0>
- THICKNESS 0 MARGINS <0 0 0 0>
- TXTXYOFF <-7 95>
- T_PNTS (0,95)(0,0)(599,0)(599,98)(0,98)(0,95)(599,95)
- .STR
-  L_SPACE 250
-  "server host"
-.TXT AT (1051,1170)
- L_SPACE 139
- TXTXYOFF <-3 95>
- T_PNTS (0,95)(0,0)(574,0)(574,97)(0,97)(0,95)(574,95)
- .STR
-  L_SPACE 250
-  "client host"
-.RECT AT (786,612)
- BACKFILL <1 0 0 0 0 0 0>
- THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
- PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-.ELL AT (544,191)
- PNTS (1594,1154)(0,1154)(0,0)(1594,0)(1594,1154)
-.TXT AT (987,614)
- BACKFILL <1 0 5 1000 0 0 0>
- THICKNESS 0 MARGINS <0 0 0 0>
- TXTXYOFF <0 92>
- T_PNTS (0,92)(0,0)(264,0)(264,262)(0,262)(0,92)(264,92)
- .STR
-  L_SPACE 250
-  "User\nApp"
-.TXT AT (1489,692)
- L_SPACE 139
- TXTXYOFF <-2 94>
- T_PNTS (0,94)(0,0)(397,0)(397,120)(0,120)(0,94)(397,94)
- .STR
-  L_SPACE 250
-  "LIBPQ"
-.LINE AT (1413,613)
- BACKFILL <1 0 0 0 0 0 0>
- THICKNESS 1
- V_SPACE <0 250 0>
- SIZE 180000 MARGINS <125 125 250 62>
- PNTS (0,0)(0,266)
-.LINE AT (1926,606)
- R_ARROW 1
- PNTS (0,153)(574,0)
-END PICTURE
-
-*END GRAPHICS
diff --git a/doc/src/graphics/clientserver.gif b/doc/src/graphics/clientserver.gif
deleted file mode 100644
index 5ee9c7d1eb4..00000000000
Binary files a/doc/src/graphics/clientserver.gif and /dev/null differ
diff --git a/doc/src/graphics/connections.ag b/doc/src/graphics/connections.ag
deleted file mode 100644
index 86e089ee1e5..00000000000
--- a/doc/src/graphics/connections.ag
+++ /dev/null
@@ -1,486 +0,0 @@
-*BEGIN GRAPHICS VERSION=430/420 ENCODING=7BIT
-** "Creator" tgl
-** "Creation Date" Tue Feb 10 03:30:09 1998
-** "Revisor" tgl
-** "Last Modified" Fri Feb 20 14:31:20 1998
-
-SESSION
- WIN_SIZE <8067 10307>
- SLIDE_STYLE <0 -1 1>
- R_ARROW 3
- REZ <0 2000 2000 70 0>
-END SESSION
-
-SLIDE_INFO
- SLIDE_STYLE <0 -1 1>
-END SLIDE_INFO
-PICTURE
-.TXT AT (142,1073)
- BACKFILL <1 0 5 1000 0 0 0>
- THICKNESS 0 R_ARROW 0
- V_SPACE <0 139 0>
- SIZE 100000 L_SPACE 139 MARGINS <0 0 0 0>
- TXTXYOFF <0 95>
- T_PNTS (0,95)(0,0)(2219,0)(2219,237)(0,237)(0,95)(2219,95)
- .STR
-  L_SPACE 250
-  "(a) frontend sends request to postmaster\n      via well-known 
- network socket"
-.GRP
- BACKFILL <1 0 0 0 0 0 0>
- THICKNESS 1
- V_SPACE <0 250 0>
- SIZE 180000 MARGINS <125 125 250 62>
- .GRP
-  .ELL AT (2264,2818)
-   V_SPACE <0 139 0>
-   SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1594,1154)(0,1154)(0,0)(1594,0)(1594,1154)
-  .RECT AT (2504,3080)
-   XYRAD <220 68>
-   PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-  .TXT AT (2625,3175)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   TXTXYOFF <-2 94>
-   T_PNTS (0,94)(0,0)(900,0)(900,97)(0,97)(0,94)(900,94)
-   .STR
-    L_SPACE 250
-    "POSTMASTER"
-  .RECT AT (2512,3459)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-  .TXT AT (2812,3546)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   TXTXYOFF <-6 94>
-   T_PNTS (0,94)(0,0)(527,0)(527,97)(0,97)(0,94)(527,94)
-   .STR
-    L_SPACE 250
-    "SERVER"
-  .ELL AT (2247,3160)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (0,0)(119,0)(119,119)(0,119)(0,0)
-  .LINE AT (2353,3220)
-   PNTS (146,0)(0,0)
-  .TXT AT (2778,3791)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   TXTXYOFF <-7 95>
-   T_PNTS (0,95)(0,0)(599,0)(599,98)(0,98)(0,95)(599,95)
-   .STR
-    L_SPACE 250
-    "server host"
- END .GRP
- .GRP
-  BACKFILL <1 0 0 0 0 0 0>
-  THICKNESS 1
-  V_SPACE <0 250 0>
-  SIZE 180000 MARGINS <125 125 250 62>
-  .TXT AT (681,3409)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0
-   V_SPACE <0 139 0>
-   SIZE 100000 L_SPACE 139 MARGINS <0 0 0 0>
-   TXTXYOFF <-3 95>
-   T_PNTS (0,95)(0,0)(574,0)(574,97)(0,97)(0,95)(574,95)
-   .STR
-    L_SPACE 250
-    "client host"
-  .ELL AT (121,2817)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1594,848)(0,848)(0,0)(1594,0)(1594,848)
-  .GRP
-   V_SPACE <0 250 0>
-   SIZE 180000 L_SPACE 250 MARGINS <125 125 250 62>
-   .RECT AT (363,3025)
-    V_SPACE <0 139 0>
-    SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-    PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-   .TXT AT (564,3027)
-    BACKFILL <1 0 5 1000 0 0 0>
-    THICKNESS 0 MARGINS <0 0 0 0>
-    TXTXYOFF <0 92>
-    T_PNTS (0,92)(0,0)(264,0)(264,262)(0,262)(0,92)(264,92)
-    .STR
-     L_SPACE 250
-     "User\nApp"
-   .TXT AT (1066,3105)
-    L_SPACE 139
-    TXTXYOFF <-2 94>
-    T_PNTS (0,94)(0,0)(397,0)(397,120)(0,120)(0,94)(397,94)
-    .STR
-     L_SPACE 250
-     "LIBPQ"
-   .LINE AT (990,3026)
-    BACKFILL <1 0 0 0 0 0 0>
-    THICKNESS 1
-    V_SPACE <0 250 0>
-    SIZE 180000 MARGINS <125 125 250 62>
-    PNTS (0,0)(0,266)
-  END .GRP
- END .GRP
-END .GRP
-.GRP
- .ELL AT (2258,4158)
-  V_SPACE <0 139 0>
-  SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-  PNTS (1594,1154)(0,1154)(0,0)(1594,0)(1594,1154)
- .RECT AT (2498,4420)
-  PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
- .TXT AT (2619,4515)
-  BACKFILL <1 0 5 1000 0 0 0>
-  THICKNESS 0 MARGINS <0 0 0 0>
-  T_PNTS (0,94)(0,0)(900,0)(900,97)(0,97)(0,94)(900,94)
-  .STR
-   L_SPACE 250
-   "POSTMASTER"
- .RECT AT (2506,4799)
-  BACKFILL <1 0 0 0 0 0 0>
-  THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-  PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
- .TXT AT (2806,4886)
-  BACKFILL <1 0 5 1000 0 0 0>
-  THICKNESS 0 MARGINS <0 0 0 0>
-  TXTXYOFF <-6 94>
-  T_PNTS (0,94)(0,0)(527,0)(527,97)(0,97)(0,94)(527,94)
-  .STR
-   L_SPACE 250
-   "SERVER"
- .ELL AT (2241,4500)
-  BACKFILL <1 0 0 0 0 0 0>
-  THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-  PNTS (0,0)(119,0)(119,119)(0,119)(0,0)
- .LINE AT (2347,4560)
-  PNTS (146,0)(0,0)
- .TXT AT (2772,5131)
-  BACKFILL <1 0 5 1000 0 0 0>
-  THICKNESS 0 MARGINS <0 0 0 0>
-  TXTXYOFF <-7 95>
-  T_PNTS (0,95)(0,0)(599,0)(599,98)(0,98)(0,95)(599,95)
-  .STR
-   L_SPACE 250
-   "server host"
-END .GRP
-.GRP
- BACKFILL <1 0 0 0 0 0 0>
- THICKNESS 1
- V_SPACE <0 250 0>
- SIZE 180000 MARGINS <125 125 250 62>
- .TXT AT (682,5401)
-  BACKFILL <1 0 5 1000 0 0 0>
-  THICKNESS 0
-  V_SPACE <0 139 0>
-  SIZE 100000 L_SPACE 139 MARGINS <0 0 0 0>
-  TXTXYOFF <-3 95>
-  T_PNTS (0,95)(0,0)(574,0)(574,97)(0,97)(0,95)(574,95)
-  .STR
-   L_SPACE 250
-   "client host"
- .ELL AT (122,4809)
-  BACKFILL <1 0 0 0 0 0 0>
-  THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-  PNTS (1594,848)(0,848)(0,0)(1594,0)(1594,848)
- .GRP
-  V_SPACE <0 250 0>
-  SIZE 180000 L_SPACE 250 MARGINS <125 125 250 62>
-  .RECT AT (364,5017)
-   V_SPACE <0 139 0>
-   SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-  .TXT AT (565,5019)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   TXTXYOFF <0 92>
-   T_PNTS (0,92)(0,0)(264,0)(264,262)(0,262)(0,92)(264,92)
-   .STR
-    L_SPACE 250
-    "User\nApp"
-  .TXT AT (1067,5097)
-   L_SPACE 139
-   TXTXYOFF <-2 94>
-   T_PNTS (0,94)(0,0)(397,0)(397,120)(0,120)(0,94)(397,94)
-   .STR
-    L_SPACE 250
-    "LIBPQ"
-  .LINE AT (991,5018)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1
-   V_SPACE <0 250 0>
-   SIZE 180000 MARGINS <125 125 250 62>
-   PNTS (0,0)(0,266)
- END .GRP
-END .GRP
-.GRP
- .GRP
-  .ELL AT (2271,1504)
-   V_SPACE <0 139 0>
-   SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1594,1154)(0,1154)(0,0)(1594,0)(1594,1154)
-  .RECT AT (2511,1766)
-   PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-  .TXT AT (2632,1861)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   T_PNTS (0,94)(0,0)(900,0)(900,97)(0,97)(0,94)(900,94)
-   .STR
-    L_SPACE 250
-    "POSTMASTER"
-  .RECT AT (2519,2145)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-  .TXT AT (2819,2232)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   TXTXYOFF <-6 94>
-   T_PNTS (0,94)(0,0)(527,0)(527,97)(0,97)(0,94)(527,94)
-   .STR
-    L_SPACE 250
-    "SERVER"
-  .ELL AT (2254,1846)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (0,0)(119,0)(119,119)(0,119)(0,0)
-  .LINE AT (2360,1906)
-   PNTS (146,0)(0,0)
-  .TXT AT (2785,2477)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   TXTXYOFF <-7 95>
-   T_PNTS (0,95)(0,0)(599,0)(599,98)(0,98)(0,95)(599,95)
-   .STR
-    L_SPACE 250
-    "server host"
- END .GRP
- .GRP
-  BACKFILL <1 0 0 0 0 0 0>
-  THICKNESS 1
-  V_SPACE <0 250 0>
-  SIZE 180000 MARGINS <125 125 250 62>
-  .TXT AT (688,2095)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0
-   V_SPACE <0 139 0>
-   SIZE 100000 L_SPACE 139 MARGINS <0 0 0 0>
-   TXTXYOFF <-3 95>
-   T_PNTS (0,95)(0,0)(574,0)(574,97)(0,97)(0,95)(574,95)
-   .STR
-    L_SPACE 250
-    "client host"
-  .ELL AT (128,1503)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1594,848)(0,848)(0,0)(1594,0)(1594,848)
-  .GRP
-   V_SPACE <0 250 0>
-   SIZE 180000 L_SPACE 250 MARGINS <125 125 250 62>
-   .RECT AT (370,1711)
-    V_SPACE <0 139 0>
-    SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-    PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-   .TXT AT (571,1713)
-    BACKFILL <1 0 5 1000 0 0 0>
-    THICKNESS 0 MARGINS <0 0 0 0>
-    TXTXYOFF <0 92>
-    T_PNTS (0,92)(0,0)(264,0)(264,262)(0,262)(0,92)(264,92)
-    .STR
-     L_SPACE 250
-     "User\nApp"
-   .TXT AT (1073,1791)
-    L_SPACE 139
-    TXTXYOFF <-2 94>
-    T_PNTS (0,94)(0,0)(397,0)(397,120)(0,120)(0,94)(397,94)
-    .STR
-     L_SPACE 250
-     "LIBPQ"
-   .LINE AT (997,1712)
-    BACKFILL <1 0 0 0 0 0 0>
-    THICKNESS 1
-    V_SPACE <0 250 0>
-    SIZE 180000 MARGINS <125 125 250 62>
-    PNTS (0,0)(0,266)
-  END .GRP
- END .GRP
-END .GRP
-.GRP
- .GRP
-  .ELL AT (2255,126)
-   V_SPACE <0 139 0>
-   SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1594,1154)(0,1154)(0,0)(1594,0)(1594,1154)
-  .RECT AT (2495,388)
-   PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-  .TXT AT (2616,483)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   T_PNTS (0,94)(0,0)(901,0)(901,97)(0,97)(0,94)(901,94)
-   .STR
-    L_SPACE 250
-    "POSTMASTER"
-  .ELL AT (2238,468)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (0,0)(119,0)(119,119)(0,119)(0,0)
-  .LINE AT (2344,528)
-   PNTS (146,0)(0,0)
-  .TXT AT (2769,1099)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0 MARGINS <0 0 0 0>
-   TXTXYOFF <-7 95>
-   T_PNTS (0,95)(0,0)(600,0)(600,98)(0,98)(0,95)(600,95)
-   .STR
-    L_SPACE 250
-    "server host"
- END .GRP
- .GRP
-  BACKFILL <1 0 0 0 0 0 0>
-  THICKNESS 1
-  V_SPACE <0 250 0>
-  SIZE 180000 MARGINS <125 125 250 62>
-  .TXT AT (672,717)
-   BACKFILL <1 0 5 1000 0 0 0>
-   THICKNESS 0
-   V_SPACE <0 139 0>
-   SIZE 100000 L_SPACE 139 MARGINS <0 0 0 0>
-   TXTXYOFF <-3 95>
-   T_PNTS (0,95)(0,0)(572,0)(572,97)(0,97)(0,95)(572,95)
-   .STR
-    L_SPACE 250
-    "client host"
-  .ELL AT (112,125)
-   BACKFILL <1 0 0 0 0 0 0>
-   THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-   PNTS (1594,848)(0,848)(0,0)(1594,0)(1594,848)
-  .GRP
-   V_SPACE <0 250 0>
-   SIZE 180000 L_SPACE 250 MARGINS <125 125 250 62>
-   .RECT AT (354,333)
-    V_SPACE <0 139 0>
-    SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-    PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
-   .TXT AT (555,335)
-    BACKFILL <1 0 5 1000 0 0 0>
-    THICKNESS 0 MARGINS <0 0 0 0>
-    TXTXYOFF <0 92>
-    T_PNTS (0,92)(0,0)(263,0)(263,262)(0,262)(0,92)(263,92)
-    .STR
-     L_SPACE 250
-     "User\nApp"
-   .TXT AT (1056,413)
-    L_SPACE 139
-    TXTXYOFF <-1 94>
-    T_PNTS (0,94)(0,0)(398,0)(398,119)(0,119)(0,94)(398,94)
-    .STR
-     L_SPACE 250
-     "LIBPQ"
-   .LINE AT (981,334)
-    BACKFILL <1 0 0 0 0 0 0>
-    THICKNESS 1
-    V_SPACE <0 250 0>
-    SIZE 180000 MARGINS <125 125 250 62>
-    PNTS (0,0)(0,266)
-  END .GRP
- END .GRP
-END .GRP
-.LINE AT (1496,476)
- R_ARROW 3
- PNTS (0,0)(747,46)
-.TXT AT (129,2424)
- BACKFILL <1 0 5 1000 0 0 0>
- THICKNESS 0 R_ARROW 0
- V_SPACE <0 139 0>
- SIZE 100000 L_SPACE 139 MARGINS <0 0 0 0>
- TXTXYOFF <-6 95>
- T_PNTS (0,95)(0,0)(2084,0)(2084,126)(0,126)(0,95)(2084,95)
- .STR
-  L_SPACE 250
-  "(b) postmaster creates backend server"
-.TXT AT (130,3778)
- L_SPACE 139
- T_PNTS (0,95)(0,0)(2265,0)(2265,120)(0,120)(0,95)(2265,95)
- .STR
-  L_SPACE 250
-  "(c) frontend connected to backend server"
-.GRP
- BACKFILL <1 0 0 0 0 0 0>
- THICKNESS 1
- V_SPACE <0 250 0>
- SIZE 180000 MARGINS <125 125 250 62>
- .ELL AT (2265,5432)
-  V_SPACE <0 139 0>
-  SIZE 100000 L_SPACE 139 MARGINS <69 69 139 34>
-  PNTS (1594,1154)(0,1154)(0,0)(1594,0)(1594,1154)
- .RECT AT (2505,5694)
-  PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
- .TXT AT (2626,5789)
-  BACKFILL <1 0 5 1000 0 0 0>
-  THICKNESS 0 MARGINS <0 0 0 0>
-  TXTXYOFF <-2 94>
-  T_PNTS (0,94)(0,0)(900,0)(900,97)(0,97)(0,94)(900,94)
-  .STR
-   L_SPACE 250
-   "POSTMASTER"
- .RECT AT (2513,6073)
-  BACKFILL <1 0 0 0 0 0 0>
-  THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-  PNTS (1139,0)(0,0)(0,273)(1139,273)(1139,0)
- .TXT AT (2813,6160)
-  BACKFILL <1 0 5 1000 0 0 0>
-  THICKNESS 0 MARGINS <0 0 0 0>
-  TXTXYOFF <-6 94>
-  T_PNTS (0,94)(0,0)(527,0)(527,97)(0,97)(0,94)(527,94)
-  .STR
-   L_SPACE 250
-   "SERVER"
- .ELL AT (2248,5774)
-  BACKFILL <1 0 0 0 0 0 0>
-  THICKNESS 1 L_SPACE 139 MARGINS <69 69 139 34>
-  PNTS (0,0)(119,0)(119,119)(0,119)(0,0)
- .LINE AT (2354,5834)
-  PNTS (146,0)(0,0)
- .TXT AT (2779,6405)
-  BACKFILL <1 0 5 1000 0 0 0>
-  THICKNESS 0 MARGINS <0 0 0 0>
-  TXTXYOFF <-7 95>
-  T_PNTS (0,95)(0,0)(599,0)(599,98)(0,98)(0,95)(599,95)
-  .STR
-   L_SPACE 250
-   "server host"
-END .GRP
-.TXT AT (154,6070)
- L_SPACE 139
- TXTXYOFF <0 95>
- T_PNTS (0,95)(0,0)(1732,0)(1732,265)(0,265)(0,95)(1732,95)
- .STR
-  L_SPACE 250
-  "(d) frontend connected\n      to multiple backend servers"
-.LINE AT (1513,1853)
- BACKFILL <1 0 0 0 0 0 0>
- THICKNESS 1 R_ARROW 3
- V_SPACE <0 250 0>
- SIZE 180000 MARGINS <125 125 250 62>
- PNTS (0,0)(747,46)
-.LINE AT (3079,1967)
- PNTS (0,0)(7,239)
-.LINE AT (1507,3166)
- PNTS (0,0)(993,418)
-.LINE AT (1491,5185)
- PNTS (0,0)(1027,1043)
-.LINE AT (1513,4923)
- PNTS (0,213)(993,0)
-.TXT AT (171,4321)
- BACKFILL <1 0 5 1000 0 0 0>
- THICKNESS 0 R_ARROW 0
- V_SPACE <0 139 0>
- SIZE 100000 L_SPACE 139 MARGINS <0 0 0 0>
- T_PNTS (0,95)(0,0)(1429,0)(1429,236)(0,236)(0,95)(1429,95)
- .STR
-  L_SPACE 250
-  "And multiple connections\ncan be established..."
-END PICTURE
-
-*END GRAPHICS
diff --git a/doc/src/graphics/connections.gif b/doc/src/graphics/connections.gif
deleted file mode 100644
index 0de39b8d899..00000000000
Binary files a/doc/src/graphics/connections.gif and /dev/null differ
diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile
deleted file mode 100644
index 76e15524108..00000000000
--- a/doc/src/sgml/Makefile
+++ /dev/null
@@ -1,231 +0,0 @@
-#----------------------------------------------------------------------------
-#
-# Makefile
-#	Postgres documentation makefile
-#	Thomas Lockhart
-#
-# Copyright (c) 1994, Regents of the University of California
-#
-#
-# IDENTIFICATION
-#    $Header: /cvsroot/pgsql/doc/src/sgml/Makefile,v 1.50 2002/04/14 17:23:20 petere Exp $
-#
-#----------------------------------------------------------------------------
-
-subdir = doc/src/sgml
-top_builddir = ../../..
-include $(top_builddir)/src/Makefile.global
-
-.SECONDARY:
-.NOTPARALLEL:
-
-ifndef COLLATEINDEX
-COLLATEINDEX = $(DOCBOOKSTYLE)/bin/collateindex.pl
-endif
-
-ifndef JADE
-JADE = jade
-endif
-SGMLINCLUDE = -D $(srcdir) -D $(srcdir)/ref
-
-ifndef NSGMLS
-NSGMLS = nsgmls
-endif
-
-ifndef SGMLSPL
-SGMLSPL = sgmlspl
-endif
-
-CONVERT = convert
-EPSTOPDF = epstopdf
-
-
-# docbook2man generates man pages from docbook refentry source code.
-
-ifndef D2MDIR
-# This is where the (patched) docbook2man perl scripts reside on hub.org.
-D2MDIR= /home/users/t/thomas/d2x/docbook2man
-endif
-D2MSCRIPT= $(D2MDIR)/docbook2man-spec.pl
-
-vpath %.sgml ./ref
-
-ALLBOOKS = admin developer programmer reference tutorial user
-
-ALLSGML := $(wildcard $(srcdir)/*.sgml $(srcdir)/ref/*.sgml) bookindex.sgml setindex.sgml
-
-ifdef DOCBOOKSTYLE
-CATALOG = -c $(DOCBOOKSTYLE)/catalog
-endif
-
-
-##
-## Man pages
-##
-
-.PHONY: man
-
-DEFAULTSECTION := $(sqlmansect_dummy)
-
-man: $(ALLSGML)
-	$(NSGMLS) $(NSGMLS_FLAGS) $(srcdir)/book-decl.sgml $(srcdir)/reference.sgml \
-	  | $(SGMLSPL) $(D2MSCRIPT) --lowercase --section $(DEFAULTSECTION) --date "`date '+%Y-%m-%d'`"
-# One more time, to resolve cross-references
-	$(NSGMLS) $(NSGMLS_FLAGS) $(srcdir)/book-decl.sgml $(srcdir)/reference.sgml \
-	  | $(SGMLSPL) $(D2MSCRIPT) --lowercase --section $(DEFAULTSECTION) --date "`date '+%Y-%m-%d'`"
-	$(mkinstalldirs) man1 man$(DEFAULTSECTION)
-	mv *.1 man1/
-	mv *.$(DEFAULTSECTION) man$(DEFAULTSECTION)/
-
-
-##
-## HTML
-##
-
-JADE.html = $(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -i output-html -t sgml
-
-postgres.html: postgres.sgml $(ALLSGML) stylesheet.dsl
-	@rm -f *.html
-	$(JADE.html) $<
-	ln -sf index.html $@
-
-$(addsuffix .html, $(ALLBOOKS)): %.html: %.sgml $(ALLSGML) stylesheet.dsl
-	@rm -f *.html
-	$(JADE.html) book-decl.sgml $<
-	ln -sf index.html $@
-
-programmer.html: catalogs.gif connections.gif
-postgres.html: catalogs.gif connections.gif
-
-
-COLLATEINDEX := $(PERL) $(COLLATEINDEX) -f -g -t 'Index'
-
-ifeq (,$(wildcard HTML.index))
-bookindex.sgml:
-	$(COLLATEINDEX) -o $@ -N
-
-setindex.sgml:
-	$(COLLATEINDEX) -x -o $@ -N
-else
-bookindex.sgml: HTML.index
-	$(COLLATEINDEX) -i 'bookindex' -o $@ $<
-
-setindex.sgml: HTML.index
-	$(COLLATEINDEX) -i 'setindex' -x -o $@ $<
-endif
-
-
-##
-## Print
-##
-
-# RTF to allow minor editing for hardcopy
-$(addsuffix .rtf, $(ALLBOOKS)): %.rtf: %.sgml $(ALLSGML) stylesheet.dsl
-	$(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t rtf -V rtf-backend -i output-print book-decl.sgml $<
-
-# TeX
-# Regular TeX and pdfTeX have slightly differing requirements, so we
-# need to distinguish the path we're taking.
-
-$(addsuffix .tex-ps, $(ALLBOOKS)): %.tex-ps: %.sgml $(ALLSGML) stylesheet.dsl
-	$(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t tex -V tex-backend -i output-print -V texdvi-output -o $@ book-decl.sgml $<
-
-programmer.tex-ps: catalogs.eps connections.eps
-
-$(addsuffix .tex-pdf, $(ALLBOOKS)): %.tex-pdf: %.sgml $(ALLSGML) stylesheet.dsl
-	$(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t tex -V tex-backend -i output-print -V texpdf-output -o $@ book-decl.sgml $<
-
-programmer.tex-pdf: catalogs.pdf connections.pdf
-
-%.dvi: %.tex-ps
-	@rm -f $*.aux $*.log
-	jadetex $<
-	jadetex $<
-	jadetex $<
-
-# Postscript from TeX
-%.ps: %.dvi
-	dvips -o $@ $<
-
-%.pdf: %.tex-pdf
-	@rm -f $*.aux $*.log $*.out
-	pdfjadetex $<
-	pdfjadetex $<
-	pdfjadetex $<
-
-
-# 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.
-$(addsuffix .fot, $(ALLBOOKS)): %.fot: %.sgml $(ALLSGML) stylesheet.dsl
-	$(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -t fot -i output-print -o $@ book-decl.sgml $<
-
-
-# Graphics
-
-%.gif:
-	cp $(srcdir)/../graphics/$@ .
-
-%.eps: %.gif
-	$(CONVERT) $< eps:$@
-
-%.pdf: %.eps
-	$(EPSTOPDF) $<
-
-
-##
-## Semi-automatic generation of some text files.
-##
-
-JADE.text = $(JADE) $(JADEFLAGS) $(SGMLINCLUDE) $(CATALOG) -d stylesheet.dsl -i output-text -t sgml
-
-INSTALL HISTORY regress_README: % : %.html
-	@echo "|";\
-	 echo "| You should now take '$<', save it as a text file in Netscape,";\
-	 echo "| and put it in place of the existing '$@' file.";\
-	 echo "|"
-
-INSTALL.html: standalone-install.sgml installation.sgml
-	$(JADE.text) -V nochunks $+ >$@
-
-HISTORY.html: release.sgml
-	( echo '<!doctype appendix PUBLIC "-//OASIS//DTD DocBook V3.1//EN">'; \
-	  cat $< ) >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 V3.1//EN" ['; \
-	  echo '<!entity % standalone-ignore "IGNORE"> ]>'; \
-	  cat $< ) >tempfile_regress_README.sgml
-	$(JADE.text) -V nochunks tempfile_regress_README.sgml >$@
-	rm tempfile_regress_README.sgml
-
-
-##
-## Check
-##
-
-check: $(addprefix check-, $(ALLBOOKS)) check-postgres
-
-# Quick syntax check without style processing
-$(addprefix check-, $(ALLBOOKS)): check-%: %.sgml bookindex.sgml
-	$(NSGMLS) $(SGMLINCLUDE) -s book-decl.sgml $<
-
-check-postgres: postgres.sgml setindex.sgml
-	$(NSGMLS) $(SGMLINCLUDE) -s $<
-
-
-##
-## Clean
-##
-
-clean distclean maintainer-clean:
-# HTML
-	rm -f HTML.manifest *.html *.gif
-# man
-	rm -rf *.1 *.$(DEFAULTSECTION) man1 man$(DEFAULTSECTION) manpage.refs manpage.links manpage.log
-# print
-	rm -f *.rtf *.tex-ps *.tex-pdf *.dvi *.aux *.log *.ps *.pdf *.out *.eps *.fot
-# index
-	rm -f HTML.index bookindex.sgml setindex.sgml
diff --git a/doc/src/sgml/admin.sgml b/doc/src/sgml/admin.sgml
deleted file mode 100644
index 24a770d3685..00000000000
--- a/doc/src/sgml/admin.sgml
+++ /dev/null
@@ -1,62 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/admin.sgml,v 1.37 2002/06/13 05:15:22 momjian Exp $
--->
-
-<book id="admin">
-
-<!-- Title information -->
-
- <title>PostgreSQL &version; Administrator's Guide</title>
-
- <bookinfo>
-  <corpauthor>The PostgreSQL Global Development Group</corpauthor>
-  &legal;
- </bookinfo>
-
-<!--
-  Disable these extra intro chapters since some elements (e.g. y2k
-  statement) are included in the first intro.sgml and cause errors if
-  included twice.
--->
-<![%single-book;[
-  &intro;
-]]>
-
-  &installation;
-  &installw;
-  &runtime;
-  &client-auth;
-  &charset;
-  &manage-ag;
-  &user-manag;
-  &maintenance;
-  &backup;
-  &monitoring;
-  &diskusage;
-  &wal;
-  &recovery;
-  &regress;
-  &release;
-
-<![%single-book;[
-  &biblio;
-  &bookindex;
-]]>
-</book>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml
deleted file mode 100644
index acd548dd292..00000000000
--- a/doc/src/sgml/advanced.sgml
+++ /dev/null
@@ -1,425 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.28 2002/06/11 15:32:32 thomas Exp $
--->
-
- <chapter id="tutorial-advanced">
-  <title>Advanced Features</title>
-
-  <sect1 id="tutorial-advanced-intro">
-   <title>Introduction</title>
-
-   <para>
-    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.
-   </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
-    of advantage if you 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 example 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>
-
-   <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 don't 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 may 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>
-
-   <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
-    <productname>PostgreSQL</productname> can do this for you.
-   </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,
-	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:  &lt;unnamed&gt; referential integrity violation - key referenced from weather not found in 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 the <citetitle>Reference
-    Manual</citetitle> 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>
-  </sect1>
-
-
-  <sect1 id="tutorial-transactions">
-   <title>Transactions</title>
-
-   <indexterm zone="tutorial-transactions">
-    <primary>transactions</primary>
-   </indexterm>
-
-   <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 as 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>
-    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
-
-    <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 don't 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>
-    <productname>PostgreSQL</> actually treats every SQL statement as being
-    executed within a transaction.  If you don't 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 may get the effect of transaction
-     blocks without asking.  Check the documentation for the interface
-     you are using.
-    </para>
-   </note>
-  </sect1>
-
-
-  <sect1 id="tutorial-inheritance">
-   <title>Inheritance</title>
-
-   <indexterm zone="tutorial-inheritance">
-    <primary>inheritance</primary>
-   </indexterm>
-
-   <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, to name 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)
-) 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
-    <type>text</type>, a native <productname>PostgreSQL</productname>
-    type for variable length character strings.  State capitals have
-    an extra column, state, that shows their state.  In
-    <productname>PostgreSQL</productname>, a table can inherit from
-    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 ft.:
-
-    <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 ft. 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 --
-    <command>SELECT</command>, <command>UPDATE</command> and
-    <command>DELETE</command> -- support this <literal>ONLY</literal>
-    notation.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-conclusion">
-   <title>Conclusion</title>
- 
-   <para>
-    <productname>PostgreSQL</productname> has many features not
-    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 both the
-    <citetitle>User's Guide</citetitle> and the
-    <citetitle>Programmer's Guide</citetitle>.
-   </para>
-
-   <para>
-    If you feel you need more introductory material, please visit the
-    <ulink url="http://www.postgresql.org">PostgreSQL web
-    site</ulink> for links to more resources.
-   </para>
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/arch-dev.sgml b/doc/src/sgml/arch-dev.sgml
deleted file mode 100644
index cbc34957665..00000000000
--- a/doc/src/sgml/arch-dev.sgml
+++ /dev/null
@@ -1,4095 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.16 2001/11/21 05:53:40 thomas Exp $
--->
-
- <chapter id="overview">
-  <title>Overview of PostgreSQL Internals</title>
-
-  <note>
-   <title>Author</title>
-   <para>
-    This chapter originally appeared as a 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>
-
-  <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. Don't expect a
-   detailed description here (I think such a description dealing with
-   all data structures and functions used within <productname>PostgreSQL</productname>
-   would exceed 1000
-   pages!). This chapter is intended to help understanding the general
-   control and data flow within the backend from receiving a query to
-   sending the results.
-  </para>
-
-  <sect1 id="query-path">
-   <title>The Path of a Query</title>
-
-   <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 receives the results sent back by the server.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      The <firstterm>parser stage</firstterm> checks the query
-      transmitted by the application
-      program (client) 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 <firstterm>querytree</firstterm> and performs the
-      transformations given in the <firstterm>rule bodies</firstterm>.
-      One application of the rewrite system is given in the realization of
-      <firstterm>views</firstterm>.
-     </para>
-
-     <para>
-      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) querytree and creates a 
-      <firstterm>queryplan</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 plan is estimated and the
-      cheapest plan is chosen and handed back.
-     </para>
-    </step>
-
-    <step>
-     <para>
-      The executor recursively steps through
-      the <firstterm>plan tree</firstterm> and
-      retrieves tuples 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 tuples derived.
-     </para>
-    </step>
-   </procedure>
-
-   <para>
-    In the following sections we will cover every of the above listed items
-    in more detail to give a better understanding on <productname>PostgreSQL</productname>'s internal
-    control and data structures.
-   </para>
-  </sect1>
-
-  <sect1 id="connect-estab">
-   <title>How Connections are Established</title>
-
-   <para>
-    <productname>PostgreSQL</productname> is implemented using a simple "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 don't know <foreignphrase>per se</foreignphrase> 
-    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>postmaster</literal> and 
-    listens at a specified TCP/IP port for incoming connections. Whenever
-    a request for a connection is detected the <literal>postmaster</literal> process
-    spawns a new server process called <literal>postgres</literal>. The server
-    tasks (<literal>postgres</literal> processes) communicate with each other using
-    <firstterm>semaphores</firstterm> and <firstterm>shared memory</firstterm>
-    to ensure data integrity
-    throughout concurrent data access. Figure
-    \ref{connection} illustrates the interaction of the master process 
-    <literal>postmaster</literal> the server process <literal>postgres</literal> and a client
-    application. 
-   </para>
-
-   <para>
-    The client process can either be the <application>psql</application> frontend (for
-    interactive SQL queries) or any user application implemented using
-    the <filename>libpg</filename> library. Note that applications implemented using
-    <application>ecpg</application>
-    (the <productname>PostgreSQL</productname> embedded SQL preprocessor for C)
-    also use this library.
-   </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 tuples to the client
-    by transmitting them over the established connection.
-   </para>
-
-<!--
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/connection.ps}
-\caption{How a connection is established}
-\label{connection}
-\end{center}
-\end{figure}
--->
-
-  </sect1>
-
-  <sect1 id="parser-stage">
-   <title>The Parser Stage</title>
-
-   <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>yacc</application>
-       and <application>lex</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>
-
-    <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. For the implementation the well known Unix
-     tools <application>lex</application> and <application>yacc</application>
-     are used.
-    </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 keywords</firstterm> etc. For
-     every keyword 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>lex</application>
-     and <filename>gram.y</filename> is transformed to
-     <filename>gram.c</filename> using <application>yacc</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>lex</application>
-     or <application>yacc</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>yacc</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>lex</application> and
-     <application>yacc</application>. You should be familiar with
-     <application>yacc</application> before you start to study the
-     grammar given in <filename>gram.y</filename> otherwise you won't
-     understand what happens there.
-    </para>
-
-    <para>
-     For a better understanding of the data structures used in
-     <productname>PostgreSQL</productname>
-     for the processing of a query we use an example to illustrate the
-     changes made to these data structures in every stage.
-     This example contains the following simple query that will be used in
-     various descriptions and figures throughout the following
-     sections. The query assumes that the tables given in
-     <citetitle>The Supplier Database</citetitle>
-     <!--
-     XXX The above citetitle should really be an xref,
-     but that part has not yet been converted from Stefan's original document.
-     - thomas 1999-02-11
-    <xref linkend="supplier">
-     -->
-     have already been defined.
-
-     <example id="simple-select">
-      <title>A Simple Select</title>
-
-      <programlisting>
-select s.sname, se.pno
-    from supplier s, sells se
-    where s.sno > 2 and s.sno = se.sno;
-      </programlisting>
-     </example>
-    </para>
-
-    <para>
-     Figure \ref{parsetree} shows the <firstterm>parse tree</firstterm> built by the
-     grammar rules and actions given in <filename>gram.y</filename> for the query
-     given in  <xref linkend="simple-select">
-     (without the <firstterm>operator tree</firstterm> for
-     the <firstterm>where clause</firstterm> which is shown in figure \ref{where_clause}
-     because there was not enough space to show both data structures in one
-     figure).
-    </para>
-
-    <para>
-     The top node of the tree is a <literal>SelectStmt</literal> node. For every entry
-     appearing in the <firstterm>from clause</firstterm> of the SQL query a <literal>RangeVar</literal>
-     node is created holding the name of the <firstterm>alias</firstterm> and a pointer to a
-     <literal>RelExpr</literal> node holding the name of the <firstterm>relation</firstterm>. All
-     <literal>RangeVar</literal> nodes are collected in a list which is attached to the field
-     <literal>fromClause</literal> of the <literal>SelectStmt</literal> node.
-    </para>
-
-    <para>
-     For every entry appearing in the <firstterm>select list</firstterm> of the SQL query a
-     <literal>ResTarget</literal> node is created holding a pointer to an <literal>Attr</literal>
-     node. The <literal>Attr</literal> node holds the <firstterm>relation name</firstterm> of the entry and
-     a pointer to a <literal>Value</literal> node holding the name of the
-     <firstterm>attribute</firstterm>.
-     All <literal>ResTarget</literal> nodes are collected to a list which is
-     connected to the field <literal>targetList</literal> of the <literal>SelectStmt</literal> node.
-    </para>
-
-    <para>
-     Figure \ref{where_clause} shows the operator tree built for the
-     where clause of the SQL query given in
-     <xref linkend="simple-select">
-     which is attached to the field
-     <literal>qual</literal> of the <literal>SelectStmt</literal> node. The top node of the
-     operator tree is an <literal>A_Expr</literal> node representing an <literal>AND</literal>
-     operation. This node has two successors called <literal>lexpr</literal> and
-     <literal>rexpr</literal> pointing to two <firstterm>subtrees</firstterm>. The subtree attached to
-     <literal>lexpr</literal> represents the qualification <literal>s.sno &gt; 2</literal> and the one
-     attached to <literal>rexpr</literal> represents <literal>s.sno = se.sno</literal>. For every
-     attribute an <literal>Attr</literal> node is created holding the name of the
-     relation and a pointer to a <literal>Value</literal> node holding the name of the
-     attribute. For the constant term appearing in the query a
-     <literal>Const</literal> node is created holding the value.
-    </para>
-
-<!--
-XXX merge in the figures later... - thomas 1999-01-29
-
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/parsetree.ps}
-\caption{{\it TargetList} and {\it FromList} for query of example \ref{simple_select}}
-\label{parsetree}
-\end{center}
-\end{figure}
-
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/where_clause.ps}
-\caption{{\it WhereClause} for query of example \ref{simple_select}}
-\label{where_clause}
-\end{center}
-\end{figure}
--->
-
-   </sect2>
-
-   <sect2>
-     <title>Transformation Process</title>
-
-    <para>
-     The <firstterm>transformation process</firstterm> takes the tree handed back by
-     the parser as input and steps recursively through it.  If
-     a <literal>SelectStmt</literal> node is found, it is transformed
-     to a <literal>Query</literal>
-     node that will be the top most node of the new data structure. Figure
-     \ref{transformed} shows the transformed data structure (the part
-     for the transformed <firstterm>where clause</firstterm> is given in figure
-     \ref{transformed_where} because there was not enough space to show all
-     parts in one figure).
-    </para>
-
-    <para>
-     Now a check is made, if the <firstterm>relation names</firstterm> in the
-     <firstterm>FROM clause</firstterm> are known to the system. For every relation name
-     that is present in the <firstterm>system catalogs</firstterm> a <abbrev>RTE</abbrev> node is
-     created containing the relation name, the <firstterm>alias name</firstterm> and
-     the <firstterm>relation id</firstterm>. From now on the relation ids are used to
-     refer to the <firstterm>relations</firstterm> given in the query. All <abbrev>RTE</abbrev> nodes
-     are collected in the <firstterm>range table entry list</firstterm> that is connected
-     to the field <literal>rtable</literal> of the <literal>Query</literal> node. If a name of a
-     relation that is not known to the system is detected in the query an
-     error will be returned and the query processing will be aborted.
-    </para>
-
-    <para>
-     Next it is checked if the <firstterm>attribute names</firstterm> used are 
-     contained in the relations given in the query. For every
-     attribute} that is found a <abbrev>TLE</abbrev> node is created holding a pointer
-     to a <literal>Resdom</literal> node (which holds the name of the column) and a
-     pointer to a <literal>VAR</literal> node. There are two important numbers in the
-     <literal>VAR</literal> node. The field <literal>varno</literal> gives the position of the
-     relation containing the current attribute} in the range
-     table entry list created above. The field <literal>varattno</literal> gives the
-     position of the attribute within the relation. If the name
-     of an attribute cannot be found an error will be returned and
-     the query processing will be aborted.
-    </para>
-
-<!--
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/transform.ps}
-\caption{Transformed {\it TargetList} and {\it FromList} for query of example \ref{simple_select}}
-\label{transformed}
-\end{center}
-\end{figure}
-
-\noindent Figure \ref{transformed_where} shows the transformed {\it where
-clause}. Every {\tt A\_Expr} node is transformed to an {\tt Expr}
-node. The {\tt Attr} nodes representing the attributes are replaced by
-{\tt VAR} nodes as it has been done for the {\it targetlist}
-above. Checks if the appearing {\it attributes} are valid and known to the
-system are made. If there is an {\it attribute} used which
-is not known an error will be returned and the {\it query
-processing} will be aborted. \\
-\\
-The whole {\it transformation process} performs a transformation of
-the data structure handed back by the {\it parser} to a more
-comfortable form. The character strings representing the {\it
-relations} and {\it attributes} in the original tree are replaced by
-{\it relation ids} and {\tt VAR} nodes whose fields are referring to
-the entries of the {\it range table entry list}. In addition to the
-transformation, also various checks if the used {\it relation}
-and {\it attribute} names (appearing in the query) are valid in the
-current context are performed.
-
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/transform_where.ps}
-\caption{Transformed {\it where clause} for query of example \ref{simple_select}}
-\label{transformed_where}
-\end{center}
-\end{figure}
-
-\pagebreak
-\clearpage
-
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/plan.ps}
-\caption{{\it Plan} for query of example \ref{simple_select}}
-\label{plan}
-\end{center}
-\end{figure}
--->
-
-   </sect2>
-  </sect1>
-
-  <sect1 id="rule-system">
-   <title>The <productname>PostgreSQL</productname> Rule System</title>
-
-   <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>tuple level</firstterm> processing and was
-       implemented deep in the <firstterm>executor</firstterm>. The rule system was
-       called whenever an individual tuple had been accessed. This
-       implementation was removed in 1995 when the last official release
-       of the <productname>PostgreSQL</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>
-    For information on the syntax and creation of rules in the
-    <productname>PostgreSQL</productname> system refer to
-    <citetitle>The PostgreSQL User's Guide</citetitle>.
-   </para>
-
-   <sect2>
-    <title>The Rewrite System</title>
-
-    <para>
-     The <firstterm>query rewrite system</firstterm> is a module between
-     the parser stage and the planner/optimizer. It processes the tree handed
-     back by the parser stage (which represents a user query) and if
-     there is a rule present that has to be applied to the query it
-     rewrites the tree to an alternate form.
-    </para>
-
-    <sect3 id="view-impl">
-     <title>Techniques To Implement Views</title>
-
-     <para>
-      Now we will sketch the algorithm of the query rewrite system. For
-      better illustration we show how to implement views using rules
-      as an example.
-     </para>
-
-     <para>
-      Let the following rule be given:
-
-      <programlisting>
-  create rule view_rule
-  as on select 
-  to test_view
-  do instead
-     select s.sname, p.pname
-     from supplier s, sells se, part p
-     where s.sno = se.sno and
-           p.pno = se.pno;   
-      </programlisting>
-     </para>
-
-     <para>
-      The given rule will be <firstterm>fired</firstterm> whenever a select
-      against the relation <literal>test_view</literal> is detected. Instead of
-      selecting the tuples from <literal>test_view</literal> the select statement
-      given in the <firstterm>action part</firstterm> of the rule is executed.
-     </para>
-
-     <para>
-      Let the following user-query against <literal>test_view</literal> be given:
-
-      <programlisting>
-  select sname 
-  from test_view
-  where sname &lt;&gt; 'Smith';
-      </programlisting>
-     </para>
-
-     <para>
-      Here is a list of the steps performed by the query rewrite
-      system whenever a user-query against <literal>test_view</literal> appears. (The
-      following listing is a very informal description of the algorithm just
-      intended for basic understanding. For a detailed description refer
-      to <xref linkend="STON89">).
-     </para>
-
-     <procedure>
-      <title><literal>test_view</literal> Rewrite</title>
-      <step>
-       <para>
-	Take the query given in the action part of the rule.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	Adapt the targetlist to meet the number and order of
-	attributes given in the user-query.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	Add the qualification given in the where clause of the
-	user-query to the qualification of the query given in the
-	action part of the rule.
-       </para>
-      </step>
-     </procedure>
-
-     <para>
-      Given the rule definition above, the user-query will be
-      rewritten to the following form (Note that the rewriting is done on
-      the internal representation of the user-query handed back by the
-      parser stage but the derived new data structure will represent the following
-      query):
-
-      <programlisting>
-  select s.sname
-  from supplier s, sells se, part p
-  where s.sno = se.sno and
-        p.pno = se.pno and
-        s.sname &lt;&gt; 'Smith';
-      </programlisting>
-     </para>
-</sect3>
-   </sect2>
-  </sect1>
-
-  <sect1 id="planner-optimizer">
-   <title>Planner/Optimizer</title>
-
-   <para>
-    The task of the <firstterm>planner/optimizer</firstterm> is to create an optimal
-    execution plan. It first combines all possible ways of
-    <firstterm>scanning</firstterm> and <firstterm>joining</firstterm>
-    the relations that appear in a
-    query. All the created paths lead to the same result and it's the
-    task of the optimizer to estimate the cost of executing each path and
-    find out which one is the cheapest.
-   </para>
-
-   <sect2>
-    <title>Generating Possible Plans</title>
-
-    <para>
-     The planner/optimizer decides which plans should be generated
-     based upon the types of indexes defined on the relations appearing in
-     a query. There is always the possibility of performing a
-     sequential scan on a relation, so a plan using only
-     sequential scans 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 anything but '&lt;&gt;' 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.
-    </para>
-
-    <para>
-     After all feasible plans have been found for scanning single
-     relations, plans for joining relations are created. The
-     planner/optimizer considers only joins between every two relations for
-     which there exists a corresponding join clause (i.e. for which a
-     restriction like <literal>where rel1.attr1=rel2.attr2</literal> exists) in the
-     where qualification. All possible plans are generated for every
-     join pair considered by the planner/optimizer. The three possible join
-     strategies are:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-	<firstterm>nested iteration join</firstterm>: The right relation is scanned
-	once for every tuple found in the left relation. This strategy
-	is easy to implement but can be very time consuming.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-	<firstterm>merge sort join</firstterm>: Each relation is sorted on the join
-	attributes before the join starts. Then the two relations are
-	merged together taking into account that both relations are
-	ordered on the join attributes. This kind of join is more
-	attractive because every relation has to be scanned only once.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-	<firstterm>hash join</firstterm>: the right relation is first hashed on its
-	join attributes. Next the left relation is scanned and the
-	appropriate values of every tuple found are used as hash keys to
-	locate the tuples in the right relation.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Data Structure of the Plan</title>
-
-    <para>
-     Here we will give a little description of the nodes appearing in the
-     plan. Figure \ref{plan} shows the plan produced for the query in
-     example \ref{simple_select}.
-    </para>
-
-    <para>
-     The top node of the plan is a <literal>MergeJoin</literal> node that has two
-     successors, one attached to the field <literal>lefttree</literal> and the second
-     attached to the field <literal>righttree</literal>. Each of the subnodes represents
-     one relation of the join. As mentioned above a merge sort
-     join requires each relation to be sorted. That's why we find
-     a <literal>Sort</literal> node in each subplan. The additional qualification given
-     in the query (<literal>s.sno &gt; 2</literal>) is pushed down as far as possible and is
-     attached to the <literal>qpqual</literal> field of the leaf <literal>SeqScan</literal> node of
-     the corresponding subplan.
-    </para>
-
-    <para>
-     The list attached to the field <literal>mergeclauses</literal> of the
-     <literal>MergeJoin</literal> node contains information about the join attributes.
-     The values <literal>65000</literal> and <literal>65001</literal>
-     for the <literal>varno</literal> fields in the
-     <literal>VAR</literal> nodes appearing in the <literal>mergeclauses</literal> list (and also in the
-     <literal>targetlist</literal>) mean that not the tuples of the current node should be
-     considered but the tuples of the next "deeper" nodes (i.e. the top
-     nodes of the subplans) should be used instead.
-    </para>
-
-    <para>
-     Note that every <literal>Sort</literal> and <literal>SeqScan</literal> node appearing in figure
-     \ref{plan} has got a <literal>targetlist</literal> but because there was not enough space
-     only the one for the <literal>MergeJoin</literal> node could be drawn.
-    </para>
-
-    <para>
-     Another task performed by the planner/optimizer is fixing the
-     <firstterm>operator ids</firstterm> in the <literal>Expr</literal>
-     and <literal>Oper</literal> nodes. As
-     mentioned earlier, <productname>PostgreSQL</productname> supports a variety of different data
-     types and even user defined types can be used. To be able to maintain
-     the huge amount of functions and operators it is necessary to store
-     them in a system table. Each function and operator gets a unique
-     operator id. According to the types of the attributes used
-     within the qualifications etc., the appropriate operator ids
-     have to be used.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="executor">
-   <title>Executor</title>
-
-   <para>
-    The <firstterm>executor</firstterm> takes the plan handed back by the
-    planner/optimizer and starts processing the top node. In the case of
-    our example (the query given in example \ref{simple_select}) the top
-    node is a <literal>MergeJoin</literal> node. 
-   </para>
-
-   <para>
-    Before any merge can be done two tuples 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 a
-    <literal>SeqScan</literal> node and again a tuple has to be fetched before the node
-    itself can be processed. The executor calls itself recursively
-    another time for the subplan attached to <literal>lefttree</literal> of the
-    <literal>SeqScan</literal> node.
-   </para>
-
-   <para>
-    Now the new top node is a <literal>Sort</literal> node. As a sort has to be done on
-    the whole relation, the executor starts fetching tuples
-    from the <literal>Sort</literal> node's subplan and sorts them into a temporary
-    relation (in memory or a file) when the <literal>Sort</literal> node is visited for
-    the first time. (Further examinations of the <literal>Sort</literal> node will
-    always return just one tuple from the sorted temporary
-    relation.)
-   </para>
-
-   <para>
-    Every time the processing of the <literal>Sort</literal> node needs a new tuple the
-    executor is recursively called for the <literal>SeqScan</literal> node
-    attached as subplan. The relation (internally referenced by the
-    value given in the <literal>scanrelid</literal> field) is scanned for the next
-    tuple. If the tuple satisfies the qualification given by the tree
-    attached to <literal>qpqual</literal> it is handed back, otherwise the next tuple
-    is fetched until the qualification is satisfied. If the last tuple of
-    the relation has been processed a <literal>NULL</literal> pointer is
-    returned.
-   </para>
-
-   <para>
-    After a tuple has been handed back by the <literal>lefttree</literal> of the
-    <literal>MergeJoin</literal> the <literal>righttree</literal> is processed in the same way. If both
-    tuples are present the executor processes the <literal>MergeJoin</literal>
-    node. Whenever a new tuple from one of the subplans is needed a
-    recursive call to the executor is performed to obtain it. If a
-    joined tuple could be created it is handed back and one complete
-    processing of the plan tree has finished. 
-   </para>
-
-   <para>
-    Now the described steps are performed once for every tuple, until a
-    <literal>NULL</literal> pointer is returned for the processing of the
-    <literal>MergeJoin</literal> node, indicating that we are finished.
-   </para>
-
-  </sect1>
-
-<!--
-**********************************************************
-**********************************************************
-**********************************************************
-**********************************************************
-**********************************************************
-
-\pagebreak
-\clearpage
-
-\section{The Realization of the Having Clause}
-\label{having_impl}
-
-The {\it having clause} has been designed in SQL to be able to use the
-results of {\it aggregate functions} within a query qualification. The
-handling of the {\it having clause} is very similar to the handling of
-the {\it where clause}. Both are formulas in first order logic (FOL)
-that have to evaluate to true for a certain object to be handed back:
-%
-\begin{itemize}
-<step> The formula given in the {\it where clause} is evaluated for
-every tuple. If the evaluation returns {\tt true} the tuple is
-returned, every tuple not satisfying the qualification is ignored.
-%
-<step> In the case of {\it groups} the {\it having clause} is evaluated
-for every group. If the evaluation returns {\tt true} the group is
-taken into account otherwise it is ignored.
-\end{itemize}
-%
-\subsection{How Aggregate Functions are Implemented}
-\label{aggregates}
-
-Before we can describe how the {\it having clause} is implemented we
-will have a look at the implementation of {\it aggregate functions} as
-long as they just appear in the {\it targetlist}. Note that {\it aggregate
-functions} are applied to groups so the query must contain a {\it
-group clause}.
-%
-\begin{example} 
-\label{having}
-Here is an example of the usage of the {\it aggregate
-function} {\tt count} which counts the number of part numbers ({\tt
-pno}) of every group. (The table {\tt sells} is defined in example
-\ref{supplier}.)
-%
-\begin{verbatim}
-  select sno, count(pno)
-  from sells
-  group by sno;
-\end{verbatim}
-%
-\end{example}
-%
-A query like the one in example \ref{having} is processed by the usual
-stages:
-%
-\begin{itemize}
-<step> the parser stage
-<step> the rewrite system
-<step> the planner/optimizer 
-<step> the executor
-\end{itemize}
-%
-and in the following sections we will describe what every stage does
-to the query in order to obtain the appropriate result.
-
-\subsubsection{The Parser Stage}
-
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/parse_having.ps}
-\caption{{\it Querytree} built up for the query of example \ref{having}}
-\label{parse_having}
-\end{center}
-\end{figure}
-
-The parser stage builds up a {\it querytree} containing the {\it
-where} qualification and information about the {\it grouping} that has
-to be done (i.e. a list of all attributes to group for is attached to
-the field {\tt groupClause}). The main difference to {\it querytrees}
-built up for queries without {\it aggregate functions} is given in the
-field {\tt hasAggs} which is set to {\tt true} and in the {\it
-targetlist}. The {\tt expr} field of the second {\tt TLE} node of the
-{\it targetlist} shown in figure \ref{parse_having} does not point
-directly to a {\tt VAR} node but to an {\tt Aggreg} node representing
-the {\it aggregate function} used in the query.
-
-A check is made that every attribute grouped for appears only without
-an {\it aggregate function} in the {\it targetlist} and that every
-attribute that appears without an {\it aggregate function} in the
-{\it targetlist} is grouped for.
-%
-
-\pagebreak 
-
-\subsubsection{The Rewrite System}
-
-The rewriting system does not make any changes to the {\it querytree}
-as long as the query involves just {\it base tables}. If any {\it
-views} are present the query is rewritten to access the tables
-specified in the {\it view definition}.
-%
-\subsubsection{Planner/Optimizer}
-Whenever an {\it aggregate function} is involved in a query (which is
-indicated by the {\tt hasAggs} flag set to {\tt true}) the planner
-creates a {\it plantree} whose top node is an {\tt AGG} node. The {\it
-targetlist} is searched for {\it aggregate functions} and for every
-function that is found, a pointer to the corresponding {\tt Aggreg}
-node is added to a list which is finally attached to the field {\tt aggs} of
-the {\tt AGG} node. This list is needed by the {\it executor} to know which
-{\it aggregate functions} are present and have to be
-handled.
-
-The {\tt AGG} node is followed by a {\tt GRP} node. The implementation
-of the {\it grouping} logic needs a sorted table for its operation so
-the {\tt GRP} node is followed by a {\tt SORT} node. The {\tt SORT}
-operation gets its tuples from a kind of {\tt Scan} node (if no
-indexes are present this will be a simple {\tt SeqScan} node). Any
-qualifications present are attached to the {\tt Scan} node. Figure
-\ref{plan_having} shows the {\it plan} created for the query given in
-example \ref{having}.
-
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/plan_having.ps}
-\caption{{\it Plantree} for the query of example \ref{having}}
-\label{plan_having}
-\end{center}
-\end{figure}
-
-Note that every node has its own {\it targetlist} which may differ from the
-one of the node above or below.  The field {\tt varattno} of every
-{\tt VAR} node included in a {\it targetlist} contains a number representing
-the position of the attribute's value in the tuple of the current node.
-
-\pagebreak
-\clearpage
-
-\subsubsection{Executor}
-
-The {\it executor} uses the function {\tt execAgg()} to execute {\tt AGG}
-nodes. As described earlier it uses one main function {\tt
-ExecProcNode} which is called recursively to execute subtrees. The
-following steps are performed by {\tt execAgg()}:
-%
-\begin{itemize}
-%
-<step> The list attached to the field {\tt aggs} of the {\tt AGG} node is
-examined and for every {\it aggregate function} included the {\it transition
-functions} are fetched from a {\it function table}. Calculating the
-value of an {\it aggregate function} is done using three functions:
-%
-\begin{itemize}
-<step> The {\it first transition function} {\tt xfn1} is called with the
-current value of the attribute the {\it aggregate function} is applied
-to and changes its internal state using the attribute's value given as
-an argument.
-%
-<step> The {\it second transition function} {\tt xfn2} is called without any
-arguments and changes its internal state only according to internal rules.
-%
-<step> The {\it final function} {\tt finalfn} takes the final states of {\tt
-xfn1} and {\tt xfn2} as arguments and finishes the {\it aggregation}.
-\end{itemize}
-%
-\begin{example} Recall the functions necessary to implement the
-{\it aggregate function} {\tt avg} building the average over all
-values of an attribute in a group (see section \ref{ext_agg} {\it
-Extending Aggregates}):
-%
-\begin{itemize}
-%
-<step> The first transition function {\tt xfn1} has to be a function that
-takes the actual value of the attribute {\tt avg} is applied to as an
-argument and adds it to the internally stored sum of previous
-calls.
-%
-<step> The second transition function {\tt xfn2} only increases an internal
-counter every time it is called. 
-%
-<step> The final function {\tt finalfn} divides the result of {\tt xfn1} by
-the counter of {\tt xfn2} to calculate the average.
-%
-\end{itemize}
-%
-\end{example}
-%
-Note that {\tt xfn2} and {\tt finalfn} may be absent (e.g. for the
-{\it aggregate function} {\tt sum} which simply sums up all values of
-the given attribute within a group. \\
-\\
-{\tt execAgg()} creates an array containing one entry for every {\it
-aggregate function} found in the list attached to the field {\tt
-aggs}. The array will hold information needed for the execution of
-every {\it aggregate function} (including the {\it transition functions}
-described above).
-%
-<step> The following steps are executed in a loop as long as there are
-still tuples returned by the subplan (i.e. as long as there are still
-tuples left in the current group). When there are no tuples left
-in the group a {\tt NULL} pointer is returned indicating the end of the
-group.
-%
-\begin{itemize}
-<step> A new tuple from the subplan (i.e. the {\it plan} attached to the
-field {\tt lefttree}) is fetched by recursively calling {\tt
-ExecProcNode()} with the subplan as argument.
-%
-<step> For every {\it aggregate function} (contained in the array created
-before) apply the transition functions {\tt xfn1} and {\tt xfn2} to
-the values of the appropriate attributes of the current tuple.
-\end{itemize}
-%
-<step> When we get here, all tuples of the current group have been
-processed and the {\it transition functions} of all {\it aggregate
-functions} have been applied to the values of the attributes. We are
-now ready to complete the {\it aggregation} by applying the {\it final
-function} ({\tt finalfn}) for every {\it aggregate function}.
-%
-<step> Store the tuple containing the new values (the results of the
-{\it aggregate functions}) and hand it back.
-\end{itemize}
-%
-Note that the procedure described above only returns one tuple
-(i.e. it processes just one group and when the end of the group is
-detected it processes the {\it aggregate functions} and hands back one
-tuple). To retrieve all tuples (i.e. to process all groups) the
-function {\tt execAgg()} has to be called (returning a new tuple every
-time) until it returns a {\tt NULL} pointer indicating that there are
-no groups left to process.
-
-\subsection{How the Having Clause is Implemented}
-
-The basic idea of the implementation is to attach the {\it operator tree}
-built for the {\it having clause} to the field {\tt qpqual} of
-node {\tt AGG} (which is the top node of the query tree). Now the executor
-has to evaluate the new {\it operator tree} attached to {\tt qpqual} for
-every group processed. If the evaluation returns {\tt true} the group
-is taken into account otherwise it is ignored and the next group will
-be examined. \\
-\\
-In order to implement the {\it having clause} a variety of changes
-have been made to the following stages:
-%
-\begin{itemize}
-<step> The {\it parser stage} has been modified slightly to build up and
-transform an {\it operator tree} for the {\it having clause}.
-%
-<step> The {\it rewrite system} has been adapted to be able to use {\it
-views} with the {\it having logic}.
-%
-<step> The {\it planner/optimizer}  now takes the {\it operator tree} of
-the {\it having clause} and attaches it to the {\tt AGG} node (which
-is the top node of the {\it queryplan}).
-%
-<step> The {\it executor} has been modified to evaluate the {\it operator tree}
-(i.e. the internal representation of the {\it having
-qualification}) attached to the {\tt AGG} node and the results of the
-{\it aggregation} are only considered if the evaluation returns {\tt true}.
-\end{itemize}
-%
-In the following sections we will describe the changes made to every
-single stage in detail.
-
-\subsubsection{The Parser Stage}
-
-The grammar rules of the {\it parser} defined in {\tt gram.y} did not
-require any changes (i.e. the rules had already been prepared for the
-{\it having clause}). The {\it operator tree} built up for the {\it having
-clause} is attached to the field {\tt havingClause} of the {\tt
-SelectStmt} node handed back by the {\it parser}. \\
-\\
-The {\it transformation} procedures applied to the tree handed back by
-the {\it parser} transform the {\it operator tree} attached to the field
-{\tt havingClause} using exactly the same functions used for the
-transformation of the {\it operator tree} for the {\it where clause}. This
-is possible because both trees are built up by the same grammar rules
-of the {\it parser} and are therefore compatible. Additional checks
-that make sure that the {\it having clause} involves at least one
-{\it aggregate function} etc. are performed at a later point in time
-in the {\it planner/optimizer} stage. \\
-\\
-The necessary changes have been applied to the following functions
-included in the file {\tt
-$\ldots$/src/backend/parser/analyze.c}. Note, that only the relevant
-parts of the affected code are presented instead of the whole
-functions. Every added source line will be marked by a {\tt '+'} at the
-beginning of the line and every changed source line will be marked by
-a {\tt '!'} throughout the following code listings. Whenever a part of
-the code that is not relevant at the moment is skipped, three
-vertical dots are inserted instead.
-%
-\pagebreak
-%
-\begin{itemize}
-<step> {\tt transformInsertStmt()} \\
-This function becomes is invoked every time a SQL {\tt insert}
-statement involving a {\tt select} is used like the following example
-illustrates:
-%
-\begin{verbatim}
-  insert into t2
-  select x, y
-  from t1;
-\end{verbatim}
-%
-Two statements have been added to this function. The first one
-performs the transformation of the {\it operator tree} attached to the
-field {\tt havingClause} using the function {\tt
-transformWhereClause()} as done for the {\it where clause}. It is
-possible to use the same function for both clauses, because they are
-both built up by the same {\it grammar rules} given in {\tt gram.y}
-and are therefore compatible.
-
-The second statement makes sure, that {\it aggregate functions} are
-involved in the query whenever a {\it having clause} is used,
-otherwise the query could have been formulated using only a {\it where
-clause}.
-%
-\begin{verbatim}
-  static Query *
-  transformInsertStmt(ParseState *pstate, 
-                      InsertStmt *stmt)
-  {
-    /* make a new query tree */
-    Query *qry = makeNode(Query);
-                            .
-                            .
-                            .
-    /* fix where clause */
-    qry->qual = transformWhereClause(pstate, 
-                                     stmt->whereClause);
-
-+   /* The havingQual has a similar meaning as "qual" in 
-+    * the where statement. So we can easily use the  
-+    * code from the "where clause" with some additional
-+    * traversals done in .../optimizer/plan/planner.c 
-+    */
-+   qry->havingQual = transformWhereClause(pstate, 
-+                                   stmt->havingClause);     
-                            .
-                            .
-                            .
-+   /* If there is a havingQual but there are no 
-+    * aggregates, then there is something wrong with 
-+    * the query because having must contain aggregates 
-+    * in its expressions! Otherwise the query could 
-+    * have been formulated using the where clause.
-+    */
-+   if((qry->hasAggs == false) && 
-+      (qry->havingQual != NULL))
-+   {
-+     elog(ERROR,"This is not a valid having query!");
-+     return (Query *)NIL;
-+   }
-    return (Query *) qry;
-  }
-\end{verbatim}
-%
-<step> {\tt transformSelectStmt()} \\
-Exactly the same statements added to the function {\tt
-transformInsertStmt()} above have been added here as well.
-%
-\begin{verbatim}
-  static Query *
-  transformSelectStmt(ParseState *pstate, 
-                      SelectStmt *stmt)
-  {
-    Query  *qry = makeNode(Query);
-
-    qry->commandType = CMD_SELECT;
-                            .
-                            .
-                            .
-    qry->qual = transformWhereClause(pstate, 
-                                     stmt->whereClause);
-
-+   /* The havingQual has a similar meaning as "qual" in 
-+    * the where statement. So we can easily use the  
-+    * code from the "where clause" with some additional
-+    * traversals done in .../optimizer/plan/planner.c 
-+    */
-+   qry->havingQual = transformWhereClause(pstate, 
-+                                   stmt->havingClause);     
-                            .
-                            .
-                            .
-+   /* If there is a havingQual but there are no 
-+    * aggregates, then there is something wrong with 
-+    * the query because having must contain aggregates 
-+    * in its expressions! Otherwise the query could 
-+    * have been formulated using the where clause.
-+    */
-+   if((qry->hasAggs == false) && 
-+      (qry->havingQual != NULL))
-+   {
-+     elog(ERROR,"This is not a valid having query!");
-+     return (Query *)NIL;
-+   }
-    return (Query *) qry;
-  }
-\end{verbatim}
-%
-\end{itemize}
-
-
-\subsubsection{The Rewrite System}
-
-This section describes the changes to the {\it rewrite system} of
-<productname>PostgreSQL</productname> that have been necessary to support the use of {\it views}
-within queries using a {\it having clause} and to support the
-definition of {\it views} by queries using a {\it having clause}.
-
-As described in section \ref{view_impl} {\it Techniques To Implement
-Views} a query rewrite technique is used to implement {\it
-views}. There are two cases to be handled within the {\it rewrite
-system} as far as the {\it having clause} is concerned:
-%
-\pagebreak
-%
-\begin{itemize}
-<step> The {\it view definition} does not contain a {\it having clause}
-but the queries evaluated against this view may contain {\it having
-clauses}.
-<step> The {\it view definition} contains a {\it having clause}. In this
-case queries evaluated against this view must meet some
-restrictions as we will describe later.
-\end{itemize}
-%
-\paragraph{No having clause in the view definition:} First we will
-look at  the changes necessary to support queries using a
-{\it having clause} against a {\it view} defined without
-a {\it having clause}. \\
-\\
-Let the following view definition be given:
-%
-\begin{verbatim}
-  create view test_view
-  as select sno, pno
-     from sells
-     where sno > 2;
-\end{verbatim}
-%
-and the following query made against <literal>test_view</literal>:
-%
-\begin{verbatim}
-  select * 
-  from testview
-  where sno <> 5;
-\end{verbatim}
-%
-The query will be rewritten to:
-%
-\begin{verbatim}
-  select sno, pno
-  from sells
-  where sno > 2 and
-        sno <> 5;
-\end{verbatim}
-%
-The query given in the definition of the {\it view} <literal>test_view</literal>
-is the {\it backbone} of the rewritten query. The {\it targetlist} is taken
-from the user's query and also the {\it where qualification } of the
-user's query is added to the {\it where qualification} of the new
-query by using an {\tt AND} operation. \\
-\\
-Now consider the following query:
-%
-\begin{verbatim}
-  select sno, count(pno)
-  from testview
-  where sno <> 5
-  group by sno
-  having count(pno) > 1;  
-\end{verbatim}
-%
-From now on it is no longer sufficient to add just the {\it where
-clause} and the {\it targetlist} of the user's query to the new query. The
-{\it group clause} and the {\it having qualification} also have to be
-added to the rewritten query:
-%
-\begin{verbatim}
-  select sno, count(pno)
-  from sells
-  where sno > 2 and
-        sno <> 5
-  group by sno
-  having count(pno) > 1;
-\end{verbatim}
-%
-\pagebreak
-
-\noindent Several changes that have already been applied to the {\it
-targetlist} and the {\it where clause} also have to be applied to the
-{\it having clause}. Here is a collection of all {\it additional} steps that
-have to be performed in order to rewrite a query using a {\it having
-clause} against a simple {\it view} (i.e. a {\it view} whose
-definition does not use any {\it group} and {\it having clauses}):
-%
-\begin{itemize}
-%
-<step> Rewrite the subselects contained in the {\it having clause} if any are
-present.
-%
-<step> Adapt the {\tt varno} and {\tt varattno} fields of all {\tt
-VAR} nodes contained in the {\it operator tree} representing the {\it
-having clause} in the same way as it has been done for the tree
-representing the {\it where clause}. The {\tt varno} fields are changed
-to use the {\it base tables} given in the {\it view definition} (which
-have been inserted into the {\it range table entry list} in the
-meantime) instead of the {\it virtual tables}. The positions of
-the attributes used in the {\it view} may differ from the positions of
-the corresponding attributes in the {\it base tables}. That's why the
-{\tt varattno} fields also have to be adapted.
-%
-<step> Adapt the {\tt varno} and {\tt varattno} fields of all {\tt
-VAR} nodes contained in the {\tt groupClause} of the user's query in
-the way and for the reasons described above.
-%
-<step> Attach the tree representing the {\it having qualification} (which is
-currently attached to the field {\tt havingClause} of the {\tt Query}
-node for the user's query) to the field {\tt havingClause} of the {\tt
-Query} node for the new (rewritten) query.
-%
-<step> Attach the list representing the {\it group clause} (currently
-attached to the field {\tt groupClause} of the {\tt Query} node for
-the user's query) to the field {\it group clause} of the node for the
-new (rewritten) query.
-%
-\end{itemize} 
-
-\paragraph{The view definition contains a having clause:}  Now we will
-look at the problems that can arise using {\it views} that are
-defined using a query involving a {\it having clause}. \\
-\\
-Let the following {\it view definition} be given:
-%
-\begin{verbatim}
-  create view test_view
-  as select sno, count(pno) as number
-     from sells
-     where sno > 2
-     group by sno
-     having count(pno) > 1;
-\end{verbatim}
-%
-Simple queries against this {\it view} will not cause any troubles:
-%
-\begin{verbatim}
-  select * 
-  from test_view
-  where sno <> 5;
-\end{verbatim}
-%
-This query can easily be rewritten by adding the {\it where
-qualification} of the user's query ({\tt sno $<>$ 5}) to the {\it
-where qualification} of the {\it view definition's } query. \\
-\\
-The next query is also simple but it will cause troubles when
-it is evaluated against the above given {\it view definition}:
-%
-\begin{verbatim}
-  select * 
-  from test_view
-  where number > 1; /* count(pno) in the view def.
-                     * is called  number here */
-\end{verbatim}
-%
-\pagebreak
-The currently implemented techniques for query rewriting will rewrite
-the query to:
-%
-\begin{verbatim}
-  select *
-  from sells
-  where sno > 2 and
-        count(pno) > 1
-  group by sno         
-  having count(pno) > 1;
-\end{verbatim}
-%
-which is an invalid query because an {\it aggregate function} appears
-in the {\it where clause}. \\
-\\
-Also the next query will cause troubles:
-%
-\begin{verbatim}
-  select pno, count(sno)
-  from test_view
-  group by pno;
-\end{verbatim}
-%
-As you can see this query does neither involve a {\it where clause}
-nor a {\it having clause} but it contains a {\it group clause} which
-groups by the attribute {\tt pno}. The query in the definition of the
-{\it view} also contains a {\it group clause} that groups by the
-attribute {\tt sno}. The two {\it group clauses} are in conflict with
-each other and therefore the query cannot be rewritten to a form that
-would make sense.\\
-\\
-{\bf Note:} There is no solution to the above mentioned problems at the
-moment and it does not make sense to put much effort into that because
-the implementation of the support for queries like:
-%
-\begin{verbatim}
-  select pno_count, count(sno) 
-  from ( select sno, count(pno) as pno_count
-         from sells 
-         where sno > 2
-         group by sno
-         having count(pno) > 1)
-  group by pno_count;
-\end{verbatim}
-%
-(which is part of the SQL92 standard) will automatically also solve
-these problems. \\
-\\
-In the next part of the current section we will present the changes
-applied to the source code in order to realize the above described
-items. Note that it is not necessary to understand the meaning of
-every single source line here and therefore we will not discuss
-detailed questions like "Why has the variable {\tt varno} to be
-increased by 3?". Questions like that belong to a chapter dealing
-with the implementation of {\it views} in <productname>PostgreSQL</productname> and to be able to
-answer them it would be necessary to know all the functions and not
-only those described here. The fact important for us is to make sure,
-that whatever is applied to the {\it targetlist} and the data
-structures representing the {\it where clause} is also applied to the
-data structures for the {\it having clause}. There are three files
-affected: \\
-\\
-\indent {\tt $\ldots$/src/backend/rewrite/rewriteHandler.c} \\
-\indent {\tt $\ldots$/src/backend/rewrite/rewriteManip.c} \\
-\indent {\tt $\ldots$/src/backend/commands/view.c} \\
-\\
-Here is a description of the changes made to the functions contained
-in the file {\tt $\ldots$/src/backend/rewrite/rewriteHandler.c}:
-%
-\pagebreak
-%
-\begin{itemize}
-<step> {\tt ApplyRetrieveRule()} \\
-This function becomes invoked whenever a {\tt select} statement
-against a {\it view} is recognized and applies the {\it rewrite rule}
-stored in the {\it system catalogs}. The additional source lines given
-in the listing below make sure that the functions {\tt
-OffsetVarNodes()} and {\tt ChangeVarNodes()} that are invoked for the
-{\it where clause} and the {\it targetlist} of the query given in the
-{\it view definition} are also called for the {\it having clause} and
-the {\it group clause} of the query in the {\it view
-definition}. These functions adapt the {\tt varno} and {\tt varattno}
-fields of the {\tt VAR} nodes involved.
-
-The additional source lines at the end of {\tt ApplyRetrieveRule()}
-attach the data structures representing the {\it having clause} and
-the {\it group clause} of the query in the {\it view definition} to
-the rewritten {\it parsetree}. As mentioned earlier, a {\it view
-definition} involving a {\it group clause} will cause troubles
-whenever a query using a different {\it group clause} against this
-{\it view} is executed. There is no mechanism preventing these
-troubles included at the moment.
-
-Note that the functions {\tt OffsetVarNodes()} , {\tt ChangeVarNodes()}
-and {\tt AddHavingQual()} appearing in {\tt ApplyRetrieveRule()} are
-described at a later point in time.
-%
-\begin{verbatim}
-  static void
-  ApplyRetrieveRule(Query *parsetree, RewriteRule *rule,
-                    int rt_index, int relation_level,
-                    Relation relation, int *modified)
-  {
-    Query  *rule_action = NULL;
-    Node   *rule_qual;
-    List   *rtable,
-                            .
-                            .
-                            .
-    OffsetVarNodes((Node *) rule_action->targetList, 
-                   rt_length);
-    OffsetVarNodes(rule_qual, rt_length);
-        
-+   OffsetVarNodes((Node *) rule_action->groupClause, 
-+                  rt_length);
-+   OffsetVarNodes((Node *) rule_action->havingQual, 
-+                  rt_length);
-                            .
-                            .
-                            .
-    ChangeVarNodes(rule_qual, 
-                   PRS2_CURRENT_VARNO + rt_length, 
-                   rt_index, 0);
-
-+   ChangeVarNodes((Node *) rule_action->groupClause,
-+                  PRS2_CURRENT_VARNO + rt_length, 
-+                  rt_index, 0);
-+   ChangeVarNodes((Node *) rule_action->havingQual,
-+                  PRS2_CURRENT_VARNO + rt_length, 
-+                  rt_index, 0);
-                            .
-                            .
-                            .
-\end{verbatim}
-\pagebreak
-\begin{verbatim}
-    if (*modified && !badsql) 
-    {
-      AddQual(parsetree, rule_action->qual);
-+     /* This will only work if the query made to the 
-+      * view defined by the following groupClause 
-+      * groups by the same attributes or does not use 
-+      * groups at all! 
-+      */
-+      if (parsetree->groupClause == NULL)
-+         parsetree->groupClause = 
-+                    rule_action->groupClause;
-+      AddHavingQual(parsetree, 
-+                    rule_action->havingQual);
-+      parsetree->hasAggs = 
-+         (rule_action->hasAggs || parsetree->hasAggs);
-+      parsetree->hasSubLinks = 
-+         (rule_action->hasSubLinks || 
-+          parsetree->hasSubLinks);
-    }
-  }
-\end{verbatim}
-%
-<step> {\tt QueryRewriteSubLink()} \\
-This function is called by {\tt QueryRewrite()} to process possibly
-contained subqueries first. It searches for nested queries by
-recursively tracing through the {\it parsetree} given as argument. The
-additional statement makes sure that the {\it having clause} is also
-examined.
-%
-\begin{verbatim}
-  static void
-  QueryRewriteSubLink(Node *node)
-  {
-    if (node == NULL)
-       return;
-    switch (nodeTag(node))
-    {
-      case T_SubLink:
-      {
-                            .
-                            .
-                            .
-         QueryRewriteSubLink((Node *) query->qual);
-+        QueryRewriteSubLink((Node *) 
-+                            query->havingQual);
-                            .
-                            .
-                            .
-      }
-                            .
-                            .
-                            .
-    }
-    return;
-  }
-\end{verbatim}
-%
-\pagebreak
-%
-<step> {\tt QueryRewrite()} \\
-This function takes the {\it parsetree} of a query and rewrites it
-using <productname>PostgreSQL</productname>'s {\it rewrite system}. Before the query itself can be
-rewritten, subqueries that are possibly part of the query have to be
-processed. Therefore the function {\tt  QueryRewriteSubLink()} is
-called for the {\it where clause} and for the {\it having clause}.
-%
-\begin{verbatim}
-  List *
-  QueryRewrite(Query *parsetree)
-  {
-    QueryRewriteSubLink(parsetree->qual);       
-+   QueryRewriteSubLink(parsetree->havingQual);
-    return QueryRewriteOne(parsetree);
-  } 
-\end{verbatim}
-%
-\end{itemize}
-%
-Here we present the changes applied to the functions that are contained
-in the file {\tt $\ldots$/src/backend/rewrite/rewriteManip.c}:
-%
-\begin{itemize}
-%
-<step> {\tt OffsetVarNodes()} \\
-Recursively steps through the {\it parsetree} given as the first
-argument and increments the {\tt varno} and {\tt varnoold} fields of
-every {\tt VAR} node found by the {\it offset} given as the second
-argument. The additional statements are necessary to be able to handle
-{\tt GroupClause} nodes and {\tt Sublink} nodes that may appear in the {\it
-parsetree} from now on.
-%
-\begin{verbatim}
-  void
-  OffsetVarNodes(Node *node, int offset)
-  {
-     if (node == NULL)
-        return;
-     switch (nodeTag(node))
-     {
-                            .
-                            .
-                            .
-+       /* This has to be done to make queries using 
-+        * groupclauses work on views 
-+        */
-+        case T_GroupClause:
-+        {
-+          GroupClause *group = (GroupClause *) node;
-+                         
-+          OffsetVarNodes((Node *)(group->entry), 
-+                         offset);
-+        }
-+        break;
-                            .
-                            .
-                            .
-+        case T_SubLink:
-+        {
-+          SubLink *sublink = (SubLink *) node;
-+          List *tmp_oper, *tmp_lefthand;                               
-+
-\end{verbatim}
-\pagebreak
-\begin{verbatim}
-+          /* We also have to adapt the variables used 
-+           * in sublink->lefthand and sublink->oper 
-+           */
-+          OffsetVarNodes((Node *)(sublink->lefthand), 
-+                         offset);
-+
-+          /* Make sure the first argument of 
-+           * sublink->oper points to the same var as 
-+           * sublink->lefthand does otherwise we will 
-+           * run into troubles using aggregates (aggno 
-+           * will not be set correctly) 
-+           */
-+          tmp_lefthand = sublink->lefthand;                            
-+          foreach(tmp_oper, sublink->oper)
-+          {                                
-+            lfirst(((Expr *)lfirst(tmp_oper))->args) = 
-+                                  lfirst(tmp_lefthand);
-+            tmp_lefthand = lnext(tmp_lefthand);
-+          }                                                            
-+        }
-+        break;
-                            .
-                            .
-                            .
-     }
-  }
-\end{verbatim}
-%
-<step> {\tt ChangeVarNodes()} \\
-This function is similar to the above described function {\tt
-OffsetVarNodes()} but instead of incrementing the fields {\tt varno}
-and {\tt varnoold} of {\it all} {\tt VAR} nodes found, it processes
-only those {\tt VAR} nodes whose {\tt varno} value matches the
-parameter {\tt old\_varno} given as argument and whose {\tt
-varlevelsup} value matches the parameter {\tt sublevels\_up}. Whenever
-such a node is found, the {\tt varno} and {\tt varnoold} fields are
-set to the value given in the parameter {\tt new\_varno}. The
-additional statements are necessary to be able to handle {\tt GroupClause}
-and {\tt Sublink} nodes.
-%
-\begin{verbatim}
-  void
-  ChangeVarNodes(Node *node, int old_varno, 
-                 int new_varno, int sublevels_up)
-  {
-    if (node == NULL)
-       return;
-    switch (nodeTag(node))
-    {
-                            .
-                            .
-                            .
-+     /* This has to be done to make queries using 
-+      * groupclauses work on views */
-+     case T_GroupClause:
-+     {
-+       GroupClause  *group = (GroupClause *) node;
-+                       
-\end{verbatim}
-\pagebreak
-\begin{verbatim}  
-+       ChangeVarNodes((Node *)(group->entry),
-+                      old_varno, new_varno, 
-+                      sublevels_up);
-+     }
-+     break;
-                            .
-                            .
-                            .
-      case T_Var:
-      {
-                            .
-                            .
-                            .
-        /* This is a hack: Whenever an attribute
-         * from the "outside" query is used within
-         * a nested subquery, the varlevelsup will 
-         * be >0. Nodes having varlevelsup > 0 are  
-         * forgotten to be processed. The call to 
-         * OffsetVarNodes() should really be done at 
-         * another place but this hack makes sure 
-         * that also those VAR nodes are processed.
-         */
-+       if (var->varlevelsup > 0) 
-+          OffsetVarNodes((Node *)var,3);
-      }
-      break;
-                            .
-                            .
-                            .
-      case T_SubLink:
-      {
-                            .
-                            .
-                            .
-+       ChangeVarNodes((Node *) query->havingQual, 
-+                      old_varno, new_varno,
-+                      sublevels_up);
-+       ChangeVarNodes((Node *) query->targetList, 
-+                      old_varno, new_varno,
-+                      sublevels_up);
-+
-+       /* We also have to adapt the variables used in 
-+        * sublink->lefthand and sublink->oper 
-+        */
-+       ChangeVarNodes((Node *) (sublink->lefthand), 
-+                      old_varno, new_varno,
-+                      sublevels_up);
-      }
-      break;
-                            .
-                            .
-                            .
-    }
-  }
-\end{verbatim}
-%
-<step> {\tt AddHavingQual()} \\
-This function adds the {\it operator tree} given by the parameter {\tt
-havingQual} to the one attached to the field {\tt havingQual} of the
-{\it parsetree} given by the parameter {\tt parsetree}. This is done
-by adding a new {\tt AND} node and attaching the old and the new {\it
-operator tree} as arguments to it. {\tt AddHavingQual()} has not been
-existing until version 6.3.2. It has been created for the {\it having logic}.
-%
-\begin{verbatim}
-  void
-  AddHavingQual(Query *parsetree, Node *havingQual)
-  {
-    Node  *copy, *old;
-
-    if (havingQual == NULL)
-       return;
-
-    copy = havingQual;
-
-    old = parsetree->havingQual;
-    if (old == NULL)
-        parsetree->havingQual = copy;
-    else
-        parsetree->havingQual =
-            (Node *) make_andclause(
-                       makeList(parsetree->havingQual, 
-                                copy, -1));
-  }
-\end{verbatim}
-%
-<step> {\tt AddNotHavingQual()} \\
-This function is similar to the above described function  {\tt
-AddHavingQual()}. It also adds the {\it operator tree} given by the
-parameter {\tt havingQual} but prefixes it by a {\tt NOT} node. {\tt
-AddNotHavingQual()} has also not been existing until version 6.3.2 and has been
-created for the {\it having logic}.
-%
-\begin{verbatim}
-  void
-  AddNotHavingQual(Query *parsetree, 
-                   Node *havingQual)
-  {
-    Node *copy;
-
-    if (havingQual == NULL)
-       return;
-
-    copy = (Node *) make_notclause((Expr *)havingQual);
-    AddHavingQual(parsetree, copy);
-}
-\end{verbatim}
-%
-<step> {\tt nodeHandleViewRule()} \\
-This function is called by {\tt HandleViewRule()}. It replaces all
-{\tt VAR} nodes of the {\it user query} evaluated against the {\it
-view} (the fields of these {\tt VAR} nodes represent the positions of
-the attributes in the {\it virtual} table) by {\tt VAR} nodes that
-have already been prepared to represent the positions of the
-corresponding attributes in the {\it physical} tables (given in the
-{\it view definition}). The additional statements make sure that {\tt
-GroupClause} nodes and {\tt Sublink} nodes are handled correctly.
-
-\begin{verbatim}
-  static void
-  nodeHandleViewRule(Node **nodePtr, List *rtable, 
-                     List *targetlist, int rt_index,
-                     int *modified, int sublevels_up)
-  {
-    Node *node = *nodePtr;
-    if (node == NULL)
-       return;
-    switch (nodeTag(node))
-    {
-                            .
-                            .
-                            .
-+     /* This has to be done to make queries using 
-+      * groupclauses work on views 
-+      */
-+     case T_GroupClause:
-+     {
-+       GroupClause  *group = (GroupClause *) node;
-+       nodeHandleViewRule((Node **) (&(group->entry)), 
-+                          rtable, targetlist, rt_index, 
-+                          modified, sublevels_up);
-+     }
-+     break;
-                            .
-                            .
-                            .
-      case T_Var:
-      {
-                            .
-                            .
-                            .
-        if (n == NULL)
-        {
-          *nodePtr = make_null(((Var *)node)->vartype);
-        }                           
-        else
-+       /* This is a hack: The varlevelsup of the 
-+        * original variable and the new one should 
-+        * be the same. Normally we adapt the node 
-+        * by changing a pointer to point to a var 
-+        * contained in 'targetlist'. In the 
-+        * targetlist all varlevelsups are 0 so if 
-+        * we want to change it to the original 
-+        * value we have to copy the node before! 
-+        * (Maybe this will cause troubles with some 
-+        * sophisticated queries on views?) 
-+        */
-+       {
-+         if(this_varlevelsup>0)
-+         {
-+            *nodePtr = copyObject(n);
-+         }
-+         else 
-+         {
-+           *nodePtr = n;
-+         }
-+         ((Var *)*nodePtr)->varlevelsup = 
-+                            this_varlevelsup;
-+       }
-        *modified = TRUE;
-      }
-      break;
-                            .
-                            .
-                            .
-      case T_SubLink:
-      {
-                            .
-                            .
-                            .
-+       nodeHandleViewRule(
-+                 (Node **) &(query->havingQual), 
-+                 rtable, targetlist, rt_index, 
-+                 modified, sublevels_up);
-+       nodeHandleViewRule(
-+                 (Node **) &(query->targetList), 
-+                 rtable, targetlist, rt_index, 
-+                 modified, sublevels_up);
-+       /* We also have to adapt the variables used 
-+        * in sublink->lefthand and sublink->oper 
-+        */
-+       nodeHandleViewRule(
-+                 (Node **) &(sublink->lefthand), 
-+                 rtable, targetlist, rt_index, 
-+                 modified, sublevels_up);                              
-+       /* Make sure the first argument of 
-+        * sublink->oper points to the same var as 
-+        * sublink->lefthand does otherwise we will 
-+        * run into troubles using aggregates 
-+        * (aggno will not be set correctly!)
-+        */                             
-+       pfree(lfirst(((Expr *) 
-+                    lfirst(sublink->oper))->args));
-+       tmp_lefthand = sublink->lefthand;                               
-+       foreach(tmp_oper, sublink->oper)
-+       {                                   
-+          lfirst(((Expr *) lfirst(tmp_oper))->args) = 
-+                                  lfirst(tmp_lefthand);
-+          tmp_lefthand = lnext(tmp_lefthand);
-+       }                                                               
-      }
-      break;
-                            .
-                            .
-                            .
-    }
-  }
-\end{verbatim}
-%
-<step> {\tt HandleViewRule()} \\
-This function calls {\tt nodeHandleViewRule()} for the {\it where
-clause}, the {\it targetlist}, the {\it group clause} and the {\it
-having clause} of the {\it user query} evaluated against the given
-{\it view}.
-%
-\begin{verbatim}
-  void
-  HandleViewRule(Query *parsetree, List *rtable,
-                 List *targetlist, int rt_index,
-                 int *modified)
-  {
-                            .
-                            .
-                            .
-+   /* The variables in the havingQual and 
-+    * groupClause also have to be adapted 
-+    */
-+   nodeHandleViewRule(&parsetree->havingQual, rtable, 
-+                      targetlist, rt_index,
-+                      modified, 0);
-+   nodeHandleViewRule(
-+           (Node **)(&(parsetree->groupClause)), 
-+           rtable, targetlist, rt_index, modified, 0);
-  }
-\end{verbatim}
-%
-\end{itemize}
-%
-The following function is contained in {\tt
-$\ldots$/src/backend/commands/view.c}:
-
-\begin{itemize}
-%
-<step> {\tt UpdateRangeTableOfViewParse()} \\
-This function updates the {\it range table} of the {\it parsetree}
-given by the parameter {\tt viewParse}. The additional statement makes
-sure that the {\tt VAR} nodes of the {\it having clause} are modified
-in the same way as the {\tt VAR} nodes of the {\it where clause} are.
-%
-\begin{verbatim}
-  static void
-  UpdateRangeTableOfViewParse(char *viewName, 
-                              Query *viewParse)
-  {
-                            .
-                            .
-                            .
-    OffsetVarNodes(viewParse->qual, 2);
-
-+   OffsetVarNodes(viewParse->havingQual, 2);
-                            .
-                            .
-                            .
-  }
-\end{verbatim}
-%
-\end{itemize}
-
-
-\subsubsection{Planner/Optimizer}
-
-The {\it planner} builds a {\it queryplan} like the one shown in
-figure \ref{plan_having} and in addition to that it takes the {\it operator
-tree} attached to the field {\tt havingClause} of the {\tt Query} node
-and attaches is to the {\tt qpqual} field of the {\tt AGG}
-node. 
-
-Unfortunately this is not the only thing to do. Remember from section
-\ref{aggregates} {\it How Aggregate Functions are Implemented} that
-the {\it targetlist} is searched for {\it aggregate functions} that
-are appended to a list that will be attached to the field {\tt aggs}
-of the {\tt AGG} node. This was sufficient as long as {\it aggregate
-functions} have only been allowed to appear within the {\it
-targetlist}. Now the {\it having clause} is another source of {\it
-aggregate functions}. Consider the following example:
-%
-\begin{verbatim}
-  select sno, max(pno)
-  from sells
-  group by sno
-  having count(pno) > 1;
-\end{verbatim}
-%
-Here the {\it aggregate functions} {\tt max} and {\tt count} are in
-use. If only the {\it targetlist} is scanned (as it was the case before the
-{\it having clause} had been implemented) we will only find and process the
-{\it aggregate function} {\tt max}. The second function {\tt count} is
-not processed and therefore any reference to the result of {\tt count}
-from within the {\it having clause} will fail. The solution to this
-problem is to scan the whole {\it operator tree} representing the {\it having
-clause} for {\it aggregate functions} not contained in the {\it targetlist} yet
-and add them to the list of {\it aggregate functions} attached to the
-field {\tt aggs} of the {\tt AGG} node. The scanning is done by the
-function \mbox{{\tt check\_having\_qual\_for\_aggs()}} which steps
-recursively through the tree.\\
-\\
-While scanning the {\it having clause} for {\it aggregate functions}
-not contained in the {\it targetlist} yet, an additional check is made to
-make sure that {\it aggregate functions} are used within
-the {\it having clause} (otherwise the query could have been
-formulated using the {\it where clause}). Consider the following query
-which is not a valid SQL92 query:
-%
-\begin{verbatim}
-  testdb=> select sno, max(pno)
-  testdb-> from sells
-  testdb-> group by sno
-  testdb-> having sno > 1;
-  ERROR:  This could have been done in a where clause!!
-  testdb=>
-\end{verbatim}
-%
-There is no need to express this query using a {\it having clause},
-this kind of qualification belongs to the {\it where clause}:
-%
-\begin{verbatim}
-  select sno, max(pno)
-  from sells
-  where sno > 1
-  group by sno;
-\end{verbatim}
-%
-There is still an unsolved problem left. Consider the following query
-where we want to know just the supplier numbers ({\tt sno}) of all
-suppliers selling more than one part:
-%
-\begin{verbatim}
-  select sno
-  from sells
-  group by sno
-  having count(pno) > 1;
-\end{verbatim}
-%
-The {\it planner} creates a {\it queryplan} (like the one shown in figure
-\ref{plan_having}) where the {\it targetlists} of all nodes involved contain
-only entries of those attributes listed after the {\tt select} keyword of
-the query. Looking at the example above this means that the
-{\it targetlists} of the {\tt AGG} node, the {\tt GRP} node the {\tt SORT}
-node and the {\tt SeqScan} node contain only the entry for the
-attribute {\tt sno}. As described earlier the {\it aggregation logic}
-operates on attributes of the tuples returned by the subplan of
-the {\tt AGG} node (i.e. the result of the {\tt GRP} node). Which
-attributes are contained in the tuples handed back by a subplan is
-determined by the {\it targetlist}. In the case of our example the attribute
-{\tt pno} needed for the {\it aggregate function} {\tt count} is not
-included and therefore the {\it aggregation} will fail. 
-
-\pagebreak
-
-\noindent The solution to this problem is given in the following
-steps:
-\begin{itemize}
-<step> Make a copy of the actual {\it targetlist} of the {\tt AGG} node.
-%
-<step> Search the {\it operator tree} representing the {\it having clause}
-for attributes that are not contained in the {\it targetlist} of the {\tt
-AGG} node yet and add them to the previously made copy.
-%
-<step> The extended {\it targetlist} is used to create the subplan attached to
-the {\tt lefttree} field of the {\tt AGG} node. That means that the
-{\it targetlists} of the {\tt GRP} node, of the {\tt SORT} node and of the
-{\tt SeqScan} node will now contain an entry for the attribute {\tt
-pno}. The {\it targetlist} of the {\tt AGG} node itself will not be changed
-because we do not want to include the attribute {\tt pno} into the
-result returned by the whole query.
-%
-\end{itemize}
-Care has to be taken that the {\tt varattno} fields of the {\tt VAR}
-nodes used in the {\it targetlists} contain the position of the
-corresponding attribute in the  {\it targetlist} of the subplan (i.e the
-subplan delivering the tuples for further processing by the actual
-node). \\
-\\
-The following part deals with the source code of the new and
-changed functions involved in the planner/optimizer stage. The files
-affected are: \\
-\\
-\indent {\tt $\ldots$/src/backend/optimizer/plan/setrefs.c} \\
-\indent {\tt $\ldots$/src/backend/optimizer/plan/planner.c} \\
-\\
-Since all of the functions presented here are very long and would need
-very much space if presented as a whole, we just list the most
-important parts. \\
-\\
-The following two functions are new and have been
-introduced for the {\it having logic}. They are contained in the file
-{\tt $\ldots$/src/backend/optimizer/plan/setrefs.c}:
-%
-\begin{itemize}
-%
-<step> {\tt check\_having\_qual\_for\_aggs()} \\
-This function takes the representation of a {\it having clause} given
-by the parameter {\tt clause}, a {\it targetlist} given by the
-parameter {\tt subplanTargetList} and a {\it group clause} given by
-the parameter {\tt groupClause} as arguments and scans the
-representation of the {\it having clause} recursively for {\it
-aggregate functions}. If an {\it aggregate function} is found it is
-attached to a list (internally called {\tt agg\_list}) and finally
-returned by the function. 
-
-Additionally the {\tt varno} field of every {\tt VAR} node found is
-set to the position of the corresponding attribute in the {\it
-targetlist} given by {\tt subplanTargetList}.
-
-If the {\it having clause} contains a subquery the function also makes
-sure, that every attribute from the {\it main query} that is used
-within the subquery also appears in the {\it group clause} given by
-{\tt groupClause}. If the attribute cannot be found in the {\it group
-clause} an error message is printed to the screen and the query
-processing is aborted.
-%
-\begin{verbatim}
-  List *
-  check_having_qual_for_aggs(Node *clause, 
-                             List *subplanTargetList, 
-                             List *groupClause)
-  {
-    List *t, *l1;
-    List *agg_list = NIL;  
-    int  contained_in_group_clause = 0;
-  
-    if (IsA(clause, Var))
-    {
-      TargetEntry *subplanVar;      
-
-      subplanVar = match_varid((Var *) clause, 
-                               subplanTargetList);      
-      /* Change the varattno fields of the 
-       * var node to point to the resdom->resnofields 
-       * of the subplan (lefttree) 
-       */         
-      ((Var *) clause)->varattno = 
-        subplanVar->resdom->resno;      
-      return NIL;      
-    }
-    else 
-      if (is_funcclause(clause) || not_clause(clause)  
-          || or_clause(clause) || and_clause(clause))
-      {
-        int new_length=0, old_length=0;        
-
-        /* This is a function. Recursively call this 
-         * routine for its arguments... (i.e. for AND, 
-         * OR, ... clauses!)
-         */
-        foreach(t, ((Expr *) clause)->args)
-        {
-          old_length=length((List *)agg_list);          
-          agg_list = nconc(agg_list,
-              check_having_qual_for_aggs(lfirst(t), 
-                                 subplanTargetList,
-                                 groupClause));          
-          if(((new_length=length((List *)agg_list)) == 
-              old_length) || (new_length == 0))
-          {
-            elog(ERROR,"This could have been done 
-                                 in a where clause!!");
-            return NIL;
-          } 
-        }
-        return agg_list;
-      }
-      else 
-        if (IsA(clause, Aggreg))
-        {
-          return lcons(clause,
-                        check_having_qual_for_aggs(
-                            ((Aggreg *)clause)->target, 
-                            subplanTargetList,
-                            groupClause));                
-        }
-        else 
-                            .
-                            .
-                            .
-  }
-\end{verbatim}
-%
-<step> {\tt check\_having\_qual\_for\_vars()} \\
-This function takes the representation of a {\it having clause} given
-by the parameter {\tt clause} and the actual {\it targetlist}
-given by the parameter {\tt targetlist\_so\_far} as arguments and
-recursively scans the representation of the {\it having clause} for
-attributes that are not included in the actual {\it targetlist}
-yet. Whenever such an attribute is found it is added to the actual
-{\it targetlist} which is finally returned by the function.
-
-Attributes contained in the {\it having clause} but not in the {\it
-targetlist} show up with queries like:
-%
-\begin{verbatim}
-  select sid 
-  from  part 
-  group by sid 
-  having min(pid) > 1;
-\end{verbatim}
-%
-In the above query the attribute {\tt pid} is used in the {\it having
-clause} but it does not appear in the {\it targetlist} (i.e. the list
-of attributes after the keyword {\tt select}). Unfortunately only
-those attributes are delivered by the subplan and can therefore be
-used within the {\it having clause}. To become able to handle queries
-like that correctly, we have to extend the actual {\it targetlist} by
-those attributes used in the {\tt having clause} but not already
-appearing in the {\it targetlist}.
-%
-\begin{verbatim}
-  List *
-  check_having_qual_for_vars(Node *clause, 
-                             List *targetlist_so_far)
-  {
-    List     *t;
-
-    if (IsA(clause, Var))
-    {
-      Rel         tmp_rel;
-      
-      tmp_rel.targetlist = targetlist_so_far;
-      /* Check if the VAR is already contained in the 
-       * targetlist 
-       */
-      if (tlist_member((Var *)clause, 
-                  (List *)targetlist_so_far) == NULL)
-      {
-        add_tl_element(&tmp_rel, (Var *)clause); 
-      }             
-      return tmp_rel.targetlist;
-    }
-    else 
-      if (is_funcclause(clause) || not_clause(clause)
-          || or_clause(clause) || and_clause(clause))
-      {
-        /* This is a function. Recursively call this 
-         * routine for its arguments...
-         */
-        foreach(t, ((Expr *) clause)->args)
-        {
-          targetlist_so_far = 
-            check_having_qual_for_vars(lfirst(t), 
-                            targetlist_so_far);
-        }
-        return targetlist_so_far;
-      }
-      else 
-        if (IsA(clause, Aggreg))
-        {
-          targetlist_so_far = 
-            check_having_qual_for_vars(
-                            ((Aggreg *)clause)->target, 
-                            targetlist_so_far);
-          return targetlist_so_far;
-        }
-                            .
-                            .
-                            .
-  }
-\end{verbatim}
-%
-\end{itemize}
-%
-The next function is found in {\tt
-$\ldots$/src/backend/optimizer/plan/planner.c}:
-%
-\begin{itemize}
-%
-<step> {\tt union\_planner()} \\
-This function creates a {\it plan} from the {\it parsetree} given to
-it by the parameter {\tt parse} that can be executed by the {\it
-executor}. 
-
-If {\it aggregate functions} are present (indicated by {\tt
-parse->hasAggs} set to true) the first step is to extend the {\it
-targetlist} by those attributes that are used within the {\it having
-clause} (if any is present) but do not appear in the {\it select list}
-(Refer to the description of {\tt check\_having\_qual\_for\_vars()}
-above).
-
-The next step is to call the function {\tt query\_planner()} creating
-a {\it plan} without taking the {\it group clause}, the {\it aggregate
-functions} and the {\it having clause} into account for the moment.
-
-Next insert a {\tt GRP} node at the top of the {\it plan} according
-to the {\it group clause} of the {\it parsetree} if any is present.  
-
-Add an {\tt AGG} node to the top of the current {\it plan} if {\it
-aggregate functions} are present and if a {\it having clause} is
-present additionally perform the following steps:
-%
-\begin{itemize}
-<step> Perform various transformations to the representation of the
-{\it having clause} (e.g. transform it to CNF, $\ldots$).
-<step> Attach the transformed representation of the {\it having clause} to the
-field {\tt plan.qual} of the just created {\tt AGG} node.
-<step> Examine the whole {\it having clause} and search for {\it
-aggregate functions}. This is done using the function {\tt
-check\_having\_qual\_for\_aggs()} which appends every {\it aggregate
-function} found to a list that is finally returned.
-<step> Append the list just created to the list already attached to the
-field {\tt aggs} of the {\tt AGG} node (this list contains the {\it
-aggregate functions} found in the {\it targetlist}).
-<step> Make sure that  {\it aggregate functions} do appear in the 
-{\it having clause}. This is done by comparing the length of the list
-attached to {\tt aggs} before and after the call to {\tt
-check\_having\_qual\_for\_aggs()}.  If the length has not changed, we
-know that no {\it aggregate function} has been detected and that this
-query could have been formulated using only a {\it where clause}. In
-this case an error message is printed to the screen and the processing
-is aborted.
-\end{itemize}
-%
-\pagebreak
-%
-\begin{verbatim}
-  Plan *
-  union_planner(Query *parse)
-  {
-     List       *tlist = parse->targetList;
-
-+    /* copy the original tlist, we will need the 
-+     * original one for the AGG node later on */
-+     List *new_tlist = new_unsorted_tlist(tlist); 
-                            .
-                            .
-                            .
-+         if (parse->hasAggs)
-+         {
-+           /* extend targetlist by variables not
-+            * contained already but used in the 
-+            * havingQual.
-+            */
-+           if (parse->havingQual != NULL)
-+             {
-+               new_tlist = 
-+                 check_having_qual_for_vars(
-+                              parse->havingQual,
-+                              new_tlist);
-+             }
-+         }          
-                            .
-                            .
-                            .
-          /* Call the planner for everything
-           * but groupclauses and aggregate funcs. 
-           */
-          result_plan = query_planner(parse,
-                                  parse->commandType,
-                                  new_tlist,
-                                  (List *) parse->qual);
-                            .
-                            .
-                            .
-        /* If aggregate is present, insert the AGG node
-         */
-        if (parse->hasAggs)
-        {
-          int old_length=0, new_length=0;                
-          /* Create the AGG node but use 'tlist' not 
-           * 'new_tlist' as target list because we
-           * don't want the additional attributes 
-           * (only used for the havingQual, see 
-           * above) to show up in the result. 
-           */
-          result_plan = (Plan *) make_agg(tlist, 
-                                       result_plan);
-                            .
-                            .
-                            .
-+         /* Check every clause of the havingQual for 
-+          * aggregates used and append them to 
-+          * the list in result_plan->aggs 
-+          */
-+         foreach(clause, 
-+                 ((Agg *) result_plan)->plan.qual)
-+         {
-+           /* Make sure there are aggregates in the 
-+            * havingQual if so, the list must be 
-+            * longer after check_having_qual_for_aggs 
-+            */
-+           old_length = 
-+             length(((Agg *) result_plan)->aggs);                 
-+                       
-+           ((Agg *) result_plan)->aggs = 
-+              nconc(((Agg *) result_plan)->aggs,
-+                    check_having_qual_for_aggs(
-+                      (Node *) lfirst(clause),
-+                      ((Agg *)result_plan)->
-+                          plan.lefttree->targetlist,
-+                      ((List *) parse->groupClause)));
-+           /* Have a look at the length of the returned 
-+            * list. If there is no difference, no 
-+            * aggregates have been found and that means 
-+            * that the Qual belongs to the where clause 
-+            */
-+           if (((new_length = 
-+                 length(((Agg *) result_plan)->aggs))== 
-+                 old_length) || (new_length == 0))
-+           {
-+             elog(ERROR,"This could have been done in a 
-+                                      where clause!!");
-+             return (Plan *)NIL;
-+           }
-+         }
-                            .
-                            .
-                            .
-  }
-\end{verbatim}
-%
-\end{itemize}
-
-\subsubsection{Executor}
-
-The {\it executor} takes the {\it queryplan} produced by the {\it
-planner/optimizer} in the way just described and processes all {\it
-aggregate functions} in the way described in section \ref{aggregates}
-{\it The Implementation of Aggregate Functions} but before the tuple
-derived is handed back the {\it operator tree} attached to the field
-{\tt qpqual} is evaluated by calling the function {\tt
-ExecQual()}. This function recursively steps through the {\it operator
-tree} (i.e. the {\it having clause}) and evaluates the predicates
-appearing there. Thanks to our changes that have been made to the {\it
-planner} the values of all operands needed to evaluate the predicates
-(e.g. the values of all {\it aggregate functions}) are already present
-and can be accessed throughout the evaluation without any problems.
-
-If the evaluation of the {\it having qualification} returns {\tt true}
-the tuple is returned by the function {\tt execAgg()} otherwise it is
-ignored and the next group is processed. \\
-\\
-The necessary changes and enhancements have been applied to the
-following function in the file {\tt
-$\ldots$/src/backend/executor/nodeAgg.c}:
-%
-\begin{itemize}
-%
-<step> {\tt execAgg()}
-Whenever the {\it executor} gets to an {\tt AGG} node this function is
-called. Before the {\it having logic} had been implemented, all the
-{\it tuples} of the current group were fetched from the {\it
-subplan} and all {\it aggregate functions} were applied to these
-tuples. After that, the results were handed back to the calling
-function.
-
-Since the {\it having logic} has been implemented there is one
-additional step executed. Before the results of applying the {\it
-aggregate functions} are handed back, the function {\tt ExecQual()} is
-called with the representation of the {\it having clause} as an
-argument. If {\tt true} is returned, the results are handed back,
-otherwise they are ignored and we start from the beginning for the
-next group until a group meeting the restrictions given in the {\it
-having clause} is found.
-%
-\begin{verbatim}
-  TupleTableSlot *
-  ExecAgg(Agg *node)
-  {
-                            .
-                            .
-                            .
-        /* We loop retrieving groups until we find one 
-         * matching node->plan.qual 
-         */
-+       do 
-+       { 
-                            .
-                            .
-                            .
-          /* Apply *all* aggregate function to the 
-           * tuples of the *current* group 
-           */
-                            .
-                            .
-                            .
-          econtext->ecxt_scantuple = 
-                   aggstate->csstate.css_ScanTupleSlot;
-          resultSlot = ExecProject(projInfo, &isDone);
-
-+         /* As long as the retrieved group does not 
-+          * match the qualifications it is ignored and
-+          * the next group is fetched 
-+          */   
-+         if(node->plan.qual != NULL)
-+         {
-+           qual_result =
-+               ExecQual(node->plan.qual,
-+                        econtext);
-+         }     
-+         if (oneTuple) pfree(oneTuple);
-+       } 
-+       while((node->plan.qual!=NULL) && 
-+                               (qual_result!=true));   
-        return resultSlot;
-  }
-\end{verbatim}
-%
-\end{itemize}
-
-\section{The Realization of Union, Intersect and Except}
-\label{union_impl}
-
-SQL92 supports the well known set theoretic operations {\it union},
-{\it intersect} and {\it set difference} (the {\it set difference} is
-called {\it except} in SQL92). The operators are used to connect two
-or more {\tt select} statements. Every {\tt select} statement returns
-a set of tuples and the operators between the {\tt select} statements
-tell how to merge the returned sets of tuples into one result
-relation.
-%
-\begin{example}
-\label{simple_set_ops}
-Let the following tables be given:
-%
-\begin{verbatim}
-
-XXX All these table examples have combinations of "-" and "+" which
-causes problems inside an SGML comment. Mess them up to keep this
-from happening for now. - thomas 1999-02-10
-
-              A  C1|C2|C3         B  C1|C2|C3
-                 MMPMMPMM            MMPMMPMM
-                  1| a| b             1| a| b
-                  2| a| b             5| a| b
-                  3| c| d             3| c| d
-                  4| e| f             8| e| f
-
-                         C  C1|C2|C3
-                            MMPMMPMM
-                             4| e| f
-                             8| e| f
-\end{verbatim}
-Now let's have a look at the results of the following queries:
-\begin{verbatim}
-  select * from A
-  union
-  select * from B;
-\end{verbatim}
-derives the set theoretic {\it union} of the two tables:
-%
-\begin{verbatim}
-                            C1|C2|C3        
-                            MMPMMPMM        
-                             1| a| b        
-                             2| a| b        
-                             3| c| d        
-                             4| e| f        
-                             5| a| b
-                             8| e| f
-\end{verbatim}
-%
-The {\tt select} statements used may be more complex:
-%
-\begin{verbatim}
-  select C1, C3 from A
-    where C2 = 'a'
-  union
-  select C1, C2 from B
-    where C3 = 'b';
-\end{verbatim}
-%
-
-\noindent will return the following table:
-%
-\begin{verbatim}
-                             C1|C3        
-                             MMPMM        
-                              1| b        
-                              2| b        
-                              1| a        
-                              5| a        
-\end{verbatim}
-%
-Note that the selected columns do not need to have identical names,
-they only have to be of the same type. In the previous example we
-selected for {\tt C1} and {\tt C3} in the first {\tt select} statement
-and for {\tt C1} and {\tt C2} in the second one. The names of the
-resulting columns are taken from the first {\tt select} statement. \\
-\\
-Let's have a look at a query using {\tt intersect}:
-%
-\begin{verbatim}
-  select * from A
-  intersect
-  select * from B;
-\end{verbatim}
-%
-will return:
-\begin{verbatim}
-                            C1|C2|C3        
-                            MMPMMPMM        
-                             1| a| b        
-                             3| c| d        
-\end{verbatim}
-%
-Here is an example using {\tt except}:
-\begin{verbatim}
-  select * from A
-  except
-  select * from B;
-\end{verbatim}
-%
-will return:
-\begin{verbatim}
-                            C1|C2|C3        
-                            MMPMMPMM        
-                             2| a| b
-                             4| e| f        
-\end{verbatim}
-%
-The last examples were rather simple because they only used one set
-operator at a time with only two operands. Now we look at some more
-complex queries involving more {\it operators}:
-%
-\begin{verbatim}
-  select * from A
-  union 
-  select * from B
-  intersect 
-  select * from C;
-\end{verbatim}
-%
-will return:
-%
-\begin{verbatim}
-                            C1|C2|C3        
-                            MMPMMPMM        
-                             4| e| f
-                             8| e| f
-\end{verbatim}
-%
-The above query performs the set theoretic computation $(A \cup B)
-\cap C$. When no parentheses are used, the operations are considered to
-be left associative, i.e. $A \cup B \cup C \cup D$ will be treated as
-$((A \cup B) \cup C) \cup D$. \\
-\\
-The same query using parenthesis can lead to a completely different
-result:
-%
-\begin{verbatim}
-  select * from A
-  union 
-  (select * from B
-   intersect 
-   select * from C);
-\end{verbatim}
-%
-performs  $A \cup (B \cap C)$ and will return:
-%
-\begin{verbatim}
-                            C1|C2|C3        
-                            MMPMMPMM        
-                             1| a| b        
-                             2| a| b        
-                             3| c| d        
-                             4| e| f        
-                             8| e| f
-\end{verbatim}
-%
-\end{example}
-%
-\subsection{How Unions have been Realized Until Version 6.3.2}
-
-First we give a description of the implementation of {\it union} and
-{\it union all} until version 6.3.2 because we need it to understand
-the implementation of {\it intersect} and {\it except} described later. \\
-\\
-A {\it union} query is passed through the usual stages:
-%
-\begin{itemize}
-<step> parser
-<step> rewrite system
-<step> planner/optimizer
-<step> executor
-\end{itemize}
-%
-and we will now describe what every single stage does to the query.
-For our explanation we assume to process a simple query (i.e. a query
-without {\it subselects}, {\it aggregates} and without involving {\it views})
-
-\subsubsection{The Parser Stage}
-
-As described earlier the {\it parser stage} can be divided into two parts:
-%
-\begin{itemize}
-<step> the {\it parser} built up by the grammar rules given in {\tt gram.y}
-and
-<step> the {\it transformation routines} performing a lot of 
-changes and analysis to the tree built up by the parser. Most of these
-routines reside in {\tt analyze.c}.
-\end{itemize}
-%
-%\pagebreak 
-%
-A {\it union} statement consists of two or more {\it select}
-statements connected by the keyword {\tt union} as the following
-example shows:
-%
-\begin{verbatim}
-  select * from A 
-    where C1=1
-  union
-  select * from B
-    where C2 = 'a'
-  union
-  select * from C
-    where C3 = 'f'
-\end{verbatim}
-%
-The above {\it union} statement consists of three {\it select}
-statements connected by the keyword {\tt union}. We will refer to the
-first {\it select} statement by A, to the second one by B and to the
- third one by C for our further explanation (in the new notation our
-query looks like this: \mbox{{\tt A union B union C}}).\\
-\\
-The {\it parser} (given by {\tt gram.y}) processes all three {\tt select}
-statements, creates a {\tt SelectStmt} node for every {\tt select} and
-attaches the {\tt where} qualifications, {\it targetlists} etc.  to the
-corresponding nodes. Then it creates a list of the second and the
-third {\tt SelectStmt} node (of B and C) and attaches it to the field
-{\tt unionClause} of the first node (of A). Finally it hands back the
-first node (node A) with the list of the remaining nodes attached as
-shown in figure \ref{parser_union_back}.
-%
-\begin{figure}
-\begin{center}
-\epsfig{figure=figures/parser_union_back.ps}
-\caption{Data structure handed back by the {\it parser}}
-\label{parser_union_back}
-\end{center}
-\end{figure}
-\\
-\\
-The following {\it transformation routines} process the data structure
-handed back by the {\it parser}. First the top node (node A) is transformed
-from a {\tt SelectStmt} node to a {\tt Query} node.  The {\it
-targetlist}, the {\tt where} qualification etc. attached to it are
-transformed as well. Next the list of the remaining nodes (attached to
-{\tt unionClause} of node A) is transformed and in this step also a
-check is made if the types and lengths of the {\it targetlists} of
-the involved nodes are equal. The new {\tt Query} nodes are now handed
-back in the same way as the {\tt SelectStmt} nodes were before
-(i.e. the {\tt Query} nodes B and C are collected in a list which is
-attached to {\tt unionClause} of {\tt Query} node A).
-
-\subsubsection{The Rewrite System}
-
-If any {\it rewrite rules} are present for the {\tt Query} nodes
-(i.e. one of the {\it select} statements uses a {\it view}) the
-necessary changes to the {\tt Query} nodes are performed (see section
-\ref{view_impl} {\it Techniques To Implement Views}). Otherwise no
-changes are made to the nodes in this stage.
-
-\subsubsection{Planner/Optimizer}
-
-This stage has to create a {\it plan} out of the {\it querytree}
-produced by the {\it parser stage} that can be executed by the {\it
-executor}. In most cases there are several ways (paths) with different
-cost to get to the same result. It's the {\it planner/optimizer's}
-task to find out which path is the cheapest and to create a {\it plan}
-using this path.  The implementation of {\it unions} in <productname>PostgreSQL</productname> is
-based on the following idea: \\
-\\
-The set derived by evaluating $A \cup B$ must contain every member of
-$A$ {\bf and} every member of $B$. So if we append the members of $B$
-to the members of $A$ we are almost done. If there exist members 
-common to $A$ and $B$ these members are now contained twice in our new
-set, so the only thing left to do is to remove these duplicates. 
-
-\pagebreak
-
-\noindent In the case of our example the {\it planner} would build up the {\it
-tree} shown in figure \ref{union_plan}. Every {\tt Query} node is
-planned separately and results in a {\tt SeqScan} node in our
-example. The three {\tt SeqScan} nodes are put together into a list
-which is attached to {\tt unionplans} of an {\tt Append} node.
-%
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/union_plan.ps}
-\caption{{\it Plan} for a union query}
-\label{union_plan}
-\end{center}
-\end{figure}
-
-\subsubsection{Executor}
-
-The {\it executor} will process all the {\tt SeqScan} nodes and append all
-the delivered tuples to a single {\it result relation}. Now it is
-possible that duplicate tuples are contained in the {\it result relation}
-which have to be removed. The removal is done by the {\tt Unique} node
-and the sort is just performed to make its work easier.
-
-\subsection{How Intersect, Except and Union Work Together}  
-
-The last section showed that every stage ({\it parser stage}, {\it
-planner/optimizer}, {\it executor}) of <productname>PostgreSQL</productname> has to provide
-features in order to support {\it union} statements. For the
-implementation of {\it intersect} and {\it except} statements (and
-statements involving all {\it set operators}) we choose a different approach
-based on {\it query rewriting}. \\
-\\
-The idea is based on the fact that {\it intersect} and {\it except}
-statements are redundant in SQL, i.e. for every {\it intersect} or
-{\it except} statement it is possible to formulate a semantically
-equivalent statement without using {\it intersect} or {\it except}.
-%
-\begin{example}
-\label{transform_intersect}
-This example shows how a query using {\it intersect} can be
-transformed to a semantically equivalent query without an {\it
-intersect}:
-%
-\pagebreak
-%
-\begin{verbatim}
-  select C1, C3 from A
-  where C1 = 1
-  intersect
-  select C1, C2 from B
-  where C2 = 'c';
-\end{verbatim}
-%
-is equivalent to:
-%
-\begin{verbatim}
-  select C1, C3
-  from A
-  where C1 = 1 and
-        (C1, C3) in (select C1, C2
-                     from B
-                     where C2 = 'c');
-\end{verbatim}
-%
-This example shows how an {\it except} query can be transformed to an
-{\it except}-less form:
-%
-\begin{verbatim}
-  select C1, C2 from A
-  where C2 = 'c'
-  except
-  select C1, C3 from B
-  where C3 = 'f';
-\end{verbatim}
-%
-is equivalent to:
-%
-\begin{verbatim}
-  select C1, C2
-  from A
-  where C2 = 'c' and
-        (C1, C2) not in (select C1, C3
-                         from B
-                         where C3 = 'f');
-\end{verbatim}
-%
-\end{example}
-%
-The transformations used in example \ref{transform_intersect} are
-always valid because they just implement the set theoretic definition
-of {\it intersect} and {\it except}:
-%
-\begin{definition} 
-\label{def_intersect}
-~ \\
-The {\it intersection} of two sets $A$ and $B$ is
-defined as:
-\begin{displaymath}
-(A \cap B) := \{x \mid x \in A \wedge x \in B \}
-\end{displaymath}
-%
-The {\it intersection} of $n$ sets $A_{1}, \ldots, A_{n}$ is defined as:
-%
-\begin{displaymath}
-\bigcap_{i=1}^{n} A_{i} := \{x \mid \bigwedge_{i=1}^{n} x \in A_{i} \} 
-\end{displaymath}
-%
-\end{definition}
-%
-\begin{definition} 
-\label{def_except}
-~ \\
-The {\it difference} of two sets $A$ and $B$ is
-defined as:
-\begin{displaymath}
-(A \backslash B) := \{x \mid x \in A \wedge x \not\in B \}
-\end{displaymath}
-%
-\end{definition}
-%
-\begin{definition} 
-\label{def_union}
-~\\
-The {\it union} of two sets $A$ and $B$ is
-defined as:
-\begin{displaymath}
-(A \cup B) := \{x \mid x \in A \vee x \in B \}
-\end{displaymath}
-%
-The {\it union} of $n$ sets $A_{1}, \ldots, A_{n}$ is defined as:
-%
-\begin{displaymath}
-\bigcup_{i=1}^{n} A_{i} := \{x \mid \bigvee_{i=1}^{n} x \in A_{i} \} 
-\end{displaymath}
-%
-\end{definition}
-
-\begin{definition} Disjunctive Normal Form (DNF) \\
-Let $F = C_{1} \vee \ldots \vee C_{n}$ be given where every $C_{i}$ is
-of the form $(L_{i}^{1} \wedge \ldots \wedge L_{i}^{k_{i}})$ and
-$L_{i}^{j}$ is a propositional variable or the negation of a
-propositional variable. Now we say $F$ is in DNF.
-\end{definition}
-%
-\begin{example} In the following example the $L_{i}^{j}$ are of the form
-$x \in X$ or $\neg (x \in X)$: \\
-\indent $((x \in A \wedge \neg (x \in B) \wedge x \in C) \vee (x \in D
-\wedge x \in E))$ is a formula in DNF \\
-\indent $((x \in A \vee x \in B) \wedge (x \in C \vee \neg (x \in D)))$
-is not in DNF.
-\end{example}
-%
-The transformation of any formula in propositional logic into DNF is done by
-successively applying the following rules: \\
-\\
-\indent $(R1)~~\neg (F_{1} \vee F_{2}) \Rightarrow (\neg F_{1} \wedge \neg
-F_{2})$ \\
-\indent $(R2)~~\neg (F_{1} \wedge F_{2}) \Rightarrow (\neg F_{1} \vee \neg
-F_{2})$ \\
-\indent $(R3)~~F_{1} \wedge (F_{2} \vee F_{3}) \Rightarrow (F_{1} \wedge
-F_{2}) \vee (F_{1} \wedge F_{3})$ \\
-\indent $(R4)~~(F_{1} \vee F_{2}) \wedge F_{3} \Rightarrow (F_{1} \wedge
-F_{3}) \vee (F_{2} \wedge F_{3})$ \\
-\\
-It can be shown that the transformation using the rules (R1) to
-(R4) always terminates after a finite number of steps.
-
-\subsubsection{Set Operations as Propositional Logic Formulas}
-
-Using the definitions from above we can treat formulas
-involving set theoretic operations as formulas of {\it propositional
-logic}. As we will see later these formulas can easily be used in the
-{\tt where-} and {\tt having} qualifications of the {\tt select}
-statements involved in the query.
-%
-\begin{example}
-Here are some examples: \\ \\
-%
-\indent $((A \cup B) \cap C) := \{x \mid (x \in A \vee x \in B) \wedge x \in C
-\}$ \\
-\indent $((A \cup B) \cap (C \cup D)) := \{x \mid (x \in A \vee x \in B)
-\wedge (x \in C \vee x \in D) \}$ \\
-\indent $((A \cap B) \backslash C) := \{x \mid (x \in A \wedge x \in
-B) \wedge x \not\in C \}$ \\
-\indent $(A \backslash (B \cup C)) := \{x \mid x \in A \wedge \neg (x
-\in B \vee x \in C) \}$ \\
-\indent $(((A \cap B) \cup (C \backslash D)) \cap E) := \{((x \in A
-\wedge x \in B) \vee (x \in C \wedge x \not\in D)) \wedge x \in E \}$
-%
-\end{example}
-%
-\subsection{Implementing Intersect and Except Using the
-Union Capabilities}
-%
-We want to be able to use queries involving more than just one type of
-set operation (e.g. only {\it union} or only {\it intersect}) at a
-time, so we have to look for a solution that supports correct handling
-of queries like that. As described above there is a solution for pure
-{\it union} statements implemented already, so we have to develop an
-approach that makes use of these {\it union} capabilities. \\
-\\
-As figure \ref{parser_union_back} illustrates, the operands of a {\it
-union} operation are just {\tt Query} nodes (the first operand is the
-top node and all further operands form a list which is attached to the
-field {\tt unionClause} of the top node). So our goal will be to
-transform every query involving set operations into this form. (Note
-that the operands to the {\it union} operation may be complex,
-i.e. {\it subselects}, {\it grouping}, {\it aggregates} etc. are allowed.)
-
-The transformation of a query involving set operations in any order
-into a query that can be accepted by the {\it union} logic is
-equivalent to transforming the {\it membership formula} (see
-definitions \ref{def_intersect}, \ref{def_except} and \ref{def_union})
-in propositional logic into {\it disjunctive normal form} (DNF). The
-transformation of any formula in propositional logic into DNF is
-always possible in a finite number of steps.
-
-\noindent The advantage of this {\it transformation technique} is the little
-impact on the whole system and the implicit invocation of the {\it
-planner/optimizer}. The only changes necessary are made to the {\it
-parser stage} and the {\it rewrite system}. \\
-\\
-Here are some changes that had to be applied to the source code before
-the {\it parser stage} and the {\it rewrite system} could be adapted:
-%
-\begin{itemize}
-<step> Add the additional field {\tt intersectClause} to the data
-structures {\tt Query} and {\tt InsertStmt} defined in the file {\tt
-$\ldots$/src/include/nodes/parsenodes.h}:
-%
-\begin{verbatim}
-  typedef struct Query
-  {
-    NodeTag    type;
-    CmdType    commandType;   
-            .
-            .
-            .
-    Node       *havingQual;
-+   List       *intersectClause;    
-    List       *unionClause;       
-    List       *base_relation_list_;
-    List       *join_relation_list_;
-  } Query;
-
-  typedef struct InsertStmt
-  {
-    NodeTag    type;
-            .
-            .
-            .
-    bool       unionall;      
-+   List       *intersectClause;  
-  } InsertStmt;
-\end{verbatim}
-%
-<step> Add the new keywords {\tt EXCEPT} and {\tt INTERSECT} to the
-file {\tt $\ldots$/src/backend/parser/keywords.c}:
-%
-\begin{verbatim}
-  static ScanKeyword ScanKeywords[] = {
-    {"abort", ABORT_TRANS},
-    {"action", ACTION},
-              .
-              .
-              .     
-    {"end", END_TRANS},
-+   {"except", EXCEPT},
-              .
-              .
-              .     
-    {"instead", INSTEAD},
-+   {"intersect", INTERSECT},
-              .
-              .
-              .     
-  };
-\end{verbatim}
-%
-<step> <productname>PostgreSQL</productname> contains functions to convert the internal
-representation of a {\it parsetree} or {\it plantree} into an ASCII
-representation (that can easily be printed to the screen (for
-debugging purposes) or be stored in a file) and vice versa. These
-functions have to be adapted to be able to deal with {\it intersects}
-and {\it excepts}. These functions can be found in the files {\tt
-$\ldots$/src/backend/nodes/outfuncs.c} and {\tt
-$\ldots$/src/backend/nodes/readfuncs.c}:
-%
-\begin{verbatim}
-  static void
-  _outQuery(StringInfo str, Query *node)
-  {
-                            .
-                            .
-                            .
-    appendStringInfo(str, " :unionClause ");
-    _outNode(str, node->unionClause);
-+   appendStringInfo(str, " :intersectClause ");
-+   _outNode(str, node->intersectClause);
-  }
-
-  static Query *
-  _readQuery()
-  {
-                            .
-                            .
-                            .
-    token = lsptok(NULL, &length);
-    local_node->unionClause = nodeRead(true);
-+   token = lsptok(NULL, &length);
-+   local_node->intersectClause = nodeRead(true);
-
-    return (local_node);
-  }
-\end{verbatim}
-%
-<step> The function {\tt ExecReScan()} is called whenever a new
-execution of a given {\it plan} has to be started (i.e. whenever we
-have to start from the beginning with the first tuple again). The call
-to this function happens implicitly. For the special kind of
-subqueries we are using for the rewritten queries (see example
-\ref{transform_intersect}) we have to take that also 
-{\tt Group} nodes are processed. The function can be found in the file
-{\tt $ldots$/backend/executor/execAmi.c}.
-%
-\begin{verbatim}
-  void
-  ExecReScan(Plan *node, ExprContext *exprCtxt, 
-             Plan *parent)
-  {
-                            .
-                            .
-                            .
-     switch (nodeTag(node))
-     {
-                            .
-                            .
-                            .
-\end{verbatim}
-\pagebreak
-\begin{verbatim}
-+      case T_Group:
-+             ExecReScanGroup((Group *) node, 
-+                              exprCtxt, parent);
-+             break;
-                            .
-                            .
-                            .
-     }
-  }
-\end{verbatim}
-%
-<step> The function {\tt ExecReScanGroup()} is called by {\tt
-ExecReScan()} described above whenever a {\tt Group} node is detected
-and can be found in the file {\tt
-$\ldots$/src/backend/executor/nodeGroup.c} . It has been created for
-the {\it intersect} and {\it except} logic although it is actually
-needed by the special kind of subselect (see above).
-%
-\begin{verbatim}
-  void
-  ExecReScanGroup(Group *node, ExprContext *exprCtxt, 
-                  Plan *parent)
-  {
-    GroupState *grpstate = node->grpstate;
-  
-    grpstate->grp_useFirstTuple = FALSE;
-    grpstate->grp_done = FALSE;
-    grpstate->grp_firstTuple = (HeapTupleData *)NIL;
-  
-    /*
-     * if chgParam of subnode is not null then plan 
-     * will be re-scanned by first ExecProcNode.
-     */
-    if (((Plan *) node)->lefttree->chgParam == NULL)
-      ExecReScan(((Plan *) node)->lefttree, 
-                 exprCtxt, (Plan *) node);
-  }
-\end{verbatim}
-%
-\end{itemize}
-
-\subsubsection{Parser}
-
-The {\it parser} defined in the file {\tt
-$\ldots$/src/backend/parser/gram.y} had to be modified in two ways:
-%
-\begin{itemize}
-%
-<step> The grammar had to be adapted to support the usage of
-parenthesis (to be able to specify the order of execution of the set
-operators). 
-%
-<step> The code building up the data structures handed back by the
-{\it parser} had to be inserted.
-%
-\end{itemize}
-%
-Here is a part of the grammar that is responsible for {\tt select}
-statements having the code building up the data structures inserted:
-%
-\pagebreak
-%
-\begin{verbatim}
-  SelectStmt :  select_w_o_sort sort_clause
-      {
-                            .
-                            .
-                            .
-         /* $1 holds the tree built up by the
-          * rule 'select_w_o_sort'
-          */
-         Node *op = (Node *) $1;
-
-         if IsA($1, SelectStmt) 
-         {
-           SelectStmt *n = (SelectStmt *)$1;
-           n->sortClause = $2;
-           $$ = (Node *)n;
-         }
-         else
-         {
-           /* Create a "flat list" of the operator
-            * tree built up by 'select_w_o_sort' and
-            * let select_list point to it 
-            */
-           create_select_list((Node *)op, 
-                              &select_list, 
-                              &unionall_present);
-           /* Replace all the A_Expr nodes in the 
-            * operator tree by Expr nodes.
-            */
-            op = A_Expr_to_Expr(op, &intersect_present);
-                            .
-                            .
-                            .
-            /* Get the leftmost SelectStmt node (which 
-             * automatically represents the first Select 
-             * Statement of the query!) */
-            first_select = 
-                   (SelectStmt *)lfirst(select_list);
-            /* Attach the list of all SelectStmt nodes 
-             * to unionClause 
-             */
-            first_select->unionClause = select_list;
-
-            /* Attach the whole operator tree to 
-             * intersectClause */
-            first_select->intersectClause = 
-                                         (List *) op;
-            /* finally attach the sort clause */
-            first_select->sortClause = $2;
-  
-            /* Now hand it back! */
-            $$ = (Node *)first_select;
-          }               
-      }
-  ; 
-\end{verbatim}
-\pagebreak
-\begin{verbatim}
-  select_w_o_sort :  '(' select_w_o_sort ')'
-      {
-        $$ = $2; 
-      }
-  |  SubSelect
-      {
-        $$ = $1; 
-      }
-  |  select_w_o_sort EXCEPT select_w_o_sort
-      {
-        $$ = (Node *)makeA_Expr(AND,NULL,$1,
-                         makeA_Expr(NOT,NULL,NULL,$3));
-      }
-  |  select_w_o_sort UNION opt_union select_w_o_sort
-      {       
-        if (IsA($4, SelectStmt))
-        {
-          SelectStmt *n = (SelectStmt *)$4;
-          n->unionall = $3;
-        }
-        $$ = (Node *)makeA_Expr(OR,NULL,$1,$4);
-      }
-  |  select_w_o_sort INTERSECT select_w_o_sort
-      {
-        $$ = (Node *)makeA_Expr(AND,NULL,$1,$3);
-      }
-  ; 
-\end{verbatim}
-
-% \pagebreak
-
-\begin{verbatim}
-  SubSelect :  SELECT opt_unique res_target_list2
-               result from_clause where_clause
-               group_clause having_clause
-    {
-      SelectStmt *n = makeNode(SelectStmt);
-      n->unique = $2;
-              .
-              .
-              .
-      n->havingClause = $8;
-      $$ = (Node *)n;
-    }
-  ;
-\end{verbatim}
-%
-The keywords {\tt SELECT}, {\tt EXCEPT}, {\tt UNION}, {\tt INTERSECT}, {\tt
-'('} and {\tt ')'} are {\it terminal symbols} and {\tt SelectStmt},
-{\tt select\_w\_o\_sort}, {\tt sort\_clause}, {\tt opt\_union}, {\tt
-SubSelect}, {\tt opt\_unique}, {\tt res\_target\_list2}, {\tt result},
-{\tt from\_clause}, {\tt where\_clause}, {\tt group\_clause}, {\tt
-having\_clause} are {\it nonterminal symbols}. The symbols {\tt
-EXCEPT}, {\tt UNION} and {\tt INTERSECT} are {\it left
-associative} meaning that a statement like:
-%
-\begin{verbatim}
-  select * from A
-  union 
-  select * from B
-  union
-  select * from C;
-\end{verbatim}
-%
-\pagebreak
-will be treated as:
-%
-\begin{verbatim}
-  ((select * from A
-    union
-    select * from B)
-    union
-    select * from C)
-\end{verbatim}
-%
-The {\tt select\_w\_o\_sort} rule builds up an {\it operator tree}
-using nodes of type {\tt A\_Expr}. For every {\it union} an {\tt OR}
-node is created, for every {\it intersect} an {\tt AND} node and for
-every {\it except} and {\tt AND NOT} node building up a representation
-of a formula in propositional logic. If the query parsed did not
-contain any set operations the rule hands back a {\tt SelectStmt} node
-representing the query otherwise the top node of the {\it operator
-tree} is returned. Figure
-\ref{union_intersect_select_w_o_sort} shows a typical {\it operator tree}
-returned by the {\tt select\_w\_o\_sort} rule.
-
-\begin{figure}[ht]
-\begin{flushright}
-\epsfig{figure=figures/union_intersect_select_w_o_sort.ps}
-\caption{{\it Operator tree} for $(A \cup B) \backslash (C \cap D)$}
-\label{union_intersect_select_w_o_sort}
-\end{flushright}
-\end{figure}
-
-\noindent The rule {\tt SelectStmt} transforms the {\it operator tree} built of
-{\tt A\_Expr} nodes into an {\it operator tree} using {\tt Expr} nodes
-by a call to the function {\tt A\_Expr\_to\_Expr()} which additionally
-replaces every {\tt OR} node by an {\tt AND} node and vice
-versa. This is performed in order to be able to use the function {\tt
-cnfify()} later on. \\
-\\
-The {\it transformations} following the {\it parser} expect a {\tt
-SelectStmt} node to be returned by the rule {\tt SelectStmt} and not
-an {\it operator tree}.  So if the rule {\tt select\_w\_o\_sort} hands
-back such a node (meaning that the query did not contain any set
-operations) we just have to attach the data structure built up by the
-{\tt sort\_clause} rule and are finished, but when we get an {\it
-operator tree} we have to perform the following steps:
-%
-\begin{itemize}
-%
-<step> Create a flat list of all {\tt SelectStmt} nodes of the {\it
-operator tree} (by a call to the function {\tt create\_select\_list()})
-and attach the list to the field
-\mbox{{\tt unionClause}} of the leftmost {\tt SelectStmt} (see next step).
-%
-<step> Find the leftmost leaf ({\tt SelectStmt} node) of the {\it operator
-tree} (this is automatically the first member of the above created
-list because of the technique {\tt create\_select\_list()} uses to
-create the list).
-%
-<step> Attach the whole {\it operator tree} (including the leftmost node
-itself) to the field \mbox{{\tt intersectClause}} of the leftmost {\tt
-SelectStmt} node.
-%
-<step> Attach the data structure built up by the {\tt sort\_clause}
-rule to the field {\tt sortClause} of the leftmost {\tt SelectStmt} node.
-%
-<step> Hand back the leftmost {\tt SelectStmt} node (with
-the {\it operator tree}, the list of all {\tt SelectStmt} nodes and the {\tt
-sortClause} attached to it).
-%
-\end{itemize}
-%
-\noindent Figure \ref{union_intersect_select} shows the final data structure
-derived from the {\it operator tree} shown in figure
-\ref{union_intersect_select_w_o_sort} handed back by the {\tt SelectStmt} rule:
-%
-\begin{figure}[ht]
-\begin{flushright}
-\epsfig{figure=figures/union_intersect_select.ps}
-\caption{Data structure handed back by {\tt SelectStmt} rule}
-\label{union_intersect_select}
-\end{flushright}
-\end{figure}
-
-\pagebreak
-
-\noindent Here is a description of the above used functions. They can
-be found in the file {\tt $\ldots$/src/backend/parser/anlayze.c}.
-%
-\begin{itemize}
-%
-<step> {\tt create\_select\_list()}: \\
-This function steps through the {\it tree} handed to it by the
-parameter {\tt ptr} and creates a list of all {\tt SelectStmt} nodes
-found. The list is handed back by the parameter {\tt
-select\_list}. The function uses a recursive {\it depth first search}
-algorithm to examine the {\it tree} leading to the fact that the
-leftmost {\tt SelectStmt} node will appear first in the created list.
-%
-\begin{verbatim}
-  void 
-  create_select_list(Node *ptr, List **select_list, 
-                     bool *unionall_present)
-  {
-    if(IsA(ptr, SelectStmt)) 
-    {
-      *select_list = lappend(*select_list, ptr);    
-      if(((SelectStmt *)ptr)->unionall == TRUE) 
-        *unionall_present = TRUE;    
-      return;    
-    }
-  
-    /* Recursively call for all arguments. 
-     * A NOT expr has no lexpr! 
-     */
-    if (((A_Expr *)ptr)->lexpr != NULL) 
-      create_select_list(((A_Expr *)ptr)->lexpr, 
-                       select_list, unionall_present);
-    create_select_list(((A_Expr *)ptr)->rexpr, 
-                       select_list, unionall_present);
-}
-\end{verbatim}
-%
-<step> {\tt A\_Expr\_to\_Expr()}: \\
-This function recursively steps through the {\it operator tree} handed
-to it by the parameter {\tt ptr} and replaces {\tt A\_Expr} nodes by
-{\tt Expr} nodes. Additionally it exchanges {\tt AND} nodes with {\tt
-OR} nodes and vice versa.  The reason for this exchange is easy to
-understand. We implement {\it intersect} and {\it except} clauses by
-rewriting these queries to semantically equivalent queries that use
-{\tt IN} and {\tt NOT IN} subselects. To be able to use all three
-operations ({\it unions}, {\it intersects} and {\it excepts}) in one
-complex query, we have to translate the queries into {\it Disjunctive
-Normal Form} (DNF). Unfortunately there is no function {\tt dnfify()},
-but there is a function {\tt cnfify()} which produces DNF when we
-exchange {\tt AND} nodes with {\tt OR} nodes and vice versa before
-calling {\tt cnfify()} and exchange them again in the result.  
-%
-\begin{verbatim}
-  Node *
-  A_Expr_to_Expr(Node *ptr, 
-                 bool *intersect_present)
-  {
-    Node *result;
-  
-    switch(nodeTag(ptr))
-    {
-      case T_A_Expr:
-      {
-        A_Expr *a = (A_Expr *)ptr;
-        
-        switch (a->oper)
-        {
-          case AND:
-          {
-            Expr *expr = makeNode(Expr);
-            Node *lexpr = 
-               A_Expr_to_Expr(((A_Expr *)ptr)->lexpr, 
-                              intersect_present);
-            Node *rexpr = 
-               A_Expr_to_Expr(((A_Expr *)ptr)->rexpr, 
-                              intersect_present);
-
-            *intersect_present = TRUE;
-              
-            expr->typeOid = BOOLOID;
-            expr->opType = OR_EXPR;
-            expr->args = makeList(lexpr, rexpr, -1);
-            result = (Node *) expr;
-            break;            
-          }               
-          case OR:
-          {
-            Expr *expr = makeNode(Expr);
-            Node *lexpr = 
-               A_Expr_to_Expr(((A_Expr *)ptr)->lexpr, 
-                              intersect_present);
-            Node *rexpr = 
-               A_Expr_to_Expr(((A_Expr *)ptr)->rexpr, 
-                              intersect_present);
-
-            expr->typeOid = BOOLOID;
-            expr->opType = AND_EXPR;
-            expr->args = makeList(lexpr, rexpr, -1);
-            result = (Node *) expr;
-            break;            
-          }
-          case NOT:
-          {
-            Expr *expr = makeNode(Expr);
-            Node *rexpr = 
-               A_Expr_to_Expr(((A_Expr *)ptr)->rexpr, 
-                              intersect_present);
-
-            expr->typeOid = BOOLOID;
-            expr->opType = NOT_EXPR;
-            expr->args = makeList(rexpr, -1);
-            result = (Node *) expr;
-            break;            
-          }
-        }       
-        break;  
-      }
-      default:
-      {
-        result = ptr;
-      }      
-    }
-  }
-  return result;  
-}
-\end{verbatim}
-%
-\end{itemize}
-
-\noindent Note that the {\tt stmtmulti} and {\tt OptStmtMulti} rules had to be
-changed in order to avoid {\it shift/reduce} conflicts. The old rules
-allowed an invalid syntax (e.g. the concatenation of two statements
-without a ';' inbetween) which will be prevented now. The new rules
-have the second line commented out as shown below:
-%
-\begin{verbatim}  
-  stmtmulti       :  stmtmulti stmt ';'
-               /* |  stmtmulti stmt */
-                  |  stmt ';'
-                  ;
-
-  OptStmtMulti    :  OptStmtMulti OptimizableStmt ';'
-               /* |  OptStmtMulti OptimizableStmt */
-                  |  OptimizableStmt ';'
-                  ;
-\end{verbatim}
-%
-
-
-\subsubsection{Transformations}
-
-This step normally transforms every {\tt SelectStmt} node found into a
-{\tt Query} node and does a lot of transformations to the {\it targetlist},
-the {\tt where} qualification etc. As mentioned above this stage
-expects a {\tt SelectStmt} node and cannot handle an {\tt A\_Expr}
-node. That's why we did the changes to the {\it operator tree} shown in
-figure \ref{union_intersect_select}. \\
-\\
-In this stage only very few changes have been necessary: 
-%
-\begin{itemize}
-<step> The transformation of the list attached to {\tt unionClause} is
-prevented. The raw list is now passed through instead and the necessary
-transformations are performed at a later point in time.
-<step> The additionally introduced field {\tt intersectClause} is also
-passed untouched through this stage.
-\end{itemize}   
-
-\noindent The changes described in the above paragraph have been
-applied to the functions {\tt transformInsertStmt()} and {\tt
-transformSelectStmt()} which are contained in the file {\tt
-$\ldots$/src/backend/parser/analyze.c}:
-%
-\begin{itemize}
-%
-<step> {\tt transformInsertStmt()}:
-%
-\begin{verbatim}
-  static Query *
-  transformInsertStmt(ParseState *pstate, 
-                      InsertStmt *stmt)
-  {
-                            .
-                            .
-                            .
-\end{verbatim}
-\pagebreak
-\begin{verbatim}
-    /* Just pass through the unionClause and 
-     * intersectClause. We will process it in 
-     * the function Except_Intersect_Rewrite() 
-     */
-    qry->unionClause = stmt->unionClause;
-    qry->intersectClause = stmt->intersectClause;	
-                            .
-                            .
-                            .
-
-    return (Query *) qry;
-  }
-\end{verbatim}
-%
-<step> {\tt transformSelectStmt()}:
-%
-\begin{verbatim}
-  static Query *
-  transformSelectStmt(ParseState *pstate, 
-                      SelectStmt *stmt)
-  {
-                            .
-                            .
-                            .
-    /* Just pass through the unionClause and 
-     * intersectClause. We will process it in 
-     * the function Except_Intersect_Rewrite() 
-     */
-    qry->unionClause = stmt->unionClause;
-    qry->intersectClause = stmt->intersectClause;	
-                            .
-                            .
-                            .
-    return (Query *) qry;
-  }
-\end{verbatim}
-%
-\end{itemize}
-
-\subsubsection{The Rewrite System}
-
-In this stage the information contained in the {\it operator tree} attached
-to the topmost {\tt SelectStmt} node is used to form a tree of {\tt
-Query} nodes representing the rewritten query (i.e. the semantically
-equivalent query that contains only {\it union} but no {\it intersect}
-or {\it except} operations). \\
-\\
-The following steps have to be performed:
-%
-\begin{itemize}
-<step> Save the {\tt sortClause}, {\tt uniqueFlag}, {\tt targetList}
-fields etc. of the topmost {\tt Query} node because the topmost node
-may change during the rewrite process (remember (only) the topmost
-{\tt SelectStmt} node has already been transformed to a {\tt Query}
-node).
-%
-<step> Recursively step through the {\it operator tree} and transform 
-every {\tt SelectStmt} node to a {\tt Query} node using the function
-{\tt intersect\_tree\_analyze()} described below. The one node already
-transformed (the topmost node) is still contained in the {\it operator
-tree} and must not be transformed again because this would cause
-troubles in the {\it transforming logic}.
-%
-\begin{figure}[ht]
-\begin{center}
-\epsfig{figure=figures/union_intersect_dnf.ps}
-\caption{Data structure of $(A \cup B) \backslash C$  after transformation to DNF}
-\label{union_intersect_dnf}
-\end{center}
-\end{figure}
-%
-<step> Transform the new {\it operator tree} into DNF (disjunctive normal
-form). <productname>PostgreSQL</productname> does not provide any function for the transformation
-into DNF but it provides a function {\tt cnfify()} that performs a
-transformation into CNF (conjunctive normal form). So we can easily
-make use of this function when we exchange every {\tt OR} with an {\tt
-AND} and vice versa before calling {\tt cnfify()} as we did already in
-the {\it parser} (compare figure \ref{union_intersect_select_w_o_sort}
-to figure \ref{union_intersect_select}). When {\tt cnfify()} is called
-with a special flag, the {\tt removeAndFlag} set to {\tt true} it
-returns a list where the entries can be thought of being connected
-together by {\tt ANDs}, so the explicit {\tt AND} nodes are removed.
-
-After {\tt cnfify()} has been called we normally would have to
-exchange {\tt OR} and {\tt AND} nodes again. We skip this step by
-simply treating every {\tt OR} node as an {\tt AND} node throughout
-the following steps (remember, that there are no {\tt AND} nodes left
-that have to be treated as {\tt OR} nodes because of the {\tt
-removeAndFlag}).
-
-\noindent Figure \ref{union_intersect_dnf} shows what the data
-structure looks like after the transformation to DNF has taken place
-for the following query:
-%
-\begin{verbatim}
-  (select * from A
-   union
-   select * from B)
-   except
-   select * from C;
-\end{verbatim}
-%
-<step> For every entry of the list returned by {\tt cnfify()} (i.e. for every  
-{\it operator tree} which may only contain {\tt OR} and {\tt NOT}
-operator nodes and {\tt Query} nodes as leaves) contained in the {\tt
-union\_list} perform the following steps:
-%
-\begin{itemize}
-%
-<step> Check if the {\it targetlists} of all {\tt Query} nodes appearing are
-compatible (i.e. all {\it targetlists} have the same number of attributes
-and the corresponding attributes are of the same type)
-%
-<step> There must be at least one positive {\tt
-OR} node (i.e. at least one {\tt OR} node which is not preceded by a
-{\tt NOT} node). Create a list of all {\tt Query} nodes (or of {\tt
-Query} nodes preceded by {\tt NOT} nodes if {\tt OR NOT} is found)
-with the non negated node first using the function {\tt
-create\_list()} described below.
-%
-<step> The first (non negated) node of the list will be the topmost   
-{\tt Query} node of the current {\it union} operand. For all other
-nodes found in the list add an {\tt IN} subselect ({\tt NOT IN}
-subselect if the {\tt Query} node is preceded by a {\tt NOT}) to the
-{\tt where} qualification of the topmost node. Adding a
-subselect to the {\tt where} qualification is done by logically
-{\tt AND}ing it to the original qualification. 
-%
-<step> Append the {\tt Query} node setup in the last steps to a list which
-is hold by the pointer {\tt union\_list}.
-\end{itemize}
-%
-<step> Take the first node of {\tt union\_list} as the new topmost node
-of the whole query and attach the rest of  the list to the
-field {\tt unionClause} of this topmost node. Since the new topmost
-node might differ from the original one (i.e. from the node which was
-topmost when we entered the {\it rewrite stage}) we have to attach the
-fields saved in the first step to the new topmost node (i.e. the {\tt
-sortClause}, {\tt targetList}, {\tt unionFlag}, etc.).
-%
-<step> Hand the new topmost {\tt Query} node back. Now the normal
-{\it query rewriting} takes place (in order to handle views if
-present) and then the {\it planner/optimizer} and {\it executor}
-functions are called to get a result. There have no changes been made
-to the code of these stages.
-%
-\end{itemize}
-Figure \ref{union_operand} shows the rewritten data structure of the
-query:
-\begin{verbatim}
-   select C1, C2 from A
-   intersect
-   select C1, C3 from C;
-\end{verbatim}
-%
-% \clearpage
-%
-\noindent against the tables defined in example \ref{simple_set_ops}.
-The rewritten data structure represents the query:
-\begin{verbatim}
-  select C1, C2 form A
-  where (C1, C2) in 
-        (select C1,C3 from C);
-\end{verbatim}
-%
-\noindent The field {\tt lefttree} of the {\tt Sublink} node points to a list
-where every entry points to a {\tt VAR} node of the {\it targetlist} of the
-topmost node (node A). The field {\tt oper} of the {\tt Sublink} node
-points to a list holding a pointer to an {\tt Expr} node for every
-attribute of the topmost {\it targetlist}. Every {\tt Expr} node is used to
-compare a {\tt VAR} node of the topmost {\it targetlist} with the
-corresponding {\tt VAR} node of the subselect's {\it targetlist}. So the
-first argument of every {\tt Expr} node points to a {\tt VAR} node of
-the topmost {\it targetlist} and the second argument points to the
-corresponding {\tt VAR} node of the subselect's {\it targetlist}.
-%
-\begin{figure}[ht]
-\begin{flushright}
-\epsfig{figure=figures/union_operand.ps}
-\caption{Data structure of $A \cap C$ after query rewriting}
-\label{union_operand}
-\end{flushright}
-\end{figure}
-%
-\clearpage
-%
-\noindent If the user's query involves {\it union} as well as {\it
-intersect} or {\it except} there will be more {\tt Query} nodes of the
-form shown in figure \ref{union_operand}. One will be the topmost node
-(as described above) and the others will be collected in a list which
-is attached to the field {\tt unionClause} of the topmost node. (The
-{\it intersectClause} fields of all {\tt Query} nodes will be set to
-{\tt NULL} because they are no longer needed.) \\
-\\
-%
-The function {\tt pg\_parse\_and\_plan()} is responsible for invoking the
-rewrite procedure. It can be found in the file {\tt
-$\ldots$/src/backend/tcop/postgres.c}.
-%
-\begin{verbatim}
-  List *
-  pg_parse_and_plan(char *query_string, Oid *typev,
-                    int nargs, 
-                    List **queryListP,
-                    CommandDest dest) 
-  {
-                            .
-                            .
-                            .
-    /* Rewrite Union, Intersect and Except Queries
-     * to normal Union Queries using IN and NOT 
-     * IN subselects */
-    if(querytree->intersectClause != NIL) 
-    {       
-      querytree = Except_Intersect_Rewrite(querytree);
-    }
-                            .
-                            .
-                            .
-  }
-\end{verbatim}
-%
-Here are the functions that have been added to perform the
-functionality described above. They can be found in the file {\tt
-$\ldots$/src/backend/rewrite/rewriteHandler.c}.
-%
-\begin{itemize}
-<step> {\tt Except\_Intersect\_Rewrite()} \\
-Rewrites queries involving {\it union clauses}, {\it intersect
-clauses} and {\it except clauses} to semantiacally equivalent queries
-that use {\tt IN} and {\tt NOT IN} subselects instead.
-
-The {\it operator tree} is attached to {\tt intersectClause} (see rule
-{\tt SelectStmt} above) of the {\it parsetree} given as an
-argument. First we save some clauses (the {\tt sortClause}, the {\tt
-unique flag} etc.).  Then we translate the {\it operator tree} to DNF
-({\it Disjunctive Normal Form}) by {\tt cnfify()}. Note that {\tt
-cnfify()} produces CNF but as we exchanged {\tt AND} nodes with {\tt
-OR} nodes within function {\tt A\_Expr\_to\_Expr()} earlier we get DNF
-when we exchange {\tt AND} nodes and {\tt OR} nodes again in the
-result. Now we create a new (rewritten) query by examining the new
-{\it operator tree} which is in DNF now. For every {\tt AND} node we
-create an entry in the {\it union list} and for every {\tt OR} node we
-create an {\tt IN} subselect. ({\tt NOT IN} subselects are created for
-{\tt OR NOT} nodes). The first entry of the {\it union list} is handed
-back but before that the saved clauses ({\tt sortClause} etc.) are
-restored to the new top node. Note that the new top node can differ
-from the one of the {\it parsetree} given as argument because of the
-translation into DNF. That's why we had to save the {\tt sortClause}
-etc.
-%
-\pagebreak
-%
-\begin{verbatim}
-  Query *                                                         
-  Except_Intersect_Rewrite (Query *parsetree)                     
-  {                                                               
-                              .
-                              .
-                              .
-    /* Save some fields, to be able to restore them               
-     * to the resulting top node at the end of the                
-     * function                                                   
-     */                                                           
-    sortClause = parsetree->sortClause;                           
-    uniqueFlag = parsetree->uniqueFlag;                           
-    into = parsetree->into;                                       
-    isBinary = parsetree->isBinary;                               
-    isPortal = parsetree->isPortal;                               
-                                                                  
-    /* Transform the SelectStmt nodes into Query nodes            
-     * as usually done by transformSelectStmt() earlier.          
-     * /                                                          
-    intersectClause =                                             
-      (List *)intersect_tree_analyze(                             
-              (Node *)parsetree->intersectClause,                 
-              (Node *)lfirst(parsetree->unionClause),             
-              (Node *)parsetree);                                 
-                              .                                   
-                              .                                   
-                              .                                   
-    /* Transform the operator tree to DNF */
-    intersectClause = 
-                cnfify((Expr *)intersectClause, true);                      
-    /* For every entry of the intersectClause list we             
-     * generate one entry in the union_list                       
-     */                                                           
-    foreach(intersect, intersectClause)                           
-    {                                                             
-      /* For every OR we create an IN subselect and               
-       * for every OR NOT we create a NOT IN subselect,           
-       */                                                         
-      intersect_list = NIL;                                       
-      create_list((Node *)lfirst(intersect),                      
-                  &intersect_list);
-      /* The first node will become the Select Query 
-       * node, all other nodes are transformed into 
-       * subselects under this node!                                         
-       */                                                         
-      intersect_node = (Query *)lfirst(intersect_list);           
-      intersect_list = lnext(intersect_list);                     
-                              .                                   
-                              .                                   
-                              .                                   
-      /* Transform all remaining nodes into subselects
-       * and add them to the qualifications of the 
-       * Select Query node                                               
-       */                                                         
-      while(intersect_list != NIL)                                
-      {                                                           
-        n = makeNode(SubLink);                                    
-                                                                  
-        /* Here we got an OR so transform it to an                
-         * IN subselect                                           
-         */                                                       
-        if(IsA(lfirst(intersect_list), Query))                    
-        {                                                         
-                              .                                   
-                              .                                   
-                              .                                   
-          n->subselect = lfirst(intersect_list);                  
-          op = "=";                                               
-          n->subLinkType = ANY_SUBLINK;                           
-          n->useor = false;                                       
-        }                                                         
-
-        /* Here we got an OR NOT node so transform        
-         * it to a NOT IN  subselect                                      
-         */                                                       
-        else                                                      
-        {                                                         
-                              .                                   
-                              .                                   
-                              .                                   
-          n->subselect = 
-             (Node *)lfirst(((Expr *)
-                   lfirst(intersect_list))->args);       
-          op = "<>";                                              
-          n->subLinkType = ALL_SUBLINK;                           
-          n->useor = true;                                        
-        }
-
-        /* Prepare the lefthand side of the Sublinks:             
-         * All the entries of the targetlist must be              
-         * (IN) or must not be (NOT IN) the subselect             
-         */                                                       
-        foreach(elist, intersect_node->targetList)                
-        {                                                         
-          Node        *expr = lfirst(elist);                      
-          TargetEntry *tent = (TargetEntry *)expr;                
-                                                                  
-          n->lefthand = 
-                 lappend(n->lefthand, tent->expr);         
-        }
-
-        /* The first arguments of oper also have to be            
-         * created for the sublink (they are the same             
-         * as the lefthand side!)                                 
-         */                                                       
-        left_expr = n->lefthand;                                  
-        right_expr = 
-             ((Query *)(n->subselect))->targetList;
-        foreach(elist, left_expr)                                 
-        {                                                         
-          Node         *lexpr = lfirst(elist);                    
-          Node         *rexpr = lfirst(right_expr);               
-          TargetEntry *tent = (TargetEntry *) rexpr;              
-          Expr         *op_expr;                                  
-                                                                  
-          op_expr = make_op(op, lexpr, tent->expr);         
-          n->oper = lappend(n->oper, op_expr);                    
-          right_expr = lnext(right_expr);                         
-        }
-
-        /* If the Select Query node has aggregates                
-         * in use add all the subselects to the                   
-         * HAVING qual else to the WHERE qual                     
-         */                                                       
-        if(intersect_node->hasAggs == false)                      
-        {                                                         
-          AddQual(intersect_node, (Node *)n);                     
-        }                                                         
-        else                                                      
-        {                                                         
-          AddHavingQual(intersect_node, (Node *)n);               
-        }
-
-        /* Now we got sublinks */                                 
-        intersect_node->hasSubLinks = true;                       
-        intersect_list = lnext(intersect_list);                   
-      }
-      intersect_node->intersectClause = NIL;                      
-      union_list = lappend(union_list, intersect_node);           
-    }                                                             
-
-    /* The first entry to union_list is our                       
-     * new top node                                               
-     */                                                           
-    result = (Query *)lfirst(union_list);                         
-                                                                  
-    /* attach the rest to unionClause */                          
-    result->unionClause = lnext(union_list);                      
-                                                                  
-    /* Attach all the items saved in the                          
-     * beginning of the function */                               
-    result->sortClause = sortClause;                              
-    result->uniqueFlag = uniqueFlag;                              
-    result->into = into;                                          
-    result->isPortal = isPortal;                                  
-    result->isBinary = isBinary;                                  
-                              .                                   
-                              .                                   
-                              .                                   
-    return  result;                                               
-  }
-\end{verbatim}
-%
-<step> {\tt create\_list()} \\
-Create a list of nodes that are either {\tt Query} nodes or {\tt NOT}
-nodes followed by a {\tt Query} node. The {\it tree} given in {\tt
-ptr} contains at least one {\it non negated} {\tt Query} node. This
-node is put to the beginning of the list.
-%
-\begin{verbatim}
-  void create_list(Node *ptr, 
-                   List **intersect_list)
-  {
-    List *arg;   
-
-    if(IsA(ptr,Query))
-    {
-      /* The non negated node is attached at the 
-       * beginning (lcons) */
-      *intersect_list = lcons(ptr, *intersect_list);
-      return;      
-    }  
-    if(IsA(ptr,Expr))
-    {
-      if(((Expr *)ptr)->opType == NOT_EXPR)
-      {
-        /* negated nodes are appended to the 
-         * end (lappend) 
-         */
-        *intersect_list = 
-               lappend(*intersect_list, ptr);        
-        return;         
-      }
-      else
-      {
-        foreach(arg, ((Expr *)ptr)->args)
-        {
-          create_list(lfirst(arg), intersect_list);
-        }     
-        return;         
-      }
-      return;      
-    }
-  }
-\end{verbatim}
-%
-<step> {\tt intersect\_tree\_analyze()} \\
-%
-The nodes given in {\tt tree} are not transformed yet so process them
-using {\tt parse\_analyze()}.  The node given in {\tt first\_select}
-has already been processed, so don't transform it again but return a
-pointer to the already processed version given in {\tt parsetree}
-instead.
-%
-\begin{verbatim}
-  Node *intersect_tree_analyze(Node *tree, 
-                Node *first_select, Node *parsetree)
-  {
-    Node *result; 
-    List *arg;
-
-    if(IsA(tree, SelectStmt))
-    {
-      List *qtrees;
-
-      /* If we get to the tree given in first_select 
-       * return parsetree instead of performing 
-       * parse_analyze() */
-      if(tree == first_select)
-      {
-        result = parsetree;
-      }
-      else 
-      {    
-        /* transform the unprocessed Query nodes */ 
-        qtrees = parse_analyze(lcons(tree, NIL), NULL);
-        result = (Node *) lfirst(qtrees);
-      }      
-    }  
-    if(IsA(tree,Expr))
-    {
-      /* Call recursively for every argument */
-       foreach(arg, ((Expr *)tree)->args)
-       {
-         lfirst(arg) = 
-             intersect_tree_analyze(lfirst(arg), 
-                          first_select, parsetree);
-       }
-       result = tree;      
-    }
-    return result;  
-  }
-\end{verbatim}
-%
-
-\end{itemize}
-
-**********************************************************
-**********************************************************
-**********************************************************
-**********************************************************
-**********************************************************
--->
-
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/arch-pg.sgml b/doc/src/sgml/arch-pg.sgml
deleted file mode 100644
index 21dbf58685e..00000000000
--- a/doc/src/sgml/arch-pg.sgml
+++ /dev/null
@@ -1,116 +0,0 @@
-<Chapter Id="arch-pg">
-	<TITLE>Architecture</TITLE>
-
-<Sect1 id="arch-pg-concepts">
-<Title><ProductName>PostgreSQL</ProductName> Architectural Concepts</Title>
-
-<Para>
-     Before we begin, you  should  understand  the  basic
-     <ProductName>PostgreSQL</ProductName>  system  architecture.   Understanding how the
-     parts of <ProductName>PostgreSQL</ProductName> interact will make the  next  chapter
-     somewhat clearer.
-     In  database  jargon,  <ProductName>PostgreSQL</ProductName> uses a simple "process  
-     per-user" client/server model.  A <ProductName>PostgreSQL</ProductName> session 
-     consists of the following cooperating Unix processes (programs):
-
-<ItemizedList>
-<ListItem>
-<Para>
-      	A supervisory daemon process (the <Application>postmaster</Application>),
-</Para>
-</ListItem>
-<ListItem>
-<Para>
-      	the user's frontend application (e.g., the <Application>psql</Application> program), and
-</Para>
-</ListItem>
-<ListItem>
-<Para>
-      	one or more backend database servers (the <Application>postgres</Application> process itself).
-</Para>
-</ListItem>
-</ItemizedList>
-</para>
-<Para>
-     A single  <Application>postmaster</Application>  manages  a  given  collection  of
-     databases  on  a  single  host.   Such  a collection of
-     databases is called a cluster (of databases).   A frontend
-     application  that  wishes  to  access  a  given database
-     within a cluster makes calls to an interface library (e.g., <application>libpq</>)
-     that is linked into the application.
-     The library sends user requests over the network to the
-     <Application>postmaster</Application>
-(<XRef LinkEnd="PGARCH-CONNECTIONS">(a)), 
-which in turn  starts  a  new backend  server  process 
-(<XRef LinkEnd="PGARCH-CONNECTIONS">(b)) 
-     
-<figure id="PGARCH-CONNECTIONS">
- <title>How a connection is established</title>
-
- <mediaobject>
-  <imageobject>
-   <imagedata align="center" fileref="connections">
-  </imageobject>
- </mediaobject>
-</figure>
-
-     and connects the frontend process to the new server 
-(<XRef LinkEnd="PGARCH-CONNECTIONS">(c)).
-From that  point  on,  the  frontend process and the backend
-     server communicate without intervention by the 
-     <Application>postmaster</Application>.   Hence, the <Application>postmaster</Application> is always running, waiting
-     for connection requests, whereas frontend  and  backend  processes
-     come  and  go.  The <FileName>libpq</FileName> library allows a single 
-     frontend to make multiple connections to backend processes.
-     However,  each backend process is a single-threaded process that can
-     only execute one query at a time; so the communication over any one
-     frontend-to-backend connection is single-threaded.
-</Para>
-
-<Para>
-     One  implication of this architecture is that the 
-     <Application>postmaster</Application> and the backend always run on the
-     same machine (the  database  server), while the frontend 
-     application may run  anywhere.   You  should  keep  this  
-     in  mind,
-     because  the  files  that  can  be accessed on a client
-     machine may not be accessible (or may only be  accessed
-     using  a  different  path name)  on  the database server
-     machine.
-</Para>
-
-<Para>
-     You should also be aware that the <Application>postmaster</Application> and
-     <application>postgres</>  servers  run  with  the  user ID  of the <ProductName>PostgreSQL</ProductName>
-     <quote>superuser</>.
-Note that the <ProductName>PostgreSQL</ProductName> superuser does not
-have  to  be  any particular user (e.g., a user named 
-<literal>postgres</literal>), although many systems are installed that way.
-Furthermore,  the  <ProductName>PostgreSQL</ProductName>  superuser should
-definitely  not  be the Unix superuser, <literal>root</literal>!
-It is safest if the <ProductName>PostgreSQL</ProductName>  superuser is an
-ordinary, unprivileged user so far as the surrounding Unix system is
-concerned.
-     In any case, all files relating to a database should belong to
-     this <ProductName>Postgres</ProductName> superuser.
-</Para>
-</sect1>
-</Chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-tabs-mode:nil
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/share/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml
deleted file mode 100644
index 4dbca080022..00000000000
--- a/doc/src/sgml/array.sgml
+++ /dev/null
@@ -1,328 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.20 2002/03/17 19:59:57 tgl Exp $ -->
-
-<chapter id="arrays">
- <title>Arrays</title>
-
- <indexterm>
-  <primary>arrays</primary>
- </indexterm>
-
- <para>
-  <productname>PostgreSQL</productname> allows columns of a table to be
-  defined as variable-length multidimensional arrays. Arrays of any
-  built-in type or user-defined type can be created.  To illustrate
-  their use, 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 query will create a table named
-  <structname>sal_emp</structname> with columns including
-  a <type>text</type> string (<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>
-  Now we do some <command>INSERT</command>s.  Observe that to write an array
-  value, we enclose the element values within curly braces and separate them
-  by commas.  If you know C, this is not unlike the syntax for
-  initializing structures.  (More details appear below.)
-     
-<programlisting>
-INSERT INTO sal_emp
-    VALUES ('Bill',
-    '{10000, 10000, 10000, 10000}',
-    '{{"meeting", "lunch"}, {}}');
-
-INSERT INTO sal_emp
-    VALUES ('Carol',
-    '{20000, 25000, 25000, 25000}',
-    '{{"talk", "consult"}, {"meeting"}}');
-</programlisting>
- </para>
-
- <para>
-  Now, we can run some queries on <structname>sal_emp</structname>.
-  First, we show how to access a single element of an array at a time.
-  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.
-  By default <productname>PostgreSQL</productname> uses the
-  <quote>one-based</quote> 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 subscript</replaceable> :
-  <replaceable>upper subscript</replaceable></literal> for one or more
-  array dimensions.  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},{""}}
-(1 row)
-</programlisting>
-
-  We could also have written
-
-<programlisting>
-SELECT schedule[1:2][1] FROM sal_emp WHERE name = 'Bill';
-</programlisting>
-
-  with the same result.  An array subscripting operation is taken to
-  represent an array slice if any of the subscripts are written in the
-  form <replaceable>lower</replaceable> <literal>:</literal>
-  <replaceable>upper</replaceable>.  A lower bound of 1 is assumed for
-  any subscript where only one value is specified.
- </para>
-
- <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 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>
-  An array can be enlarged by assigning to an element adjacent to
-  those already present, or by assigning to a slice that is adjacent
-  to or overlaps the data already present.  For example, if an array
-  value currently has 4 elements, it will have five elements after an
-  update that assigns to <literal>array[5]</>.  Currently, enlargement in
-  this fashion is only allowed for one-dimensional arrays, not
-  multidimensional arrays.
- </para>
-
- <para>
-  Array slice assignment allows creation of arrays that do not use one-based
-  subscripts.  For example one might assign to <literal>array[-2:7]</> to
-  create an array with subscript values running from -2 to 7.
- </para>
-
- <para>
-  The syntax for <command>CREATE TABLE</command> allows fixed-length
-  arrays to be defined:
-
-<programlisting>
-CREATE TABLE tictactoe (
-    squares   integer[3][3]
-);
-</programlisting>
-
-  However, the current implementation does not enforce the array size
-  limits --- the behavior is the same as for arrays of unspecified
-  length.
- </para>
-
- <para>
-  Actually, 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 number of dimensions or sizes in
-  <command>CREATE TABLE</command> is simply documentation, it does not
-  affect runtime behavior.
- </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:1]
-(1 row)
-</programlisting>
-
-  <function>array_dims</function> produces a <type>text</type> result,
-  which is convenient for people to read but perhaps not so convenient
-  for programs.
- </para>
-
- <para>
-  To search for a value in an array, you must check each value of the
-  array. This can be done by hand (if you know the size of the array):
-
-<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. Although it is not part
-  of the primary <productname>PostgreSQL</productname> distribution,
-  there is an extension available that defines new functions and
-  operators for iterating over array values. Using this, the above
-  query could be:
-
-<programlisting>
-SELECT * FROM sal_emp WHERE pay_by_quarter[1:4] *= 10000;
-</programlisting>
-
-  To search the entire array (not just specified columns), you could
-  use:
-
-<programlisting>
-SELECT * FROM sal_emp WHERE pay_by_quarter *= 10000;
-</programlisting>
-
-  In addition, you could find rows where the array had all values
-  equal to 10 000 with:
-
-<programlisting>
-SELECT * FROM sal_emp WHERE pay_by_quarter **= 10000;
-</programlisting>
-
-  To install this optional module, look in the
-  <filename>contrib/array</filename> directory of the
-  <productname>PostgreSQL</productname> source distribution.
- </para>
-
- <tip>
-  <para>
-   Arrays are not sets; using arrays in the manner described in the
-   previous paragraph is often a sign of database misdesign.  The
-   array field should generally be split off into a separate table.
-   Tables can obviously be searched easily.
-  </para>
- </tip>
-
- <note>
-  <para>
-   A limitation of the present array implementation is that individual
-   elements of an array cannot be SQL NULLs.  The entire array can be set
-   to NULL, but you can't have an array with some elements NULL and some
-   not.  Fixing this is on the to-do list.
-  </para>
- </note>
-
- <formalpara>
-  <title>Array input and output syntax.</title>
-  <para>
-   The external 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 datatypes provided
-   in the <productname>PostgreSQL</productname> distribution, type
-   <literal>box</> uses a semicolon (<literal>;</>) but all the others
-   use comma.)  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.
-   You may write whitespace before a left brace, after a right
-   brace, or before any individual item string.  Whitespace after an item
-   is not ignored, however: after skipping leading whitespace, everything
-   up to the next right brace or delimiter is taken as the item value.
-  </para>
- </formalpara>
-
- <formalpara>
-  <title>Quoting array elements.</title>
-  <para>
-   As shown above, when writing an array value you may write 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 whatever the delimiter character is), double quotes,
-   backslashes, or leading white space must be double-quoted.  To put a double
-   quote or backslash in an array element value, precede it with a backslash.
-   Alternatively, you can use backslash-escaping to protect all data characters
-   that would otherwise be taken as array syntax or ignorable white space.
-  </para>
- </formalpara>
-
-  <para>
-   The array output routine will put double quotes around element values
-   if they are empty strings or contain curly braces, delimiter characters,
-   double quotes, backslashes, or white space.  Double quotes and backslashes
-   embedded in element values will be backslash-escaped.  For numeric
-   datatypes it is safe to assume that double quotes will never appear, but
-   for textual datatypes one should be prepared to cope with either presence
-   or absence of quotes.  (This is a change in behavior from pre-7.2
-   <productname>PostgreSQL</productname> releases.)
-  </para>
-
- <tip>
-  <para>
-   Remember that what you write in an SQL query 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 ('{"\\\\","\\""}');
-</programlisting>
-   The string-literal 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 query to get one backslash into the stored array element.)
-  </para>
- </tip>
-
-</chapter>
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
deleted file mode 100644
index c476dcb7880..00000000000
--- a/doc/src/sgml/backup.sgml
+++ /dev/null
@@ -1,459 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v 2.22 2001/11/28 20:49:09 petere Exp $
--->
-<chapter id="backup">
- <title>Backup and Restore</title>
-
- <indexterm zone="backup"><primary>backup</></>
-
- <para>
-  As 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 basic understanding of
-  the underlying techniques and assumptions.
- </para>
-
- <para>
-  There are two 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>
-  </itemizedlist>
- </para>
-
- <sect1 id="backup-dump">
-  <title><acronym>SQL</> Dump</title>
-
-  <para>
-   The idea behind the SQL-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
-   <application>pg_dump</> 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 results 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 do 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, you must
-   have read access to all tables that you want to back up, so in
-   practice you almost always have to be 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>
-   As any other <productname>PostgreSQL</> client application,
-   <application>pg_dump</> will by default connect with the database
-   user name that is equal to the current Unix 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>
-   Dumps created by <application>pg_dump</> are internally consistent,
-   that is, updates to the database while <application>pg_dump</> is
-   running will not be in the dump. <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 <command>VACUUM FULL</command>.)
-  </para>
-
-  <important>
-   <para>
-    When 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.  <quote>Large objects</> are not dumped by default, either.
-    See <application>pg_dump</>'s command reference page if you use
-    large objects.
-   </para>
-  </important>
-
-  <sect2 id="backup-dump-restore">
-   <title>Restoring the dump</title>
-
-   <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 what
-    you used as <replaceable class="parameter">outfile</replaceable>
-    for the pg_dump command. The database <replaceable
-    class="parameter">dbname</replaceable> will not be created by this
-    command, you must create it yourself from template0 before executing
-    <application>psql</> (e.g., with <literal>createdb -T template0
-    <replaceable class="parameter">dbname</></literal>).
-    <application>psql</> supports similar options to <application>pg_dump</> 
-    for controlling the database server location and the user names. See
-    its reference page for more information.
-   </para>
-
-   <para>
-    If the objects in the original database were owned by different
-    users, then the dump will instruct <application>psql</> to connect
-    as each affected user in turn and then create the relevant
-    objects. This way the original ownership is preserved. This also
-    means, however, that all these users must already exist, and
-    furthermore that you must be allowed to connect as each of them.
-    It might therefore be necessary to temporarily relax the client
-    authentication settings.
-   </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
-    <informalexample>
-<programlisting>
-pg_dump -h <replaceable>host1</> <replaceable>dbname</> | psql -h <replaceable>host2</> <replaceable>dbname</>
-</programlisting>
-    </informalexample>
-   </para>
-
-
-  <important>
-   <para>
-	The dumps produced by pg_dump are relative to template0. This means 
-    that any languages, procedures, etc. added to template1 will also be
-    dumped by <application>pg_dump</>. As a result, when restoring, if 
-    you are using a customized template1, you must create the empty
-    database from template0, as in the example above.
-   </para>
-  </important>
-
-  </sect2>
-
-  <sect2 id="backup-dump-all">
-   <title>Using <command>pg_dumpall</></title>
-
-   <para>
-    The above mechanism is cumbersome and inappropriate when backing
-    up an entire database cluster. For this reason the
-    <application>pg_dumpall</> program is provided.
-    <application>pg_dumpall</> backs up each database in a given
-    cluster and also makes sure that the state of global data such as
-    users and groups is preserved. The call sequence for
-    <application>pg_dumpall</> is simply
-<synopsis>
-pg_dumpall &gt; <replaceable>outfile</>
-</synopsis>
-    The resulting dumps can be restored with <application>psql</> as
-    described above. But in this case it is definitely necessary that
-    you have database superuser access, as that is required to restore
-    the user and group information.
-   </para>
-  </sect2>
-
-  <sect2 id="backup-dump-large">
-   <title>Large Databases</title>
-
-   <note>
-    <title>Acknowledgement</title>
-    <para>
-     Originally written by Hannu Krosing
-     (<email>hannu@trust.ee</email>) on 1999-06-19
-    </para>
-   </note>
-
-   <para>
-    Since <productname>PostgreSQL</productname> allows tables larger
-    than the maximum file size on your system, it can be problematic
-    to dump the table to a file, since the resulting file will likely
-    be larger than the maximum size allowed by your system. As
-    <application>pg_dump</> writes to the standard output, you can
-    just use standard *nix tools to work around this possible problem.
-   </para>
-
-   <formalpara>
-    <title>Use compressed dumps.</title>
-    <para>
-     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>
-createdb <replaceable class="parameter">dbname</replaceable>
-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 <application>split</>.</title>
-    <para>
-     This allows you to split the output into pieces that are
-     acceptable in size to the underlying file system. For example, to
-     make chunks of 1 megabyte:
-
-     <informalexample>
-<programlisting>
-pg_dump <replaceable class="parameter">dbname</replaceable> | split -b 1m - <replaceable class="parameter">filename</replaceable>
-</programlisting>
-     </informalexample>
-
-     Reload with
-
-     <informalexample>
-<programlisting>
-createdb <replaceable class="parameter">dbname</replaceable>
-cat <replaceable class="parameter">filename</replaceable>* | psql <replaceable class="parameter">dbname</replaceable>
-</programlisting>
-     </informalexample>
-    </para>
-   </formalpara>
-
-   <formalpara>
-    <title>Use the 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. For large databases, this will produce similar dump
-     sizes to using <command>gzip</command>, but has the added advantage that the tables can be
-     restored selectively. The following command dumps a database using the
-     custom dump format:
-
-     <informalexample>
-<programlisting>
-pg_dump -Fc <replaceable class="parameter">dbname</replaceable> > <replaceable class="parameter">filename</replaceable>
-</programlisting>
-     </informalexample>
-
-     See the <application>pg_dump</> and <application>pg_restore</> reference pages for details.
-
-    </para>
-   </formalpara>
-
-  </sect2>
-
-  <sect2 id="backup-dump-caveats">
-   <title>Caveats</title>
-
-   <para>
-    <application>pg_dump</> (and by implication
-    <application>pg_dumpall</>) has a few limitations which stem from
-    the difficulty to reconstruct certain information from the system
-    catalogs.
-   </para>
-
-   <para>
-    Specifically, the order in which <application>pg_dump</> writes
-    the objects is not very sophisticated. This can lead to problems
-    for example when functions are used as column default values. The
-    only answer is to manually reorder the dump. If you created
-    circular dependencies in your schema then you will have more work
-    to do.
-   </para>
-
-   <para>
-    For reasons of backward compatibility, <application>pg_dump</> does
-    not dump large objects by default. To dump large objects you must use 
-    either the custom or the TAR output format, and use the -b option in 
-    <application>pg_dump</>. See the reference pages for details.
-    The directory <filename>contrib/pg_dumplo</> of the
-    <productname>PostgreSQL</> source tree also contains a program that can
-    dump large objects.
-   </para>
-
-   <para>
-    Please familiarize yourself with the
-    <citerefentry><refentrytitle>pg_dump</></> reference page.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="backup-file">
-  <title>File system level backup</title>
-
-  <para>
-   An alternative backup strategy is to directly copy the files that
-   <productname>PostgreSQL</> uses to store the data in the database. In
-   <xref linkend="creating-cluster"> it is explained where these files
-   are located, but you have probably found them already if you are
-   interested in this method. You can use whatever method you prefer
-   for doing usual file system backups, for example
-   <informalexample>
-<programlisting>
-tar -cf backup.tar /usr/local/pgsql/data
-</programlisting>
-   </informalexample>
-  </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 not work as there is always some buffering
-      going on. For this reason it is also not advisable to trust file
-      systems that claim to support <quote>consistent
-      snapshots</quote>. Information about stopping the server can be
-      found in <xref linkend="postmaster-shutdown">.
-     </para>
-
-     <para>
-      Needless to say that 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 you
-      may 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 contains only half the
-      truth. The other half is in 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 will render all other tables in the database
-      cluster useless.
-     </para>
-    </listitem>
-   </orderedlist>
-  </para>
-
-  <para>
-   Also note that the file system backup will not necessarily be
-   smaller than an SQL dump. On the contrary, it will most likely be
-   larger. (<application>pg_dump</application> does not need to dump
-   the contents of indexes for example, just the commands to recreate
-   them.)
-  </para>
-
- </sect1>
-
- <sect1 id="migration">
-  <title>Migration between releases</title>
-  <indexterm zone="migration"><primary>upgrading</></>
-
-  <para>
-   As a general rule, the internal data storage format is subject to
-   change between releases of <productname>PostgreSQL</>. This does not
-   apply to different <quote>patch levels</quote>, these always have
-   compatible storage formats. For example, releases 7.0.1, 7.1.2, and
-   7.2 are not compatible, whereas 7.1.1 and 7.1.2 are. When you
-   update between compatible versions, then you can simply reuse the
-   data area in disk by the new executables. Otherwise you need to
-   <quote>back up</> your data and <quote>restore</> it on the new
-   server, using <application>pg_dump</>. (There are checks in place
-   that prevent you from doing the wrong thing, so no harm can be done
-   by confusing these things.) The precise installation procedure is
-   not subject of this section, these details are in <xref linkend="installation">.
-  </para>
-
-  <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
-<informalexample>
-<programlisting>
-pg_dumpall -p 5432 | psql -d template1 -p 6543
-</programlisting>
-</informalexample>
-   to transfer your data, or use an intermediate file if you want.
-   Then you can shut down the old server and start the new server at
-   the port the old one was running at. You should make sure that the
-   database is not updated after you run <application>pg_dumpall</>,
-   otherwise you will obviously lose that data. See <xref
-   linkend="client-authentication"> for information on how to prohibit
-   access. In practice you probably want to test your client
-   applications on the new setup before switching over.
-  </para>
-
-  <para>
-   If you cannot or do not want to run two servers in parallel you can
-   do the back up step before installing the new version, bring down
-   the server, move the old version out of the way, install the new
-   version, start the new server, restore the data. For example:
-<informalexample>
-<programlisting>
-pg_dumpall > backup
-pg_ctl stop
-mv /usr/local/pgsql /usr/local/pgsql.old
-cd /usr/src/postgresql-&version;
-gmake install
-initdb -D /usr/local/pgsql/data
-postmaster -D /usr/local/pgsql/data
-psql < backup
-</programlisting>
-</informalexample>
-   See <xref linkend="runtime"> about ways to start and stop the
-   server and other details. The installation instructions will advise
-   you of strategic places to perform these steps.
-  </para>
-
-  <note>
-   <para>
-    When you <quote>move the old installation out of the way</quote>
-    it is no longer perfectly usable. Some parts of the installation
-    contain information about where the other parts are located. This
-    is usually not a big problem but if you plan on using two
-    installations in parallel for a while you should assign them
-    different installation directories at build time.
-   </para>
-  </note>
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-tabs-mode:nil
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/share/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/biblio.sgml b/doc/src/sgml/biblio.sgml
deleted file mode 100644
index a03c03504f3..00000000000
--- a/doc/src/sgml/biblio.sgml
+++ /dev/null
@@ -1,540 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/biblio.sgml,v 1.19 2002/01/08 23:50:37 petere Exp $
--->
-
- <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
-   <ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/papers/">
-    the University of California, Berkeley, Computer Science
-    Department web site</ulink>
-  </para>
-
-  <bibliodiv>
-   <title><acronym>SQL</acronym> Reference Books</title>
-   <para>Reference texts for <acronym>SQL</acronym> features.</para>
-
-   <biblioentry id="BOWMAN93">
-    <title>The Practical <acronym>SQL</acronym> Handbook</title>
-    <titleabbrev>Bowman et al, 1996</titleabbrev>
-    <subtitle>Using Structured Query Language</subtitle>
-    <edition>Third 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-44787-8</isbn>
-    <pubdate>1996</pubdate>
-    <publisher>
-     <publishername>Addison-Wesley</publishername>
-    </publisher>
-    <copyright>
-     <year>1996</year>
-     <holder>Addison-Wesley Longman, Inc.</holder>
-    </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="DATE94">
-    <title>An Introduction to Database Systems</title>
-    <titleabbrev>Date, 1994</titleabbrev>
-    <edition>Sixth Edition</edition>
-    <authorgroup>
-     <author>
-      <firstname>C. J.</firstname>
-      <surname>Date</surname>
-     </author>
-    </authorgroup>
-    <volumenum>Volume 1</volumenum>
-    <pubdate>1994</pubdate>
-    <publisher>
-     <publishername>Addison-Wesley</publishername>
-    </publisher>
-    <copyright>
-     <year>1994</year>
-     <holder>Addison-Wesley Longman, Inc.</holder>
-    </copyright>
-   </biblioentry>
-
-  <biblioentry id="ELMA99">
-   <title>Fundamentals of Database Systems</title>
-   <edition>3rd Edition</edition>
-   <authorgroup>
-    <author>
-     <firstname>Ramez</firstname>
-     <surname>Elmasri</surname>
-    </author>
-    <author>
-     <firstname>Shamkant</firstname>
-     <surname>Navathe</surname>
-    </author>
-   </authorgroup>
-   <isbn>0-805-31755-4</isbn>
-   <pubdate>August 1999</pubdate>
-   <publisher>
-    <publishername>Addison-Wesley</publishername>
-   </publisher>
-  </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
-ssimkovi@ag.or.at
--->
-     </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://s2k-ftp.CS.Berkeley.EDU:8000/postgres/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://s2k-ftp.CS.Berkeley.EDU:8000/postgres/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><ulink url="http://simon.cs.cornell.edu/home/praveen/papers/partindex.de95.ps.Z">Generalized Partial Indexes</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://s2k-ftp.CS.Berkeley.EDU:8000/postgres/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://s2k-ftp.CS.Berkeley.EDU:8000/postgres/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://s2k-ftp.CS.Berkeley.EDU:8000/postgres/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://s2k-ftp.CS.Berkeley.EDU:8000/postgres/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://s2k-ftp.CS.Berkeley.EDU:8000/postgres/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://s2k-ftp.CS.Berkeley.EDU:8000/postgres/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>
-
-  </bibliodiv>
- </bibliography>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/bki.sgml b/doc/src/sgml/bki.sgml
deleted file mode 100644
index 36503de6590..00000000000
--- a/doc/src/sgml/bki.sgml
+++ /dev/null
@@ -1,245 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/bki.sgml,v 1.11 2002/04/25 02:56:55 tgl Exp $
- -->
-
-<chapter id="bki">
- <title><acronym>BKI</acronym> Backend Interface</title>
-
- <para>
-  Backend Interface (<acronym>BKI</acronym>) files are scripts in a
-  special language that are input to the
-  <productname>PostgreSQL</productname> backend running in the special
-  <quote>bootstrap</quote> mode that allows it to perform database
-  functions without a database system already existing.
-  <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.sh</filename> from some
-  specially formatted C header files in 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 may be found in the documentation for
-  <application>initdb</application>.
- </para>
-
- <sect1 id="bki-format">
-  <title><acronym>BKI</acronym> File Format</title>
-
-  <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.  You should also study the source
-   code of <application>initdb</application> to get an idea of how the
-   backend is invoked.
-  </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 a <literal>#</literal> are ignored.
-  </para>
-
- </sect1>
-
- <sect1 id="bki-commands">
-  <title><acronym>BKI</acronym> Commands</title>
-
-  <variablelist>
-   <varlistentry>
-    <term>
-     open <replaceable class="parameter">tablename</replaceable>
-    </term>
-
-    <listitem>
-     <para>
-      Open the table called
-      <replaceable class="parameter">tablename</replaceable>
-      for further manipulation.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     close <optional><replaceable class="parameter">tablename</replaceable></optional>
-    </term>
-
-    <listitem>
-     <para>
-      Close the open table called <replaceable
-      class="parameter">tablename</replaceable>.  It is an error if
-      <replaceable class="parameter">tablename</replaceable> is not
-      already opened.  If no <replaceable
-      class="parameter">tablename</replaceable> is given, then the
-      currently open table is closed.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     create <replaceable class="parameter">tablename</replaceable>
-     (<replaceable class="parameter">name1</replaceable> =
-     <replaceable class="parameter">type1</replaceable> <optional>,
-     <replaceable class="parameter">name2</replaceable> = <replaceable
-     class="parameter">type2</replaceable>, ...</optional>)
-    </term>
-
-    <listitem>
-     <para>
-      Create a table named <replaceable
-      class="parameter">tablename</replaceable> with the columns given
-      in parentheses.
-     </para>
-
-     <para>
-      The <replaceable>type</replaceable> is not necessarily the data
-      type that the column will have in the SQL environment; that is
-      determined by the <structname>pg_attribute</structname> system
-      catalog.  The type here is essentially only used to allocate
-      storage.  The following types are allowed: <type>bool</type>,
-      <type>bytea</type>, <type>char</type> (1 byte),
-      <type>name</type>, <type>int2</type>, <type>int2vector</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>oidvector</type>, <type>smgr</type>,
-      <type>_int4</type> (array), <type>_aclitem</type> (array).
-      Array types can also be indicated by writing
-      <literal>[]</literal> after the name of the element type.
-     </para>
-
-     <note>
-      <para>
-       The table will only be created on disk, it will not
-       automatically be registered in the system catalogs and will
-       therefore not be accessible unless appropriate rows are
-       inserted in <structname>pg_class</structname>,
-       <structname>pg_attribute</structname>, etc.
-      </para>
-     </note>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>
-     insert <optional>OID = <replaceable class="parameter">oid_value</replaceable></optional> (<replaceable class="parameter">value1</replaceable> <replaceable class="parameter">value2</replaceable> ...)
-    </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, then the next available OID is
-      used.
-     </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>
-     declare <optional>unique</optional> index <replaceable
-     class="parameter">indexname</replaceable> on <replaceable
-     class="parameter">tablename</replaceable> using <replaceable
-     class="parameter">amname</replaceable> (<replaceable
-     class="parameter">opclass1</replaceable> <replaceable
-     class="parameter">name1</replaceable> <optional>, ...</optional>)
-    </term>
-
-    <listitem>
-     <para>
-      Create an index named <replaceable
-      class="parameter">indexname</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.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>build indices</term>
-
-    <listitem>
-     <para>
-      Build the indices that have previously been declared.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
- </sect1>
-
- <sect1 id="bki-example">
-  <title>Example</title>
-
-  <para>
-   The following sequence of commands will create the
-   <literal>test_table</literal> table with the 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 (cola = int4, colb = text)
-open test_table
-insert OID=421 ( 1 "value1" )
-insert OID=422 ( 2 _null_ )
-close test_table
-</programlisting>
-  </para>
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/book-decl.sgml b/doc/src/sgml/book-decl.sgml
deleted file mode 100644
index 4992fb202ef..00000000000
--- a/doc/src/sgml/book-decl.sgml
+++ /dev/null
@@ -1,11 +0,0 @@
-<!doctype book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
-
-<!entity % version SYSTEM "version.sgml">
-%version;
-<!entity % filelist SYSTEM "filelist.sgml">
-%filelist;
-
-<!entity % set-of-books "IGNORE">
-<!entity % single-book "INCLUDE">
-
-]>
diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
deleted file mode 100644
index c3ed19e4b2a..00000000000
--- a/doc/src/sgml/catalogs.sgml
+++ /dev/null
@@ -1,2750 +0,0 @@
-<!--
- Documentation of the system catalogs, directed toward PostgreSQL developers
- $Header: /cvsroot/pgsql/doc/src/sgml/catalogs.sgml,v 2.44 2002/06/20 15:44:06 momjian Exp $
- -->
-
-<chapter id="catalogs">
- <title>System Catalogs</title>
-
- <sect1 id="catalogs-overview">
-  <title>Overview</title>
-
-  <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.
-   <productname>PostgreSQL</productname>'s system catalogs are regular
-   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 -- and actually
-   creates the database on disk.)  There are some exceptions for
-   esoteric operations, such as adding index access methods.
-  </para>
-
-  <table>
-   <title>System Catalogs</title>
-
-   <tgroup cols="2">
-    <thead>
-     <row>
-      <entry>Catalog Name</entry>
-      <entry>Purpose</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>pg_aggregate</entry>
-      <entry>aggregate functions</entry>
-     </row>
-
-     <row>
-      <entry>pg_am</entry>
-      <entry>index access methods</entry>
-     </row>
-
-     <row>
-      <entry>pg_amop</entry>
-      <entry>access method operators</entry>
-     </row>
-
-     <row>
-      <entry>pg_amproc</entry>
-      <entry>access method support procedures</entry>
-     </row>
-
-     <row>
-      <entry>pg_attrdef</entry>
-      <entry>column default values</entry>
-     </row>
-
-     <row>
-      <entry>pg_attribute</entry>
-      <entry>table columns (<quote>attributes</quote>, <quote>fields</quote>)</entry>
-     </row>
-
-     <row>
-      <entry>pg_class</entry>
-      <entry>tables, indexes, sequences (<quote>relations</quote>)</entry>
-     </row>
-
-     <row>
-      <entry>pg_database</entry>
-      <entry>databases within this database cluster</entry>
-     </row>
-
-     <row>
-      <entry>pg_description</entry>
-      <entry>descriptions or comments on database objects</entry>
-     </row>
-
-     <row>
-      <entry>pg_group</entry>
-      <entry>groups of database users</entry>
-     </row>
-
-     <row>
-      <entry>pg_index</entry>
-      <entry>additional index information</entry>
-     </row>
-
-     <row>
-      <entry>pg_inherits</entry>
-      <entry>table inheritance hierarchy</entry>
-     </row>
-
-     <row>
-      <entry>pg_language</entry>
-      <entry>languages for writing functions</entry>
-     </row>
-
-     <row>
-      <entry>pg_largeobject</entry>
-      <entry>large objects</entry>
-     </row>
-
-     <row>
-      <entry>pg_listener</entry>
-      <entry>asynchronous notification</entry>
-     </row>
-
-     <row>
-      <entry>pg_namespace</entry>
-      <entry>namespaces (schemas)</entry>
-     </row>
-
-     <row>
-      <entry>pg_opclass</entry>
-      <entry>index access method operator classes</entry>
-     </row>
-
-     <row>
-      <entry>pg_operator</entry>
-      <entry>operators</entry>
-     </row>
-
-     <row>
-      <entry>pg_proc</entry>
-      <entry>functions and procedures</entry>
-     </row>
-
-     <row>
-      <entry>pg_relcheck</entry>
-      <entry>check constraints</entry>
-     </row>
-
-     <row>
-      <entry>pg_rewrite</entry>
-      <entry>query rewriter rules</entry>
-     </row>
-
-     <row>
-      <entry>pg_shadow</entry>
-      <entry>database users</entry>
-     </row>
-
-     <row>
-      <entry>pg_statistic</entry>
-      <entry>optimizer statistics</entry>
-     </row>
-
-     <row>
-      <entry>pg_trigger</entry>
-      <entry>triggers</entry>
-     </row>
-
-     <row>
-      <entry>pg_type</entry>
-      <entry>data types</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   More detailed documentation of most catalogs follow below.  The
-   catalogs that relate to index access methods are explained in the
-   <citetitle>Programmer's Guide</citetitle>.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-aggregate">
-  <title>pg_aggregate</title>
-
-  <para>
-   <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 datatypes, and
-   other information that is similar to ordinary functions.
-  </para>
-
-  <table>
-   <title>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>aggfnoid</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>pg_proc OID of the aggregate function</entry>
-     </row>
-     <row>
-      <entry>aggtransfn</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>Transition function</entry>
-     </row>
-     <row>
-      <entry>aggfinalfn</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>Final function</entry>
-     </row>
-     <row>
-      <entry>aggtranstype</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry>The type of the aggregate function's internal transition (state) data</entry>
-     </row>
-     <row>
-      <entry>agginitval</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 the field is NULL, the transition state
-       value starts out NULL.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   New aggregate functions are registered with the <command>CREATE
-   AGGREGATE</command> command.  See the <citetitle>Programmer's
-   Guide</citetitle> for more information about writing aggregate
-   functions and the meaning of the transition functions, etc.
-  </para>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-attrdef">
-  <title>pg_attrdef</title>
-
-  <para>
-   This catalog 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>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>adrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The table this column belongs to</entry>
-     </row>
-
-     <row>
-      <entry>adnum</entry>
-      <entry><type>int2</type></entry>
-      <entry>pg_attribute.attnum</entry>
-      <entry>The number of the column</entry>
-     </row>
-
-     <row>
-      <entry>adbin</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>An internal representation of the column default value</entry>
-     </row>
-
-     <row>
-      <entry>adsrc</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>A human-readable representation of the default value</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-attribute">
-  <title>pg_attribute</title>
-
-  <para>
-   <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 other objects.  See <structname>pg_class</structname>.)
-  </para>
-
-  <para>
-   The term attribute is equivalent to column and is used for
-   historical reasons.
-  </para>
-
-  <table>
-   <title>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>attrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The table this column belongs to</entry>
-     </row>
-
-     <row>
-      <entry>attname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Column name</entry>
-     </row>
-
-     <row>
-      <entry>atttypid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry>The data type of this column</entry>
-     </row>
-
-     <row>
-      <entry>attstattarget</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       <structfield>attstattarget</structfield> controls the level of detail
-       of statistics accumulated for this column by
-       <command>ANALYZE</command>.
-       A zero value indicates that no statistics should be collected.
-       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>attlen</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       This is a copy of the
-       <structname>pg_type</structname>.<structfield>typlen</structfield>
-       for this column's type.
-      </entry>
-     </row>
-
-     <row>
-      <entry>attnum</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>attndims</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>attcacheoff</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       Always -1 in storage, but when loaded into a tuple descriptor
-       in memory this may be updated to cache the offset of the attribute
-       within the tuple.
-      </entry>
-     </row>
-
-     <row>
-      <entry>atttypmod</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 and output functions as the third
-       argument. The value will generally be -1 for types that do not
-       need typmod.
-      </entry>
-     </row>
-
-     <row>
-      <entry>attbyval</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       A copy of
-       <structname>pg_type</structname>.<structfield>typbyval</structfield>
-       of this column's type
-      </entry>
-     </row>
-
-     <row>
-      <entry>attstorage</entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       A copy of
-       <structname>pg_type</structname>.<structfield>typstorage</structfield>
-       of this column's type
-      </entry>
-     </row>
-
-     <row>
-      <entry>attisset</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       If true, this attribute is a set.  In that case, what is really
-       stored in the attribute is the OID of a tuple in the
-       <structname>pg_proc</structname> catalog.  The
-       <structname>pg_proc</structname> tuple contains the query
-       string that defines this set - i.e., the query to run to get
-       the set.  So the <structfield>atttypid</structfield> (see
-       above) refers to the type returned by this query, but the
-       actual length of this attribute is the length (size) of an
-       <type>oid</type>.  --- At least this is the theory.  All this
-       is probably quite broken these days.
-      </entry>
-     </row>
-
-     <row>
-      <entry>attalign</entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       A copy of
-       <structname>pg_type</structname>.<structfield>typalign</structfield>
-       of this column's type
-      </entry>
-     </row>
-
-     <row>
-      <entry>attnotnull</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This represents a NOT NULL constraint.  It is possible to
-       change this field to enable or disable the constraint.
-      </entry>
-     </row>
-
-     <row>
-      <entry>atthasdef</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>
-
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-class">
-  <title>pg_class</title>
-
-  <para>
-   <structname>pg_class</structname> catalogs tables and mostly
-   everything else that has columns or is otherwise similar to a
-   table.  This includes indexes (but see also
-   <structname>pg_index</structname>), sequences, views, and some
-   kinds of special relation.  Below, when we mean all of these
-   kinds of objects we speak of <quote>relations</quote>.  Not all
-   fields are meaningful for all relation types.
-  </para>
-
-  <table>
-   <title>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>relname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the table, index, view, etc.</entry>
-     </row>
-
-     <row>
-      <entry>relnamespace</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_namespace.oid</entry>
-      <entry>
-       The OID of the namespace that contains this relation
-      </entry>
-     </row>
-
-     <row>
-      <entry>reltype</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry>
-       The OID of the data type that corresponds to this table, if any
-       (zero for indexes, which have no pg_type entry)
-      </entry>
-     </row>
-
-     <row>
-      <entry>relowner</entry>
-      <entry><type>int4</type></entry>
-      <entry>pg_shadow.usesysid</entry>
-      <entry>Owner of the relation</entry>
-     </row>
-
-     <row>
-      <entry>relam</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_am.oid</entry>
-      <entry>If this is an index, the access method used (B-tree, hash, etc.)</entry>
-     </row>
-
-     <row>
-      <entry>relfilenode</entry>
-      <entry><type>oid</type></entry>
-      <entry></entry>
-      <entry>Name of the on-disk file of this relation</entry>
-     </row>
-
-     <row>
-      <entry>relpages</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       Size of the on-disk representation of this table in pages (size
-       <symbol>BLCKSZ</symbol>).
-       This is only an estimate used by the planner.
-       It is updated by <command>VACUUM</command>,
-       <command>ANALYZE</command>, and <command>CREATE INDEX</command>.
-      </entry>
-     </row>
-
-     <row>
-      <entry>reltuples</entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>
-       Number of tuples in the table.
-       This is only an estimate used by the planner.
-       It is updated by <command>VACUUM</command>,
-       <command>ANALYZE</command>, and <command>CREATE INDEX</command>.
-      </entry>
-     </row>
-
-     <row>
-      <entry>reltoastrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</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>reltoastidxid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>
-       For a TOAST table, the OID of its index.  0 if not a TOAST table.
-      </entry>
-     </row>
-
-     <row>
-      <entry>relhasindex</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if this is a table and it has (or recently had) any indexes.
-       This is set by CREATE INDEX, but not cleared immediately by DROP INDEX.
-       VACUUM clears relhasindex if it finds the table has no indexes.
-      </entry>
-     </row>
-
-     <row>
-      <entry>relisshared</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>relkind</entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       'r' = ordinary table, 'i' = index, 'S' = sequence, 'v' = view,
-       's' = special, 't' = secondary TOAST table
-      </entry>
-     </row>
-
-     <row>
-      <entry>relnatts</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
-       <structname>pg_attribute</structname>.<structfield>attnum</structfield>.
-      </entry>
-     </row>
-
-     <row>
-      <entry>relchecks</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Number of check constraints on the table; see
-       <structname>pg_relcheck</structname> catalog
-      </entry>
-     </row>
-
-     <row>
-      <entry>reltriggers</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>
-       Number of triggers on the table; see
-       <structname>pg_trigger</structname> catalog
-      </entry>
-     </row>
-
-     <row>
-      <entry>relukeys</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>unused  (<emphasis>Not</emphasis> the number of unique keys)</entry>
-     </row>
-
-     <row>
-      <entry>relfkeys</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>unused  (<emphasis>Not</emphasis> the number of foreign keys on the table)</entry>
-     </row>
-
-     <row>
-      <entry>relrefs</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>unused</entry>
-     </row>
-
-     <row>
-      <entry>relhasoids</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>relhaspkey</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       True if the table has (or once had) a primary key.
-      </entry>
-     </row>
-
-     <row>
-      <entry>relhasrules</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Table has rules; see
-       <structname>pg_rewrite</structname> catalog
-      </entry>
-     </row>
-
-     <row>
-      <entry>relhassubclass</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>At least one table inherits from this one</entry>
-     </row>
-
-     <row>
-      <entry>relacl</entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>
-       Access permissions.  See the descriptions of
-       <command>GRANT</command> and <command>REVOKE</command> for
-       details.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-database">
-  <title>pg_database</title>
-
-  <para>
-   The <structname>pg_database</structname> catalog stores information
-   about the available databases.  Databases are created with the
-   <command>CREATE DATABASE</command> command.  Consult the
-   <citetitle>Administrator's Guide</citetitle> 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>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>datname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Database name</entry>
-     </row>
-
-     <row>
-      <entry>datdba</entry>
-      <entry><type>int4</type></entry>
-      <entry>pg_shadow.usesysid</entry>
-      <entry>Owner of the database, initially who created it</entry>
-     </row>
-
-     <row>
-      <entry>encoding</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>Character/multibyte encoding for this database</entry>
-     </row>
-
-     <row>
-      <entry>datistemplate</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       If true then this database can be used in the
-       <quote>TEMPLATE</quote> clause of <command>CREATE
-       DATABASE</command> to create a new database as a clone of
-       this one.
-      </entry>
-     </row>
-
-     <row>
-      <entry>datallowconn</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 template0 database from being altered.
-      </entry>
-     </row>
-
-     <row>
-      <entry>datlastsysoid</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>datvacuumxid</entry>
-      <entry><type>xid</type></entry>
-      <entry></entry>
-      <entry>
-       All tuples inserted or deleted by transaction IDs before this one
-       have been marked as known committed or known aborted in this database.
-       This is used to determine when commit-log space can be recycled.
-      </entry>
-     </row>
-
-     <row>
-      <entry>datfrozenxid</entry>
-      <entry><type>xid</type></entry>
-      <entry></entry>
-      <entry>
-       All tuples inserted by transaction IDs before this one have been
-       relabeled with a permanent (<quote>frozen</>) transaction ID in this
-       database.  This is useful to check whether a database must be vacuumed
-       soon to avoid transaction ID wraparound problems.
-      </entry>
-     </row>
-
-     <row>
-      <entry>datpath</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>
-       If the database is stored at an alternative location then this
-       records the location.  It's either an environment variable name
-       or an absolute path, depending how it was entered.
-      </entry>
-     </row>
-
-     <row>
-      <entry>datconfig</entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>Session defaults for run-time configuration variables</entry>
-     </row>
-
-     <row>
-      <entry>datacl</entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>Access permissions</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-
-
- <sect1 id="catalog-pg-description">
-  <title>pg_description</title>
-
-  <para>
-   The pg_description table can store an optional description or
-   comment for each database object.  Descriptions can be manipulated
-   with the <command>COMMENT</command> command.  Client applications
-   can view the descriptions by joining with this table.  Many built-in
-   system objects have comments associated with them that are shown by
-   <application>psql</application>'s <literal>\d</literal> commands.
-  </para>
-
-  <table>
-   <title>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>objoid</entry>
-      <entry><type>oid</type></entry>
-      <entry>any oid attribute</entry>
-      <entry>The oid of the object this description pertains to</entry>
-     </row>
-
-     <row>
-      <entry>classoid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The oid of the system catalog this object appears in</entry>
-     </row>
-
-     <row>
-      <entry>objsubid</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>For a comment on a table attribute, this is the attribute's
-       column number (the objoid and classoid refer to the table itself).
-       For all other object types, this field is presently zero.
-      </entry>
-     </row>
-
-     <row>
-      <entry>description</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-group">
-  <title>pg_group</title>
-
-  <para>
-   This catalog defines groups and stores what users belong to what
-   groups.  Groups are created with the <command>CREATE
-   GROUP</command> command.  Consult the <citetitle>Administrator's
-   Guide</citetitle> for information about user permission management.
-  </para>
-
-  <para>
-   Because user and group identities are cluster-wide,
-   <structname>pg_group</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_group</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title>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>groname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the group</entry>
-     </row>
-
-     <row>
-      <entry>grosysid</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>An arbitrary number to identify this group</entry>
-     </row>
-
-     <row>
-      <entry>grolist</entry>
-      <entry><type>int4[]</type></entry>
-      <entry>pg_shadow.usesysid</entry>
-      <entry>An array containing the ids of the users in this group</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-index">
-  <title>pg_index</title>
-
-  <para>
-   <structname>pg_index</structname> contains part of the information
-   about indexes.  The rest is mostly in
-   <structname>pg_class</structname>.
-  </para>
-
-  <table>
-   <title>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>indexrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The oid of the pg_class entry for this index</entry>
-     </row>
-
-     <row>
-      <entry>indrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The oid of the pg_class entry for the table this index is for</entry>
-     </row>
-
-     <row>
-      <entry>indproc</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>The registered procedure if this is a functional index</entry>
-     </row>
-
-     <row>
-      <entry>indkey</entry>
-      <entry><type>int2vector</type></entry>
-      <entry>pg_attribute.attnum</entry>
-      <entry>
-       This is a vector (array) of up to
-       <symbol>INDEX_MAX_KEYS</symbol> values that indicate which
-       table columns this index pertains to.  For example a value of
-       <literal>1 3</literal> would mean that the first and the third
-       column make up the index key.
-      </entry>
-     </row>
-
-     <row>
-      <entry>indclass</entry>
-      <entry><type>oidvector</type></entry>
-      <entry>pg_opclass.oid</entry>
-      <entry>
-       For each column in the index key this contains a reference to
-       the <quote>operator class</quote> to use.  See
-       <structname>pg_opclass</structname> for details.
-      </entry>
-     </row>
-
-     <row>
-      <entry>indisclustered</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>unused</entry>
-     </row>
-
-     <row>
-      <entry>indisunique</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, this is a unique index.</entry>
-     </row>
-
-     <row>
-      <entry>indisprimary</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>If true, this index represents the primary key of the table.
-      (indisunique should always be true when this is true.)</entry>
-     </row>
-
-     <row>
-      <entry>indreference</entry>
-      <entry><type>oid</type></entry>
-      <entry></entry>
-      <entry>unused</entry>
-     </row>
-
-     <row>
-      <entry>indpred</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Expression tree (in the form of a nodeToString representation)
-      for partial index predicate</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-inherits">
-  <title>pg_inherits</title>
-
-  <para>
-   This catalog records information about table inheritance hierarchies.
-  </para>
-
-  <table>
-   <title>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>inhrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>
-       This is the reference to the subtable, that is, it records the
-       fact that the identified table is inherited from some other
-       table.
-      </entry>
-     </row>
-
-     <row>
-      <entry>inhparent</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>
-       This is the reference to the parent table, which the table
-       referenced by <structfield>inhrelid</structfield> inherited
-       from.
-      </entry>
-     </row>
-
-     <row>
-      <entry>inhseqno</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       If there is more than one parent for a subtable (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>pg_language</title>
-
-  <para>
-   <structname>pg_language</structname> registers call interfaces or
-   languages in which you can write functions or stored procedures.
-   See under <command>CREATE LANGUAGE</command> and in the
-   <citetitle>Programmer's Guide</citetitle> for more information
-   about language handlers.
-  </para>
-
-  <table>
-   <title>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>lanname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the language (to be specified when creating a function)</entry>
-     </row>
-
-     <row>
-      <entry>lanispl</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This is false for internal languages (such as SQL) and true for
-       dynamically loaded language handler modules.  It essentially
-       means that, if it is true, the language may be dropped.
-      </entry>
-     </row>
-
-     <row>
-      <entry>lanpltrusted</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       This is a trusted language.  See under <command>CREATE
-       LANGUAGE</command> what this means.  If this is an internal
-       language (<structfield>lanispl</structfield> is false) then
-       this field is meaningless.
-      </entry>
-     </row>
-
-     <row>
-      <entry>lanplcallfoid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>
-       For non-internal 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>lanvalidator</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>
-       This references a language validator function that is responsible
-       for checking the syntax and validity of new functions when they
-       are created. See under <command>CREATE LANGUAGE</command> for
-       further information about validators.
-      </entry>
-     </row>
-
-     <row>
-      <entry>lancompiler</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>not currently used</entry>
-     </row>
-
-     <row>
-      <entry>lanacl</entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>Access permissions</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-largeobject">
-  <title>pg_largeobject</title>
-
-  <para>
-   <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 LOBLKSIZE (which is currently
-   BLCKSZ/4, or typically 2Kbytes).
-  </para>
-
-  <table>
-   <title>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>loid</entry>
-      <entry><type>oid</type></entry>
-      <entry></entry>
-      <entry>Identifier of the large object that includes this page</entry>
-     </row>
-
-     <row>
-      <entry>pageno</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>data</entry>
-      <entry><type>bytea</type></entry>
-      <entry></entry>
-      <entry>
-       Actual data stored in the large object.
-       This will never be more than LOBLKSIZE bytes, and may 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 (pageno * LOBLKSIZE) within the object.  The implementation
-   allows sparse storage: pages may be missing, and may be shorter than
-   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-listener">
-  <title>pg_listener</title>
-
-  <para>
-   <structname>pg_listener</structname> supports the <command>LISTEN</>
-   and <command>NOTIFY</> commands.  A listener creates an entry in
-   <structname>pg_listener</structname> for each notification name
-   it is listening for.  A notifier scans <structname>pg_listener</structname>
-   and updates each matching entry to show that a notification has occurred.
-   The notifier also sends a signal (using the PID recorded in the table)
-   to awaken the listener from sleep.
-  </para>
-
-  <table>
-   <title>pg_listener Columns</title>
-
-   <tgroup cols=4>
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>relname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Notify condition name.  (The name need not match any actual
-      relation in the database; the term <quote>relname</> is historical.)
-      </entry>
-     </row>
-
-     <row>
-      <entry>listenerpid</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>PID of the backend process that created this entry.</entry>
-     </row>
-
-     <row>
-      <entry>notification</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>
-       Zero if no event is pending for this listener.  If an event is
-       pending, the PID of the backend that sent the notification.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-namespace">
-  <title>pg_namespace</title>
-
-  <para>
-   A namespace is the structure underlying SQL92 schemas: each namespace
-   can have a separate collection of relations, types, etc without name
-   conflicts.
-  </para>
-
-  <table>
-   <title>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>nspname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the namespace</entry>
-     </row>
-
-     <row>
-      <entry>nspowner</entry>
-      <entry><type>int4</type></entry>
-      <entry>pg_shadow.usesysid</entry>
-      <entry>Owner (creator) of the namespace</entry>
-     </row>
-
-     <row>
-      <entry>nspacl</entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>Access permissions</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-operator">
-  <title>pg_operator</title>
-
-  <para>
-   See <command>CREATE OPERATOR</command> and the
-   <citetitle>Programmer's Guide</citetitle> for details on these
-   operator parameters.
-  </para>
-
-  <table>
-   <title>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>oprname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the operator</entry>
-     </row>
-
-     <row>
-      <entry>oprnamespace</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_namespace.oid</entry>
-      <entry>
-       The OID of the namespace that contains this operator
-      </entry>
-     </row>
-
-     <row>
-      <entry>oprowner</entry>
-      <entry><type>int4</type></entry>
-      <entry>pg_shadow.usesysid</entry>
-      <entry>Owner (creator) of the operator</entry>
-     </row>
-
-     <row>
-      <entry>oprprec</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>precedence (currently unused, as precedences are hard-wired
-      in the grammar)</entry>
-     </row>
-
-     <row>
-      <entry>oprkind</entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>
-       'b' = infix (<quote>both</quote>), 'l' = prefix
-       (<quote>left</quote>), 'r' = postfix (<quote>right</quote>)
-      </entry>
-     </row>
-
-     <row>
-      <entry>oprisleft</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>left-associativity (currently unused, as this is hard-wired
-      in the grammar)</entry>
-     </row>
-
-     <row>
-      <entry>oprcanhash</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>This operator supports hash joins.</entry>
-     </row>
-
-     <row>
-      <entry>oprleft</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry>Type of the left operand</entry>
-     </row>
-
-     <row>
-      <entry>oprright</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry>Type of the right operand</entry>
-     </row>
-
-     <row>
-      <entry>oprresult</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry>Type of the result</entry>
-     </row>
-
-     <row>
-      <entry>oprcom</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_operator.oid</entry>
-      <entry>Commutator of this operator, if any</entry>
-     </row>
-
-     <row>
-      <entry>oprnegate</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_operator.oid</entry>
-      <entry>Negator of this operator, if any</entry>
-     </row>
-
-     <row>
-      <entry>oprlsortop</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_operator.oid</entry>
-      <entry>
-       If this operator supports merge joins, the operator that sorts
-       the type of the left-hand operand (<literal>L&lt;L</>)
-      </entry>
-     </row>
-
-     <row>
-      <entry>oprrsortop</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_operator.oid</entry>
-      <entry>
-       If this operator supports merge joins, the operator that sorts
-       the type of the right-hand operand (<literal>R&lt;R</>)
-      </entry>
-     </row>
-
-     <row>
-      <entry>oprltcmpop</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_operator.oid</entry>
-      <entry>
-       If this operator supports merge joins, the less-than operator that
-       compares the left and right operand types (<literal>L&lt;R</>)
-      </entry>
-     </row>
-
-     <row>
-      <entry>oprgtcmpop</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_operator.oid</entry>
-      <entry>
-       If this operator supports merge joins, the greater-than operator that
-       compares the left and right operand types (<literal>L&gt;R</>)
-      </entry>
-     </row>
-
-     <row>
-      <entry>oprcode</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>Function that implements this operator</entry>
-     </row>
-
-     <row>
-      <entry>oprrest</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>Restriction selectivity estimation function for this operator</entry>
-     </row>
-
-     <row>
-      <entry>oprjoin</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>Join selectivity estimation function for this operator</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-proc">
-  <title>pg_proc</title>
-
-  <para>
-   This catalog stores information about functions (or procedures).
-   The description of <command>CREATE FUNCTION</command> and the
-   <citetitle>Programmer's Guide</citetitle> contain more information
-   about the meaning of some fields.
-  </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 <structname>pg_aggregate</structname>.
-  </para>
-
-  <table>
-   <title>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>proname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Name of the function</entry>
-     </row>
-
-     <row>
-      <entry>pronamespace</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_namespace.oid</entry>
-      <entry>
-       The OID of the namespace that contains this function
-      </entry>
-     </row>
-
-     <row>
-      <entry>proowner</entry>
-      <entry><type>int4</type></entry>
-      <entry>pg_shadow.usesysid</entry>
-      <entry>Owner (creator) of the function</entry>
-     </row>
-
-     <row>
-      <entry>prolang</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_language.oid</entry>
-      <entry>Implementation language or call interface of this function</entry>
-     </row>
-
-     <row>
-      <entry>proisagg</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Function is an aggregate function</entry>
-     </row>
-
-     <row>
-      <entry>proistrusted</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>not functional</entry>
-     </row>
-
-     <row>
-      <entry>proimplicit</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Function may be invoked as an implicit type coercion</entry>
-     </row>
-
-     <row>
-      <entry>proisstrict</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>proretset</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>Function returns a set (ie, multiple values of the specified
-      data type)</entry>
-     </row>
-
-     <row>
-      <entry>provolatile</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 may 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>pronargs</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Number of arguments</entry>
-     </row>
-
-     <row>
-      <entry>prorettype</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry>Data type of the return value (0 if the function does not return a value)</entry>
-     </row>
-
-     <row>
-      <entry>proargtypes</entry>
-      <entry><type>oidvector</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry>A vector with the data types of the function arguments</entry>
-     </row>
-
-     <row>
-      <entry>probyte_pct</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>dead code</entry>
-     </row>
-
-     <row>
-      <entry>properbyte_cpu</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>dead code</entry>
-     </row>
-
-     <row>
-      <entry>propercall_cpu</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>dead code</entry>
-     </row>
-
-     <row>
-      <entry>prooutin_ratio</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>dead code</entry>
-     </row>
-
-     <row>
-      <entry>prosrc</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>probin</entry>
-      <entry><type>bytea</type></entry>
-      <entry></entry>
-      <entry>Additional information about how to invoke the function.
-      Again, the interpretation is language-specific.
-      </entry>
-     </row>
-
-     <row>
-      <entry>proacl</entry>
-      <entry><type>aclitem[]</type></entry>
-      <entry></entry>
-      <entry>Access permissions</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-  Currently, prosrc contains the function's C-language name (link symbol)
-  for compiled functions, both built-in and dynamically loaded.  For all
-  other language types, prosrc contains the function's source text.
-  </para>
-
-  <para>
-  Currently, probin 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-relcheck">
-  <title>pg_relcheck</title>
-
-  <para>
-   This system catalog stores CHECK constraints on tables.  (Column
-   constraints are not treated specially.  Every column constraint is
-   equivalent to some table constraint.)  See under <command>CREATE
-   TABLE</command> for more information.
-  </para>
-
-  <table>
-   <title>pg_relcheck Columns</title>
-
-   <tgroup cols=4>
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>References</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>rcrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The table this check constraint is on</entry>
-     </row>
-
-     <row>
-      <entry>rcname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Constraint name</entry>
-     </row>
-
-     <row>
-      <entry>rcbin</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>An internal representation of the constraint expression</entry>
-     </row>
-
-     <row>
-      <entry>rcsrc</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>A human-readable representation of the constraint expression</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-   <para>
-    <structname>pg_class</structname>.<structfield>relchecks</structfield>
-    needs to match up with the entries in this table.
-   </para>
-  </note>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-rewrite">
-  <title>pg_rewrite</title>
-
-  <para>
-   This system catalog stores rewrite rules for tables and views.
-  </para>
-
-  <table>
-   <title>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>rulename</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Rule name</entry>
-     </row>
-
-     <row>
-      <entry>ev_type</entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry>Event type that the rule is for: '1' = SELECT,
-      '2' = UPDATE, '3' = INSERT, '4' = DELETE</entry>
-     </row>
-
-     <row>
-      <entry>ev_class</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The table this rule is for</entry>
-     </row>
-
-     <row>
-      <entry>ev_attr</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>is_instead</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if the rule is an INSTEAD rule</entry>
-     </row>
-
-     <row>
-      <entry>ev_qual</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Expression tree (in the form of a nodeToString representation)
-      for the rule's qualifying condition</entry>
-     </row>
-
-     <row>
-      <entry>ev_action</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Query tree (in the form of a nodeToString representation)
-      for the rule's action</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-   <para>
-    <structname>pg_class</structname>.<structfield>relhasrules</structfield>
-    must be true if a table has any rules in this catalog.
-   </para>
-  </note>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-shadow">
-  <title>pg_shadow</title>
-
-  <para>
-   <structname>pg_shadow</structname> contains information about
-   database users.  The name stems from the fact that this table
-   should not be readable by the public since it contains passwords.
-   <structname>pg_user</structname> is a publicly readable view on
-   <structname>pg_shadow</structname> that blanks out the password field.
-  </para>
-
-  <para>
-   The <citetitle>Administrator's Guide</citetitle> contains detailed
-   information about user and permission management.
-  </para>
-
-  <para>
-   Because user identities are cluster-wide,
-   <structname>pg_shadow</structname>
-   is shared across all databases of a cluster: there is only one
-   copy of <structname>pg_shadow</structname> per cluster, not
-   one per database.
-  </para>
-
-  <table>
-   <title>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>usename</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>User name</entry>
-     </row>
-
-     <row>
-      <entry>usesysid</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>User id (arbitrary number used to reference this user)</entry>
-     </row>
-
-     <row>
-      <entry>usecreatedb</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>User may create databases</entry>
-     </row>
-
-     <row>
-      <entry>usetrace</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>not used</entry>
-     </row>
-
-     <row>
-      <entry>usesuper</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>User is a superuser</entry>
-     </row>
-
-     <row>
-      <entry>usecatupd</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>
-       User may update system catalogs.  (Even a superuser may not do
-       this unless this attribute is true.)
-      </entry>
-     </row>
-
-     <row>
-      <entry>passwd</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry>Password</entry>
-     </row>
-
-     <row>
-      <entry>valuntil</entry>
-      <entry><type>abstime</type></entry>
-      <entry></entry>
-      <entry>Account expiry time (only used for password authentication)</entry>
-     </row>
-
-     <row>
-      <entry>useconfig</entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>Session defaults for run-time configuration variables</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-statistic">
-  <title>pg_statistic</title>
-
-  <para>
-   <structname>pg_statistic</structname> stores statistical data about
-   the contents of the database.  Entries are created by
-   <command>ANALYZE</command> and subsequently used by the query planner.
-   There is one entry for each table column that has been analyzed.
-   Note that all the statistical data is inherently approximate,
-   even assuming that it is up-to-date.
-  </para>
-
-  <para>
-   Since different kinds of statistics may 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 NULL-ness) 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
-   may be considered sensitive.  (Example: minimum and maximum values
-   of a salary column might be quite interesting.)
-   <structname>pg_stats</structname> is a publicly readable view on
-   <structname>pg_statistic</structname> that only exposes information
-   about those tables that are readable by the current user.
-   <structname>pg_stats</structname> is also designed to present the
-   information in a more readable format than the underlying
-   <structname>pg_statistic</structname> table --- at the cost that
-   its schema must be extended whenever new slot types are added.
-  </para>
-
-  <table>
-   <title>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>starelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The table that the described column belongs to</entry>
-     </row>
-
-     <row>
-      <entry>staattnum</entry>
-      <entry><type>int2</type></entry>
-      <entry>pg_attribute.attnum</entry>
-      <entry>The number of the described column</entry>
-     </row>
-
-     <row>
-      <entry>stanullfrac</entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>The fraction of the column's entries that are NULL</entry>
-     </row>
-
-     <row>
-      <entry>stawidth</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry>The average stored width, in bytes, of non-NULL entries</entry>
-     </row>
-
-     <row>
-      <entry>stadistinct</entry>
-      <entry><type>float4</type></entry>
-      <entry></entry>
-      <entry>The number of distinct non-NULL 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 fraction of the number
-      of rows in the table (for example, a column in which values appear about
-      twice on the average could be represented by stadistinct = -0.5).
-      A zero value means the number of distinct values is unknown.
-      </entry>
-     </row>
-
-     <row>
-      <entry>stakindN</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>A code number indicating the kind of statistics stored in the Nth
-      <quote>slot</quote> of the <structname>pg_statistic</structname> row.
-      </entry>
-     </row>
-
-     <row>
-      <entry>staopN</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_operator.oid</entry>
-      <entry>An operator used to derive the statistics stored in the
-      Nth <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>stanumbersN</entry>
-      <entry><type>float4[]</type></entry>
-      <entry></entry>
-      <entry>Numerical statistics of the appropriate kind for the Nth
-      <quote>slot</quote>, or NULL if the slot kind does not involve numerical values.
-      </entry>
-     </row>
-
-     <row>
-      <entry>stavaluesN</entry>
-      <entry><type>text[]</type></entry>
-      <entry></entry>
-      <entry>Column data values of the appropriate kind for the Nth
-      <quote>slot</quote>, or NULL if the slot kind does not store any data values.
-      For data-type independence, all column data values are converted
-      to external textual form and stored as TEXT datums.
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-trigger">
-  <title>pg_trigger</title>
-
-  <para>
-   This system catalog stores triggers on tables.  See under
-   <command>CREATE TRIGGER</command> for more information.
-  </para>
-
-  <table>
-   <title>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>tgrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The table this trigger is on</entry>
-     </row>
-
-     <row>
-      <entry>tgname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Trigger name (need not be unique)</entry>
-     </row>
-
-     <row>
-      <entry>tgfoid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>The function to be called</entry>
-     </row>
-
-     <row>
-      <entry>tgtype</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Bitmask identifying trigger conditions</entry>
-     </row>
-
-     <row>
-      <entry>tgenabled</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if trigger is enabled (not presently checked everywhere
-      it should be, so disabling a trigger by setting this false does not
-      work reliably)</entry>
-     </row>
-
-     <row>
-      <entry>tgisconstraint</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if trigger is a RI constraint</entry>
-     </row>
-
-     <row>
-      <entry>tgconstrname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>RI constraint name</entry>
-     </row>
-
-     <row>
-      <entry>tgconstrrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>The table referenced by an RI constraint</entry>
-     </row>
-
-     <row>
-      <entry>tgdeferrable</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if deferrable</entry>
-     </row>
-
-     <row>
-      <entry>tginitdeferred</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry>True if initially deferred</entry>
-     </row>
-
-     <row>
-      <entry>tgnargs</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Number of argument strings passed to trigger function</entry>
-     </row>
-
-     <row>
-      <entry>tgattr</entry>
-      <entry><type>int2vector</type></entry>
-      <entry></entry>
-      <entry>Currently unused</entry>
-     </row>
-
-     <row>
-      <entry>tgargs</entry>
-      <entry><type>bytea</type></entry>
-      <entry></entry>
-      <entry>Argument strings to pass to trigger, each null-terminated</entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <note>
-   <para>
-    <structname>pg_class</structname>.<structfield>reltriggers</structfield>
-    needs to match up with the entries in this table.
-   </para>
-  </note>
-
- </sect1>
-
-
- <sect1 id="catalog-pg-type">
-  <title>pg_type</title>
-
-  <para>
-   This catalog stores information about data types.  Scalar types
-   (<quote>base types</>) are created with <command>CREATE TYPE</command>.
-   A complex type is also created for each table in the database, to
-   represent the row structure of the table.  It is also possible to create
-   derived types with <command>CREATE DOMAIN</command>.
-  </para>
-
-  <table>
-   <title>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>typname</entry>
-      <entry><type>name</type></entry>
-      <entry></entry>
-      <entry>Data type name</entry>
-     </row>
-
-     <row>
-      <entry>typnamespace</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_namespace.oid</entry>
-      <entry>
-       The OID of the namespace that contains this type
-      </entry>
-     </row>
-
-     <row>
-      <entry>typowner</entry>
-      <entry><type>int4</type></entry>
-      <entry>pg_shadow.usesysid</entry>
-      <entry>Owner (creator) of the type</entry>
-     </row>
-
-     <row>
-      <entry>typlen</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>Length of the storage representation of the type, -1 if variable length</entry>
-     </row>
-
-     <row>
-      <entry>typprtlen</entry>
-      <entry><type>int2</type></entry>
-      <entry></entry>
-      <entry>unused</entry>
-     </row>
-
-     <row>
-      <entry>typbyval</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.
-       Only <type>char</type>, <type>short</type>, and
-       <type>int</type> equivalent items can be passed by value, so if
-       the type is not 1, 2, or 4 bytes long,
-       <productname>PostgreSQL</> does not have
-       the option of passing by value and so
-       <structfield>typbyval</structfield> had better be false.
-       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; this is currently true for
-       type <type>float4</type>, for example.
-      </entry>
-     </row>
-
-     <row>
-      <entry>typtype</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 complex type (i.e.,
-       a table's row type), or <literal>d</literal> for a derived type (i.e.,
-       a domain).  See also <structfield>typrelid</structfield> 
-       and <structfield>typbasetype</structfield>.
-      </entry>
-     </row>
-
-     <row>
-      <entry>typisdefined</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 typisdefined is false,
-      nothing except the type name and OID can be relied on.
-      </entry>
-     </row>
-
-     <row>
-      <entry>typdelim</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>typrelid</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_class.oid</entry>
-      <entry>
-       If this is a complex type (see
-       <structfield>typtype</structfield>), then this field points to
-       the <structfield>pg_class</structfield> entry that defines the
-       corresponding table. A table could theoretically be used as a
-       composite data type, but this is not fully functional.
-       Zero for non-complex types.
-      </entry>
-     </row>
-
-     <row>
-      <entry>typelem</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</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>oidvector</type>.
-       If a fixed-length type has a <structfield>typelem</structfield> then
-       its internal representation must be N 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>typinput</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>Input function</entry>
-     </row>
-
-     <row>
-      <entry>typoutput</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>Output function</entry>
-     </row>
-
-     <row>
-      <entry>typreceive</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>unused</entry>
-     </row>
-
-     <row>
-      <entry>typsend</entry>
-      <entry><type>regproc</type></entry>
-      <entry>pg_proc.oid</entry>
-      <entry>unused</entry>
-     </row>
-
-     <row>
-      <entry>typalign</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>'c' = CHAR alignment, i.e., no alignment needed.</para>
-        </listitem>
-        <listitem>
-         <para>'s' = SHORT alignment (2 bytes on most machines).</para>
-        </listitem>
-        <listitem>
-         <para>'i' = INT alignment (4 bytes on most machines).</para>
-        </listitem>
-        <listitem>
-         <para>'d' = DOUBLE 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 field in
-        a struct representing a table row.
-       </para>
-      </note></entry>
-     </row>
-
-     <row>
-      <entry>typstorage</entry>
-      <entry><type>char</type></entry>
-      <entry></entry>
-      <entry><para>
-       <structfield>typstorage</structfield> tells for variable-length
-       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>'p': Value must always be stored plain.</para>
-        </listitem>
-        <listitem>
-         <para>
-          'e': Value can be stored in a <quote>secondary</quote>
-          relation (if relation has one, see
-          <structname>pg_class</structname>.<structfield>reltoastrelid</structfield>).
-         </para>
-        </listitem>
-        <listitem>
-         <para>'m': Value can be stored compressed inline.</para>
-        </listitem>
-        <listitem>
-         <para>'x': Value can be stored compressed inline or in <quote>secondary</quote>.</para>
-        </listitem>
-       </itemizedlist>
-       Note that 'm' fields can also be moved out to secondary
-       storage, but only as a last resort ('e' and 'x' fields are
-       moved first).
-      </para></entry>
-     </row>
-
-     <row>
-      <entry>typnotnull</entry>
-      <entry><type>bool</type></entry>
-      <entry></entry>
-      <entry><para>
-       <structfield>typnotnull</structfield> represents a NOT NULL
-       constraint on a type.  Presently used for domains only.
-      </para></entry>
-     </row>
-
-     <row>
-      <entry>typbasetype</entry>
-      <entry><type>oid</type></entry>
-      <entry>pg_type.oid</entry>
-      <entry><para>
-       If this is a derived type (see <structfield>typtype</structfield>),
-       then <structfield>typbasetype</structfield> identifies
-       the type that this one is based on.  Zero if not a derived type.
-      </para></entry>
-     </row>
-
-     <row>
-      <entry>typtypmod</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry><para>
-       <structfield>typtypmod</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 and output functions as the third
-       argument. The value will generally be -1 for types that do not
-       need typmod.  This value is copied to
-       <structfield>pg_attribute.atttypmod</structfield> when
-       creating a column of a domain type.
-       </para></entry>
-     </row>
-
-     <row>
-      <entry>typndims</entry>
-      <entry><type>int4</type></entry>
-      <entry></entry>
-      <entry><para>
-       <structfield>typndims</structfield> is the number of array dimensions
-       for a domain that is an array.  (The array element type is
-       typbasetype.)  Zero for non-domains and non-array domains.
-       This value is copied to
-       <structfield>pg_attribute.attndims</structfield> when
-       creating a column of a domain type.
-       </para></entry>
-     </row>
-
-     <row>
-      <entry>typdefaultbin</entry>
-      <entry><type>text</type></entry>
-      <entry></entry>
-      <entry><para>
-       If <structfield>typdefaultbin</> is not NULL, it is the nodeToString
-       representation of a default expression for the type.  Currently this is
-       only used for domains.
-      </para></entry>
-     </row>
-
-     <row>
-      <entry>typdefault</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 may be fed to the type's input
-       converter to produce a constant.
-      </para></entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-tabs-mode:nil
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/share/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml
deleted file mode 100644
index a19940ce9a6..00000000000
--- a/doc/src/sgml/charset.sgml
+++ /dev/null
@@ -1,1259 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/charset.sgml,v 2.24 2002/04/03 05:39:27 petere Exp $ -->
-
-<chapter id="charset">
- <title>Localization</>
-
- <abstract>
-  <para>
-   Describes the available localization features from the point of
-   view of the administrator.
-  </para>
- </abstract>
-
-  <para>
-   <productname>PostgreSQL</productname> supports localization with
-   three approaches:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Using the locale features of the operating system to provide
-      locale-specific collation order, number formatting, translated
-      messages, and other aspects.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Using explicit multiple-byte character sets defined in the
-      <productname>PostgreSQL</productname> server to support languages
-      that require more characters than will fit into a single byte,
-      and to provide character set recoding between client and server.
-      The number of supported character sets is fixed at the time the
-      server is compiled, and internal operations such as string
-      comparisons require expansion of each character into a 32-bit
-      word.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Single byte character recoding provides a more light-weight
-      solution for users of multiple, yet single-byte character sets.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-
- <sect1 id="locale">
-  <title>Locale Support</title>
-  
-  <indexterm zone="locale"><primary>locale</></>
-
-  <para>
-   <firstterm>Locale</> support refers to an application respecting
-   cultural preferences regarding alphabets, sorting, number
-   formatting, etc.  <productname>PostgreSQL</> uses the standard ISO
-   C and <acronym>POSIX</acronym>-like locale facilities provided by the server operating
-   system.  For additional information refer to the documentation of your
-   system.
-  </para>
-
-  <sect2>
-   <title>Overview</>
-
-   <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; 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 tell
-    <command>initdb</command> exactly which locale you want with the
-    option <option>--locale</option>.  For example:
-<screen>
-<prompt>$ </><userinput>initdb --locale=sv_SE</>
-</screen>
-   </para>
-
-   <para>
-    This example sets the locale to Swedish (<literal>sv</>) as spoken in
-    Sweden (<literal>SE</>).  Other possibilities might be
-    <literal>en_US</> (U.S. English) and <literal>fr_CA</> (Canada,
-    French).  If more than one character set can be useful for a locale
-    then the specifications look like this:
-    <literal>cs_CZ.ISO8859-2</>. What locales are available under what
-    names on your system depends on what was provided by the operating
-    system vendor and what was installed.
-   </para>
-
-   <para>
-    Occasionally it is useful to mix rules from several locales, e.g.,
-    use U.S. collation rules but Spanish messages.  To support that, a
-    set of locale subcategories exist that control only a certain
-    aspect 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? The 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 <literal>C</> or <literal>POSIX</>.
-   </para>
-
-   <para>
-    The nature of some locale categories is that their value has to be
-    fixed for the lifetime of a database cluster.  That is, once
-    <command>initdb</command> has run, you cannot change them anymore.
-    <literal>LC_COLLATE</literal> and <literal>LC_CTYPE</literal> are
-    those categories.  They affect the sort order of indexes, so they
-    must be kept fixed, or indexes on text columns will become corrupt.
-    <productname>PostgreSQL</productname> enforces this by recording
-    the values of <envar>LC_COLLATE</> and <envar>LC_CTYPE</> that are
-    seen by <command>initdb</>.  The server automatically adopts
-    those two values when it is started.
-   </para>
-
-   <para>
-    The other locale categories can be changed as desired whenever the
-    server is started by setting the run-time configuration variables
-    that have the same name as the locale categories (see <xref
-    linkend="runtime-config"> for details).  The defaults 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 delete the
-    assignments from <filename>postgresql.conf</filename> then the
-    server will inherit the settings from the 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 to different locales, messages may
-    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>
-     (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
-     <citerefentry><refentrytitle>gettext</><manvolnum>3</></> manual
-     page, for more information.
-    </para>
-   </note>
-
-   <para>
-    To enable messages translated to the user's preferred language,
-    the <option>--enable-nls</option> option must be used.  This
-    option is independent of the other locale support.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Benefits</>
-
-   <para>
-    Locale support influences in particular the following features:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Sort order in <command>ORDER BY</> queries.
-       <indexterm><primary>ORDER BY</></>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <function>to_char</> family of functions
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       The <literal>LIKE</> and <literal>~</> operators for pattern
-       matching
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    The only severe drawback of using the locale support in
-    <productname>PostgreSQL</> is its speed.  So use locale only if you
-    actually need it.  It should be noted in particular that selecting
-    a non-C locale disables index optimizations for <literal>LIKE</> and
-    <literal>~</> operators, which can make a huge difference in the
-    speed of searches that use those operators.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Problems</>
-
-   <para>
-    If locale support doesn't work in spite of the explanation above,
-    check that the locale support in your operating system is correctly configured.
-    To check whether a given locale is installed and functional you
-    can use <application>Perl</>, for example.  Perl has also support
-    for locales and if a locale is broken <command>perl -v</> will
-    complain something like this:
-<screen>
-<prompt>$</> <userinput>export LC_CTYPE='not_exist'</>
-<prompt>$</> <userinput>perl -v</>
-<computeroutput>
-perl: warning: Setting locale failed.
-perl: warning: Please check that your locale settings:
-LC_ALL = (unset),
-LC_CTYPE = "not_exist",
-LANG = (unset)
-are supported and installed on your system.
-perl: warning: Falling back to the standard locale ("C").
-</computeroutput>
-</screen>
-   </para>
-
-   <para>
-    Check that your locale files are in the right location.  Possible
-    locations include: <filename>/usr/lib/locale</filename> (<systemitem class="osname">Linux</>,
-    <systemitem class="osname">Solaris</>), <filename>/usr/share/locale</filename> (<systemitem class="osname">Linux</>),
-    <filename>/usr/lib/nls/loc</filename> (<systemitem class="osname">DUX 4.0</>).  Check the locale
-    man page of your system if you are not sure.
-   </para>
-
-   <para>
-    Check that <productname>PostgreSQL</> is actually using the locale that
-    you think it is.  <envar>LC_COLLATE</> and <envar>LC_CTYPE</> settings are
-    determined at <application>initdb</> time and cannot be changed without
-    repeating <application>initdb</>.  Other locale settings including
-    <envar>LC_MESSAGES</> and <envar>LC_MONETARY</> are determined by the 
-    environment the postmaster is started in, and can be changed with a simple
-    postmaster restart.  You can check the <envar>LC_COLLATE</> and
-    <envar>LC_CTYPE</> settings of
-    a database with the <filename>contrib/pg_controldata</> utility program.
-   </para>
-
-   <para>
-    The directory <filename>src/test/locale</> contains a test suite
-    for <productname>PostgreSQL</>'s locale support.
-   </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.  If you create such
-    an application you need to devise a plan to cope with this
-    situation.  The embedded SQL interface (<application>ecpg</>) is
-    also affected by this problem.  It is currently recommended that
-    servers interfacing with <application>ecpg</> applications be
-    configured to send messages in English.
-   </para>
-
-   <para>
-    Maintaining catalogs of message translations requires the on-going
-    efforts of many volunteers that want to see
-    <productname>PostgreSQL</> speak their preferred language well.
-    If messages in your language is currently not available or fully
-    translated, your assistance would be appreciated.  If you want to
-    help, refer to the <citetitle>Developer's Guide</> or write to the
-    developers' mailing list.
-   </para>
-  </sect2>
- </sect1>
-
-
-  <sect1 id="multibyte">
-   <title>Multibyte Support</title>
-
-  <indexterm zone="multibyte"><primary>multibyte</></>
-
-   <note>
-    <title>Author</title>
-
-    <para>
-     Tatsuo Ishii (<email>ishii@postgresql.org</email>),
-     last updated 2000-03-22.
-     Check <ulink
-      url="http://www.sra.co.jp/people/t-ishii/PostgreSQL/">Tatsuo's
-      web site</ulink> for more information.
-    </para>
-   </note>
-
-   <para>
-    Multibyte (<acronym>MB</acronym>) support is intended to allow
-    <productname>PostgreSQL</productname> to handle
-    multiple-byte character sets such as <acronym>EUC</> (Extended Unix Code), Unicode, and
-    Mule internal code. With <acronym>MB</acronym> enabled you can use multibyte
-    character sets in regular expressions (regexp), LIKE, and some
-    other functions. The default
-    encoding system is selected while initializing your
-    <productname>PostgreSQL</productname> installation using
-    <application>initdb</application>. Note that this can be
-    overridden when you create a database using
-    <application>createdb</application> or by using the SQL command
-    <command>CREATE DATABASE</>. So you can have multiple databases each with
-    a different encoding system.
-   </para>
-
-   <sect2>
-    <title>Enabling Multibyte Support</title>
-
-    <para>
-     Run configure with the multibyte option:
-
-<synopsis>
-./configure --enable-multibyte<optional>=<replaceable>encoding_system</replaceable></optional>
-</synopsis>
-
-     where <replaceable>encoding_system</replaceable> can be one of the
-     values in the following table:
-
-     <table tocentry="1">
-      <title>Character Set Encodings</title>
-      <titleabbrev>Encodings</titleabbrev>
-      <tgroup cols="2">
-       <thead>
-	<row>
-	 <entry>Encoding</entry>
-	 <entry>Description</entry>
-	</row>
-       </thead>
-       <tbody>
-	<row>
-	 <entry><literal>SQL_ASCII</literal></entry>
-	 <entry><acronym>ASCII</acronym></entry>
-	</row>
-	<row>
-	 <entry><literal>EUC_JP</literal></entry>
-	 <entry>Japanese <acronym>EUC</></entry>
-	</row>
-	<row>
-	 <entry><literal>EUC_CN</literal></entry>
-	 <entry>Chinese <acronym>EUC</></entry>
-	</row>
-	<row>
-	 <entry><literal>EUC_KR</literal></entry>
-	 <entry>Korean <acronym>EUC</></entry>
-	</row>
-	<row>
-	 <entry><literal>JOHAB</literal></entry>
-	 <entry>Korean <acronym>EUC</> (Hangle base)</entry>
-	</row>
-	<row>
-	 <entry><literal>EUC_TW</literal></entry>
-	 <entry>Taiwan <acronym>EUC</acronym></entry>
-	</row>
-	<row>
-	 <entry><literal>UNICODE</literal></entry>
-	 <entry>Unicode (<acronym>UTF</acronym>-8)</entry>
-	</row>
-	<row>
-	 <entry><literal>MULE_INTERNAL</literal></entry>
-	 <entry>Mule internal code</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN1</literal></entry>
-	 <entry>ISO 8859-1 ECMA-94 Latin Alphabet No.1</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN2</literal></entry>
-	 <entry>ISO 8859-2 ECMA-94 Latin Alphabet No.2</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN3</literal></entry>
-	 <entry>ISO 8859-3 ECMA-94 Latin Alphabet No.3</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN4</literal></entry>
-	 <entry>ISO 8859-4 ECMA-94 Latin Alphabet No.4</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN5</literal></entry>
-	 <entry>ISO 8859-9 ECMA-128 Latin Alphabet No.5</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN6</literal></entry>
-	 <entry>ISO 8859-10 ECMA-144 Latin Alphabet No.6</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN7</literal></entry>
-	 <entry>ISO 8859-13 Latin Alphabet No.7</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN8</literal></entry>
-	 <entry>ISO 8859-14 Latin Alphabet No.8</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN9</literal></entry>
-	 <entry>ISO 8859-15 Latin Alphabet No.9</entry>
-	</row>
-	<row>
-	 <entry><literal>LATIN10</literal></entry>
-	 <entry>ISO 8859-16 ASRO SR 14111 Latin Alphabet No.10</entry>
-	</row>
-	<row>
-	 <entry><literal>ISO-8859-5</literal></entry>
-	 <entry>ECMA-113 Latin/Cyrillic</entry>
-	</row>
-	<row>
-	 <entry><literal>ISO-8859-6</literal></entry>
-	 <entry>ECMA-114 Latin/Arabic</entry>
-	</row>
-	<row>
-	 <entry><literal>ISO-8859-7</literal></entry>
-	 <entry>ECMA-118 Latin/Greek</entry>
-	</row>
-	<row>
-	 <entry><literal>ISO-8859-8</literal></entry>
-	 <entry>ECMA-121 Latin/Hebrew</entry>
-	</row>
-	<row>
-	 <entry><literal>KOI8</literal></entry>
-	 <entry><acronym>KOI</acronym>8-R(U)</entry>
-	</row>
-	<row>
-	 <entry><literal>WIN</literal></entry>
-	 <entry>Windows CP1251</entry>
-	</row>
-	<row>
-	 <entry><literal>ALT</literal></entry>
-	 <entry>Windows CP866</entry>
-	</row>
-	<row>
-	 <entry><literal>WIN1256</literal></entry>
-	 <entry>Arabic Windows CP1256</entry>
-	</row>
-	<row>
-	 <entry><literal>TCVN</literal></entry>
-	 <entry>Vietnamese TCVN-5712(Windows CP1258)</entry>
-	</row>
-	<row>
-	 <entry><literal>WIN874</literal></entry>
-	 <entry>Thai Windows CP874</entry>
-	</row>
-       </tbody>
-      </tgroup>
-     </table>
-    </para>
-
-    <important>
-     <para>
-      Before <productname>PostgreSQL</>7.2, <literal>LATIN5</> mistakenly
-      meant ISO 8859-5.  From 7.2 on,
-      <literal>LATIN5</> means ISO 8859-9. If you have a <literal>LATIN5</>
-      database created on 7.1 or earlier and want to migrate to 7.2 (or
-      later), you should be very careful about this change.
-     </para>
-    </important>
-
-    <important>
-     <para>
-      Not all APIs supports all the encodings listed above. For example, the
-      <productname>PostgreSQL</>
-      JDBC driver does not support <literal>MULE_INTERNAL</>, <literal>LATIN6</>,
-      <literal>LATIN8</>, and <literal>LATIN10</>.
-     </para>
-    </important>
-    
-    <para>
-     Here is an example of configuring
-     <productname>PostgreSQL</productname> to use a Japanese encoding by
-     default:
-
-<screen>
-$ <userinput>./configure --enable-multibyte=EUC_JP</userinput>
-</screen>
-    </para>
-
-    <para>
-     If the encoding system is omitted (<literal>./configure --enable-multibyte</literal>),
-     <literal>SQL_ASCII</> is assumed.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Setting the Encoding</title>
-
-    <para>
-     <application>initdb</application> defines the default encoding
-     for a <productname>PostgreSQL</productname> installation. For example:
-
-<screen>
-$ <userinput>initdb -E EUC_JP</>
-</screen>
-
-     sets the default encoding to <literal>EUC_JP</literal> (Extended Unix Code for Japanese).
-     Note that you can use <option>--encoding</option> instead of <option>-E</option> if you prefer
-     to type longer option strings. 
-     If no <option>-E</> or <option>--encoding</option> option is given, the encoding
-     specified at configure time is used.
-    </para>
-
-    <para>
-     You can create a database with a different encoding:
-
-<screen>
-$ <userinput>createdb -E EUC_KR korean</>
-</screen>
-
-     will create a database named <database>korean</database> with <literal>EUC_KR</literal> encoding.
-     Another way to accomplish this is to use a SQL command:
-
-<programlisting>
-CREATE DATABASE korean WITH ENCODING = 'EUC_KR';
-</programlisting>
-
-     The encoding for a database is represented as an
-     <firstterm>encoding column</firstterm>  in the
-     <literal>pg_database</literal> system catalog.
-     You can see that by using the <option>-l</option> option or the
-     <command>\l</command> command of <command>psql</command>.
-
-<screen>
-$ <userinput>psql -l</userinput>
-            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)
-</screen>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Automatic encoding translation between server and
-     client</title>
-
-    <para>
-     <productname>PostgreSQL</productname> supports an automatic
-     encoding translation between server
-     and client for some encodings.  The available combinations are
-     listed in <xref linkend="multibyte-translation-table">.
-    </para>
-
-     <table tocentry="1" id="multibyte-translation-table">
-      <title>Client/Server Character Set Encodings</title>
-      <titleabbrev>Communication Encodings</titleabbrev>
-      <tgroup cols="2">
-       <thead>
-	<row>
-	 <entry>Server Encoding</entry>
-	 <entry>Available Client Encodings</entry>
-	</row>
-       </thead>
-       <tbody>
-	<row>
-	 <entry><literal>SQL_ASCII</literal></entry>
-	 <entry><literal>SQL_ASCII</literal>, <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>EUC_JP</literal></entry>
-	 <entry><literal>EUC_JP</literal>, <literal>SJIS</literal>,
-	 <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>EUC_CN</literal></entry>
-	 <entry><literal>EUC_CN</literal>, <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>EUC_KR</literal></entry>
-	 <entry><literal>EUC_KR</literal>, <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>JOHAB</literal></entry>
-	 <entry><literal>JOHAB</literal>, <literal>UNICODE</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>EUC_TW</literal></entry>
-	 <entry><literal>EUC_TW</literal>, <literal>BIG5</literal>,
-	 <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN1</literal></entry>
-	 <entry><literal>LATIN1</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN2</literal></entry>
-	 <entry><literal>LATIN2</literal>, <literal>WIN1250</literal>,
-	 <literal>UNICODE</literal>,
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN3</literal></entry>
-	 <entry><literal>LATIN3</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN4</literal></entry>
-	 <entry><literal>LATIN4</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN5</literal></entry>
-	 <entry><literal>LATIN5</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN6</literal></entry>
-	 <entry><literal>LATIN6</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN7</literal></entry>
-	 <entry><literal>LATIN7</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN8</literal></entry>
-	 <entry><literal>LATIN8</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN9</literal></entry>
-	 <entry><literal>LATIN9</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>  
-	 <entry><literal>LATIN10</literal></entry>
-	 <entry><literal>LATIN10</literal>, <literal>UNICODE</literal>
-	 <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>ISO_8859_5</literal></entry>
-	 <entry><literal>ISO_8859_5</literal>,
-	 <literal>UNICODE</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>ISO_8859_6</literal></entry>
-	 <entry><literal>ISO_8859_6</literal>,
-	 <literal>UNICODE</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>ISO_8859_7</literal></entry>
-	 <entry><literal>ISO_8859_7</literal>,
-	 <literal>UNICODE</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>ISO_8859_8</literal></entry>
-	 <entry><literal>ISO_8859_8</literal>,
-	 <literal>UNICODE</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>ISO_8859_9</literal></entry>
-	 <entry><literal>ISO_8859_9</literal>, <literal>WIN</literal>, 
-	 <literal>ALT</literal>, <literal>KOI8R</literal>,
-	 <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>UNICODE</literal></entry>
-	 <entry>
-	 <literal>EUC_JP</literal>, <literal>SJIS</literal>, 
-	 <literal>EUC_KR</literal>, <literal>UHC</literal>, <literal>JOHAB</literal>,
-	 <literal>EUC_CN</literal>, <literal>GBK</literal>,
-	 <literal>EUC_TW</literal>, <literal>BIG5</literal>, 
-	 <literal>LATIN1</literal> to <literal>LATIN10</literal>, 
-	 <literal>ISO_8859_5</literal>, 
-	 <literal>ISO_8859_6</literal>,
- 	 <literal>ISO_8859_7</literal>, 
-	 <literal>ISO_8859_8</literal>, 
-	 <literal>WIN</literal>, <literal>ALT</literal>, 
-	 <literal>KOI8</literal>, 
-	 <literal>WIN1256</literal>,
-	 <literal>TCVN</literal>,
-	 <literal>WIN874</literal>,
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>MULE_INTERNAL</literal></entry>
-	 <entry><literal>EUC_JP</literal>, <literal>SJIS</literal>, <literal>EUC_KR</literal>, <literal>EUC_CN</literal>, 
-	  <literal>EUC_TW</literal>, <literal>BIG5</literal>, <literal>LATIN1</literal> to <literal>LATIN5</literal>, 
-	  <literal>WIN</literal>, <literal>ALT</literal>, <literal>WIN1250</literal></entry>
-	</row>
-	<row>
-	 <entry><literal>KOI8</literal></entry>
-	 <entry><literal>ISO_8859_9</literal>, <literal>WIN</literal>, 
-	 <literal>ALT</literal>, <literal>KOI8</literal>,
-	 <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>WIN</literal></entry>
-	 <entry><literal>ISO_8859_9</literal>, <literal>WIN</literal>, 
-	 <literal>ALT</literal>, <literal>KOI8</literal>,
-	 <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>ALT</literal></entry>
-	 <entry><literal>ISO_8859_9</literal>, <literal>WIN</literal>, 
-	 <literal>ALT</literal>, <literal>KOI8</literal>,
-	 <literal>UNICODE</literal>, <literal>MULE_INTERNAL</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>WIN1256</literal></entry>
-	 <entry><literal>WIN1256</literal>,
-	 <literal>UNICODE</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>TCVN</literal></entry>
-	 <entry><literal>TCVN</literal>,
-	 <literal>UNICODE</literal>
-	 </entry>
-	</row>
-	<row>
-	 <entry><literal>WIN874</literal></entry>
-	 <entry><literal>WIN874</literal>,
-	 <literal>UNICODE</literal>
-	 </entry>
-	</row>
-       </tbody>
-      </tgroup>
-     </table>
-
-    <para>
-     To enable the automatic encoding translation, you have to tell
-     <productname>PostgreSQL</productname> the 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>
-	Using <application>libpq</> functions.
-	<command>\encoding</command> actually calls
-	<function>PQsetClientEncoding()</function> for its purpose.
-
-<synopsis>
-int PQsetClientEncoding(PGconn *<replaceable>conn</replaceable>, const char *<replaceable>encoding</replaceable>)
-</synopsis>
-
-	where <replaceable>conn</replaceable> is a connection to the server,
-	and <replaceable>encoding</replaceable> is an encoding you
-	want to use. If it successfully sets the encoding, it returns 0,
-	otherwise -1. The current encoding for this connection can be shown by
-	using:
-
-<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>
-
-      <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 'encoding';
-</programlisting>
-
-	Also you can use the SQL92 syntax <literal>SET NAMES</literal> for this purpose:
-
-<programlisting>
-SET NAMES 'encoding';
-</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 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>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>About Unicode</title>
-
-    <indexterm><primary>Unicode</></>
-
-    <para>
-     An automatic encoding translation between Unicode and other
-     encodings has been supported since <productname>PostgreSQL</> 7.1.
-     For 7.1 it was not enabled by default.
-     To enable this feature, run configure with the
-     <option>--enable-unicode-conversion</option> option. Note that this requires
-     the <option>--enable-multibyte</option> option also.
-    </para>
-    <para>
-    For 7.2, <option>--enable-unicode-conversion</option> is not necessary.
-    The Unicode conversion functionality is automatically enabled
-    if <option>--enable-multibyte</option> is specified.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>What happens if the translation is not possible?</title>
-
-    <para>
-     Suppose you choose <literal>EUC_JP</literal> for the server
-     and <literal>LATIN1</literal> for the client,
-     then some Japanese characters cannot be translated into <literal>LATIN1</literal>. In
-     this case, a letter that cannot be represented in the <literal>LATIN1</literal> character set
-     would be transformed as:
-
-<synopsis>
-(HEXA DECIMAL)
-</synopsis>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>References</title>
-
-    <para>
-     These are good sources to start learning about various kinds of encoding
-     systems.
-
-     <variablelist>
-      <varlistentry>
-       <term><ulink url="ftp://ftp.ora.com/pub/examples/nutshell/ujip/doc/cjk.inf"></ulink></term>
-
-       <listitem>
-        <para>
-         Detailed explanations of <literal>EUC_JP</literal>,
-         <literal>EUC_CN</literal>, <literal>EUC_KR</literal>,
-         <literal>EUC_TW</literal> appear in section 3.2.
-        </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 2044</term>
-
-       <listitem>
-        <para>
-	 <acronym>UTF</acronym>-8 is defined here.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>History</title>
-
-<literallayout class="monospaced">
-Dec 7, 2000
-	* An automatic encoding translation between Unicode and other
-	  encodings are implemented
-	* Changes above will appear in 7.1
-
-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 frontend 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>jonahkuo@mail.ttn.com.tw</email>)
-
-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 cleanliness
-
-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)
-	* 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 <productname>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
-</literallayout>
-   </sect2>
-
-   <sect2>
-    <title>WIN1250 on Windows/ODBC</title>
-
-    <para>
-<!--
-[Here is a good documentation explaining how to use WIN1250 on
-Windows/ODBC from Pavel Behal]
-
-Version: 0.91 for PgSQL 6.5
-Author: Pavel Behal
-Revised by: Tatsuo Ishii
-Email: behal@opf.slu.cz
-License: The Same as <productname>PostgreSQL</>
-
-Sorry for my Eglish and C code, I'm not native :-)
-
-!!!!!!!!!!!!!!!!!!!!!!!!! NO WARRANTY !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--->
-
-     The WIN1250 character set on Windows client platforms can be used
-     with <productname>PostgreSQL</productname> with locale support
-     enabled.
-    </para>
-
-    <para>
-     The following should be kept in mind:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-	Success depends on proper system locales. This has been tested
-	with <systemitem class="osname">Red Hat 6.0</> and <systemitem
-	class="osname">Slackware 3.6</>, with the
-        <literal>cs_CZ.iso8859-2</literal> locale.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-	Never try to set the server's database encoding to WIN1250.
-	Always use LATIN2 instead since there is no WIN1250 locale
-	in Unix.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-	The WIN1250 encoding is usable only for Windows ODBC clients. The
-	characters are recoded on the fly, to be displayed and stored
-	back properly.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <procedure>
-     <title>WIN1250 on Windows/ODBC</title>
-     <step>
-      <para>
-       Compile <productname>PostgreSQL</productname> with locale enabled
-       and the server-side encoding set to <literal>LATIN2</literal>.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Set up your installation. Do not forget to create locale
-       variables in your environment. For example (this may
-       not be correct for <emphasis>your</emphasis> environment):
-
-<programlisting>
-LC_ALL=cs_CZ.ISO8859-2
-</programlisting>
-      </para>
-     </step>
-
-     <step>
-      <para>
-       You have to start the server with locales set!
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Try it with the Czech language, and have it sort on a query.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Install ODBC driver for <productname>PostgreSQL</productname> on your Windows machine.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Set up your data source properly. Include this line in your ODBC
-       configuration dialog in the field <guilabel>Connect Settings</guilabel>:
-
-<programlisting>
-SET CLIENT_ENCODING = 'WIN1250';
-</programlisting>
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Now try it again, but in Windows with ODBC.
-      </para>
-     </step>
-    </procedure>
-   </sect2>
-  </sect1>
-
-
- <sect1 id="recode">
-  <title>Single-byte character set recoding</>
-<!-- formerly in README.charsets, by Josef Balatka, <balatka@email.cz> -->
-
-  <para>
-   You can set up this feature with the <option>--enable-recode</> option
-   to <filename>configure</>. This option was formerly described as
-   <quote>Cyrillic recode support</> which doesn't express all its
-   power. It can be used for <emphasis>any</> single-byte character
-   set recoding.
-  </para>
-
-  <para>
-   This method uses a file <filename>charset.conf</> file located in
-   the database directory (<envar>PGDATA</>).  It's a typical
-   configuration text file where spaces and newlines separate items
-   and records and # specifies comments.  Three keywords with the
-   following syntax are recognized here:
-<synopsis>
-BaseCharset      <replaceable>server_charset</>
-RecodeTable      <replaceable>from_charset</> <replaceable>to_charset</> <replaceable>file_name</>
-HostCharset      <replaceable>host_spec</>    <replaceable>host_charset</>
-</synopsis>
-  </para>
-
-  <para>
-   <token>BaseCharset</> defines the encoding of the database server.
-   All character set names are only used for mapping inside of
-   <filename>charset.conf</> so you can freely use typing-friendly
-   names.
-  </para>
-
-  <para>
-   <token>RecodeTable</> records specify translation tables between
-   server and client.  The file name is relative to the
-   <envar>PGDATA</> directory.  The table file format is very
-   simple. There are no keywords and characters are represented by a
-   pair of decimal or hexadecimal (0x prefixed) values on single
-   lines:
-<synopsis>
-<replaceable>char_value</>   <replaceable>translated_char_value</>
-</synopsis>
-  </para>
-
-  <para>
-   <token>HostCharset</> records define the client character set by IP
-   address. You can use a single IP address, an IP mask range starting
-   from the given address or an IP interval (e.g., 127.0.0.1,
-   192.168.1.100/24, 192.168.1.20-192.168.1.40).
-  </para>
-
-  <para>
-   The <filename>charset.conf</> file is always processed up to the
-   end, so you can easily specify exceptions from the previous
-   rules. In the <filename>src/data/</> directory you will find an
-   example <filename>charset.conf</> and a few recoding tables.
-  </para>
-
-  <para>
-   As this solution is based on the client's IP address and character
-   set mapping there are obviously some restrictions as well. You
-   cannot use different encodings on the same host at the same
-   time. It is also inconvenient when you boot your client hosts into
-   multiple operating systems.  Nevertheless, when these restrictions are
-   not limiting and you do not need multibyte characters then it is a
-   simple and effective solution.
-  </para>
- </sect1>
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
deleted file mode 100644
index b6f49b95848..00000000000
--- a/doc/src/sgml/client-auth.sgml
+++ /dev/null
@@ -1,796 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.35 2002/04/09 00:38:24 momjian Exp $
--->
-
-<chapter id="client-authentication">
- <title>Client Authentication</title>
-
- <indexterm zone="client-authentication">
-  <primary>client authentication</primary>
- </indexterm>
-
- <para>
-  When a client application connects to the database server, it
-  specifies which <productname>PostgreSQL</productname> user name it
-  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 -- see
-  <xref linkend="user-manag"> for more information. Therefore, it is
-  essential to restrict which database users can connect.
- </para>
-
- <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
-  user name that was requested.
- </para>
-
- <para>
-  <productname>PostgreSQL</productname> offers a number of different
-  client authentication methods. The method to be used can be selected
-  on the basis of (client) host, database, and user.
- </para>
-
- <para>
-  <productname>PostgreSQL</productname> user names are logically
-  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 may have many users who have no local
-  account, and in such cases there need be no connection between
-  database user names and OS user names.
- </para>
-
- <sect1 id="pg-hba-conf">
-  <title>The <filename>pg_hba.conf</filename> file</title>
-
-  <indexterm zone="pg-hba-conf">
-   <primary>pg_hba.conf</primary>
-  </indexterm>
-
-  <para>
-   Client authentication is controlled by the file
-   <filename>pg_hba.conf</filename> in the data directory, e.g.,
-   <filename>/usr/local/pgsql/data/pg_hba.conf</filename>.
-   (<acronym>HBA</> stands for host-based authentication.) A default
-   <filename>pg_hba.conf</filename> file is installed when the data area
-   is initialized by <command>initdb</command>.
-  </para>
-
-  <para>
-   The general format of the <filename>pg_hba.conf</filename> file is of
-   a set of records, one per line. Blank lines are ignored, as is any
-   text after the <quote>#</quote> comment character. 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. Records
-   cannot be continued across lines.
-  </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 may have one of the three formats
-   <synopsis>
-local   <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>authentication-method</replaceable> [ <replaceable>authentication-option</replaceable> ]
-host    <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable> <replaceable>IP-mask</replaceable> <replaceable>authentication-method</replaceable>
-hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <replaceable>IP-address</replaceable> <replaceable>IP-mask</replaceable> <replaceable>authentication-method</replaceable>
-    </synopsis>
-   The meaning of the fields is as follows:
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>local</literal></term>
-     <listitem>
-      <para>
-       This record applies to connection attempts using Unix domain
-       sockets.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>host</literal></term>
-     <listitem>
-      <para>
-       This record applied to connection attempts using TCP/IP networks.
-       Note that TCP/IP connections are disabled unless the server is
-       started with the <option>-i</option> option or the
-       <literal>tcpip_socket</> <filename>postgresql.conf</>
-       configuration parameter is enabled.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>hostssl</literal></term>
-     <listitem>
-      <para>
-       This record applies to connection attempts using SSL over
-       TCP/IP. To make use of this option the server must be
-       built with SSL support enabled. Furthermore, SSL must be
-       enabled with the <option>-l</> option or equivalent configuration
-       setting when the server is started.  (Note: <literal>host</literal>
-       records will match either SSL or non-SSL connection attempts, but
-       <literal>hostssl</literal> records requires SSL connections.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>database</replaceable></term>
-     <listitem>
-      <para>
-       Specifies the database for this record. The value
-       <literal>all</literal> specifies that it applies to all
-       databases, while the value <literal>sameuser</> identifies the
-       database with the same name as the connecting user. The value
-       <literal>samegroup</> identifies a group with the same name as
-       the database name. Only members of this group can connect to the
-       database. Otherwise, this is the name of a specific
-       <productname>PostgreSQL</productname> database. Multiple database
-       names can be supplied by separating them with commas. A file
-       containing database names can be specified by preceding the file
-       name with <literal>@</>. The file must be in the same directory
-       as <filename>pg_hba.conf</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>user</replaceable></term>
-     <listitem>
-      <para>
-       Specifies the user for this record. The value
-       <literal>all</literal> specifies that it applies to all users.
-       Otherwise, this is the name of a specific
-       <productname>PostgreSQL</productname> user. Multiple user names
-       can be supplied by separating them with commas. Group names can
-       be specified by preceding the group name with <literal>+</>. A
-       file containing user names can be specified by preceding the file
-       name with <literal>@</>. The file must be in the same directory
-       as <filename>pg_hba.conf</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>IP address</replaceable></term>
-     <term><replaceable>IP mask</replaceable></term>
-     <listitem>
-      <para>
-       These two fields specify the client machine IP addresses
-       (<literal>host</literal> or <literal>hostssl</literal>) for this
-       record. (Of course IP addresses can be spoofed but this
-       consideration is beyond the scope of
-       <productname>PostgreSQL</productname>.) The precise logic is that
-       <blockquote>
-        <informalfigure>
-         <programlisting>(<replaceable>actual-IP-address</replaceable> xor <replaceable>IP-address-field</replaceable>) and <replaceable>IP-mask-field</replaceable></programlisting>
-        </informalfigure>
-       </blockquote>
-       must be zero for the record to match.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable>authentication method</replaceable></term>
-     <listitem>
-      <para>
-       Specifies the authentication method to use when connecting via
-       this record. The possible choices are summarized here; details
-       are in <xref linkend="auth-methods">.
-
-       <variablelist>
-        <varlistentry>
-         <term><literal>trust</></term>
-         <listitem>
-         <para>
-          The connection is allowed unconditionally. This method allows
-          any user that has login access to the client host to connect as
-          any <productname>PostgreSQL</productname> user whatsoever.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>reject</></term>
-        <listitem>
-         <para>
-          The connection is rejected unconditionally. This is useful for
-          <quote>filtering out</> certain hosts from a group.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>md5</></term>
-        <listitem>
-         <para>
-          Requires the client to supply an MD5 encrypted password for
-          authentication. This is the only method that allows encrypted
-          passwords to be stored in pg_shadow.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>crypt</></term>
-        <listitem>
-         <para>
-          Like <literal>md5</literal> method but uses older crypt
-          encryption, which is needed for pre-7.2 clients.
-          <literal>md5</literal> is preferred for 7.2 and later clients.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>password</></term>
-        <listitem>
-         <para>
-          Same as "md5", but the password is sent in cleartext over the
-          network. This should not be used on untrusted networks.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>krb4</></term>
-        <listitem>
-         <para>
-          Kerberos V4 is used to authenticate the user. This is only
-          available for TCP/IP connections.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>krb5</></term>
-        <listitem>
-         <para>
-          Kerberos V5 is used to authenticate the user. This is only
-          available for TCP/IP connections.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>ident</></term>
-        <listitem>
-	 <para>
-          For TCP/IP connections, authentication is done by contacting
-          the <firstterm>ident</firstterm> server on the client host.
-          This is only as secure as the client machine. You must specify
-          the map name after the 'ident' keyword. It determines how to
-          map remote user names to PostgreSQL user names. If you use
-          "sameuser", the user names are assumed to be identical. If
-          not, the map name is looked up in the $PGDATA/pg_ident.conf
-          file. The connection is accepted if that file contains an
-          entry for this map name with the ident-supplied user name and
-          the requested PostgreSQL user name.
-         </para>
-         <para>
-          On machines that support unix-domain socket credentials
-          (currently Linux, FreeBSD, NetBSD, and BSD/OS), ident allows
-          reliable authentication of 'local' connections without ident
-          running on the local machine.
-         </para>
-         <para>
-	  On systems without <symbol>SO_PEERCRED</> requests, ident
-	  authentication is only available for TCP/IP connections. As a
-	  work around, it is possible to specify the <systemitem
-	  class="systemname">localhost</> address <systemitem
-	  class="systemname">127.0.0.1</> and make connections to this
-	  address.
-	 </para>
-         <para>
-          Following the <literal>ident</> keyword, an <firstterm>ident
-          map</firstterm> name should be supplied which specifies which
-          operating system users equate with which database users. See
-          below for details.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>pam</></term>
-        <listitem>
-         <para>
-          This authentication type operates similarly to
-          <firstterm>password</firstterm> except that it uses PAM
-          (Pluggable Authentication Modules) as the authentication
-          mechanism. The default PAM service name is
-          <literal>postgresql</literal>. You can optionally supply you
-          own service name after the <literal>pam</> keyword in the
-          file. For more information about PAM, please read the <ulink
-          url="http://www.kernel.org/pub/linux/libs/pam/"><productname>L
-          inux-PAM</productname> Page</ulink> and the <ulink
-          url="http://www.sun.com/software/solaris/pam/"><systemitem
-          class="osname">Solaris</> PAM Page</ulink>.
-         </para>
-        </listitem>
-       </varlistentry>
-
-      </variablelist>
-
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </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 connections but require a password for
-   remote TCP 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>
-    <indexterm>
-     <primary>SIGHUP</primary>
-    </indexterm>
-   The <filename>pg_hba.conf</filename> file is read on start-up and when
-   the <application>postmaster</> receives a
-   <systemitem>SIGHUP</systemitem> signal. If you edit the file on an
-   active system, you will need to signal the <application>postmaster</>
-   (using <literal>pg_ctl reload</> or <literal>kill -HUP</>) to make it
-   re-read the file.
-  </para>
-
-  <para>
-   An example of a <filename>pg_hba.conf</filename> file is shown in
-   <xref linkend="example-pg-hba.conf">. See below for details on the
-   different authentication methods.
-
-   <example id="example-pg-hba.conf">
-    <title>An example <filename>pg_hba.conf</filename> file</title>
-<programlisting>
-# TYPE       DATABASE    USER       IP_ADDRESS    MASK               AUTHTYPE
-
-# Allow any user on the local system to connect to any
-# database under any user name, but only via an IP connection:
-
-host         all         all        127.0.0.1     255.255.255.255    trust     
-
-# The same, over Unix-socket connections:
-
-local        all         all                                         trust
-
-# Allow any user from any host with IP address 192.168.93.x to
-# connect to database "template1" as the same user name that ident on that
-# host identifies him as (typically his Unix user name):
-
-host         template1   all        192.168.93.0  255.255.255.0      ident sameuser
-
-# Allow a user from host 192.168.12.10 to connect to database "template1"
-# if the user's password is correctly supplied:
-
-host         template1   all        192.168.12.10 255.255.255.255    md5
-
-# In the absence of preceding "host" lines, these two lines will reject
-# all connection attempts from 192.168.54.1 (since that entry will be
-# matched first), but allow Kerberos V5-validated connections from anywhere
-# else on the Internet. The zero mask means that no bits of the host IP
-# address are considered, so it matches any host:
-
-host         all        all         192.168.54.1   255.255.255.255    reject
-host         all        all         0.0.0.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 <productname>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":
-
-host         all        all         192.168.0.0    255.255.0.0        ident omicron
-
-# If these are the only two lines for local connections, they will allow
-# local users to connect only to their own databases (database named the
-# same as the user name), except for administrators who may connect to
-# all databases.  The file $PGDATA/admins lists the user names who are
-# permitted to connect to all databases.  Passwords are required in all
-# cases.  (If you prefer to use ident authorization, an ident map can
-# serve a parallel purpose to the password list file used here.)
-
-local        sameuser   all                                            md5
-local        all        @admins                                        md5
-</programlisting>
-   </example>
-  </para>
- </sect1>
-
- <sect1 id="auth-methods">
-  <title>Authentication methods</title>
-  <para>
-   The following describes the authentication methods in more detail.
-  </para>
-
-  <sect2 id="auth-trust">
-   <title>Trust authentication</title>
-
-   <para>
-    When <literal>trust</> authentication is specified,
-    <productname>PostgreSQL</productname> assumes that anyone who can
-    connect to the postmaster is authorized to access the database as
-    whatever database user he specifies (including the database superuser).
-    This method should only be used when there is adequate system-level
-    protection on connections to the postmaster port.
-   </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 may be able to use <literal>trust</> even on a multiuser
-    machine, if you restrict access to the postmaster's socket file using
-    file-system permissions.  To do this, set the parameter
-    <varname>unix_socket_permissions</varname> (and possibly
-    <varname>unix_socket_group</varname>) in <filename>postgresql.conf</>,
-    as described in <xref linkend="runtime-config-general">.  Or you could
-    set <varname>unix_socket_directory</varname> to place the socket file
-    in a suitably restricted directory.
-   </para>
-
-   <para>
-    Setting file-system permissions only helps for Unix-socket connections.
-    Local TCP connections are not restricted by it; therefore, if you want
-    to use 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 connections
-    if you trust every user on every machine that is allowed to connect
-    to the postmaster by the <filename>pg_hba.conf</> lines that specify
-    <literal>trust</>.  It is seldom reasonable to use <literal>trust</>
-    for any TCP connections other than those from localhost (127.0.0.1).
-   </para>
-
-  </sect2>
-
-  <sect2 id="auth-password">
-   <title>Password authentication</title>
-
-   <indexterm>
-    <primary>MD5</>
-   </indexterm>
-   <indexterm>
-    <primary>crypt</>
-   </indexterm>
-   <indexterm>
-    <primary>password</primary>
-   </indexterm>
-
-   <para>
-    Password-based authentication methods include <literal>md5</>,
-    <literal>crypt</>, and <literal>password</>. These methods operate
-    similarly except for the way that the password is sent across the
-    connection. If you are at all concerned about password
-    <quote>sniffing</> attacks then <literal>md5</> is preferred, with
-    <literal>crypt</> a second choice if you must support pre-7.2
-    clients. Plain <literal>password</> should especially be avoided for
-    connections over the open Internet (unless you use SSL, SSH, or
-    other communications security wrappers around the connection).
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname> database passwords are
-    separate from operating system user passwords. Ordinarily, the
-    password for each database user is stored in the pg_shadow system
-    catalog table. Passwords can be managed with the query language
-    commands <command>CREATE USER</command> and <command>ALTER
-    USER</command>, e.g., <userinput>CREATE USER foo WITH PASSWORD
-    'secret';</userinput>. By default, that is, if no password has been
-    set up, the stored password is <literal>NULL</literal> and password
-    authentication will always fail for that user.
-   </para>
-
-   <para>
-    To restrict the set of users that are allowed to connect to certain
-    databases, list the users separated by commas, or in a separate
-    file. The file should contain user names separated by commas or one
-    user name per line, and be in the same directory as
-    <filename>pg_hba.conf</>. Mention the (base) name of the file
-    preceded with <literal>@</>in the <literal>USER</> column. The
-    <literal>DATABASE</> column can similarly accept a list of values or
-    a file name. You can also specify group names by preceding the group
-    name with <literal>+</>.
-   </para>
-
-  </sect2>
-
-  <sect2 id="kerberos-auth">
-   <title>Kerberos authentication</title>
-
-   <indexterm zone="kerberos-auth">
-    <primary>Kerberos</primary>
-   </indexterm>
-
-   <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 far beyond the scope
-    of this document; in all generality it can be quite complex (yet
-    powerful). The <ulink
-    url="http://www.nrl.navy.mil/CCS/people/kenh/kerberos-faq.html">Kerb
-    eros <acronym>FAQ</></ulink> or <ulink
-    url="ftp://athena-dist.mit.edu">MIT Project Athena</ulink> can be a
-    good starting point for exploration. Several sources for
-    <productname>Kerberos</> distributions exist.
-   </para>
-
-   <para>
-    In order to use <productname>Kerberos</>, support for it must be
-    enabled at build time. Both Kerberos 4 and 5 are supported
-    (<literal>./configure --with-krb4</> or <literal>./configure
-    --with-krb5</> respectively), although only one version can be
-    supported in any one build.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</> operates like a normal Kerberos service.
-    The name of the service principal is
-    <replaceable>servicename/hostname@realm</>, where
-    <replaceable>servicename</> is <literal>postgres</literal> (unless a
-    different service name was selected at configure time with
-    <literal>./configure --with-krb-srvnam=whatever</>).
-    <replaceable>hostname</> is the fully qualified domain name of the
-    server machine. The service principal's realm is the preferred realm
-    of the server machine.
-   </para>
-
-   <para>
-    Client principals must have their <productname>PostgreSQL</> user
-    name as their first component, for example
-    <replaceable>pgusername/otherstuff@realm</>. At present the realm of
-    the client is not checked by <productname>PostgreSQL</>; so if you
-    have cross-realm authentication enabled, then any principal in any
-    realm that can communicate with yours will be accepted.
-   </para>
-
-   <para>
-    Make sure that your server key file is readable (and preferably only
-    readable) by the <productname>PostgreSQL</productname> server
-    account (see <xref linkend="postgres-user">). The location of the
-    key file is specified with the <varname>krb_server_keyfile</> run
-    time configuration parameter. (See also <xref
-    linkend="runtime-config">.) The default is <filename>/etc/srvtab</>
-    if you are using Kerberos 4 and
-    <filename>FILE:/usr/local/pgsql/etc/krb5.keytab</> (or whichever
-    directory was specified as <varname>sysconfdir</> at build time)
-    with Kerberos 5.
-   </para>
-
-   <para>
-    To generate the keytab file, use for example (with version 5)
-<screen>
-<prompt>kadmin% </><userinput>ank -randkey postgres/server.my.domain.org</>
-<prompt>kadmin% </><userinput>ktadd -k krb5.keytab postgres/server.my.domain.org</>
-</screen>
-    Read the <productname>Kerberos</> documentation for details.
-   </para>
-
-   <para>
-    When connecting to the database make sure you have a ticket for a
-    principal matching the requested database user name. An example: For
-    database user name <literal>fred</>, both principal
-    <literal>fred@EXAMPLE.COM</> and
-    <literal>fred/users.example.com@EXAMPLE.COM</> can be used to
-    authenticate to the database server.
-   </para>
-
-   <para>
-    If you use <application>mod_auth_krb</application> 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, no extra passwords required.
-   </para>
-
-  </sect2>
-
-  <sect2>
-   <title>Ident-based authentication</title>
-
-   <indexterm>
-    <primary>ident</primary>
-   </indexterm>
-
-   <para>
-    The <quote>Identification Protocol</quote> is described in
-    <citetitle>RFC 1413</citetitle>. 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>.
-    Since <productname>PostgreSQL</> knows both <replaceable>X</> and
-    <replaceable>Y</> when a physical connection is established, it
-    can interrogate the ident server on the host of the connecting
-    client and could theoretically determine the operating system user
-    for any given connection this way.
-   </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>
-    On systems supporting <symbol>SO_PEERCRED</symbol> requests for
-    Unix-domain sockets, ident authentication can also be applied to
-    local connections. In this case, no security risk is added by using
-    ident authentication; indeed it is a preferable choice for local
-    connections on such systems.
-   </para>
-
-   <para>
-    When using ident-based authentication, after having determined the
-    name of the operating system user that initiated the connection,
-    <productname>PostgreSQL</productname> checks whether that user is
-    allowed to connect as the database user he is requesting to connect
-    as. This is controlled by the ident map argument that follows the
-    <literal>ident</> keyword in the <filename>pg_hba.conf</filename>
-    file. There is a predefined ident map <literal>sameuser</literal>,
-    which allows any operating system user to connect as the database
-    user of the same name (if the latter exists). Other maps must be
-    created manually.
-   </para>
-
-   <para>
-    <indexterm><primary>pg_ident.conf</primary></indexterm> Ident maps
-    other than <literal>sameuser</literal> are defined in the file
-    <filename>pg_ident.conf</filename> in the data directory, which
-    contains lines of the general form:
-<synopsis>
-<replaceable>map-name</> <replaceable>ident-username</> <replaceable>database-username</>
-</synopsis>
-    Comments and whitespace are handled in the usual way. 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 which operating system user is allowed to connect
-    as which database user. The same <replaceable>map-name</> can be
-    used repeatedly to specify more user-mappings within a single map.
-    There is no restriction regarding how many database users a given
-    operating system user may correspond to and vice versa.
-   </para>
-
-  <para>
-    <indexterm>
-     <primary>SIGHUP</primary>
-    </indexterm>
-   The <filename>pg_ident.conf</filename> file is read on start-up and
-   when the <application>postmaster</> receives a
-   <systemitem>SIGHUP</systemitem> signal. If you edit the file on an
-   active system, you will need to signal the <application>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 setup, anyone
-    logged in to a machine on the 192.168 network that does not have the
-    Unix user name <systemitem>bryanh</>, <systemitem>ann</>, or
-    <systemitem>robert</> would not be granted access. Unix user
-    <systemitem>robert</> would only be allowed access when he tries to
-    connect as <productname>PostgreSQL</> user <systemitem>bob</>, not
-    as <systemitem>robert</> or anyone else. <systemitem>ann</> would
-    only be allowed to connect as <systemitem>ann</>. User
-    <systemitem>bryanh</> would be allowed to connect as either
-    <systemitem>bryanh</> himself or as <systemitem>guest1</>.
-   </para>
-
-   <example id="example-pg-ident.conf">
-    <title>An example <filename>pg_ident.conf</> file</title>
-<programlisting>
-#MAP           IDENT-NAME   POSTGRESQL-NAME
-
-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>
-  </sect2>
- </sect1>
-
-  <sect1 id="client-authentication-problems">
-   <title>Authentication problems</title>
-
-   <para>
-    Genuine authentication failures and related problems generally
-    manifest themselves through error messages like the following.
-   </para>
-
-   <para>
-<ProgramListing>
-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 authorizing entry in its <filename>pg_hba.conf</filename>
-    configuration file.
-   </para>
-
-   <para>
-<ProgramListing>
-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 1:  user "andym" does not exist
-</ProgramListing>
-    The indicated user name was not found.
-   </para>
-
-   <para>
-<ProgramListing>
-FATAL 1:  Database "testdb" does not exist in the system catalog.
-</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 may or may not be the right thing.
-   </para>
-
-   <para>
-    Note that the server log may 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 log.
-   </para>
-  </sect1>
-
- </chapter>
diff --git a/doc/src/sgml/compiler.sgml b/doc/src/sgml/compiler.sgml
deleted file mode 100644
index b7c99f6d7a1..00000000000
--- a/doc/src/sgml/compiler.sgml
+++ /dev/null
@@ -1,77 +0,0 @@
-<Chapter Id="compiler">
-<DocInfo>
-<AuthorGroup>
-<Author>
-<FirstName>Brian</FirstName>
-<Surname>Gallew</Surname>
-</Author>
-</AuthorGroup>
-<Date>Transcribed 1998-02-12</Date>
-</DocInfo>
-
-<Title><application>gcc</application> Default Optimizations</Title>
-
-<Para>
-<Note>
-<Para>
-Contributed by Brian Gallew (<email>geek+@cmu.edu</email>)
-</Para>
-</Note>
-</para>
-
-<Para>
-Configuring gcc to use certain flags by default is a simple matter of
-editing the 
-<FileName>/usr/local/lib/gcc-lib/<Replaceable>platform</Replaceable>/<Replaceable>version</Replaceable>/specs</FileName>
-file.
-The format of this file pretty simple.  The file is broken into
-sections, each of which is three lines long.  The first line is
-"*<Replaceable>section_name</Replaceable>:" (e.g. "*asm:").
-The second line is a list of flags,
-and the third line is blank.
-</para>
-
-<Para>
-The easiest change to make is to append
-the desired default flags to the list in the appropriate section.  As
-an example, let's suppose that I have linux running on a '486 with gcc
-2.7.2 installed in the default location.  In the file
-/usr/local/lib/gcc-lib/i486-linux/2.7.2/specs, 13 lines down I find
-the following section:
-<ProgramListing>
-- ----------SECTION----------
-*cc1:
-
-
-- ----------SECTION----------
-</ProgramListing>
-As you can see, there aren't any default flags.  If I always wanted
-compiles of C code to use "-m486 -fomit-frame-pointer", I would
-change it to look like:
-<ProgramListing>
-- ----------SECTION----------
-*cc1:
-- -m486 -fomit-frame-pointer
-
-- ----------SECTION----------
-</ProgramListing>
-If I wanted to be able to generate 386 code for another, older linux
-box lying around, I'd have to make it look like this:
-<ProgramListing>
-- ----------SECTION----------
-*cc1:
-%{!m386:-m486} -fomit-frame-pointer
-
-- ----------SECTION----------
-</ProgramListing>
-This will always omit frame pointers, any will build 486-optimized
-code unless -m386 is specified on the command line.
-</para>
-
-<Para>
-You can actually do quite a lot of customization with the specs file.
-Always remember, however, that these changes are global, and affect
-all users of the system.
-</para>
-
-</Chapter>
diff --git a/doc/src/sgml/contacts.sgml b/doc/src/sgml/contacts.sgml
deleted file mode 100644
index e20698f0011..00000000000
--- a/doc/src/sgml/contacts.sgml
+++ /dev/null
@@ -1,35 +0,0 @@
-<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
-<ulink url="http://www.postgresql.org"><productname>PostgreSQL</productname> web page</ulink>
- for subscription information to the no-cost mailing lists.
-</Para>
-
-<Sect1 id="people">
-<Title>People</Title>
--->
-
-<Para>
-<ItemizedList Mark="bullet" Spacing="compact">
-<ListItem>
-<Para>
-<ULink url="lockhart@fourpalms.org">Thomas Lockhart</ULink>
- works on SQL standards compliance and documentation.
-</Para>
-</ListItem>
-</ItemizedList>
-</Para>
-
-</Appendix>
diff --git a/doc/src/sgml/cvs.sgml b/doc/src/sgml/cvs.sgml
deleted file mode 100644
index 03dacedf28c..00000000000
--- a/doc/src/sgml/cvs.sgml
+++ /dev/null
@@ -1,879 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.23 2002/01/09 00:52:37 petere Exp $
-CVS code repository
-Thomas Lockhart
--->
-
-<appendix id="cvs">
- <docinfo>
-  <authorgroup>
-   <author>
-    <firstname>Marc</firstname>
-    <surname>Fournier</surname>
-   </author>
-   <author>
-    <firstname>Tom</firstname>
-    <surname>Lane</surname>
-   </author>
-   <author>
-    <firstname>Thomas</firstname>
-    <surname>Lockhart</surname>
-   </author>
-  </authorgroup>
-  <date>1999-05-20</date>
- </docinfo>
-
- <title>The <productname>CVS</productname> Repository</title>
-
- <para>
-  The <productname>PostgreSQL</productname> source code is stored and managed using the
-  <productname>CVS</productname> code management system.
- </para>
-
- <para>
-  At least two methods,
-  anonymous CVS and <productname>CVSup</productname>, 
-  are available to pull the <productname>CVS</productname> code tree from the 
-  <productname>PostgreSQL</productname> server to your local machine.
- </para>
-
- <sect1 id="anoncvs">
-  <title>Getting The Source Via Anonymous <productname>CVS</productname></title>
-
-  <para>
-   If you would like to keep up with the current sources on a regular
-   basis, you can fetch them from our <productname>CVS</productname> server 
-   and then use <productname>CVS</productname> to
-   retrieve updates from time to time.
-  </para>
-
-  <procedure>
-   <title>Anonymous CVS</title>
-
-   <step>
-    <para>
-     You will need a local copy of <productname>CVS</productname> 
-     (Concurrent Version Control System), which you can get from
-     <ulink url="http://www.cyclic.com/">http://www.cyclic.com/</ulink> or
-     any GNU software archive site.  
-     We currently recommend version 1.10 (the most recent at the time
-     of writing). Many systems have a recent version of 
-     <application>cvs</application> installed by default.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Do an initial login to the <productname>CVS</productname> server:
-
-     <programlisting>
-$ cvs -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot login
-     </programlisting>
-
-     You will be prompted for a password; just press <literal>ENTER</literal>.
-     You should only need to do this once, since the password will be
-     saved in <literal>.cvspass</literal> in your home directory.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Fetch the <productname>PostgreSQL</productname> sources:
-     <programlisting>
-cvs -z3 -d :pserver:anoncvs@anoncvs.postgresql.org:/projects/cvsroot co -P pgsql
-     </programlisting>
-
-     which installs the <productname>PostgreSQL</productname> sources into a 
-     subdirectory <filename>pgsql</filename>
-     of the directory you are currently in.
-
-     <note>
-      <para>
-       If you have a fast link to the Internet, you may not need
-       <option>-z3</option>, which instructs
-       <productname>CVS</productname> to use gzip compression for transferred data.  But
-       on a modem-speed link, it's a very substantial win.
-      </para>
-     </note>
-    </para>
-
-    <para>
-     This initial checkout is a little slower than simply downloading
-     a <filename>tar.gz</filename> file; expect it to take 40 minutes or so if you
-     have a 28.8K modem.  The advantage of
-     <productname>CVS</productname>
-     doesn't show up until you want to update the file set later on.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Whenever you want to update to the latest <productname>CVS</productname> sources,
-     <command>cd</command> into
-     the <filename>pgsql</filename> subdirectory, and issue
-     <programlisting>
-$ cvs -z3 update -d -P
-     </programlisting>
-
-     This will fetch only the changes since the last time you updated.
-     You can update in just a couple of minutes, typically, even over
-     a modem-speed line.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     You can save yourself some typing by making a file <filename>.cvsrc</filename>
-     in your home directory that contains
-
-     <programlisting>
-cvs -z3
-update -d -P
-     </programlisting>
-
-     This supplies the <option>-z3</option> option to all cvs commands, and the
-     <option>-d</option> and <option>-P</option> options to cvs update.  Then you just have
-     to say
-     <programlisting>
-$ cvs update
-     </programlisting>
-
-     to update your files.
-    </para>
-   </step>
-  </procedure>
-
-  <caution>
-   <para>
-    Some older versions of <productname>CVS</productname> have a bug that
-    causes all checked-out files to be stored world-writable in your
-    directory.  If you see that this has happened, you can do something like
-    <programlisting>
-$ chmod -R go-w pgsql
-    </programlisting>
-    to set the permissions properly.
-    This bug is fixed as of 
-    <productname>CVS</productname> version 1.9.28.
-   </para>
-  </caution>
-
-  <para>
-   <productname>CVS</productname> can do a lot of other things,
-   such as fetching prior revisions
-   of the <productname>PostgreSQL</productname> sources
-   rather than the latest development version.
-   For more info consult the manual that comes with
-   <productname>CVS</productname>, or see the online
-   documentation at
-   <ulink url="http://www.cyclic.com/">http://www.cyclic.com/</ulink>.
-  </para>
- </sect1>
-
- <sect1 id="cvs-tree">
-  <title><productname>CVS</productname> Tree Organization</title>
-
-  <para>
-   <note>
-    <title>Author</title>
-    <para>
-     Written by Marc G. Fournier (<email>scrappy@hub.org</email>) on 1998-11-05
-    </para>
-   </note>
-  </para>
-
-  <para>
-   The command <command>cvs checkout</command> has a flag, <option>-r</option>,
-   that lets you check out a
-   certain revision of a module.  This flag makes it easy to, for example,
-   retrieve the
-   sources that make up release 6_4 of the module `tc' at any time in the
-   future:
-
-   <programlisting>
-$ cvs checkout -r REL6_4 tc
-   </programlisting>
-
-   This is useful, for instance, if someone claims that there is a bug in
-   that release, but you cannot find the bug in the current working copy.
-
-   <tip>
-    <para>
-     You can also check out a module as it was at any given date using the
-     <option>-D</option> option.
-    </para>
-   </tip>
-  </para>
-
-  <para>
-   When you tag more than one file with the same tag you can think
-   about the tag as <quote>a curve drawn through a matrix of filename vs.
-   revision number</quote>.  Say we have 5 files with the following revisions:
-   
-   <programlisting>
-             file1   file2   file3   file4   file5
-     
-             1.1     1.1     1.1     1.1  /--1.1*      <-*-  TAG
-             1.2*-   1.2     1.2    -1.2*-
-             1.3  \- 1.3*-   1.3   / 1.3
-             1.4          \  1.4  /  1.4
-                           \-1.5*-   1.5
-                             1.6
-   </programlisting>
-
-   then the tag <literal>TAG</literal> will reference
-   file1-1.2, file2-1.3, etc.
-
-   <note>
-    <para>
-     For creating a release branch, other then a
-     -b option added to the command, it's the same thing.</para>
-   </note>
-  </para>
-
-  <para>
-   So, to create the 6.4 release
-   I did the following:
-
-   <programlisting>
-$ cd pgsql
-$ cvs tag -b REL6_4
-   </programlisting>
-
-   which will create the tag and the branch for the RELEASE tree.
-  </para>
-
-  <para>
-   For those with <productname>CVS</productname> access, it's simple to
-   create directories for different versions.
-   First, create two subdirectories, RELEASE and CURRENT, so that you don't
-   mix up the two.  Then do:
-
-   <programlisting>
-cd RELEASE
-cvs checkout -P -r REL6_4 pgsql
-cd ../CURRENT
-cvs checkout -P pgsql
-   </programlisting>
-
-   which results in two directory trees, <filename>RELEASE/pgsql</filename> and
-   <filename>CURRENT/pgsql</filename>. From that point on,
-   <productname>CVS</productname>
-   will keep track of which repository branch is in which directory tree, and will
-   allow independent updates of either tree.
-  </para>
-
-  <para>
-   If you are <emphasis>only</emphasis> working on the <literal>CURRENT</literal>
-   source tree, you just do
-   everything as before we started tagging release branches.
-  </para>
-
-  <para>
-   After you've done the initial checkout on a branch
-
-   <programlisting>
-$ cvs checkout -r REL6_4
-   </programlisting>
-
-   anything you do within that directory structure is restricted to that
-   branch.  If you apply a patch to that directory structure and do a
-
-   <programlisting>
-cvs commit
-   </programlisting>
-
-   while inside of it, the patch is applied to the branch and
-   <emphasis>only</emphasis> the branch.
-  </para>
- </sect1>
-
- <sect1 id="cvsup">
-  <title>Getting The Source Via <productname>CVSup</productname></title>
-
-  <para>
-   An alternative to using anonymous CVS for retrieving 
-   the <productname>PostgreSQL</productname> source tree
-   is <productname>CVSup</productname>.
-   <productname>CVSup</productname> was developed by
-   John Polstra (<email>jdp@polstra.com</email>) to
-   distribute CVS repositories and other file trees for
-   <ulink url="http://www.freebsd.org">the FreeBSD project</ulink>.
-  </para>
-
-  <para>
-   A major advantage to using
-   <productname>CVSup</productname> is that it can reliably
-   replicate the <emphasis>entire</emphasis> CVS repository on your local system,
-   allowing fast local access to cvs operations such as <option>log</option>
-   and <option>diff</option>. Other advantages include fast synchronization to
-   the <productname>PostgreSQL</productname> server due to an efficient
-   streaming transfer protocol which only sends the changes since the last update.
-  </para>
-
-  <sect2>
-   <title>Preparing A <productname>CVSup</productname> Client System</title>
-
-   <para>
-    Two directory areas are required for <productname>CVSup</productname>
-    to do it's job: a local <productname>CVS</productname> repository
-    (or simply a directory area if you are fetching a snapshot rather
-    than a repository; see below)
-    and a local <productname>CVSup</productname> bookkeeping
-    area. These can coexist in the same directory tree.
-   </para>
-
-   <para>
-    Decide where you want to keep your local copy of the 
-    <productname>CVS</productname> repository. On one of our systems we
-    recently set up a repository in <filename>/home/cvs/</filename>, 
-    but had formerly kept it under a
-    <productname>PostgreSQL</productname> development tree in
-    <filename>/opt/postgres/cvs/</filename>. If you intend to keep your
-    repository in <filename>/home/cvs/</filename>, then put
-
-    <programlisting>
-setenv CVSROOT /home/cvs
-    </programlisting>
-
-    in your <filename>.cshrc</filename> file, or a similar line in
-    your <filename>.bashrc</filename> or
-    <filename>.profile</filename> file, depending on your shell. 
-   </para>
-
-   <para>
-    The <application>cvs</application> repository area must be initialized.
-    Once <envar>CVSROOT</envar> is set, then this can be done with a
-    single command:
-
-    <programlisting>
-$ cvs init
-    </programlisting>
-
-    after which you should see at least a directory named
-    <filename>CVSROOT</filename> when listing the
-    <envar>CVSROOT</envar> directory:
-
-    <programlisting>
-$ ls $CVSROOT
-CVSROOT/
-    </programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Running a <productname>CVSup</productname> Client</title>
-
-   <para>
-    Verify that
-    <application>cvsup</application> is in your path; on most systems
-    you can do this by typing
-
-    <programlisting>
-which cvsup
-    </programlisting>
-
-    Then, simply run 
-    <application>cvsup</application> using:
-
-    <programlisting>
-$ cvsup -L 2 <replaceable class="parameter">postgres.cvsup</replaceable>
-    </programlisting>
-
-    where <option>-L 2</option> enables some status messages so you
-    can monitor the progress of the update,
-    and <replaceable class="parameter">postgres.cvsup</replaceable> is
-    the path and name you have given to your
-    <productname>CVSup</productname> configuration file.
-   </para>
-
-   <para>
-    Here is a <productname>CVSup</productname> configuration file
-    modified for a specific installation, and which maintains a full
-    local <productname>CVS</productname> repository:
-
-    <programlisting>
-# This file represents the standard CVSup distribution file
-# for the <productname>PostgreSQL</> ORDBMS project
-# Modified by lockhart@fourpalms.org 1997-08-28
-# - Point to my local snapshot source tree
-# - Pull the full CVS repository, not just the latest snapshot
-#
-# Defaults that apply to all the collections
-*default host=cvsup.postgresql.org
-*default compress
-*default release=cvs
-*default delete use-rel-suffix
-# enable the following line to get the latest snapshot
-#*default tag=.
-# enable the following line to get whatever was specified above or by default
-# at the date specified below
-#*default date=97.08.29.00.00.00
-
-# base directory where CVSup will store its 'bookmarks' file(s)
-# will create subdirectory sup/
-#*default base=/opt/postgres # /usr/local/pgsql
-*default base=/home/cvs
-
-# prefix directory where CVSup will store the actual distribution(s)
-*default prefix=/home/cvs
-
-# complete distribution, including all below 
-pgsql
-
-# individual distributions vs 'the whole thing'
-# pgsql-doc
-# pgsql-perl5
-# pgsql-src
-
-   </programlisting>
-   </para>
-
-   <para>
-    The following is a suggested <productname>CVSup</productname> config file from
-    <ulink url="ftp://ftp.postgresql.org/pub/CVSup/README.cvsup">the <productname>PostgreSQL</> ftp site</ulink>
-    which will fetch the current snapshot only:
-
-    <programlisting>
-# This file represents the standard CVSup distribution file
-# for the <productname>PostgreSQL</> ORDBMS project
-#
-# Defaults that apply to all the collections
-*default host=cvsup.postgresql.org
-*default compress
-*default release=cvs
-*default delete use-rel-suffix
-*default tag=.
-
-# base directory where CVSup will store its 'bookmarks' file(s)
-*default base=<replaceable class="parameter">/usr/local/pgsql</replaceable>
-
-# prefix directory where CVSup will store the actual distribution(s)
-*default prefix=<replaceable class="parameter">/usr/local/pgsql</replaceable>
-
-# complete distribution, including all below 
-pgsql
-
-# individual distributions vs 'the whole thing'
-# pgsql-doc
-# pgsql-perl5
-# pgsql-src
-
-    </programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Installing <productname>CVSup</productname></title>
-
-   <para>
-    <productname>CVSup</productname> is available as source, pre-built 
-    binaries, or Linux RPMs. It is far easier to use a binary than to
-    build from source, primarily because the very capable, but
-    voluminous, Modula-3 compiler is required for the build.
-   </para>
-
-   <procedure>
-    <title><productname>CVSup</productname> Installation from Binaries</title>
-
-    <para>
-     You can use pre-built binaries
-     if you have a platform for which binaries
-     are posted on 
-     <ulink url="ftp://ftp.postgresql.org/pub">the <productname>PostgreSQL</productname> ftp site</ulink>,
-     or if you are running FreeBSD, for which
-     <productname>CVSup</productname> is available as a port.
-
-     <note>
-      <para>
-       <productname>CVSup</productname> was originally developed as a
-       tool for distributing the <productname>FreeBSD</productname>
-       source tree. It is available as a <quote>port</quote>, and for those running 
-       FreeBSD, if this is not sufficient to tell how to obtain and
-       install it then please contribute a procedure here.
-      </para>
-     </note>
-    </para>
-
-    <para>
-     At the time of writing, binaries are available for
-     Alpha/Tru64, ix86/xBSD,
-     HPPA/HP-UX 10.20, MIPS/IRIX,
-     ix86/linux-libc5, ix86/linux-glibc,
-     Sparc/Solaris, and Sparc/SunOS.
-    </para>
-
-    <step>
-     <para>
-      Retrieve the binary tar file for
-      <application>cvsup</application>
-      (<application>cvsupd</application> is not required
-      to be a client) appropriate for your platform.
-     </para>
-
-     <substeps>
-      <step performance="optional">
-       <para>
-	If you are running FreeBSD, install the <productname>CVSup</productname> port.
-       </para>
-      </step>
-      
-      <step performance="optional">
-       <para>
-	If you have another platform, check for and download the appropriate binary from
-	<ulink url="ftp://ftp.postgresql.org/pub">the <productname>PostgreSQL</productname> ftp site</ulink>.
-       </para>
-      </step>
-     </substeps>
-    </step>
-
-    <step>
-     <para>
-      Check the tar file to verify the contents and directory
-      structure, if any. For the linux tar file at least, the static binary
-      and man page is included without any directory packaging.
-     </para>
-
-     <substeps>
-      <step>
-       <para>
-	If the binary is in the top level of the tar file, then simply 
-	unpack the tar file into your target directory:
-
-	<programlisting>
-$ cd /usr/local/bin
-$ tar zxvf /usr/local/src/cvsup-16.0-linux-i386.tar.gz
-$ mv cvsup.1 ../doc/man/man1/
-	</programlisting>
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If there is a directory structure in the tar file, then unpack 
-	the tar file within /usr/local/src and move the binaries into
-	the appropriate location as above.
-       </para>
-      </step>
-     </substeps>
-    </step>
-
-    <step>
-     <para>
-      Ensure that the new binaries are in your path.
-
-      <programlisting>
-$ rehash
-$ which cvsup
-$ set path=(<replaceable>path to cvsup</replaceable> $path)
-$ which cvsup
-/usr/local/bin/cvsup
-      </programlisting>
-     </para>
-    </step>
-   </procedure>
-  </sect2>
-
-  <sect2>
-   <title>Installation from Sources</title>
-
-   <para>
-    Installing <productname>CVSup</productname> from sources is not
-    entirely trivial, primarily because most systems will need to
-    install a Modula-3 compiler first.
-    This compiler is available as Linux <productname>RPM</productname>,
-    FreeBSD package, or source code.
-
-    <note>
-     <para>
-      A clean-source installation of Modula-3 takes roughly 200MB of disk space,
-      which shrinks to roughly 50MB of space when the sources are removed.</para>
-    </note>
-   </para>
-
-   <procedure>
-    <title>Linux installation</title>
-
-    <step>
-     <para>
-      Install Modula-3.
-     </para>
-
-     <substeps>
-      <step>
-       <para>
-	Pick up the <productname>Modula-3</productname>
-	distribution from
-	<ulink url="http://m3.polymtl.ca/m3">Polytechnique Montréal</ulink>,
-	who are actively maintaining the code base originally developed by 
-	<ulink
-	 url="http://www.research.digital.com/SRC/modula-3/html/home.html">the DEC Systems Research Center</ulink>.
-       The <productname>PM3</productname> <productname>RPM</productname> distribution is roughly
-	30MB compressed. At the time of writing, the 1.1.10-1 release
-	installed cleanly on RH-5.2, whereas the 1.1.11-1 release is
-	apparently built for another release (RH-6.0?) and does not run on RH-5.2.
-
-	<tip>
-	 <para>
-	  This particular rpm packaging has
-	  <emphasis>many</emphasis> <productname>RPM</productname> files,
-	  so you will likely want to place them into a separate
-	  directory.
-	 </para>
-	</tip>
-       </para>
-      </step>
-
-      <step>
-       <para>
-	Install the Modula-3 rpms:
-
-	<programlisting>
-# rpm -Uvh pm3*.rpm
-	</programlisting>
-       </para>
-      </step>
-     </substeps>
-    </step>
-
-    <step>
-     <para>
-     Unpack the cvsup distribution:
-
-      <programlisting>
-# cd /usr/local/src
-# tar zxf cvsup-16.0.tar.gz
-      </programlisting>
-     </para>
-    </step>
-
-    <step>
-     <para>
-      Build the cvsup distribution, suppressing the GUI interface
-      feature to avoid requiring X11 libraries:
-
-      <programlisting>
-# make M3FLAGS="-DNOGUI"
-      </programlisting>
-
-      and if you want to build a static binary to move to systems
-      that may not have Modula-3 installed, try:
-
-      <programlisting>
-# make M3FLAGS="-DNOGUI -DSTATIC"
-      </programlisting>
-     </para>
-    </step>
-
-    <step>
-     <para>
-      Install the built binary:
-
-      <programlisting>
-# make M3FLAGS="-DNOGUI -DSTATIC" install
-      </programlisting>
-     </para>
-    </step>
-   </procedure>
-  </sect2>
- </sect1>
-</appendix>
-
-<!--
-> It became clear that I had a problem with my m3 installation; some
-> X11 libraries were not being found correctly.
-
-By the way, you can build the client without the GUI by doing this
-in the "client" subdirectory:
-
-    m3build -DNOGUI
-
-If you build it that way, then it doesn't need the X11 libraries and
-it's quite a bit smaller.  The GUI is fun to watch, but it's not
-very useful.  I originally implemented it because it made debugging
-the multi-threaded client program much easier.
-
-To build a statically-linked client, edit <filename>client/src/m3makefile</filename>
-to add <literal>build_standalone()</literal>
- just before the <literal>program()</literal> entry near
-the end of the file:
-
-<programlisting>
-build_standalone()
-program(cvsup)
-</programlisting>
-
-Then, if cvsup has already been built, remove the machine-specific build directory
-(e.g. <filename>LINUXELF/</filename>) and rebuild:
-
-<programlisting>
-rm -rf LINUXELF
-m3build -DNOGUI -v
-cp -p LINUXELF/cvsup /usr/local/bin
-</programlisting>
-
-> Anyway, with the reinstall and the two-line patch above (and that
-> one include-file _POSIX_SOURCE workaround from the previous try),
-> things built cleanly.
-
-Good!
-
-> Now I just need a server somewhere to test.
-
-If you want to try it out, there are public servers for the FreeBSD
-source repository at cvsup.freebsd.org and cvsup2.freebsd.org.
-Here's a suggested supfile:
-
-*default host=cvsup.freebsd.org compress
-*default release=cvs
-*default base=/home/jdp/cvsup-test	# FIX THIS
-*default delete use-rel-suffix
-# *default tag=.
-src-bin
-
-This will fetch you the source repository for the programs that get
-installed into "/bin".  I chose it because it's one of the smaller
-pieces of the system.  Make an empty directory someplace for
-testing, and change the "FIX THIS" line to specify that directory
-after the "base=".
-
-If you are on a T1 or better, you should probably delete the
-"compress" keyword in the first line.
-
-As shown, it will get the repository (RCS) files.  If you uncomment
-the line containing "tag=." then it will instead check out the
-latest version of each file.  There's a bunch more information about
-what you can do in
-<ulink url="http://www.freebsd.org/handbook/cvsup.html">the CVSup Handbook</ulink>.
-
-There is one other thing I want to send you, but not tonight.  I
-discovered the hard way that you need a malloc package that is
-thread-safe with respect to the Modula-3 threads package.  The
-Modula-3 runtime takes care to do the proper mutual exclusion around
-all calls it makes to malloc.  But if you call certain functions in
-the native C library which in turn call malloc, then the mutual
-exclusion gets bypassed.  This can lead to rare but baffling core
-dumps.
-
-For FreeBSD, I solved this by adding a thread-safe malloc package
-into the Modula-3 runtime.  The package is quite portable, and I'm
-sure it will work well for Linux with very few changes (probably
-none at all).  I want to send it to you along with instructions
-for making it a part of the "libm3core" library.  It's very simple,
-but I've run out of steam for tonight. :-)  Once you have this
-malloc in place, the CVSup system should be rock solid.  We have
-servers that have been up for weeks and have served many thousands
-of clients without any observed problems.
-
-> We hope to have the PostgreSQL tree using CVSup within a month or
-> so, and hope to retire sup in September...
-
-Great!  I'll do my best to help make sure you don't regret it.
-
-John
-
-Tom,
-
-I'm appending the sources for the thread safe version of malloc that
-I told you about.  I believe that it will simply compile and work
-under Linux, but I've never had an opportunity to test it there.
-I urge you to put it into your Modula-3 system; otherwise, you
-are guaranteed to get occasional mysterious core dumps from cvsupd.
-
-As a first step, I'd suggest simply trying to compile it under
-Linux, like this:
-
-    cc -O -c malloc.c
-
-You shouldn't get any errors or warnings.  If you do, contact me
-before you waste any more time on it.
-
-Assuming it compiles OK, copy malloc.c into this directory of your
-Modula-3 source tree:
-
-    m3/m3core/src/runtime/LINUXELF
-
-In that same directory, edit "m3makefile" and add this line to the
-end of the file:
-
-    c_source       ("malloc")
-
-Then chdir up into "m3/m3core" of the Modula-3 tree and type
-"m3build".  (I'm assuming you already have a working Modula-3
-installation.)  After that finishes, become root and type "m3ship"
-to install it.
-
-That's all there is to it.  If you built cvsup and cvsupd to use
-shared libraries, you don't even need to re-link them.  They'll pick
-up the change automatically from the updated shared library.
-
-Let me know if you run into any problems with it.
-
-By the way, this is a very good malloc in its own right.  It's worth
-using even aside from the thread safety of it.
-
-Regards,
-John
-
-I've deposited a statically built cvsup client executable (and man pages
-and test configuration) in 
-
-  /pub/incoming/cvsup-15.1-client-linux.tar.gz
-
-This was built and linked on Linux/v2.0.30, RH/v4.2, gnulib/v5.3.12 and
-includes the thread-safe malloc provided by John Polstra. I'll forward
-to you the malloc code and an additional installation e-mail from John.
-
-The Modula-3 installation takes a good bit of room (~50MB?) and the
-build environment is unique to Modula-3, but suprisingly enough it
-pretty much works.
-
-The cvsup Makefiles do not work on my machine (they are not portable
-yet) but each major package (there are 4) can be built without needing
-the makefiles with two commands each. Not difficult at all. John gives
-some hints in his e-mail on how to build a static executable, and on how
-to shrink the size of the executable by leaving out the GUI support.
-Again, easy to do. 
-
-My client test case, picking up a sub-tree of the FreeBSD distribution,
-worked flawlessly. I haven't tried running a server.
-
-Thanks to John for getting me going.
-
-			- Tom
-
-
-For the thread-safe malloc, do the following:
-1) install Modula-3
-2) add the enclosed file "malloc.c" to m3/m3core/src/runtime/LINUXELF
-3) edit the last line of m3makefile in the same directory to add
-     c_source       ("malloc")
-4) do an "m3build" and an m3ship from the appropriate directory.
-
-From what John said, the malloc problem can be noticable for the
-server-side running cvsupd. Clients may not need it.
-
-Unfortunately I seem to have lost John's original good instructions for
-this, so am doing this from memory. May need to ask John to give
-instructions again...
-
-			- Tom
-
--->
-
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
deleted file mode 100644
index b087acdfd7b..00000000000
--- a/doc/src/sgml/datatype.sgml
+++ /dev/null
@@ -1,3113 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.93 2002/06/11 15:32:32 thomas Exp $
--->
-
- <chapter id="datatype">
-  <title id="datatype-title">Data Types</title>
-
-  <indexterm zone="datatype">
-   <primary>data types</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>types</primary>
-   <see>data types</see>
-  </indexterm>
-
-  <para>
-   <productname>PostgreSQL</productname> has a rich set of native data 
-   types available to users.
-   Users may add new types to <productname>PostgreSQL</productname> using the
-   <command>CREATE TYPE</command> command.
-  </para>
-
-  <para>
-   <xref linkend="datatype-table"> shows all general-purpose data types
-   included in the standard distribution.  Most of the alternative names
-   listed in the 
-   <quote>Aliases</quote> column are the names used internally by
-   <productname>PostgreSQL</productname> for historical reasons.  In
-   addition, some internally used or deprecated types are available,
-   but they are not listed here.
-  </para>
-
- <para>
-   <table id="datatype-table">
-    <title>Data Types</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Type 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</type></entry>
-       <entry></entry>
-       <entry>fixed-length bit string</entry>
-      </row>
-
-      <row>
-       <entry><type>bit varying(<replaceable>n</replaceable>)</type></entry>
-       <entry><type>varbit(<replaceable>n</replaceable>)</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 in 2D plane</entry>
-      </row>
-
-      <row>
-       <entry><type>bytea</type></entry>
-       <entry></entry>
-       <entry>binary data</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>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>cidr</type></entry>
-       <entry></entry>
-       <entry>IP network address</entry>
-      </row>
-
-      <row>
-       <entry><type>circle</type></entry>
-       <entry></entry>
-       <entry>circle in 2D 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</entry>
-      </row>
-
-      <row>
-       <entry><type>inet</type></entry>
-       <entry></entry>
-       <entry>IP 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>p</replaceable>)</type></entry>
-       <entry></entry>
-       <entry>general-use time span</entry>
-      </row>
-
-      <row>
-       <entry><type>line</type></entry>
-       <entry></entry>
-       <entry>infinite line in 2D plane</entry>
-      </row>
-
-      <row>
-       <entry><type>lseg</type></entry>
-       <entry></entry>
-       <entry>line segment in 2D plane</entry>
-      </row>
-
-      <row>
-       <entry><type>macaddr</type></entry>
-       <entry></entry>
-       <entry>MAC address</entry>
-      </row>
-
-      <row>
-       <entry><type>money</type></entry>
-       <entry></entry>
-       <entry>US-style currency</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 with selectable precision</entry>
-      </row>
-
-      <row>
-       <entry><type>path</type></entry>
-       <entry></entry>
-       <entry>open and closed geometric path in 2D plane</entry>
-      </row>
-
-      <row>
-       <entry><type>point</type></entry>
-       <entry></entry>
-       <entry>geometric point in 2D plane</entry>
-      </row>
-
-      <row>
-       <entry><type>polygon</type></entry>
-       <entry></entry>
-       <entry>closed geometric path in 2D plane</entry>
-      </row>
-
-      <row>
-       <entry><type>real</type></entry>
-       <entry><type>float4</type></entry>
-       <entry>single precision floating-point number</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</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><type>timestamp</type></entry>
-       <entry>date and time</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>
-     </tbody>
-    </tgroup>
-   </table>
-  </para>
-
-  <note>
-   <title>Compatibility</title>
-   <para>
-    The following types (or spellings thereof) are specified by SQL:
-    <type>bit</type>, <type>bit varying</type>, <type>boolean</type>,
-    <type>char</type>, <type>character</type>, <type>character
-    varying</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>,
-    <type>timestamp</type> (both with or without time zone).
-   </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
-   to <productname>PostgreSQL</productname>, such as open and closed
-   paths, or have several possibilities for formats, such as the date
-   and time types.
-   Most of the input and output functions corresponding to the
-   base types (e.g., integers and floating-point numbers) do some
-   error-checking.
-   Some of the input and output functions are not invertible.  That is,
-   the result of an output function may lose precision when compared to
-   the original input.
-  </para>
-
-  <para>
-   Some of the operators and functions (e.g.,
-   addition and multiplication) do not perform run-time error-checking in the
-   interests of improving execution speed.
-   On some systems, for example, the numeric operators for some data types may
-   silently underflow or overflow.
-  </para>
-
-  <sect1 id="datatype-numeric">
-   <title>Numeric Types</title>
-
-   <indexterm zone="datatype-numeric">
-    <primary>data types</primary>
-    <secondary>numeric</secondary>
-   </indexterm>
-
-   <indexterm zone="datatype-numeric">
-    <primary>integer</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-numeric">
-    <primary>smallint</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-numeric">
-    <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>
-
-   <indexterm zone="datatype-numeric">
-    <primary>numeric (data type)</primary>
-   </indexterm>
-
-   <indexterm>
-    <primary>decimal</primary>
-    <see>numeric</see>
-   </indexterm>
-
-   <indexterm zone="datatype-numeric">
-    <primary>real</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-numeric">
-    <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-numeric">
-    <primary>floating point</primary>
-   </indexterm>
-
-   <para>
-    Numeric types consist of two-, four-, and eight-byte integers,
-    four- and eight-byte
-    floating-point numbers and fixed-precision decimals.
-   </para>
-
-   <para>
-    <table tocentry="1">
-     <title>Numeric Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>Type 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>Fixed-precision</entry>
-	<entry>-32768 to +32767</entry>
-       </row>
-       <row>
-	<entry><type>integer</></entry>
-	<entry>4 bytes</entry>
-	<entry>Usual choice for fixed-precision</entry>
-	<entry>-2147483648 to +2147483647</entry>
-       </row>
-       <row>
-	<entry><type>bigint</></entry>
-	<entry>8 bytes</entry>
-	<entry>Very large range fixed-precision</entry>
-	<entry>-9223372036854775808 to 9223372036854775807</entry>
-       </row>
-
-       <row>
-	<entry><type>decimal</></entry>
-	<entry>variable</entry>
-	<entry>user-specified precision, exact</entry>
-	<entry>no limit</entry>
-       </row>
-       <row>
-	<entry><type>numeric</></entry>
-	<entry>variable</entry>
-	<entry>user-specified precision, exact</entry>
-	<entry>no limit</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>autoincrementing integer</entry>
-	<entry>1 to 9223372036854775807</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-   <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>The Integer Types</title>
-
-    <para>
-     The types <type>smallint</type>, <type>integer</type>,
-     <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 usual 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 <type>integer</type> range is not sufficient,
-     because the latter is definitely faster.
-    </para>
-
-    <para>
-     The <type>bigint</type> type may not function correctly on all
-     platforms, since it relies on compiler support for eight-byte
-     integers.  On a machine without such support, <type>bigint</type>
-     acts the same as <type>integer</type> (but still takes up eight
-     bytes of storage).  However, we are not aware of any reasonable
-     platform where this is actually the case.
-    </para>
-
-    <para>
-     SQL only specifies the integer types <type>integer</type> (or
-     <type>int</type>) and <type>smallint</type>.  The type
-     <type>bigint</type>, and the type names <type>int2</type>,
-     <type>int4</type>, and <type>int8</type> are extensions, which
-     are shared with various other RDBMS products.
-    </para>
-
-    <note>
-     <para>
-      If you have a column of type <type>smallint</type> or
-      <type>bigint</type> with an index, you may encounter problems
-      getting the system to use that index.  For instance, a clause of
-      the form
-<programlisting>
-... WHERE smallint_column = 42
-</programlisting>
-      will not use an index, because the system assigns type
-      <type>integer</type> to the constant 42, and
-      <productname>PostgreSQL</productname> currently
-      cannot use an index when two different data types are involved.  A
-      workaround is to single-quote the constant, thus:
-<programlisting>
-... WHERE smallint_column = '42'
-</programlisting>
-      This will cause the system to delay type resolution and will
-      assign the right type to the constant.
-     </para>
-    </note>
-
-   </sect2>
-
-   <sect2 id="datatype-numeric-decimal">
-    <title>Arbitrary Precision Numbers</title>
-
-    <para>
-     The type <type>numeric</type> can store numbers with up to 1,000
-     digits of precision and perform calculations exactly. It is
-     especially recommended for storing monetary amounts and other
-     quantities where exactness is required. However, the
-     <type>numeric</type> type is very slow compared to the
-     floating-point types described in the next section.
-    </para>
-
-    <para>
-     In what follows we use these terms:  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 precision and the scale of the numeric type 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 SQL standard requires a default scale of 0, i.e., coercion to
-     integer accuracy.  We find this a bit useless.  If you're concerned about
-     portability, always specify the precision and scale explicitly.)
-    </para>
-
-    <para>
-     If the precision or scale of a value is greater than the declared
-     precision or scale of a column, the system will attempt to round
-     the value.  If the value cannot be rounded so as to satisfy the
-     declared limits, an error is raised.
-    </para>
-
-    <para>
-     The types <type>decimal</type> and <type>numeric</type> are
-     equivalent.  Both types are part of the SQL standard.
-    </para>
-   </sect2>
-
-
-   <sect2 id="datatype-float">
-    <title>Floating-Point Types</title>
-
-    <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> 754
-     binary floating point (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 printing back out a value may 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 further 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 may or may
-        not work as expected.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     Normally, 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 normally has a range of around
-     -1E+308 to +1E+308 with a precision of at least 15 digits.  Values that
-     are too large or too small will cause an error.  Rounding may
-     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>
-
-   </sect2>
-
-   <sect2 id="datatype-serial">
-    <title>The 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>sequences</primary>
-     <secondary>and serial type</secondary>
-    </indexterm>
-
-    <para>
-     The <type>serial</type> data types are not truly types, but are a
-     notational convenience for setting up unique identifier columns
-     in tables.
-     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 DEFAULT nextval('<replaceable class="parameter">tablename</replaceable>_<replaceable class="parameter">colname</replaceable>_seq') UNIQUE NOT NULL
-);
-</programlisting>
-
-     Thus, we have created an integer column and arranged for its default
-     values to be assigned from a sequence generator.  UNIQUE and NOT NULL
-     constraints are applied to ensure that explicitly-inserted values
-     will never be duplicates, either.
-    </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 just
-     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>
-     Implicit sequences supporting the <type>serial</type> types are
-     not automatically dropped when a table containing a serial type
-     is dropped. So, the following commands executed in order will likely fail:
-
-<programlisting>
-CREATE TABLE <replaceable class="parameter">tablename</replaceable> (<replaceable class="parameter">colname</replaceable> SERIAL);
-DROP TABLE <replaceable class="parameter">tablename</replaceable>;
-CREATE TABLE <replaceable class="parameter">tablename</replaceable> (<replaceable class="parameter">colname</replaceable> SERIAL);
-</programlisting>
-
-     The sequence will remain in the database until explicitly dropped using
-     <command>DROP SEQUENCE</command>.  (This annoyance will probably be
-     fixed in some future release.)
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="datatype-money">
-   <title>Monetary Type</title>
-
-   <note>
-    <title>Deprecated</title>
-    <para>
-     The <type>money</type> type is deprecated. Use
-     <type>numeric</type> or <type>decimal</type> instead, in
-     combination with the <function>to_char</function> function.  The
-     money type may become a locale-aware layer over the
-     <type>numeric</type> type in a future release.
-    </para>
-   </note>
-
-   <para>
-    The <type>money</type> type stores a currency amount with fixed
-    decimal point representation.  The output format is
-    locale-specific.
-   </para>
-
-   <para>
-    Input is accepted in a variety of formats, including integer and
-    floating-point literals, as well as <quote>typical</quote>
-    currency formatting, such as <literal>'$1,000.00'</literal>.
-    Output is in the latter form.
-   </para>
-
-   <para>
-    <table tocentry="1">
-     <title>Monetary Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>Type Name</entry>
-	<entry>Storage</entry>
-	<entry>Description</entry>
-	<entry>Range</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry>money</entry>
-	<entry>4 bytes</entry>
-	<entry>Fixed-precision</entry>
-	<entry>-21474836.48 to +21474836.47</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-  </sect1>
-
-
-  <sect1 id="datatype-character">
-   <title>Character Types</title>
-
-   <indexterm zone="datatype-character">
-    <primary>character strings</primary>
-    <secondary>data types</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>strings</primary>
-    <see>character strings</see>
-   </indexterm>
-
-   <indexterm>
-    <primary>text</primary>
-    <see>character strings</see>
-   </indexterm>
-
-    <table tocentry="1">
-     <title>Character Types</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-	<entry>Type name</entry>
-	<entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><type>character(<replaceable>n</>)</type>, <type>char(<replaceable>n</>)</type></entry>
-	<entry>Fixed-length blank padded</entry>
-       </row>
-       <row>
-	<entry><type>character varying(<replaceable>n</>)</type>, <type>varchar(<replaceable>n</>)</type></entry>
-	<entry>Variable-length with limit</entry>
-       </row>
-       <row>
-	<entry><type>text</type></entry>
-	<entry>Variable unlimited length</entry>
-       </row>
-     </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    <acronym>SQL</acronym> defines two primary character types:
-    <type>character(<replaceable>n</>)</type> and <type>character
-    varying(<replaceable>n</>)</type>, where <replaceable>n</> is a
-    positive integer.  Both of these types can store strings up to
-    <replaceable>n</> characters 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 SQL 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>
-
-   <note>
-    <para>
-     Prior to <productname>PostgreSQL</> 7.2, strings that were too long were silently
-     truncated, no error was raised.
-    </para>
-   </note>
-
-   <para>
-    The notations <type>char(<replaceable>n</>)</type> and
-    <type>varchar(<replaceable>n</>)</type> are aliases for
-    <type>character(<replaceable>n</>)</type> and <type>character
-    varying(<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 latter is a <productname>PostgreSQL</> extension.
-   </para>
-
-   <para>
-    In addition, <productname>PostgreSQL</productname> supports the
-    more general <type>text</type> type, which stores strings of any
-    length.  Unlike <type>character varying</type>, <type>text</type>
-    does not require an explicit declared upper limit on the size of
-    the string.  Although the type <type>text</type> is not in the SQL
-    standard, many other RDBMS packages have it as well.
-   </para>
-
-   <para>
-    The storage requirement for data of these types is 4 bytes plus
-    the actual string, and in case of <type>character</type> plus the
-    padding.  Long strings will be compressed by the system
-    automatically, so the physical requirement on disk may be less.
-    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 very useful to change
-    this because with multibyte character encodings the number of
-    characters and bytes can be quite different anyway.  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 are no performance differences between these three types,
-     apart from the increased storage size when using the blank-padded
-     type.
-    </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.
-   </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   |           4
-</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>
-SELECT b, char_length(b) FROM test2;
-<computeroutput>
-   b   | char_length
--------+-------------
- ok    |           2
- good  |           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
-    <productname>PostgreSQL</productname>.  The <type>name</type> type
-    exists <emphasis>only</emphasis> for storage of internal catalog
-    names and is not intended for use by the general user.  Its length
-    is currently defined as 32 bytes (31 usable characters plus terminator)
-    but should be referenced using the macro
-    <symbol>NAMEDATALEN</symbol>.  The length is set at compile time
-    (and is therefore adjustable for special uses); the default
-    maximum length may 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 poor-man's
-    enumeration type.
-   </para>
-
-    <table tocentry="1">
-     <title>Specialty Character Type</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-	<entry>Type Name</entry>
-	<entry>Storage</entry>
-	<entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry>"char"</entry>
-	<entry>1 byte</entry>
-	<entry>Single character internal type</entry>
-       </row>
-       <row>
-	<entry>name</entry>
-	<entry>32 bytes</entry>
-	<entry>Thirty-one character internal type</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  </sect1>
-
- <sect1 id="datatype-binary">
-  <title>Binary Strings</title>
-   <para>
-    The <type>bytea</type> data type allows storage of binary strings.
-   </para>
-
-   <table tocentry="1">
-    <title>Binary String Types</title>
-    <tgroup cols="3">
-     <thead>
-      <row>
-       <entry>Type Name</entry>
-       <entry>Storage</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry><type>bytea</type></entry>
-       <entry>4 bytes plus the actual binary string</entry>
-       <entry>Variable (not specifically limited)
-              length binary string</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    A binary string is a sequence of octets that does not have either a
-    character set or collation associated with it.  <type>Bytea</type>
-    specifically allows storing octets of zero value and other
-    <quote>non-printable</quote> octets.
-   </para>
-
-   <para>
-    Octets of certain values <emphasis>must</emphasis> be escaped (but all
-    octet values <emphasis>may</emphasis> be escaped) when used as part of
-    a string literal in an <acronym>SQL</acronym> statement. In general,
-    to escape an octet, it is converted into the three-digit octal number
-    equivalent of its decimal octet value, and preceded by two
-    backslashes. Some octet values have alternate escape sequences, as
-    shown in <xref linkend="datatype-binary-sqlesc">.
-   </para>
-
-   <table id="datatype-binary-sqlesc">
-    <title><acronym>SQL</acronym> Literal Escaped Octets</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Decimal Octet Value</entry>
-       <entry>Description</entry>
-       <entry>Input Escaped Representation</entry>
-       <entry>Example</entry>
-       <entry>Printed Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry> <literal> 0 </literal> </entry>
-       <entry> zero octet </entry>
-       <entry> <literal> '\\000' </literal> </entry>
-       <entry> <literal> select '\\000'::bytea; </literal> </entry>
-       <entry> <literal> \000 </literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal> 39 </literal> </entry>
-       <entry> single quote </entry>
-       <entry> <literal> '\\'' or '\\047' </literal> </entry>
-       <entry> <literal> select '\''::bytea; </literal></entry>
-       <entry> <literal> ' </literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal>92</literal> </entry>
-       <entry> backslash </entry>
-       <entry> <literal> '\\\\' or '\\134' </literal> </entry>
-       <entry> <literal> select '\\\\'::bytea; </literal></entry>
-       <entry> <literal> \\ </literal></entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    Note that the result in each of the examples above was exactly one
-    octet in length, even though the output representation of the zero
-    octet and backslash are more than one character. <type>Bytea</type>
-    output octets are also escaped. In general, each
-    <quote>non-printable</quote> octet decimal value 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) has a special alternate output representation.
-    Details are in <xref linkend="datatype-binary-resesc">.
-   </para>
-
-   <table id="datatype-binary-resesc">
-    <title><acronym>SQL</acronym> Output Escaped Octets</title>
-    <tgroup cols="5">
-     <thead>
-      <row>
-       <entry>Decimal Octet Value</entry>
-       <entry>Description</entry>
-       <entry>Output Escaped Representation</entry>
-       <entry>Example</entry>
-       <entry>Printed Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-
-      <row>
-       <entry> <literal> 92 </literal> </entry>
-       <entry> backslash </entry>
-       <entry> <literal> \\ </literal> </entry>
-       <entry> <literal> select '\\134'::bytea; </literal></entry>
-       <entry> <literal> \\ </literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal> 0 to 31 and 127 to 255 </literal> </entry>
-       <entry> <quote>non-printable</quote> octets </entry>
-       <entry> <literal> \### (octal value) </literal> </entry>
-       <entry> <literal> select '\\001'::bytea; </literal> </entry>
-       <entry> <literal> \001 </literal></entry>
-      </row>
-
-      <row>
-       <entry> <literal> 32 to 126 </literal> </entry>
-       <entry> <quote>printable</quote> octets </entry>
-       <entry> ASCII representation </entry>
-       <entry> <literal>  select '\\176'::bytea; </literal> </entry>
-       <entry> <literal> ~ </literal></entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    <acronym>SQL</acronym> string literals (input strings) must be
-    preceded with two backslashes due to the fact that they must pass
-    through two parsers in the PostgreSQL backend. The first backslash
-    is interpreted as an escape character by the string-literal parser,
-    and therefore is consumed, leaving the octets that follow.
-    The remaining backslash is recognized by the <type>bytea</type> input
-    function as the prefix of a three digit octal value. For example, a string
-    literal passed to the backend as <literal>'\\001'</literal> becomes
-    <literal>'\001'</literal> after passing through the string-literal
-    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.
-   </para>
-
-   <para>
-    For a similar reason, a backslash must be input as
-    <literal>'\\\\'</literal> (or <literal>'\\134'</literal>). The first
-    and third backslashes are interpreted as escape characters by the
-    string-literal parser, and therefore are consumed, leaving two
-    backslashes in the string passed to the <type>bytea</type> input function,
-    which interprets them as representing a single backslash.
-    For example, a string literal passed to the
-    backend as <literal>'\\\\'</literal> becomes <literal>'\\'</literal>
-    after passing through the string-literal parser. The
-    <literal>'\\'</literal> is then sent to the <type>bytea</type> input
-    function, where it is converted to a single octet with a decimal
-    value of 92.
-   </para>
-
-   <para>
-    A single quote is a bit different in that it must be input as
-    <literal>'\''</literal> (or <literal>'\\134'</literal>),
-    <emphasis>not</emphasis> as <literal>'\\''</literal>. This is because,
-    while the literal parser interprets the single quote as a special
-    character, and will consume the single backslash, the
-    <type>bytea</type> input function does <emphasis>not</emphasis>
-    recognize a single quote as a special octet. Therefore a string
-    literal passed to the backend as <literal>'\''</literal> becomes
-    <literal>'''</literal> after passing through the string-literal
-    parser. The <literal>'''</literal> is then sent to the
-    <type>bytea</type> input function, where it is retains its single
-    octet decimal value of 39.
-   </para>
-
-   <para>
-    Depending on the front end to PostgreSQL you use, you may have
-    additional work to do in terms of escaping and unescaping
-    <type>bytea</type> strings. For example, you may also have to escape
-    line feeds and carriage returns if your interface automatically
-    translates these. Or you may have to double up on backslashes if
-    the parser for your language or choice also treats them as an
-    escape character.
-   </para>
-
-    <para>
-     <type>Bytea</type> provides most of the functionality of the binary
-     string type per SQL99 section 4.3. A comparison of SQL99 Binary
-     Strings and PostgreSQL <type>bytea</type> is presented in
-     <xref linkend="datatype-binary-compat-comp">.
-    </para>
-
-    <table id="datatype-binary-compat-comp">
-     <title>Comparison of SQL99 Binary String and PostgreSQL
-     <type>BYTEA</type> types</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>SQL99</entry>
-        <entry><type>BYTEA</type></entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry> Name of data type <type>BINARY LARGE OBJECT</type>
-                or <type>BLOB</type> </entry>
-        <entry> Name of data type <type>BYTEA</type> </entry>
-       </row>
-
-       <row>
-        <entry> Sequence of octets that does not have either a character set
-                or collation associated with it. </entry>
-        <entry> same </entry>
-       </row>
-
-       <row>
-        <entry> Described by a binary data type descriptor containing the
-                name of the data type and the maximum length
-                in octets</entry>
-        <entry> Described by a binary data type descriptor containing the
-                name of the data type with no specific maximum length
-                </entry>
-       </row>
-
-       <row>
-        <entry> All binary strings are mutually comparable in accordance
-                with the rules of comparison predicates.</entry>
-        <entry> same</entry>
-       </row>
-
-       <row>
-        <entry> Binary string values can only be compared for equality.
-                </entry>
-        <entry> Binary string values can be compared for equality, greater
-                than, greater than or equal, less than, less than or equal
-                </entry>
-       </row>
-
-       <row>
-        <entry> Operators operating on and returning binary strings
-                include concatenation, substring, overlay, and trim</entry>
-        <entry> Operators operating on and returning binary strings
-                include concatenation, substring, and trim. The
-                <literal>leading</literal> and <literal>trailing</literal>
-                arguments for trim are not yet implemented.
-                </entry>
-       </row>
-
-       <row>
-        <entry> Other operators involving binary strings
-                include length, position, and the like predicate</entry>
-        <entry> same</entry>
-       </row>
-
-       <row>
-        <entry> A binary string literal is comprised of an even number of
-                hexadecimal digits, in single quotes, preceded by <quote>X</quote>,
-                e.g. <literal>X'1a43fe'</literal></entry>
-        <entry> A binary string literal is comprised of octets
-                escaped according to the rules shown in 
-                <xref linkend="datatype-binary-sqlesc"> </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-  </sect1>
-
-
-  <sect1 id="datatype-datetime">
-   <title>Date/Time Types</title>
-
-   <para>
-    <productname>PostgreSQL</productname> supports the full set of
-    <acronym>SQL</acronym> date and time types.
-   </para>
-
-   <para>
-    <table tocentry="1">
-     <title>Date/Time Types</title>
-     <tgroup cols="6">
-      <thead>
-       <row>
-	<entry>Type</entry>
-        <entry>Description</entry>
-	<entry>Storage</entry>
-        <entry>Earliest</entry>
-        <entry>Latest</entry>
-        <entry>Resolution</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><type>timestamp [ (<replaceable>p</replaceable>) ] without time zone</type></entry>
-        <entry>both date and time</entry>
-        <entry>8 bytes</entry>
-        <entry>4713 BC</entry>
-        <entry>AD 1465001</entry>
-        <entry>1 microsecond / 14 digits</entry>
-       </row>
-       <row>
-        <entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ with time zone ]</type></entry>
-        <entry>both date and time</entry>
-        <entry>8 bytes</entry>
-        <entry>4713 BC</entry>
-        <entry>AD 1465001</entry>
-        <entry>1 microsecond / 14 digits</entry>
-       </row>
-       <row>
-        <entry><type>interval [ (<replaceable>p</replaceable>) ]</type></entry>
-        <entry>for time intervals</entry>
-        <entry>12 bytes</entry>
-        <entry>-178000000 years</entry>
-        <entry>178000000 years</entry>
-        <entry>1 microsecond</entry>
-       </row>
-       <row>
-        <entry><type>date</type></entry>
-        <entry>dates only</entry>
-        <entry>4 bytes</entry>
-        <entry>4713 BC</entry>
-        <entry>32767 AD</entry>
-        <entry>1 day</entry>
-       </row>
-       <row>
-        <entry><type>time [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
-        <entry>times of day only</entry>
-        <entry>8 bytes</entry>
-        <entry>00:00:00.00</entry>
-        <entry>23:59:59.99</entry>
-        <entry>1 microsecond</entry>
-       </row>
-       <row>
-        <entry><type>time [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
-        <entry>times of day only</entry>
-        <entry>12 bytes</entry>
-        <entry>00:00:00.00+12</entry>
-        <entry>23:59:59.99-12</entry>
-        <entry>1 microsecond</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-   <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
-    effective limit of precision is determined by the underlying double
-    precision floating-point number used to store values (in seconds
-    for <type>interval</type> and
-    in seconds since 2000-01-01 for <type>timestamp</type>).  The
-    useful range of <replaceable>p</replaceable> is from 0 to about
-    6 for <type>timestamp</type>, but may be more for <type>interval</type>.
-    The system will accept <replaceable>p</replaceable> ranging from
-    0 to 13.
-   </para>
-
-   <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.
-    <productname>PostgreSQL</productname> uses your operating
-    system's underlying features to provide output time-zone
-    support, and these systems usually contain information for only
-    the time period 1902 through 2038 (corresponding to the full
-    range of conventional Unix system time).
-    <type>timestamp with time zone</type> and <type>time with time
-     zone</type> will use time zone
-    information only within that year range, and assume that times
-    outside that range are in <acronym>UTC</acronym>.
-   </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 new
-    applications and are encouraged to move any old
-    ones over when appropriate. Any or all of these internal types
-    might disappear in a future release.
-   </para>
-
-   <sect2 id="datatype-datetime-input">
-    <title>Date/Time Input</title>
-
-    <para>
-     Date and time input is accepted in almost any reasonable format, including
-     <acronym>ISO 8601</acronym>, <acronym>SQL</acronym>-compatible, 
-     traditional <productname>PostgreSQL</productname>, and others.
-     For some formats, ordering of month and day in date input can be
-     ambiguous and there is support for specifying the expected
-     ordering of these fields.
-     The command
-     <literal>SET DateStyle TO 'US'</literal> 
-     or <literal>SET DateStyle TO 'NonEuropean'</literal>
-     specifies the variant <quote>month before day</quote>, the command
-     <literal>SET DateStyle TO 'European'</literal> sets the variant
-     <quote>day before month</quote>. The <literal>ISO</literal> style
-     is the default but this default can be changed at compile time or at run time.
-    </para>
-
-    <para>
-     <productname>PostgreSQL</productname> is more flexible in
-     handling date/time 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>SQL9x</acronym> requires the following syntax
-<synopsis>
-<replaceable>type</replaceable> [ (<replaceable>p</replaceable>) ] '<replaceable>value</replaceable>'
-</synopsis>
-     where <replaceable>p</replaceable> in the optional precision
-     specification is an integer corresponding to 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.
-    </para>
-
-    <sect3>
-    <title><type>date</type></title>
-
-    <indexterm>
-     <primary>date</primary>
-     <secondary>data type</secondary>
-    </indexterm>
- 
-    <para>
-     The following are some possible inputs for the <type>date</type> type.
-
-     <table tocentry="1">
-      <title>Date Input</title>
-      <tgroup cols="2">
-       <thead>
-	<row>
-	 <entry>Example</entry>
-	 <entry>Description</entry>
-	</row>
-       </thead>
-       <tbody>
-	<row>
-	 <entry>January 8, 1999</entry>
-	 <entry>Unambiguous</entry>
-	</row>
-	<row>
-	 <entry>1999-01-08</entry>
-	 <entry>ISO-8601 format, preferred</entry>
-	</row>
-	<row>
-	 <entry>1/8/1999</entry>
-	 <entry>U.S.; read as August 1 in European mode</entry>
-	</row>
-	<row>
-	 <entry>8/1/1999</entry>
-	 <entry>European; read as August 1 in U.S. mode</entry>
-	</row>
-	<row>
-	 <entry>1/18/1999</entry>
-	 <entry>U.S.; read as January 18 in any mode</entry>
-	</row>
-	<row>
-	 <entry>19990108</entry>
-	 <entry>ISO-8601 year, month, day</entry>
-	</row>
-	<row>
-	 <entry>990108</entry>
-	 <entry>ISO-8601 year, month, day</entry>
-	</row>
-	<row>
-	 <entry>1999.008</entry>
-	 <entry>Year and day of year</entry>
-	</row>
-	<row>
-	 <entry>99008</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 before the Common Era</entry>
-	</row>
-       </tbody>
-      </tgroup>
-     </table>
-    </para>
-    </sect3>
-
-    <sect3>
-     <title><type>time [ ( <replaceable>p</replaceable> ) ] [ without time zone ]</type></title>
-
-     <indexterm>
-      <primary>time</primary>
-      <secondary>data type</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>time without time zone</primary>
-      <secondary>time</secondary>
-     </indexterm>
-
-     <para>
-      Per SQL99, this type can be specified as <type>time</type> or
-      as <type>time without time zone</type>. The optional precision
-      <replaceable>p</replaceable> should be between 0 and 13, and
-      defaults to the precision of the input time literal.
-     </para>
-
-     <para>
-      The following are valid <type>time</type> inputs.
-
-      <table tocentry="1">
-       <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 <= 12</entry>
-	 </row>
-	 <row>
-	  <entry><literal>allballs</literal></entry>
-	  <entry>Same as 00:00:00</entry>
-	 </row>
-	</tbody>
-       </tgroup>
-      </table>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title><type>time [ ( <replaceable>precision</replaceable> ) ] with time zone</type></title>
-
-     <indexterm>
-      <primary>time with time zone</primary>
-      <secondary>data type</secondary>
-     </indexterm>
-     <indexterm>
-      <primary>time</primary>
-      <secondary>data type</secondary>
-     </indexterm>
-
-     <para>
-      This type is defined by SQL92, 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 optional precision
-      <replaceable>p</replaceable> should be between 0 and 13, and
-      defaults to the precision of the input time literal.
-     </para>
-
-     <para>
-      <type>time with time zone</type> accepts all input also legal
-      for the <type>time</type> type, appended with a legal time zone,
-      as follows:
-
-      <table tocentry="1">
-       <title>Time With Time Zone Input</title>
-       <tgroup cols="2">
-       <thead>
-	<row>
-	 <entry>Example</entry>
-	 <entry>Description</entry>
-	</row>
-       </thead>
-       <tbody>
-	<row>
-	 <entry>04:05:06.789-8</entry>
-	 <entry>ISO 8601</entry>
-	</row>
-	<row>
-	 <entry>04:05:06-08:00</entry>
-	 <entry>ISO 8601</entry>
-	</row>
-	<row>
-	 <entry>04:05-08:00</entry>
-	 <entry>ISO 8601</entry>
-	</row>
-	<row>
-	 <entry>040506-08</entry>
-	 <entry>ISO 8601</entry>
-	</row>
-       </tbody>
-      </tgroup>
-     </table>
-    </para>
-
-     <para>
-      Refer to <xref linkend="datatype-timezone-table"> for
-      more examples of time zones.
-     </para>
-    </sect3>
-
-    <sect3>
-    <title><type>timestamp [ (<replaceable>precision</replaceable>) ] without time zone</type></title>
-
-    <indexterm>
-     <primary>timestamp without time zone</primary>
-     <secondary>data type</secondary>
-    </indexterm>
-
-     <para>
-      Valid input for the <type>timestamp [ (<replaceable>p</replaceable>) ] without time zone</type>
-      type consists of a concatenation
-      of a date and a time, followed by an optional <literal>AD</literal> or
-      <literal>BC</literal>, followed by an optional time zone. (See below.)
-      Thus
-
-<programlisting>
-1999-01-08 04:05:06
-</programlisting>
-
-      is a valid <type>timestamp without time zone</type> value that
-      is <acronym>ISO</acronym>-compliant.
-      In addition, the wide-spread format
-
-<programlisting>
-January 8 04:05:06 1999 PST
-</programlisting>
-      is supported.
-     </para>
-
-     <para>
-      The optional precision
-      <replaceable>p</replaceable> should be between 0 and 13, and
-      defaults to the precision of the input <type>timestamp</type> literal.
-     </para>
-
-     <para>
-      For <type>timestamp without time zone</type>, any explicit time
-      zone specified in the input is silently swallowed. That is, the
-      resulting date/time value is derived from the explicit date/time
-      fields in the input value, and is not adjusted for time zone.
-     </para>
-    </sect3>
-
-    <sect3>
-    <title><type>timestamp [ (<replaceable>precision</replaceable>) ] with time zone</type></title>
-
-    <indexterm>
-     <primary>timestamp</primary>
-     <secondary>data type</secondary>
-    </indexterm>
-
-     <para>
-      Valid input for the <type>timestamp</type> type consists of a concatenation
-      of a date and a time, followed by an optional <literal>AD</literal> or
-      <literal>BC</literal>, followed by an optional time zone. (See below.)
-      Thus
-
-<programlisting>
-1999-01-08 04:05:06 -8:00
-</programlisting>
-
-      is a valid <type>timestamp</type> value that is <acronym>ISO</acronym>-compliant.
-      In addition, the wide-spread format
-
-<programlisting>
-January 8 04:05:06 1999 PST
-</programlisting>
-      is supported.
-     </para>
-
-     <para>
-      The optional precision
-      <replaceable>p</replaceable> should be between 0 and 13, and
-      defaults to the precision of the input <type>timestamp</type> literal.
-     </para>
-
-     <para>
-      <table tocentry="1" id="datatype-timezone-table">
-       <title>Time Zone Input</title>
-       <tgroup cols="2">
-	<thead>
-	 <row>
-	  <entry>Time Zone</entry>
-	  <entry>Description</entry>
-	 </row>
-	</thead>
-	<tbody>
-	 <row>
-	  <entry>PST</entry>
-	  <entry>Pacific Standard Time</entry>
-	 </row>
-	 <row>
-	  <entry>-8:00</entry>
-	  <entry>ISO-8601 offset for PST</entry>
-	 </row>
-	 <row>
-	  <entry>-800</entry>
-	  <entry>ISO-8601 offset for PST</entry>
-	 </row>
-	 <row>
-	  <entry>-8</entry>
-	  <entry>ISO-8601 offset for PST</entry>
-	 </row>
-	</tbody>
-       </tgroup>
-      </table>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title><type>interval [ ( <replaceable>precision</replaceable> ) ]</type></title>
-
-     <indexterm>
-      <primary>interval</primary>
-     </indexterm>
-
-      <para>
-       <type>interval</type> values can be written with the following syntax:
-
-<programlisting>
-  Quantity Unit [Quantity Unit...] [Direction]
-@ Quantity Unit [Quantity Unit...] [Direction]
-</programlisting>
-
-      where: <literal>Quantity</literal> is a number (possibly signed),
-      <literal>Unit</literal> is <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;
-      <literal>Direction</literal> can be <literal>ago</literal> or
-      empty.  The at sign (<literal>@</>) is optional noise.  The amounts
-      of different units are implicitly added up with appropriate
-      sign accounting.
-     </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'</>.
-     </para>
-
-     <para>
-      The optional precision
-      <replaceable>p</replaceable> should be between 0 and 13, and
-      defaults to the precision of the input literal.
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Special values</title>
-
-     <indexterm>
-      <primary>time</primary>
-      <secondary>constants</secondary>
-     </indexterm>
-
-     <indexterm>
-      <primary>date</primary>
-      <secondary>constants</secondary>
-     </indexterm>
-
-     <para>
-      The following <acronym>SQL</acronym>-compatible functions can be
-      used as date or time
-      input for the corresponding data type: <literal>CURRENT_DATE</literal>,
-      <literal>CURRENT_TIME</literal>,
-      <literal>CURRENT_TIMESTAMP</literal>. The latter two accept an
-      optional precision specification.
-     </para>
-
-     <para>
-      <productname>PostgreSQL</productname> also supports several
-      special constants for convenience.
-
-      <table tocentry="1">
-       <title>Special Date/Time Constants</title>
-       <tgroup cols="2">
-	<thead>
-	 <row>
-	  <entry>Constant</entry>
-	  <entry>Description</entry>
-	 </row>
-	</thead>
-	<tbody>
-	 <row>
-	  <entry><literal>epoch</literal></entry>
-	  <entry>1970-01-01 00:00:00+00 (Unix system time zero)</entry>
-	 </row>
-	 <row>
-	  <entry><literal>infinity</literal></entry>
-	  <entry>Later than other valid times</entry>
-	 </row>
-	 <row>
-	  <entry><literal>-infinity</literal></entry>
-	  <entry>Earlier than other valid times</entry>
-	 </row>
-	 <row>
-	  <entry><literal>invalid</literal></entry>
-	  <entry>Illegal entry</entry>
-	 </row>
-	 <row>
-	  <entry><literal>now</literal></entry>
-	  <entry>Current transaction time</entry>
-	 </row>
-	 <row>
-	  <entry><literal>today</literal></entry>
-	  <entry>Midnight today</entry>
-	 </row>
-	 <row>
-	  <entry><literal>tomorrow</literal></entry>
-	  <entry>Midnight tomorrow</entry>
-	 </row>
-	 <row>
-	  <entry><literal>yesterday</literal></entry>
-	  <entry>Midnight yesterday</entry>
-	 </row>
-	 <row>
-	  <entry><literal>zulu</>, <literal>allballs</>, <literal>z</></entry>
-	  <entry>00:00:00.00 GMT</entry>
-	 </row>
-	</tbody>
-       </tgroup>
-      </table>
-
-      <literal>'now'</literal> is
-      evaluated when the value is first interpreted.
-     </para>
-
-      <note>
-       <para>
-	As of <productname>PostgreSQL</> version 7.2,
-	<literal>'current'</literal> is no longer supported as a
-	date/time constant.
-	Previously,
-	<literal>'current'</literal> was stored as a special value,
-	and evaluated to <literal>'now'</literal> only when
-	used in an expression or type
-	conversion.
-       </para>
-      </note>
-    </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>
-
-    <para>
-     Output formats can be set to one of the four styles
-     ISO 8601, <acronym>SQL</acronym> (Ingres), traditional
-     PostgreSQL, and German, using the <command>SET DateStyle</command>.
-     The default is the <acronym>ISO</acronym> format.
-
-     <table tocentry="1">
-      <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 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>'PostgreSQL'</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>
-
-    <para>
-     The output of the <type>date</type> and <type>time</type> styles
-     is of course 
-     only the date or time part in accordance with the above examples.
-    </para>
-
-    <para>
-     The <acronym>SQL</acronym> style has European and non-European
-     (U.S.) variants, 
-     which determines whether month follows day or vice versa. (See
-     also <xref linkend="datatype-datetime-input">
-     for how this setting affects interpretation of
-     input values.) 
-
-     <table tocentry="1">
-      <title>Date-Order Conventions</title>
-      <tgroup cols="3">
-       <thead>
-	<row>
-	 <entry>Style Specification</entry>
-	 <entry>Description</entry>
-	 <entry>Example</entry>
-	</row>
-       </thead>
-       <tbody>
-	<row>
-	 <entry>European</entry>
-	 <entry><replaceable>day</replaceable>/<replaceable>month</replaceable>/<replaceable>year</replaceable></entry>
-	 <entry>17/12/1997 15:37:16.00 MET</entry>
-	</row>
-	<row>
-	 <entry>US</entry>
-	 <entry><replaceable>month</replaceable>/<replaceable>day</replaceable>/<replaceable>year</replaceable></entry>
-	 <entry>12/17/1997 07:37:16.00 PST</entry>
-	</row>
-       </tbody>
-      </tgroup>
-     </table>
-    </para>
-
-    <para>
-    <type>interval</type> output looks like the input format, except that units like
-    <literal>week</literal> or <literal>century</literal> are converted to years and days.
-    In ISO mode the output looks like
-
-<programlisting>
-[ Quantity Units [ ... ] ] [ Days ] Hours:Minutes [ ago ]
-</programlisting>
-    </para>
-
-    <para>
-     There are several ways to affect the appearance of date/time types:
-
-     <itemizedlist spacing="compact" mark="bullet">
-      <listitem>
-       <para>
-	The <envar>PGDATESTYLE</envar> environment variable used by the backend directly 
-	on postmaster start-up.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	The <envar>PGDATESTYLE</envar> environment variable used by the frontend <application>libpq</application>
-	on session start-up.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<command>SET DATESTYLE</command> <acronym>SQL</acronym> command.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-   </sect2>
-
-   <sect2 id="datatype-timezones">
-    <title>Time Zones</title>
-
-    <indexterm zone="datatype-timezones">
-     <primary>time zones</primary>
-    </indexterm>
-
-    <para>
-     <productname>PostgreSQL</productname> endeavors to be compatible with
-     <acronym>SQL92</acronym> definitions for typical usage.
-     However, the <acronym>SQL92</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 
-	does not have an associated time zone, the
-	<type>time</type> type can.
-	Time zones in the real world can have no meaning unless 
-	associated with a date as well as a time
-	since the offset may vary through the year with daylight-saving
-	time boundaries.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-	The default time zone is specified as a constant integer offset 
-	from GMT/UTC. It is not possible 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
-     recommend <emphasis>not</emphasis> using the SQL92 type <type>time
-     with time zone</type> (though it is supported by
-     <productname>PostgreSQL</productname> for legacy applications and
-     for compatibility with other RDBMS implementations).
-     <productname>PostgreSQL</productname> 
-     assumes your local time zone for any type containing only
-     date or time. Further, time zone support is derived from 
-     the underlying operating system
-     time-zone capabilities, and hence can handle daylight-saving time 
-     and other expected behavior.
-    </para>
-
-    <para>
-     <productname>PostgreSQL</productname> obtains time-zone support 
-     from the underlying operating system for dates between 1902 and
-     2038 (near the typical date limits for Unix-style
-     systems). Outside of this range, all dates are assumed to be
-     specified and used in Universal Coordinated Time (UTC).
-    </para>
-
-    <para>
-     All dates and times are stored internally in UTC,
-     traditionally known as Greenwich Mean Time (GMT). 
-     Times are converted to local time on the database server before being
-     sent to the client frontend, hence by default are in the server
-     time zone.
-    </para>
-
-    <para>
-     There are several ways to affect the time-zone behavior:
-
-     <itemizedlist spacing="compact" mark="bullet">
-      <listitem>
-       <para>
-	The <envar>TZ</envar> environment variable is used by the backend directly
-	on postmaster start-up as the default time zone.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	The <envar>PGTZ</envar> environment variable, if set at the client, is used by <application>libpq</application>
-	to send a <command>SET TIME ZONE</command> command to the backend upon
-	connection.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	The <acronym>SQL</acronym> command <command>SET TIME ZONE</command>
-	sets the time zone for the session.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	The <acronym>SQL92</acronym> qualifier on
-<programlisting>
-<replaceable>timestamp</replaceable> AT TIME ZONE '<replaceable>zone</replaceable>'
-</programlisting>
-	where <replaceable>zone</replaceable> can be specified as a
-	text time zone (e.g. <literal>'PST'</literal>) or as an
-	interval (e.g. <literal>INTERVAL '-08:00'</literal>).
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-     <note>
-      <para>
-       If an invalid time zone is specified,
-       the time zone becomes GMT (on most systems anyway).
-      </para>
-     </note>
-
-     <note>
-      <para>
-       If the run-time option <literal>AUSTRALIAN_TIMEZONES</literal> is set 
-       then <literal>CST</literal> and <literal>EST</literal> refer to
-       Australian time zones, not American ones.
-      </para>
-     </note>
-
-   </sect2>
-
-   <sect2 id="datatype-datetime-internals">
-    <title>Internals</title>
-
-    <para>
-     <productname>PostgreSQL</productname> uses Julian dates
-     for all date/time calculations. They have the nice property of correctly
-     predicting/calculating any date more recent than 4713BC
-     to far into the future, using the assumption that the length of the
-     year is 365.2425 days.
-    </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>
-
-   <para>
-    <productname>PostgreSQL</productname> provides the
-    <acronym>SQL99</acronym> type <type>boolean</type>.
-    <type>boolean</type> can have one of only two states:
-    <quote>true</quote> or <quote>false</quote>.  A third state,
-    <quote>unknown</quote>, is represented by the
-    <acronym>SQL</acronym> NULL state.
-   </para>
-
-   <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>'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>'0'</literal></member>
-    </simplelist>
-    Using the key words <literal>TRUE</literal> and
-    <literal>FALSE</literal> is preferred (and
-    <acronym>SQL</acronym>-compliant).
-   </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>
-
-   <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>
-
-   <tip>
-    <para>
-     Values of the <type>boolean</type> type cannot be cast directly
-     to other types (e.g., <literal>CAST
-     (<replaceable>boolval</replaceable> AS integer)</literal> does
-     not work).  This can be accomplished using the
-     <literal>CASE</literal> expression: <literal>CASE WHEN
-     <replaceable>boolval</replaceable> THEN 'value if true' ELSE
-     'value if false' END</literal>.  See also <xref
-     linkend="functions-conditional">.
-    </para>
-   </tip>
-
-   <para>
-    <type>boolean</type> uses 1 byte of storage.
-   </para>
-  </sect1>
-
-  <sect1 id="datatype-geometric">
-   <title>Geometric Types</title>
-
-   <para>
-    Geometric types represent two-dimensional spatial objects. 
-    The most fundamental type,
-    the point, forms the basis for all of the other types.
-   </para>
-
-   <para>
-    <table tocentry="1">
-     <title>Geometric Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>Geometric Type</entry>
-	<entry>Storage</entry>
-	<entry>Representation</entry>
-	<entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><type>point</type></entry>
-	<entry>16 bytes</entry>
-	<entry>(x,y)</entry>
-	<entry>Point in space</entry>
-       </row>
-       <row>
-	<entry><type>line</type></entry>
-	<entry>32 bytes</entry>
-	<entry>((x1,y1),(x2,y2))</entry>
-	<entry>Infinite line</entry>
-       </row>
-       <row>
-	<entry><type>lseg</type></entry>
-	<entry>32 bytes</entry>
-	<entry>((x1,y1),(x2,y2))</entry>
-	<entry>Finite line segment</entry>
-       </row>
-       <row>
-	<entry><type>box</type></entry>
-	<entry>32 bytes</entry>
-	<entry>((x1,y1),(x2,y2))</entry>
-	<entry>Rectangular box</entry>
-       </row>
-       <row>
-	<entry><type>path</type></entry>
-	<entry>4+32n bytes</entry>
-	<entry>((x1,y1),...)</entry>
-	<entry>Closed path (similar to polygon)</entry>
-       </row>
-       <row>
-	<entry><type>path</type></entry>
-	<entry>4+32n bytes</entry>
-	<entry>[(x1,y1),...]</entry>
-	<entry>Open path</entry>
-       </row>
-       <row>
-	<entry><type>polygon</type></entry>
-	<entry>4+32n bytes</entry>
-	<entry>((x1,y1),...)</entry>
-	<entry>Polygon (similar to closed path)</entry>
-       </row>
-       <row>
-	<entry><type>circle</type></entry>
-	<entry>24 bytes</entry>
-	<entry><(x,y),r></entry>
-	<entry>Circle (center and radius)</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-   <para>
-    A rich set of functions and operators is available to perform various geometric
-    operations such as scaling, translation, rotation, and determining 
-    intersections.
-   </para>
-
-   <sect2>
-    <title>Point</title>
-
-    <indexterm>
-     <primary>point</primary>
-    </indexterm>
-
-    <para>
-     Points are the fundamental two-dimensional building block for geometric types.
-    </para>
-
-    <para>
-     <type>point</type> is specified using the following syntax:
-
-     <synopsis>
-( <replaceable>x</replaceable> , <replaceable>y</replaceable> )
-  <replaceable>x</replaceable> , <replaceable>y</replaceable>
-     </synopsis>
-
-     where the arguments are
-
-     <variablelist>
-      <varlistentry>
-       <term><replaceable>x</replaceable></term>
-       <listitem>
-	<para>
-	 The x-axis coordinate as a floating-point number
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable>y</replaceable></term>
-       <listitem>
-	<para>
-	 The y-axis coordinate as a floating-point number
-	</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Line Segment</title>
-
-    <indexterm>
-     <primary>line</primary>
-    </indexterm>
-
-    <para>
-     Line segments (<type>lseg</type>) are represented by pairs of points.
-    </para>
-
-    <para>
-     <type>lseg</type> is specified using the following syntax:
-
-     <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 the arguments are
-
-     <variablelist>
-      <varlistentry>
-       <term>(<replaceable>x1</replaceable>,<replaceable>y1</replaceable>)</term>
-       <term>(<replaceable>x2</replaceable>,<replaceable>y2</replaceable>)</term>
-       <listitem>
-	<para>
-	 The end points of the line segment
-	</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Box</title>
-
-    <indexterm>
-     <primary>box (data type)</primary>
-    </indexterm>
-
-    <para>
-     Boxes are represented by pairs of points that are opposite
-     corners of the box.
-    </para>
-
-    <para>
-     <type>box</type> is specified using the following syntax:
-
-     <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 the arguments are
-
-     <variablelist>
-      <varlistentry>
-       <term>(<replaceable>x1</replaceable>,<replaceable>y1</replaceable>)</term>
-       <term>(<replaceable>x2</replaceable>,<replaceable>y2</replaceable>)</term>
-       <listitem>
-	<para>
-	 Opposite corners of the box
-	</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-
-    <para>
-     Boxes are output using the first syntax.
-     The corners are reordered on input to store
-     the upper right corner, then the lower left corner.
-     Other corners of the box can be entered, but the lower
-     left and upper right corners are determined from the input and stored.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Path</title>
-
-    <indexterm>
-     <primary>path (data type)</primary>
-    </indexterm>
-
-    <para>
-     Paths are represented by connected sets of points. Paths can be
-     <firstterm>open</firstterm>, where
-     the first and last points in the set are not connected, and <firstterm>closed</firstterm>,
-     where the first and last point are connected. Functions
-     <function>popen(p)</function>
-     and
-     <function>pclose(p)</function>
-     are supplied to force a path to be open or closed, and functions
-     <function>isopen(p)</function>
-     and
-     <function>isclosed(p)</function>
-     are supplied to test for either type in a query.
-    </para>
-
-    <para>
-     <type>path</type> is specified using the following syntax:
-
-     <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 arguments are
-
-     <variablelist>
-      <varlistentry>
-       <term>(<replaceable>x</replaceable>,<replaceable>y</replaceable>)</term>
-       <listitem>
-	<para>
-	 End points of the line segments comprising the path.
-	 A leading square bracket ("[") indicates an open path, while
-	 a leading parenthesis ("(") indicates a closed path.
-	</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-
-    <para>
-     Paths are output using the first syntax.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Polygon</title>
-
-    <indexterm>
-     <primary>polygon</primary>
-    </indexterm>
-
-    <para>
-     Polygons are represented by sets of points. Polygons should probably be
-     considered equivalent to closed paths, but are stored differently 
-     and have their own set of support routines.
-    </para>
-
-    <para>
-     <type>polygon</type> is specified using the following syntax:
-
-     <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 arguments are
-
-     <variablelist>
-      <varlistentry>
-       <term>(<replaceable>x</replaceable>,<replaceable>y</replaceable>)</term>
-       <listitem>
-	<para>
-	 End points of the line segments comprising the boundary of the
-	 polygon
-	</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-
-    <para>
-     Polygons are output using the first syntax.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Circle</title>
-
-    <indexterm>
-     <primary>circle</primary>
-    </indexterm>
-
-    <para>
-     Circles are represented by a center point and a radius.
-    </para>
-
-    <para>
-     <type>circle</type> is specified using the following syntax:
-
-     <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 the arguments are
-
-     <variablelist>
-      <varlistentry>
-       <term>(<replaceable>x</replaceable>,<replaceable>y</replaceable>)</term>
-       <listitem>
-	<para>
-	 Center of the circle
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable>r</replaceable></term>
-       <listitem>
-	<para>
-	 Radius of the circle
-	</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-
-    <para>
-     Circles are output using the first syntax.
-    </para>
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="datatype-net-types">
-   <title>Network Address Data Types</title>
-
-   <indexterm zone="datatype-net-types">
-    <primary>network</primary>
-    <secondary>addresses</secondary>
-   </indexterm>
-
-   <para>
-    <productname>PostgreSQL</> offers data types to store IP and MAC
-    addresses.  It is preferable to use these types over plain text
-    types, because these types offer input error checking and several
-    specialized operators and functions.
-
-    <table tocentry="1" id="datatype-net-types-table">
-     <title>Network Address Data Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>Name</entry>
-	<entry>Storage</entry>
-	<entry>Description</entry>
-	<entry>Range</entry>
-       </row>
-      </thead>
-      <tbody>
-
-       <row>
-	<entry><type>cidr</type></entry>
-	<entry>12 bytes</entry>
-	<entry>IP networks</entry>
-	<entry>valid IPv4 networks</entry>
-       </row>
-
-       <row>
-	<entry><type>inet</type></entry>
-	<entry>12 bytes</entry>
-	<entry>IP hosts and networks</entry>
-	<entry>valid IPv4 hosts or networks</entry>
-       </row>
-
-       <row>
-	<entry><type>macaddr</type></entry>
-	<entry>6 bytes</entry>
-	<entry>MAC addresses</entry>
-	<entry>customary formats</entry>
-       </row>
-
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-   <para>
-    IP v6 is not yet supported.
-   </para>
-
-
-   <sect2 id="datatype-inet">
-    <title><type>inet</type></title>
-
-    <indexterm>
-     <primary>inet (data type)</primary>
-    </indexterm>
-
-    <para>
-     The <type>inet</type> type holds an IP host address, and
-     optionally the identity of the subnet it is in, all in one field.
-     The subnet identity is represented by the number of bits in the
-     network part of the address (the <quote>netmask</quote>).  If the
-     netmask is 32, 
-     then the value does not indicate a subnet, only a single host.
-     Note that if you want to accept networks only, 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">x.x.x.x/y</replaceable> where <replaceable
-     class="parameter">x.x.x.x</replaceable> is an IP address and
-     <replaceable class="parameter">y</replaceable> is the number of
-     bits in the netmask.  If the <replaceable
-     class="parameter">/y</replaceable> part is left off, then the
-     netmask is 32, and the value represents just a single host.
-     On display, the <replaceable class="parameter">/y</replaceable>
-     portion is suppressed if the netmask is 32.
-    </para>
-   </sect2>
-
-   <sect2 id="datatype-cidr">
-    <title><type>cidr</></title>
-
-    <indexterm>
-     <primary>cidr</primary>
-    </indexterm>
-
-    <para>
-     The <type>cidr</type> type holds an IP network specification.
-     Input and output formats follow Classless Internet Domain Routing
-     conventions.
-     The format for
-     specifying classless networks is <replaceable
-     class="parameter">x.x.x.x/y</> where <replaceable
-     class="parameter">x.x.x.x</> is the network 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 numbering system, except
-     that it will be at least large enough to include all of the octets
-     written in the input.
-    </para>
-
-    <para>
-     Here are some examples:
-
-     <table tocentry="1">
-      <title><type>cidr</> Type Input Examples</title>
-      <tgroup cols="3">
-       <thead> 
-	<row> 
-	 <entry><type>CIDR</type> Input</entry>
-	 <entry><type>CIDR</type> Displayed</entry>
-	 <entry><function>abbrev</function>(<type>CIDR</type>)</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>
-       </tbody>
-      </tgroup>
-     </table>
-    </para>
-   </sect2>
-
-   <sect2 id="datatype-inet-vs-cidr">
-    <title><type>inet</type> vs <type>cidr</type></title>
-
-    <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.
-
-      <tip>
-        <para>
-	If you do not like the output format for <type>inet</type> or
-	<type>cidr</type> values, try the <function>host</>(),
-	<function>text</>(), and <function>abbrev</>() functions.
-	</para>
-      </tip>
-    </para>
-   </sect2>
-
-   <sect2 id="datatype-macaddr">
-    <title><type>macaddr</></>
-
-    <indexterm>
-     <primary>macaddr (data type)</primary>
-    </indexterm>
-
-    <indexterm>
-     <primary>MAC address</primary>
-     <see>macaddr</see>
-    </indexterm>
-
-    <para>
-     The <type>macaddr</> type stores MAC addresses, i.e., Ethernet
-     card hardware addresses (although MAC addresses are used for
-     other purposes as well).  Input is accepted in various customary
-     formats, including
-
-     <simplelist>
-      <member><literal>'08002b:010203'</></member>
-      <member><literal>'08002b-010203'</></member>
-      <member><literal>'0800.2b01.0203'</></member>
-      <member><literal>'08-00-2b-01-02-03'</></member>
-      <member><literal>'08:00:2b:01:02:03'</></member>
-     </simplelist>
-
-     which 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
-     last of the shown forms.
-    </para>
-
-    <para>
-     The directory <filename class="directory">contrib/mac</filename>
-     in the <productname>PostgreSQL</productname> source distribution
-     contains tools that can be used to map MAC addresses to hardware
-     manufacturer names.
-    </para>
-   </sect2>
-
-  </sect1>
-
-  <sect1 id="datatype-bit">
-   <title>Bit String Types</title>
-
-   <indexterm zone="datatype-bit">
-    <primary>bit strings</primary>
-    <secondary>data type</secondary>
-   </indexterm>
-
-   <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>x</replaceable>)</type> and <type>BIT
-    VARYING(<replaceable>x</replaceable>)</type>; where
-    <replaceable>x</replaceable> is a positive integer.
-   </para>
-
-   <para>
-    <type>BIT</type> type data must match the length
-    <replaceable>x</replaceable> exactly; it is an error to attempt to
-    store shorter or longer bit strings.  <type>BIT VARYING</type> is
-    of variable length up to the maximum length
-    <replaceable>x</replaceable>; longer strings will be rejected.
-    <type>BIT</type> without length is equivalent to
-    <literal>BIT(1)</literal>, <type>BIT VARYING</type> without length
-    specification means unlimited length.
-   </para>
-
-   <note>
-    <para>
-     Prior to <productname>PostgreSQL</> 7.2, <type>BIT</type> type data was
-     zero-padded on the right.  This was changed to comply with the
-     SQL standard.  To implement zero-padded bit strings, a
-     combination of the concatenation operator and the
-     <function>substring</function> function can be used.
-    </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">.
-   </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 does not match type bit(3)
-</computeroutput>
-SELECT SUBSTRING(b FROM 1 FOR 2) FROM test;
-</programlisting>
-   </example>
-
-  </sect1>
-
-  <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>xid</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>cid</primary>
-   </indexterm>
-
-   <indexterm zone="datatype-oid">
-    <primary>tid</primary>
-   </indexterm>
-
-   <para>
-    Object identifiers (OIDs) are used internally by
-    <productname>PostgreSQL</productname> as primary keys for various system
-    tables.  Also, an OID system column is added to user-created tables
-    (unless <literal>WITHOUT OIDS</> is specified at table creation time).
-    Type <type>oid</> represents an object identifier.  There are also
-    several aliases for <type>oid</>: <type>regproc</>, <type>regprocedure</>,
-    <type>regoper</>, <type>regoperator</>, <type>regclass</>,
-    and <type>regtype</>.
-   </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
-    (which is implemented as unsigned 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  <type>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,
-    one may write <literal>'mytable'::regclass</> to get the OID of table
-    <literal>mytable</>, rather than <literal>SELECT oid FROM pg_class WHERE
-    relname = 'mytable'</>.  (In reality, a much more complicated SELECT would
-    be needed to deal with selecting the right OID when there are multiple
-    tables named <literal>mytable</> in different schemas.)
-   </para>
-
-   <para>
-    <table tocentry="1">
-     <title>Object Identifier Types</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>Type name</entry>
-	<entry>References</entry>
-	<entry>Description</entry>
-	<entry>Examples</entry>
-       </row>
-      </thead>
-
-      <tbody>
-
-       <row>
-	<entry><type>oid</></entry>
-	<entry>any</entry>
-	<entry>Numeric object identifier</entry>
-	<entry>564182</entry>
-       </row>
-
-       <row>
-	<entry><type>regproc</></entry>
-	<entry>pg_proc</entry>
-	<entry>Function name</entry>
-	<entry>sum</entry>
-       </row>
-
-       <row>
-	<entry><type>regprocedure</></entry>
-	<entry>pg_proc</entry>
-	<entry>Function with argument types</entry>
-	<entry>sum(int4)</entry>
-       </row>
-
-       <row>
-	<entry><type>regoper</></entry>
-	<entry>pg_operator</entry>
-	<entry>Operator name</entry>
-	<entry>+</entry>
-       </row>
-
-       <row>
-	<entry><type>regoperator</></entry>
-	<entry>pg_operator</entry>
-	<entry>Operator with argument types</entry>
-	<entry>*(integer,integer)  -(NONE,integer)</entry>
-       </row>
-
-       <row>
-	<entry><type>regclass</></entry>
-	<entry>pg_class</entry>
-	<entry>Relation name</entry>
-	<entry>pg_type</entry>
-       </row>
-
-       <row>
-	<entry><type>regtype</></entry>
-	<entry>pg_type</entry>
-	<entry>Type name</entry>
-	<entry>integer</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-   <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</> is more appropriate.  For <type>regoperator</>,
-    unary operators are identified by writing NONE for the unused
-    operand.
-   </para>
-
-   <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 they are unique.
-    Recommended practice when using OIDs for row identification is to create
-    a unique constraint on the OID column of each table for which the OID will
-    be used.  Never assume that OIDs are unique across tables; use the
-    combination of <structfield>tableoid</> and row OID if you need a
-    database-wide identifier.  (Future releases of
-    <productname>PostgreSQL</productname> are likely to use a separate
-    OID counter for each table, so that <structfield>tableoid</>
-    <emphasis>must</> be included to arrive at a globally unique identifier.)
-   </para>
-
-   <para>
-    Another identifier type used by the system is <type>xid</>, or transaction
-    (abbreviated xact) identifier.  This is the datatype of the system columns
-    <structfield>xmin</> and <structfield>xmax</>.
-    Transaction identifiers are 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 the <citetitle>Administrator's Guide</> for details.  However, it is
-    unwise to depend on uniqueness of transaction IDs over the long term
-    (more than one billion transactions).
-   </para>
-
-   <para>
-    A third identifier type used by the system is <type>cid</>, or command
-    identifier.  This is the datatype of the system columns
-    <structfield>cmin</> and <structfield>cmax</>.
-    Command identifiers are also 32-bit quantities.  This creates a hard
-    limit of 2<superscript>32</> (4 billion) SQL commands within a single
-    transaction.
-    In practice this limit is not a problem --- note that the limit is on
-    number of SQL queries, not number of tuples processed.
-   </para>
-
-   <para>
-    A final identifier type used by the system is <type>tid</>, or tuple
-    identifier.  This is the datatype 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 tuple within its table.
-   </para>
-
-  </sect1>
-
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-tabs-mode:nil
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/share/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml
deleted file mode 100644
index 47f857af8b7..00000000000
--- a/doc/src/sgml/datetime.sgml
+++ /dev/null
@@ -1,1122 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.27 2002/03/22 19:20:07 petere Exp $
-Date/time details
--->
-
- <appendix id="datetime-appendix">
-  <title id="datetime-appendix-title">Date/Time Support</title>
-
-  <para>
-   <productname>PostgreSQL</productname> uses an internal heuristic
-   parser for all date/time support. Dates and times are input as
-   strings, and are broken up into distinct fields with a preliminary
-   determination of what kind of information may 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>
-   <title>Date/Time Keywords</title>
-
-   <para>
-    <table tocentry="1">
-     <title>Month Abbreviations</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-	<entry>Month</entry>
-	<entry>Abbreviations</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry>April</entry>
-	<entry>Apr</entry>
-       </row>
-       <row>
-	<entry>August</entry>
-	<entry>Aug</entry>
-       </row>
-       <row>
-	<entry>December</entry>
-	<entry>Dec</entry>
-       </row>
-       <row>
-	<entry>February</entry>
-	<entry>Feb</entry>
-       </row>
-       <row>
-	<entry>January</entry>
-	<entry>Jan</entry>
-       </row>
-       <row>
-	<entry>July</entry>
-	<entry>Jul</entry>
-       </row>
-       <row>
-	<entry>June</entry>
-	<entry>Jun</entry>
-       </row>
-       <row>
-	<entry>March</entry>
-	<entry>Mar</entry>
-       </row>
-       <row>
-	<entry>November</entry>
-	<entry>Nov</entry>
-       </row>
-       <row>
-	<entry>October</entry>
-	<entry>Oct</entry>
-       </row>
-       <row>
-	<entry>September</entry>
-	<entry>Sep, Sept</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    <note>
-     <para>
-      The month <literal>May</literal> has no explicit abbreviation, for obvious reasons.
-     </para>
-    </note>
-   </para>
-
-    <para>
-     <table tocentry="1">
-      <title>Day of the Week Abbreviations</title>
-      <tgroup cols="2">
-       <thead>
-	<row>
-	 <entry>Day</entry>
-	 <entry>Abbreviation</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>
-
-   <para>
-    <table tocentry="1">
-     <title><productname>PostgreSQL</productname> Field Modifiers</title>
-     <titleabbrev>Field Modifiers</titleabbrev>
-     <tgroup cols="2">
-      <thead>
-       <row>
-	<entry>Identifier</entry>
-	<entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><literal>ABSTIME</literal></entry>
-	<entry>Keyword ignored</entry>
-       </row>
-       <row>
-	<entry><literal>AM</literal></entry>
-	<entry>Time is before 12:00</entry>
-       </row>
-       <row>
-	<entry><literal>AT</literal></entry>
-	<entry>Keyword 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>Keyword ignored</entry>
-       </row>
-       <row>
-	<entry><literal>PM</literal></entry>
-	<entry>Time is on or after after 12:00</entry>
-       </row>
-       <row>
-	<entry><literal>T</literal></entry>
-	<entry>Next field is time</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-   <para>
-    The keyword <literal>ABSTIME</literal> is ignored for historical
-    reasons; in very old releases of
-    <productname>PostgreSQL</productname> invalid <type>ABSTIME</type>
-    fields were emitted as <literal>Invalid Abstime</literal>. This is no
-    longer the case however and this keyword will likely be dropped in
-    a future release.
-   </para>
-  </sect1>
-
-  <sect1 id="timezones">
-   <title>Time Zones</title>
-
-   <indexterm zone="timezones">
-    <primary>time zones</primary>
-   </indexterm>
-
-   <para>
-    <productname>PostgreSQL</productname> contains internal tabular
-    information for time zone decoding, since there is no *nix standard
-    system interface to provide access to general, cross-timezone
-    information. The underlying OS <emphasis>is</emphasis> used to
-    provide time zone information for <emphasis>output</emphasis>, however.
-   </para>
-
-   <para>
-    The following table of time zones recognized by
-    <productname>PostgreSQL</productname> is organized by time
-    zone offset from UTC, rather than alphabetically; this is intended
-    to facilitate
-    matching local usage with recognized abbreviations for cases where
-    these might differ.
-
-    <table tocentry="1">
-     <title><productname>PostgreSQL</productname> Recognized Time Zones</title>
-     <titleabbrev>Time Zones</titleabbrev>
-     <tgroup cols="3">
-      <thead>
-       <row>
-	<entry>Time Zone</entry>
-	<entry>Offset from UTC</entry>
-	<entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry>NZDT</entry>
-	<entry>+13:00</entry>
-	<entry>New Zealand Daylight Time</entry>
-       </row>
-       <row>
-	<entry>IDLE</entry>
-	<entry>+12:00</entry>
-	<entry>International Date Line, East</entry>
-       </row>
-       <row>
-	<entry>NZST</entry>
-	<entry>+12:00</entry>
-	<entry>New Zealand Standard Time</entry>
-       </row>
-       <row>
-	<entry>NZT</entry>
-	<entry>+12:00</entry>
-	<entry>New Zealand Time</entry>
-       </row>
-       <row>
-	<entry>AESST</entry>
-	<entry>+11:00</entry>
-	<entry>Australia Eastern Summer Standard Time</entry>
-       </row>
-       <row>
-	<entry>ACSST</entry>
-	<entry>+10:30</entry>
-	<entry>Central Australia Summer Standard Time</entry>
-       </row>
-       <row>
-	<entry>CADT</entry>
-	<entry>+10:30</entry>
-	<entry>Central Australia Daylight Savings Time</entry>
-       </row>
-       <row>
-	<entry>SADT</entry>
-	<entry>+10:30</entry>
-	<entry>South Australian Daylight Time</entry>
-       </row>
-       <row>
-	<entry>AEST</entry>
-	<entry>+10:00</entry>
-	<entry>Australia Eastern Standard Time</entry>
-       </row>
-       <row>
-	<entry>EAST</entry>
-	<entry>+10:00</entry>
-	<entry>East Australian Standard Time</entry>
-       </row>
-       <row>
-	<entry>GST</entry>
-	<entry>+10:00</entry>
-	<entry>Guam Standard Time, USSR Zone 9</entry>
-       </row>
-       <row>
-	<entry>LIGT</entry>
-	<entry>+10:00</entry>
-	<entry>Melbourne, Australia</entry>
-       </row>
-       <row>
-	<entry>SAST</entry>
-	<entry>+09:30</entry>
-	<entry>South Australia Standard Time</entry>
-       </row>
-       <row>
-	<entry>CAST</entry>
-	<entry>+09:30</entry>
-	<entry>Central Australia Standard Time</entry>
-       </row>
-       <row>
-	<entry>AWSST</entry>
-	<entry>+09:00</entry>
-	<entry>Australia Western Summer Standard Time</entry>
-       </row>
-       <row>
-	<entry>JST</entry>
-	<entry>+09:00</entry>
-	<entry>Japan Standard Time,USSR Zone 8</entry>
-       </row>
-       <row>
-	<entry>KST</entry>
-	<entry>+09:00</entry>
-	<entry>Korea Standard Time</entry>
-       </row>
-       <row>
-	<entry>MHT</entry>
-	<entry>+09:00</entry>
-	<entry>Kwajalein Time</entry>
-       </row>
-       <row>
-	<entry>WDT</entry>
-	<entry>+09:00</entry>
-	<entry>West Australian Daylight Time</entry>
-       </row>
-       <row>
-	<entry>MT</entry>
-	<entry>+08:30</entry>
-	<entry>Moluccas Time</entry>
-       </row>
-       <row>
-	<entry>AWST</entry>
-	<entry>+08:00</entry>
-	<entry>Australia Western Standard Time</entry>
-       </row>
-       <row>
-	<entry>CCT</entry>
-	<entry>+08:00</entry>
-	<entry>China Coastal Time</entry>
-       </row>
-       <row>
-	<entry>WADT</entry>
-	<entry>+08:00</entry>
-	<entry>West Australian Daylight Time</entry>
-       </row>
-       <row>
-	<entry>WST</entry>
-	<entry>+08:00</entry>
-	<entry>West Australian Standard Time</entry>
-       </row>
-       <row>
-	<entry>JT</entry>
-	<entry>+07:30</entry>
-	<entry>Java Time</entry>
-       </row>
-       <row>
-	<entry>ALMST</entry>
-	<entry>+07:00</entry>
-	<entry>Almaty Summer Time</entry>
-       </row>
-       <row>
-	<entry>WAST</entry>
-	<entry>+07:00</entry>
-	<entry>West Australian Standard Time</entry>
-       </row>
-       <row>
-	<entry>CXT</entry>
-	<entry>+07:00</entry>
-	<entry>Christmas (Island) Time</entry>
-       </row>
-       <row>
-	<entry>ALMT</entry>
-	<entry>+06:00</entry>
-	<entry>Almaty Time</entry>
-       </row>
-<!--
-       Conflicts with China Coastal Time
-       <row>
-	<entry>CCT</entry>
-	<entry>+06:30</entry>
-	<entry>Cocos Island Time</entry>
-       </row>
--->
-       <row>
-	<entry>MAWT</entry>
-	<entry>+06:00</entry>
-	<entry>Mawson (Antarctica) Time</entry>
-       </row>
-       <row>
-	<entry>IOT</entry>
-	<entry>+05:00</entry>
-	<entry>Indian Chagos Time</entry>
-       </row>
-       <row>
-	<entry>MVT</entry>
-	<entry>+05:00</entry>
-	<entry>Maldives Island Time</entry>
-       </row>
-       <row>
-	<entry>TFT</entry>
-	<entry>+05:00</entry>
-	<entry>Kerguelen Time</entry>
-       </row>
-       <row>
-	<entry>AFT</entry>
-	<entry>+04:30</entry>
-	<entry>Afganistan Time</entry>
-       </row>
-       <row>
-	<entry>EAST</entry>
-	<entry>+04:00</entry>
-	<entry>Antananarivo Savings Time</entry>
-       </row>
-       <row>
-	<entry>MUT</entry>
-	<entry>+04:00</entry>
-	<entry>Mauritius Island Time</entry>
-       </row>
-       <row>
-	<entry>RET</entry>
-	<entry>+04:00</entry>
-	<entry>Reunion Island Time</entry>
-       </row>
-       <row>
-	<entry>SCT</entry>
-	<entry>+04:00</entry>
-	<entry>Mahe Island Time</entry>
-       </row>
-       <row>
-	<entry>IT</entry>
-	<entry>+03:30</entry>
-	<entry>Iran Time</entry>
-       </row>
-       <row>
-	<entry>EAT</entry>
-	<entry>+03:00</entry>
-	<entry>Antananarivo, Comoro Time</entry>
-       </row>
-       <row>
-	<entry>BT</entry>
-	<entry>+03:00</entry>
-	<entry>Baghdad Time</entry>
-       </row>
-       <row>
-	<entry>EETDST</entry>
-	<entry>+03:00</entry>
-	<entry>Eastern Europe Daylight Savings Time</entry>
-       </row>
-       <row>
-	<entry>HMT</entry>
-	<entry>+03:00</entry>
-	<entry>Hellas Mediterranean Time (?)</entry>
-       </row>
-       <row>
-	<entry>BDST</entry>
-	<entry>+02:00</entry>
-	<entry>British Double Standard Time</entry>
-       </row>
-       <row>
-	<entry>CEST</entry>
-	<entry>+02:00</entry>
-	<entry>Central European Savings Time</entry>
-       </row>
-       <row>
-	<entry>CETDST</entry>
-	<entry>+02:00</entry>
-	<entry>Central European Daylight Savings Time</entry>
-       </row>
-       <row>
-	<entry>EET</entry>
-	<entry>+02:00</entry>
-	<entry>Eastern Europe, USSR Zone 1</entry>
-       </row>
-       <row>
-	<entry>FWT</entry>
-	<entry>+02:00</entry>
-	<entry>French Winter Time</entry>
-       </row>
-       <row>
-	<entry>IST</entry>
-	<entry>+02:00</entry>
-	<entry>Israel Standard Time</entry>
-       </row>
-       <row>
-	<entry>MEST</entry>
-	<entry>+02:00</entry>
-	<entry>Middle Europe Summer Time</entry>
-       </row>
-       <row>
-	<entry>METDST</entry>
-	<entry>+02:00</entry>
-	<entry>Middle Europe Daylight Time</entry>
-       </row>
-       <row>
-	<entry>SST</entry>
-	<entry>+02:00</entry>
-	<entry>Swedish Summer Time</entry>
-       </row>
-       <row>
-	<entry>BST</entry>
-	<entry>+01:00</entry>
-	<entry>British Summer Time</entry>
-       </row>
-       <row>
-	<entry>CET</entry>
-	<entry>+01:00</entry>
-	<entry>Central European Time</entry>
-       </row>
-       <row>
-	<entry>DNT</entry>
-	<entry>+01:00</entry>
-	<entry><foreignphrase>Dansk Normal Tid</foreignphrase></entry>
-       </row>
-       <row>
-	<entry>FST</entry>
-	<entry>+01:00</entry>
-	<entry>French Summer Time</entry>
-       </row>
-       <row>
-	<entry>MET</entry>
-	<entry>+01:00</entry>
-	<entry>Middle Europe Time</entry>
-       </row>
-       <row>
-	<entry>MEWT</entry>
-	<entry>+01:00</entry>
-	<entry>Middle Europe Winter Time</entry>
-       </row>
-       <row>
-	<entry>MEZ</entry>
-	<entry>+01:00</entry>
-	<entry>Middle Europe Zone</entry>
-       </row>
-       <row>
-	<entry>NOR</entry>
-	<entry>+01:00</entry>
-	<entry>Norway Standard Time</entry>
-       </row>
-       <row>
-	<entry>SET</entry>
-	<entry>+01:00</entry>
-	<entry>Seychelles Time</entry>
-       </row>
-       <row>
-	<entry>SWT</entry>
-	<entry>+01:00</entry>
-	<entry>Swedish Winter Time</entry>
-       </row>
-       <row>
-	<entry>WETDST</entry>
-	<entry>+01:00</entry>
-	<entry>Western Europe Daylight Savings Time</entry>
-       </row>
-       <row>
-	<entry>GMT</entry>
-	<entry>+00:00</entry>
-	<entry>Greenwich Mean Time</entry>
-       </row>
-       <row>
-	<entry>UT</entry>
-	<entry>+00:00</entry>
-	<entry>Universal Time</entry>
-       </row>
-       <row>
-	<entry>UTC</entry>
-	<entry>+00:00</entry>
-	<entry>Universal Time, Coordinated</entry>
-       </row>
-       <row>
-	<entry>Z</entry>
-	<entry>+00:00</entry>
-	<entry>Same as UTC</entry>
-       </row>
-       <row>
-	<entry>ZULU</entry>
-	<entry>+00:00</entry>
-	<entry>Same as UTC</entry>
-       </row>
-       <row>
-	<entry>WET</entry>
-	<entry>+00:00</entry>
-	<entry>Western Europe</entry>
-       </row>
-       <row>
-	<entry>WAT</entry>
-	<entry>-01:00</entry>
-	<entry>West Africa Time</entry>
-       </row>
-       <row>
-	<entry>NDT</entry>
-	<entry>-02:30</entry>
-	<entry>Newfoundland Daylight Time</entry>
-       </row>
-       <row>
-	<entry>ADT</entry>
-	<entry>-03:00</entry>
-	<entry>Atlantic Daylight Time</entry>
-       </row>
-       <row>
-	<entry>AWT</entry>
-	<entry>-03:00</entry>
-	<entry>(unknown)</entry>
-       </row>
-       <row>
-	<entry>NFT</entry>
-	<entry>-03:30</entry>
-	<entry>Newfoundland Standard Time</entry>
-       </row>
-       <row>
-	<entry>NST</entry>
-	<entry>-03:30</entry>
-	<entry>Newfoundland Standard Time</entry>
-       </row>
-       <row>
-	<entry>AST</entry>
-	<entry>-04:00</entry>
-	<entry>Atlantic Standard Time (Canada)</entry>
-       </row>
-       <row>
-	<entry>ACST</entry>
-	<entry>-04:00</entry>
-	<entry>Atlantic/Porto Acre Summer Time</entry>
-       </row>
-       <row>
-	<entry>ACT</entry>
-	<entry>-05:00</entry>
-	<entry>Atlantic/Porto Acre Standard Time</entry>
-       </row>
-       <row>
-	<entry>EDT</entry>
-	<entry>-04:00</entry>
-	<entry>Eastern Daylight Time</entry>
-       </row>
-       <!--
-      <row>
-      <entry>ZP4</entry>
-      <entry>-04:00</entry>
-      <entry>GMT +4 hours</entry>
-      </row>
-       -->
-       <row>
-	<entry>CDT</entry>
-	<entry>-05:00</entry>
-	<entry>Central Daylight Time</entry>
-       </row>
-       <row>
-	<entry>EST</entry>
-	<entry>-05:00</entry>
-	<entry>Eastern Standard Time</entry>
-       </row>
-       <!--
-      <row>
-      <entry>ZP5</entry>
-      <entry>-05:00</entry>
-      <entry>GMT +5  hours</entry>
-      </row>
-       -->
-       <row>
-	<entry>CST</entry>
-	<entry>-06:00</entry>
-	<entry>Central Standard Time</entry>
-       </row>
-       <row>
-	<entry>MDT</entry>
-	<entry>-06:00</entry>
-	<entry>Mountain Daylight Time</entry>
-       </row>
-       <!--
-      <row>
-      <entry>ZP6</entry>
-      <entry>-06:00</entry>
-      <entry>GMT +6  hours</entry>
-      </row>
-       -->
-       <row>
-	<entry>MST</entry>
-	<entry>-07:00</entry>
-	<entry>Mountain Standard Time</entry>
-       </row>
-       <row>
-	<entry>PDT</entry>
-	<entry>-07:00</entry>
-	<entry>Pacific Daylight Time</entry>
-       </row>
-       <row>
-	<entry>AKDT</entry>
-	<entry>-08:00</entry>
-	<entry>Alaska Daylight Time</entry>
-       </row>
-       <row>
-	<entry>PST</entry>
-	<entry>-08:00</entry>
-	<entry>Pacific Standard Time</entry>
-       </row>
-       <row>
-	<entry>YDT</entry>
-	<entry>-08:00</entry>
-	<entry>Yukon Daylight Time</entry>
-       </row>
-       <row>
-	<entry>AKST</entry>
-	<entry>-09:00</entry>
-	<entry>Alaska Standard Time</entry>
-       </row>
-       <row>
-	<entry>HDT</entry>
-	<entry>-09:00</entry>
-	<entry>Hawaii/Alaska Daylight Time</entry>
-       </row>
-       <row>
-	<entry>YST</entry>
-	<entry>-09:00</entry>
-	<entry>Yukon Standard Time</entry>
-       </row>
-       <row>
-	<entry>AHST</entry>
-	<entry>-10:00</entry>
-	<entry>Alaska-Hawaii Standard Time</entry>
-       </row>
-       <row>
-	<entry>HST</entry>
-	<entry>-10:00</entry>
-	<entry>Hawaii Standard Time</entry>
-       </row>
-       <row>
-	<entry>CAT</entry>
-	<entry>-10:00</entry>
-	<entry>Central Alaska Time</entry>
-       </row>
-       <row>
-	<entry>NT</entry>
-	<entry>-11:00</entry>
-	<entry>Nome Time</entry>
-       </row>
-       <row>
-	<entry>IDLW</entry>
-	<entry>-12:00</entry>
-	<entry>International Date Line, West</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-  <sect2>
-   <title>Australian Time Zones</title>
-
-   <para>
-    Australian time zones and their naming variants
-    account for fully one quarter of all time zones in the 
-    <productname>PostgreSQL</productname> time zone lookup table.
-    There are two naming conflicts with time zones commonly used
-    in the United States, <literal>CST</literal> and <literal>EST</literal>.
-   </para>
-
-   <para>
-    If the run-time option <literal>AUSTRALIAN_TIMEZONES</literal> is set 
-    then <literal>CST</literal>, <literal>EST</literal>, and
-    <literal>SAT</literal> will be
-    interpreted as Australian timezone names.  Without this option,
-    <literal>CST</literal> and <literal>EST</literal> are taken as
-    American timezone names, while <literal>SAT</literal> is interpreted as a
-    noise word indicating <literal>Saturday</literal>.
-
-    <table tocentry="1">
-     <title><productname>PostgreSQL</productname> Australian Time Zones</title>
-     <titleabbrev>Australian Time Zones</titleabbrev>
-     <tgroup cols="3">
-      <thead>
-       <row>
-	<entry>Time Zone</entry>
-	<entry>Offset from UTC</entry>
-	<entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry>ACST</entry>
-	<entry>+09:30</entry>
-	<entry>Central Australia Standard Time</entry>
-       </row>
-       <row>
-	<entry>CST</entry>
-	<entry>+10:30</entry>
-	<entry>Australian Central Standard Time</entry>
-       </row>
-       <row>
-	<entry>EST</entry>
-	<entry>+10:00</entry>
-	<entry>Australian Eastern Standard Time</entry>
-       </row>
-       <row>
-	<entry>SAT</entry>
-	<entry>+09:30</entry>
-	<entry>South Australian Standard Time</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Date/Time Input Interpretation</title>
-
-   <para>
-    The date/time types are all decoded using a common set of routines.
-   </para>
-
-   <procedure>
-    <title>Date/Time Input Interpretation</title>
-
-    <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 (":"), this is a time
-	 string. Include all subsequent digits and colons.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If the numeric token contains a dash ("-"), slash ("/"), or
-	 two or more dots ("."),
-	this is a date string which may have a text month.
-       </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. 141516 for 14:15:16).
-       </para>
-      </step>
-      <step>
-       <para>
-	If the token starts with a plus ("+") or minus ("-"),
-	then it is either a 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 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>
-       <para>
-	Set field values and bit mask for fields.
-	For example, set year, month, day for <literal>today</literal>, 
-	and additionally hour, minute, second for <literal>now</literal>.
-       </para>
-      </step>
-      
-      <step>
-       <para>
-	If not found, do a similar binary-search table lookup to match
-	the token with a time zone.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If not found, throw an error.
-       </para>
-      </step>
-     </substeps>
-    </step>
-    
-    <step>
-     <para>
-      The token is a number or number field.
-     </para>
-
-     <substeps>
-      <step>
-       <para>
-	If there are more than 4 digits, 
-	and if no other date fields have been previously read, then interpret 
-	as a <quote>concatenated date</quote> (e.g. <literal>19990118</literal>). 8
-	and 6 digits are interpreted as year, month, and day, while 7
-	and 5 digits are interpreted as year, day of year, respectively.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If the token is three digits
-	and a year has already been decoded, 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. 
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If four or more digits, then interpret as a year.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If in European date mode, and if the day field has not yet been read,
-	and if the value is less than or equal to 31, then interpret as a day.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If the month field has not yet been read,
-	and if the value is less than or equal to 12, then interpret as a month.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If the day field has not yet been read,
-	and if the value is less than or equal to 31, then interpret as a day.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	If two digits or four or more digits, then interpret as a year.
-       </para>
-      </step>
-
-      <step>
-       <para>
-	Otherwise, throw an error.
-       </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
-      <literal>1BC</literal> 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 4 digits. If the field was less than 70, then add 2000;
-      otherwise, add 1900.
-
-      <tip>
-       <para>
-	Gregorian years 1-99AD may be entered by using 4 digits with leading
-	zeros (e.g. 0099 is 99AD). Previous versions of
-	<productname>PostgreSQL</productname> accepted years with three
-	digits and with single digits, but as of version 7.0 the rules have
-	been tightened up to reduce the possibility of ambiguity.
-       </para>
-      </tip>
-     </para>
-    </step>
-   </procedure>
-  </sect2>
- </sect1>
-
- <sect1 id="units-history">
-  <title>History of Units</title>
-
-  <note>
-   <para>
-    Contributed by José Soares (<email>jose@sferacarta.com</email>)
-   </para>
-  </note>
-
-  <para>
-   The Julian Day was invented by the French scholar
-   Joseph Justus Scaliger (1540-1609)
-   and probably takes its name from the Scaliger's father,
-   the Italian scholar Julius Caesar Scaliger (1484-1558).
-   Astronomers have used the Julian period to assign a unique number to
-   every day since 1 January 4713 BC. This is the so-called Julian Day
-   (JD). JD 0 designates the 24 hours from noon UTC on 1 January 4713 BC
-   to noon UTC on 2 January 4713 BC.
-  </para>
-
-  <para>
-   <quote>Julian Day</quote> is different from <quote>Julian Date</quote>.
-
-   The Julian calendar was introduced by Julius Caesar in 45 BC. It was
-   in common use until the 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.
-   The accumulating calendar error prompted  Pope Gregory XIII 
-   to reform the calendar in accordance with instructions
-   from the Council of Trent.
-  </para>
-
-  <para>   
-   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 only 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 this century.
-
-   The reform was observed by Great Britain and Dominions (including what is
-   now the USA) in 1752.
-   Thus 2 Sep 1752 was followed by 14 Sep 1752.
-
-   This is why Unix systems have <application>cal</application>
-   produce the following:
-
-   <programlisting>
-% cal 9 1752
-   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
-   </programlisting>
-  </para>
-
-  <note>
-   <para>
-    SQL92 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 1752-09-03 and 1752-09-13, although eliminated in
-    some countries by Papal fiat, conform to
-    <quote>natural rules</quote> and are hence valid dates.
-   </para>
-  </note>
-
-  <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 the
-   calendar in 2637 BC.
-   
-   The People's Republic of China uses the Gregorian calendar
-   for civil purposes. Chinese calendar is used for determining
-   festivals.
-  </para>
- </sect1>
-</appendix>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/developer.sgml b/doc/src/sgml/developer.sgml
deleted file mode 100644
index be1591e033d..00000000000
--- a/doc/src/sgml/developer.sgml
+++ /dev/null
@@ -1,34 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/Attic/developer.sgml,v 1.6 2001/10/09 18:45:59 petere Exp $ -->
-<!-- PostgreSQL Developer's Guide -->
-
-<book id="developer">
- <title>PostgreSQL &version; Developer's Guide</title>
-
- <bookinfo>
-  <corpauthor>The PostgreSQL Global Development Group</corpauthor>
-  &legal;
-
-  <abstract>
-   <para>
-    This document contains assorted information that can be of use to
-    <productname>PostgreSQL</> developers.
-   </para>
-  </abstract>
- </bookinfo>
- 
- &sources;
- &arch-dev; 
- &catalogs;
- &protocol;
- &compiler;
- &bki;
- &page;
- &geqo;
- &nls;
-<!-- appendices -->
- &cvs;
- &docguide;
-<![%single-book;[
- &biblio;
-]]>
-</book>
diff --git a/doc/src/sgml/dfunc.sgml b/doc/src/sgml/dfunc.sgml
deleted file mode 100644
index cc1fb54f968..00000000000
--- a/doc/src/sgml/dfunc.sgml
+++ /dev/null
@@ -1,331 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.20 2002/01/20 22:19:55 petere Exp $
--->
-
-<sect2 id="dfunc">
- <title id="dfunc-title">Compiling and Linking Dynamically-Loaded Functions</title>
-
- <para>
-  Before you are able to use your
-  <productname>PostgreSQL</productname> extension functions written in
-  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.
- </para>
-
- <para>
-  For more information 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>.
-  In addition, the <productname>PostgreSQL</productname> source code
-  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
-  of the <productname>PostgreSQL</productname> source code, however.
- </para>
-
- <para>
-  <indexterm><primary>PIC</></>
-  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>), 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
-  this is the theory.  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>
-
- <para>
-
-<!--
-  Note:  Reading GNU Libtool sources is generally a good way of figuring out
-  this information.  The methods used within
- <productname>PostgreSQL</> source code are not
-  necessarily ideal.
--->
-
-  <variablelist>
-   <varlistentry>
-    <term><productname>BSD/OS</productname></term>
-    <indexterm><primary>BSD/OS</></>
-    <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
-      <productname>BSD/OS</productname>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><productname>FreeBSD</productname></term>
-    <indexterm><primary>FreeBSD</></>
-    <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
-      <productname>FreeBSD</productname>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><productname>HP-UX</productname></term>
-    <indexterm><primary>HP-UX</></>
-    <listitem>
-     <para>
-      The compiler flag of the system compiler to create
-      <acronym>PIC</acronym> is <option>+z</option>.  When using
-      <productname>GCC</productname> 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>
-      <productname>HP-UX</productname> uses the extension
-      <filename>.sl</filename> for shared libraries, unlike most other
-      systems.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><productname>IRIX</productname></term>
-    <indexterm><primary>IRIX</></>
-    <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><productname>Linux</productname></term>
-    <indexterm><primary>Linux</></>
-    <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>
-
-   <varlistentry>
-    <term><productname>NetBSD</productname></term>
-    <indexterm><primary>NetBSD</></>
-    <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>
-
-   <varlistentry>
-    <term><productname>OpenBSD</productname></term>
-    <indexterm><primary>OpenBSD</></>
-    <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><productname>Solaris</productname></term>
-    <indexterm><primary>Solaris</></>
-    <listitem>
-     <para>
-      The compiler flag to create <acronym>PIC</acronym> is
-      <option>-KPIC</option> with the Sun compiler and
-      <option>-fpic</option> with <productname>GCC</productname>.  To
-      link shared libraries, the compiler option is
-      <option>-G</option> with either compiler or alternatively
-      <option>-shared</option> with <productname>GCC</productname>.
-<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>
-
-   <varlistentry>
-    <term>Tru64 UNIX</term>   
-    <indexterm><primary>Tru64 UNIX</></>
-    <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><productname>UnixWare</productname></term>
-    <indexterm><primary>UnixWare</></>
-    <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>
-
-  </variablelist>
- </para>
-
- <tip>
-  <para>
-   If you want to package your extension modules for wide distribution
-   you should consider using <ulink
-   url="http://www.gnu.org/software/libtool/"><productname>GNU
-   Libtool</productname></ulink> for building shared libraries.  It
-   encapsulates the platform differences into a general and powerful
-   interface.  Serious packaging also requires considerations about
-   library versioning, symbol resolution methods, and other issues.
-  </para>
- </tip>
-
- <para>
-  The resulting shared library file can then be loaded into
-  <productname>PostgreSQL</productname>.  When specifying the file name
-  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` > 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
-You should look at the <citetitle>PostgreSQL User's Manual</>
-for an explanation of this
-procedure.
-
-  -->
-
-</sect2>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-tabs-mode:nil
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/share/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/diskusage.sgml b/doc/src/sgml/diskusage.sgml
deleted file mode 100644
index 6bec4e20b4a..00000000000
--- a/doc/src/sgml/diskusage.sgml
+++ /dev/null
@@ -1,109 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/diskusage.sgml,v 1.1 2002/06/13 05:15:22 momjian Exp $
--->
-
-<chapter id="diskusage">
- <title>Monitoring Disk Usage</title>
-
- <sect1 id="disk-usage">
-  <title>Monitoring 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. To store long column values, there is also a
-   <acronym>TOAST</> file associated with the table, named based on the
-   table's oid (actually pg_class.relfilenode), and an index on the
-   <acronym>TOAST</> table. There also may be indexes associated with
-   the base table.
-  </para>
-
-  <para>
-   You can monitor disk space from two places; from inside
-   <application>psql</> and from the command line using
-   <application>contrib/oid2name</>. Using <application>psql</> you can
-   issue queries to see the disk usage for any table:
-<programlisting>
-play=# SELECT relfilenode, relpages
-play-# FROM pg_class
-play-# WHERE relname = 'customer';
- relfilenode | relpages 
--------------+----------
-       16806 |       60
-(1 row)
-</programlisting>
-  </para>
-
-  <para>   
-   Each page is typically 8 kilobytes. <literal>relpages</> is only
-   updated by <command>VACUUM</> and <command>ANALYZE</>. To show the
-   space used by <acronym>TOAST</> tables, use a query based on the heap
-   relfilenode:
-<programlisting>
-play=# SELECT relname, relpages
-play-# FROM pg_class
-play-# WHERE relname = 'pg_toast_16806' or
-play-#       relname = 'pg_toast_16806_index'
-play-# ORDER BY relname;
-       relname        | relpages 
-----------------------+----------
- pg_toast_16806       |        0
- pg_toast_16806_index |        1
-</programlisting>
-  </para>
-
-  <para>
-   You can easily display index usage too:
-<programlisting>
-play=# SELECT c2.relname, c2.relpages
-play-# FROM pg_class c, pg_class c2, pg_index i
-play-# WHERE c.relname = 'customer' AND
-play-#       c.oid = i.indrelid AND
-play-#       c2.oid = i.indexrelid
-play-# ORDER BY c2.relname;
-       relname        | relpages 
-----------------------+----------
- customer_id_indexdex |       26
-</programlisting>
-  </para>
-
-  <para>
-   It is easy to find your largest files using <application>psql</>:
-<programlisting>
-play=# SELECT relname, relpages
-play-# FROM pg_class
-play-# ORDER BY relpages DESC;
-       relname        | relpages 
-----------------------+----------
- bigtable             |     3290
- customer             |     3144
-</programlisting>
-  </para>
-
-  <para>
-   You can also use <application>oid2name</> to show disk usage. See
-   <filename>README.oid2name</> for examples. It includes a script
-   shows disk usage for each database.
-  </para>
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml
deleted file mode 100644
index 7df4995cfb8..00000000000
--- a/doc/src/sgml/docguide.sgml
+++ /dev/null
@@ -1,1274 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.41 2002/03/22 19:20:08 petere Exp $ -->
-
-<appendix id="docguide">
- <title>Documentation</title>
-
- <para>
-  <productname>PostgreSQL</productname> has four primary documentation
-  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>
-     Postscript, for printing
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     man pages, for quick reference.
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  Additionally, a number of plain-text README-type files can be found
-  throughout the <productname>PostgreSQL</productname> source tree,
-  documenting various implementation issues.
- </para>
-
- <para>
-  The documentation is organized into several <quote>books</quote>:
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     <citetitle>Tutorial</citetitle>:  introduction for new users
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <citetitle>User's Guide</citetitle>: documents the SQL implementation
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <citetitle>Reference Manual</citetitle>: reference pages for programs and SQL commands
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <citetitle>Administrator's Guide</citetitle>: installation and server maintenance
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <citetitle>Programmer's Guide</citetitle>: programming client
-     applications and server extensions
-    </para>
-   </listitem>
-   <listitem>
-    <para>
-     <citetitle>Developer's Guide</citetitle>: assorted information
-     for developers of <productname>PostgreSQL</> proper
-    </para>
-   </listitem>
-  </itemizedlist>
-
-  All books are available as HTML and Postscript.  The
-  <citetitle>Reference Manual</citetitle> contains reference entries which
-  are also shipped as man pages.
- </para>
-
- <para>
-  <acronym>HTML</acronym> documentation and man pages are part of a
-  standard distribution and are installed by default.  Postscript
-  format documentation is available separately for download.
- </para>
-
- <sect1>
-  <title>DocBook</title>
-  <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 SGML 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</ulink> group.  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://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>
- </sect1>
-
-
- <sect1 id="doc-toolsets">
-  <title>Tool Sets</title>
-
-  <para>
-   The following tools are used to process the documentation.  Some
-   may be optional, as noted.
-
-   <variablelist>
-    <varlistentry>
-     <term><ulink url="http://www.oasis-open.org/docbook/sgml/">DocBook DTD</ulink></term>
-     <listitem>
-      <para>
-       This is the definition of DocBook itself.  We currently use
-       version 3.1; you cannot use later or earlier versions.  Note
-       that there is also an <acronym>XML</acronym> version of DocBook
-       -- do not use that.
-      </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://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://docbook.sourceforge.net/projects/dsssl/index.html">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://docbook2x.sourceforge.net">DocBook2X tools</ulink></term>
-     <listitem>
-      <para>
-       This optional package is used to create man pages.  It has a
-       number of prerequisite packages of its own.  Check the web
-       site.
-      </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>
-   </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 may be some other packaged
-   distributions for these tools. Please report package status to the
-   docs mailing list and we will include that information here.
-  </para>
-
-  <sect2>
-   <title><productname>Linux</productname> <acronym>RPM</acronym> Installation</title>
-
-   <para>
-    Many vendors provide a complete RPM set for DocBook processing in
-    their distribution, which is usually based on the <ulink
-    url="http://sources.redhat.com/docbook-tools/">docbook-tools</ulink>
-    effort at Red Hat Software.  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>
-
-  <sect2>
-   <title>FreeBSD Installation</title>
-
-   <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/docbook-310</filename></para>
-     </listitem>
-     <listitem>
-      <para><filename>textproc/iso8879</filename></para>
-     </listitem>
-     <listitem>
-      <para><filename>textproc/dsssl-docbook-modular</filename></para>
-     </listitem>
-    </itemizedlist>
-    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</filename>.  Be sure to
-    have the following line in there:
-<programlisting>
-CATALOG "/usr/local/share/sgml/docbook/3.1/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>
-
-  <sect2>
-   <title>Debian Packages</title>
-
-   <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 jade
-apt-get install docbook
-apt-get install docbook-stylesheets
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Manual Installation from Source</title>
-
-   <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>
-       <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>
-      </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>
-      <para>
-       Obtain the <ulink
-       url="http://www.oasis-open.org/docbook/sgml/3.1/docbk31.zip">DocBook
-       V3.1</ulink> distribution.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Create the directory
-       <filename>/usr/local/share/sgml/docbook31</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/docbook31</userinput>
-<prompt>$ </prompt><userinput>cd /usr/local/share/sgml/docbook31</userinput>
-</screen>
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Unpack the archive.
-<screen>
-<prompt>$ </prompt><userinput>unzip -a ...../docbk31.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 "docbook31/docbook.cat"
-</programlisting>
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Optionally, you can edit the file
-       <filename>docbook.cat</filename> and comment out or remove the
-       line containing <literal>DTDDECL</literal>.  If you do not then
-       you will get warnings from <application>jade</application>, but
-       there is no further harm.
-      </para>
-     </step>
-
-     <step>
-      <para>
-       Download the <ulink
-       url="http://www.oasis-open.org/cover/ISOEnts.zip">ISO 8879
-       character entities</ulink> archive, 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/docbook31</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>
-
-    <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,
-     <productname>PostgreSQL</productname> doesn't use this catalog
-     entry.  See <xref linkend="doc-build"> for information about how
-     to select the stylesheets instead.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Installing <productname>JadeTeX</productname></title>
-
-    <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></ulink> site.
-     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
-     <productname>PostgreSQL</productname> documentation sources, you
-     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>
- </sect1>
-
-
- <sect1 id="doc-build">
-  <title>Building The Documentation</title>
-
-  <para>
-   Before you can build the documentation you need to run the
-   <filename>configure</filename> script as you would when building
-   the programs themselves.  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 V3.1... yes
-checking for DocBook stylesheets... /usr/lib/sgml/stylesheets/nwalsh-modular
-checking for sgmlspl... sgmlspl
-</computeroutput>
-</screen>
-   If neither <filename>onsgmls</filename> nor
-   <filename>nsgmls</filename> were found then you will not see the
-   remaining 4 lines.  <filename>nsgmls</filename> is part of the Jade
-   package.  If <quote>DocBook V3.1</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>
-
-  <para>
-   Once you have everything set up, change to the directory
-   <filename>doc/src/sgml</filename> and run one of the following
-   commands: (Remember to use GNU make.)
-   <itemizedlist>
-    <listitem>
-     <para>
-      To build the <acronym>HTML</acronym> version of the
-      <citetitle>Administrator's Guide</citetitle>:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake admin.html</userinput>
-</screen>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      For the RTF version of the same:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake admin.rtf</userinput>
-</screen>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      To get a <acronym>DVI</acronym> version via
-      <productname>JadeTeX</productname>:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake admin.dvi</userinput>
-</screen>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      And Postscript from the <acronym>DVI</acronym>:
-<screen>
-<prompt>doc/src/sgml$ </prompt><userinput>gmake admin.ps</userinput>
-</screen>
-     </para>
-     <note>
-      <para>
-       The official Postscript format documentation is generated
-       differently.  See <xref linkend="doc-hardcopy"> below.
-      </para>
-     </note>
-    </listitem>
-   </itemizedlist>
-
-   The other books can be built with analogous commands by replacing
-   <literal>admin</literal> with one of <literal>developer</literal>,
-   <literal>programmer</literal>, <literal>tutorial</literal>, or
-   <literal>user</literal>.  Using <literal>postgres</literal> builds
-   an integrated version of all 5 books, which is practical since the
-   browser interface makes it easy to move around all of the
-   documentation by just clicking.
-  </para>
-
-  <sect2>
-   <title>HTML</title>
-
-   <para>
-    When building <acronym>HTML</acronym> documentation in
-    <filename>doc/src/sgml</filename>, some of the resulting files
-    will possibly (or quite certainly) have conflicting names between
-    books.  Therefore the files are not in that directory in the
-    regular distribution.  Instead, the files belonging to each book
-    are stored in a tar archive that is unpacked at installation time.
-    To create a set of <acronym>HTML</acronym> documentation packages
-    use the commands
-<programlisting>
-cd doc/src
-gmake tutorial.tar.gz
-gmake user.tar.gz
-gmake admin.tar.gz
-gmake programmer.tar.gz
-gmake postgres.tar.gz
-gmake install
-</programlisting>
-    In the distribution, these archives live in the
-    <filename>doc</filename> directory and are installed by default
-    with <command>gmake install</command>.
-  </para>
- </sect2>
-
- <sect2 id="doc-manpages">
-  <title>Manpages</title>
-
-  <para>
-   We use the <application>docbook2man</application> utility 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 page package, use the commands
-<programlisting>
-cd doc/src
-gmake man
-</programlisting>
-   which will result in a tar file being generated in the
-   <filename>doc/src</filename> directory.
-  </para>
-
-  <para>
-   The man build leaves a lot of confusing output, and special care
-   must be taken to produce quality results.  There is still room for
-   improvement in this area.
-  </para>
- </sect2>
-
- <sect2 id="doc-hardcopy">
-  <title>Hardcopy Generation</title>
-
-  <para>
-   The hardcopy Postscript documentation is generated by converting the
-   <acronym>SGML</acronym> source code to <acronym>RTF</acronym>, then
-   importing into <productname>Applixware</productname>. 
-   After a little cleanup (see the following
-   section) the output is <quote>printed</quote> to a postscript file.
-  </para>
-
-<!--
-  <para>
-   Some figures were redrawn to avoid having bitmap
-   <acronym>GIF</acronym> files in the hardcopy documentation. One
-   figure, of the system catalogs, was sufficiently complex that there
-   was  not time to redraw it. It was converted to fit using the
-   following commands:
-
-   <programlisting>
-% convert -monochrome -v -geometry 500x500'>' catalogs.ps catalogs.gif
-% convert -v -crop 400x500 catalogs.gif catalogs-cropped.gif
-   </programlisting>
-
-  </para>
--->
-
-   <para>
-    Several areas are addressed while generating Postscript
-    hardcopy, including RTF repair, ToC generation, and page break
-    adjustments. 
-   </para>
-
-   <procedure>
-    <title><productname>Applixware</productname> <acronym>RTF</acronym> Cleanup</title>
-
-    <para>
-     <application>jade</application>, an integral part of the
-     hardcopy procedure, omits specifying a default style for body
-     text. In the past, this undiagnosed problem led to a long process
-     of Table of Contents (ToC) 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> input by typing (for example):
-      <programlisting>
-% cd doc/src/sgml
-% make tutorial.rtf
-      </programlisting>
-     </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
-       <emphasis>preceding</emphasis> paragraph to the current
-       paragraph, and instead tie the current paragraph to the
-       following one. A utility, <application>fixrtf</application> is
-       available in 
-       <filename>doc/src/sgml</filename> to accomplish these repairs:
-
-       <programlisting>
-% cd doc/src/sgml
-% fixrtf tutorial.rtf
-       </programlisting>
-
-       or
-
-       <programlisting>
-% cd doc/src/sgml
-% fixrtf --refentry reference.rtf
-       </programlisting>
-      </para>
-
-      <para>
-      The script adds <literal>{\s0 Normal;}</literal> as
-      the zero-th style in the document. According to <productname>Applixware</productname>, the
-      RTF standard would prohibit adding an implicit zero-th style,
-      though M$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 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
-	<literal>Tools.BookBuilding.CreateToC</literal>. 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
-	<literal>Format.Style</literal>, selecting each of the three
-	ToC styles, and adjusting the indents for <literal>First</literal> and
-	<literal>Left</literal>. Use the following values:
-
-	<table>
-	 <title>Indent Formatting for Table of Contents</title>
-	 <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>
-	</table>
-       </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>
-
-       <listitem>
-	<para>
-	 Insert figures into the document. Center each figure on the page using
-	 the centering margins button on the <productname>Applixware</productname> toolbar.
-
-	 <note>
-	  <para>
-	   Not all documents have figures.
-	   You can grep the <acronym>SGML</acronym> source files for
-	   the string <literal>graphic</literal> to identify those parts of the
-	   documentation that may have figures. A few figures are replicated in
-	   various parts of the documentation.
-	  </para>
-	 </note>
-	</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 per document.
-     </para>
-    </step>
-
-<!--
-Later stylesheets seem to not need this adjustment - thomas 2001-11-29
-    <step performance="required">
-     <para>
-      If a bibliography is present, remove the <firstterm>short
-       form</firstterm> reference title from each entry. The
-      <productname>DocBook</productname> stylesheets from Norm Walsh
-      seem to print these out, even though this is a subset of the
-      information immediately following.
-     </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
-	 <literal>Tools->Book Building->Create Table of
-	  Contents</literal>. 
-	</para>
-       </step>
-
-       <step>
-	<para>
-	 Unbind the ToC by selecting
-	 <literal>Tools->Field Editing->Unprotect</literal>.
-	</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>
-
-    <step performance="required">
-     <para>
-      Compress the Postscript file using <application>gzip</application>.
-      Place the compressed file into the <filename>doc</filename> directory.
-     </para>
-    </step>
-   </procedure>
-  </sect2>
-
-  <sect2>
-   <title>Plain Text Files</title>
-
-   <para>
-    Several files are distributed as plain text, for reading during
-    the installation process. The <filename>INSTALL</filename> file
-    corresponds to the chapter in the <citetitle>Administrator's
-    Guide</citetitle>, 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>
-
-<!--
-  * This is how you can create text files via RTF and ApplixWare,
-  * for historical reference.
-
-   <procedure>
-    <title>Plain Text Generation</title>
-
-    <para>
-     Both <filename>INSTALL</filename> and
-     <filename>HISTORY</filename> are generated from existing
-     <acronym>SGML</acronym> sources. They are extracted from the same 
-     intermediate <acronym>RTF</acronym> file.
-    </para>
-
-    <step performance="required">
-     <para>
-      Generate <acronym>RTF</acronym> by typing:
-      <programlisting>
-% cd doc/src/sgml
-% make installation.rtf
-      </programlisting>
-     </para>
-    </step>
-      
-    <step performance="required">
-     <para>
-      Import <filename>installation.rtf</filename> into
-      <productname>Applix Words</productname>.
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-      Set the page width and margins.
-     </para>
-
-     <substeps>
-      <step performance="required">
-       <para>
-	Adjust the page width in File.PageSetup to 10 inches.
-       </para>
-      </step>
-
-      <step performance="required">
-       <para>
-	Select all text.
-	Adjust the right margin using the ruler to 9.5 inches. This
-	will give a maximum column width of 79 characters, within the
-	80 columns upper limit goal.
-       </para>
-      </step>
-     </substeps>
-    </step>
-
-    <step performance="required">
-     <para>
-      Lop off the parts of the document that are not needed.
-     </para>
-
-     <para>
-      For <filename>INSTALL</filename>, remove all release notes from
-      the end of the text, except for those from the current release.
-      For <filename>HISTORY</filename>, remove all text up to the
-      release notes, preserving and modifying the title and ToC.
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-      Export the result as <literal>ASCII Layout</literal>.
-     </para>
-    </step>
-
-    <step performance="required">
-     <para>
-      Using emacs or vi, clean up the tabular information in
-      <filename>INSTALL</filename>. Remove the <literal>mailto</literal>
-      <acronym>URLs</acronym> for the porting contributors to shrink
-      the column heights.
-     </para>
-    </step>
-   </procedure>
--->
-
-  </sect2>
- </sect1>
-
-
- <sect1 id="doc-sources">
-  <title>Documentation Authoring</title>
-
-   <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>
-
-    <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-default-dtd-file "./reference.ced")
-(setq sgml-exposed-tags nil)
-(setq sgml-catalog-files '("/usr/local/share/sgml/catalog"))
-(setq sgml-ecat-files nil)
-
-(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>
-     Currently, each <acronym>SGML</acronym> source file has the
-     following block at the end of the file:
-
-<programlisting>
-&lt;!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
---&gt;
-</programlisting>
-     This will set up a number of editing mode parameters even if you
-     do not set up your <filename>~/.emacs</filename> file, but it is
-     a bit unfortunate, since if you followed the installation
-     instructions above, then the catalog path will not match your
-     location.  Hence you might need to turn off local variables:
-<programlisting>
-(setq inhibit-local-variables t)
-</programlisting>
-    </para>
-
-    <para>
-     The <productname>PostgreSQL</productname> distribution includes a
-     parsed DTD definitions file <filename>reference.ced</filename>.
-     You may find that when using PSGML, 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 V3.1//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>
-
-    <para>
-     <productname>GNU Emacs</productname> ships with a different SGML
-     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.
-    </para>
-
-    <para>
-     Norm Walsh offers a major <ulink
-     url="http://nwalsh.com/emacs/docbookide/index.html">mode
-     specifically for DocBook</ulink> which also has font-lock and a
-     number of features to reduce typing.
-    </para>
-   </sect2>
-
- </sect1>
-
-</appendix>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml
deleted file mode 100644
index 6dc7399198b..00000000000
--- a/doc/src/sgml/ecpg.sgml
+++ /dev/null
@@ -1,1085 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.36 2002/01/20 22:19:55 petere Exp $
--->
-
- <chapter id="ecpg">
-  <docinfo>
-   <authorgroup>
-    <author>
-     <firstname>Linus</firstname>
-     <surname>Tolke</surname>
-    </author>
-    <author>
-     <firstname>Michael</firstname>
-     <surname>Meskes</surname>
-    </author>
-   </authorgroup>
-   <copyright>
-    <year>1996-1997</year>
-    <holder>Linus Tolke</holder>
-   </copyright>
-   <copyright>
-    <year>1998</year>
-    <holder>Michael Meskes</holder>
-   </copyright>
-   <date>Transcribed 1998-02-12</date>
-  </docinfo>
-
-  <title><application>ecpg</application> - Embedded <acronym>SQL</acronym> 
-   in <acronym>C</acronym></title>
-
-  <indexterm zone="ecpg"><primary>embedded SQL</primary><secondary>in C</secondary></indexterm>
-
-  <para>
-   This describes the embedded <acronym>SQL</acronym> package for
-   <productname>PostgreSQL</productname>. It works with
-   <acronym>C</acronym> and <acronym>C++</acronym>. It was written by
-   Linus Tolke (<email>linus@epact.se</email>) and Michael Meskes
-   (<email>meskes@debian.org</email>). The package is installed with the
-   <productname>PostgreSQL</> distribution, and carries a similar license.
-  </para>
-
-  <sect1 id="ecpg-why">
-   <title>Why Embedded <acronym>SQL</acronym>?</title>
-
-   <para>
-    Embedded <acronym>SQL</acronym> has advantages over other methods
-    for handling <acronym>SQL</acronym> queries. It takes care of
-    the tedious passing of information to and from variables in your
-    <acronym>C</acronym> or <acronym>C++</acronym> program. Many
-    <acronym>RDBMS</acronym> packages support this embedded language.
-   </para>
-
-   <para> 
-    There is an ANSI standard describing how the embedded language
-    should work. <application>ecpg</application> was designed to match
-    this standard as much as possible. It is possible to port embedded
-    <acronym>SQL</acronym> programs written for other
-    <acronym>RDBMS</acronym> to <productname>PostgreSQL</productname>.
-   </para>
-  </sect1>
-
-  <sect1 id="ecpg-concept">
-   <title>The Concept</title>
-
-   <para>
-    You write your program in <acronym>C/C++</acronym> with special
-    <acronym>SQL</acronym> constructs. When declaring variables to be
-    used in <acronym>SQL</acronym> statements, you need to put them in a
-    special <command>declare</> section. You use a special syntax for the
-    <acronym>SQL</acronym> queries.
-   </para>
-
-   <para>
-    Before compiling you run the file through the embedded
-    <acronym>SQL</acronym> <acronym>C</acronym> preprocessor and it
-    converts the <acronym>SQL</acronym> statements you used to function
-    calls with the variables used as arguments. Both query input and
-    result output variables are passed.
-   </para>
-
-   <para>
-    After compiling, you must link with a special library that contains
-    needed functions. These functions fetch information from the
-    arguments, perform the <acronym>SQL</acronym> query using the
-    <filename>libpq</filename> interface, and put the result in the
-    arguments specified for output.
-   </para>
-  </sect1>
-
-  <sect1 id="ecpg-use">
-   <title>How To Use <application>ecpg</application></title>
-
-   <para>
-    This section describes how to use <application>ecpg</application>.
-   </para>
-
-   <sect2>
-    <title>Preprocessor</title>
-
-    <para>
-     The preprocessor is called <application>ecpg</application>. After
-     installation it resides in the <productname>PostgreSQL</productname>
-     <filename>bin/</filename> directory.
-    </para>
-   </sect2>
-   <sect2>
-    <title>Library</title>
-
-    <para>
-     The <application>ecpg</application> library is called
-     <filename>libecpg.a</filename> or <filename>libecpg.so</filename>.
-     Additionally, the library uses the <filename>libpq</filename>
-     library for communication to the
-     <productname>PostgreSQL</productname> server. You will have to link
-     your program using <parameter>-lecpg -lpq</parameter>.
-    </para>
-
-    <para>
-     The library has some methods that are <quote>hidden</quote> but may prove
-     useful.
-
-     <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>. Most
-        <acronym>SQL</acronym> statement log their arguments and results.
-       </para>
-
-       <para>
-        The most important function , <function>ECPGdo</function>, logs
-        all <acronym>SQL</acronym> statements with both the expanded
-        string, i.e. the string with all the input variables inserted,
-        and the result from the <productname>PostgreSQL</productname>
-        server. This can be very useful when searching for errors in
-        your <acronym>SQL</acronym> statements.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <function>ECPGstatus()</function>
-        This method returns TRUE if we are connected to a database and FALSE if not.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Error handling</title>
-
-    <para>
-     To detect errors from the <productname>PostgreSQL</productname>
-     server, include a line like: 
-<programlisting>
-exec sql include sqlca; 
-</programlisting>
-     in the include section of your file. This will define a struct and
-     a variable with the name <parameter>sqlca</parameter> as follows:
-<programlisting>
-struct sqlca
-{
- char sqlcaid[8];
- long sqlabc;
- long sqlcode;
- struct
- {
-  int sqlerrml;
-  char sqlerrmc[70];
- } sqlerrm;
- char sqlerrp[8];
- long sqlerrd[6];
- /* 0: empty                                         */
- /* 1: OID of processed tuple if applicable          */
- /* 2: number of rows processed in an INSERT, UPDATE */
- /*    or DELETE statement                           */
- /* 3: empty                                         */
- /* 4: empty                                         */
- /* 5: empty                                         */
- char sqlwarn[8];
- /* 0: set to 'W' if at least one other is 'W'       */
- /* 1: if 'W' at least one character string          */
- /*    value was truncated when it was               */
- /*    stored into a host variable.                  */
- /* 2: empty                                         */
- /* 3: empty                                         */
- /* 4: empty                                         */
- /* 5: empty                                         */
- /* 6: empty                                         */
- /* 7: empty                                         */
- char sqlext[8];
-} sqlca;
-</programlisting>
-    </para>
-
-    <para>
-     If an no error occurred in the last <acronym>SQL</acronym> statement.
-     <parameter>sqlca.sqlcode</parameter> will be 0 (ECPG_NO_ERROR). If
-     <parameter>sqlca.sqlcode</parameter> is less that zero, this is a
-     serious error, like the database definition does not match the
-     query. If it is greater than zero, it is a normal error like the
-     table did not contain the requested row.
-    </para>
-
-    <para>
-     <parameter>sqlca.sqlerrm.sqlerrmc</parameter> will contain a string
-     that describes the error. The string ends with the line number in
-     the source file.
-    </para>
-
-    <para>
-     These are the errors that can occur:
-
-     <variablelist>
-      <varlistentry>
-       <term><computeroutput>-12, Out of memory in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         Should not normally occur. This indicates your virtual memory is
-         exhausted.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-200 (ECPG_UNSUPPORTED): Unsupported type %s on line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         Should not normally occur. This 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.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-201 (ECPG_TOO_MANY_ARGUMENTS): Too many arguments line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         This means that <productname>PostgreSQL</productname> has
-         returned more arguments than we have matching variables.
-         Perhaps you have forgotten a couple of the host variables in
-         the <command>INTO :var1,:var2</command>-list.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-202 (ECPG_TOO_FEW_ARGUMENTS): Too few arguments line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         This means that <productname>PostgreSQL</productname> has
-         returned fewer arguments than we have host variables. Perhaps
-         you have too many host variables in the <command>INTO
-         :var1,:var2</command>-list.
-        </para> 
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-203 (ECPG_TOO_MANY_MATCHES): Too many matches line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         This means the query has returned several rows but the
-         variables specified are not arrays. The
-         <command>SELECT</command> command was not unique.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-204 (ECPG_INT_FORMAT): Not correctly formatted int type: %s line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         This means the host variable is of type <type>int</type> and
-         the field in the <productname>PostgreSQL</productname> database
-         is of another type and contains a value that cannot be
-         interpreted as an <type>int</type>. The library uses
-         <function>strtol()</function> for this conversion.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-205 (ECPG_UINT_FORMAT): Not correctly formatted unsigned type: %s line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         This means the host variable is of type <type>unsigned
-         int</type> and the field in the
-         <productname>PostgreSQL</productname> database is of another type
-         and contains a value that cannot be interpreted as an
-         <type>unsigned int</type>. The library uses
-         <function>strtoul()</function> for this conversion.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-206 (ECPG_FLOAT_FORMAT): Not correctly formatted floating-point type: %s line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         This means the host variable is of type <type>float</type> and
-         the field in the <productname>PostgreSQL</productname> 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.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-207 (ECPG_CONVERT_BOOL): Unable to convert %s to bool on line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         This means the host variable is of type <type>bool</type> and
-         the field in the <productname>PostgreSQL</productname> database
-         is neither <literal>'t'</> nor <literal>'f'</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-208 (ECPG_EMPTY): Empty query line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         <productname>PostgreSQL</productname> returned <symbol>PGRES_EMPTY_QUERY</symbol>, probably
-         because the query indeed was empty.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-209 (ECPG_MISSING_INDICATOR): NULL value without indicator in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         <productname>PostgreSQL</productname> returned <symbol>ECPG_MISSING_INDICATOR</symbol>
-         because a NULL was returned and no NULL indicator variable was supplied.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-210 (ECPG_NO_ARRAY): Variable is not an array in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         <productname>PostgreSQL</productname> returned <symbol>ECPG_NO_ARRAY</symbol>
-         because an ordinary variable was used in a place that requires
-         an array.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-211 (ECPG_DATA_NOT_ARRAY): Data read from backend is not an array in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         <productname>PostgreSQL</productname> returned <symbol>ECPG_DATA_NOT_ARRAY</symbol>
-         because the database returned an ordinary variable in a place
-         that requires array value.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-220 (ECPG_NO_CONN): No such connection %s in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The program tried to access a connection that does not exist.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-221 (ECPG_NOT_CONN): Not connected in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The program tried to access a connection that does exist but is
-         not open.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-230 (ECPG_INVALID_STMT): Invalid statement name %s in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The statement you are trying to use has not been prepared.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-240 (ECPG_UNKNOWN_DESCRIPTOR): Descriptor %s not found in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The descriptor specified was not found. The statement you are trying to use has not been prepared.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-241 (ECPG_INVALID_DESCRIPTOR_INDEX): Descriptor index out of range in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The descriptor index specified was out of range.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-242 (ECPG_UNKNOWN_DESCRIPTOR_ITEM): Descriptor %s not found in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The descriptor specified was not found. The statement you are trying to use has not been prepared.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-243 (ECPG_VAR_NOT_NUMERIC): Variable is not a numeric type in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The database returned a numeric value and the variable was not
-         numeric.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-244 (ECPG_VAR_NOT_CHAR): Variable is not a character type in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The database returned a non-numeric value and the variable was
-         numeric.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-400 (ECPG_PGSQL): Postgres error: %s line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         Some <productname>PostgreSQL</productname> error. 
-         The message contains the error message from the
-         <productname>PostgreSQL</productname> backend.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-401 (ECPG_TRANS): Error in transaction processing line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         <productname>PostgreSQL</productname> signaled that we cannot start,
-         commit or rollback the transaction.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>-402 (ECPG_CONNECT): Could not connect to database %s in line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         The connect to the database did not work.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>100 (ECPG_NOT_FOUND): Data not found line %d.</computeroutput></term>
-       <listitem>
-        <para>
-         This is a <quote>normal</quote> error that tells you that what you are querying cannot
-         be found or you are at the end of the cursor.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="ecpg-limitations">
-   <title>Limitations</title>
-
-   <para>
-    What will never be included and why it cannot be done:
-
-    <variablelist>
-     <varlistentry>
-      <term>Oracle's single tasking</term>
-      <listitem>
-       <para>
-        Oracle version 7.0 on <systemitem class="osname">AIX</> 3 uses OS-supported locks in shared
-        memory that allow an application designer to link an application
-        in a <quote>single tasking</quote> way. Instead of starting one client
-        process per application process, both the database part and the
-        application part run in the same process. In later versions of
-        Oracle this is no longer supported.
-       </para>
-
-       <para>
-        This would require a total redesign of the
-        <productname>PostgreSQL</productname> access model and the
-        performance gain does not justify the effort.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect1>
-
-  <sect1 id="ecpg-porting">
-   <title>Porting From Other <acronym>RDBMS</acronym> Packages</title>
-
-   <para>
-    The design of <application>ecpg</application> follows the SQL
-    standard. Porting from a standard RDBMS should not be a problem.
-    Unfortunately there is no such thing as a standard RDBMS. Therefore
-    <application>ecpg</application> tries to understand syntax
-    extensions as long as they do not create conflicts with the
-    standard.
-   </para>
-
-   <para>
-    The following list shows all the known incompatibilities. If you
-    find one not listed please notify the developers. Note, however, that
-    we list only incompatibilities from a precompiler of another RDBMS
-    to <application>ecpg</application> and not
-    <application>ecpg</application> features that these RDBMS do not
-    support.
-   </para>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term>Syntax of FETCH</term>
-      <indexterm><primary>FETCH</><secondary>embedded SQL</></indexterm>
-      <listitem>
-       <para>
-        The standard syntax for FETCH is:
-       </para>
-       <para>
-        FETCH [direction] [amount] IN|FROM <replaceable>cursor</replaceable>.
-       </para>
-       <para>
-        <indexterm><primary>Oracle</></>
-        <application>Oracle</application>, however, does not use the keywords IN
-        or FROM. This feature cannot be added since it would create parsing
-        conflicts.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect1>
-
-  <sect1 id="ecpg-develop">
-   <title>For the Developer</title>
-
-   <para>
-    This section explain how <application>ecpg</application>
-    works internally. It contains valuable information to help users
-    understand how to use <application>ecpg</application>.
-   </para>
-
-   <sect2>
-    <title>The Preprocessor</title>
-
-    <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.
-    </para>
-
-    <para>
-     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>EXEC SQL</command>
-     statement can be one of these:
-
-     <variablelist>
-      <varlistentry>
-       <term>Declare sections</term>
-       <listitem>
-        <para>
-         <command>Declare</> sections begin with:
-<programlisting>
-exec sql begin declare section;
-</programlisting>
-         and end with:
-<programlisting>
-exec sql end declare section;
-</programlisting>
-         In this section only variable declarations are allowed. Every
-         variable declared within this section is stored in a list
-         of variables indexed by name together with its corresponding
-         type.
-        </para>
-
-        <para>
-         In particular the definition of a structure or union also must
-         be listed inside a <command>declare</> section. Otherwise
-         <application>ecpg</application> cannot handle these types since
-         it does not know the definition.
-        </para>
-
-        <para>
-         The declaration is also echoed to the file to make it a normal
-         C variable.
-        </para>
-
-        <para>
-         The special types <type>VARCHAR</type> and <type>VARCHAR2</type> are converted into a named 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>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Include statements</term>
-       <listitem>
-        <para>
-         An include statement looks like:
-<programlisting>
-exec sql include filename;
-</programlisting>
-         Note that this is NOT the same as:
-<programlisting>
-#include &lt;filename.h&gt;
-</programlisting>
-        </para>
-
-        <para>
-         Instead the file specified is parsed by
-         <application>ecpg</application> so the contents of the file are
-         included in the resulting C code. This way you are able to
-         specify EXEC SQL commands in an include file.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Connect statement</term>
-       <listitem>
-        <para>
-         A connect statement looks like:
-<programlisting>
-exec sql connect to <replaceable>connection target</replaceable>;
-</programlisting>
-         It creates a connection to the specified database.
-        </para>
-
-        <para>
-         The <replaceable>connection target</replaceable> can be specified in the
-         following ways:
-         <itemizedlist>
-          <listitem>
-           <simpara>
-            <literal>dbname[@server][:port][as <replaceable>connection
-            name</replaceable>][user <replaceable>user name</replaceable>]</literal>
-           </simpara>
-          </listitem>
-
-          <listitem>
-           <simpara>
-            <literal>tcp:postgresql://server[:port][/dbname][as
-            <replaceable>connection name</replaceable>][user <replaceable>user name</replaceable>]</literal>
-           </simpara>
-          </listitem>
-
-          <listitem>
-           <simpara>
-            <literal>unix:postgresql://server[:port][/dbname][as
-            <replaceable>connection name</replaceable>][user <replaceable>user name</replaceable>]</literal>
-           </simpara>
-          </listitem>
- 
-          <listitem>
-           <simpara>
-            <literal><replaceable>character variable</replaceable>[as
-            <replaceable>connection name</replaceable>][user <replaceable>user name</replaceable>]</literal>
-           </simpara>
-          </listitem>
- 
-          <listitem>
-           <simpara>
-            <literal><replaceable>character string</replaceable>[as
-            <replaceable>connection name</replaceable>][<replaceable>user</replaceable>]</literal>
-           </simpara>
-          </listitem>
- 
-          <listitem>
-           <simpara>
-            <literal>default</literal>
-           </simpara>
-          </listitem>
- 
-          <listitem>
-           <simpara>
-            <literal>user</literal>
-           </simpara>
-          </listitem>
-         </itemizedlist>
-        </para>
-
-        <para>
-         There are also different ways to specify the user name:
-
-         <itemizedlist>
-          <listitem>
-           <simpara>
-            <literal><replaceable>userid</replaceable></literal>
-           </simpara>
-          </listitem>
-
-          <listitem>
-           <simpara>
-            <literal><replaceable>userid</replaceable>/<replaceable>password</replaceable></literal>
-           </simpara>
-          </listitem>
-
-          <listitem>
-           <simpara>
-            <literal><replaceable>userid</replaceable> identified by <replaceable>password</replaceable></literal>
-           </simpara>
-          </listitem>
-
-          <listitem>
-           <simpara>
-            <literal><replaceable>userid</replaceable> using <replaceable>password</replaceable></literal>
-           </simpara>
-          </listitem>
-         </itemizedlist>
-        </para>
-
-        <para> 
-         Finally, the <replaceable>userid</replaceable> and <replaceable>password</replaceable> may be a constant text, a
-         character variable, or a character string.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Disconnect statements</term>
-       <listitem>
-        <para>
-         A disconnect statement looks like:
-         <programlisting>
-exec sql disconnect [<replaceable>connection target</replaceable>];
-         </programlisting>
-         It closes the connection to the specified database.
-        </para>
-
-        <para>
-         The <replaceable>connection target</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>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Open cursor statement</term>
-       <listitem>
-        <para>
-         An open cursor statement looks like:
-<programlisting>
-exec sql open <replaceable>cursor</replaceable>;
-</programlisting>
-         and is not copied to the output. Instead, the cursor's
-         <command>DECLARE</> command is used because it opens the cursor
-         as well.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Commit statement</term>
-       <listitem>
-        <para>
-         A commit statement looks like:
-<programlisting>
-exec sql commit;
-</programlisting>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Rollback statement</term>
-       <listitem>
-        <para>
-         A rollback statement looks like:
-<programlisting>
-exec sql rollback;
-</programlisting>
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Other statements</term>
-       <listitem>
-        <para>
-         Other <acronym>SQL</acronym> statements are used by
-         starting with <command>exec sql</command> and ending 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
-         (<command>:</command>). The variable with that name is looked
-         up among the variables that were previously declared within a
-         <command>declare</> section. Depending on whether the variable is
-         being use for input or output, a pointer to the variable is
-         output to allow access by the function.
-        </para>
-
-        <para>
-         For every variable that is part of the <acronym>SQL</acronym>
-         query, the function gets other arguments:
-
-         <itemizedlist>
-          <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 value of the indicator variable or a pointer to the pointer of the indicator variable.
-           </para>
-          </listitem>
-
-          <listitem>
-           <para>
-            0.
-           </para>
-          </listitem>
-
-          <listitem>
-           <para>
-            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>
-         </itemizedlist>
-        </para>
-
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>A Complete Example</title>
-
-    <para>
-     Here is a complete example describing the output of the preprocessor of a
-     file <filename>foo.pgc</filename>:
-<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>
-/* Processed by ecpg (2.6.0) */
-/* These two include files are added by the preprocessor */
-#include &lt;ecpgtype.h&gt;;
-#include &lt;ecpglib.h&gt;;
-
-/* 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,&amp;(index),1L,1L,sizeof(int),
-        ECPGt_NO_INDICATOR, NULL , 0L, 0L, 0L, ECPGt_EOIT,
-        ECPGt_int,&amp;(result),1L,1L,sizeof(int),
-        ECPGt_NO_INDICATOR, NULL , 0L, 0L, 0L, ECPGt_EORT);
-#line 147 "foo.pgc"
-</programlisting>
-     (The indentation in this manual is added for readability and not
-     something the preprocessor does.)
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>The Library</title>
-
-    <para>
-     The most important function in the library is
-     <function>ECPGdo</function>. It takes a variable number of
-     arguments. Hopefully there are no computers that limit the
-     number of variables that can be accepted by a <function>varargs()</function> function. This
-     can easily add up to 50 or so arguments.
-    </para>
-
-    <para>
-     The arguments are:
-
-     <variablelist>
-      <varlistentry>
-       <term>A line number</term>
-       <listitem>
-        <para>
-         This is a 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> query 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
-         query. Where the variables should go the string contains
-         <literal>?</literal>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Input variables</term>
-       <listitem>
-        <para>
-         As described in the section about the preprocessor, every input variable
-         gets ten arguments.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>ECPGt_EOIT</literal></term>
-       <listitem>
-        <para>
-         An enum telling that there are no more input variables.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>Output variables</term>
-       <listitem>
-        <para>
-         As described in the section about the preprocessor, every input variable
-         gets ten arguments. These variables are filled by the function.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>ECPGt_EORT</term>
-       <listitem>
-        <para>
-         An enum telling that there are no more variables.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-
-    <para>
-     In the default mode, queries are committed only when <command>exec
-     sql commit</command> is issued. <application>Ecpg</application>
-     also supports auto-commit of transactions via the
-     <option>-t</option> command-line option or via the <literal>exec
-     sql set autocommit to on</literal> statement. In
-     <literal>autocommit</literal> mode, each query 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>
-   </sect2>
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml
deleted file mode 100644
index 4ae498e02ac..00000000000
--- a/doc/src/sgml/extend.sgml
+++ /dev/null
@@ -1,285 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.15 2002/01/07 02:29:11 petere Exp $
--->
-
- <chapter id="extend">
-  <title>Extending <acronym>SQL</acronym>: An Overview</title>
-
-  <para>
-   In  the  sections  that follow, we will discuss how you
-   can extend the <productname>PostgreSQL</productname> 
-   <acronym>SQL</acronym> query language by adding:
-
-   <itemizedlist spacing="compact" mark="bullet">
-    <listitem>
-     <para>
-      functions
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      data types
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      operators
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      aggregates
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <sect1 id="extend-how">
-   <title>How Extensibility Works</title>
-
-   <para>
-    <productname>PostgreSQL</productname> is extensible because its operation  is  
-    catalog-driven.   If  you  are familiar with standard 
-    relational 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
-    between <productname>PostgreSQL</productname> and  standard  relational  systems  is
-    that <productname>PostgreSQL</productname> stores much more information in its 
-    catalogs -- not only information about tables and  columns,
-    but also information about its types, functions, access
-    methods, and so on.  These tables can be  modified  by
-    the  user, and since <productname>PostgreSQL</productname> bases its internal operation 
-    on these tables, this means that <productname>PostgreSQL</productname> can  be
-    extended   by   users.    By  comparison,  conventional
-    database systems can only be extended by changing hardcoded  
-    procedures within the <acronym>DBMS</acronym> or by loading modules
-    specially written by the <acronym>DBMS</acronym> vendor.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname> is also unlike most  other  data  managers  in
-    that  the server can 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.
-   </para>
-  </sect1>
-
-  <sect1 id="type-system">
-   <title>The <productname>PostgreSQL</productname> Type System</title>
-
-   <para>
-    The <productname>PostgreSQL</productname> type system
-    can be broken down in several ways.
-    Types are divided into base types and composite  types.
-    Base  types  are those, like <type>int4</type>, that are implemented
-    in a language such as C.  They generally correspond  to
-    what are often known as <firstterm>abstract data types</firstterm>; <productname>PostgreSQL</productname>
-    can only operate on such types through methods provided
-    by  the  user and only understands the behavior of such
-    types to the extent that the user describes them.  
-    Composite  types  are  created whenever the user creates a
-    table.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname>  stores  these  types
-    in only one way (within the
-    file that stores all rows of a table)  but  the
-    user can <quote>look inside</quote> at the attributes of these types
-    from the query language and optimize their retrieval by
-    (for example) defining indexes on the attributes.
-    <productname>PostgreSQL</productname>  base  types are further
-    divided into built-in
-    types and user-defined  types.   Built-in  types  (like
-    <type>int4</type>)  are  those  that  are  compiled
-    into the system.
-    User-defined types are those created by the user in the
-    manner to be described later.
-   </para>
-  </sect1>
-
-  <sect1 id="pg-system-catalogs">
-   <title>About the <productname>PostgreSQL</productname> System Catalogs</title>
-
-   <para>
-    Having  introduced the basic extensibility concepts, we
-    can now take a look at how the  catalogs  are  actually
-    laid  out.  You can skip this section for now, but some
-    later sections will  be  incomprehensible  without  the
-    information  given  here,  so  mark this page for later
-    reference.
-    All system catalogs have names  that  begin  with
-    <literal>pg_</literal>.
-    The  following  tables contain information that may be
-    useful to the end user.  (There are many  other  system
-    catalogs,  but there should rarely be a reason to query
-    them directly.)
-
-    <table tocentry="1">
-     <title>PostgreSQL System Catalogs</title>
-     <titleabbrev>Catalogs</titleabbrev>
-     <tgroup cols="2">
-      <thead>
-       <row>
-	<entry>Catalog Name</entry>
-	<entry>Description</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry>pg_database</entry>
-	<entry> databases</entry>
-       </row>
-       <row>
-	<entry>pg_class</entry>
-	<entry> tables</entry>
-       </row>
-       <row>
-	<entry>pg_attribute</entry>
-	<entry> table columns</entry>
-       </row>
-       <row>
-	<entry>pg_index</entry>
-	<entry> indexes</entry>
-       </row>
-       <row>
-	<entry>pg_proc</entry>
-	<entry> procedures/functions </entry>
-       </row>
-       <row>
-	<entry>pg_type</entry>
-	<entry> data types (both base and complex)</entry>
-       </row>
-       <row>
-	<entry>pg_operator</entry>
-	<entry> operators</entry>
-       </row>
-       <row>
-	<entry>pg_aggregate</entry>
-	<entry> aggregate functions</entry>
-       </row>
-       <row>
-	<entry>pg_am</entry>
-	<entry> access methods</entry>
-       </row>
-       <row>
-	<entry>pg_amop</entry>
-	<entry> access method operators</entry>
-       </row>
-       <row>
-	<entry>pg_amproc</entry>
-	<entry> access method support functions</entry>
-       </row>
-       <row>
-	<entry>pg_opclass</entry>
-	<entry> access method operator classes</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-   <para>
-    <figure float="1" id="EXTEND-CATALOGS">
-     <title>The major <productname>PostgreSQL</productname> system catalogs</title>
-     <mediaobject>
-      <imageobject>
-       <imagedata fileref="catalogs" align="center">
-      </imageobject>
-     </mediaobject>
-    </figure>
-
-    The <citetitle>Developer's Guide</citetitle> gives a more detailed  explanation
-    of  these catalogs and their columns.  However,
-    <xref linkend="EXTEND-CATALOGS">
-    shows the major entities and their  relationships
-    in  the system catalogs.  (Columns that do not refer
-    to other entities are not shown unless they are part of
-    a primary key.)
-    This diagram is more or less incomprehensible until you
-    actually start looking at the contents of the  catalogs
-    and  see  how  they relate to each other.  For now, the
-    main things to take away from this diagram are as  follows:
-     
-    <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       In  several of the sections that follow, we will
-       present various join queries on the system 
-       catalogs  that display information we need to extend
-       the system.  Looking at this diagram should make
-       some  of  these  join  queries  (which are often
-       three- or four-way joins)  more  understandable,
-       because  you  will  be  able  to  see  that  the
-       columns used in the queries form foreign keys
-       in other tables.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Many  different  features  (tables, columns,
-       functions,  types,  access  methods,  etc.)  are
-       tightly  integrated  in  this  schema.  A simple
-       create command may modify many  of  these  catalogs.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Types and procedures
-       are central to the schema.
-
-       <note>
-	<para>
-	 We  use  the words <firstterm>procedure</firstterm>
-	 and <firstterm>function</firstterm> more or less interchangeably.
-	</para>
-       </note>
-
-       Nearly  every catalog contains some reference to
-       rows in one or both of these tables.   For
-       example,  <productname>PostgreSQL</productname>  frequently  uses type 
-       signatures (e.g.,  of  functions  and  operators)  to
-       identify unique rows of other catalogs.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       There are many columns and relationships that
-       have obvious meanings, but there are many  
-       (particularly  those  that  have  to  do with access
-       methods) that do not.  The relationships between
-       <classname>pg_am</>, <classname>pg_amop</>, <classname>pg_amproc</>, <classname>pg_operator</>, and
-       <classname>pg_opclass</> are particularly hard  to  understand
-       and  will  be described in depth (in <xref linkend="xindex">)
-       after we have discussed basic extensions.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/features.sgml b/doc/src/sgml/features.sgml
deleted file mode 100644
index b023225a158..00000000000
--- a/doc/src/sgml/features.sgml
+++ /dev/null
@@ -1,1844 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.2 2002/06/19 06:11:36 thomas Exp $
--->
-
- <appendix id="features">
-  <title>SQL99 Feature List</title>
-
-  <sect1 id="features-sql99">
-   <title>Supported Features</title>
-
-   <para>
-    <acronym>SQL92</acronym> defined three feature sets for
-    compliance: basic, intermediate, and advanced. Most database
-    products claiming <acronym>SQL</acronym> standards compliance were
-    compliant at only the basic level, since the entire set of
-    intermediate and advanced features was either too voluminous or in
-    conflict with legacy behaviors.
-   </para>
-
-   <para>
-    <acronym>SQL99</acronym> defines a large set of individual
-    features rather than the ineffectively broad three levels found in
-    <acronym>SQL92</acronym>. We provide a list of supported features,
-    followed by a list of the features defined in SQL99 which are not
-    yet supported in PostgreSQL.
-   </para>
-
-   <para>
-    <informaltable>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Identifier</entry>
-        <entry>Description</entry>
-        <entry>Comment</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>E011</entry>
-        <entry>Numeric data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E011-01</entry>
-        <entry>INTEGER and SMALLINT data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E011-02</entry>
-        <entry>REAL, DOUBLE PRECISON, and FLOAT data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E011-03</entry>
-        <entry>DECIMAL and NUMERIC data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E011-04</entry>
-        <entry>Arithmetic operators</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E011-05</entry>
-        <entry>Numeric comparison</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E011-06</entry>
-        <entry>Implicit casting among the numeric data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021</entry>
-        <entry>Character data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-01</entry>
-        <entry>CHARACTER data type</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-02</entry>
-        <entry>CHARACTER VARYING data type</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-03</entry>
-        <entry>Character literals</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-04</entry>
-        <entry>CHARACTER_LENGTH function</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-05</entry>
-        <entry>OCTET_LENGTH function</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-06</entry>
-        <entry>SUBSTRING function</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-07</entry>
-        <entry>Character concatenation</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-08</entry>
-        <entry>UPPER and LOWER functions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-09</entry>
-        <entry>TRIM function</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-10</entry>
-        <entry>Implicit casting among the character data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E021-11</entry>
-        <entry>POSITION function</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E011-12</entry>
-        <entry>Character comparison</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E031</entry>
-        <entry>Identifiers</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E031-01</entry>
-        <entry>Delimited identifiers</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E031-02</entry>
-        <entry>Lower case identifiers</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E031-03</entry>
-        <entry>Trailing underscore</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051</entry>
-        <entry>Basic query specification</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051-01</entry>
-        <entry>SELECT DISTINCT</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051-02</entry>
-        <entry>GROUP BY clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051-04</entry>
-        <entry>GROUP BY can contain columns not in &lt;select list&gt;</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051-05</entry>
-        <entry>Select list items can be renamed</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051-06</entry>
-        <entry>HAVING clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051-07</entry>
-        <entry>Qualified * in select list</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051-08</entry>
-        <entry>Correlation names in the FROM clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E051-09</entry>
-        <entry>Rename columns in the FROM clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061</entry>
-        <entry>Basic predicates and search conditions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-01</entry>
-        <entry>Comparison predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-02</entry>
-        <entry>BETWEEN predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-03</entry>
-        <entry>IN predicate with list of values</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-04</entry>
-        <entry>LIKE predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-05</entry>
-        <entry>LIKE predicate ESCAPE clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-06</entry>
-        <entry>NULL predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-07</entry>
-        <entry>Quantified comparison predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-08</entry>
-        <entry>EXISTS predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-09</entry>
-        <entry>Subqueries in comparison predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-11</entry>
-        <entry>Subqueries in IN predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-12</entry>
-        <entry>Subqueries in quantified comparison predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-13</entry>
-        <entry>Correlated subqueries</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E061-14</entry>
-        <entry>Search condition</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E071</entry>
-        <entry>Basic query expressions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E071-01</entry>
-        <entry>UNION DISTINCT table operator</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E071-02</entry>
-        <entry>UNION ALL table operator</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E071-03</entry>
-        <entry>EXCEPT DISTINCT table operator</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E071-05</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>Table operators in subqueries</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E081</entry>
-        <entry>Basic Privileges</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E081-01</entry>
-        <entry>SELECT privilege</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E081-02</entry>
-        <entry>DELETE privilege</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E081-03</entry>
-        <entry>INSERT privilege at the table level</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E081-04</entry>
-        <entry>UPDATE privilege at the table level</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E081-06</entry>
-        <entry>REFERENCES privilege at the table level</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E081-08</entry>
-        <entry>WITH GRANT OPTION</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E091</entry>
-        <entry>Set functions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E091-01</entry>
-        <entry>AVG</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E091-02</entry>
-        <entry>COUNT</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E091-03</entry>
-        <entry>MAX</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E091-04</entry>
-        <entry>MIN</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E091-05</entry>
-        <entry>SUM</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E091-06</entry>
-        <entry>ALL quantifier</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E091-07</entry>
-        <entry>DISTINCT quantifier</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E101</entry>
-        <entry>Basic data manipulation</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E101-01</entry>
-        <entry>INSERT statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E101-03</entry>
-        <entry>Searched UPDATE statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E101-04</entry>
-        <entry>Searched DELETE statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E111</entry>
-        <entry>Single row SELECT statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E121</entry>
-        <entry>Basic cursor support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E121-01</entry>
-        <entry>DECLARE CURSOR</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E121-02</entry>
-        <entry>ORDER BY columns need not be in select list</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E121-03</entry>
-        <entry>Value expressions in ORDER BY clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E121-04</entry>
-        <entry>OPEN statement</entry>
-        <entry>(cursor)</entry>
-       </row>
-       <row>
-        <entry>E121-06</entry>
-        <entry>Positioned UPDATE statement</entry>
-        <entry>(cursor)</entry>
-       </row>
-       <row>
-        <entry>E121-07</entry>
-        <entry>Positioned DELETE statement</entry>
-        <entry>(cursor)</entry>
-       </row>
-       <row>
-        <entry>E121-08</entry>
-        <entry>CLOSE statement</entry>
-        <entry>(cursor)</entry>
-       </row>
-       <row>
-        <entry>E121-10</entry>
-        <entry>FETCH statement implicit NEXT</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E131</entry>
-        <entry>Null value support (nulls in lieu of values)</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E141</entry>
-        <entry>Basic integrity constraints</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E141-01</entry>
-        <entry>NOT NULL constraints</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E141-02</entry>
-        <entry>UNIQUE constraints of NOT NULL columns</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E141-03</entry>
-        <entry>PRIMARY KEY constraints</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E141-04</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>CHECK constraints</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E141-07</entry>
-        <entry>Column defaults</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E141-08</entry>
-        <entry>NOT NULL inferred on PRIMARY KEY</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E141-10</entry>
-        <entry>Names in a foreign key can be specified in any order</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E151</entry>
-        <entry>Transaction support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E151-01</entry>
-        <entry>COMMIT statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E151-02</entry>
-        <entry>ROLLBACK statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E152</entry>
-        <entry>Basic SET TRANSACTION statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E152-01</entry>
-        <entry>SET TRANSACTION statement: ISOLATION LEVEL SERIALIZABLE
-         clause</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E153</entry>
-        <entry>Updatable queries with subqueries</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E161</entry>
-        <entry>SQL comments using leading double minus</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F031</entry>
-        <entry>Basic schema manipulation</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F031-01</entry>
-        <entry>CREATE TABLE statement to create persistent base
-         tables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F031-02</entry>
-        <entry>CREATE VIEW statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F031-03</entry>
-        <entry>GRANT statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F031-04</entry>
-        <entry>ALTER TABLE statement COLUMN clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F031-13</entry>
-        <entry>DROP TABLE statement clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F031-16</entry>
-        <entry>DROP VIEW statement RESTRICT clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F031-19</entry>
-        <entry>REVOKE statement RESTRICT clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F041</entry>
-        <entry>Basic joined table</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F041-01</entry>
-        <entry>Inner join (but not necessarily the INNER keyword)</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F041-02</entry>
-        <entry>INNER keyword</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F041-03</entry>
-        <entry>LEFT OUTER JOIN</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F041-04</entry>
-        <entry>RIGHT OUTER JOIN</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F041-05</entry>
-        <entry>Outer joins can be nested</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F041-07</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>All comparison operators are supported
-         (rather than just =)</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F051</entry>
-        <entry>Basic date and time</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F051-01</entry>
-        <entry>DATE data type (including support of DATE literal)</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F051-02</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>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>Comparison predicate on DATE TIMESTAMP data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F051-05</entry>
-        <entry>Explicit CAST between datetime types and character types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F051-06</entry>
-        <entry>CURRENT_DATE</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F051-07</entry>
-        <entry>LOCALTIME</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F051-08</entry>
-        <entry>LOCALTIMESTAMP</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F081</entry>
-        <entry>UNION and EXCEPT in views</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F131</entry>
-        <entry>Grouped operations</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F131-01</entry>
-        <entry>WHERE, GROUP BY and HAVING clauses supported in queries
-         with grouped views</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F131-02</entry>
-        <entry>Multiple tables supported in queries with grouped
-         views</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F131-03</entry>
-        <entry>Set functions supported in queries with grouped views</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F131-04</entry>
-        <entry>Subqueries with GROUP BY and HAVING clauses and grouped
-         views</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F131-05</entry>
-        <entry>Single row SELECT with GROUP BY and HAVING clauses and
-         grouped views</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F181</entry>
-        <entry>Multiple module support</entry>
-        <entry>Allow separate compilation modules in ecpg</entry>
-       </row>
-       <row>
-        <entry>F201</entry>
-        <entry>CAST function</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F221</entry>
-        <entry>Explicit defaults</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F261</entry>
-        <entry>CASE expression</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F261-01</entry>
-        <entry>Simple CASE</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F261-02</entry>
-        <entry>Searched CASE</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F261-03</entry>
-        <entry>NULLIF</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F261-04</entry>
-        <entry>COALESCE</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F311</entry>
-        <entry>Schema definition statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F311-01</entry>
-        <entry>CREATE SCHEMA</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F311-02</entry>
-        <entry>CREATE TABLE for persistent base tables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F311-03</entry>
-        <entry>CREATE VIEW</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F311-04</entry>
-        <entry>CREATE VIEW: WITH CHECK OPTION</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F311-05</entry>
-        <entry>GRANT statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F471</entry>
-        <entry>Scalar subquery values</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F481</entry>
-        <entry>Expanded NULL predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S011</entry>
-        <entry>Distinct data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T321</entry>
-        <entry>Basic SQL-invoked routines</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T321-01</entry>
-        <entry>User-defined functions with no overloading</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T321-03</entry>
-        <entry>Function invocation</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T321-05</entry>
-        <entry>RETURN statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F032</entry>
-        <entry>CASCADE drop behavior</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F034</entry>
-        <entry>Extended REVOKE statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F034-01</entry>
-        <entry>REVOKE statement performed by other than the owner of a
-         schema object</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F034-02</entry>
-        <entry>REVOKE statement: GRANT OPTION FOR clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F034-03</entry>
-        <entry>REVOKE statement to revoke a privilege that the grantee
-         has WITH GRANT OPTION</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F052</entry>
-        <entry>Intervals and datetime arithmetic</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F111</entry>
-        <entry>Isolation levels other than SERIALIZABLE</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F111-02</entry>
-        <entry>READ COMMITTED isolation level</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F171</entry>
-        <entry>Multiple schemas per user</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F191</entry>
-        <entry>Referential delete actions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F222</entry>
-        <entry>INSERT statement: DEFAULT VALUES clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F271</entry>
-        <entry>Compound character literals</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F281</entry>
-        <entry>LIKE enhancements</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F291</entry>
-        <entry>UNIQUE predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F302</entry>
-        <entry>INTERSECT table operator</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F302-02</entry>
-        <entry>INTERSECT ALL table operator</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F304</entry>
-        <entry>EXCEPT ALL table operator</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F321</entry>
-        <entry>User authorization</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F341</entry>
-        <entry>Usage tables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F361</entry>
-        <entry>Subprogram support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F381-01</entry>
-        <entry>ALTER TABLE statement: ALTER COLUMN clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F381-02</entry>
-        <entry>ALTER TABLE statement: ADD CONSTRAINT clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F381-03</entry>
-        <entry>ALTER TABLE statement: DROP CONSTRAINT clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F391</entry>
-        <entry>Long identifiers</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F401</entry>
-        <entry>Extended joined table</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F401-01</entry>
-        <entry>NATURAL JOIN</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F401-02</entry>
-        <entry>FULL OUTER JOIN</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F401-03</entry>
-        <entry>UNION JOIN</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F401-04</entry>
-        <entry>CROSS JOIN</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F411</entry>
-        <entry>Time zone specification</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F431</entry>
-        <entry>Read-only scrollable cursors</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F431-01</entry>
-        <entry>FETCH with explicit NEXT</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F431-02</entry>
-        <entry>FETCH FIRST</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F431-03</entry>
-        <entry>FETCH LAST</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F431-04</entry>
-        <entry>FETCH PRIOR</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F431-05</entry>
-        <entry>FETCH ABSOLUTE</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F431-06</entry>
-        <entry>FETCH RELATIVE</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F461</entry>
-        <entry>Named character sets</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F491</entry>
-        <entry>Constraint management</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F511</entry>
-        <entry>BIT data type</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F531</entry>
-        <entry>Temporary tables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F555</entry>
-        <entry>Enhanced seconds precision</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F561</entry>
-        <entry>Full value expressions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F571</entry>
-        <entry>Truth value tests</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F591</entry>
-        <entry>Derived tables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F611</entry>
-        <entry>Indicator data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F641</entry>
-        <entry>Row and table constructors</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F651</entry>
-        <entry>Catalog name qualifiers</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F661</entry>
-        <entry>Simple tables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F701</entry>
-        <entry>Referential update actions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F741</entry>
-        <entry>Referential MATCH types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F761</entry>
-        <entry>Session management</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F771</entry>
-        <entry>Connection management</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F791</entry>
-        <entry>Insensitive cursors</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F831</entry>
-        <entry>Full cursor update</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F831-01</entry>
-        <entry>Updateable scrollable cursors</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F831-02</entry>
-        <entry>Updateable ordered cursors</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S071</entry>
-        <entry>SQL paths in function and type name resolution</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S091</entry>
-        <entry>Basic array support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S091-01</entry>
-        <entry>Arrays of built-in data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S092</entry>
-        <entry>Arrays of user-defined types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S201</entry>
-        <entry>SQL routines on arrays</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S201-01</entry>
-        <entry>Array parameters</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S201-02</entry>
-        <entry>Array as result type of functions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T031</entry>
-        <entry>BOOLEAN data type</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T141</entry>
-        <entry>SIMILAR predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T151</entry>
-        <entry>DISTINCT predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T171</entry>
-        <entry>LIKE clause in table definition</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T191</entry>
-        <entry>Referential action RESTRICT</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T201</entry>
-        <entry>Comparable data types for referential constraints</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211</entry>
-        <entry>Basic trigger capability</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211-01</entry>
-        <entry>Triggers activated on UPDATE, INSERT, or DELETE of one
-         base table</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211-02</entry>
-        <entry>BEFORE triggers</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211-03</entry>
-        <entry>AFTER triggers</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211-04</entry>
-        <entry>FOR EACH ROW triggers</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211-08</entry>
-        <entry>Multiple triggers for the same the event are executed in
-         the order in which they were created</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T212</entry>
-        <entry>Enhanced trigger capability</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T231</entry>
-        <entry>SENSITIVE cursors</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T241</entry>
-        <entry>START TRANSACTION statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T251</entry>
-        <entry>SET TRANSACTION statement: LOCAL option</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T312</entry>
-        <entry>OVERLAY function</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T322</entry>
-        <entry>Overloading of SQL-invoked functions and procedures</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T323</entry>
-        <entry>Explicit security for external routines</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T351</entry>
-        <entry>Bracketed SQL comments (/*...*/ comments)</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T401</entry>
-        <entry>INSERT into a cursor</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T441</entry>
-        <entry>ABS and MOD functions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T461</entry>
-        <entry>Symmetric BETWEEN predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T501</entry>
-        <entry>Enhanced EXISTS predicate</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T551</entry>
-        <entry>Optional key words for default syntax</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T571</entry>
-        <entry>Array-returning external SQL-invoked functions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T581</entry>
-        <entry>Regular expression substring function</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T591</entry>
-        <entry>UNIQUE constraints of possibly null columns</entry>
-        <entry></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </informaltable>
-   </para>
-  </sect1>
-
-  <sect1 id="unsupported-features-sql99">
-   <title>Unsupported Features</title>
-
-   <para>
-    The following features defined in <acronym>SQL99</acronym> are not
-    implemented in the current release of
-    <productname>PostgreSQL</productname>. In a few cases, equivalent
-    functionality is available.
-
-    <informaltable>
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Identifier</entry>
-        <entry>Description</entry>
-        <entry>Comment</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry>E081-05</entry>
-        <entry>UPDATE privilege at the column level</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E081-07</entry>
-        <entry>REFERENCES privilege at the column level</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E121-17</entry>
-        <entry>WITH HOLD cursors</entry>
-        <entry>Cursor stays open across transactions</entry>
-       </row>
-       <row>
-        <entry>E152-02</entry>
-        <entry>SET TRANSACTION statement: READ ONLY and READ WRITE
-         clauses</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E171</entry>
-        <entry>SQLSTATE support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>E182</entry>
-        <entry>Module language</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F021</entry>
-        <entry>Basic information schema</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F021-01</entry>
-        <entry>COLUMNS view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F021-02</entry>
-        <entry>TABLES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F021-03</entry>
-        <entry>VIEWS view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F021-04</entry>
-        <entry>TABLE_CONSTRAINTS view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F021-05</entry>
-        <entry>REFERENTIAL_CONSTRAINTS view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F021-06</entry>
-        <entry>CHECK_CONSTRAINTS view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F033</entry>
-        <entry>ALTER TABLE statement: DROP COLUMN clause</entry>
-        <entry>Syntax accepted</entry>
-       </row>
-       <row>
-        <entry>F111-01</entry>
-        <entry>READ UNCOMMITTED isolation level</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F111-03</entry>
-        <entry>REPEATABLE READ isolation level</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F121</entry>
-        <entry>Basic diagnostics management</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F121-01</entry>
-        <entry>GET DIAGNOSTICS statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F121-02</entry>
-        <entry>SET TRANSACTION statement: DIAGNOSTICS SIZE clause</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F231</entry>
-        <entry>Privilege Tables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F231-01</entry>
-        <entry>TABLE_PRIVILEGES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F231-02</entry>
-        <entry>COLUMN_PRIVILEGES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F231-03</entry>
-        <entry>USAGE_PRIVILEGES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F251</entry>
-        <entry>Domain support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F301</entry>
-        <entry>CORRESPONDING in query expressions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F302-01</entry>
-        <entry>INTERSECT DISTINCT table operator</entry>
-        <entry>Syntax accepted</entry>
-       </row>
-       <row>
-        <entry>F381</entry>
-        <entry>Extended schema manipulation</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F421</entry>
-        <entry>National character</entry>
-        <entry>Syntax accepted</entry>
-       </row>
-       <row>
-        <entry>F441</entry>
-        <entry>Extended set function support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F451</entry>
-        <entry>Character set definition</entry>
-        <entry>Alternate implementation</entry>
-       </row>
-       <row>
-        <entry>F501</entry>
-        <entry>Features and conformance views</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F501-01</entry>
-        <entry>SQL_FEATURES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F501-02</entry>
-        <entry>SQL_SIZING view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F501-03</entry>
-        <entry>SQL_LANGUAGES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F502</entry>
-        <entry>Enhanced documentation tables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F502-01</entry>
-        <entry>SQL_SIZING_PROFILES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F502-02</entry>
-        <entry>SQL_IMPLEMENTATION_INFO view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F502-03</entry>
-        <entry>SQL_PACKAGES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F521</entry>
-        <entry>Assertions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F671</entry>
-        <entry>Subqueries in CHECK</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F691</entry>
-        <entry>Collation and translation</entry>
-        <entry>Alternate implementation</entry>
-       </row>
-       <row>
-        <entry>F711</entry>
-        <entry>ALTER domain</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F721</entry>
-        <entry>Deferrable constraints</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F731</entry>
-        <entry>INSERT column privileges</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F751</entry>
-        <entry>View CHECK enhancements</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F781</entry>
-        <entry>Self-referencing operations</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F801</entry>
-        <entry>Full set function</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F811</entry>
-        <entry>Extended flagging</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F812</entry>
-        <entry>Basic flagging</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F813</entry>
-        <entry>Extended flagging for "Core SQL Flagging" and "Catalog
-         Lookup" only</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>F821</entry>
-        <entry>Local table references</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S011-01</entry>
-        <entry>USER_DEFINED_TYPES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S023</entry>
-        <entry>Basic structured types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S024</entry>
-        <entry>Enhanced structured types</entry>
-        <entry>Alternate implementation</entry>
-       </row>
-       <row>
-        <entry>S041</entry>
-        <entry>Basic reference types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S043</entry>
-        <entry>Enhanced reference types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S051</entry>
-        <entry>Create table of type</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S081</entry>
-        <entry>Subtables</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S091-02</entry>
-        <entry>Arrays of distinct types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S091-03</entry>
-        <entry>Array expressions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S094</entry>
-        <entry>Arrays of reference types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S111</entry>
-        <entry>ONLY in query expressions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S151</entry>
-        <entry>Type predicate</entry>
-        <entry>IS OF (type list)</entry>
-       </row>
-       <row>
-        <entry>S161</entry>
-        <entry>Subtype treatment</entry>
-        <entry>TREAT(expr AS type)</entry>
-       </row>
-       <row>
-        <entry>S211</entry>
-        <entry>User-defined cast functions</entry>
-        <entry>CREATE CAST(type AS type) WITH</entry>
-       </row>
-       <row>
-        <entry>S231</entry>
-        <entry>Structured type locators</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S232</entry>
-        <entry>Array locators</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S241</entry>
-        <entry>Transform functions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>S251</entry>
-        <entry>User-defined orderings</entry>
-        <entry>CREATE ORDERING FOR</entry>
-       </row>
-       <row>
-        <entry>S261</entry>
-        <entry>Specific type method</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T011</entry>
-        <entry>Timestamp in Information Schema</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T041</entry>
-        <entry>Basic LOB data type support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T041-01</entry>
-        <entry>BLOB data type</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T041-02</entry>
-        <entry>CLOB data type</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T041-03</entry>
-        <entry>POSITION, LENGTH, LOWER, TRIM, UPPER, and SUBSTRING
-         functions for LOB data types</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T041-04</entry>
-        <entry>Concatenation of LOB data types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T041-05</entry>
-        <entry>LOB locator: non-holdable</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T042</entry>
-        <entry>Extended LOB data type support</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T051</entry>
-        <entry>Row types</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T111</entry>
-        <entry>Updatable joins, unions, and columns</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T121</entry>
-        <entry>WITH (excluding RECURSIVE) in query expression</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T131</entry>
-        <entry>Recursive query</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211-05</entry>
-        <entry>Ability to specify a search condition that must be true
-         before the trigger is invoked</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211-06</entry>
-        <entry>Support for run-time rules for the interaction of triggers
-         and constraints</entry> 
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T211-07</entry>
-        <entry>TRIGGER privilege</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T261</entry>
-        <entry>Chained transactions</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T271</entry>
-        <entry>Savepoints</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T281</entry>
-        <entry>SELECT privilege with column granularity</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T301</entry>
-        <entry>Functional Dependencies</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T321-02</entry>
-        <entry>User-defined stored procedures with no overloading</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T321-04</entry>
-        <entry>CALL statement</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T321-06</entry>
-        <entry>ROUTINES view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T321-07</entry>
-        <entry>PARAMETERS view</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T331</entry>
-        <entry>Basic roles</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T332</entry>
-        <entry>Extended roles</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T411</entry>
-        <entry>UPDATE statement: SET ROW option</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T431</entry>
-        <entry>CUBE and ROLLUP operations</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T471</entry>
-        <entry>Result sets return value</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T491</entry>
-        <entry>LATERAL derived table</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T511</entry>
-        <entry>Transaction counts</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T541</entry>
-        <entry>Updatable table references</entry>
-        <entry>?</entry>
-       </row>
-       <row>
-        <entry>T561</entry>
-        <entry>Holdable locators</entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry>T601</entry>
-        <entry>Local cursor references</entry>
-        <entry></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </informaltable>
-   </para>
-  </sect1>
- </appendix>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml
deleted file mode 100644
index d8c5998fb84..00000000000
--- a/doc/src/sgml/filelist.sgml
+++ /dev/null
@@ -1,112 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/filelist.sgml,v 1.19 2002/06/15 02:59:55 thomas Exp $ -->
-
-<!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">
-<!entity y2k        SYSTEM "y2k.sgml">
-
-<!entity bookindex  SYSTEM "bookindex.sgml">
-<!entity setindex   SYSTEM "setindex.sgml">
-
-<!-- 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 datetime   SYSTEM "datetime.sgml">
-<!entity features   SYSTEM "features.sgml">
-<!entity func       SYSTEM "func.sgml">
-<!entity indices    SYSTEM "indices.sgml">
-<!entity inherit    SYSTEM "inherit.sgml">
-<!entity keywords   SYSTEM "keywords.sgml">
-<!entity manage     SYSTEM "manage.sgml">
-<!entity mvcc       SYSTEM "mvcc.sgml">
-<!entity perform    SYSTEM "perform.sgml">
-<!entity queries    SYSTEM "queries.sgml">
-<!entity syntax     SYSTEM "syntax.sgml">
-<!entity typeconv   SYSTEM "typeconv.sgml">
-
-<!-- reference pages -->
-<!entity % allfiles   SYSTEM "ref/allfiles.sgml">
-%allfiles;
-
-<!-- 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 installation  SYSTEM "installation.sgml">
-<!entity installw      SYSTEM "install-win32.sgml">
-<!entity maintenance   SYSTEM "maintenance.sgml">
-<!entity manage-ag     SYSTEM "manage-ag.sgml">
-<!entity monitoring    SYSTEM "monitoring.sgml">
-<!entity recovery      SYSTEM "recovery.sgml">
-<!entity regress       SYSTEM "regress.sgml">
-<!entity release       SYSTEM "release.sgml">
-<!entity runtime       SYSTEM "runtime.sgml">
-<!entity user-manag    SYSTEM "user-manag.sgml">
-<!entity wal           SYSTEM "wal.sgml">
-
-<!-- programmer's guide -->
-<!entity arch-pg    SYSTEM "arch-pg.sgml">
-<!entity dfunc      SYSTEM "dfunc.sgml">
-<!entity ecpg       SYSTEM "ecpg.sgml">
-<!entity extend     SYSTEM "extend.sgml">
-<!entity func-ref   SYSTEM "func-ref.sgml">
-<!entity gist       SYSTEM "gist.sgml">
-<!entity indexcost  SYSTEM "indexcost.sgml">
-<!entity jdbc       SYSTEM "jdbc.sgml">
-<!entity libpgeasy  SYSTEM "libpgeasy.sgml">
-<!entity libpq      SYSTEM "libpq.sgml">
-<!entity libpqpp    SYSTEM "libpq++.sgml">
-<!entity libpgtcl   SYSTEM "libpgtcl.sgml">
-<!entity pygresql   SYSTEM "pygresql.sgml">
-<!entity lobj       SYSTEM "lobj.sgml">
-<!entity odbc       SYSTEM "odbc.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 "plsql.sgml">
-<!entity pltcl      SYSTEM "pltcl.sgml">
-
-<!-- developer's guide -->
-<!entity arch-dev   SYSTEM "arch-dev.sgml">
-<!entity biblio     SYSTEM "biblio.sgml">
-<!entity bki        SYSTEM "bki.sgml">
-<!entity catalogs   SYSTEM "catalogs.sgml">
-<!entity compiler   SYSTEM "compiler.sgml">
-<!entity contacts   SYSTEM "contacts.sgml">
-<!entity cvs        SYSTEM "cvs.sgml">
-<!entity docguide   SYSTEM "docguide.sgml">
-<!entity geqo       SYSTEM "geqo.sgml">
-<!entity index      SYSTEM "index.sgml">
-<!entity page       SYSTEM "page.sgml">
-<!entity protocol   SYSTEM "protocol.sgml">
-<!entity sources    SYSTEM "sources.sgml">
-<!entity nls        SYSTEM "nls.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">
diff --git a/doc/src/sgml/fixrtf b/doc/src/sgml/fixrtf
deleted file mode 100755
index 2c1172408c8..00000000000
--- a/doc/src/sgml/fixrtf
+++ /dev/null
@@ -1,43 +0,0 @@
-#!/bin/sh
-# 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/src/sgml/func-ref.sgml b/doc/src/sgml/func-ref.sgml
deleted file mode 100644
index 129a9d2473a..00000000000
--- a/doc/src/sgml/func-ref.sgml
+++ /dev/null
@@ -1,19 +0,0 @@
-<Chapter Id="func-ref">
-<Title>Functions</Title>
-
-<Abstract>
-<Para>
-Reference information for user-callable functions.
-</Para>
-</Abstract>
-
-<Note>
-<Para>
-This section needs to be written. Volunteers?
-</Para>
-</Note>
-
-<Para>
-</Para>
-
-</Chapter>
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
deleted file mode 100644
index 4c30789eff4..00000000000
--- a/doc/src/sgml/func.sgml
+++ /dev/null
@@ -1,5182 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.103 2002/06/15 20:03:51 momjian Exp $
-PostgreSQL documentation
--->
-
- <chapter id="functions">
-  <title>Functions and Operators</title>
-
-  <indexterm zone="functions">
-   <primary>functions</primary>
-  </indexterm>
-
-  <indexterm zone="functions">
-   <primary>operators</primary>
-  </indexterm>
-
-  <para>
-   <productname>PostgreSQL</productname> provides a large number of
-   functions and operators for the built-in data types.  Users can also
-   define their own functions and operators, as described in the
-   <citetitle>Programmer's Guide</citetitle>.  The
-   <application>psql</application> commands <command>\df</command> and
-   <command>\do</command> can be used to show the list of all actually
-   available functions and operators, respectively.
-  </para>
-
-  <para>
-   If you are concerned about portability then take 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>RDBMS</acronym> products, and in many cases this
-   functionality is compatible and consistent between various products.
-  </para>
-
-
-  <sect1 id="functions-logical">
-   <title>Logical Operators</title>
-
-   <indexterm zone="functions-logical">
-    <primary>operators</primary>
-    <secondary>logical</secondary>
-   </indexterm>
-
-   <indexterm>
-    <primary>Boolean</primary>
-    <secondary>operators</secondary>
-    <see>operators, logical</see>
-   </indexterm>
-
-   <para>
-    The usual logical operators are available:
-
-    <indexterm>
-     <primary>and</primary>
-     <secondary>operator</secondary>
-    </indexterm>
-
-    <indexterm>
-     <primary>or</primary>
-     <secondary>operator</secondary>
-    </indexterm>
-
-    <indexterm>
-     <primary>not</primary>
-     <secondary>operator</secondary>
-    </indexterm>
-
-    <simplelist>
-     <member>AND</member>
-     <member>OR</member>
-     <member>NOT</member>
-    </simplelist>
-
-    <acronym>SQL</acronym> uses a three-valued Boolean logic where NULL 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>
-  </sect1>
-
-  <sect1 id="functions-comparison">
-   <title>Comparison Operators</title>
-
-   <indexterm zone="functions-comparison">
-    <primary>comparison</primary>
-    <secondary>operators</secondary>
-   </indexterm>
-
-   <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 data types where this
-    makes sense.  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>able> &lt;= <replaceable>y</replaceable>
-    </synopsis>
-    Similarly,
-    <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>able> &gt; <replaceable>y</replaceable>
-    </synopsis>
-    There is no difference between the two respective forms apart from
-    the <acronym>CPU</acronym> cycles required to rewrite the first one
-    into the second one internally.
-   </para>
-
-   <para>
-    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 less standard, constructs
-    <synopsis>
-<replaceable>expression</replaceable> ISNULL
-<replaceable>expression</replaceable> NOTNULL
-    </synopsis>
-   </para>
-
-   <para>
-    Do <emphasis>not</emphasis> write
-    <literal><replaceable>expression</replaceable> = NULL</literal>
-    because NULL is not <quote>equal to</quote> NULL.  (NULL represents
-    an unknown value, and it is not known whether two unknown values are
-    equal.)
-   </para>
-
-   <para>
-    Some applications may (incorrectly) require that
-    <literal><replaceable>expression</replaceable> = NULL</literal>
-    returns true if <replaceable>expression</replaceable> evaluates to
-    the NULL value.  To support these applications, the run-time option
-    <varname>transform_null_equals</varname> can be turned on (e.g.,
-    <literal>SET transform_null_equals TO ON;</literal>).
-    <productname>PostgreSQL</productname> will then convert
-    <literal>x = NULL</literal> clauses to
-    <literal>x IS NULL</literal>.  This was 
-    the default behavior in releases 6.5 through 7.1.
-   </para>
-
-   <para>
-    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 are similar to <literal>IS NULL</literal> in that they will
-    always return TRUE or FALSE, never NULL, even when the operand is NULL.
-    A NULL input is treated as the logical value UNKNOWN.
-   </para>
-  </sect1>
-
-  <sect1 id="functions-math">
-   <title>Mathematical Functions and Operators</title>
-
-   <para>
-    Mathematical operators are provided for many
-    <productname>PostgreSQL</productname> types. For types without
-    common mathematical conventions for all possible permutations 
-    (e.g. date/time types) we
-    describe the actual behavior in subsequent sections.
-   </para>
-
-   <table>
-    <title>Mathematical Operators</title>
-
-    <tgroup cols="4">
-     <thead>
-      <row>
-       <entry>Name</entry>
-       <entry>Description</entry>
-       <entry>Example</entry>
-       <entry>Result</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry> <literal>+</literal> </entry>
-       <entry>Addition</entry>
-       <entry>2 + 3</entry>
-       <entry>5</entry>
-      </row>
-
-      <row>
-       <entry> <literal>-</literal> </entry>
-       <entry>Subtraction</entry>
-       <entry>2 - 3</entry>
-       <entry>-1</entry>
-      </row>
-
-      <row>
-       <entry> <literal>*</literal> </entry>
-       <entry>Multiplication</entry>
-       <entry>2 * 3</entry>
-       <entry>6</entry>
-      </row>
-
-      <row>
-       <entry> <literal>/</literal> </entry>
-       <entry>Division (integer division truncates results)</entry>
-       <entry>4 / 2</entry>
-       <entry>2</entry>
-      </row>
-
-      <row>
-       <entry> <literal>%</literal> </entry>
-       <entry>Modulo (remainder)</entry>
-       <entry>5 % 4</entry>
-       <entry>1</entry>
-      </row>
-
-      <row>
-       <entry> <literal>^</literal> </entry>
-       <entry>Exponentiation</entry>
-       <entry>2.0 ^ 3.0</entry>
-       <entry>8</entry>
-      </row>
-
-      <row>
-       <entry> <literal>|/</literal> </entry>
-       <entry>Square root</entry>
-       <entry>|/ 25.0</entry>
-       <entry>5</entry>
-      </row>
-
-      <row>
-       <entry> <literal>||/</literal> </entry>
-       <entry>Cube root</entry>
-       <entry>||/ 27.0</entry>
-       <entry>3</entry>
-      </row>
-
-      <row>
-       <entry> <literal>!</literal> </entry>
-       <entry>Factorial</entry>
-       <entry>5 !</entry>
-       <entry>120</entry>
-      </row>
-
-      <row>
-       <entry> <literal>!!</literal> </entry>
-       <entry>Factorial (prefix operator)</entry>
-       <entry>!! 5</entry>
-       <entry>120</entry>
-      </row>
-
-      <row>
-       <entry> <literal>@</literal> </entry>
-       <entry>Absolute value</entry>
-       <entry>@ -5.0</entry>
-       <entry>5</entry>
-      </row>
-
-      <row>
-       <entry> <literal>&amp;</literal> </entry>
-       <entry>Binary AND</entry>
-       <entry>91 & 15</entry>
-       <entry>11</entry>
-      </row>
-
-      <row>
-       <entry> <literal>|</literal> </entry>
-       <entry>Binary OR</entry>
-       <entry>32 | 3</entry>
-       <entry>35</entry>
-      </row>
-
-      <row>
-       <entry> <literal>#</literal> </entry>
-       <entry>Binary XOR</entry>
-       <entry>17 # 5</entry>
-       <entry>20</entry>
-      </row>
-
-      <row>
-       <entry> <literal>~</literal> </entry>
-       <entry>Binary NOT</entry>
-       <entry>~1</entry>
-       <entry>-2</entry>
-      </row>
-
-      <row>
-       <entry> &lt;&lt; </entry>
-       <entry>Binary shift left</entry>
-       <entry>1 &lt;&lt; 4</entry>
-       <entry>16</entry>
-      </row>
-
-      <row>
-       <entry> &gt;&gt; </entry>
-       <entry>Binary shift right</entry>
-       <entry>8 &gt;&gt; 2</entry>
-       <entry>2</entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    The <quote>binary</quote> operators are also available for the bit
-    string types <type>BIT</type> and <type>BIT VARYING</type>.
-
-    <table>
-     <title>Bit String Binary Operators</title>
-
-     <tgroup cols="2">
-      <thead>
-       <row>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry>B'10001' & B'01101'</entry>
-        <entry>00001</entry>
-       </row>
-       <row>
-        <entry>B'10001' | B'01101'</entry>
-        <entry>11101</entry>
-       </row>
-       <row>
-        <entry>B'10001' # B'01101'</entry>
-        <entry>11110</entry>
-       </row>
-       <row>
-        <entry>~ B'10001'</entry>
-        <entry>01110</entry>
-       </row>
-       <row>
-        <entry>B'10001' << 3</entry>
-        <entry>01000</entry>
-       </row>
-       <row>
-        <entry>B'10001' >> 2</entry>
-        <entry>00100</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    Bit string arguments to <literal>&</literal>, <literal>|</literal>,
-    and <literal>#</literal> must be of equal length.  When bit
-    shifting, the original length of the string is preserved, as shown
-    here.
-   </para>
-
-   <table tocentry="1">
-    <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><function>abs</function>(<replaceable>x</replaceable>)</entry>
-       <entry>(same as x)</entry>
-       <entry>absolute value</entry>
-       <entry><literal>abs(-17.4)</literal></entry>
-       <entry>17.4</entry>
-      </row>
-
-      <row>
-       <entry><function>cbrt</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>cube root</entry>
-       <entry><literal>cbrt(27.0)</literal></entry>
-       <entry>3</entry>
-      </row>
-
-      <row>
-       <entry><function>ceil</function>(<type>numeric</type>)</entry>
-       <entry><type>numeric</type></entry>
-       <entry>smallest integer not less than argument</entry>
-       <entry><literal>ceil(-42.8)</literal></entry>
-       <entry>-42</entry>
-      </row>
-
-      <row>
-       <entry><function>degrees</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>radians to degrees</entry>
-       <entry><literal>degrees(0.5)</literal></entry>
-       <entry>28.6478897565412</entry>
-      </row>
-
-      <row>
-       <entry><function>exp</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>exponential</entry>
-       <entry><literal>exp(1.0)</literal></entry>
-       <entry>2.71828182845905</entry>
-      </row>
-
-      <row>
-       <entry><function>floor</function>(<type>numeric</type>)</entry>
-       <entry><type>numeric</type></entry>
-       <entry>largest integer not greater than argument</entry>
-       <entry><literal>floor(-42.8)</literal></entry>
-       <entry>-43</entry>
-      </row>
-
-      <row>
-       <entry><function>ln</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>natural logarithm</entry>
-       <entry><literal>ln(2.0)</literal></entry>
-       <entry>0.693147180559945</entry>
-      </row>
-
-      <row>
-       <entry><function>log</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>base 10 logarithm</entry>
-       <entry><literal>log(100.0)</literal></entry>
-       <entry>2</entry>
-      </row>
-
-      <row>
-       <entry><function>log</function>(<parameter>b</parameter> <type>numeric</type>,
-        <parameter>x</parameter> <type>numeric</type>)</entry>
-       <entry><type>numeric</type></entry>
-       <entry>logarithm to base <parameter>b</parameter></entry>
-       <entry><literal>log(2.0, 64.0)</literal></entry>
-       <entry>6.0000000000</entry>
-      </row>
-
-      <row>
-       <entry><function>mod</function>(<parameter>y</parameter>,
-        <parameter>x</parameter>)</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>1</entry>
-      </row>
-
-      <row>
-       <entry><function>pi</function>()</entry>
-       <entry><type>dp</type></entry>
-       <entry><quote>Pi</quote> constant</entry>
-       <entry><literal>pi()</literal></entry>
-       <entry>3.14159265358979</entry>
-      </row>
-
-      <row>
-       <entry><function>pow</function>(<parameter>e</parameter> <type>dp</type>,
-        <parameter>n</parameter> <type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>raise a number to exponent <parameter>e</parameter></entry>
-       <entry><literal>pow(9.0, 3.0)</literal></entry>
-       <entry>729</entry>
-      </row>
-
-      <row>
-       <entry><function>radians</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>degrees to radians</entry>
-       <entry><literal>radians(45.0)</literal></entry>
-       <entry>0.785398163397448</entry>
-      </row>
-
-      <row>
-       <entry><function>random</function>()</entry>
-       <entry><type>dp</type></entry>
-       <entry>value between 0.0 to 1.0</entry>
-       <entry><literal>random()</literal></entry>
-       <entry></entry>
-      </row>
-
-      <row>
-       <entry><function>round</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>round to nearest integer</entry>
-       <entry><literal>round(42.4)</literal></entry>
-       <entry>42</entry>
-      </row>
-
-      <row>
-       <entry><function>round</function>(<parameter>v</parameter> <type>numeric</type>, <parameter>s</parameter> <type>integer</type>)</entry>
-       <entry><type>numeric</type></entry>
-       <entry>round to <parameter>s</parameter> decimal places</entry>
-       <entry><literal>round(42.4382, 2)</literal></entry>
-       <entry>42.44</entry>
-      </row>
-<!--
-     <row>
-      <entry><function>setseed</function>(<replaceable>new-seed</replaceable>)</entry>
-      <entry>set seed for subsequent random() calls</entry>
-      <entry><literal>setseed(0.54823)</literal></entry>
-      <entry></entry>
-     </row>
--->
-      <row>
-       <entry><function>sign</function>(<type>numeric</type>)</entry>
-       <entry><type>numeric</type></entry>
-       <entry>sign of the argument (-1, 0, +1)</entry>
-       <entry><literal>sign(-8.4)</literal></entry>
-       <entry>-1</entry>
-      </row>
-
-      <row>
-       <entry><function>sqrt</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>square root</entry>
-       <entry><literal>sqrt(2.0)</literal></entry>
-       <entry>1.4142135623731</entry>
-      </row>
-
-      <row>
-       <entry><function>trunc</function>(<type>dp</type>)</entry>
-       <entry><type>dp</type></entry>
-       <entry>truncate toward zero</entry>
-       <entry><literal>trunc(42.8)</literal></entry>
-       <entry>42</entry>
-      </row>
-
-      <row>
-       <entry><function>trunc</function>(<type>numeric</type>,
-        <parameter>r</parameter>rameter> <type>integer</type>)</entry>
-       <entry><type>numeric</type></entry>
-       <entry>truncate to <parameter>s</parameter> decimal places</entry>
-       <entry><literal>trunc(42.4382, 2)</literal></entry>
-       <entry>42.43</entry>
-      </row>
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    In the table above, <literal>dp</literal> indicates <type>double precision</type>.
-    The functions <function>exp</function>, <function>ln</function>,
-    <function>log</function>, <function>pow</function>,
-    <function>round</function> (1 argument), <function>sqrt</function>,
-    and <function>trunc</function> (1 argument) are also available for
-    the type <type>numeric</type> in place of
-    <type>double precision</type>.
-    Functions returning a <type>numeric</type> result take
-    <type>numeric</type> input arguments, unless otherwise specified.
-    Many of these functions are implemented on top
-    of the host system's C library; accuracy and behavior in boundary cases
-    could therefore vary depending on the host system.
-   </para>
-
-   <table>
-    <title>Trigonometric Functions</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Function</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><function>acos</function>(<replaceable>x</replaceable>)</entry>
-       <entry>inverse cosine</entry>
-      </row>
-
-      <row>
-       <entry><function>asin</function>(<replaceable>x</replaceable>)</entry>
-       <entry>inverse sine</entry>
-      </row>
-
-      <row>
-       <entry><function>atan</function>(<replaceable>x</replaceable>)</entry>
-       <entry>inverse tangent</entry>
-      </row>
-
-      <row>
-       <entry><function>atan2</function>(<replaceable>x</replaceable>,
-        <replaceable>y</replaceable>)</entry>
-       <entry>inverse tangent of
-        <replaceable>a</replaceable>aceable>/<replaceable>x</replaceable></entry>
-      </row>
-
-      <row>
-       <entry><function>cos</function>(<replaceable>x</replaceable>)</entry>
-       <entry>cosine</entry>
-      </row>
-
-      <row>
-       <entry><function>cot</function>(<replaceable>x</replaceable>)</entry>
-       <entry>cotangent</entry>
-      </row>
-
-      <row>
-       <entry><function>sin</function>(<replaceable>x</replaceable>)</entry>
-       <entry>sine</entry>
-      </row>
-
-      <row>
-       <entry><function>tan</function>(<replaceable>x</replaceable>)</entry>
-       <entry>tangent</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    All trigonometric functions have arguments and return values of
-    type <type>double precision</type>.
-   </para>
-
-  </sect1>
-
-
-  <sect1 id="functions-string">
-   <title>String Functions and Operators</title>
-
-   <para>
-    This section describes functions and operators for examining and
-    manipulating string values.  Strings in this context include values
-    of all 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 the automatic padding when using the
-    <type>CHARACTER</type> type.  Generally, the functions described
-    here also work on data of non-string types by converting that data
-    to a string representation first.  Some functions also exist
-    natively for bit-string types.
-   </para>
-
-   <para>
-    <acronym>SQL</acronym> defines some string functions with a special syntax where
-    certain keywords rather than commas are used to separate the
-    arguments.  Details are in <xref linkend="functions-string-sql">.
-    These functions are also implemented using the regular syntax for
-    function invocation.  (See <xref linkend="functions-string-other">.)
-   </para>
-
-   <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> <parameter>string</parameter> <literal>||</literal>
-        <parameter>string</parameter> </entry>
-       <entry> <type>text</type> </entry>
-       <entry>
-        string concatenation
-        <indexterm>
-         <primary>character strings</primary>
-         <secondary>concatenation</secondary>
-        </indexterm>
-       </entry>
-       <entry><literal>'Postgre' || 'SQL'</literal></entry>
-       <entry><literal>PostgreSQL</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>bit_length</function>(<parameter>string</parameter>)</entry>
-       <entry><type>integer</type></entry>
-       <entry>number of bits in string</entry>
-       <entry><literal>bit_length('jose')</literal></entry>
-       <entry><literal>32</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>char_length</function>(<parameter>string</parameter>) or <function>character_length</function>(<parameter>string</parameter>)</entry>
-       <entry><type>integer</type></entry>
-       <entry>
-        number of characters in string
-        <indexterm>
-         <primary>character strings</primary>
-         <secondary>length</secondary>
-        </indexterm>
-        <indexterm>
-         <primary>length</primary>
-         <secondary>character strings</secondary>
-         <see>character strings, length</see>
-        </indexterm>
-       </entry>
-       <entry><literal>char_length('jose')</literal></entry>
-       <entry><literal>4</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>lower</function>(<parameter>string</parameter>)</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><function>octet_length</function>(<parameter>string</parameter>)</entry>
-       <entry><type>integer</type></entry>
-       <entry>number of bytes in string</entry>
-       <entry><literal>octet_length('jose')</literal></entry>
-       <entry><literal>4</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>overlay</function>(<parameter>string</parameter> placing <parameter>string</parameter> from <type>integer</type> <optional>for <type>integer</type></optional>)</entry>
-       <entry><type>text</type></entry>
-       <entry>
-        insert substring
-        <indexterm>
-         <primary>overlay</primary>
-        </indexterm>
-       </entry>
-       <entry><literal>overlay('Txxxxas' placing 'hom' from 2 for 4)</literal></entry>
-       <entry><literal>Thomas</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>position</function>(<parameter>substring</parameter> in <parameter>string</parameter>)</entry>
-       <entry><type>integer</type></entry>
-       <entry>location of specified substring</entry>
-       <entry><literal>position('om' in 'Thomas')</literal></entry>
-       <entry><literal>3</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>substring</function>(<parameter>string</parameter> <optional>from <type>integer</type></optional> <optional>for <type>integer</type></optional>)</entry>
-       <entry><type>text</type></entry>
-       <entry>
-        extract substring
-        <indexterm>
-         <primary>substring</primary>
-        </indexterm>
-       </entry>
-       <entry><literal>substring('Thomas' from 2 for 3)</literal></entry>
-       <entry><literal>hom</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>substring</function>(<parameter>string</parameter> <optional>from <replaceable>pattern</replaceable></optional> <optional>for <replaceable>escape</replaceable></optional>)</entry>
-       <entry><type>text</type></entry>
-       <entry>
-        extract regular expression
-        <indexterm>
-         <primary>substring</primary>
-        </indexterm>
-       </entry>
-       <entry><literal>substring('Thomas' from 'mas$' for <optional>escape '\\'</optional>)</literal></entry>
-       <entry><literal>mas</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <function>trim</function>(<optional>leading | trailing | both</optional>
-        <optional><parameter>characters</parameter></optional> from
-        <parameter>string</parameter>)
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Removes the longest string containing only the
-        <parameter>characters</parameter> (a space by default) from the
-        beginning/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><function>upper</function>(<parameter>string</parameter>)</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 below.  Some of them are used internally to implement the
-    <acronym>SQL</acronym>-standard string functions listed above.
-   </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><function>ascii</function>(<type>text</type>)</entry>
-       <entry>integer</entry>
-       <entry>Returns the <acronym>ASCII</acronym> code of the first character of the argument.</entry>
-       <entry><literal>ascii('x')</literal></entry>
-       <entry><literal>120</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>btrim</function>(<parameter>string</parameter> <type>text</type>, <parameter>trim</parameter> <type>text</type>)</entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Remove (trim) the longest string consisting only of characters
-        in <parameter>trim</parameter> 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><function>chr</function>(<type>integer</type>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Returns the character with the given <acronym>ASCII</acronym> code.</entry>
-       <entry><literal>chr(65)</literal></entry>
-       <entry><literal>A</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <function>convert</function>(<parameter>string</parameter>
-        <type>text</type>,
-        <optional><parameter>src_encoding</parameter> <type>name</type>,</optional>
-        <parameter>dest_encoding</parameter> <type>name</type>)
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Converts string using <parameter>dest_encoding</parameter>.
-        The original encoding is specified by
-        <parameter>src_encoding</parameter>.  If
-        <parameter>src_encoding</parameter> is omitted, database
-        encoding is assumed.
-       </entry>
-       <entry><literal>convert('text_in_unicode', 'UNICODE', 'LATIN1')</literal></entry>
-       <entry><literal>text_in_unicode</literal> represented in ISO 8859-1</entry>
-      </row>
-
-      <row>
-       <entry><function>initcap</function>(<type>text</type>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Converts first letter of each word (whitespace separated) to upper case.</entry>
-       <entry><literal>initcap('hi thomas')</literal></entry>
-       <entry><literal>Hi Thomas</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>length</function>(<parameter>string</parameter>)</entry>
-       <entry><type>integer</type></entry>
-       <entry>
-        length of string
-        <indexterm>
-         <primary>character strings</primary>
-         <secondary>length</secondary>
-        </indexterm>
-        <indexterm>
-         <primary>length</primary>
-         <secondary>character strings</secondary>
-         <see>character strings, length</see>
-        </indexterm>
-       </entry>
-       <entry><literal>length('jose')</literal></entry>
-       <entry><literal>4</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <function>lpad</function>(<parameter>string</parameter> <type>text</type>,
-        <parameter>length</parameter> <type>integer</type>
-        <optional>, <parameter>fill</parameter> <type>text</type></optional>)
-       </entry>
-       <entry>text</entry>
-       <entry>
-        Fills 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><function>ltrim</function>(<parameter>string</parameter> <type>text</type>, <parameter>text</parameter> <type>text</type>)</entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Removes the longest string containing only characters from
-        <parameter>trim</parameter> from the start of the string.
-       </entry>
-       <entry><literal>ltrim('zzzytrim','xyz')</literal></entry>
-       <entry><literal>trim</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>pg_client_encoding</function>()</entry>
-       <entry><type>name</type></entry>
-       <entry>
-        Returns current client encoding name.
-       </entry>
-       <entry><literal>pg_client_encoding()</literal></entry>
-       <entry><literal>SQL_ASCII</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>repeat</function>(<type>text</type>, <type>integer</type>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Repeat text a number of times.</entry>
-       <entry><literal>repeat('Pg', 4)</literal></entry>
-       <entry><literal>PgPgPgPg</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <function>rpad</function>(<parameter>string</parameter> <type>text</type>,
-        <parameter>length</parameter> <type>integer</type>
-        <optional>, <parameter>fill</parameter> <type>text</type></optional>)
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Fills 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><function>rtrim</function>(<parameter>string</parameter>
-        text, <parameter>trim</parameter> text)</entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Removes the longest string containing only characters from
-        <parameter>trim</parameter> from the end of the string.
-       </entry>
-       <entry><literal>rtrim('trimxxxx','x')</literal></entry>
-       <entry><literal>trim</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>strpos</function>(<parameter>string</parameter>, <parameter>substring</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Locates 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><function>substr</function>(<parameter>string</parameter>, <parameter>from</parameter> <optional>, <parameter>count</parameter></optional>)</entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Extracts specified 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><function>to_ascii</function>(<type>text</type>
-        <optional>ptional>, <parameter>encoding</parameter></optional>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Converts text from multibyte encoding to <acronym>ASCII</acronym>.</entry>
-       <entry><literal>to_ascii('Karel')</literal></entry>
-       <entry><literal>Karel</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <function>translate</function>(<parameter>string</parameter>
-        <type>text</type>,
-        <parameter>from</parameter> <type>text</type>,
-        <parameter>to</parameter> <type>text</type>)
-       </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.
-       </entry>
-       <entry><literal>translate('12345', '14', 'ax')</literal></entry>
-       <entry><literal>a23x5</literal></entry>
-      </row>       
-      
-      <row>
-       <entry>
-        <function>encode</function>(<parameter>data</parameter> <type>bytea</type>,
-        <parameter>type</parameter> <type>text</type>)
-       </entry>
-       <entry><type>text</type></entry>
-       <entry>
-        Encodes binary data to <acronym>ASCII</acronym>-only representation.  Supported
-        types are: 'base64', 'hex', 'escape'.
-       </entry>
-       <entry><literal>encode('123\\000\\001', 'base64')</literal></entry>
-       <entry><literal>MTIzAAE=</literal></entry>
-      </row>       
-
-      <row>
-       <entry>
-        <function>decode</function>(<parameter>string</parameter> <type>text</type>,
-        <parameter>type</parameter> <type>text</type>)
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Decodes binary data from <parameter>string</parameter> previously 
-        encoded with encode().  Parameter type is same as in encode().
-       </entry>
-       <entry><literal>decode('MTIzAAE=', 'base64')</literal></entry>
-       <entry><literal>123\000\001</literal></entry>
-      </row>       
-
-     </tbody>
-    </tgroup>
-   </table>
-
-   <para>
-    The <function>to_ascii</function> function supports conversion from
-    LATIN1, LATIN2, WIN1250 (CP1250) only.
-   </para>
-  </sect1>
-
-
-  <sect1 id="functions-binarystring">
-   <title>Binary String Functions and Operators</title>
-
-   <para>
-    This section describes functions and operators for examining and
-    manipulating binary string values.  Strings in this context include
-    values of the type <type>BYTEA</type>.
-   </para>
-
-   <para>
-    <acronym>SQL</acronym> defines some string functions with a
-    special syntax where 
-    certain keywords rather than commas are used to separate the
-    arguments.  Details are in
-    <xref linkend="functions-binarystring-sql">.
-    Some functions are also implemented using the regular syntax for
-    function invocation.
-    (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> <parameter>string</parameter> <literal>||</literal>
-        <parameter>string</parameter> </entry>
-       <entry> <type>bytea</type> </entry>
-       <entry>
-        string concatenation
-        <indexterm>
-         <primary>binary strings</primary>
-         <secondary>concatenation</secondary>
-        </indexterm>
-       </entry>
-       <entry><literal>'\\\\Postgre'::bytea || '\\047SQL\\000'::bytea</literal></entry>
-       <entry><literal>\\Postgre'SQL\000</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>octet_length</function>(<parameter>string</parameter>)</entry>
-       <entry><type>integer</type></entry>
-       <entry>number of bytes in binary string</entry>
-       <entry><literal>octet_length('jo\\000se'::bytea)</literal></entry>
-       <entry><literal>5</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>position</function>(<parameter>substring</parameter> in <parameter>string</parameter>)</entry>
-       <entry><type>integer</type></entry>
-       <entry>location of specified substring</entry>
-      <entry><literal>position('\\000om'::bytea in 'Th\\000omas'::bytea)</literal></entry>
-       <entry><literal>3</literal></entry>
-      </row>
-
-      <row>
-       <entry><function>substring</function>(<parameter>string</parameter> <optional>from <type>integer</type></optional> <optional>for <type>integer</type></optional>)</entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        extract substring
-        <indexterm>
-         <primary>substring</primary>
-        </indexterm>
-       </entry>
-       <entry><literal>substring('Th\\000omas'::bytea from 2 for 3)</literal></entry>
-       <entry><literal>h\000o</literal></entry>
-      </row>
-
-      <row>
-       <entry>
-        <function>trim</function>(<optional>both</optional>
-        <parameter>characters</parameter> from
-        <parameter>string</parameter>)
-       </entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Removes the longest string containing only the
-        <parameter>characters</parameter> from the
-        beginning/end/both ends of the <parameter>string</parameter>.
-       </entry>
-       <entry><literal>trim('\\000'::bytea from '\\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 below.  Some of them are used internally to implement the
-    <acronym>SQL</acronym>-standard string functions listed above.
-   </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><function>btrim</function>(<parameter>string</parameter>
-        <type>bytea</type> <parameter>trim</parameter> <type>bytea</type>)</entry>
-       <entry><type>bytea</type></entry>
-       <entry>
-        Remove (trim) the longest string consisting only of characters
-        in <parameter>trim</parameter> from the start and end of
-        <parameter>string</parameter>.
-      </entry>
-      <entry><literal>btrim('\\000trim\\000'::bytea,'\\000'::bytea)</literal></entry>
-      <entry><literal>trim</literal></entry>
-     </row>
-
-     <row>
-      <entry><function>length</function>(<parameter>string</parameter>)</entry>
-      <entry><type>integer</type></entry>
-      <entry>
-       length of binary string
-       <indexterm>
-        <primary>binary strings</primary>
-	<secondary>length</secondary>
-       </indexterm>
-       <indexterm>
-        <primary>length</primary>
-	<secondary>binary strings</secondary>
-	<see>binary strings, length</see>
-       </indexterm>
-      </entry>
-      <entry><literal>length('jo\\000se'::bytea)</literal></entry>
-      <entry><literal>5</literal></entry>
-     </row>
-
-     <row>
-      <entry>
-       <function>encode</function>(<parameter>string</parameter> <type>bytea</type>,
-              <parameter>type</parameter> <type>text</type>)
-      </entry>
-      <entry><type>text</type></entry>
-      <entry>
-       Encodes binary string to <acronym>ASCII</acronym>-only representation.  Supported
-       types are: 'base64', 'hex', 'escape'.
-      </entry>
-      <entry><literal>encode('123\\000456'::bytea, 'escape')</literal></entry>
-      <entry><literal>123\000456</literal></entry>
-     </row>       
-
-     <row>
-      <entry>
-       <function>decode</function>(<parameter>string</parameter> <type>text</type>,
-              <parameter>type</parameter> <type>text</type>)
-      </entry>
-      <entry><type>bytea</type></entry>
-      <entry>
-       Decodes binary string from <parameter>string</parameter> previously 
-       encoded with encode().  Parameter type is same as in encode().
-      </entry>
-      <entry><literal>decode('123\\000456', 'escape')</literal></entry>
-      <entry><literal>123\000456</literal></entry>
-     </row>       
-
-    </tbody>
-   </tgroup>
-  </table>
-
- </sect1>
-
-
- <sect1 id="functions-matching">
-  <title>Pattern Matching</title>
-
-   <para>
-    There are two separate approaches to pattern matching provided by
-    <productname>PostgreSQL</productname>:  the traditional
-    <acronym>SQL</acronym> 
-    <function>LIKE</function> operator and the more recent
-    <acronym>SQL99</acronym> 
-    <function>SIMILAR TO</function> operator implementing
-    <acronym>POSIX</acronym>-style regular expressions.
-    Additionally, a pattern matching function,
-    <function>SUBSTRING</function>, is available, as defined in
-    <acronym>SQL99</acronym>.
-   </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>
-
-   <para>
-    Both <function>LIKE</function> and <function>SIMILAR TO</function>
-    are SQL-standard operators which are also available in alternate
-    forms as <productname>PostgreSQL</productname> operators; look at
-    <literal>~</literal> and <literal>~~</literal> for examples.
-   </para>
-
-  <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>
-     Every <replaceable>pattern</replaceable> defines a set of strings.
-     The <function>LIKE</function> expression returns true if the
-     <replaceable>string</replaceable> is contained in the set of
-     strings represented by <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 underscore, 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 string
-     of zero or more characters.
-    </para>
-
-    <informalexample>
-     <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>
-    </informalexample>
-
-   <para>
-    <function>LIKE</function> pattern matches always cover the entire
-    string.  To match a pattern anywhere within a string, the
-    pattern must therefore 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 may 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 the query.  Thus, writing a pattern
-    that actually matches a literal backslash means writing four backslashes
-    in the query.  You can avoid this by selecting a different escape
-    character with <literal>ESCAPE</literal>; then backslash is not special
-    to <function>LIKE</function> anymore. (But it is still special to the string
-    literal parser, so you still need two of them.)
-   </para>
-
-   <para>
-    It's also possible to select no escape character by writing
-    <literal>ESCAPE ''</literal>.  This effectively disables the
-     escape mechanism and
-     turns off the special meaning of underscore and percent signs in
-    the pattern.
-   </para>
-
-   <para>
-    The keyword <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
-    <productname>PostgreSQL</productname> extension.
-   </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>.  All of these operators are
-    <productname>PostgreSQL</productname>-specific.
-   </para>
-  </sect2>
-
-
-  <sect2 id="functions-regexp">
-   <title><function>SIMILAR TO</function> and <acronym>POSIX</acronym>
-     Regular Expressions</title>
-
-   <indexterm zone="functions-regexp">
-    <primary>regular expressions</primary>
-    <seealso>pattern matching</seealso>
-   </indexterm>
-
-   <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>
-
-       <row>
-        <entry> <literal>SIMILAR TO</literal> </entry>
-        <entry>Matches regular expression, case sensitive</entry>
-        <entry><literal>'thomas' SIMILAR TO '.*thomas.*'</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> function.
-     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 --- 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>
-
-    <informalexample>
-     <para>
-      Some examples:
-      <programlisting>
-'abc' SIMILAR TO 'abc'    <lineannotation>true</lineannotation>
-'abc' SIMILAR TO '^a'     <lineannotation>true</lineannotation>
-'abc' SIMILAR TO '(b|d)'  <lineannotation>true</lineannotation>
-'abc' SIMILAR TO '^(b|c)' <lineannotation>false</lineannotation>
-      </programlisting>
-     </para>
-    </informalexample>
-
-<!-- derived from the re_format.7 man page -->
-   <para>
-    Regular expressions (<quote>RE</quote>s), as defined in
-     <acronym>POSIX</acronym> 
-    1003.2, come in two forms: modern REs (roughly those of
-    <command>egrep</command>; 1003.2 calls these
-    <quote>extended</quote> REs) and obsolete REs (roughly those of
-    <command>ed</command>; 1003.2 <quote>basic</quote> REs).
-    <productname>PostgreSQL</productname> implements the modern form.
-   </para>
-
-   <para>
-    A (modern) RE is one or more non-empty
-    <firstterm>branches</firstterm>, separated by
-    <literal>|</literal>.  It matches anything that matches one of the
-    branches.
-   </para>
-
-   <para>
-    A branch is one or more <firstterm>pieces</firstterm>,
-    concatenated.  It matches a match for the first, followed by a
-    match for the second, etc.
-   </para>
-
-   <para>
-    A piece is an <firstterm>atom</firstterm> possibly followed by a
-    single <literal>*</literal>, <literal>+</literal>,
-    <literal>?</literal>, or <firstterm>bound</firstterm>.  An atom
-    followed by <literal>*</literal> matches a sequence of 0 or more
-    matches of the atom.  An atom followed by <literal>+</literal>
-    matches a sequence of 1 or more matches of the atom.  An atom
-    followed by <literal>?</literal> matches a sequence of 0 or 1
-    matches of the atom.
-   </para>
-
-   <para>
-    A <firstterm>bound</firstterm> is <literal>{</literal> followed by
-    an unsigned decimal integer, possibly followed by
-    <literal>,</literal> possibly followed by another unsigned decimal
-    integer, always followed by <literal>}</literal>.  The integers
-    must lie between 0 and <symbol>RE_DUP_MAX</symbol> (255)
-    inclusive, and if there are two of them, the first may not exceed
-    the second.  An atom followed by a bound containing one integer
-    <replaceable>i</replaceable> and no comma matches a sequence of
-    exactly <replaceable>i</replaceable> matches of the atom.  An atom
-    followed by a bound containing one integer
-    <replaceable>i</replaceable> and a comma matches a sequence of
-    <replaceable>i</replaceable> or more matches of the atom.  An atom
-    followed by a bound containing two integers
-    <replaceable>i</replaceable> and <replaceable>j</replaceable>
-    matches a sequence of <replaceable>i</replaceable> through
-    <replaceable>j</replaceable> (inclusive) matches of the atom.
-   </para>
-
-   <note>
-    <para>
-     A repetition operator (<literal>?</literal>,
-     <literal>*</literal>, <literal>+</literal>, or bounds) cannot
-     follow another repetition operator.  A repetition operator cannot
-     begin an expression or subexpression or follow
-     <literal>^</literal> or <literal>|</literal>.
-    </para>
-   </note>
-
-   <para>
-    An <firstterm>atom</firstterm> is a regular expression enclosed in
-    <literal>()</literal> (matching a match for the regular
-    expression), an empty set of <literal>()</literal> (matching the
-    null string), a <firstterm>bracket expression</firstterm> (see
-    below), <literal>.</literal> (matching any single character),
-    <literal>^</literal> (matching the null string at the beginning of the
-    input string), <literal>$</literal> (matching the null string at the end
-    of the input string), a <literal>\</literal> followed by one of the
-    characters <literal>^.[$()|*+?{\</literal> (matching that
-    character taken as an ordinary character), a <literal>\</literal>
-    followed by any other character (matching that character taken as
-    an ordinary character, as if the <literal>\</literal> had not been
-    present), or a single character with no other significance
-    (matching that character).  A <literal>{</literal> followed by a
-    character other than a digit is an ordinary character, not the
-    beginning of a bound.  It is illegal to end an RE with
-    <literal>\</literal>.
-   </para>
-
-   <para>
-    Note that the backslash (<literal>\</literal>) already has a special
-    meaning in string
-    literals, so to write a pattern constant that contains a backslash
-    you must write two backslashes in the query.
-   </para>
-
-   <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
-    (but see below) 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, and portable programs should avoid
-    relying on them.
-   </para>
-
-   <para>
-    To include a literal <literal>]</literal> in the list, make it the
-    first character (following a possible <literal>^</literal>).  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 and
-    some combinations using <literal>[</literal> (see next
-    paragraphs), all other special characters, including
-    <literal>\</literal>, lose their special significance within a
-    bracket expression.
-   </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
-    a single element of the bracket expression's list.  A bracket
-    expression containing a multiple-character collating element can thus
-    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>
-
-   <para>
-    Within a bracket expression, a collating element enclosed in
-    <literal>[=</literal> and <literal>=]</literal> is an 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
-    may not 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 may provide others.  A character class may not be used as
-    an endpoint of a range.
-   </para>
-
-   <para>
-    There are two special cases of bracket expressions:  the bracket
-    expressions <literal>[[:<:]]</literal> and
-    <literal>[[:>:]]</literal> match the null string at the beginning
-    and end of a word respectively.  A word is defined as a sequence
-    of word characters which is neither preceded nor followed by word
-    characters.  A word character is an 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.
-   </para>
-
-   <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, it matches the longest.  Subexpressions also match the
-    longest possible substrings, subject to the constraint that the
-    whole match be as long as possible, with subexpressions starting
-    earlier in the RE taking priority over ones starting later.  Note
-    that higher-level subexpressions thus take priority over their
-    lower-level component subexpressions.
-   </para>
-
-   <para>
-    Match lengths are measured in characters, not collating
-    elements.  A null string is considered longer than no match at
-    all.  For example, <literal>bb*</literal> matches the three middle
-    characters of <literal>abbbc</literal>,
-    <literal>(wee|week)(knights|nights)</literal> matches all ten
-    characters of <literal>weeknights</literal>, when
-    <literal>(.*).*</literal> is matched against
-    <literal>abc</literal> the parenthesized subexpression matches all
-    three characters, and when <literal>(a*)*</literal> is matched
-    against <literal>bc</literal> both the whole RE and the
-    parenthesized subexpression match the null 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</literal> becomes <literal>[xX]</literal>.  When
-    it appears inside a bracket expression, all case counterparts of
-    it are added to the bracket expression, so that (e.g.)
-    <literal>[x]</literal> becomes <literal>[xX]</literal> and
-    <literal>[^x]</literal> becomes <literal>[^xX]</literal>.
-   </para>
-
-   <para>
-    There is no particular limit on the length of REs, except insofar
-    as memory is limited.  Memory usage is approximately linear in RE
-    size, and largely insensitive to RE complexity, except for bounded
-    repetitions.  Bounded repetitions are implemented by macro
-    expansion, which is costly in time and space if counts are large
-    or bounded repetitions are nested.  An RE like, say,
-    <literal>((((a{1,100}){1,100}){1,100}){1,100}){1,100}</literal>
-    will (eventually) run almost any existing machine out of swap
-    space.
-    <footnote>
-     <para>
-      This was written in 1994, mind you.  The
-      numbers have probably changed, but the problem
-      persists.
-     </para>
-    </footnote>
-   </para>
-<!-- end re_format.7 man page -->
-  </sect2>
-
- </sect1>
-
-
-  <sect1 id="functions-formatting">
-   <title>Data Type Formatting Functions</title>
-
-   <indexterm zone="functions-formatting">
-    <primary>formatting</primary>
-   </indexterm>
-
-   <note>
-    <title>Author</title>
-    <para>
-     Written by Karel Zak (<email>zakkr@zf.jcu.cz</email>) on 2000-01-24
-    </para>
-   </note>
-
-   <para>
-    The <productname>PostgreSQL</productname> formatting functions
-    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.
-    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>
-
-    <table tocentry="1">
-     <title>Formatting Functions</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>Function</entry>
-	<entry>Returns</entry>
-	<entry>Description</entry>
-	<entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><function>to_char</function>(<type>timestamp</type>, <type>text</type>)</entry>
-	<entry><type>text</type></entry>
-	<entry>convert time stamp to string</entry>
-	<entry><literal>to_char(timestamp 'now','HH12:MI:SS')</literal></entry>
-       </row>
-       <row>
-	<entry><function>to_char</function>(<type>interval</type>, <type>text</type>)</entry>
-	<entry><type>text</type></entry>
-	<entry>convert interval to string</entry>
-	<entry><literal>to_char(interval '15h 2m 12s','HH24:MI:SS')</literal></entry>
-       </row>
-       <row>
-	<entry><function>to_char</function>(<type>int</type>, <type>text</type>)</entry>
-	<entry><type>text</type></entry>
-	<entry>convert int4/int8 to string</entry>
-	<entry><literal>to_char(125, '999')</literal></entry>
-       </row>
-       <row>
-	<entry><function>to_char</function>(<type>double precision</type>,
-        <type>text</type>)</entry>
-	<entry><type>text</type></entry>
-	<entry>convert real/double precision to string</entry>
-	<entry><literal>to_char(125.8, '999D9')</literal></entry>
-       </row>
-       <row>
-	<entry><function>to_char</function>(<type>numeric</type>, <type>text</type>)</entry>
-	<entry><type>text</type></entry>
-	<entry>convert numeric to string</entry>
-	<entry><literal>to_char(numeric '-125.8', '999D99S')</literal></entry>
-       </row>
-       <row>
-	<entry><function>to_date</function>(<type>text</type>, <type>text</type>)</entry>
-	<entry><type>date</type></entry>
-	<entry>convert string to date</entry>
-	<entry><literal>to_date('05 Dec 2000', 'DD Mon YYYY')</literal></entry>
-       </row>
-       <row>
-	<entry><function>to_timestamp</function>(<type>text</type>, <type>text</type>)</entry>
-	<entry><type>timestamp</type></entry>
-	<entry>convert string to time stamp</entry>
-	<entry><literal>to_timestamp('05 Dec 2000', 'DD Mon YYYY')</literal></entry>
-       </row>
-       <row>
-	<entry><function>to_number</function>(<type>text</type>, <type>text</type>)</entry>
-	<entry><type>numeric</type></entry>
-	<entry>convert string to numeric</entry>
-	<entry><literal>to_number('12,454.8-', '99G999D9S')</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    In an output template string, there are certain patterns that are
-    recognized and replaced with appropriately-formatted data from the value
-    to be formatted.  Any text that is not a template pattern is simply
-    copied verbatim.  Similarly, in an input template string, template patterns
-    identify the parts of the input data string to be looked at and the
-    values to be found there.
-   </para>
-
-    <table tocentry="1">
-     <title>Template patterns for date/time conversions</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> or <literal>A.M.</literal> or
-<literal>li</literal>literal> or <literal>P.M.</literal></entry>
-	<entry>meridian indicator (upper case)</entry>
-       </row>
-       <row>
-	<entry><literal>am</literal> or <literal>a.m.</literal> or
-<literal>li</literal>literal> or <literal>p.m.</literal></entry>
-	<entry>meridian indicator (lower case)</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>BC</literal> or <literal>B.C.</literal> or
-<literal>li</literal>literal> or <literal>A.D.</literal></entry>
-	<entry>era indicator (upper case)</entry>
-       </row>
-       <row>
-	<entry><literal>bc</literal> or <literal>b.c.</literal> or
-<literal>li</literal>literal> or <literal>a.d.</literal></entry>
-	<entry>era indicator (lower case)</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 mixed case 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)</entry>
-       </row>
-       <row>
-	<entry><literal>Mon</literal></entry>
-	<entry>abbreviated mixed case month name (3 chars)</entry>
-       </row>
-       <row>
-	<entry><literal>mon</literal></entry>
-	<entry>abbreviated lower case month name (3 chars)</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 mixed case 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)</entry>
-       </row>
-       <row>
-	<entry><literal>Dy</literal></entry>
-	<entry>abbreviated mixed case day name (3 chars)</entry>
-       </row>
-       <row>
-	<entry><literal>dy</literal></entry>
-	<entry>abbreviated lower case day name (3 chars)</entry>
-       </row>
-       <row>
-	<entry><literal>DDD</literal></entry>
-	<entry>day of year (001-366)</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 week (1-7; SUN=1)</entry>
-       </row>
-       <row>
-	<entry><literal>W</literal></entry>
-	<entry>week of month (1-5) where first week start on the first day of the month</entry>
-       </row> 
-       <row>
-	<entry><literal>WW</literal></entry>
-	<entry>week number of year (1-53) where first week start on the first day of the year</entry>
-       </row>
-       <row>
-	<entry><literal>IW</literal></entry>
-	<entry>ISO week number of year (The first Thursday of the new year is in week 1.)</entry>
-       </row>
-       <row>
-	<entry><literal>CC</literal></entry>
-	<entry>century (2 digits)</entry>
-       </row>
-       <row>
-	<entry><literal>J</literal></entry>
-	<entry>Julian Day (days since January 1, 4712 BC)</entry>
-       </row>
-       <row>
-	<entry><literal>Q</literal></entry>
-	<entry>quarter</entry>
-       </row>
-       <row>
-	<entry><literal>RM</literal></entry>
-	<entry>month in Roman Numerals (I-XII; I=January) - upper case</entry>
-       </row>
-       <row>
-	<entry><literal>rm</literal></entry>
-	<entry>month in Roman Numerals (I-XII; I=January) - lower case</entry>
-       </row>
-       <row>
-	<entry><literal>TZ</literal></entry>
-	<entry>timezone name - upper case</entry>
-       </row>
-       <row>
-	<entry><literal>tz</literal></entry>
-	<entry>timezone name - lower case</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Certain modifiers may be applied to any template pattern to alter its
-    behavior.  For example, <quote><literal>FMMonth</literal></quote>
-    is the <quote><literal>Month</literal></quote> pattern with the
-    <quote><literal>FM</literal></quote> prefix.
-   </para>
-
-    <table tocentry="1">
-     <title>Template pattern modifiers for date/time conversions</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 zeroes)</entry>
-	<entry><literal>FMMonth</literal></entry>
-       </row>
-       <row>
-	<entry><literal>TH</literal> suffix</entry>
-	<entry>add upper-case ordinal number suffix</entry>
-	<entry><literal>DDTH</literal></entry>
-       </row>	
-       <row>
-	<entry><literal>th</literal> suffix</entry>
-	<entry>add lower-case ordinal number suffix</entry>
-	<entry><literal>DDth</literal></entry>
-       </row>
-       <row>
-	<entry><literal>FX</literal> prefix</entry>
-	<entry>Fixed format global option (see below)</entry>
-	<entry><literal>FX Month DD Day</literal></entry>
-       </row>	
-       <row>
-	<entry><literal>SP</literal> suffix</entry>
-	<entry>spell mode (not yet implemented)</entry>
-	<entry><literal>DDSP</literal></entry>
-       </row>       
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Usage notes:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       <literal>FM</literal> suppresses leading zeroes or trailing blanks
-       that would otherwise be added to make the output of a pattern be
-       fixed-width.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>to_timestamp</function> and <function>to_date</function>
-       skip multiple blank spaces in the input string if the <literal>FX</literal> option 
-       is not used. <literal>FX</literal> must be specified as the first item
-       in the template; for example 
-       <literal>to_timestamp('2000    JUN','YYYY MON')</literal> is right, but
-       <literal>to_timestamp('2000    JUN','FXYYYY MON')</literal> returns an error,
-       because <function>to_timestamp</function> expects one blank space only.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       If a backslash (<quote><literal>\</literal></quote>) is desired
-       in a string constant, a double backslash
-       (<quote><literal>\\</literal></quote>) must be entered; for
-       example <literal>'\\HH\\MI\\SS'</literal>.  This is true for
-       any string constant in <productname>PostgreSQL</productname>.
-      </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 keywords.  For example, in
-       <literal>'"Hello Year: "YYYY'</literal>, the <literal>YYYY</literal>
-       will be replaced by year data, but the single <literal>Y</literal>
-       will not be.
-      </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>'\\"YYYY
-       Month\\"'</literal>. <!-- "" font-lock sanity :-) -->
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>YYYY</literal> conversion from string to <type>timestamp</type> or
-       <type>date</type> is restricted if you use a year 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 year 20000):
-       <literal>to_date('200001131', 'YYYYMMDD')</literal> will be 
-       interpreted as a 4-digit year; better is to 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>
-       Millisecond <literal>MS</literal> and microsecond <literal>US</literal>
-       values in a conversion from string to time stamp are used as part of the
-       seconds 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.
-       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>
-    </itemizedlist>
-   </para>
-
-    <table tocentry="1">
-     <title>Template patterns for numeric conversions</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>negative value with minus sign (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 < 0)</entry>
-       </row>
-       <row>
-	<entry><literal>PL</literal></entry>
-	<entry>plus sign in specified position (if number > 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>convert to ordinal number</entry>
-       </row>
-       <row>
-	<entry><literal>V</literal></entry>
-	<entry>shift <replaceable>n</replaceable> digits (see
-	 notes)</entry>
-       </row>
-       <row>
-	<entry><literal>EEEE</literal></entry>
-	<entry>scientific notation (not implemented yet)</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    Usage notes:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       A sign formatted using <literal>SG</literal>, <literal>PL</literal>, or
-       <literal>MI</literal> is not an anchor in
-       the number; for example,
-       <literal>to_char(-12, 'S9999')</literal> produces <literal>'  -12'</literal>,
-       but <literal>to_char(-12, 'MI9999')</literal> produces <literal>'-  12'</literal>.
-       The Oracle implementation does not allow the use of
-       <literal>MI</literal> ahead of <literal>9</literal>, but rather
-       requires that <literal>9</literal> precede
-       <literal>MI</literal>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>9</literal> specifies a value with the same number of 
-       digits as there are <literal>9</literal>s. If a digit is
-       not available use blank space.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>TH</literal> does not convert values less than zero
-       and does not convert decimal numbers.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <literal>PL</literal>, <literal>SG</literal>, and
-       <literal>TH</literal> are <productname>PostgreSQL</productname>
-       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>
-    </itemizedlist>
-   </para>   
-
-    <table tocentry="1">
-     <title><function>to_char</function> Examples</title>
-     <tgroup cols="2">
-      <thead>
-       <row>
-	<entry>Input</entry>
-	<entry>Output</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><literal>to_char(now(),'Day, DD  HH12:MI:SS')</literal></entry>
-        <entry><literal>'Tuesday  , 06  05:39:18'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(now(),'FMDay, FMDD  HH12:MI:SS')</literal></entry>
-        <entry><literal>'Tuesday, 6  05:39:18'</literal></entry>
-       </row>          
-       <row>
-        <entry><literal>to_char(-0.1,'99.99')</literal></entry>
-        <entry><literal>' -.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>' 0.1'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(12,'9990999.9')</literal></entry>
-        <entry><literal>'    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>' 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 9 9')</literal></entry>
-        <entry><literal>' 4 8 5'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(1485,'9,999')</literal></entry>
-        <entry><literal>' 1,485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(1485,'9G999')</literal></entry>
-        <entry><literal>' 1 485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(148.5,'999.999')</literal></entry>
-        <entry><literal>' 148.500'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(148.5,'999D999')</literal></entry>
-        <entry><literal>' 148,500'</literal></entry>	 
-       </row>
-       <row>
-        <entry><literal>to_char(3148.5,'9G999D999')</literal></entry>
-        <entry><literal>' 3 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'</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 485</literal></entry>	 
-       </row>
-       <row>
-        <entry><literal>to_char(485,'RN')</literal></entry>		
-        <entry><literal>'        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>' 482nd'</literal></entry>				
-       </row>
-       <row>
-        <entry><literal>to_char(485, '"Good number:"999')</literal></entry>
-        <entry><literal>'Good number: 485'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(485.8,'"Pre:"999" Post:" .999')</literal></entry>
-        <entry><literal>'Pre: 485 Post: .800'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(12,'99V999')</literal></entry>		
-        <entry><literal>' 12000'</literal></entry>
-       </row>
-       <row>
-        <entry><literal>to_char(12.4,'99V999')</literal></entry>
-        <entry><literal>' 12400'</literal></entry>
-       </row>
-       <row>		
-        <entry><literal>to_char(12.45, '99V9')</literal></entry>
-        <entry><literal>' 125'</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-  </sect1>
-
-
-  <sect1 id="functions-datetime">
-   <title>Date/Time Functions and Operators</title>
-
-   <para>
-    <xref linkend="functions-datetime-table"> shows the available
-    functions for date/time value processing.  
-    <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 (see <xref
-                                                              linkend="datatype-datetime">).
-   </para>
-
-   <para>
-    The date/time operators described below behave similarly for types
-    involving time zones as well as those without.
-
-    <table id="operators-datetime-table">
-     <title>Date/Time Operators</title>
-
-     <tgroup cols="3">
-      <thead>
-       <row>
-        <entry>Name</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><type>timestamp</type> '2001-09-28 01:00' + <type>interval</type> '23 hours'</entry>
-        <entry><type>timestamp</type> '2001-09-29 00:00'</entry>
-       </row>
-
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><type>date</type> '2001-09-28' + <type>interval</type> '1 hour'</entry>
-        <entry><type>timestamp</type> '2001-09-28 01:00'</entry>
-       </row>
-
-       <row>
-        <entry> <literal>+</literal> </entry>
-        <entry><type>time</type> '01:00' + <type>interval</type> '3 hours'</entry>
-        <entry><type>time</type> '04:00'</entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><type>timestamp</type> '2001-09-28 23:00' - <type>interval</type> '23 hours'</entry>
-        <entry><type>timestamp</type> '2001-09-28'</entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><type>date</type> '2001-09-28' - <type>interval</type> '1 hour'</entry>
-        <entry><type>timestamp</type> '2001-09-27 23:00'</entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><type>time</type> '05:00' - <type>interval</type> '2 hours'</entry>
-        <entry><type>time</type> '03:00'</entry>
-       </row>
-
-       <row>
-        <entry> <literal>-</literal> </entry>
-        <entry><type>interval</type> '2 hours' - <type>time</type> '05:00'</entry>
-        <entry><type>time</type> '03:00:00'</entry>
-       </row>
-
-       <row>
-        <entry> <literal>*</literal> </entry>
-        <entry><type>interval</type> '1 hour' * <type>int</type> '3'</entry>
-        <entry><type>interval</type> '03:00'</entry>
-       </row>
-
-       <row>
-        <entry> <literal>/</literal> </entry>
-        <entry><type>interval</type> '1 hour' / <type>int</type> '3'</entry>
-        <entry><type>interval</type> '00:20'</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-   <para>
-    The date/time functions are summarized below, with additional
-    details in subsequent sections.
-
-    <table id="functions-datetime-table">
-     <title>Date/Time Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-	<entry>Name</entry>
-	<entry>Return Type</entry>
-	<entry>Description</entry>
-	<entry>Example</entry>
-	<entry>Result</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-	<entry><function>age</function>(<type>timestamp</type>)</entry>
-	<entry><type>interval</type></entry>
-	<entry>Subtract from today</entry>
-	<entry><literal>age(timestamp '1957-06-13')</literal></entry>
-	<entry><literal>43 years 8 mons 3 days</literal></entry>
-       </row>
-
-       <row>
-	<entry><function>age</function>(<type>timestamp</type>, <type>timestamp</type>)</entry>
-	<entry><type>interval</type></entry>
-	<entry>Subtract arguments</entry>
-	<entry><literal>age('2001-04-10', timestamp '1957-06-13')</literal></entry>
-	<entry><literal>43 years 9 mons 27 days</literal></entry>
-       </row>
-
-       <row>
-	<entry><function>current_date</function></entry>
-	<entry><type>date</type></entry>
-	<entry>Today's date; see <link linkend="functions-datetime-current">below</link>
-	</entry>
-	<entry></entry>
-	<entry></entry>
-       </row>
-
-       <row>
-        <entry><function>current_time</function></entry>
-        <entry><type>time with time zone</type></entry>
-        <entry>Time of day; see <link linkend="functions-datetime-current">below</link>
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-	<entry><function>current_timestamp</function></entry>
-	<entry><type>timestamp with time zone</type></entry>
-	<entry>Date and time; see <link linkend="functions-datetime-current">below</link>
-	</entry>
-	<entry></entry>
-	<entry></entry>
-       </row>
-
-       <row>
-	<entry><function>date_part</function>(<type>text</type>, <type>timestamp</type>)</entry>
-	<entry><type>double precision</type></entry>
-	<entry>Get subfield (equivalent to
-	 <function>extract</function>); see also <link
-                                                linkend="functions-datetime-datepart">below</link>
-        </entry>
-	<entry><literal>date_part('hour', timestamp '2001-02-16 20:38:40')</literal></entry>
-	<entry><literal>20</literal></entry>
-       </row>
-
-       <row>
-	<entry><function>date_part</function>(<type>text</type>, <type>interval</type>)</entry>
-	<entry><type>double precision</type></entry>
-	<entry>Get subfield (equivalent to
-	 <function>extract</function>); see also <link
-                                                linkend="functions-datetime-datepart">below</link>
-        </entry>
-	<entry><literal>date_part('month', interval '2 years 3 months')</literal></entry>
-	<entry><literal>3</literal></entry>
-       </row>
-
-       <row>
-	<entry><function>date_trunc</function>(<type>text</type>, <type>timestamp</type>)</entry>
-	<entry><type>timestamp</type></entry>
-	<entry>Truncate to specified precision; see also <link
-                                                        linkend="functions-datetime-trunc">below</link>
-        </entry>
-	<entry><literal>date_trunc('hour', timestamp '2001-02-16 20:38:40')</literal></entry>
-	<entry><literal>2001-02-16 20:00:00+00</literal></entry>
-       </row>
-
-       <row>
-	<entry><function>extract</function>(<parameter>field</parameter> from
-         <type>timestamp</type>)</entry>
-	<entry><type>double precision</type></entry>
-	<entry>Get subfield; see also <link
-                                     linkend="functions-datetime-extract">below</link>
-        </entry>
-	<entry><literal>extract(hour from timestamp '2001-02-16 20:38:40')</literal></entry>
-	<entry><literal>20</literal></entry>
-       </row>
-
-       <row>
-	<entry><function>extract</function>(<parameter>field</parameter> from
-         <type>interval</type>)</entry>
-	<entry><type>double precision</type></entry>
-	<entry>Get subfield; see also <link
-                                     linkend="functions-datetime-extract">below</link>
-        </entry>
-	<entry><literal>extract(month from interval '2 years 3 months')</literal></entry>
-	<entry><literal>3</literal></entry>
-       </row>
-
-       <row>
-	<entry><function>isfinite</function>(<type>timestamp</type>)</entry>
-	<entry><type>boolean</type></entry>
-	<entry>Test for finite time stamp (neither invalid nor infinity)</entry>
-	<entry><literal>isfinite(timestamp '2001-02-16 21:28:30')</literal></entry>
-	<entry><literal>true</literal></entry>
-       </row>
-
-       <row>
-	<entry><function>isfinite</function>(<type>interval</type>)</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><function>localtime</function></entry>
-        <entry><type>time</type></entry>
-        <entry>Time of day; see <link linkend="functions-datetime-current">below</link>
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry><function>localtimestamp</function></entry>
-        <entry><type>timestamp</type></entry>
-        <entry>Date and time; see <link linkend="functions-datetime-current">below</link>
-        </entry>
-        <entry></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-	<entry><function>now</function>()</entry>
-	<entry><type>timestamp</type></entry>
-	<entry>Current date and time (equivalent to
-	 <function>current_timestamp</function>); see <link
-                                                     linkend="functions-datetime-current">below</link>
-	</entry>
-	<entry></entry>
-	<entry></entry>
-       </row>
-
-       <row>
-	<entry><function>timeofday()</function></entry>
-	<entry><type>text</type></entry>
-	<entry>Current date and time; see <link
-                                         linkend="functions-datetime-current">below</link>
-	</entry>
-	<entry><literal>timeofday()</literal></entry>
-	<entry><literal>Wed Feb 21 17:01:13.000126 2001 EST</literal></entry>
-       </row>
-
-      </tbody>
-     </tgroup>
-    </table>
-   </para>
-
-  <sect2 id="functions-datetime-extract">
-   <title><function>EXTRACT</function>, <function>date_part</function></title>
-
-<synopsis>
-EXTRACT (<replaceable>field</replaceable> FROM <replaceable>source</replaceable>)
-</synopsis>
-
-   <para>
-    The <function>extract</function> function retrieves sub-fields
-    from date/time values, such as year or hour.
-    <replaceable>source</replaceable> is a value expression that
-    evaluates to type <type>timestamp</type> or <type>interval</type>.
-    (Expressions of type <type>date</type> or <type>time</type> will
-    be 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 values:
-
-    <!-- alphabetical -->
-    <variablelist>
-     <varlistentry>
-      <term><literal>century</literal></term>
-      <listitem>
-       <para>
-        The year field divided by 100
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>20</computeroutput>
-</screen>
-       </informalexample>
-
-       <para>
-        Note that the result for the century field is simply the year field
-        divided by 100, and not the conventional definition which puts most
-        years in the 1900's in the twentieth century.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>day</literal></term>
-      <listitem>
-       <para>
-        The day (of the month) field (1 - 31)
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>16</computeroutput>
-</screen>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>decade</literal></term>
-      <listitem>
-       <para>
-        The year field divided by 10
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(DECADE FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>200</computeroutput>
-</screen>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>dow</literal></term>
-      <listitem>
-       <para>
-        The day of the week (0 - 6; Sunday is 0) (for
-        <type>timestamp</type> values only)
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>5</computeroutput>
-</screen>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>doy</literal></term>
-      <listitem>
-       <para>
-        The day of the year (1 - 365/366) (for <type>timestamp</type> values only)
-       </para>
-       <informalexample>
-<screen>
-SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>47</computeroutput>
-</screen>
-       </informalexample>
-      </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-00 (Result may be
-        negative.); for <type>interval</type> values, the total number
-        of seconds in the interval
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(EPOCH FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>982352320</computeroutput>
-
-SELECT EXTRACT(EPOCH FROM INTERVAL '5 days 3 hours');
-<lineannotation>Result: </lineannotation><computeroutput>442800</computeroutput>
-</screen>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>hour</literal></term>
-      <listitem>
-       <para>
-        The hour field (0 - 23)
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(HOUR FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>20</computeroutput>
-</screen>
-       </informalexample>
-      </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>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(MICROSECONDS FROM TIME '17:12:28.5');
-<lineannotation>Result: </lineannotation><computeroutput>28500000</computeroutput>
-</screen>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>millennium</literal></term>
-      <listitem>
-       <para>
-        The year field divided by 1000
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>2</computeroutput>
-</screen>
-       </informalexample>
-
-       <para>
-        Note that the result for the millennium field is simply the year field
-        divided by 1000, and not the conventional definition which puts
-        years in the 1900's in the second millennium.
-       </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>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(MILLISECONDS FROM TIME '17:12:28.5');
-<lineannotation>Result: </lineannotation><computeroutput>28500</computeroutput>
-</screen>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>minute</literal></term>
-      <listitem>
-       <para>
-        The minutes field (0 - 59)
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>38</computeroutput>
-</screen>
-       </informalexample>
-      </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>
-
-       <informalexample>
-<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>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>quarter</literal></term>
-      <listitem>
-       <para>
-        The quarter of the year (1 - 4) that the day is in (for
-        <type>timestamp</type> values only)
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(QUARTER FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>1</computeroutput>
-</screen>
-       </informalexample>
-      </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>
-
-       <informalexample>
-<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>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-<!--
-     <varlistentry>
-      <term><literal>timezone</literal></term>
-      <listitem>
-       <para>
-        The time zone offset. XXX But in what units?
-       </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>
-        From a <type>timestamp</type> value, calculate 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>
-        week starts on Monday.)  In other words, the first Thursday of
-        a year is in week 1 of that year.
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(WEEK FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>7</computeroutput>
-</screen>
-       </informalexample>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>year</literal></term>
-      <listitem>
-       <para>
-        The year field
-       </para>
-
-       <informalexample>
-<screen>
-SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>2001</computeroutput>
-</screen>
-       </informalexample>
-      </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>
-
-   <anchor id="functions-datetime-datepart">
-   <para>
-    The <function>date_part</function> function is modeled on the traditional
-    <productname>Ingres</productname> equivalent to the
-    <acronym>SQL</acronym>-function <function>extract</function>:
-<synopsis>
-date_part('<replaceable>field</replaceable>', <replaceable>source</replaceable>)
-</synopsis>
-    Note that here the <replaceable>field</replaceable> value needs to
-    be a string.  The valid field values for
-    <function>date_part</function> are the same as for
-    <function>extract</function>.
-   </para>
-
-   <informalexample>
-<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>
-   </informalexample>
-
-  </sect2>
-
-  <sect2 id="functions-datetime-trunc">
-   <title><function>date_trunc</function></title>
-
-   <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> (values of type <type>date</type> and
-    <type>time</type> are cast automatically).
-    <replaceable>field</replaceable> selects to which precision to
-    truncate the time stamp value.  The return value is of type
-    <type>timestamp</type> with all fields that are less than the
-    selected one set to zero (or one, for day and month).
-   </para>
-
-   <para>
-    Valid values for <replaceable>field</replaceable> are:
-    <simplelist>
-     <member>microseconds</member>
-     <member>milliseconds</member>
-     <member>second</member>
-     <member>minute</member>
-     <member>hour</member>
-     <member>day</member>
-     <member>month</member>
-     <member>year</member>
-     <member>decade</member>
-     <member>century</member>
-     <member>millennium</member>
-    </simplelist>
-   </para>
-
-   <informalexample>
-    <para>
-<screen>
-SELECT date_trunc('hour', TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>2001-02-16 20:00:00+00</computeroutput>
-
-SELECT date_trunc('year', TIMESTAMP '2001-02-16 20:38:40');
-<lineannotation>Result: </lineannotation><computeroutput>2001-01-01 00:00:00+00</computeroutput>
-</screen>
-    </para>
-   </informalexample>
-  </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>
-
-   <para>
-    The following functions are available to obtain the current date and/or
-    time:
-     <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>
-     <function>CURRENT_TIME</function>,
-     <function>CURRENT_TIMESTAMP</function>,
-     <function>LOCALTIME</function>, and
-     <function>LOCALTIMESTAMP</function>
-     can optionally be given
-     a precision parameter, which causes the result to be rounded
-     to that many fractional digits.  Without a precision parameter,
-     the result is given to the full available precision.
-    </para>
-
-    <note>
-     <para>
-      Prior to <productname>PostgreSQL</productname> 7.2, the precision
-      parameters were unimplemented, and the result was always given
-      in integer seconds.
-     </para>
-    </note>
-
-    <informalexample>
-     <screen>
-SELECT CURRENT_TIME;
-<computeroutput>14:39:53.662522-05</computeroutput>
-
-SELECT CURRENT_DATE;
-<computeroutput>2001-12-23</computeroutput>
-
-SELECT CURRENT_TIMESTAMP;
-<computeroutput>2001-12-23 14:39:53.662522-05</computeroutput>
-
-SELECT CURRENT_TIMESTAMP(2);
-<computeroutput>2001-12-23 14:39:53.66-05</computeroutput>
-
-SELECT LOCALTIMESTAMP;
-<computeroutput>2001-12-23 14:39:53.662522</computeroutput>
-</screen>
-   </informalexample>
-
-   <para>
-    The function <function>now()</function> is the traditional
-    <productname>PostgreSQL</productname> equivalent to
-    <function>CURRENT_TIMESTAMP</function>.
-   </para>
-
-   <para>
-    There is also <function>timeofday()</function>, which for historical
-    reasons returns a text string rather than a <type>timestamp</type> value:
-   </para>
-
-   <informalexample>
-<screen>
-SELECT timeofday();
- Sat Feb 17 19:07:32.000126 2001 EST
-</screen>
-   </informalexample>
-
-   <para>
-    It is quite important to realize that
-    <function>CURRENT_TIMESTAMP</function> and related functions all return
-    the time as of the start of the current transaction; their values do not
-    increment while a transaction is running.  But
-    <function>timeofday()</function> returns the actual current time.
-   </para>
-
-   <para>
-    All the date/time data types also accept the special literal value
-    <literal>now</literal> to specify the current date and time.  Thus,
-    the following three all return the same result:
-<programlisting>
-SELECT CURRENT_TIMESTAMP;
-SELECT now();
-SELECT TIMESTAMP 'now';
-</programlisting>
-    <note>
-     <para>
-      You do not want to use the third form when specifying a DEFAULT
-      value 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>
-    </note>
-   </para>
-  </sect2>
- </sect1>
-
-  
- <sect1 id="functions-geometry">
-   <title>Geometric Functions and Operators</title>
-
-   <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.
-   </para>
-
-   <table>
-     <title>Geometric Operators</title>
-     <tgroup cols="3">
-      <thead>
-       <row>
-	<entry>Operator</entry>
-	<entry>Description</entry>
-	<entry>Usage</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry> + </entry>
-	<entry>Translation</entry>
-	<entry><literal>box '((0,0),(1,1))' + point '(2.0,0)'</literal></entry>
-       </row>
-       <row>
-	<entry> - </entry>
-	<entry>Translation</entry>
-	<entry><literal>box '((0,0),(1,1))' - point '(2.0,0)'</literal></entry>
-       </row>
-       <row>
-	<entry> * </entry>
-	<entry>Scaling/rotation</entry>
-	<entry><literal>box '((0,0),(1,1))' * point '(2.0,0)'</literal></entry>
-       </row>
-       <row>
-	<entry> / </entry>
-	<entry>Scaling/rotation</entry>
-	<entry><literal>box '((0,0),(2,2))' / point '(2.0,0)'</literal></entry>
-       </row>
-       <row>
-	<entry> # </entry>
-	<entry>Intersection</entry>
-	<entry><literal>'((1,-1),(-1,1))' # '((1,1),(-1,-1))'</literal></entry>
-       </row>
-       <row>
-	<entry> # </entry>
-	<entry>Number of points in polygon</entry>
-	<entry><literal># '((1,0),(0,1),(-1,0))'</literal></entry>
-       </row>
-       <row>
-	<entry> ## </entry>
-	<entry>Point of closest proximity</entry>
-	<entry><literal>point '(0,0)' ## lseg '((2,0),(0,2))'</literal></entry>
-       </row>
-       <row>
-	<entry> &amp;&amp; </entry>
-	<entry>Overlaps?</entry>
-	<entry><literal>box '((0,0),(1,1))' &amp;&amp; box '((0,0),(2,2))'</literal></entry>
-       </row>
-       <row>
-	<entry> &amp;&lt; </entry>
-	<entry>Overlaps to left?</entry>
-	<entry><literal>box '((0,0),(1,1))' &amp;&lt; box '((0,0),(2,2))'</literal></entry>
-       </row>
-       <row>
-	<entry> &amp;&gt; </entry>
-	<entry>Overlaps to right?</entry>
-	<entry><literal>box '((0,0),(3,3))' &amp;&gt; box '((0,0),(2,2))'</literal></entry>
-       </row>
-       <row>
-	<entry> &lt;-&gt; </entry>
-	<entry>Distance between</entry>
-	<entry><literal>circle '((0,0),1)' &lt;-&gt; circle '((5,0),1)'</literal></entry>
-       </row>
-       <row>
-	<entry> &lt;&lt; </entry>
-	<entry>Left of?</entry>
-	<entry><literal>circle '((0,0),1)' &lt;&lt; circle '((5,0),1)'</literal></entry>
-       </row>
-       <row>
-	<entry> &lt;^ </entry>
-	<entry>Is below?</entry>
-	<entry><literal>circle '((0,0),1)' &lt;^ circle '((0,5),1)'</literal></entry>
-       </row>
-       <row>
-	<entry> &gt;&gt; </entry>
-	<entry>Is right of?</entry>
-	<entry><literal>circle '((5,0),1)' &gt;&gt; circle '((0,0),1)'</literal></entry>
-       </row>
-       <row>
-	<entry> &gt;^ </entry>
-	<entry>Is above?</entry>
-	<entry><literal>circle '((0,5),1)' >^ circle '((0,0),1)'</literal></entry>
-       </row>
-       <row>
-	<entry> ?# </entry>
-	<entry>Intersects or overlaps</entry>
-	<entry><literal>lseg '((-1,0),(1,0))' ?# box '((-2,-2),(2,2))'</literal></entry>
-       </row>
-       <row>
-	<entry> ?- </entry>
-	<entry>Is horizontal?</entry>
-	<entry><literal>point '(1,0)' ?- point '(0,0)'</literal></entry>
-       </row>
-       <row>
-	<entry> ?-| </entry>
-	<entry>Is perpendicular?</entry>
-	<entry><literal>lseg '((0,0),(0,1))' ?-| lseg '((0,0),(1,0))'</literal></entry>
-       </row>
-       <row>
-	<entry> @-@  </entry>
-	<entry>Length or circumference</entry>
-	<entry><literal>@-@ path '((0,0),(1,0))'</literal></entry>
-       </row>
-       <row>
-	<entry> ?| </entry>
-	<entry>Is vertical?</entry>
-	<entry><literal>point '(0,1)' ?| point '(0,0)'</literal></entry>
-       </row>
-       <row>
-	<entry> ?|| </entry>
-	<entry>Is parallel?</entry>
-	<entry><literal>lseg '((-1,0),(1,0))' ?|| lseg '((-1,2),(1,2))'</literal></entry>
-       </row>
-       <row>
-	<entry> @ </entry>
-	<entry>Contained or on</entry>
-	<entry><literal>point '(1,1)' @ circle '((0,0),2)'</literal></entry>
-       </row>
-       <row>
-	<entry> @@ </entry>
-	<entry>Center of</entry>
-	<entry><literal>@@ circle '((0,0),10)'</literal></entry>
-       </row>
-       <row>
-	<entry> ~= </entry>
-	<entry>Same as</entry>
-	<entry><literal>polygon '((0,0),(1,1))' ~= polygon '((1,1),(0,0))'</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-   </table>
-
-   <table>
-     <title>Geometric Functions</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>Function</entry>
-	<entry>Returns</entry>
-	<entry>Description</entry>
-	<entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><function>area</function>(object)</entry>
-	<entry><type>double precision</type></entry>
-	<entry>area of item</entry>
-	<entry><literal>area(box '((0,0),(1,1))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>box</function>(box, box)</entry>
-	<entry><type>box</type></entry>
-	<entry>intersection box</entry>
-	<entry><literal>box(box '((0,0),(1,1))',box '((0.5,0.5),(2,2))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>center</function>(object)</entry>
-	<entry><type>point</type></entry>
-	<entry>center of item</entry>
-	<entry><literal>center(box '((0,0),(1,2))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>diameter</function>(circle)</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><function>height</function>(box)</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><function>isclosed</function>(path)</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><function>isopen</function>(path)</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><function>length</function>(object)</entry>
-	<entry><type>double precision</type></entry>
-	<entry>length of item</entry>
-	<entry><literal>length(path '((-1,0),(1,0))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>pclose</function>(path)</entry>
-	<entry><type>path</type></entry>
-	<entry>convert path to closed</entry>
-	<entry><literal>popen(path '[(0,0),(1,1),(2,0)]')</literal></entry>
-       </row>
-<![IGNORE[
-<!-- Not defined by this name. Implements the intersection operator '#' -->
-       <row>
-	<entry><function>point</function>(lseg,lseg)</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><function>npoint</function>(path)</entry>
-	<entry><type>integer</type></entry>
-	<entry>number of points</entry>
-	<entry><literal>npoints(path '[(0,0),(1,1),(2,0)]')</literal></entry>
-       </row>
-       <row>
-	<entry><function>popen</function>(path)</entry>
-	<entry><type>path</type></entry>
-	<entry>convert path to open path</entry>
-	<entry><literal>popen(path '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>radius</function>(circle)</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><function>width</function>(box)</entry>
-	<entry><type>double precision</type></entry>
-	<entry>horizontal size</entry>
-	<entry><literal>width(box '((0,0),(1,1))')</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-   </table>
-
-
-   <table>
-     <title>Geometric Type Conversion Functions</title>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>Function</entry>
-	<entry>Returns</entry>
-	<entry>Description</entry>
-	<entry>Example</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><function>box</function>(<type>circle</type>)</entry>
-	<entry><type>box</type></entry>
-	<entry>circle to box</entry>
-	<entry><literal>box(circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-	<entry><function>box</function>(<type>point</type>, <type>point</type>)</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><function>box</function>(<type>polygon</type>)</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><function>circle</function>(<type>box</type>)</entry>
-	<entry><type>circle</type></entry>
-	<entry>to circle</entry>
-	<entry><literal>circle(box '((0,0),(1,1))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>circle</function>(<type>point</type>, <type>double precision</type>)</entry>
-	<entry><type>circle</type></entry>
-	<entry>point to circle</entry>
-	<entry><literal>circle(point '(0,0)', 2.0)</literal></entry>
-       </row>
-       <row>
-	<entry><function>lseg</function>(<type>box</type>)</entry>
-	<entry><type>lseg</type></entry>
-	<entry>box diagonal to <type>lseg</type></entry>
-	<entry><literal>lseg(box '((-1,0),(1,0))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>lseg</function>(<type>point</type>, <type>point</type>)</entry>
-	<entry><type>lseg</type></entry>
-	<entry>points to <type>lseg</type></entry>
-	<entry><literal>lseg(point '(-1,0)', point '(1,0)')</literal></entry>
-       </row>
-       <row>
-	<entry><function>path</function>(<type>polygon</type>)</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><function>point</function>(<type>circle</type>)</entry>
-	<entry><type>point</type></entry>
-	<entry>center</entry>
-	<entry><literal>point(circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-	<entry><function>point</function>(<type>lseg</type>, <type>lseg</type>)</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><function>point</function>(<type>polygon</type>)</entry>
-	<entry><type>point</type></entry>
-	<entry>center</entry>
-	<entry><literal>point(polygon '((0,0),(1,1),(2,0))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>polygon</function>(<type>box</type>)</entry>
-	<entry><type>polygon</type></entry>
-	<entry>12 point polygon</entry>
-	<entry><literal>polygon(box '((0,0),(1,1))')</literal></entry>
-       </row>
-       <row>
-	<entry><function>polygon</function>(<type>circle</type>)</entry>
-	<entry><type>polygon</type></entry>
-	<entry>12-point polygon</entry>
-	<entry><literal>polygon(circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-	<entry><function>polygon</function>(<replaceable class="parameter">npts</replaceable>, <type>circle</type>)</entry>
-	<entry><type>polygon</type></entry>
-	<entry><replaceable class="parameter">npts</replaceable> polygon</entry>
-	<entry><literal>polygon(12, circle '((0,0),2.0)')</literal></entry>
-       </row>
-       <row>
-	<entry><function>polygon</function>(<type>path</type>)</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>
-
-  </sect1>
-
-
-  <sect1 id="functions-net">
-   <title>Network Address Type Functions</title>
-
-
-    <table tocentry="1" 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>Usage</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry> &lt; </entry>
-	<entry>Less than</entry>
-	<entry><literal>inet '192.168.1.5' &lt; inet '192.168.1.6'</literal></entry>
-       </row>
-       <row>
-	<entry> &lt;= </entry>
-	<entry>Less than or equal</entry>
-	<entry><literal>inet '192.168.1.5' &lt;= inet '192.168.1.5'</literal></entry>
-       </row>
-       <row>
-	<entry> = </entry>
-	<entry>Equals</entry>
-	<entry><literal>inet '192.168.1.5' = inet '192.168.1.5'</literal></entry>
-       </row>
-       <row>
-	<entry> &gt;= </entry>
-	<entry>Greater or equal</entry>
-	<entry><literal>inet '192.168.1.5' &gt;= inet '192.168.1.5'</literal></entry>
-       </row>
-       <row>
-	<entry> &gt; </entry>
-	<entry>Greater</entry>
-	<entry><literal>inet '192.168.1.5' &gt; inet '192.168.1.4'</literal></entry>
-       </row>
-       <row>
-	<entry> &lt;&gt; </entry>
-	<entry>Not equal</entry>
-	<entry><literal>inet '192.168.1.5' &lt;&gt; inet '192.168.1.4'</literal></entry>
-       </row>
-       <row>
-	<entry> &lt;&lt; </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> &lt;&lt;= </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> &gt;&gt; </entry>
-	<entry>contains</entry>
-	<entry><literal>inet'192.168.1/24' &gt;&gt; inet '192.168.1.5'</literal></entry>
-       </row>
-       <row>
-	<entry> &gt;&gt;= </entry>
-	<entry>contains or equals</entry>
-	<entry><literal>inet '192.168.1/24' &gt;&gt;= inet '192.168.1/24'</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-    <para>
-     All of the operators for <type>inet</type> can be applied to
-     <type>cidr</type> values as well.  The operators
-     <literal>&lt;&lt;</literal>, <literal>&lt;&lt;=</literal>,
-     <literal>&gt;&gt;</literal>, <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 part is identical to or a subnet of the other.
-    </para>
-
-
-    <table tocentry="1" id="cidr-inet-functions">
-     <title><type>cidr</type> and <type>inet</type> Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-	<entry>Function</entry>
-	<entry>Returns</entry>
-	<entry>Description</entry>
-	<entry>Example</entry>
-	<entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><function>broadcast</function>(<type>inet</type>)</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><function>host</function>(<type>inet</type>)</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><function>masklen</function>(<type>inet</type>)</entry>
-	<entry><type>integer</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><function>set_masklen</function>(<type>inet</type>,<type>integer</type>)</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><function>netmask</function>(<type>inet</type>)</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><function>network</function>(<type>inet</type>)</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><function>text</function>(<type>inet</type>)</entry>
-	<entry><type>text</type></entry>
-	<entry>extract IP address and masklen as text</entry>
-	<entry><literal>text(inet '192.168.1.5')</literal></entry>
-	<entry><literal>192.168.1.5/32</literal></entry>
-       </row>
-       <row>
-	<entry><function>abbrev</function>(<type>inet</type>)</entry>
-	<entry><type>text</type></entry>
-	<entry>extract abbreviated display as text</entry>
-	<entry><literal>abbrev(cidr '10.1.0.0/16')</literal></entry>
-	<entry><literal>10.1/16</literal></entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-
-   <para>
-    All of the functions for <type>inet</type> can be applied to
-    <type>cidr</type> values as well.  The <function>host</function>(),
-    <function>text</function>(), and <function>abbrev</function>() functions are primarily
-    intended to offer alternative display formats. You can cast a text
-    field to inet using normal casting syntax: <literal>inet(expression)</literal> or 
-    <literal>colname::inet</literal>.
-   </para>
-
-    <table tocentry="1" id="macaddr-functions">
-     <title><type>macaddr</type> Functions</title>
-     <tgroup cols="5">
-      <thead>
-       <row>
-	<entry>Function</entry>
-	<entry>Returns</entry>
-	<entry>Description</entry>
-	<entry>Example</entry>
-	<entry>Result</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><function>trunc</function>(<type>macaddr</type>)</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 function <function>trunc</function>(<type>macaddr</type>) returns a MAC
-    address with the last 3 bytes set to 0.  This can be used to
-    associate the remaining prefix with a manufacturer.  The directory
-    <filename>contrib/mac</filename> in the source distribution contains some
-    utilities to create and maintain such an association table.
-   </para>
-
-   <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-sequence">
-  <title>Sequence-Manipulation Functions</title>
-
-  <indexterm>
-   <primary>sequences</primary>
-  </indexterm>
-  <indexterm>
-   <primary>nextval</primary>
-  </indexterm>
-  <indexterm>
-   <primary>currval</primary>
-  </indexterm>
-  <indexterm>
-   <primary>setval</primary>
-  </indexterm>
-
-   <table>
-    <title>Sequence Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Function</entry> <entry>Returns</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-	<entry><function>nextval</function>(<type>text</type>)</entry>
-	<entry><type>bigint</type></entry>
-	<entry>Advance sequence and return new value</entry>
-      </row>
-      <row>
-	<entry><function>currval</function>(<type>text</type>)</entry>
-	<entry><type>bigint</type></entry>
-	<entry>Return value most recently obtained with <function>nextval</function></entry>
-      </row>
-      <row>
-	<entry><function>setval</function>(<type>text</type>,<type>bigint</type>)</entry>
-	<entry><type>bigint</type></entry>
-	<entry>Set sequence's current value</entry>
-      </row>
-      <row>
-	<entry><function>setval</function>(<type>text</type>,<type>bigint</type>,<type>boolean</type>)</entry>
-	<entry><type>bigint</type></entry>
-	<entry>Set sequence's current value and <literal>is_called</literal> flag</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-  <para>
-   This section describes <productname>PostgreSQL</productname>'s functions
-   for operating on <firstterm>sequence objects</firstterm>.
-   Sequence objects (also called sequence generators or
-   just sequences) are special single-row tables created with
-   <command>CREATE SEQUENCE</command>.  A sequence object is usually used to
-   generate unique identifiers for rows of a table.  The sequence functions
-   provide simple, multiuser-safe methods for obtaining successive
-   sequence values from sequence objects.
-  </para>
-
-  <para>
-   For largely historical reasons, the sequence to be operated on by
-   a sequence-function call is specified by a text-string argument.
-   To achieve some compatibility with the handling of ordinary SQL
-   names, the sequence functions convert their argument to lower case
-   unless the string is double-quoted.  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>
-   Of course, the text argument can be the result of an expression,
-   not only a simple literal, which is occasionally useful.
-  </para>
-
-  <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 server processes
-	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 server process.  (An error is
-	reported if <function>nextval</function> has never been called for this
-	sequence in this process.)  Notice that because this is returning
-	a process-local value, it gives a predictable answer even if other
-	server processes are executing <function>nextval</function> meanwhile.
-       </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.  In the three-parameter form,
-	<literal>is_called</literal> may be set either <literal>true</literal> or
-	<literal>false</literal>.  If it's 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>.  For example,
-       </para>
-
-       <informalexample>
-<screen>
-SELECT setval('foo', 42);           <lineannotation>Next nextval() will return 43</lineannotation>
-SELECT setval('foo', 42, true);     <lineannotation>Same as above</lineannotation>
-SELECT setval('foo', 42, false);    <lineannotation>Next nextval() will return 42</lineannotation>
-</screen>
-       </informalexample>
-
-       <para>
-        The result returned by <function>setval</function> is just the value of its
-	second argument.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-  </para>
-
-  <important>
-   <para>
-    To avoid blocking of 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 may leave unused <quote>holes</quote> in the
-    sequence of assigned values.  <function>setval</function> operations are never
-    rolled back, either.
-   </para>
-  </important>
-
-  <para>
-   If a sequence object has been created with default parameters,
-   <function>nextval()</function> calls on it will return successive values
-   beginning with one.  Other behaviors can be obtained by using
-   special parameters in the <command>CREATE SEQUENCE</command> command;
-   see its command reference page for more information.
-  </para>
-
- </sect1>
-
-
- <sect1 id="functions-conditional">
-  <title>Conditional Expressions</title>
-
-  <indexterm>
-   <primary>case</primary>
-  </indexterm>
-
-  <indexterm>
-   <primary>conditionals</primary>
-  </indexterm>
-
-  <para>
-   This section describes the <acronym>SQL</acronym>-compliant conditional expressions
-   available in <productname>PostgreSQL</productname>.
-  </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>
-
-  <bridgehead renderas="sect2">CASE</bridgehead>
-
-<synopsis>
-CASE WHEN <replaceable>condition</replaceable> THEN <replaceable>result</replaceable>
-     <optional>WHEN ...</optional>
-     <optional>ELSE <replaceable>result</replaceable></optional>
-END
-</synopsis>
-
-  <para>
-   The <acronym>SQL</acronym> <token>CASE</token> expression is a
-   generic conditional expression, similar to if/else statements in
-   other languages.  <token>CASE</token> clauses can be used wherever
-   an expression is valid.  <replaceable>condition</replaceable> is an
-   expression that returns a <type>boolean</type> result.  If the result is true
-   then the value of the <token>CASE</token> expression is
-   <replaceable>result</replaceable>.  If the result is false any
-   subsequent <token>WHEN</token> clauses are searched in the same
-   manner.  If no <token>WHEN</token>
-   <replaceable>condition</replaceable> is true then the value of the
-   case expression is the <replaceable>result</replaceable> in the
-   <token>ELSE</token> clause.  If the <token>ELSE</token> clause is
-   omitted and no condition matches, the result is NULL.
-  </para>
-
-  <informalexample>
-   <para>
-    An example:
-<screen>
-<prompt>=&gt;</prompt> <userinput>SELECT * FROM test;</userinput>
-<computeroutput>
- a
----
- 1
- 2
- 3
-</computeroutput>
-
-<prompt>=&gt;</prompt> <userinput>SELECT a,
-          CASE WHEN a=1 THEN 'one'
-               WHEN a=2 THEN 'two'
-               ELSE 'other'
-          END
-    FROM test;</userinput>
-<computeroutput>
- a | case
----+-------
- 1 | one
- 2 | two
- 3 | other
-</computeroutput>
-</screen>
-   </para>
-  </informalexample>
-
-  <para>
-   The data types of all the <replaceable>result</replaceable>
-   expressions must be coercible to a single output type.
-   See <xref linkend="typeconv-union-case"> for more detail.
-  </para>
-
-<synopsis>
-CASE <replaceable>expression</replaceable>
-    WHEN <replaceable>value</replaceable> THEN <replaceable>result</replaceable>
-    <optional>WHEN ...</optional>
-    <optional>ELSE <replaceable>result</replaceable></optional>
-END
-</synopsis>
-
-  <para>
-   This <quote>simple</quote> <token>CASE</token> expression is a
-   specialized variant of the general form above.  The
-   <replaceable>expression</replaceable> is computed and compared to
-   all the <replaceable>value</replaceable>s in the
-   <token>WHEN</token> clauses until one is found that is equal.  If
-   no match is found, the <replaceable>result</replaceable> in the
-   <token>ELSE</token> clause (or NULL) is returned.  This is similar
-   to the <function>switch</function> statement in C.
-  </para>
-
-  <informalexample>
-   <para>
-    The example above can be written using the simple
-    <token>CASE</token> syntax:
-<screen>
-<prompt>=&gt;</prompt> <userinput>SELECT a,
-          CASE a WHEN 1 THEN 'one'
-                 WHEN 2 THEN 'two'
-                 ELSE 'other'
-          END
-    FROM test;</userinput>
-<computeroutput>
- a | case
----+-------
- 1 | one
- 2 | two
- 3 | other
-</computeroutput>
-</screen>
-    </para>
-   </informalexample>
-
-   <bridgehead renderas="sect2">COALESCE</bridgehead>
-
-<synopsis>
-<function>COALESCE</function>(<replaceable>value</replaceable><optional
-     >, ...</optional>)
-</synopsis>
-
-  <para>
-   The <function>COALESCE</function> function returns the first of its
-   arguments that is not NULL.  This is often useful 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>
-
- <bridgehead renderas="sect2">NULLIF</bridgehead>
-
-  <indexterm>
-   <primary>nullif</primary>
-  </indexterm>
-
-<synopsis>
-<function>NULLIF</function>(<replaceable>value1</replaceable>,
-    <replaceable>value2</replaceable>)
-</synopsis>
-
-  <para>
-   The <function>NULLIF</function> function returns NULL if and only
-   if <replaceable>value1</replaceable> and
-   <replaceable>value2</replaceable> are equal.  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>
-
-  <tip>
-   <para>
-    <function>COALESCE</function> and <function>NULLIF</function> are
-    just shorthand for <token>CASE</token> expressions.  They are actually
-    converted into <token>CASE</token> expressions at a very early stage
-    of processing, and subsequent processing thinks it is dealing with
-    <token>CASE</token>.  Thus an incorrect <function>COALESCE</function> or
-    <function>NULLIF</function> usage may draw an error message that
-    refers to <token>CASE</token>.
-   </para>
-  </tip>
-
- </sect1>
-
-
-  <sect1 id="functions-misc">
-   <title>Miscellaneous Functions</title>
-
-   <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><function>current_user</function></entry>
-       <entry><type>name</type></entry>
-       <entry>user name of current execution context</entry>
-      </row>
-      <row>
-       <entry><function>session_user</function></entry>
-       <entry><type>name</type></entry>
-       <entry>session user name</entry>
-      </row>
-      <row>
-       <entry><function>user</function></entry>
-       <entry><type>name</type></entry>
-       <entry>equivalent to <function>current_user</function></entry>
-      </row>
-      <row>
-       <entry><function>current_schema()</function></entry>
-       <entry><type>name</type></entry>
-       <entry>name of current schema</entry>
-      </row>
-      <row>
-       <entry><function>current_schemas(boolean)</function></entry>
-       <entry><type>name[]</type></entry>
-       <entry>names of schemas in search path optionally including implicit schemas</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm zone="functions-misc">
-    <primary>user</primary>
-    <secondary>current</secondary>
-   </indexterm>
-
-   <indexterm zone="functions-misc">
-    <primary>schema</primary>
-    <secondary>current</secondary>
-   </indexterm>
-
-   <indexterm zone="functions-misc">
-    <primary>search path</primary>
-    <secondary>current</secondary>
-   </indexterm>
-
-   <para>
-    The <function>session_user</function> is the user that initiated a
-    database connection; it is fixed for the duration of that
-    connection. 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 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>
-
-   <note>
-    <para>
-     <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 parentheses.
-    </para>
-   </note>
-
-   <note>
-    <title>Deprecated</title>
-    <para>
-     The function <function>getpgusername()</function> is an obsolete equivalent
-     of <function>current_user</function>.
-    </para>
-   </note>
-
-   <para>
-    <function>current_schema</function> returns the name of the schema that is
-    at the front of the search path (or NULL 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 pg_catalog are included in the search 
-    path returned.
-   </para>
-
-   <table>
-    <title>System Information Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><function>version</function></entry>
-       <entry><type>text</type></entry>
-       <entry>PostgreSQL version information</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm zone="functions-misc">
-    <primary>version</primary>
-   </indexterm>
-
-   <para>
-    <function>version()</function> returns a string describing the PostgreSQL
-    server's version.
-   </para>
-
-   <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><function>has_table_privilege</function>(<parameter>user</parameter>,
-                                  <parameter>table</parameter>,
-                                  <parameter>access</parameter>)
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does user have access to table</entry>
-      </row>
-      <row>
-       <entry><function>has_table_privilege</function>(<parameter>table</parameter>,
-                                  <parameter>access</parameter>)
-       </entry>
-       <entry><type>boolean</type></entry>
-       <entry>does current user have access to table</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm zone="functions-misc">
-    <primary>has_table_privilege</primary>
-   </indexterm>
-
-   <para>
-    <function>has_table_privilege</function> determines whether a user
-    can access a table in a particular way.  The user can be
-    specified by name or by ID
-    (<classname>pg_user</classname>.<structfield>usesysid</structfield>), 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 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>RULE</literal>, <literal>REFERENCES</literal>, or
-    <literal>TRIGGER</literal>.  (Case of the string is not significant, however.)
-    An example is:
-<programlisting>
-SELECT has_table_privilege('myschema.mytable', 'select');
-</programlisting>
-   </para>
-
-   <table>
-    <title>Catalog Information Functions</title>
-    <tgroup cols="3">
-     <thead>
-      <row><entry>Name</entry> <entry>Return Type</entry> <entry>Description</entry></row>
-     </thead>
-
-     <tbody>
-      <row>
-       <entry><function>pg_get_viewdef</function>(<parameter>viewname</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Get CREATE VIEW command for view</entry>
-      </row>
-      <row>
-       <entry><function>pg_get_viewdef</function>(<parameter>viewOID</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Get CREATE VIEW command for view</entry>
-      </row>
-      <row>
-       <entry><function>pg_get_ruledef</function>(<parameter>ruleOID</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Get CREATE RULE command for rule</entry>
-      </row>
-      <row>
-       <entry><function>pg_get_indexdef</function>(<parameter>indexOID</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Get CREATE INDEX command for index</entry>
-      </row>
-      <row>
-       <entry><function>pg_get_userbyid</function>(<parameter>userid</parameter>)</entry>
-       <entry><type>name</type></entry>
-       <entry>Get user name given ID</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm zone="functions-misc">
-    <primary>pg_get_viewdef</primary>
-   </indexterm>
-
-   <indexterm zone="functions-misc">
-    <primary>pg_get_ruledef</primary>
-   </indexterm>
-
-   <indexterm zone="functions-misc">
-    <primary>pg_get_indexdef</primary>
-   </indexterm>
-
-   <indexterm zone="functions-misc">
-    <primary>pg_get_userbyid</primary>
-   </indexterm>
-
-   <para>
-    These functions extract information from the system catalogs.
-    <function>pg_get_viewdef()</function>, <function>pg_get_ruledef()</function>, and
-    <function>pg_get_indexdef()</function> respectively reconstruct the creating
-    command for a view, rule, or index.  (Note that this is a decompiled
-    reconstruction, not the verbatim text of the command.)
-    <function>pg_get_userbyid()</function> extracts a user's name given a
-    <structfield>usesysid</structfield> value.
-   </para>
-
-   <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><function>obj_description</function>(<parameter>objectOID</parameter>, <parameter>tablename</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Get comment for a database object</entry>
-      </row>
-      <row>
-       <entry><function>obj_description</function>(<parameter>objectOID</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Get comment for a database object (<emphasis>deprecated</emphasis>)</entry>
-      </row>
-      <row>
-       <entry><function>col_description</function>(<parameter>tableOID</parameter>, <parameter>columnnumber</parameter>)</entry>
-       <entry><type>text</type></entry>
-       <entry>Get comment for a table column</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-
-   <indexterm zone="functions-misc">
-    <primary>obj_description</primary>
-   </indexterm>
-
-   <indexterm zone="functions-misc">
-    <primary>col_description</primary>
-   </indexterm>
-
-   <para>
-    These functions extract comments previously stored with the
-    <command>COMMENT</command> command.  <literal>NULL</literal> is returned if
-    no comment can be found matching the specified parameters.
-   </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 a table with OID 123456.
-    The one-parameter form of <function>obj_description()</function> requires only
-    the object OID.  It is now deprecated since there is no guarantee that
-    OIDs are unique across different system catalogs; therefore, the wrong
-    comment could be returned.
-   </para>
-
-   <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>
-
-  </sect1>
-
-
- <sect1 id="functions-aggregate">
-  <title>Aggregate Functions</title>
-
-  <note>
-   <title>Author</title>
-   <para>
-    Written by Isaac Wilcox <email>isaac@azartmedia.com</email> on 2000-06-16
-   </para>
-  </note>
-
-  <para>
-   <firstterm>Aggregate functions</firstterm> compute a single result
-   value from a set of input values.  The special syntax
-   considerations for aggregate functions are explained in <xref
-                                                                 linkend="syntax-aggregates">.  Consult the <citetitle>PostgreSQL
-   Tutorial</citetitle> for additional introductory information.
-  </para>
-
-  <table tocentry="1">
-   <title>Aggregate Functions</title>
-
-   <tgroup cols="3">
-    <thead>
-     <row>
-      <entry>Function</entry>
-      <entry>Description</entry>
-      <entry>Notes</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry>avg(<replaceable class="parameter">expression</replaceable>)</entry>
-      <entry>the average (arithmetic mean) of all input values</entry>
-      <entry>
-       <indexterm>
-        <primary>average</primary>
-        <secondary>function</secondary>
-       </indexterm>
-       Finding the average value is available on the following data
-       types: <type>smallint</type>, <type>integer</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, <type>numeric</type>, <type>interval</type>.
-       The result is of type <type>numeric</type> for any integer type
-       input, <type>double precision</type> for floating-point input,
-       otherwise the same as the input data type.
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>count</function>(*)</entry>
-      <entry>number of input values</entry>
-      <entry>The return value is of type <type>bigint</type>.</entry>
-     </row>
-
-     <row>
-      <entry><function>count</function>(<replaceable class="parameter">expression</replaceable>)</entry>
-      <entry>
-       Counts the input values for which the value of <replaceable
-                                                                   class="parameter">expression</replaceable> is not NULL.
-      </entry>
-      <entry>The return value is of type <type>bigint</type>.</entry>
-     </row>
-
-     <row>
-      <entry><function>max</function>(<replaceable class="parameter">expression</replaceable>)</entry>
-      <entry>the maximum value of <replaceable class="parameter">expression</replaceable> across all input values</entry>
-      <entry>
-       Available for all numeric, string, and date/time types.  The
-       result has the same type as the input expression.
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>min</function>(<replaceable class="parameter">expression</replaceable>)</entry>
-      <entry>the minimum value of <replaceable class="parameter">expression</replaceable> across all input values</entry>
-      <entry>
-       Available for all numeric, string, and date/time types.  The
-       result has the same type as the input expression.
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>stddev</function>(<replaceable
-                                                      class="parameter">expression</replaceable>)</entry>
-      <entry>the sample standard deviation of the input values</entry>
-      <entry>
-       <indexterm>
-        <primary>standard deviation</primary>
-       </indexterm>
-       Finding the standard deviation is available on the following
-       data types: <type>smallint</type>, <type>integer</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, <type>numeric</type>.  The result is of type
-       <type>double precision</type> for floating-point input,
-       otherwise <type>numeric</type>.
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>sum</function>(<replaceable class="parameter">expression</replaceable>)</entry>
-      <entry>sum of <replaceable class="parameter">expression</replaceable> across all input values</entry>
-      <entry>
-       Summation is available on the following data types:
-       <type>smallint</type>, <type>integer</type>,
-       <type>bigint</type>, <type>real</type>, <type>double
-       precision</type>, <type>numeric</type>, <type>interval</type>.
-       The result is of type <type>bigint</type> for <type>smallint</type>
-       or <type>integer</type> input, <type>numeric</type> for
-       <type>bigint</type> 
-       input, <type>double precision</type> for floating-point input,
-       otherwise the same as the input data type.
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>variance</function>(<replaceable
-                                                        class="parameter">expression</replaceable>)</entry>
-      <entry>the sample variance of the input values</entry>
-      <entry>
-       <indexterm>
-        <primary>variance</primary>
-       </indexterm>
-       The variance is the square of the standard deviation.  The
-       supported data types and result types are the same as for
-       standard deviation.
-      </entry>
-     </row>
-
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-   It should be noted that except for <function>COUNT</function>,
-   these functions return NULL when no rows are selected.  In
-   particular, <function>SUM</function> of no rows returns NULL, not
-   zero as one might expect.  <function>COALESCE</function> may be
-   used to substitute zero for NULL when necessary.
-  </para>
-
- </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>subqueries</primary>
-  </indexterm>
-
-  <para>
-   This section describes the <acronym>SQL</acronym>-compliant subquery
-   expressions available in <productname>PostgreSQL</productname>.
-   All of the expression forms documented in this section return
-   Boolean (true/false) results.
-  </para>
-
-  <bridgehead renderas="sect2">EXISTS</bridgehead>
-
-<synopsis>
-EXISTS ( <replaceable>subquery</replaceable> )
-</synopsis>
-
-  <para>
-   The argument of <token>EXISTS</token> is an arbitrary 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
-   TRUE; if the subquery returns no rows, the result of <token>EXISTS</token> 
-   is 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 far 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 any side-effects (such as
-   calling sequence functions); whether the side-effects occur or not
-   may be difficult to predict.
-  </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 uninteresting.  A common coding convention is
-   to write all 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 col2, but it produces at
-   most one output row for each tab1 row, even if there are multiple matching
-   tab2 rows:
-<screen>
-SELECT col1 FROM tab1
-    WHERE EXISTS(SELECT 1 FROM tab2 WHERE col2 = tab1.col2);
-</screen>
-  </para>
-
-   <bridgehead renderas="sect2">IN (scalar form)</bridgehead>
-
-<synopsis>
-<replaceable>expression</replaceable> IN
- <replaceable>ble>value</replaceable><optional>, ...</optional>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>IN</token> is a parenthesized list
-   of scalar expressions.  The result is 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>
-
-   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>
-
-  <note>
-  <para>
-   This form of <token>IN</token> is not truly a subquery expression, but it
-   seems best to document it in the same place as subquery <token>IN</token>.
-  </para>
-  </note>
-
-   <bridgehead renderas="sect2">IN (subquery form)</bridgehead>
-
-<synopsis>
-<replaceable>expression</replaceable> IN (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>IN</token> 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 TRUE if any equal subquery row is found.
-   The result is FALSE if no equal row is found (including the special
-   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>expression</replaceable>,
-<replaceable>ble>expres</replaceable><optional>nal>,</optional>nal>)
-    IN (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>IN</token> is a parenthesized
-   subquery, which must return exactly as many columns as there are
-   expressions in the left-hand list.  The left-hand expressions are
-   evaluated and compared row-wise to each row of the subquery result.
-   The result of <token>IN</token> is TRUE if any equal subquery row is found.
-   The result is FALSE if no equal row is found (including the special
-   case where the subquery returns no rows).
-  </para>
-
-  <para>
-   As usual, NULLs in the expressions or subquery 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 row results are either unequal or NULL, with at least one NULL,
-   then the result of <token>IN</token> is NULL.
-  </para>
-
-   <bridgehead renderas="sect2">NOT IN (scalar form)</bridgehead>
-
-<synopsis>
-<replaceable>expression</replaceable> NOT IN
- <replaceable>ble>value</replaceable><optional>, ...</optional>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>NOT IN</token> is a parenthesized list
-   of scalar expressions.  The result is TRUE 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>
-
-   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, NULLs are much more likely to trip up the novice when
-   working with <token>NOT IN</token> than when working with <token>IN</token>.
-   It's best to express your condition positively if possible.
-  </para>
-  </tip>
-
-   <bridgehead renderas="sect2">NOT IN (subquery form)</bridgehead>
-
-<synopsis>
-<replaceable>expression</replaceable> NOT IN (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>NOT IN</token> 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 TRUE if only unequal subquery rows
-   are found (including the special case where the subquery returns no rows).
-   The result is 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>expression</replaceable>,
-<replaceable>ble>expres</replaceable><optional>nal>,</optional>nal>)
-    NOT IN (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>NOT IN</token> is a parenthesized
-   subquery, which must return exactly as many columns as there are
-   expressions in the left-hand list.  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 TRUE if only unequal subquery rows
-   are found (including the special case where the subquery returns no rows).
-   The result is FALSE if any equal row is found.
-  </para>
-
-  <para>
-   As usual, NULLs in the expressions or subquery 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 row results are either unequal or NULL, with at least one NULL,
-   then the result of <token>NOT IN</token> is NULL.
-  </para>
-
-   <bridgehead renderas="sect2">ANY</bridgehead>
-
-<synopsis>
-<replaceable>expression</replaceable>
-<replaceable>ble>oper</replaceable>ble> ANY (<replaceable>subquery</replaceable>)
-<replaceable>expression</replaceable>
-<replaceable>ble>oper</replaceable>ble> SOME (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>ANY</token> 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 TRUE if any true result is obtained.
-   The result is FALSE if no true result is found (including the special
-   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>expression</replaceable>,
-<replaceable>ble>expres</replaceable><optional>nal>,</optional>optiona<replaceable>aceable></replaceable>aceable> ANY (<replaceable>subquery</replaceable>)
-(<replaceable>expression</replaceable>,
-<replaceable>ble>expres</replaceable><optional>nal>,</optional>optiona<replaceable>aceable></replaceable>aceable> SOME (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>ANY</token> is a parenthesized
-   subquery, which must return exactly as many columns as there are
-   expressions in the left-hand list.  The left-hand expressions are
-   evaluated and compared row-wise to each row of the subquery result,
-   using the given <replaceable>operator</replaceable>.  Presently,
-   only <literal>=</literal> and <literal>&lt;&gt;</literal> operators are allowed
-   in row-wise <token>ANY</token> queries.
-   The result of <token>ANY</token> is TRUE if any equal or unequal row is
-   found, respectively.
-   The result is FALSE if no such row is found (including the special
-   case where the subquery returns no rows).
-  </para>
-
-  <para>
-   As usual, NULLs in the expressions or subquery 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 there is at least one NULL row result, then the result of <token>ANY</token>
-   cannot be FALSE; it will be TRUE or NULL. 
-  </para>
-
-   <bridgehead renderas="sect2">ALL</bridgehead>
-
-<synopsis>
-<replaceable>expression</replaceable>
-<replaceable>ble>oper</replaceable>ble> ALL (<replaceable>subquery</replaceable>)
-</synopsis>
-
-  <para>
-   The right-hand side of this form of <token>ALL</token> 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 TRUE if all rows yield TRUE
-   (including the special case where the subquery returns no rows).
-   The result is FALSE if any false result is found.
-  </para>
-
-  <para>
-   <token>NOT IN</token> is equivalent to <literal>&lt;&gt; ALL</literal>.
-  </para>
-
-  <para>
-   Note that if there are no failures but at least one right-hand row yields
-   NULL for the operator's result, the result of the <token>ALL</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>expression</replaceable>, <replaceable>expression</replaceable><optional>, ...</optional>) <replaceable>operator</replaceable> ALL (<replaceable>subquery</replaceable>)
-   </synopsis>
-
-  <para>
-   The right-hand side of this form of <token>ALL</token> is a parenthesized
-   subquery, which must return exactly as many columns as there are
-   expressions in the left-hand list.  The left-hand expressions are
-   evaluated and compared row-wise to each row of the subquery result,
-   using the given <replaceable>operator</replaceable>.  Presently,
-   only <literal>=</literal> and <literal>&lt;&gt;</literal> operators are allowed
-   in row-wise <token>ALL</token> queries.
-   The result of <token>ALL</token> is TRUE if all subquery rows are equal
-   or unequal, respectively (including the special
-   case where the subquery returns no rows).
-   The result is FALSE if any row is found to be unequal or equal,
-   respectively.
-  </para>
-
-  <para>
-   As usual, NULLs in the expressions or subquery 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 there is at least one NULL row result, then the result of <token>ALL</token>
-   cannot be TRUE; it will be FALSE or NULL. 
-  </para>
-
-   <bridgehead renderas="sect2">Row-wise comparison</bridgehead>
-
-   <synopsis>
-(<replaceable>expression</replaceable>, <replaceable>expression</replaceable><optional>, ...</optional>) <replaceable>operator</replaceable> (<replaceable>subquery</replaceable>)
-(<replaceable>expression</replaceable>, <replaceable>expression</replaceable><optional>, ...</optional>) <replaceable>operator</replaceable> (<replaceable>expression</replaceable> <replaceable>expression</replaceable><optional>, ...</optional>)
-   </synopsis>
-
-  <para>
-   The left-hand side is a list of scalar expressions.  The right-hand side
-   can be either a list of scalar expressions of the same length, or a
-   parenthesized subquery, which must return exactly as many columns as there
-   are expressions on the left-hand side.  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, or to the right-hand expression list.
-   Presently, only <literal>=</literal> and <literal>&lt;&gt;</literal> operators are allowed
-   in row-wise comparisons.
-   The result is TRUE if the two rows are equal or unequal, respectively.
-  </para>
-
-  <para>
-   As usual, NULLs in the expressions or subquery 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 the row comparison is unknown (NULL).
-  </para>
-
- </sect1>
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/geqo.sgml b/doc/src/sgml/geqo.sgml
deleted file mode 100644
index b1d9a9670a5..00000000000
--- a/doc/src/sgml/geqo.sgml
+++ /dev/null
@@ -1,318 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/geqo.sgml,v 1.23 2002/01/20 22:19:56 petere Exp $
-Genetic Optimizer
--->
-
- <chapter id="geqo">
-  <docinfo>
-   <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>
-  </docinfo>
-
-  <title>Genetic Query Optimization</title>
-
-  <para>
-   <note>
-    <title>Author</title>
-    <para>
-     Written by Martin Utesch (<email>utesch@aut.tu-freiberg.de</email>)
-     for the Institute of Automatic Control at the University of Mining and Technology in Freiberg, Germany.
-    </para>
-   </note>
-  </para>
-
-  <sect1 id="geqo-intro">
-   <title>Query Handling as a Complex Optimization Problem</title>
-
-   <para>
-    Among all relational operators the most difficult one to process and
-    optimize is the <firstterm>join</firstterm>. The number of alternative plans to answer a query
-    grows exponentially with the number of joins included in it. 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., R-tree,
-    B-tree, hash in <productname>PostgreSQL</productname>) as access paths for relations.
-   </para>
-
-   <para>
-    The current <productname>PostgreSQL</productname> optimizer
-    implementation performs a <firstterm>near-exhaustive search</firstterm>
-    over the space of alternative strategies. This query 
-    optimization technique is inadequate to support database application
-    domains that involve the need for extensive queries, such as artificial
-    intelligence.
-   </para>
-
-   <para>
-    The Institute of Automatic Control at the University of Mining and
-    Technology, in Freiberg, Germany, encountered the described problems as its
-    folks wanted to take the <productname>PostgreSQL</productname> DBMS 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.
-   </para>
-
-   <para>
-    Performance difficulties in exploring the space of possible query
-    plans created the demand for a new optimization technique being developed.
-   </para>
-
-   <para>
-    In the following we propose the implementation of a <firstterm>Genetic Algorithm</firstterm>
-    as an option for the database query optimization problem.
-   </para>
-  </sect1>
-
-  <sect1 id="geqo-intro2">
-   <title>Genetic Algorithms</title>
-
-   <para>
-    The genetic algorithm (<acronym>GA</acronym>) is a heuristic optimization method which
-    operates through
-    determined, 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">
-+=========================================+
-|>>>>>>>>>>>  Algorithm GA  <<<<<<<<<<<<<<|
-+=========================================+
-| 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>
-
-   <para>
-    The <acronym>GEQO</acronym> module is intended for the solution of the query
-    optimization problem similar to a 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.
-    E. g., the query 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>
-    Parts of the <acronym>GEQO</acronym> module are adapted from D. Whitley's Genitor
-    algorithm.
-   </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>
-    The <acronym>GEQO</acronym> module allows
-    the <productname>PostgreSQL</productname> query optimizer to
-    support large join queries effectively through
-    non-exhaustive search.
-   </para>
-
-  <sect2 id="geqo-future">
-   <title>Future Implementation Tasks for
-    <productname>PostgreSQL</> <acronym>GEQO</acronym></title>
-
-     <para>
-      Work is still needed to improve the genetic algorithm parameter
-      settings.
-      In file <filename>backend/optimizer/geqo/geqo_params.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>
-
-   </sect2>
-  </sect1>
-
- <sect1 id="geqo-biblio">
-  <title>Further Readings</title>
-
-  <para>
-   The following resources contain additional information about
-   genetic algorithms:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <ulink url="http://surf.de.uu.net/encore/www/">The Hitch-Hiker's
-      Guide to Evolutionary Computation</ulink> (FAQ for <ulink
-      url="news://comp.ai.genetic">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="ELMA99">
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <xref linkend="FONG">
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/gist.sgml b/doc/src/sgml/gist.sgml
deleted file mode 100644
index 386526a3cc4..00000000000
--- a/doc/src/sgml/gist.sgml
+++ /dev/null
@@ -1,109 +0,0 @@
-<Chapter Id="gist">
-<DocInfo>
-<AuthorGroup>
-<Author>
-<FirstName>Gene</FirstName>
-<Surname>Selkov</Surname>
-</Author>
-</AuthorGroup>
-<Date>Transcribed 1998-02-19</Date>
-</DocInfo>
-<Title>GiST Indexes</Title>
-
-<Para>
-The information about GIST is at
- <ULink url="http://GiST.CS.Berkeley.EDU:8000/gist/">http://GiST.CS.Berkeley.EDU:8000/gist/</ULink>
-
-with more on different indexing and sorting schemes at
-<ULink url="http://s2k-ftp.CS.Berkeley.EDU:8000/personal/jmh/">http://s2k-ftp.CS.Berkeley.EDU:8000/personal/jmh/</ULink>.
-
-And there is more interesting reading at
-<ULink url="http://epoch.cs.berkeley.edu:8000/">http://epoch.cs.berkeley.edu:8000/</ULink> and
-<ULink url="http://www.sai.msu.su/~megera/postgres/gist/">http://www.sai.msu.su/~megera/postgres/gist/</ULink>.
-</para>
-
-<Para>
-<Note>
-<Title>Author</Title>
-<Para>
-This extraction from an email sent by 
-Eugene Selkov, Jr. (<email>selkovjr@mcs.anl.gov</email>)
-contains good information
-on GiST. Hopefully we will learn more in the future and update this information.
-- thomas 1998-03-01
-</Para>
-</Note>
-</para>
-<Para>
-Well, I can't say I quite understand what's going on, but at least
-I (almost) succeeded in porting GiST examples to linux. The GiST access
-method is already in the postgres tree (<FileName>src/backend/access/gist</FileName>).
-</para>
-<Para>
-<ULink url="ftp://s2k-ftp.cs.berkeley.edu/pub/gist/pggist/pggist.tgz">Examples at Berkeley</ULink>
-come with an overview of the methods and demonstrate spatial index 
-mechanisms for 2D boxes, polygons, integer intervals and text
-(see also <ULink url="http://gist.cs.berkeley.edu:8000/gist/">GiST at Berkeley</ULink>).
-In the box example, we
-are supposed to see a performance gain when using the GiST index; it did
-work for me but I do not have a reasonably large collection of boxes
-to check that. Other examples also worked, except polygons: I got an 
-error doing
-
-<ProgramListing>
-test=> CREATE INDEX pix ON polytmp
-test-> USING GIST (p:box gist_poly_ops) WITH (ISLOSSY);
-ERROR:  cannot open pix
-
-(PostgreSQL 6.3               Sun Feb  1 14:57:30 EST 1998)
-</ProgramListing>
-</para>
-<Para>
-I could not get sense of this error message; it appears to be something
-we'd rather ask the developers about (see also Note 4 below). What I
-would suggest here is that someone of you linux guys (linux==gcc?) fetch the 
-original sources quoted above and apply my patch (see attachment) and 
-tell us what you feel about it. Looks cool to me, but I would not like 
-to hold it up while there are so many competent people around.
-</para>
-<Para>
-A few notes on the sources:
-</para>
-<Para>
-1. I failed to make use of the original (HP-UX) Makefile and rearranged
-   the Makefile from the ancient postgres95 tutorial to do the job. I tried
-   to keep it generic, but I am a very poor makefile writer -- just did
-   some monkey work. Sorry about that, but I guess it is now a little
-   more portable that the original makefile.
-</para>
-<Para>
-2. I built the example sources right under pgsql/src (just extracted the
-   tar file there). The aforementioned Makefile assumes it is one level
-   below pgsql/src (in our case, in pgsql/src/pggist).
-</para>
-<Para>
-3. The changes I made to the *.c files were all about #include's,
-   function prototypes and typecasting. Other than that, I just threw 
-   away a bunch of unused vars and added a couple parentheses to please
-   gcc. I hope I did not screw up too much :)
-</para>
-<Para>
-4. There is a comment in polyproc.sql:
-
-<ProgramListing>
--- -- there's a memory leak in rtree poly_ops!!
--- -- CREATE INDEX pix2 ON polytmp USING RTREE (p poly_ops);
-</ProgramListing>
-
-   Roger that!! I thought it could be related to a number of
-   <ProductName>PostgreSQL</ProductName> versions
-   back and tried the query. My system went nuts and I had to shoot down
-   the postmaster in about ten minutes.
-</para>
-
-<Para>
-I will continue to look into GiST for a while, but I would also
-appreciate
-more examples of R-tree usage.
-</para>
-</Chapter>
diff --git a/doc/src/sgml/history.sgml b/doc/src/sgml/history.sgml
deleted file mode 100644
index 8f2d74117b5..00000000000
--- a/doc/src/sgml/history.sgml
+++ /dev/null
@@ -1,269 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.19 2002/01/07 02:29:12 petere Exp $
--->
-
-<sect1 id="history">
- <title>A Short History of <productname>PostgreSQL</productname></title>
-
- <para>
-  The object-relational database management system now known as 
-  <productname>PostgreSQL</productname> (and briefly called
-  <productname>Postgres95</productname>) is derived from the
-  <productname>POSTGRES</productname> package written at the University of
-  California at Berkeley.  With over a decade of
-  development behind it, <productname>PostgreSQL</productname> 
-  is the most advanced open-source database available anywhere,
-  offering multiversion concurrency control, supporting almost
-  all SQL constructs (including subselects, transactions, and
-  user-defined types and functions), and having a wide range of
-  language bindings available (including C, C++, Java, Perl, Tcl, and Python).
- </para>
-
- <sect2>
-  <title>The Berkeley <productname>POSTGRES</productname> Project</title>
-
-  <para>
-   Implementation of the <productname>POSTGRES</productname> 
-   <acronym>DBMS</acronym> 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 rewrite 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.
-   <productname>POSTGRES</productname>  became  the  primary  data manager
-   for  the
-   <ulink url="http://meteora.ucsd.edu/s2k/s2k_home.html">Sequoia 2000</ulink>
-   scientific computing project in late 1992.
-  </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>
-  <title><productname>Postgres95</productname></title>
-
-  <para>
-   In 1994, Andrew Yu and Jolly Chen
-   added a SQL language interpreter to <productname>POSTGRES</productname>.
-   <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. Aggregates were
-      re-implemented.  Support for the GROUP BY query clause was also added.
-      The <filename>libpq</filename> interface remained
-      available  for  <acronym>C</acronym>  
-      programs.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      In addition to the monitor program, a new program
-      (<application>psql</application>) was provided for interactive SQL queries
-      using <acronym>GNU</acronym> <application>Readline</application>.
-     </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> backend.
-     </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>
-   The emphasis during development of <productname>Postgres95</productname>
-   was on identifying and understanding existing problems in the backend code.
-   With <productname>PostgreSQL</productname>, 
-   the emphasis has shifted to augmenting features and capabilities, although
-   work continues in all areas.
-  </para>
-
-  <para>
-   Major enhancements in <productname>PostgreSQL</productname> include:
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Table-level locking has been replaced by multiversion concurrency control,
-     which allows readers to continue reading consistent data during writer activity
-     and enables hot backups from <application>pg_dump</> while the database stays available for
-     queries.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Important backend features, including subselects, defaults, 
-     constraints, and triggers, have been implemented.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Additional <acronym>SQL92</acronym>-compliant language features have been added,
-     including primary keys, quoted identifiers, literal string type coercion,
-     type casting, and binary and hexadecimal integer input.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Built-in types have been improved, including new wide-range date/time types 
-     and additional geometric type support.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Overall backend code speed has been increased by approximately 20-40%, 
-     and backend start-up time has decreased by 80% since version 6.0 was released.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect2>
-</sect1>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/indexcost.sgml b/doc/src/sgml/indexcost.sgml
deleted file mode 100644
index c30be63166c..00000000000
--- a/doc/src/sgml/indexcost.sgml
+++ /dev/null
@@ -1,291 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/indexcost.sgml,v 2.11 2002/03/22 19:20:10 petere Exp $
--->
-
- <chapter id="indexcost">
-  <title>Index Cost Estimation Functions</title>
-
-  <note>
-   <title>Author</title>
-
-   <para>
-    Written by Tom Lane (<email>tgl@sss.pgh.pa.us</email>) on 2000-01-24
-   </para>
-  </note>
-
-   <note>
-    <para>
-     This must eventually become part of a much larger chapter about
-     writing new index access methods.
-    </para>
-   </note>
-
-  <para>
-   Every index access method must provide a cost estimation function for
-   use by the planner/optimizer.  The procedure OID of this function is
-   given in the <literal>amcostestimate</literal> field of the access
-   method's <literal>pg_am</literal> entry.
-
-   <note>
-    <para>
-     Prior to <productname>PostgreSQL</productname> 7.0, a different
-     scheme was used for registering 
-     index-specific cost estimation functions.
-    </para>
-   </note>
-  </para>
-
-  <para>
-   The amcostestimate function is given a list of WHERE 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 main-table tuples 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 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 amcostestimate function must have the signature:
-
-   <programlisting>
-void
-amcostestimate (Query *root,
-                RelOptInfo *rel,
-                IndexOptInfo *index,
-                List *indexQuals,
-                Cost *indexStartupCost,
-                Cost *indexTotalCost,
-                Selectivity *indexSelectivity,
-                double *indexCorrelation);
-   </programlisting>
-
-   The first four parameters are inputs:
-
-   <variablelist>
-    <varlistentry>
-     <term>root</term>
-     <listitem>
-      <para>
-       The query being processed.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>rel</term>
-     <listitem>
-      <para>
-       The relation the index is on.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>index</term>
-     <listitem>
-      <para>
-       The index itself.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>indexQuals</term>
-     <listitem>
-      <para>
-       List of index qual clauses (implicitly ANDed);
-       a NIL list indicates no qualifiers are available.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   The last four parameters are pass-by-reference outputs:
-
-   <variablelist>
-    <varlistentry>
-     <term>*indexStartupCost</term>
-     <listitem>
-      <para>
-       Set to cost of index start-up processing
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>*indexTotalCost</term>
-     <listitem>
-      <para>
-       Set to total cost of index processing
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>*indexSelectivity</term>
-     <listitem>
-      <para>
-       Set to index selectivity
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>*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 in the units used by
-   <filename>src/backend/optimizer/path/costsize.c</filename>: a sequential disk block fetch
-   has cost 1.0, a nonsequential fetch has cost random_page_cost, and
-   the cost of processing one index tuple should usually be taken as
-   cpu_index_tuple_cost (which is a user-adjustable optimizer parameter).
-   In addition, an appropriate multiple of cpu_operator_cost should be charged
-   for any comparison operators invoked during index processing (especially
-   evaluation of the indexQuals themselves).
-  </para>
-
-  <para>
-   The access costs should include all disk and CPU costs associated with
-   scanning the index itself, but NOT the costs of retrieving or processing
-   the main-table tuples 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 tuple.  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 indexSelectivity should be set to the estimated fraction of the main
-   table tuples that will be retrieved during the index scan.  In the case
-   of a lossy index, this will typically be higher than the fraction of
-   tuples that actually pass the given qual conditions.
-  </para>
-
-  <para>
-   The 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 tuples from the main
-   table.
-  </para>
-
-  <procedure>
-   <title>Cost Estimation</title>
-   <para>
-    A typical cost estimator will proceed as follows:
-   </para>
-
-   <step>
-    <para>
-     Estimate and return the fraction of main-table tuples 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,
-                                           lfirsti(rel->relids));
-     </programlisting>
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Estimate the number of index tuples that will be visited during the
-     scan.  For many index types this is the same as indexSelectivity times
-     the number of tuples in the index, but it might be more.  (Note that the
-     index's size in pages and tuples is available from the IndexOptInfo struct.)
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Estimate the number of index pages that will be retrieved during the scan.
-     This might be just 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 have cost 1.0 each, not random_page_cost.
-     * Also, we charge for evaluation of the indexquals at each index tuple.
-     * All the costs are assumed to be paid incrementally during the scan.
-     */
-    *indexStartupCost = 0;
-    *indexTotalCost = numIndexPages +
-        (cpu_index_tuple_cost + cost_qual_eval(indexQuals)) * numIndexTuples;
-     </programlisting>
-    </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>
-
-  <para>
-   By convention, the <literal>pg_proc</literal> entry for an
-   <literal>amcostestimate</literal> function should show
-
-   <programlisting>
-prorettype = 0
-pronargs = 8
-proargtypes = 0 0 0 0 0 0 0 0
-   </programlisting>
-
-   We use zero ("opaque") for all the arguments since none of them have types
-   that are known in pg_type.
-  </para>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
deleted file mode 100644
index 417a50dcb35..00000000000
--- a/doc/src/sgml/indices.sgml
+++ /dev/null
@@ -1,933 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/indices.sgml,v 1.31 2002/01/07 02:29:12 petere Exp $ -->
-
-<chapter id="indexes">
- <title id="indexes-title">Indexes</title>
-
- <indexterm zone="indexes">
-  <primary>indexes</primary>
- </indexterm>
-
- <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>
-
-
- <sect1 id="indexes-intro">
-  <title>Introduction</title>
-
-  <para>
-   The classical example for the need of an index is if there is a
-   table similar to this:
-<programlisting>
-CREATE TABLE test1 (
-    id integer,
-    content varchar
-);
-</programlisting>
-   and the application requires a lot of queries of the form
-<programlisting>
-SELECT content FROM test1 WHERE id = <replaceable>constant</replaceable>;
-</programlisting>
-   Ordinarily, the system would have to scan the entire
-   <structname>test1</structname> table row by row to find all
-   matching entries.  If there are a lot of rows in
-   <structname>test1</structname> and only a few rows (possibly zero
-   or one) returned by the query, then this is clearly an inefficient
-   method.  If the system were instructed to maintain an index on the
-   <structfield>id</structfield> column, then it could 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 books of non-fiction:  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, and would not have to read the entire book to find the
-   interesting location.  As it is the task of the author to
-   anticipate the items that the readers are most likely to look up,
-   it is the task of the database programmer to foresee which indexes
-   would be of advantage.
-  </para>
-
-  <para>
-   The following command would be used to create the 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 the index is created, no further intervention is required: the
-   system will use the index when it thinks it would be more efficient
-   than a sequential table scan.  But you may have to run the
-   <command>ANALYZE</command> command regularly to update
-   statistics to allow the query planner to make educated decisions.
-   Also read <xref linkend="performance-tips"> for information about
-   how to find out whether an index is used and when and why the
-   planner may choose to <emphasis>not</emphasis> use an index.
-  </para>
-
-  <para>
-   Indexes can benefit <command>UPDATE</command>s and
-   <command>DELETE</command>s with search conditions.  Indexes can also be
-   used in join queries.  Thus,
-   an index defined on a column that is part of a join condition can
-   significantly speed up queries with joins.
-  </para>
-
-  <para>
-   When 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 non-essential or do not get used at all
-   should be removed.  Note that a
-   query or data manipulation command can use at most one index
-   per table.
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-types">
-  <title>Index Types</title>
-
-  <para>
-   <productname>PostgreSQL</productname> provides several index types:
-   B-tree, R-tree, GiST, and Hash.  Each index type is more appropriate for
-   a particular query type because of the algorithm it uses.
-   <indexterm>
-    <primary>indexes</primary>
-    <secondary>B-tree</secondary>
-   </indexterm>
-   <indexterm>
-    <primary>B-tree</primary>
-    <see>indexes</see>
-   </indexterm>
-   By
-   default, the <command>CREATE INDEX</command> command will create a
-   B-tree index, which fits the most common situations.  In
-   particular, the <productname>PostgreSQL</productname> query optimizer
-   will consider using a B-tree index whenever an indexed column is
-   involved in a comparison using one of these operators:
-
-   <simplelist type="inline">
-    <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>
-  </para>
-
-  <para>
-   <indexterm>
-    <primary>indexes</primary>
-    <secondary>R-tree</secondary>
-   </indexterm>
-   <indexterm>
-    <primary>R-tree</primary>
-    <see>indexes</see>
-   </indexterm>
-   R-tree indexes are especially suited for spatial data.  To create
-   an R-tree index, use a command of the form
-<synopsis>
-CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable> USING RTREE (<replaceable>column</replaceable>);
-</synopsis>
-   The <productname>PostgreSQL</productname> query optimizer will
-   consider using an R-tree index whenever an indexed column is
-   involved in a comparison using one of these operators:
-
-   <simplelist type="inline">
-    <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>@</literal></member>
-    <member><literal>~=</literal></member>
-    <member><literal>&amp;&amp;</literal></member>
-   </simplelist>
-   (Refer to <xref linkend="functions-geometry"> about the meaning of
-   these operators.)
-  </para>
-
-  <para>
-   <indexterm>
-    <primary>indexes</primary>
-    <secondary>hash</secondary>
-   </indexterm>
-   <indexterm>
-    <primary>hash</primary>
-    <see>indexes</see>
-   </indexterm>
-   The query optimizer 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>
-   <note>
-    <para>
-     Because of the limited utility of hash indexes, a B-tree index
-     should generally be preferred over a hash index.  We do not have
-     sufficient evidence that hash indexes are actually faster than
-     B-trees even for <literal>=</literal> comparisons.  Moreover,
-     hash indexes require coarser locks; see <xref
-     linkend="locking-indexes">.
-    </para>
-   </note>  
-  </para>
-
-  <para>
-   The B-tree index is an implementation of Lehman-Yao
-   high-concurrency B-trees.  The R-tree index method implements
-   standard R-trees using Guttman's quadratic split algorithm.  The
-   hash index is an implementation of Litwin's linear hashing.  We
-   mention the algorithms used solely to indicate that all of these
-   access methods are fully dynamic and do not have to be optimized
-   periodically (as is the case with, for example, static hash access
-   methods).
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-multicolumn">
-  <title>Multicolumn Indexes</title>
-
-  <indexterm zone="indexes-multicolumn">
-   <primary>indexes</primary>
-   <secondary>multicolumn</secondary>
-  </indexterm>
-
-  <para>
-   An index can be defined on more than one column.  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 make queries like
-<programlisting>
-SELECT name FROM test2 WHERE major = <replaceable>constant</replaceable> AND minor = <replaceable>constant</replaceable>;
-</programlisting>
-   then it may 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 and GiST implementations support multicolumn
-   indexes.  Up to 16 columns may be specified.  (This limit can be
-   altered when building <productname>PostgreSQL</productname>; see the
-   file <filename>pg_config.h</filename>.)
-  </para>
-
-  <para>
-   The query optimizer can use a multicolumn index for queries that
-   involve the first <parameter>n</parameter> consecutive columns in
-   the index (when used with appropriate operators), up to the total
-   number of columns specified in the index definition.  For example,
-   an index on <literal>(a, b, c)</literal> can be used in queries
-   involving all of <literal>a</literal>, <literal>b</literal>, and
-   <literal>c</literal>, or in queries involving both
-   <literal>a</literal> and <literal>b</literal>, or in queries
-   involving only <literal>a</literal>, but not in other combinations.
-   (In a query involving <literal>a</literal> and <literal>c</literal>
-   the optimizer might choose to use the index for
-   <literal>a</literal> only and treat <literal>c</literal> like an
-   ordinary unindexed column.)
-  </para>
-
-  <para>
-   Multicolumn indexes can only be used if the clauses involving the
-   indexed columns are joined with <literal>AND</literal>.  For instance,
-<programlisting>
-SELECT name FROM test2 WHERE major = <replaceable>constant</replaceable> OR minor = <replaceable>constant</replaceable>;
-</programlisting>
-   cannot make use of the index <structname>test2_mm_idx</structname>
-   defined above to look up both columns.  (It can be used to look up
-   only the <structfield>major</structfield> column, however.)
-  </para>
-
-  <para>
-   Multicolumn indexes should be used sparingly.  Most of the time,
-   an index on a single column is sufficient and saves space and time.
-   Indexes with more than three columns are almost certainly
-   inappropriate.
-  </para>
- </sect1>
-
-
- <sect1 id="indexes-unique">
-  <title>Unique Indexes</title>
-
-  <indexterm zone="indexes-unique">
-   <primary>indexes</primary>
-   <secondary>unique</secondary>
-  </indexterm>
-
-  <para>
-   Indexes may 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 will not be allowed.  NULL values are not considered
-   equal.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname> automatically creates unique
-   indexes when a table is declared with a unique constraint or a
-   primary key, on the columns that make up the primary key or unique
-   columns (a multicolumn index, if appropriate), to enforce that
-   constraint.  A unique index can be added to a table at any later
-   time, to add a unique 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.
-   </para>
-  </note>
- </sect1>
-
-
- <sect1 id="indexes-functional">
-  <title>Functional Indexes</title>
-
-  <indexterm zone="indexes-functional">
-   <primary>indexes</primary>
-   <secondary>on functions</secondary>
-  </indexterm>
-
-  <para>
-   For a <firstterm>functional index</firstterm>, an index is defined
-   on the result of a function applied to one or more columns of a
-   single table.  Functional indexes can be used to obtain fast access
-   to data based on the result of function calls.
-  </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(column)</literal>
-   operation:
-<programlisting>
-CREATE INDEX test1_lower_col1_idx ON test1 (lower(col1));
-</programlisting>
-  </para>
-
-  <para>
-   The function in the index definition can take more than one
-   argument, but they must be table columns, not constants.
-   Functional indexes are always single-column (namely, the function
-   result) even if the function uses more than one input field; there
-   cannot be multicolumn indexes that contain function calls.
-  </para>
-
-  <tip>
-   <para>
-    The restrictions mentioned in the previous paragraph can easily be
-    worked around by defining a custom function to use in the index
-    definition that computes any desired result internally.
-   </para>
-  </tip>
- </sect1>
-
-
- <sect1 id="indexes-opclass">
-  <title>Operator Classes</title>
-
-  <para>
-   An index definition may 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>, ...</optional>);
-</synopsis>
-   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.  There are also some
-   operator classes with special purposes:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The operator classes <literal>box_ops</literal> and
-      <literal>bigbox_ops</literal> both support R-tree indexes on the
-      <literal>box</literal> data type.  The difference between them is
-      that <literal>bigbox_ops</literal> scales box coordinates down,
-      to avoid floating-point exceptions from doing multiplication,
-      addition, and subtraction on very large floating-point
-      coordinates.  If the field on which your rectangles lie is about
-      20 000 units square or larger, you should use
-      <literal>bigbox_ops</literal>.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   The following query shows all defined operator classes:
-<programlisting>
-SELECT am.amname AS acc_method,
-       opc.opcname AS ops_name,
-       opr.oprname AS ops_comp
-    FROM pg_am am, pg_opclass opc, pg_amop amop, pg_operator opr
-    WHERE opc.opcamid = am.oid AND
-          amop.amopclaid = opc.oid AND
-          amop.amopopr = opr.oid
-    ORDER BY acc_method, ops_name, ops_comp
-</programlisting>
-  </para>
- </sect1>
-
-
-  <sect1 id="keys">
-   <title id="keys-title">Keys</title>
-
-   <para>
-    <note>
-     <title>Author</title>
-     <para>
-      Written by Herouth Maoz (<email>herouth@oumail.openu.ac.il</email>).
-      This originally appeared on the User's Mailing List on 1998-03-02
-      in response to the question:
-      "What is the difference between PRIMARY KEY and UNIQUE constraints?".
-     </para>
-    </note>
-   </para>
-
-   <para>
-<literallayout>
-Subject: Re: [QUESTIONS] PRIMARY KEY | UNIQUE
-
-        What's the difference between:
-
-              PRIMARY KEY(fields,...) and
-              UNIQUE (fields,...)
-
-       - Is this an alias?
-       - If PRIMARY KEY is already unique, then why
-         is there another kind of key named UNIQUE?
-</literallayout>
-   </para>
-
-   <para>
-    A primary key is the field(s) used to identify a specific row. For example,
-    Social Security numbers identifying a person.
-   </para>
-
-   <para>
-    A simply UNIQUE combination of fields has nothing to do with identifying
-    the row. It's simply an integrity constraint. For example, I have
-    collections of links. Each collection is identified by a unique number,
-    which is the primary key. This key is used in relations.
-   </para>
-
-   <para>
-    However, my application requires that each collection will also have a
-    unique name. Why? So that a human being who wants to modify a collection
-    will be able to identify it. It's much harder to know, if you have two
-    collections named <quote>Life Science</quote>, the one tagged 24433 is the one you
-    need, and the one tagged 29882 is not.
-   </para>
-
-   <para>
-    So, the user selects the collection by its name. We therefore make sure,
-    within the database, that names are unique. However, no other table in the
-    database relates to the collections table by the collection Name. That
-    would be very inefficient.
-   </para>
-
-   <para>
-    Moreover, despite being unique, the collection name does not actually
-    define the collection! For example, if somebody decided to change the name
-    of the collection from <quote>Life Science</quote> to <quote>Biology</quote>, it will still be the
-    same collection, only with a different name. As long as the name is unique,
-    that's OK.
-   </para>
-
-   <para>
-    So:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Primary key:
-       <itemizedlist spacing="compact" mark="bullet">
-	<listitem>
-	 <para>
-	  Is used for identifying the row and relating to it.
-	 </para>
-	</listitem>
-	<listitem>
-	 <para>
-	  Is impossible (or hard) to update.
-	 </para>
-	</listitem>
-	<listitem>
-	 <para>
-	  Should not allow NULLs.
-	 </para>
-	</listitem>
-       </itemizedlist>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Unique field(s):
-       <itemizedlist spacing="compact" mark="bullet">
-	<listitem>
-	 <para>
-	  Are used as an alternative access to the row.
-	 </para>
-	</listitem>
-	<listitem>
-	 <para>
-	  Are updatable, so long as they are kept unique.
-	 </para>
-	</listitem>
-	<listitem>
-	 <para>
-	  NULLs are acceptable.
-	 </para>
-	</listitem>
-       </itemizedlist>
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    As for why no non-unique keys are defined explicitly in standard
-    <acronym>SQL</acronym> syntax? Well, you
-    must understand that indexes are implementation-dependent.
-    <acronym>SQL</acronym> does not
-    define the implementation, merely the relations between data in the
-    database. <productname>PostgreSQL</productname> does allow
-    non-unique indexes, but indexes
-    used to enforce <acronym>SQL</acronym> keys are always unique.
-   </para>
-
-   <para>
-    Thus, you may query a table by any combination of its columns, despite the
-    fact that you don't have an index on these columns. The indexes are merely
-    an implementation aid that each <acronym>RDBMS</acronym> offers
-    you, in order to cause
-    commonly used queries to be done more efficiently.
-    Some <acronym>RDBMS</acronym> may give you
-    additional measures, such as keeping a key stored in main memory. They will
-    have a special command, for example
-<synopsis>
-CREATE MEMSTORE ON <replaceable>table</replaceable> COLUMNS <replaceable>cols</replaceable>
-</synopsis>
-    (This is not an existing command, just an example.)
-   </para>
-
-   <para>
-    In fact, when you create a primary key or a unique combination of fields,
-    nowhere in the <acronym>SQL</acronym> specification does it say
-    that an index is created, nor that
-    the retrieval of data by the key is going to be more efficient than a
-    sequential scan!
-   </para>
-
-   <para>
-    So, if you want to use a combination of fields that is not unique as a
-    secondary key, you really don't have to specify anything - just start
-    retrieving by that combination! However, if you want to make the retrieval
-    efficient, you'll have to resort to the means your
-    <acronym>RDBMS</acronym> provider gives you
-    - be it an index, my imaginary <literal>MEMSTORE</literal> command, or an intelligent
-    <acronym>RDBMS</acronym>
-    that creates indexes without your knowledge based on the fact that you have
-    sent it many queries based on a specific combination of keys... (It learns
-    from experience).
-   </para>
-  </sect1>
-
-
- <sect1 id="indexes-partial">
-  <title>Partial Indexes</title>
-
-  <indexterm zone="indexes-partial">
-   <primary>indexes</primary>
-   <secondary>partial</secondary>
-  </indexterm>
-
-  <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 for only those table
-   rows that satisfy the predicate.
-  </para>
-
-  <para>
-   A major motivation for partial indexes 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 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 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 > inet '192.168.100.0' AND client_ip < 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.  If the distribution of values is
-    inherent (due to the nature of the application) and static (not
-    changing over time), this is not difficult, but if the common values are
-    merely due to the coincidental data load this can require a lot of
-    maintenance work.
-   </para>
-  </example>
-
-  <para>
-   Another possibility 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 at all, 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 < 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 > 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 may be among the billed or among the 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
-   match.  <productname>PostgreSQL</productname> supports partial
-   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 query's WHERE condition mathematically <firstterm>implies</>
-   the index's predicate.
-   <productname>PostgreSQL</productname> does not have a sophisticated
-   theorem prover that can recognize mathematically equivalent
-   predicates 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 the query's WHERE condition
-   or the index will not be recognized to be usable.
-  </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 bool,
-                    ...);
-CREATE UNIQUE INDEX tests_success_constraint ON tests (subject, target)
-    WHERE success;
-</programlisting>
-    This is a particularly efficient way of doing it when there are few
-    successful trials and many unsuccessful ones.
-   </para>
-  </example>
-
-  <para>
-   Finally, a partial index can also be used to override the system's
-   query plan choices.  It may occur that data sets with peculiar
-   distributions will 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,
-   <productname>PostgreSQL</> makes reasonable choices about index
-   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
-   <productname>PostgreSQL</> work.  In most cases, the advantage of a
-   partial index over a regular index will not be much.
-  </para>
-
-  <para>
-   More information about partial indexes can be found in <xref
-   linkend="STON89b">, <xref linkend="OLSON93">, and <xref
-   linkend="SESHADRI95">.
-  </para>
- </sect1>
-
- <sect1 id="indexes-examine">
-  <title>Examining Index Usage</title>
-
-  <para>
-   Although indexes in <productname>PostgreSQL</> do not need
-   maintenance and tuning, it is still important to check
-   which indexes are actually used by the real-life query workload.
-   Examining index usage is done with the <command>EXPLAIN</> command;
-   its application for this purpose is illustrated in <xref
-   linkend="using-explain">.
-  </para>
-
-  <para>
-   It is difficult to formulate a general procedure for determining
-   which indexes to set up.  There are a number of typical cases that
-   have been shown in the examples throughout the previous sections.
-   A good deal of experimentation will be necessary in most cases.
-   The rest of this section gives some tips for that.
-  </para>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Always run <command>ANALYZE</command> first.  This command
-     collects statistics about the distribution of the values in the
-     table.  This information is required to guess 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.
-    </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 proportionally reduced 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 will 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 in production use yet.
-     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 (described in the <citetitle>Administrator's
-     Guide</citetitle>).  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 problem for why the index is not
-     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 of the plan nodes can be tuned with
-     run-time parameters (described in the <citetitle>Administrator's
-     Guide</citetitle>).  An inaccurate selectivity estimate is due to
-     insufficient statistics.  It may be possible to help this by
-     tuning the statistics-gathering parameters (see <command>ALTER
-     TABLE</command> reference).
-    </para>
-
-    <para>
-     If you do not succeed in adjusting the costs to be more
-     appropriate, then you may have to resort to forcing index usage
-     explicitly.  You may also want to contact the
-     <productname>PostgreSQL</> developers to examine the issue.
-    </para>
-   </listitem>
-  </itemizedlist>
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/info.sgml b/doc/src/sgml/info.sgml
deleted file mode 100644
index c3700650edd..00000000000
--- a/doc/src/sgml/info.sgml
+++ /dev/null
@@ -1,177 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/info.sgml,v 1.15 2001/11/28 20:49:10 petere Exp $
--->
-
-<sect1 id="resources">
- <title>Documentation Resources</title>
-
- <para>
-  This manual set is organized into several parts:
-
-  <variablelist>
-   <varlistentry>
-    <term>Tutorial</term>
-    <listitem>
-     <para>
-      An informal introduction for new users
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>User's Guide</term>
-    <listitem>
-     <para>
-      Documents the SQL query language environment, including data types
-      and functions.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Programmer's Guide</term>
-    <listitem>
-     <para>
-      Advanced information for application programmers. Topics include
-      type and function extensibility, library interfaces,
-      and application design issues.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Administrator's Guide</term>
-    <listitem>
-     <para>
-      Installation and server management information
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Reference Manual</term>
-    <listitem>
-     <para>
-      Reference pages for SQL command syntax and client and server programs
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Developer's Guide</term>
-    <listitem>
-     <para>
-      Information for <productname>PostgreSQL</productname> developers.
-      This is intended for those who are contributing to the
-      <productname>PostgreSQL</productname> project;
-      application development information appears in the 
-      <citetitle>Programmer's Guide</citetitle>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </para>
-
- <para>
-  In addition to this manual set, there are other resources to help you with
-  <productname>PostgreSQL</productname> installation and use:
-
-  <variablelist>
-   <varlistentry>
-    <term>man pages</term>
-    <listitem>
-     <para>
-      The <citetitle>Reference Manual</citetitle>'s pages in the traditional
-      Unix man format.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>FAQs</term>
-    <listitem>
-     <para>
-      Frequently Asked Questions (FAQ) lists document both general issues
-      and some platform-specific issues.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>READMEs</term>
-    <listitem>
-     <para>
-      README files are available for some contributed packages.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Web Site</term>
-    <listitem>
-     <para>
-      The <ulink
-      url="http://www.postgresql.org"><productname>PostgreSQL</productname>
-      web site</ulink> carries details on the latest release, upcoming
-      features, and other information to make your work or play with
-      <productname>PostgreSQL</productname> more productive.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Mailing Lists</term>
-    <listitem>
-     <para>
-      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 <ulink
-      url="http://www.postgresql.org/users-lounge/">User's
-      Lounge</ulink> section of the <productname>PostgreSQL</>
-      web site for details.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>Yourself!</term>
-    <listitem>
-     <para>
-      <productname>PostgreSQL</productname> is an open-source effort.
-      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. 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.
-     </para>
-
-     <para>
-      Even those without a lot of experience can provide corrections
-      and minor changes in the documentation, and that is a good way
-      to start.  The <email>pgsql-docs@postgresql.org</email> mailing
-      list is the place to get going.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </para>
-</sect1>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/inherit.sgml b/doc/src/sgml/inherit.sgml
deleted file mode 100644
index a0d27b0768f..00000000000
--- a/doc/src/sgml/inherit.sgml
+++ /dev/null
@@ -1,188 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/inherit.sgml,v 1.19 2002/04/13 17:17:29 tgl Exp $
--->
-
- <chapter id="inherit">
-  <title>Inheritance</title>
-
-  <para>
-   Let's create two tables. The capitals  table  contains
-   state  capitals  which  are also cities. Naturally, the
-   capitals table should inherit from cities.
-
-<programlisting>
-CREATE TABLE cities (
-    name            text,
-    population      float,
-    altitude        int     -- (in ft)
-);
-
-CREATE TABLE capitals (
-    state           char(2)
-) INHERITS (cities);
-</programlisting>
-
-   In this case, a row  of  capitals  <firstterm>inherits</firstterm>  all
-   attributes  (name,  population,  and altitude) from its
-   parent, cities.  The type  of  the  attribute  name  is
-   <type>text</type>,  a  native  <productname>PostgreSQL</productname>  type  for variable length
-   ASCII strings.  The type of the attribute population is
-   <type>float</type>,  a  native <productname>PostgreSQL</productname> type for double precision
-   floating-point numbers.  State capitals have  an  extra
-   attribute, state, that shows their state.  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
-   descendants. 
-
-   <note>
-    <para>
-     The inheritance hierarchy is actually a directed acyclic graph.
-    </para>
-   </note>
-  </para>
-
-  <para>
-    For example, the  following  query finds the  names  of  all  cities,
-    including  state capitals, that are located at an altitude 
-    over 500ft:
-
-    <programlisting>
-SELECT name, altitude
-    FROM cities
-    WHERE altitude &gt; 500;
-    </programlisting>
-
-   which 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 500ft:
-
-   <programlisting>
-SELECT name, altitude
-    FROM ONLY cities
-    WHERE altitude &gt; 500;
-
-   name    | altitude
------------+----------
- Las Vegas |     2174
- Mariposa  |     1953
-   </programlisting>         
-  </para>
-
-  <para>
-   Here the <quote>ONLY</quote> before cities indicates that the query should
-   be  run over only cities and not tables below cities in the
-   inheritance hierarchy.  Many of the  commands  that  we
-   have  already discussed -- <command>SELECT</command>,
-   <command>UPDATE</command> and <command>DELETE</command> --
-   support this <quote>ONLY</quote> notation.
-  </para>
-
-  <para>
-  In some cases you may wish to know which table a particular tuple
-  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>
-
-   (If you try to reproduce this example, you will probably get different
-   numeric OIDs.)  By doing a join with 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>
-   
-  </para>
-
-  <note>
-   <title>Deprecated</title> 
-   <para>
-     In previous versions of <productname>PostgreSQL</productname>, the
-     default was not to get access to child tables. This was found to
-     be error prone and is also in violation of SQL99. Under the old
-     syntax, to get the sub-tables you append <literal>*</literal> to the table name.
-     For example
-<programlisting>
-SELECT * from cities*;
-</programlisting>
-     You can still explicitly specify scanning child tables by appending
-     <literal>*</literal>, as well as explicitly specify not scanning child tables by
-     writing <quote>ONLY</quote>.  But beginning in version 7.1, the default
-     behavior for an undecorated table name is to scan its child tables
-     too, whereas before the default was not to do so.  To get the old
-     default behavior, set the configuration option
-     <literal>SQL_Inheritance</literal> to off, e.g.,
-<programlisting>
-SET SQL_Inheritance TO OFF;
-</programlisting>
-     or add a line in your <filename>postgresql.conf</filename> file.
-   </para>
-  </note>
-
-  <para>
-   A 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.  Thus, in the above example,
-   specifying that another table's column <literal>REFERENCES cities(name)</>
-   would allow the other table to contain city names but not capital names.
-   This deficiency will probably be fixed in some future release.
-  </para>
-
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/install-win32.sgml b/doc/src/sgml/install-win32.sgml
deleted file mode 100644
index 6064022cf7e..00000000000
--- a/doc/src/sgml/install-win32.sgml
+++ /dev/null
@@ -1,131 +0,0 @@
-<chapter id="install-win32">
- <title>Installation on <productname>Windows</productname></title>
-
- <indexterm>
-  <primary>installation</primary>
-  <secondary>on Windows</secondary>
- </indexterm>
-
- <abstract>
-  <para>
-   Build, installation, and use instructions for
-   <productname>PostgreSQL</productname> client libraries on
-   <productname>Windows</productname>
-  </para>
- </abstract>
-
- <para>
-  Although <productname>PostgreSQL</productname> is written for
-  Unix-like operating systems, the C client library
-  (<application>libpq</application>) and the interactive terminal
-  (<application>psql</application>) can be compiled natively under
-  Windows.  The makefiles included in the source distribution are
-  written for <productname>Microsoft Visual C++</productname> and will
-  probably not work with other systems.  It should be possible to
-  compile the libraries manually in other cases.
- </para>
-
- <tip>
-  <para>
-   If you are using Windows 98 or newer you can build and use all of
-   <productname>PostgreSQL</productname> <quote>the Unix way</quote>
-   if you install the <productname>Cygwin</productname> toolkit first.
-   In that case see <xref linkend="installation">.
-  </para>
- </tip>
-
- <para>
-  To build everything that you can on
-  <productname>Windows</productname>, change into the
-  <filename>src</filename> directory and type the command
-<screen>
-<userinput>nmake /f win32.mak</userinput>
-</screen>
-  This assumes that you have <productname>Visual C++</productname> in
-  your path.
- </para>
-
- <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 program to <filename>libpq.dll</filename>
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>interfaces\libpq\Release\libpq.lib</filename></term>
-    <listitem>
-     <para>
-      Static library version of the frontend library
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><filename>bin\psql\Release\psql.exe</filename></term>
-    <listitem>
-     <para>
-      The <productname>PostgreSQL</productname> interactive terminal
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </para>
-
- <para>
-  The only file that really needs to be installed is the
-  <filename>libpq.dll</filename> library.  This file should in most
-  cases be placed in the <filename>WINNT\SYSTEM32</filename> directory
-  (or in <filename>WINDOWS\SYSTEM</filename> on a Windows 95/98/ME
-  system).  If this file is installed using a setup program, 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 plan 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 compilers settings.
- </para>
-
- <para>
-  To use the libraries, 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>
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
deleted file mode 100644
index 620a61583bb..00000000000
--- a/doc/src/sgml/installation.sgml
+++ /dev/null
@@ -1,1842 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.78 2002/06/15 02:41:56 thomas Exp $ -->
-
-<chapter id="installation">
- <title><![%standalone-include[<productname>PostgreSQL</>]]>
-  Installation Instructions</title>
-
- <indexterm zone="installation">
-  <primary>installation</primary>
- </indexterm>
-
- <sect1 id="install-short">
-  <title>Short Version</title>
-
-  <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/postmaster -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>
-   The long version is the rest of this
-   <![%standalone-include;[document.]]>
-   <![%standalone-ignore;[chapter.]]>
-  </para>
- </sect1>
-
-
- <sect1 id="install-requirements">
-  <title>Requirements</title>
-
-  <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>
-
-  <para>
-   The following prerequisites exist for building <productname>PostgreSQL</>:
-   <itemizedlist>
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>make</primary>
-      </indexterm>
-
-      <acronym>GNU</> <application>make</> is required; other
-      <application>make</> programs 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 GNU 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>
-      It is recommended to use version 3.76.1 or later.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      You need an <acronym>ISO</>/<acronym>ANSI</> C compiler. Recent
-      versions of <productname>GCC</> are recommendable, but
-      <productname>PostgreSQL</> is known to build with a wide variety
-      of compilers from different vendors.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <application>gzip</> is needed to unpack the distribution in the
-      first place.  If you are reading this, you probably already got
-      past that hurdle.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>readline</primary>
-      </indexterm>
-
-      The <acronym>GNU</> <productname>Readline</> library (for
-      comfortable line editing and command history retrieval) will be
-      used by default.  If you don't want to use it then you must
-      specify the <option>--without-readline</option> option for
-      <filename>configure</>.  (On <productname>NetBSD</productname>,
-      the <filename>libedit</filename> library is
-      <productname>readline</productname>-compatible and is used if
-      <filename>libreadline</filename> is not found.)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>flex</primary>
-      </indexterm>
-      <indexterm>
-       <primary>bison</primary>
-      </indexterm>
-      <indexterm>
-       <primary>yacc</primary>
-      </indexterm>
-
-      <acronym>GNU</> <application>Flex</> and <application>Bison</> are
-      needed to build from scratch, but they are
-      <emphasis>not</> required when building from a released source
-      package because pre-generated output files are included in released
-      packages. You will
-      need these programs only when building from a CVS tree or if you
-      changed the actual scanner and parser definition files. If
-      you need them, be sure to get <application>Flex</> 2.5.4 or
-      later and <application>Bison</> 1.28 or later. Other <application>yacc</>
-      programs can sometimes be used, but doing so requires extra
-      effort and is not recommended. Other <application>lex</> programs will
-      definitely not work.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <indexterm>
-       <primary>installation</primary>
-       <secondary>on Windows</secondary>
-      </indexterm>
-
-      To build on <productname>Windows NT</> or <productname>Windows
-      2000</> you need the <productname>Cygwin</> and
-      <productname>cygipc</> packages. See the file
-      <filename>doc/FAQ_MSWIN</> for details.
-     </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
-   30 MB for the source tree during compilation and about 10 MB for the
-   installation directory. An empty database cluster takes about 20 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 an extra 20 MB. Use the
-   <command>df</command> command to check for disk space.
-  </para>
- </sect1>
-
-<![%standalone-ignore;[
- <sect1 id="install-getsource">
-  <title>Getting The Source</title>
-
-  <para>
-   The <productname>PostgreSQL</> &version; sources can be obtained by
-   anonymous FTP from <ulink
-   url="ftp://ftp.postgresql.org/pub/postgresql-&version;.tar.gz"></ulink>.
-   Use a mirror if possible. 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>
- </sect1>
-]]>
-
- <sect1 id="install-upgrading">
-  <title>If You Are Upgrading</title>
-
-  <indexterm zone="install-upgrading">
-   <primary>upgrading</primary>
-  </indexterm>
-
-  <para>
-   The internal data storage format changes with new releases of
-   <productname>PostgreSQL</>. Therefore, if you are upgrading an
-   existing installation that does not have a version number
-   <quote>&majorversion;.x</quote>, you must back up and restore your
-   data as shown here. 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>
-     Make sure that your database is not updated during or after the
-     backup. 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.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     <indexterm>
-      <primary>pg_dumpall</primary>
-     </indexterm>
-
-     To dump 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
-     <command>pg_dumpall</>.
-    </para>
-
-    <para>
-     <command>pg_dumpall</command> does not
-     save large objects.  Check
-     <![%standalone-include[the <citetitle>Administrator's Guide</>]]>
-     <![%standalone-ignore[<xref linkend="backup-dump-caveats">]]>
-     if you need to do this.
-    </para>
-
-    <para>
-     Make sure that you use the <command>pg_dumpall</> command
-     from the version you are currently running. &version;'s
-     <command>pg_dumpall</> should not be used on older databases.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     If you are installing the new version at the same location as the
-     old one then shut down the old server, at the latest before you
-     install the new files:
-<screen>
-<userinput>kill -INT `cat /usr/local/pgsql/data/postmaster.pid`</>
-</screen>
-     Versions prior to 7.0 do not have this
-     <filename>postmaster.pid</> file. If you are using such a version
-     you must find out the process id of the server yourself, for
-     example by typing <userinput>ps ax | grep postmaster</>, and
-     supply it to the <command>kill</> command.
-    </para>
-
-    <para>
-     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
-<screen>
-<userinput>/etc/rc.d/init.d/postgresql stop</userinput>
-</screen>
-     works.  Another possibility is <userinput>pg_ctl stop</>.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     If you are installing in the same place as the old version then
-     it is also a good idea to move the old installation out of the
-     way, in case you have trouble and need to revert to it.
-     Use a command like this:
-<screen>
-<userinput>mv /usr/local/pgsql /usr/local/pgsql.old</>
-</screen>
-    </para>
-   </step>
-  </procedure>
-
-  <para>
-   After you have installed <productname>PostgreSQL</> &version;, create a new database
-   directory and start the new server. 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</>
-<userinput>/usr/local/pgsql/bin/postmaster -D /usr/local/pgsql/data</>
-</programlisting>
-   Finally, restore your data with
-<screen>
-<userinput>/usr/local/pgsql/bin/psql -d template1 -f <replaceable>outputfile</></userinput>
-</screen>
-   using the <emphasis>new</> <application>psql</>.
-  </para>
-
-  <para>
-   You can also install the new version in parallel with the old one
-   to decrease the downtime. These topics are discussed at length in
-   <![%standalone-include[the <citetitle>Administrator's Guide</>,]]>
-   <![%standalone-ignore[<xref linkend="migration">,]]>
-   which you are encouraged
-   to read in any case.
-  </para>
- </sect1>
-
-
- <sect1 id="install-procedure">
-  <title>Installation Procedure</title>
-
-  <procedure>
-
-  <step id="configure">
-   <title>Configuration</>
-
-   <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 guess values for various
-    system dependent variables and detect some quirks of your
-    operating system, and finally will create several files in the build
-    tree to record what it found.
-   </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.
-        </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>--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>PREFIX</>/share</>. Note that this has
-         nothing to do with where your database files will be placed.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--sysconfdir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         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>
-         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>
-         The directory for installing C and C++ header files. The
-         default is <filename><replaceable>PREFIX</>/include</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--docdir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Documentation files, except <quote>man</> pages, will be
-         installed into this directory. The default is
-         <filename><replaceable>PREFIX</>/doc</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--mandir=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         The man pages that come with <productname>PostgreSQL</> will be installed under
-         this directory, in their respective
-         <filename>man<replaceable>x</></> subdirectories.
-         The default is <filename><replaceable>PREFIX</>/man</>.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-
-     <note>
-      <para>
-       Care has been taken to make it possible to install
-	<productname>PostgreSQL</> 
-       into shared installation locations (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>.  Second, the
-       installation layout of the C and C++ header files has been
-       reorganized in the 7.2 release.  The public 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 <citetitle>Programmer's Guide</citetitle> for
-       information about how to get at the header files for each interface.
-       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-recode</option></term>
-       <listitem>
-        <para>
-         Enables single-byte character set recode support. See
-         <![%standalone-include[the <citetitle>Administrator's Guide</citetitle>]]>
-         <![%standalone-ignore[<xref linkend="recode">]]> about this feature.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-multibyte</option></term>
-       <listitem>
-        <para>
-         Allows the use of multibyte character encodings (including Unicode)
-         and character set encoding conversion. Read 
-         <![%standalone-include[the <citetitle>Administrator's Guide</citetitle>]]>
-         <![%standalone-ignore[<xref linkend="multibyte">]]>
-         for details.
-        </para>
-
-        <para>
-         Note that some interfaces (such as Tcl or Java) expect all character
-         strings to be in Unicode, so this option will be required to correctly
-         support these interfaces.
-        </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 a 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>
-
-        <comment>
-         The list of provided translations should be shown somewhere.
-        </comment>
-
-        <para>
-         To use this option, you will need an implementation of the
-         <application>gettext</> API.  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 here:  <ulink
-         url="http://www.postgresql.org/~petere/gettext.html"
-         ></ulink>.  If
-         you are using the <application>gettext</> implementation in the GNU 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>
-
-        <comment>
-         The download location should be moved.
-        </comment>
-
-       </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
-	 <productname>PostgreSQL</> servers on the same machine.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-CXX</option></term>
-       <listitem>
-        <para>
-         Build the C++ interface library.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-perl</option></term>
-       <listitem>
-        <para>
-         Build the Perl interface module. The Perl interface
-         will be installed at the usual place for Perl modules
-         (typically under <filename>/usr/lib/perl</filename>), so you
-         must have root access to perform the installation step (see
-         <xref linkend="install">). You need to have Perl 5 installed to
-         use this option.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-python</option></term>
-       <listitem>
-        <para>
-         Build the Python interface module. You need to have root
-         access to be able to install the Python module at its default
-         place
-         (<filename>/usr/lib/python<replaceable>x</>.<replaceable>y</></>).
-         To be able to use this option, you must have Python installed
-         and your system needs to support shared libraries. If you
-         instead want to build a new complete interpreter binary, you
-         will have to do it manually.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-tcl</option></term>
-       <listitem>
-        <para>
-         Builds components that require Tcl/Tk, which are
-         <application>libpgtcl</>, <application>pgtclsh</>,
-         <application>pgtksh</application>, <application>PgAccess</>,
-         and <application>PL/Tcl</>.  But see below about
-         <option>--without-tk</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--without-tk</option></term>
-       <listitem>
-        <para>
-         If you specify <option>--with-tcl</> and this option, then
-         programs that require <productname>Tk</>
-         (<application>pgtksh</> and <application>PgAccess</>) will be
-         excluded.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-tclconfig=<replaceable>DIRECTORY</replaceable></option></term>
-       <term><option>--with-tkconfig=<replaceable>DIRECTORY</replaceable></option></term>
-       <listitem>
-        <para>
-         Tcl/Tk installs the files <filename>tclConfig.sh</filename> and
-         <filename>tkConfig.sh</filename>, which contain
-         configuration information needed to build modules
-         interfacing to Tcl or Tk. These files are normally found
-         automatically at their well-known locations, but if you want to
-         use a different version of Tcl or Tk you can specify the
-         directory in which to find them.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-odbc</option></term>
-       <listitem>
-        <para>
-         Build the ODBC driver.  By default, the driver will be independent
-         of a driver manager.  To work better with a driver manager already
-         installed on your system, use one of the following options in addition
-         to this one.  More information can be found in the
-         <citetitle>Programmer's Guide</citetitle>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-iodbc</option></term>
-       <listitem>
-        <para>
-         Build the ODBC driver for use with <productname>iODBC</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-unixodbc</option></term>
-       <listitem>
-        <para>
-         Build the ODBC driver for use with <productname>unixODBC</>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-odbcinst=<replaceable>DIRECTORY</></option></term>
-       <listitem>
-        <para>
-         Specifies the directory where the ODBC driver will expect its
-         <filename>odbcinst.ini</> configuration file. The default is
-         <filename>/usr/local/pgsql/etc</filename> or whatever you
-         specified as <option>--sysconfdir</option>. It should be
-         arranged that the driver reads the same file as the driver
-         manager.
-        </para>
-
-        <para>
-         If either the option <option>--with-iodbc</option> or the
-         option <option>--with-unixodbc</option> is used, this option
-         will be ignored because in that case the driver manager
-         handles the location of the configuration file.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-java</option></term>
-       <listitem>
-        <para>
-         Build the <acronym>JDBC</acronym> driver and associated Java
-         packages.  This option requires
-         <application>Ant</application> to be installed (as well as a
-         <acronym>JDK</acronym>, of course).  Refer to the
-         <acronym>JDBC</acronym> driver documentation in the
-         <citetitle>Programmer's Guide</citetitle> for more
-         information.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--with-krb4<optional>=<replaceable>DIRECTORY</></></option></term>
-       <term><option>--with-krb5<optional>=<replaceable>DIRECTORY</></></option></term>
-       <listitem>
-        <para>
-         Build with support for Kerberos authentication. You can use
-         either Kerberos version 4 or 5, but not both. The
-         <replaceable>DIRECTORY</> argument specifies the root
-         directory of the Kerberos installation;
-         <filename>/usr/athena</> is assumed as default. If the
-         relevant header files and libraries are not under a common
-         parent directory, then you must use the
-         <option>--with-includes</> and <option>--with-libraries</>
-         options in addition to this option. If, on the other hand,
-         the required files are in a location that is searched by
-         default (e.g., <filename>/usr/lib</>), then you can leave off
-         the argument.
-        </para>
-
-        <para>
-         <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 name of the Kerberos service principal.
-         <literal>postgres</literal> is the default. There's probably no
-         reason to change this.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <indexterm>
-        <primary>OpenSSL</primary>
-        <seealso>SSL</seealso>
-       </indexterm>
-
-       <term><option>--with-openssl<optional>=<replaceable>DIRECTORY</></></option></term>
-       <listitem>
-        <para>
-         Build with support for <acronym>SSL</> (encrypted) connections. 
-         This requires the <productname>OpenSSL</> package to be installed.
-         The <replaceable>DIRECTORY</> argument specifies the
-         root directory of the <productname>OpenSSL</> installation; the
-         default is <filename>/usr/local/ssl</>.
-        </para>
-
-        <para>
-         <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</> (Pluggable Authentication Modules)
-	 support.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--enable-syslog</option></term>
-       <listitem>
-        <para>
-         Enables the <productname>PostgreSQL</> server to use the
-         <systemitem>syslog</> logging facility. (Using this option does not mean
-         that you must log with <systemitem>syslog</> or even that it will be done
-         by default, it simply makes it possible to turn that option
-         on at run time.)
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--without-readline</option></term>
-       <listitem>
-        <para>
-         Prevents the use of the Readline library.  This disables
-         command-line editing and history in
-         <application>psql</application>, so it is not recommended.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><option>--without-zlib</option></term>
-       <listitem>
-        <para>
-         Prevents the use of the Zlib library.  This disables
-         compression support in <application>pg_dump</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 through 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 may 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-cassert</option></term>
-       <listitem>
-        <para>
-	 Enables <firstterm>assertion</> checks in the server, which test for
-	 many <quote>can't happen</> conditions.  This is invaluable for
-	 code development purposes, but the tests slow things down a little.
-	 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.  Currently, 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 will work only if you use GCC.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-   </para>
-
-   <para>
-    If you prefer a C or C++ compiler different from the one
-    <filename>configure</filename> picks then you can set the
-    environment variables <envar>CC</> or <envar>CXX</envar>,
-    respectively, to the program of your choice.  Similarly, you can
-    override the default compiler flags with the <envar>CFLAGS</envar>
-    and <envar>CXXFLAGS</envar> variables.  For example:
-<screen>
-<userinput>env CC=/opt/bin/gcc CFLAGS='-O2 -pipe' ./configure</>
-</screen>
-   </para>
-  </step>
-
-  <step>
-   <title>Build</title>
-
-   <para>
-    To start the build, type
-<screen>
-<userinput>gmake</userinput>
-</screen>
-    (Remember to use <acronym>GNU</> <application>make</>.) The build
-    may take anywhere from 5 minutes to half an hour depending on your
-    hardware. The last line displayed should be
-<screen>
-All of PostgreSQL is successfully made. Ready to install.
-</screen>
-   </para>
-  </step>
-
-  <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.)
-    It is possible that some tests fail, due to differences in error
-    message wording or floating point results.
-    <![%standalone-include[The file
-    <filename>src/test/regress/README</> and the
-    <citetitle>Administrator's Guide</citetitle> 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>
-
-  <step id="install">
-   <title>Installing The Files</title>
-
-   <note>
-    <para>
-     If you are upgrading an existing system and are going to install
-     the new files over the old ones, then you should have backed up
-     your data and shut down the old server by now, as explained in
-     <xref linkend="install-upgrading"> above.
-    </para>
-   </note>
-
-   <para>
-    To install <productname>PostgreSQL</> enter
-<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 could create the target
-    directories in advance and arrange for appropriate permissions to
-    be granted.
-   </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>
-    If you built the Perl or Python interfaces and you were not the
-    root user when you executed the above command then that part of
-    the installation probably failed. In that case you should become
-    the root user and then do
-<screen>
-<userinput>gmake -C src/interfaces/perl5 install</userinput>
-<userinput>gmake -C src/interfaces/python install</userinput>
-</screen>
-    If you do not have superuser
-    access you are on your own: you can still take the required files
-    and place them in other directories where Perl or Python can find
-    them, but how to do that is left as an exercise.
-   </para>
-
-   <para>
-    The standard installation provides only the header files needed for client
-    application development.  If you plan to do any server-side program
-    development (such as custom functions or data types written in C),
-    then you may want to install the entire <productname>PostgreSQL</>
-    include tree into your target include directory.  To do that, enter
-<screen>
-<userinput>gmake install-all-headers</userinput>
-</screen>
-    This adds a megabyte or two to the installation footprint, and is only
-    useful if you don't plan to keep the whole source tree around for
-    reference.  (If you do, you can just use the source's include
-    directory when building server-side software.)
-   </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>
-    </para>
-   </formalpara>
-
-   <para>
-    To undo the installation use the command <command>gmake
-    uninstall</>. However, this will not remove any created directories.
-   </para>
-  </step>
-  </procedure>
-
-  <para>
-   After the installation you can make room by removing the built
-   files from the source tree with the <command>gmake clean</>
-   command. This will preserve the files made by the configure
-   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 from the same source tree you must do
-   this and re-configure for each build.
-  </para>
-
-  <para>
-   If you perform a build and then discover that your configure options
-   were wrong, or if you change anything that configure investigates
-   (for example, you install GNU <application>Readline</>), then it's
-   a good idea to do <command>gmake distclean</> before reconfiguring
-   and rebuilding.  Without this, your changes in configuration choices
-   may 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 libraries</primary>
-   </indexterm>
-
-   <para>
-    On some systems that have shared libraries (which most systems do)
-    you need to tell your 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</>.
-   </para>
-
-   <para>
-    The method to set the shared library search path varies between
-    platforms, but the most widely usable 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://www.visi.com/~barr/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 Linux systems the following is the preferred method, but you
-    must have root access. Edit the file <filename>/etc/ld.so.conf</>
-    to add a line
-<programlisting>
-<filename>/usr/local/pgsql/lib</>
-</programlisting>
-    Then run command <command>/sbin/ldconfig</>.
-   </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
-    on 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>
-    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
-<programlisting>
-/sbin/ldconfig /usr/local/pgsql/lib
-</programlisting>
-    (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.
-   </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 need to
-    add <filename>/usr/local/pgsql/bin</> (or whatever you set
-    <option><literal>--bindir</></> to in <xref linkend="configure">)
-    into your <envar>PATH</>. 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 every user):
-<programlisting>
-PATH=/usr/local/pgsql/bin:$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>
-     <seealso>man pages</seealso>
-    </indexterm>
-    To enable your system to find the <application>man</>
-    documentation, you need to add a line like the following to a
-    shell start-up file:
-<programlisting>
-MANPATH=/usr/local/pgsql/man:$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>
-  </sect2>
- </sect1>
-
-
-<![%standalone-include;[
- <sect1 id="install-getting-started">
-  <title>Getting Started</title>
-
-  <para>
-   The following is a quick summary of how to get <productname>PostgreSQL</> up and
-   running once installed. The <citetitle>Administrator's Guide</>
-   contains more information.
-  </para>
-
-  <procedure>
-   <step>
-    <para>
-     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.
-<screen>
-<userinput>adduser postgres</>
-</screen>
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Create a database installation with the <command>initdb</>
-     command. To run <command>initdb</> you must be logged in to your
-     <productname>PostgreSQL</> server account. It will not work as
-     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>
-   </step>
-
-   <step>
-    <para>
-     The previous 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/postmaster -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/postmaster -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>
-
-    <para>
-     In order to allow TCP/IP connections (rather than only Unix
-     domain socket ones) you need to pass the <option>-i</> option to
-     <filename>postmaster</>.
-    </para>
-   </step>
-
-   <step>
-    <para>
-     Create a database:
-<screen>
-<userinput>createdb testdb</>
-</screen>
-     Then enter
-<screen>
-<userinput>psql testdb</>
-</screen>
-     to connect to that database. At the prompt you can enter SQL
-     commands and start experimenting.
-    </para>
-   </step>
-  </procedure>
- </sect1>
-
- <sect1 id="install-whatnow">
-  <title>What Now?</title>
-
-  <para>
-   <itemizedlist>
-    <listitem>
-     <para>
-      The <productname>PostgreSQL</> distribution contains a
-      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 <citetitle>Tutorial</> 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 the <citetitle>Administrator's Guide</citetitle>,
-      which contains information about how to set up the database
-      server, database users, and authentication.
-     </para>
-    </listitem>
-
-    <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 <citetitle>Administrator's
-      Guide</citetitle>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Run the regression tests against the installed server (using the
-      sequential test method). If you didn't run the tests before
-      installation, you should definitely do it now. This is also
-      explained in the <citetitle>Administrator's Guide</citetitle>.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </para>
-
-<!-- do we still ship this? -->
-<!--
-  <para>
-   The documentation is also available in Postscript format. If you
-   have a Postscript printer, or have your machine already set up to
-   accept Postscript files using a print filter, then to print, for
-   example the <citetitle>User's Guide</> simply type
-<programlisting>
-cd /usr/local/pgsql/doc
-gunzip -c user.ps.gz | lpr
-</programlisting>
-   Here is how you might do it if you have <productname>Ghostscript</>
-   installed on your system and are writing to a Laserjet printer.
-<programlisting>
-gunzip -c user.ps.gz \
-    | gs -sDEVICE=laserjet -r300 -q -dNOPAUSE -sOutputFile=- \
-    | lpr
-</programlisting>
-   Printer setups can vary wildly from system to system. If in doubt,
-   consult your manuals or your local expert.
-  </para>
--->
-
- </sect1>
-]]>
-
-
- <sect1 id="supported-platforms">
-  <title>Supported Platforms</title>
-
-  <para>
-   <productname>PostgreSQL</> has been verified by the developer
-   community to work on the platforms listed below. A supported
-   platform generally means that <productname>PostgreSQL</> builds and
-   installs according to these instructions and that the regression
-   tests pass.
-  </para>
-
-  <note>
-   <para>
-    If you are having problems with the installation on a supported
-    platform, please write to <email>pgsql-bugs@postgresql.org</email>
-    or <email>pgsql-ports@postgresql.org</email>, not to the people
-    listed here.
-   </para>
-  </note>
-
-    <informaltable>
-     <tgroup cols="5">
-      <thead>
-       <row>
-	<entry><acronym>OS</acronym></entry>
-	<entry>Processor</entry>
-	<entry>Version</entry>
-	<entry>Reported</entry>
-	<entry>Remarks</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-	<entry><systemitem class="osname">AIX</></entry>
-	<entry><systemitem>RS6000</></entry>
-	<entry>7.2</entry>
-	<entry>2001-12-19,
-	 Andreas Zeugswetter (<email>ZeugswetterA@spardat.at</email>),
-	 Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
-        <entry>see also <filename>doc/FAQ_AIX</filename></entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">BeOS</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-29,
-	 Cyril Velter (<email>cyril.velter@libertysurf.fr</email>)</entry>
-        <entry>5.0.4</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">BSD/OS</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-27,
-	 Bruce Momjian (<email>pgman@candle.pha.pa.us</email>)</entry>
-        <entry>4.2</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">FreeBSD</></entry>
-	<entry><systemitem>Alpha</></entry>
-	<entry>7.2</entry>
-	<entry>2001-12-18,
-	 Chris Kings-Lynne (<email>chriskl@familyhealth.com.au</email>)</entry>
-        <entry></entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">FreeBSD</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-14,
-	 Chris Kings-Lynne (<email>chriskl@familyhealth.com.au</email>)</entry>
-        <entry></entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">HP-UX</></entry>
-	<entry><systemitem>PA-RISC</></entry>
-	<entry>7.2</entry>
-        <entry>2001-11-29,
-	 Joseph Conway (<email>Joseph.Conway@home.com</email>),
-	 Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
-        <entry>11.00 and 10.20; see also <filename>doc/FAQ_HPUX</filename></entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">IRIX</></entry>
-	<entry><systemitem>MIPS</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-28,
-	 Luis Amigo (<email>lamigo@atc.unican.es</email>)</entry>
-	<entry>6.5.13, MIPSPro 7.30</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Linux</></entry>
-	<entry><systemitem>Alpha</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-16,
-	 Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
-	<entry>2.2.18; tested at SourceForge</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Linux</></entry>
-	<entry><systemitem>armv4l</></entry>
-	<entry>7.2</entry>
-	<entry>2001-12-10,
-	 Mark Knox (<email>segfault@hardline.org</email>)</entry>
-	<entry>2.2.x</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Linux</></entry>
-	<entry><systemitem>MIPS</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-15,
-	 Hisao Shibuya (<email>shibuya@alpha.or.jp</>)</entry>
-	<entry>2.0.x; <productname>Cobalt Qube2</></entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Linux</></entry>
-	<entry><systemitem>PlayStation 2</></entry>
-	<entry>7.2</entry>
-	<entry>2001-12-12,
-	 Permaine Cheung <email>pcheung@redhat.com</email>)</entry>
-	<entry>#undef HAS_TEST_AND_SET, slock_t</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Linux</></entry>
-	<entry><systemitem>PPC74xx</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-16,
-	 Tom Lane (<email>tgl@sss.pgh.pa.us</email>)</entry>
-	<entry>2.2.18; Apple G3</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Linux</></entry>
-	<entry><systemitem>S/390</></entry>
-	<entry>7.2</entry>
-	<entry>2001-12-12,
-	 Permaine Cheung <email>pcheung@redhat.com</email>)</entry>
-	<entry></entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Linux</></entry>
-	<entry><systemitem>Sparc</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-28, 
-	 Doug McNaught (<email>doug@wireboard.com</email>)</entry>
-	<entry>2.2.19</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Linux</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-15,
-	 Thomas Lockhart (<email>lockhart@fourpalms.org</email>)</entry>
-	<entry>2.0.x, 2.2.x, 2.4.x</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">MacOS X</></entry>
-	<entry><systemitem>PPC</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-28,
-	 Gavin Sherry (<email>swm@linuxworld.com.au</email>)</entry>
-	<entry>10.1.x</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">NetBSD</></entry>
-	<entry><systemitem>Alpha</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-20,
-	 Thomas Thai (<email>tom@minnesota.com</email>)</entry>
-	<entry>1.5W</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">NetBSD</></entry>
-	<entry><systemitem>arm32</></entry>
-	<entry>7.1</entry>
-	<entry>2001-03-21,
-	 Patrick Welche (<email>prlw1@cam.ac.uk</email>)</entry>
-	<entry>1.5E</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">NetBSD</></entry>
-	<entry><systemitem>m68k</></entry>
-	<entry>7.0</entry>
-	<entry>2000-04-10,
-	 Henry B. Hotz (<email>hotz@jpl.nasa.gov</email>)</entry>
-	<entry>Mac 8xx</entry>
-       </row>
-      <row>
-       <entry><systemitem class="osname">NetBSD</></entry>
-       <entry><systemitem>MIPS</></entry>
-       <entry>7.2.1</entry>
-       <entry>2002-06-13,
-        Warwick Hunter (<email>whunter@agile.tv</email>)</entry>
-       <entry>1.5.3</entry>
-      </row>
-       <row>
-	<entry><systemitem class="osname">NetBSD</></entry>
-	<entry><systemitem>PPC</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-28,
-	 Bill Studenmund (<email>wrstuden@netbsd.org</email>)</entry>
-	<entry>1.5</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">NetBSD</></entry>
-	<entry><systemitem>Sparc</></entry>
-	<entry>7.2</entry>
-	<entry>2001-12-03,
-	 Matthew Green (<email>mrg@eterna.com.au</email>)</entry>
-	<entry>32- and 64-bit builds</entry>
-       </row>
-       <row>
-        <entry><systemitem class="osname">NetBSD</></entry>
-        <entry><systemitem>VAX</></entry>
-        <entry>7.1</entry>
-        <entry>2001-03-30,
-	 Tom I. Helbekkmo (<email>tih@kpnQwest.no</email>)</entry>
-        <entry>1.5</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">NetBSD</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-28,
-	 Bill Studenmund (<email>wrstuden@netbsd.org</email>)</entry>
-	<entry>1.5</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">OpenBSD</></entry>
-	<entry><systemitem>Sparc</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-27,
-	 Brandon Palmer (<email>bpalmer@crimelabs.net</email>)</entry>
-        <entry>3.0</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">OpenBSD</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-26,
-	 Brandon Palmer (<email>bpalmer@crimelabs.net</email>)</entry>
-        <entry>3.0</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Open UNIX</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-28,
-	 OU-8 Larry Rosenman (<email>ler@lerctr.org</email>),
-	 UW-7 Olivier Prenant (<email>ohp@pyrenet.fr</email>)</entry>
-	<entry>see also <filename>doc/FAQ_SCO</filename></entry>
-       </row>
-     <row>
-      <entry><systemitem class="osname">QNX 4 RTOS</></entry>
-      <entry><systemitem>x86</></entry>
-      <entry>7.2</entry>
-      <entry>2001-12-10,
-       Bernd Tegge (<email>tegge@repas-aeg.de</email>)
-      </entry>
-      <entry>4.25; see also <filename>doc/FAQ_QNX4</filename></entry>
-     </row>
-       <row>
-	<entry><systemitem class="osname">Solaris</></entry>
-	<entry><systemitem>Sparc</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-12,
-	 Andrew Sullivan (<email>andrew@libertyrms.com</email>)</entry>
-	<entry>2.6-8; see also <filename>doc/FAQ_Solaris</filename></entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Solaris</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-28, 
-	 Martin Renters (<email>martin@datafax.com</email>)</entry>
-	<entry>2.8; see also <filename>doc/FAQ_Solaris</filename></entry>
-       </row>
-      <row>
-       <entry><systemitem class="osname">SunOS 4</></entry>
-       <entry><systemitem>Sparc</></entry>
-       <entry>7.2</entry>
-       <entry>2001-12-04, Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
-       <entry></entry>
-      </row>
-       <row>
-	<entry><systemitem class="osname">Tru64 UNIX</></entry>
-	<entry><systemitem>Alpha</></entry>
-	<entry>7.2</entry>
-	<entry>2001-11-26,
-	 Alessio Bragadini (<email>alessio@albourne.com</email>),
-         Bernd Tegge (<email>tegge@repas-aeg.de</email>)</entry>
-        <entry>5.0; 4.0g with cc and gcc</entry>
-       </row>
-       <row>
-	<entry><systemitem class="osname">Windows</></entry>
-	<entry><systemitem>x86</></entry>
-	<entry>7.2</entry>
-	<entry>2001-12-13,
-	 Dave Page (<email>dpage@vale-housing.co.uk</email>),
-	 Jason Tishler (<email>jason@tishler.net</email>)</entry>
-        <entry>with <application>Cygwin</application>; see <filename>doc/FAQ_MSWIN</filename></entry>
-       </row>
-      <row>
-       <entry><systemitem class="osname">Windows</></entry>
-       <entry><systemitem>x86</></entry>
-       <entry>7.2</entry>
-       <entry>2001-12-10,
-	Dave Page (<email>dpage@vale-housing.co.uk</email>)</entry>
-       <entry>
-	native is client-side only;
-<![%standalone-include[see Administrator's Guide]]>
-<![%standalone-ignore[see <xref linkend="install-win32">]]>
-       </entry>
-      </row>
-      </tbody>
-     </tgroup>
-    </informaltable>
-
-  <formalpara>
-   <title>Unsupported Platforms:</title>
-   <para>
-    The following platforms are either known not to work, or they used
-    to work in a previous release and we did not receive explicit
-    confirmation of a successful test with version &majorversion; at
-    the time this list was compiled.  We include these here to let you
-    know that these platforms <emphasis>could</> be supported if given
-    some attention.
-   </para>
-  </formalpara>
-
-  <informaltable>
-   <tgroup cols="5">
-    <thead>
-     <row>
-      <entry><acronym>OS</acronym></entry>
-      <entry>Processor</entry>
-      <entry>Version</entry>
-      <entry>Reported</entry>
-      <entry>Remarks</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><systemitem class="osname">DG/UX 5.4R4.11</></entry>
-      <entry><systemitem>m88k</></entry>
-      <entry>6.3</entry>
-      <entry>1998-03-01, Brian E Gallew (<email>geek+@cmu.edu</email>)</entry>
-      <entry>no recent reports</entry>
-     </row>
-     <row>
-      <entry><systemitem class="osname">MkLinux DR1</></entry>
-      <entry><systemitem>PPC750</></entry>
-      <entry>7.0</entry>
-      <entry>2001-04-03, Tatsuo Ishii (<email>t-ishii@sra.co.jp</email>)</entry>
-      <entry>7.1 needs OS update?</entry>
-     </row>
-     <row>
-      <entry><systemitem class="osname">NeXTSTEP</></entry>
-      <entry><systemitem>x86</></entry>
-      <entry>6.x</entry>
-      <entry>1998-03-01, David Wetzel (<email>dave@turbocat.de</email>)</entry>
-      <entry>bit rot suspected</entry>
-     </row>
-     <row>
-      <entry><systemitem class="osname">QNX RTOS v6</></entry>
-      <entry><systemitem>x86</></entry>
-      <entry>7.2</entry>
-      <entry>2001-11-20, Igor Kovalenko (<email>Igor.Kovalenko@motorola.com</email>)</entry>
-      <entry>patches available in archives, but too late for 7.2</entry>
-     </row>
-     <row>
-      <entry><systemitem class="osname">SCO OpenServer 5</></entry>
-      <entry><systemitem>x86</></entry>
-      <entry>6.5</entry>
-      <entry>1999-05-25, Andrew Merrill (<email>andrew@compclass.com</>)</entry>
-      <entry>&version; should work, but no reports; see also <filename>doc/FAQ_SCO</filename></entry>
-     </row>
-     <row>
-      <entry><systemitem class="osname">System V R4</></entry>
-      <entry><systemitem>m88k</></entry>
-      <entry>6.2.1</entry>
-      <entry>1998-03-01, Doug Winterburn (<email>dlw@seavme.xroads.com</email>)</entry>
-      <entry>needs new <acronym>TAS</acronym> spinlock code</entry>
-     </row>
-     <row>
-      <entry><systemitem class="osname">System V R4</></entry>
-      <entry><systemitem>MIPS</></entry>
-      <entry>6.4</entry>
-      <entry>1998-10-28, Frank Ridderbusch (<email>ridderbusch.pad@sni.de</email>)</entry>
-      <entry>no recent reports</entry>
-     </row>
-     <row>
-      <entry><systemitem class="osname">Ultrix</></entry>
-      <entry><systemitem>MIPS</></entry>
-      <entry>7.1</entry>
-      <entry>2001-03-26</entry>
-      <entry><acronym>TAS</acronym> spinlock code not detected</entry>
-     </row>
-     <row>
-      <entry><systemitem class="osname">Ultrix</></entry>
-      <entry><systemitem>VAX</></entry>
-      <entry>6.x</entry>
-      <entry>1998-03-01</entry>
-      <entry></entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </informaltable>
- </sect1>
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-tabs-mode:nil
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/share/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/intro.sgml b/doc/src/sgml/intro.sgml
deleted file mode 100644
index 5b98495e93d..00000000000
--- a/doc/src/sgml/intro.sgml
+++ /dev/null
@@ -1,121 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.19 2002/01/07 02:29:12 petere Exp $
--->
-
- <preface id="preface">
-  <title>Preface</title>
-
-  <sect1 id="intro-whatis">
-   <title> What is <productname>PostgreSQL</productname>?</title>
-
-   <para>
-    <productname>PostgreSQL</productname> is an object-relational
-    database management system (<acronym>ORDBMS</acronym>) based on
-    <ulink url="http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/postgres.html">
-    <productname>POSTGRES, Version 4.2</productname></ulink>,
-    developed at the University of California at Berkeley Computer
-    Science Department.  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.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname> is an open-source descendant of
-    this original Berkeley code.  It provides SQL92/SQL99 language support
-    and other modern features.
-   </para>
-
-   <para>
-    <productname>POSTGRES</productname> pioneered many of the
-    object-relational concepts now becoming available in some commercial
-    databases.
-    Traditional   relational  database  management  systems
-    (<acronym>RDBMS</acronym>) support a data model consisting of a collection
-    of named relations, containing attributes of a specific
-    type.  In current commercial  systems,  possible  types
-    include  floating  point  numbers,  integers, character
-    strings, money, and dates.  It is  commonly  recognized
-    that  this model is inadequate for future data-processing applications.
-    The relational  model  successfully  replaced  previous
-    models  in  part  because  of its <quote>Spartan simplicity</quote>.
-    However, this simplicity makes  the
-    implementation  of  certain applications very difficult.
-    <productname>PostgreSQL</productname> offers  substantial additional
-    power  by  incorporating  the following additional
-    concepts in such a way that  users  can  easily
-    extend the system:
-
-    <itemizedlist spacing="compact">
-     <listitem>
-      <simpara>inheritance</>
-     </listitem>
-     <listitem>
-      <simpara>data types</>
-     </listitem>
-     <listitem>
-      <simpara>functions</simpara>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    Other features provide additional power and flexibility:
-
-    <itemizedlist spacing="compact">
-     <listitem>
-      <simpara>constraints</simpara>
-     </listitem>
-     <listitem>
-      <simpara>triggers</simpara>
-     </listitem>
-     <listitem>
-      <simpara>rules</simpara>
-     </listitem>
-     <listitem>
-      <simpara>transactional integrity</simpara>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    These features put <productname>PostgreSQL</productname> into the
-    category of databases referred to as
-    <firstterm>object-relational</firstterm>. Note that this is distinct
-    from those referred to as <firstterm>object-oriented</firstterm>,
-    which in general are not as well suited to supporting
-    traditional relational database languages.
-    So, although <productname>PostgreSQL</productname> has some
-    object-oriented features, it is firmly in the relational database
-    world. In fact, some commercial databases have recently
-    incorporated features pioneered by <productname>PostgreSQL</productname>.
-   </para>
-
-  </sect1>
-
-   &history;
-   &info;
-   &notation;
-   &problems;
-   &y2k;
-
- </preface>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/jdbc.sgml b/doc/src/sgml/jdbc.sgml
deleted file mode 100644
index c77817d16a4..00000000000
--- a/doc/src/sgml/jdbc.sgml
+++ /dev/null
@@ -1,2605 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.36 2002/03/22 19:20:11 petere Exp $
--->
-
- <chapter id="jdbc">
-  <title><acronym>JDBC</acronym> Interface</title>
-
-  <note>
-   <title>Author</title>
-   <para>
-    Originally written by Peter T. Mount (<email>peter@retep.org.uk</email>), 
-    the original author of the <acronym>JDBC</acronym> driver.
-   </para>
-  </note>
-
-  <para>
-   <acronym>JDBC</acronym> is a core <acronym>API</acronym> of Java 1.1 and later.
-   It provides a standard set of
-   interfaces to <acronym>SQL</acronym>-compliant databases.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</> provides a <firstterm>type
-   4</firstterm> <acronym>JDBC</acronym> Driver.  Type 4 indicates
-   that the driver is written in Pure Java, and communicates in the
-   database system's own network protocol. Because of this, the driver
-   is platform independent; once compiled, the driver can be used on
-   any system.
-  </para>
-
-  <para>
-   This chapter is not intended as a complete guide to
-   <acronym>JDBC</acronym> programming, but should help to get you
-   started. For more information refer to the standard
-   <acronym>JDBC</acronym> <acronym>API</acronym> documentation.
-   Also, take a look at the examples included with the source. The
-   basic example is used here.
-  </para>
-
- <sect1 id="jdbc-setup">
-  <title>Setting up the <acronym>JDBC</acronym> Driver</title>
-
-  <sect2 id="jdbc-build">
-   <title>Getting the Driver</title>
-
-   <para>
-    Precompiled versions of the driver can be downloaded from
-    the <ulink
-    url="http://jdbc.postgresql.org"><productname>PostgreSQL</productname>
-    <acronym>JDBC</acronym> web site</ulink>.
-   </para>
-
-   <para>
-    Alternatively you can build the driver from source.  Although you 
-    should only need to do this if you are making changes to the source
-    code.
-   </para>
-
-   <para>
-    Starting with <productname>PostgreSQL</productname> version 7.1,
-    the <acronym>JDBC</acronym> driver is built using
-    <application>Ant</application>, a special tool for building
-    Java-based packages.  You should download
-    <application>Ant</application> from the <ulink
-    url="http://jakarta.apache.org/ant/index.html"><application>Ant</application>
-    web site</ulink> and install it before proceeding.  Precompiled
-    <application>Ant</application> distributions are typically set up
-    to read a file <filename>.antrc</filename> in the current user's
-    home directory for configuration.  For example, to use a different
-    <acronym>JDK</acronym> than the default, this may work:
-<programlisting>
-JAVA_HOME=/usr/local/sun-jdk1.3
-JAVACMD=$JAVA_HOME/bin/java
-</programlisting>
-   </para>
-
-   <para>
-    To build the driver, add the <option>--with-java</option> option to your
-    <filename>configure</filename> command line, e.g.,
-<screen>
-<prompt>$</prompt> <userinput>./configure --prefix=<replaceable>xxx</replaceable> --with-java ...</userinput>
-</screen>
-    This will build and install the driver along with the rest of the
-    <productname>PostgreSQL</productname> package when you issue the
-    <literal>make/gmake</literal> and <literal>make/gmake install</literal>
-    commands.  If you only want to build the driver and not the rest
-    of <productname>PostgreSQL</productname>, change into the
-    directory <filename
-    class="directory">src/interfaces/jdbc</filename> and issue the
-    respective <literal>make/gmake</literal> command there.  Refer to the
-    <productname>PostgreSQL</productname> installation instructions
-    for more information about the configuration and build process.
-   </para>
-
-   <para>When building the driver from source the jar file that is created
-    will be named <filename>postgresql.jar</filename>.  The build will 
-    create this file in the <filename>src/interfaces/jdbc/jars</filename>
-    directory.  The resulting driver will be built for the version of 
-    Java you are running.  If you build with a 1.1 JDK you will build
-    a version that supports the jdbc1 specification, if you build with a 
-    Java2 JDK (i.e. JDK1.2 or JDK1.3) you will build a version that 
-    supports the jdbc2 specification. 
-   </para>
- 
-   <note>
-    <para>
-     Do not try to build the driver by calling <command>javac</command> 
-     directly, as the driver uses some dynamic loading techniques for
-     performance reasons, and <command>javac</command> cannot cope.
-     Do not try to run <command>ant</command> directly either, because
-     some configuration information is communicated through the
-     makefiles.  Running <command>ant</command> directly without
-     providing these parameters will result in a broken driver.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="jdbc-classpath">
-   <title>Setting up the Class Path</title>
-
-   <para>
-    To use the driver, the jar archive (named
-    <filename>postgresql.jar</filename> if you built from source, otherwise
-    it will likely be named <filename>jdbc7.2-1.1.jar</filename> or 
-    <filename>jdbc7.2-1.2.jar</filename> for the jdbc1 and jdbc2 versions
-    respectively)
-    needs to be included in the
-    class path, either by putting it in the <envar>CLASSPATH</envar>
-    environment variable, or by using flags on the
-    <command>java</command> command line.  By default, the jar archive
-    is installed in the directory <filename
-    class="directory">/usr/local/pgsql/share/java</filename>.  You may
-    have it in a different directory if you used the
-    <option>--prefix</option> option when you ran
-    <filename>configure</filename>, or if you are using a binary distribution
-    that places it in some different location.
-   </para>
-
-   <informalexample>
-    <para>
-     For instance, I have an application that uses the
-     <acronym>JDBC</acronym> driver to access a large database
-     containing astronomical objects. I have the application and the
-     <acronym>JDBC</acronym> driver installed in the <filename
-     class="directory">/usr/local/lib</filename> directory, and the
-     Java <acronym>JDK</acronym> installed in
-     <filename>/usr/local/jdk1.3.1</filename>.  To run the
-     application, I would use:
-<programlisting>
-export CLASSPATH=/usr/local/lib/finder.jar<co id="co.jdbc-finder">:/usr/local/pgsql/share/java/postgresql.jar:.
-java Finder
-</programlisting>
-     <calloutlist>
-      <callout arearefs="co.jdbc-finder">
-       <para>
-        <filename>finder.jar</filename> contains the Finder application.
-       </para>
-      </callout>
-     </calloutlist>
-    </para>
-
-    <para>
-     Loading the driver from within the application is covered in
-     <xref linkend="jdbc-use">.
-    </para>
-   </informalexample>
-  </sect2>
-
-  <sect2 id="jdbc-prepare">
-   <title>Preparing the Database for <acronym>JDBC</acronym></title>
-
-   <para>
-    Because Java only uses TCP/IP connections, the
-    <application>PostgreSQL</application> server must be configured to
-    accept TCP/IP connections.  This can be done by setting 
-    <literal>tcpip_socket = true</literal> in the 
-    <filename>postgresql.conf</filename> file or by supplying the
-    <option>-i</option> option flag when starting
-    <command>postmaster</command>.
-   </para>
-
-   <para>
-    Also, the client authentication setup in the
-    <filename>pg_hba.conf</filename> file may need to be configured.
-    Refer to the <citetitle>Administrator's Guide</citetitle> for
-    details.  The <acronym>JDBC</acronym> Driver supports trust,
-    ident, password, md5, and crypt authentication methods.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="jdbc-use">
-  <title>Using the Driver</title>
-
-  <sect2 id="jdbc-import">
-   <title>Importing <acronym>JDBC</acronym></title>
-
-   <para>
-    Any source that uses <acronym>JDBC</acronym> needs to import the
-    <literal>java.sql</literal> package, using:
-
-<programlisting>
-import java.sql.*;
-</programlisting>
-
-    <important>
-     <para>
-      Do not import the <literal>org.postgresql</literal> package. If
-      you do, your source will not compile, as
-      <command>javac</command> will get confused.
-     </para>
-    </important>
-   </para>
-  </sect2>
-
-  <sect2 id="jdbc-load">
-   <title>Loading the Driver</title>
-
-   <para>
-    Before you can connect to a database, you need to load the
-    driver. There are two methods available, and it depends on your
-    code which is the best one to use.
-   </para>
-
-   <para>
-    In the first method, your code implicitly loads the driver using the
-    <function>Class.forName()</function> method.
-    For <productname>PostgreSQL</>, you would use:
-
-<programlisting>
-Class.forName("org.postgresql.Driver");
-</programlisting>
-
-    This will load the driver, and while loading, the driver will automatically
-    register itself with <acronym>JDBC</acronym>.
-
-    <note>
-     <para>
-      The <function>forName()</function> method can throw a
-      <classname>ClassNotFoundException</classname> if the driver is
-      not available.
-     </para>
-    </note>
-   </para>
-
-   <para>
-    This is the most common method to use, but restricts your code to
-    use just <productname>PostgreSQL</productname>.  If your code may
-    access another database system in the future, and you do not use
-    any <productname>PostgreSQL</productname>-specific extensions, then
-    the second method is advisable.
-   </para>
-
-   <para>
-    The second method passes the driver as a parameter to the
-    <acronym>JVM</acronym> as it starts, using the <option>-D</option>
-    argument. Example:
-<programlisting>
-java -Djdbc.drivers=org.postgresql.Driver example.ImageViewer
-</programlisting>
-    In this example, the <acronym>JVM</acronym> will attempt to load
-    the driver as part of its initialization. Once done, the
-    <classname>ImageViewer</classname> is started.
-   </para>
-
-   <para>
-    Now, this method is the better one to use because it allows your
-    code to be used with other database packages without recompiling
-    the code. The only thing that would also change is the connection
-    <acronym>URL</acronym>, which is covered next.
-   </para>
-
-   <para>
-    One last thing: When your code then tries to open a
-    <classname>Connection</classname>, and you get a <errorname>No
-    driver available</errorname> <classname>SQLException</classname>
-    being thrown, this is probably caused by the driver not being in
-    the class path, or the value in the parameter not being correct.
-   </para>
-  </sect2>
-
-  <sect2 id="jdbc-connect">
-   <title>Connecting to the Database</title>
-
-   <para>
-    With <acronym>JDBC</acronym>, a database is represented by a
-    <acronym>URL</acronym> (Uniform Resource Locator).  With
-    <application>PostgreSQL</application>, this takes one of the
-    following forms:
-
-    <itemizedlist>
-     <listitem>
-<synopsis>
-jdbc:postgresql:<replaceable class="parameter">database</replaceable>
-</synopsis>
-     </listitem>
-
-     <listitem>
-<synopsis>
-jdbc:postgresql://<replaceable class="parameter">host</replaceable>/<replaceable class="parameter">database</replaceable>
-</synopsis>
-     </listitem>
-
-     <listitem>
-<synopsis>
-jdbc:postgresql://<replaceable class="parameter">host</replaceable>:<replaceable class="parameter">port</replaceable>/<replaceable class="parameter">database</replaceable>
-</synopsis>
-     </listitem>
-    </itemizedlist>
-
-    where:
-
-    <variablelist>
-     <varlistentry>
-      <term>
-       <replaceable class="parameter">host</replaceable>
-      </term>
-      <listitem>
-       <para>
-        The host name of the server. Defaults to <literal>localhost</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       <replaceable class="parameter">port</replaceable>
-      </term>
-      <listitem>
-       <para>
-        The port number the server is listening on. Defaults to the
-        <productname>PostgreSQL</productname> standard port number (5432).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       <replaceable class="parameter">database</replaceable>
-      </term>
-      <listitem>
-       <para>
-        The database name.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    To connect, you need to get a <classname>Connection</classname> instance from 
-    <acronym>JDBC</acronym>. To do this,
-    you would use the <function>DriverManager.getConnection()</function> method:
-
-<programlisting>
-Connection db = DriverManager.getConnection(url, username, password);
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="jdbc-disconnect">
-   <title>Closing the Connection</title>
-
-   <para>
-    To close the database connection, simply call the
-    <function>close()</function> method to the <classname>Connection</classname>:
-<programlisting>
-db.close();
-</programlisting>
-   </para>
-  </sect2>
- </sect1>
-
-
-  <sect1 id="jdbc-query">
-   <title>Issuing a Query and Processing the Result</title>
-
-   <para>
-    Any time you want to issue <acronym>SQL</acronym> statements to
-    the database, you require a <classname>Statement</classname> or 
-    <classname>PreparedStatement</classname> instance. Once you have 
-    a <classname>Statement</classname> or 
-    <classname>PreparedStatement</classname>, you can use issue a
-    query. This will return a <classname>ResultSet</classname>
-    instance, which contains the entire result.  <xref
-    linkend="jdbc-query-example"> illustrates this process.
-   </para>
-
-   <example id="jdbc-query-example">
-    <title>Processing a Simple Query in <acronym>JDCB</acronym></title>
-
-    <para>
-     This example will issue a simple query and print out the first
-     column of each row using a <classname>Statement</classname>.
-<programlisting>
-Statement st = db.createStatement();
-ResultSet rs = st.executeQuery("SELECT * FROM mytable where columnfoo = 500");
-while(rs.next()) {
-    System.out.print("Column 1 returned ");
-    System.out.println(rs.getString(1));
-}
-rs.close();
-st.close();
-</programlisting>
-    </para>
-
-    <para>
-     This example will issue the same query as before using 
-     a <classname>PreparedStatement</classname>
-     and a bind value in the query.
-<programlisting>
-int foovalue = 500;
-PreparedStatement st = db.prepareStatement("SELECT * FROM mytable where columnfoo = ?");
-st.setInt(1, foovalue);
-ResultSet rs = st.executeQuery();
-while(rs.next()) {
-    System.out.print("Column 1 returned ");
-    System.out.println(rs.getString(1));
-}
-rs.close();
-st.close();
-</programlisting>
-    </para>
-   </example>
-
-   <sect2>
-    <title>Using the <classname>Statement</classname> or <classname>
-    PreparedStatement</classname> Interface</title>
-
-    <para>
-     The following must be considered when using the
-     <classname>Statement</classname> or 
-     <classname>PreparedStatement</classname> interface:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        You can use a single <classname>Statement</classname> instance
-        as many times as you want. You could create one as soon as you
-        open the connection and use it for the connection's
-        lifetime. But you have to remember that only one
-        <classname>ResultSet</classname> can exist per
-        <classname>Statement</classname> or 
-        <classname>PreparedStatement</classname> at a given time.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        If you need to perform a query while processing a
-        <classname>ResultSet</classname>, you can simply create and
-        use another <classname>Statement</classname>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        If you are using threads, and several are using the database,
-        you must use a separate <classname>Statement</classname> for
-        each thread. Refer to <xref linkend="jdbc-thread"> if you are
-        thinking of using threads, as it covers some important points.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        When you are done using the <classname>Statement</classname>
-        or <classname>PreparedStatement</classname>
-        you should close it.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Using the <classname>ResultSet</classname> Interface</title>
-
-    <para>
-     The following must be considered when using the
-     <classname>ResultSet</classname> interface:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        Before reading any values, you must call
-        <function>next()</function>. This returns true if there is a
-        result, but more importantly, it prepares the row for
-        processing.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Under the <acronym>JDBC</acronym> specification, you should
-        access a field only once. It is safest to stick to this rule,
-        although at the current time, the
-        <productname>PostgreSQL</productname> driver will allow you to
-        access a field as many times as you want.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        You must close a <classname>ResultSet</classname> by calling
-        <function>close()</function> once you have finished using it.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Once you make another query with the
-        <classname>Statement</classname> used to create a
-        <classname>ResultSet</classname>, the currently open
-        <classname>ResultSet</classname> instance is closed
-        automatically.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        <classname>ResultSet</classname> is currently read only.
-        You can not update data through the <classname>ResultSet</classname>.
-        If you want to update data you need to do it the old fashioned way
-        by issuing a <acronym>SQL</acronym> update statement.  This is 
-        in conformance with the <acronym>JDBC</acronym> specification 
-        which does not require drivers to provide this functionality.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="jdbc-update">
-   <title>Performing Updates</title>
-
-   <para>
-    To change data (perform an insert, update, or delete) 
-    you use the <function>executeUpdate()</function> method.
-    <function>executeUpdate()</function> is similar to the
-    <function>executeQuery()</function> used to issue a select,
-    however it doesn't return a <classname>ResultSet</classname>,
-    instead it returns the number of records affected by the insert,
-    update, or delete statement.
-   </para>
-
-  <example id="jdbc-delete-example">
-   <title>Simple Delete Example</title>
-   <para>
-     This example will issue a simple delete and print out the number
-     of rows deleted.
-<programlisting>
-int foovalue = 500;
-PreparedStatement st = db.prepareStatement("DELETE FROM mytable where columnfoo = ?");
-st.setInt(1, foovalue);
-int rowsDeleted = st.executeUpdate();
-System.out.println(rowsDeleted + " rows deleted");
-st.close();
-</programlisting>
-   </para>
-  </example>
-  </sect1>
-
-  <sect1 id="jdbc-ddl">
-   <title>Creating and Modifying Database Objects</title>
-
-   <para>
-    To create, modify or drop a database object like a table or view
-    you use the <function>execute()</function> method.
-    <function>execute</function> is similar to the
-    <function>executeQuery()</function> used to issue a select,
-    however it doesn't return a result.
-   </para>
-
-  <example id="jdbc-drop-table-example">
-   <title>Drop Table Example</title>
-   <para>
-     This example will drop a table.
-<programlisting>
-Statement st = db.createStatement();
-ResultSet rs = st.executeQuery("DROP TABLE mytable");
-st.close();
-</programlisting>
-   </para>
-  </example>
-  </sect1>
-
- <sect1 id="jdbc-binary-data">
-  <title>Storing Binary Data</title>
-
-  <para>
-    <application>PostgreSQL</application> provides two distinct ways to 
-    store binary data.  Binary data can be stored in a table using 
-    <application>PostgreSQL's</application> binary data type 
-    <type>bytea</type>, or by using the <firstterm>Large Object</firstterm>
-    feature which stores the binary data in a separate table in a special 
-    format, and refers to that table by storing a value of type 
-    <type>OID</type> in your table.
-  </para>
-
-  <para>
-    In order to determine which method is appropriate you 
-    need to understand the limitations of each method.  The 
-    <type>bytea</type> data type is not well suited for storing very 
-    large amounts of binary data.  While a column of type 
-    <type>bytea</type> can hold upto 1Gig of binary data, it would 
-    require a huge amount of memory (<acronym>RAM</acronym>) to 
-    process such a large value.  The Large Object method for 
-    storing binary data is better suited to storing very large values, 
-    but it has its own limitations.  Specifically deleting a row 
-    that contains a Large Object does not delete the Large Object.
-    Deleting the Large Object is a separate operation that needs to
-    be performed.  Large Objects also have some security
-    issues since anyone connected to the database case view 
-    and/or modify any Large Object, even if they don't have 
-    permissions to view/update the row containing the Large Object.
-  </para>
-
-  <para>
-    7.2 is the first release of the <acronym>JDBC</acronym> Driver 
-    that supports the <type>bytea</type> data type.  The introduction of 
-    this functionality in 7.2 has introduced a change in behavior 
-    as compared to previous releases.  In 7.2 the methods 
-    <function>getBytes()</function>, <function>setBytes()</function>, 
-    <function>getBinaryStream()</function>, and 
-    <function>setBinaryStream()</function> operate on 
-    the <type>bytea</type> data type.  In 7.1 these methods operated 
-    on the <type>OID</type> data type associated with Large Objects.  
-    It is possible to revert the driver back to the old 7.1 behavior 
-    by setting the <parameter>compatible</parameter> property on 
-    the <classname>Connection</classname> to a value of 
-    <literal>7.1</literal>
-  </para>
-
-  <para>
-    To use the <type>bytea</type> data type you should simply use 
-    the <function>getBytes()</function>, <function>setBytes()</function>,
-    <function>getBinaryStream()</function>, or 
-    <function>setBinaryStream()</function> methods.
-  </para>
-
-  <para>
-    To use the Large Object functionality you can use either the 
-    <classname>LargeObject</classname> <acronym>API</acronym>
-    provided by the <application>PostgreSQL</application> 
-    <acronym>JDBC</acronym> Driver, or by using the 
-    <function>getBLOB()</function> and <function>setBLOB()</function>
-    methods.
-  </para>
-
-  <important>
-   <para>
-    For <application>PostgreSQL</application>, you must access Large
-    Objects within an <acronym>SQL</acronym> transaction.  You would
-    open a transaction by using the
-    <function>setAutoCommit()</function> method with an input
-    parameter of <literal>false</literal>.
-   </para>
-  </important>
-
-  <note><para>In a future release of the
-      <acronym>JDBC</acronym> Driver, the <function>getBLOB()</function>
-      and <function>setBLOB()</function> methods may no longer 
-      interact with Large Objects and will instead work on 
-      <type>bytea</type> data types.  So it is recommended that you 
-      use the <classname>LargeObject</classname> <acronym>API</acronym> 
-      if you intend to use Large Objects.
-  </para></note>
-
-
-  <example id="jdbc-binary-data-example">
-   <title>Binary Data Examples</title>
-
-   <para>
-    For example, suppose you have a table containing the file name of
-    an image and you also want to store the image in a <type>bytea</type>
-    column:
-<programlisting>
-CREATE TABLE images (imgname text, img bytea);
-</programlisting>
-   </para>
-
-   <para>
-    To insert an image, you would use:
-<programlisting>
-File file = new File("myimage.gif");
-FileInputStream fis = new FileInputStream(file);
-PreparedStatement ps = conn.prepareStatement("INSERT INTO images VALUES (?, ?)");
-ps.setString(1, file.getName());
-ps.setBinaryStream(2, fis, file.length());
-ps.executeUpdate();
-ps.close();
-fis.close();
-</programlisting>
-
-    Here, <function>setBinaryStream()</function> transfers a set number
-    of bytes from a stream into the column of type <type>bytea</type>.
-    This also could have been done using the <function>setBytes()</function>
-    method if the contents of the image was already in a 
-    <classname>byte[]</classname>. 
-   </para>
-
-   <para>
-    Retrieving an image is even easier.  (We use
-    <classname>PreparedStatement</classname> here, but the
-    <classname>Statement</classname> class can equally be used.)
-
-<programlisting>
-PreparedStatement ps = con.prepareStatement("SELECT img FROM images WHERE imgname=?");
-ps.setString(1, "myimage.gif");
-ResultSet rs = ps.executeQuery();
-if (rs != null) {
-    while(rs.next()) {
-        byte[] imgBytes = rs.getBytes(1);
-        // use the stream in some way here
-    }
-    rs.close();
-}
-ps.close();
-</programlisting>
-   </para>
-
-   <para>
-    Here the binary data was retrieved as an
-    <classname>byte[]</classname>.  You could have used a 
-    <classname>InputStream</classname> object instead.  
-   </para>
-
-   <para>
-    Alternatively you could be storing a very large file and want to use
-    the <classname>LargeObject</classname> <acronym>API</acronym> to 
-    store the file:
-<programlisting>
-CREATE TABLE imagesLO (imgname text, imgOID OID);
-</programlisting>
-   </para>
-
-   <para>
-    To insert an image, you would use:
-<programlisting>
-// All LargeObject API calls must be within a transaction
-conn.setAutoCommit(false);
-
-// Get the Large Object Manager to perform operations with
-LargeObjectManager lobj = ((org.postgresql.Connection)conn).getLargeObjectAPI();
-
-//create a new large object
-int oid = lobj.create(LargeObjectManager.READ | LargeObjectManager.WRITE);
-
-//open the large object for write
-LargeObject obj = lobj.open(oid, LargeObjectManager.WRITE);
-
-// Now open the file
-File file = new File("myimage.gif");
-FileInputStream fis = new FileInputStream(file);
-
-// copy the data from the file to the large object
-byte buf[] = new byte[2048];
-int s, tl = 0;
-while ((s = fis.read(buf, 0, 2048)) > 0)
-{
-	obj.write(buf, 0, s);
-	tl += s;
-}
-
-// Close the large object
-obj.close();
-
-//Now insert the row into imagesLO
-PreparedStatement ps = conn.prepareStatement("INSERT INTO imagesLO VALUES (?, ?)");
-ps.setString(1, file.getName());
-ps.setInt(2, oid);
-ps.executeUpdate();
-ps.close();
-fis.close();
-</programlisting>
-</para>
-   <para>
-    Retrieving the image from the Large Object:
-
-<programlisting>
-// All LargeObject API calls must be within a transaction
-conn.setAutoCommit(false);
-
-// Get the Large Object Manager to perform operations with
-LargeObjectManager lobj = ((org.postgresql.Connection)conn).getLargeObjectAPI();
-
-PreparedStatement ps = con.prepareStatement("SELECT imgOID FROM imagesLO WHERE imgname=?");
-ps.setString(1, "myimage.gif");
-ResultSet rs = ps.executeQuery();
-if (rs != null) {
-    while(rs.next()) {
-	//open the large object for reading
-	int oid = rs.getInt(1);
-	LargeObject obj = lobj.open(oid, LargeObjectManager.READ);
-
-	//read the data
-	byte buf[] = new byte[obj.size()];
-	obj.read(buf, 0, obj.size());
-	//do something with the data read here
-
-	// Close the object
-	obj.close();
-    }
-    rs.close();
-}
-ps.close();
-</programlisting>
-   </para>
-
-  </example>
- </sect1>
-
-
- <sect1 id="jdbc-ext">
-  <title><application>PostgreSQL</application> Extensions to the
-    <acronym>JDBC</acronym> <acronym>API</acronym></title>
-
-  <para>
-   <productname>PostgreSQL</productname> is an extensible database
-   system.  You can add your own functions to the backend, which can
-   then be called from queries, or even add your own data types.  As
-   these are facilities unique to <productname>PostgreSQL</productname>,
-   we support them from Java, with a set of extension
-   <acronym>API</acronym>'s. Some features within the core of the
-   standard driver actually use these extensions to implement Large
-   Objects, etc.
-  </para>
-
-  <sect2>
-   <title>Accessing the Extensions</title>
-
-   <para>
-    To access some of the extensions, you need to use some extra
-    methods in the <classname>org.postgresql.Connection</classname>
-    class. In this case, you would need to case the return value of
-    <function>Driver.getConnection()</function>.  For example:
-<programlisting>
-Connection db = Driver.getConnection(url, username, password);
-// ...
-// later on
-Fastpath fp = ((org.postgresql.Connection)db).getFastpathAPI();
-</programlisting>
-   </para>
-
-   <sect3>
-    <title>Class <classname>org.postgresql.Connection</classname></title>
-
-<synopsis>
-public class Connection extends Object implements Connection
-
-java.lang.Object
-   |
-   +----org.postgresql.Connection
-</synopsis>
-
-    <para>
-     These are the extra methods used to gain access to
-     <productname>PostgreSQL</productname>'s extensions. Methods
-     defined by <classname>java.sql.Connection</classname> are not
-     listed.
-    </para>
-
-    <sect4>
-     <title>Methods</title>
-
-     <itemizedlist>
-      <listitem>
-<synopsis>
-public Fastpath getFastpathAPI() throws SQLException
-</synopsis>
-       <para>
-        This returns the Fastpath <acronym>API</acronym> for the
-        current connection.  It is primarily used by the Large Object
-        <acronym>API</acronym>.
-       </para>
-
-       <para>
-        The best way to use this is as follows:
-<programlisting>
-import org.postgresql.fastpath.*;
-...
-Fastpath fp = ((org.postgresql.Connection)myconn).getFastpathAPI();
-</programlisting>
-        where <varname>myconn</> is an open <classname>Connection</> to <productname>PostgreSQL</productname>.
-       </para>
-
-       <formalpara>
-        <title>Returns:</title>
-        <para>
-         Fastpath object allowing access to functions on the
-         <productname>PostgreSQL</productname> backend.
-        </para>
-       </formalpara>
-
-       <formalpara>
-        <title>Throws:</title>
-        <para>
-         SQLException by Fastpath when initializing for first time
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-       <para>
-<synopsis>
-public LargeObjectManager getLargeObjectAPI() throws SQLException
-</synopsis>
-        This returns the Large Object <acronym>API</acronym> for the
-        current connection.
-       </para>
-
-       <para>
-        The best way to use this is as follows:
-<programlisting>
-import org.postgresql.largeobject.*;
-...
-LargeObjectManager lo = ((org.postgresql.Connection)myconn).getLargeObjectAPI();
-</programlisting>
-        where <varname>myconn</> is an open <classname>Connection</> to
-        <productname>PostgreSQL</productname>.
-       </para>
-
-       <formalpara>
-        <title>Returns:</title>
-        <para>
-         <classname>LargeObject</classname> object that implements the <acronym>API</acronym>
-        </para>
-       </formalpara>
-
-       <formalpara>
-        <title>Throws:</title>
-        <para>
-         <classname>SQLException</classname> by <classname>LargeObject</classname> when initializing for first time
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-       <para>
-<synopsis>
-public void addDataType(String type, String name)
-</synopsis>
-        This allows client code to add a handler for one of
-        <productname>PostgreSQL</productname>'s more unique data types. Normally, a data type not
-        known by the driver is returned by <literal>ResultSet.getObject()</literal> as a
-        <classname>PGobject</> instance.  This method allows you to write a class
-        that extends <classname>PGobject</>, and tell the driver the type name, and
-        class name to use. The down side to this, is that you must
-        call this method each time a connection is made.
-       </para>
-
-       <para>
-        The best way to use this is as follows:
-<programlisting>
- ...
-((org.postgresql.Connection)myconn).addDataType("mytype","my.class.name");
- ...
-</programlisting>
-        where <varname>myconn</varname> is an open <classname>Connection</> to
-        <productname>PostgreSQL</productname>.  The handling class must
-        extend <classname>org.postgresql.util.PGobject</classname>.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </sect4>
-   </sect3>
-
-
-   <sect3>
-    <title>Class <classname>org.postgresql.Fastpath</classname></title>
-
-<synopsis>
-public class Fastpath extends Object
-
-java.lang.Object
-   |
-   +----org.postgresql.fastpath.Fastpath
-</synopsis>
-
-    <para>
-     <classname>Fastpath</classname> is an <acronym>API</acronym> that
-     exists within the <application>libpq</application> C interface, and allows a client machine
-     to execute a function on the database backend.  Most client code
-     will not need to use this method, but it is provided because the
-     Large Object <acronym>API</acronym> uses it.
-    </para>
-
-    <para>
-     To use, you need to import the
-     <classname>org.postgresql.fastpath</classname> package, using the
-     line:
-<programlisting>
-import org.postgresql.fastpath.*;
-</programlisting>
-     Then, in your code, you need to get a
-     <classname>FastPath</classname> object:
-<programlisting>
-Fastpath fp = ((org.postgresql.Connection)conn).getFastpathAPI();
-</programlisting>
-     This will return an instance associated with the database
-     connection that you can use to issue commands. The casing of
-     <classname>Connection</classname> to
-     <classname>org.postgresql.Connection</classname> is required, as
-     the <function>getFastpathAPI()</function> is an extension method,
-     not part of <acronym>JDBC</acronym>.  Once you have a
-     <classname>Fastpath</classname> instance, you can use the
-     <function>fastpath()</function> methods to execute a backend
-     function.
-    </para>
-
-    <formalpara>
-     <title>See Also:</title>
-     <para>
-      <classname>FastpathFastpathArg</classname>, <classname>LargeObject</classname>
-     </para>
-    </formalpara>
-
-    <sect4>
-     <title>Methods</title>
-
-     <itemizedlist>
-      <listitem>
-<synopsis>
-public Object fastpath(int fnid,
-                       boolean resulttype,
-                       FastpathArg args[]) throws SQLException
-</synopsis>
-       <para>
-        Send a function call to the <productname>PostgreSQL</productname> backend.
-       </para>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-                <parameter>fnid</> - Function id
-                <parameter>resulttype</> - True if the result is an integer, false 
-for
-                other results
-                <parameter>args</> - <classname>FastpathArguments</classname> to pass to fastpath
-        </para>
-       </formalpara>
-
-       <formalpara>
-        <title>Returns:</title>
-        <para>
-         null if no data, Integer if an integer result, or byte[]
-         otherwise
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public Object fastpath(String name,
-                       boolean resulttype,
-                       FastpathArg args[]) throws SQLException
-</synopsis>
-       <para>
-        Send a function call to the <productname>PostgreSQL</productname> backend by name.
-       </para>
-
-       <note>
-        <para>
-         The mapping for the procedure name to function id needs to
-         exist, usually to an earlier call to <function>addfunction()</function>. This is
-         the preferred method to call, as function id's can/may change
-         between versions of the backend. For an example of how this
-         works, refer to org.postgresql.LargeObject
-        </para>
-       </note>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-                <parameter>name</> - Function name
-                <parameter>resulttype</> - True if the result is an integer, false 
-for
-                other results
-                <parameter>args</> - <classname>FastpathArguments</classname> to pass to fastpath
-        </para>
-       </formalpara>
-
-       <formalpara>
-        <title>Returns:</title>
-        <para>
-         null if no data, Integer if an integer result, or byte[]
-         otherwise
-        </para>
-       </formalpara>
-
-       <formalpara>
-        <title>See Also:</title>
-        <para><classname>LargeObject</classname></para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>          
-public int getInteger(String name,
-                      FastpathArg args[]) throws SQLException
-</synopsis>
-       <para>
-        This convenience method assumes that the return value is an Integer
-       </para>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-                <parameter>name</parameter> - Function name
-                <parameter>args</parameter> - Function arguments
-        </para>
-       </formalpara>
-
-       <formalpara>
-        <title>Returns:</title>
-        <para>integer result</para>
-       </formalpara>
-
-       <formalpara>
-        <title>Throws:</title>
-        <para>
-         <classname>SQLException</classname> if a database-access error occurs or no result
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public byte[] getData(String name,
-                      FastpathArg args[]) throws SQLException
-</synopsis>
-       <para>
-        This convenience method assumes that the return value is binary
-        data.
-       </para>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-                <parameter>name</parameter> - Function name
-                <parameter>args</parameter> - Function arguments
-        </para>
-       </formalpara>
-
-       <formalpara>
-        <title>Returns:</title>
-        <para>byte[] array containing result</para>
-       </formalpara>
-
-       <formalpara>
-        <title>Throws:</title>
-        <para>
-         <classname>SQLException</classname> if a database-access error occurs or no result
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public void addFunction(String name,
-                        int fnid)
-</synopsis>
-       <para>
-        This adds a function to our look-up table.  User code should
-        use the <function>addFunctions</function> method, which is based upon a query,
-        rather than hard coding the oid. The oid for a function is not
-        guaranteed to remain static, even on different servers of the
-        same version.
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public void addFunctions(ResultSet rs) throws SQLException
-</synopsis>
-       <para>
-        This takes a <classname>ResultSet</classname> containing two columns. Column 1
-        contains the function name, Column 2 the oid.  It reads the
-        entire <classname>ResultSet</classname>, loading the values into the function table.
-       </para>
-
-       <important>
-        <para>
-         Remember to <function>close()</function> the
-         <classname>ResultSet</classname> after calling this!
-        </para>
-       </important>
-
-       <note>
-        <title>Implementation note about function name look-ups</title>
-
-        <para>
-         <productname>PostgreSQL</productname> stores the function id's and their corresponding
-         names in the <classname>pg_proc</> table. To speed things up locally,
-         instead of querying each function from that table when
-         required, a <classname>Hashtable</classname> is used. Also, only the function's
-         required are entered into this table, keeping connection
-         times as fast as possible.
-        </para>
-
-        <para>
-         The <classname>org.postgresql.LargeObject</classname> class
-         performs a query upon its start-up, and passes the returned
-         <classname>ResultSet</classname> to the
-         <function>addFunctions()</function> method here.  Once this
-         has been done, the Large Object <acronym>API</acronym> refers
-         to the functions by name.
-        </para>
-
-        <para>
-         Do not think that manually converting them to the OIDs will
-         work. OK, they will for now, but they can change during
-         development (there was some discussion about this for V7.0),
-         so this is implemented to prevent any unwarranted headaches
-         in the future.
-        </para>
-       </note>
-
-       <formalpara>
-        <title>See Also:</title>
-        <para>
-         <classname>LargeObjectManager</classname>
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public int getID(String name) throws SQLException
-</synopsis>
-       <para>
-        This returns the function id associated by its name If
-        <function>addFunction()</function> or <function>addFunctions()</function> have not been called for this
-        name, then an <classname>SQLException</classname> is thrown.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </sect4>
-   </sect3>
-
-
-   <sect3>
-    <title>Class <classname>org.postgresql.fastpath.FastpathArg</classname></title>
-
-<synopsis>
-public class FastpathArg extends Object
-
-java.lang.Object
-   |
-   +----org.postgresql.fastpath.FastpathArg
-</synopsis>
-
-    <para>
-     Each fastpath call requires an array of arguments, the number and
-     type dependent on the function being called.  This class
-     implements methods needed to provide this capability.
-    </para>
-
-    <para>
-     For an example on how to use this, refer to the
-     <classname>org.postgresql.LargeObject</classname> package.
-    </para>
-
-    <formalpara>
-     <title>See Also:</title>
-     <para>
-      <classname>Fastpath</classname>, <classname>LargeObjectManager</classname>, <classname>LargeObject</classname>
-     </para>
-    </formalpara>
-
-    <sect4>
-     <title>Constructors</title>
-
-     <itemizedlist>
-      <listitem>
-<synopsis>
-public FastpathArg(int value)
-</synopsis>
-       <para>
-        Constructs an argument that consists of an integer value
-       </para>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-         value - int value to set
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public FastpathArg(byte bytes[])
-</synopsis>
-       <para>
-        Constructs an argument that consists of an array of bytes
-       </para>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-         bytes - array to store
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public FastpathArg(byte buf[],
-                   int off,
-                   int len)
-</synopsis>
-       <para>
-        Constructs an argument that consists of part of a byte array
-       </para>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-         <variablelist>
-          <varlistentry>
-           <term><parameter>buf</></term>
-           <listitem>
-            <simpara>source array</simpara>
-           </listitem>
-          </varlistentry>
-
-          <varlistentry>
-           <term><parameter>off</parameter></term>
-           <listitem>
-            <simpara>offset within array</simpara>
-           </listitem>
-          </varlistentry>
-
-          <varlistentry>
-           <term><parameter>len</parameter></term>
-           <listitem>
-            <simpara>length of data to include</simpara>
-           </listitem>
-          </varlistentry>
-         </variablelist>
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public FastpathArg(String s)
-</synopsis>
-       <para>
-        Constructs an argument that consists of a String.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </sect4>
-   </sect3>
-  </sect2>
-
-
-  <sect2>
-   <title>Geometric Data Types</title>
-
-   <para>
-    <productname>PostgreSQL</productname> has a set of data types that
-    can store geometric features into a table. These include single
-    points, lines, and polygons.  We support these types in Java with
-    the org.postgresql.geometric package.  It contains classes that
-    extend the org.postgresql.util.PGobject class.  Refer to that
-    class for details on how to implement your own data type handlers.
-   </para>
-
-<programlisting>
-Class org.postgresql.geometric.PGbox
-
-java.lang.Object
-   |
-   +----org.postgresql.util.PGobject
-           |
-           +----org.postgresql.geometric.PGbox
-
-   public class PGbox extends PGobject implements Serializable, 
-Cloneable
-
-   This represents the box data type within <productname>PostgreSQL</productname>.
-
-Variables
-
- public PGpoint point[]
-
-          These are the two corner points of the box.
-
-Constructors
-
- public PGbox(double x1,
-              double y1,
-              double x2,
-              double y2)
-
-        Parameters:
-                x1 - first x coordinate
-                y1 - first y coordinate
-                x2 - second x coordinate
-                y2 - second y coordinate
-
- public PGbox(PGpoint p1,
-              PGpoint p2)
-
-        Parameters:
-                p1 - first point
-                p2 - second point
-
- public PGbox(String s) throws SQLException
-                            
-        Parameters:
-                s - Box definition in <productname>PostgreSQL</productname> syntax
-
-        Throws: SQLException
-                if definition is invalid
-                
- public PGbox()
-
-          Required constructor
-              
-Methods
-
- public void setValue(String value) throws SQLException
-                
-          This method sets the value of this object. It should be 
-overridden, but still called by subclasses.
-                            
-        Parameters:
-                value - a string representation of the value of the 
-object
-        Throws: SQLException
-                thrown if value is invalid for this type
-
-        Overrides:
-                setValue in class PGobject
-
- public boolean equals(Object obj)
-
-        Parameters:
-                obj - Object to compare with
-                
-        Returns:
-                true if the two boxes are identical
-          
-        Overrides:
-                equals in class PGobject
-
- public Object clone()
-        
-          This must be overridden to allow the object to be cloned
-
-        Overrides:
-                clone in class PGobject
-   
- public String getValue()
-        
-        Returns:
-                the PGbox in the syntax expected by <productname>PostgreSQL</productname>
-
-        Overrides:
-                getValue in class PGobject
-
-<!-- **************************************************************** -->
-Class org.postgresql.geometric.PGcircle
-
-java.lang.Object
-   |
-   +----org.postgresql.util.PGobject
-           |
-           +----org.postgresql.geometric.PGcircle
-        
-   public class PGcircle extends PGobject implements Serializable, 
-Cloneable
-               
-   This represents <productname>PostgreSQL</productname>'s circle data type, consisting of a point 
-and a radius
-
-Variables
-
- public PGpoint center
-           
-          This is the center point
- 
- double radius
-           
-          This is the radius
-   
-Constructors   
-
- public PGcircle(double x,
-                 double y,
-                 double r)
-          
-        Parameters:
-               x - coordinate of center
-                y - coordinate of center
-                r - radius of circle
-
- public PGcircle(PGpoint c,
-                 double r)
-          
-        Parameters:
-                c - PGpoint describing the circle's center
-                r - radius of circle
-
- public PGcircle(String s) throws SQLException
-
-        Parameters:
-                s - definition of the circle in <productname>PostgreSQL</productname>'s syntax.
-
-        Throws: SQLException
-                on conversion failure
-
- public PGcircle()
-
-          This constructor is used by the driver.
-            
-Methods   
-
- public void setValue(String s) throws SQLException
-
-        Parameters:
-                s - definition of the circle in <productname>PostgreSQL</productname>'s syntax.
-
-        Throws: SQLException
-                on conversion failure
-
-        Overrides:
-                setValue in class PGobject
-
- public boolean equals(Object obj)
-
-        Parameters:
-                obj - Object to compare with
-            
-        Returns:
-                true if the two circles are identical
-
-        Overrides:
-                equals in class PGobject
-
- public Object clone()
-
-          This must be overridden to allow the object to be cloned
-
-        Overrides:
-                clone in class PGobject
-
- public String getValue()
-
-        Returns:
-                the PGcircle in the syntax expected by <productname>PostgreSQL</productname>
-        
-        Overrides:
-                getValue in class PGobject
-
-<!-- **************************************************************** -->
-Class org.postgresql.geometric.PGline
-
-java.lang.Object
-   |
-   +----org.postgresql.util.PGobject
-           |
-           +----org.postgresql.geometric.PGline
-
-   public class PGline extends PGobject implements Serializable, 
-Cloneable
-
-   This implements a line consisting of two points. Currently line is 
-not yet implemented in the backend, but this class ensures that when 
-it's done were ready for it.
-
-Variables
-   
- public PGpoint point[]
-     
-          These are the two points.
-
-Constructors
-
- public PGline(double x1,
-               double y1,
-               double x2,
-               double y2)
-
-        Parameters:
-                x1 - coordinate for first point
-                y1 - coordinate for first point
-                x2 - coordinate for second point
-                y2 - coordinate for second point
-
- public PGline(PGpoint p1,
-               PGpoint p2)
-     
-        Parameters:
-                p1 - first point
-                p2 - second point
-
- public PGline(String s) throws SQLException
-               
-        Parameters:
-                s - definition of the line in <productname>PostgreSQL</productname>'s syntax.
-
-        Throws: SQLException
-                on conversion failure
-
- public PGline()
-
-          required by the driver
-               
-Methods
-
- public void setValue(String s) throws SQLException
-
-        Parameters:
-                s - Definition of the line segment in <productname>PostgreSQL</productname>'s 
-syntax
-
-        Throws: SQLException
-                on conversion failure
-
-        Overrides:
-                setValue in class PGobject
-                
- public boolean equals(Object obj)
-
-        Parameters:
-                obj - Object to compare with
-               
-        Returns:
-                true if the two lines are identical
-   
-        Overrides:
-                equals in class PGobject
-
- public Object clone()
-        
-          This must be overridden to allow the object to be cloned
-
-        Overrides:
-                clone in class PGobject
-
- public String getValue()
-   
-        Returns:
-                the PGline in the syntax expected by <productname>PostgreSQL</productname>
-        
-        Overrides:
-                getValue in class PGobject
-
-<!-- **************************************************************** -->
-Class org.postgresql.geometric.PGlseg
-             
-java.lang.Object
-   |
-   +----org.postgresql.util.PGobject
-           |
-           +----org.postgresql.geometric.PGlseg
-          
-   public class PGlseg extends PGobject implements Serializable, 
-Cloneable
- 
-   This implements a lseg (line segment) consisting of two points
-
-Variables
-
- public PGpoint point[]
-           
-          These are the two points.
-
-Constructors
-   
- public PGlseg(double x1,
-               double y1,
-               double x2,
-               double y2)
-     
-        Parameters:
-
-                x1 - coordinate for first point
-                y1 - coordinate for first point
-                x2 - coordinate for second point
-                y2 - coordinate for second point
-
- public PGlseg(PGpoint p1,
-               PGpoint p2)
-           
-        Parameters:
-                p1 - first point
-                p2 - second point
-   
- public PGlseg(String s) throws SQLException
-
-        Parameters:
-                s - Definition of the line segment in <productname>PostgreSQL</productname>'s syntax.
-
-        Throws: SQLException
-                on conversion failure
-
- public PGlseg()
-
-          required by the driver
-               
-Methods    
-   
- public void setValue(String s) throws SQLException
-   
-        Parameters:
-                s - Definition of the line segment in <productname>PostgreSQL</productname>'s 
-syntax
-
-        Throws: SQLException
-                on conversion failure
-     
-        Overrides:
-                setValue in class PGobject
-                
- public boolean equals(Object obj)
-
-        Parameters:
-                obj - Object to compare with
-               
-        Returns:
-                true if the two line segments are identical
-   
-        Overrides:
-                equals in class PGobject
-   
- public Object clone()
-
-          This must be overridden to allow the object to be cloned
-
-        Overrides:
-               clone in class PGobject
-
- public String getValue()
-
-        Returns:
-                the PGlseg in the syntax expected by <productname>PostgreSQL</productname>
-        
-        Overrides:
-                getValue in class PGobject
-
-<!-- **************************************************************** -->
-Class org.postgresql.geometric.PGpath
-                                
-java.lang.Object
-   |
-   +----org.postgresql.util.PGobject
-           |
-           +----org.postgresql.geometric.PGpath
-          
-   public class PGpath extends PGobject implements Serializable, 
-Cloneable
-               
-   This implements a path (a multiply segmented line, which may be 
-closed)
-           
-Variables
-
- public boolean open
-               
-          True if the path is open, false if closed
-
- public PGpoint points[]
-
-          The points defining this path
-
-Constructors   
-
- public PGpath(PGpoint points[],
-               boolean open)
-          
-        Parameters:
-                points - the PGpoints that define the path
-                open - True if the path is open, false if closed
-
- public PGpath()
-
-          Required by the driver
-
- public PGpath(String s) throws SQLException
-
-        Parameters:
-                s - definition of the path in <productname>PostgreSQL</productname>'s syntax.
-
-        Throws: SQLException
-                on conversion failure
-
-Methods
-
- public void setValue(String s) throws SQLException
-   
-        Parameters:
-                s - Definition of the path in <productname>PostgreSQL</productname>'s syntax
-           
-        Throws: SQLException
-                on conversion failure
-
-        Overrides:
-                setValue in class PGobject
-
- public boolean equals(Object obj)
-
-        Parameters:
-                obj - Object to compare with
-
-        Returns:
-                true if the two pathes are identical
-
-        Overrides:
-                equals in class PGobject
-
- public Object clone()
-
-          This must be overridden to allow the object to be cloned
-
-        Overrides:
-                clone in class PGobject
-
- public String getValue()
-
-          This returns the path in the syntax expected by 
-<productname>PostgreSQL</productname>
-
-        Overrides:
-                getValue in class PGobject
-
- public boolean isOpen()
-
-     This returns true if the path is open
-
- public boolean isClosed()
-
-     This returns true if the path is closed
-
- public void closePath()
-
-     Marks the path as closed
-
- public void openPath()
-
-     Marks the path as open
-
-<!-- **************************************************************** -->
-Class org.postgresql.geometric.PGpoint
-                                
-java.lang.Object
-   |
-   +----org.postgresql.util.PGobject
-           |
-           +----org.postgresql.geometric.PGpoint
-          
-   public class PGpoint extends PGobject implements Serializable, 
-Cloneable
-
-   This implements a version of java.awt.Point, except it uses double 
-to represent the coordinates.
-
-   It maps to the point data type in <productname>PostgreSQL</productname>.
-
-Variables
-
- public double x
-
-          The X coordinate of the point
-
- public double y
-
-          The Y coordinate of the point
-
-Constructors
-
- public PGpoint(double x,
-                double y)
-
-        Parameters:
-                x - coordinate
-                y - coordinate
-
- public PGpoint(String value) throws SQLException
-     
-          This is called mainly from the other geometric types, when a 
-point is embedded within their definition.
-             
-        Parameters:
-                value - Definition of this point in <productname>PostgreSQL</productname>'s 
-syntax
-   
- public PGpoint()
-          
-          Required by the driver
-
-Methods
-
- public void setValue(String s) throws SQLException
-
-        Parameters:
-                s - Definition of this point in <productname>PostgreSQL</productname>'s syntax
-
-        Throws: SQLException
-                on conversion failure
-
-        Overrides:
-                setValue in class PGobject
-          
- public boolean equals(Object obj)
-
-        Parameters:
-                obj - Object to compare with
-
-        Returns:
-                true if the two points are identical
-
-        Overrides:
-                equals in class PGobject
-
- public Object clone()
-                
-          This must be overridden to allow the object to be cloned
-
-        Overrides:
-                clone in class PGobject
-          
- public String getValue()       
-    
-        Returns:
-                the PGpoint in the syntax expected by <productname>PostgreSQL</productname>
-
-        Overrides:
-                getValue in class PGobject
-          
- public void translate(int x,
-                       int y)
-
-          Translate the point with the supplied amount.
-
-        Parameters:
-                x - integer amount to add on the x axis
-                y - integer amount to add on the y axis
-
- public void translate(double x,
-                       double y)
-          
-          Translate the point with the supplied amount.
- 
-        Parameters:
-                x - double amount to add on the x axis
-                y - double amount to add on the y axis
-
- public void move(int x,
-                  int y)
-                
-          Moves the point to the supplied coordinates.
-
-        Parameters:
-                x - integer coordinate
-                y - integer coordinate
-
-public void move(double x,
-                  double y)
-          
-          Moves the point to the supplied coordinates.
-
-        Parameters:
-                x - double coordinate
-                y - double coordinate
-
- public void setLocation(int x,
-                         int y)
-
-          Moves the point to the supplied coordinates. refer to
-          java.awt.Point for description of this
-
-        Parameters:
-                x - integer coordinate
-                y - integer coordinate
-
-        See Also:
-                Point
-
- public void setLocation(Point p)
-
-          Moves the point to the supplied java.awt.Point refer to
-          java.awt.Point for description of this
-
-        Parameters:
-                p - Point to move to
-
-        See Also:
-                Point
-
-<!-- **************************************************************** -->
-Class org.postgresql.geometric.PGpolygon
-                                
-java.lang.Object
-   |
-   +----org.postgresql.util.PGobject
-           |
-           +----org.postgresql.geometric.PGpolygon
-
-   public class PGpolygon extends PGobject implements Serializable, 
-Cloneable
-               
-   This implements the polygon data type within <productname>PostgreSQL</productname>.
-
-Variables
-
- public PGpoint points[]
-
-          The points defining the polygon
-                                
-Constructors
-
- public PGpolygon(PGpoint points[])
-
-          Creates a polygon using an array of PGpoints
-
-        Parameters:
-                points - the points defining the polygon
-
- public PGpolygon(String s) throws SQLException
-                 
-        Parameters:
-                s - definition of the polygon in <productname>PostgreSQL</productname>'s syntax.
-
-        Throws: SQLException
-                on conversion failure
-
- public PGpolygon()
-
-          Required by the driver
-
-Methods
-
- public void setValue(String s) throws SQLException
-
-        Parameters:
-                s - Definition of the polygon in <productname>PostgreSQL</productname>'s syntax
-
-        Throws: SQLException
-                on conversion failure
-
-        Overrides:
-                setValue in class PGobject
-
- public boolean equals(Object obj)
-     
-        Parameters:
-                obj - Object to compare with
-                                
-        Returns:
-                true if the two polygons are identical
-
-        Overrides:
-                equals in class PGobject
-
- public Object clone()
-        
-          This must be overridden to allow the object to be cloned
-
-        Overrides:
-                clone in class PGobject
-                 
- public String getValue()
-
-        Returns:
-                the PGpolygon in the syntax expected by <productname>PostgreSQL</productname>
-
-        Overrides:
-                getValue in class PGobject
-</programlisting>
-  </sect2>
-
-
-  <sect2>
-   <title>Large Objects</title>
-
-   <para>
-    Large objects are supported in the standard
-    <acronym>JDBC</acronym> specification.  However, that interface is
-    limited, and the <acronym>API</acronym> provided by <productname>PostgreSQL</productname> allows for random
-    access to the objects contents, as if it was a local file.
-   </para>
-
-   <para>
-    The org.postgresql.largeobject package provides to Java the <application>libpq</application>
-    C interface's large object <acronym>API</acronym>. It consists of
-    two classes, <classname>LargeObjectManager</classname>, which deals with creating,
-    opening and deleting large objects, and <classname>LargeObject</classname> which deals
-    with an individual object.
-   </para>
-
-   <sect3>
-    <title>Class <classname>org.postgresql.largeobject.LargeObject</classname></title>
-
-<synopsis>
-public class LargeObject extends Object
-
-java.lang.Object
-   |
-   +----org.postgresql.largeobject.LargeObject
-</synopsis>
-
-    <para>
-     This class implements the large object interface to
-     <productname>PostgreSQL</productname>.
-    </para>
-
-    <para>
-     It provides the basic methods required to run the interface, plus
-     a pair of methods that provide <classname>InputStream</classname> and <classname>OutputStream</classname>
-     classes for this object.
-    </para>
-
-    <para>
-     Normally, client code would use the methods in 
-     <classname>BLOB</classname> to access large objects.
-    </para>
-
-    <para>
-     However, sometimes lower level access to Large Objects is
-     required, that is not supported by the <acronym>JDBC</acronym>
-     specification.
-    </para>
-
-    <para>
-     Refer to org.postgresql.largeobject.LargeObjectManager on how to
-     gain access to a Large Object, or how to create one.
-    </para>
-
-    <formalpara>
-     <title>See Also:</title>
-     <para><classname>LargeObjectManager</classname></para>
-    </formalpara>
-
-    <sect4>
-     <title>Variables</title>
-
-     <variablelist>
-      <varlistentry>
-       <term>public static final int SEEK_SET</term>
-       <listitem>
-        <para>Indicates a seek from the beginning of a file</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>public static final int SEEK_CUR</term>
-       <listitem>
-        <para>Indicates a seek from the current position</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>public static final int SEEK_END</term>
-       <listitem>
-        <para>Indicates a seek from the end of a file</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </sect4>
-
-    <sect4>
-     <title>Methods</title>
-
-     <itemizedlist>
-      <listitem>
-<synopsis>
-public int getOID()
-</synopsis>
-       <para>
-        Returns the OID of this <classname>LargeObject</classname>
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public void close() throws SQLException
-</synopsis>
-       <para>
-        This method closes the object. You must not call methods in
-        this object after this is called.
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public byte[] read(int len) throws SQLException
-</synopsis>
-       <para>
-        Reads some data from the object, and return as a byte[] array
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public int read(byte buf[],
-                 int off,
-                 int len) throws SQLException
-</synopsis>
-       <para>
-        Reads some data from the object into an existing array
-       </para>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-         <variablelist>
-          <varlistentry>
-           <term>buf</term>
-           <listitem>
-            <simpara>destination array</simpara>
-           </listitem>
-          </varlistentry>
-
-          <varlistentry>
-           <term>off</term>
-           <listitem>
-            <simpara>offset within array</simpara>
-           </listitem>
-          </varlistentry>
-
-          <varlistentry>
-           <term>len</term>
-           <listitem>
-            <simpara>number of bytes to read</simpara>
-           </listitem>
-          </varlistentry>
-         </variablelist>
-        </para>
-       </formalpara>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public void write(byte buf[]) throws SQLException
-</synopsis>
-       <para>
-        Writes an array to the object
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public void write(byte buf[],
-                  int off,
-                  int len) throws SQLException
-</synopsis>
-       <para>
-        Writes some data from an array to the object
-       </para>
-
-       <formalpara>
-        <title>Parameters:</title>
-        <para>
-         <variablelist>
-          <varlistentry>
-           <term>buf</term>
-           <listitem>
-            <simpara>destination array</simpara>
-           </listitem>
-          </varlistentry>
-
-          <varlistentry>
-           <term>off</term>
-           <listitem>
-            <simpara>offset within array</simpara>
-           </listitem>
-          </varlistentry>
-
-          <varlistentry>
-           <term>len</term>
-           <listitem>
-            <simpara>number of bytes to write</simpara>
-           </listitem>
-          </varlistentry>
-         </variablelist>
-        </para>
-       </formalpara>
-      </listitem>
-
-<!--
- public void seek(int pos,
-                  int ref) throws SQLException
-
-          Sets the current position within the object.
-
-          This is similar to the fseek() call in the standard C 
-library.It allows you to have random access to the large object.
-
-        Parameters:
-                pos - position within object
-                ref - Either SEEK_SET, SEEK_CUR or SEEK_END
-        Throws: SQLException
-                if a database-access error occurs.
-
- public void seek(int pos) throws SQLException
-
-          Sets the current position within the object.
-
-          This is similar to the fseek() call in the standard C 
-library.It allows you to have random access to the large object.
-
-        Parameters:
-                pos - position within object from begining
-
-        Throws: SQLException
-                if a database-access error occurs.
-
- public int tell() throws SQLException
-
-        Returns:
-                the current position within the object
-
-        Throws: SQLException
-                if a database-access error occurs.
-
- public int size() throws SQLException
-
-          This method is inefficient, as the only way to find out the 
-size of the object is to seek to the end, record the current position, 
-then return to the original position.
-
-          A better method will be found in the future.
-
-        Returns:
-                the size of the large object
-
-        Throws: SQLException
-                if a database-access error occurs.
-
- public InputStream getInputStream() throws SQLException
-
-          Returns an InputStream from this object.
-
-          This InputStream can then be used in any method that 
-requires an InputStream.
-
-        Throws: SQLException
-                if a database-access error occurs.
-
- public OutputStream getOutputStream() throws SQLException
-
-          Returns an OutputStream to this object
-
-          This OutputStream can then be used in any method that 
-requires an OutputStream.
-
-        Throws: SQLException
-                if a database-access error occurs.
--->
-     </itemizedlist>
-    </sect4>
-   </sect3>
-
-
-   <sect3>
-    <title>Class <classname>org.postgresql.largeobject.LargeObjectManager</classname></title>
-
-<synopsis>                                
-public class LargeObjectManager extends Object
-
-java.lang.Object
-   |
-   +----org.postgresql.largeobject.LargeObjectManager
-</synopsis>
-
-    <para>
-     This class implements the large object interface to
-     <productname>PostgreSQL</productname>.  It provides methods that
-     allow client code to create, open and delete large objects from
-     the database. When opening an object, an instance of
-     <classname>org.postgresql.largeobject.LargeObject</classname> is
-     returned, and its methods then allow access to the object.
-    </para>
-
-    <para>
-     This class can only be created by org.postgresql.Connection.  To
-     get access to this class, use the following segment of code:
-<programlisting>
-import org.postgresql.largeobject.*;
-Connection  conn;
-LargeObjectManager lobj;
-// ... code that opens a connection ...
-lobj = ((org.postgresql.Connection)myconn).getLargeObjectAPI();
-</programlisting>
-    </para>
-
-    <para>
-     Normally, client code would use the <classname>BLOB</classname>
-     methods to access large objects.  However, sometimes
-     lower level access to Large Objects is required, that is not
-     supported by the <acronym>JDBC</acronym> specification.
-    </para>
-
-    <para>
-     Refer to org.postgresql.largeobject.LargeObject on how to
-     manipulate the contents of a Large Object.
-    </para>
-
-    <sect4>
-     <title>Variables</title>
-
-     <variablelist>
-      <varlistentry>
-       <term>public static final int WRITE</term>
-       <listitem>
-        <simpara>This mode indicates we want to write to an object.</simpara>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>public static final int READ</term>
-       <listitem>
-        <simpara>This mode indicates we want to read an object.</simpara>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>public static final int READWRITE</term>
-       <listitem>
-        <simpara>This mode is the default. It indicates we want read and write access to a large object.</simpara>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </sect4>
-
-    <sect4>
-     <title>Methods</title>
-
-     <itemizedlist>
-      <listitem>
-<synopsis>
-public LargeObject open(int oid) throws SQLException
-</synopsis>
-       <para>
-        This opens an existing large object, based on its OID. This
-        method assumes that READ and WRITE access is required (the
-        default).
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public LargeObject open(int oid,
-                        int mode) throws SQLException
-</synopsis>
-       <para>
-        This opens an existing large object, based on its OID, and
-        allows setting the access mode.
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public int create() throws SQLException
-</synopsis>
-       <para>
-        This creates a large object, returning its OID.
-        It defaults to READWRITE for the new object's attributes.
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public int create(int mode) throws SQLException
-</synopsis>
-       <para>
-        This creates a large object, returning its OID, and sets the
-        access mode.
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public void delete(int oid) throws SQLException
-</synopsis>
-       <para>          
-        This deletes a large object.
-       </para>
-      </listitem>
-
-      <listitem>
-<synopsis>
-public void unlink(int oid) throws SQLException
-</synopsis>
-       <para>
-        This deletes a large object.  It is identical to the delete
-        method, and is supplied as the C <acronym>API</acronym> uses
-        <quote>unlink</quote>.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </sect4>
-   </sect3>
-  </sect2>
-
- </sect1>
-
-
- <sect1 id="jdbc-thread">
-  <title>Using the driver in a multithreaded or a servlet environment</title>
-
-  <para>
-   A problem with many <acronym>JDBC</acronym> drivers is that only
-   one thread can use a <classname>Connection</classname> at any one
-   time -- otherwise a thread could send a query while another one is
-   receiving results, and this would be a bad thing for the database
-   engine.
-  </para>
-
-  <para>
-   The <productname>PostgreSQL</productname> <acronym>JDBC</acronym> Driver
-   is thread safe.
-   Consequently, if your application uses multiple threads then you do
-   not have to worry about complex algorithms to ensure that only one
-   uses the database at any time.
-  </para>
-
-  <para>
-   If a thread attempts to use the connection while another one is
-   using it, it will wait until the other thread has finished its
-   current operation.  If it is a regular <acronym>SQL</acronym>
-   statement, then the operation consists of sending the statement and
-   retrieving any <classname>ResultSet</classname> (in full).  If it
-   is a <classname>Fastpath</classname> call (e.g., reading a block
-   from a <classname>LargeObject</classname>) then it is the time to
-   send and retrieve that block.
-  </para>
-
-  <para>
-   This is fine for applications and applets but can cause a
-   performance problem with servlets.  With servlets you can have a
-   heavy load on the connection. If you have several threads
-   performing queries then each but one will pause, which may not be what
-   you are after.
-  </para>
-
-  <para>
-   To solve this, you would be advised to create a pool of
-   connections.  When ever a thread needs to use the database, it asks
-   a manager class for a <classname>Connection</classname>. The
-   manager hands a free connection to the thread and marks it as
-   busy. If a free connection is not available, it opens one.  Once
-   the thread has finished with it, it returns it to the manager who
-   can then either close it or add it to the pool. The manager would
-   also check that the connection is still alive and remove it from
-   the pool if it is dead.
-  </para>
-
-  <para>
-   So, with servlets, it is up to you to use either a single
-   connection, or a pool. The plus side for a pool is that threads
-   will not be hit by the bottle neck caused by a single network
-   connection. The down side is that it increases the load on the
-   server, as a backend process is created for each
-   <classname>Connection</classname>.  It is up to you and your
-   applications requirements.
-  </para>
- </sect1>
-
-
- <sect1 id="jdbc-reading">
-  <title>Further Reading</title>
-
-  <para>
-   If you have not yet read it, I'd advise you read the
-   <acronym>JDBC</acronym> <acronym>API</acronym> Documentation
-   (supplied with Sun's <acronym>JDK</acronym>), and the
-   <acronym>JDBC</acronym> Specification.  Both are available from
-   <ulink
-   url="http://java.sun.com/products/jdbc/index.html">http://java.sun.com/products/jdbc/index.html</ulink>.
-  </para>
-
-  <para>
-   <ulink
-   url="http://jdbc.postgresql.org">http://jdbc.postgresql.org</ulink>
-   contains updated information not included in this document, and
-   also includes precompiled drivers.
-  </para>
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/keywords.sgml b/doc/src/sgml/keywords.sgml
deleted file mode 100644
index 4c1a1740258..00000000000
--- a/doc/src/sgml/keywords.sgml
+++ /dev/null
@@ -1,3202 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/keywords.sgml,v 2.6 2002/06/20 16:00:43 momjian Exp $ -->
-
-<appendix id="sql-keywords-appendix">
- <title><acronym>SQL</acronym> Key Words</title>
-
- <indexterm zone="sql-keywords-appendix">
-  <primary>key words</primary>
-  <secondary>list of</secondary>
- </indexterm>
-
- <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 in most or all contexts where an
-  identifier is expected.  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 only allowed as
-  <quote>AS</quote> column label names (and perhaps in very few other
-  contexts).  Some reserved key words are allowable as names for
-  functions; this is also shown in the table.
- </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 <peter_e@gmx.net>
- about remaking it.
--->
-
-<table id="keywords-table">
- <title><acronym>SQL</acronym> Key Words</title>
-
- <tgroup cols="4">
-  <thead>
-   <row>
-    <entry>Key Word</entry>
-    <entry><productname>PostgreSQL</productname></entry>
-    <entry><acronym>SQL</acronym> 99</entry>
-    <entry><acronym>SQL</acronym> 92</entry>
-   </row>
-  </thead>
-
-  <tbody>
-   <row>
-    <entry><token>ABORT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ABS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ABSOLUTE</token></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>
-   </row>
-   <row>
-    <entry><token>ACTION</token></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>
-   </row>
-   <row>
-    <entry><token>ADD</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ADMIN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AFTER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AGGREGATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ALIAS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ALL</token></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>
-   </row>
-   <row>
-    <entry><token>ALTER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ANALYSE</token></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ANALYZE</token></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AND</token></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>
-   </row>
-   <row>
-    <entry><token>ARE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ARRAY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AS</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ASC</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ASENSITIVE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ASSERTION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ASSIGNMENT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ASYMMETRIC</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ATOMIC</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>AUTHORIZATION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>AVG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BACKWARD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BEFORE</token></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>
-   </row>
-   <row>
-    <entry><token>BETWEEN</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BINARY</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BIT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BITVAR</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BIT_LENGTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BLOB</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BOOLEAN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BOTH</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>BREADTH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>BY</token></entry>
-    <entry>non-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>
-   </row>
-   <row>
-    <entry><token>CACHE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CALL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CALLED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CARDINALITY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CASCADE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CASCADED</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CASE</token></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>
-   </row>
-   <row>
-    <entry><token>CATALOG</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>CHAIN</token></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>
-   </row>
-   <row>
-    <entry><token>CHARACTER</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHARACTERISTICS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CHARACTER_LENGTH</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>CHARACTER_SET_NAME</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>CHAR_LENGTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHECK</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CHECKED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CHECKPOINT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CLASS</token></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>
-   </row>
-   <row>
-    <entry><token>CLOB</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CLOSE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CLUSTER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COALESCE</token></entry>
-    <entry>non-reserved (cannot be function or type)</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>
-   </row>
-   <row>
-    <entry><token>COLLATE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLLATION</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>COLLATION_NAME</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>COLUMN</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COLUMN_NAME</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>COMMAND_FUNCTION_CODE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COMMENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>COMMIT</token></entry>
-    <entry>non-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>
-   </row>
-   <row>
-    <entry><token>COMPLETION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONDITION_NUMBER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONNECT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONNECTION</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>CONSTRAINT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONSTRAINTS</token></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>
-   </row>
-   <row>
-    <entry><token>CONSTRAINT_NAME</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>CONSTRUCTOR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONTAINS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CONTINUE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CONVERT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COPY</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CORRESPONDING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>COUNT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CREATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CREATEDB</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CREATEUSER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CROSS</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CUBE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_DATE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_PATH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_ROLE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>CURRENT_TIME</token></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>
-   </row>
-   <row>
-    <entry><token>CURRENT_USER</token></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>
-   </row>
-   <row>
-    <entry><token>CURSOR_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>CYCLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DATA</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>DATABASE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DATE</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>DATETIME_INTERVAL_PRECISION</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>DEALLOCATE</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>DECIMAL</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DECLARE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DEFAULT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DEFERRABLE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DEFERRED</token></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></entry>
-   </row>
-   <row>
-    <entry><token>DEFINER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DELETE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DELIMITER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DELIMITERS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DEPTH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DEREF</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DESC</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DESCRIBE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DESCRIPTOR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DESTROY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DESTRUCTOR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DETERMINISTIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DIAGNOSTICS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DICTIONARY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DISCONNECT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DISPATCH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DISTINCT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DO</token></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DOMAIN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>DOUBLE</token></entry>
-    <entry>non-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>
-   </row>
-   <row>
-    <entry><token>DYNAMIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>DYNAMIC_FUNCTION</token></entry>
-    <entry></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></entry>
-   </row>
-   <row>
-    <entry><token>EACH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ELSE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ENCODING</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ENCRYPTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>END</token></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>
-   </row>
-   <row>
-    <entry><token>EQUALS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ESCAPE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EVERY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXCEPT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXCEPTION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXCLUSIVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXEC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXECUTE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXISTING</token></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>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXPLAIN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>EXTERNAL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>EXTRACT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FALSE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FETCH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FINAL</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FIRST</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FLOAT</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FOR</token></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>
-   </row>
-   <row>
-    <entry><token>FOREIGN</token></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>
-   </row>
-   <row>
-    <entry><token>FORWARD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FOUND</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FREE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FREEZE</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>FROM</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FULL</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>FUNCTION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>G</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GENERAL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GENERATED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GET</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GLOBAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GO</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GOTO</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GRANT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GRANTED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>GROUP</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>GROUPING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HANDLER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HAVING</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>HIERARCHY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HOLD</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>HOST</token></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>
-   </row>
-   <row>
-    <entry><token>IDENTITY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>IGNORE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ILIKE</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IMMEDIATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>IMPLEMENTATION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IN</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INCREMENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INDEX</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INDICATOR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INFIX</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INHERITS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INITIALIZE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INITIALLY</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INNER</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INOUT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INPUT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INSENSITIVE</token></entry>
-    <entry>non-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>
-   </row>
-   <row>
-    <entry><token>INSTANCE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INSTANTIABLE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INSTEAD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>INT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INTEGER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INTERSECT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INTERVAL</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INTO</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>INVOKER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>IS</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ISNULL</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ISOLATION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ITERATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>JOIN</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>K</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>KEY</token></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></entry>
-   </row>
-   <row>
-    <entry><token>KEY_TYPE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LANCOMPILER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LANGUAGE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LARGE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LAST</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LATERAL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LEADING</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LEFT</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LENGTH</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>LESS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LEVEL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LIKE</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LIMIT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LISTEN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOAD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>LOCALTIME</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCALTIMESTAMP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCATION</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCATOR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOCK</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>LOWER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>M</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MAP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MATCH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>MAX</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>MAXVALUE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MESSAGE_LENGTH</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>MESSAGE_TEXT</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>METHOD</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MIN</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>MINVALUE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MOD</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MODE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MODIFIES</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MODIFY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MODULE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>MONTH</token></entry>
-    <entry>non-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>
-   </row>
-   <row>
-    <entry><token>MOVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>MUMPS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>NAMES</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NATIONAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NATURAL</token></entry>
-    <entry>reserved (can be function)</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>
-   </row>
-   <row>
-    <entry><token>NCLOB</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NEW</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NEXT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NO</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NOCREATEDB</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NOCREATEUSER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NONE</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NOT</token></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>
-   </row>
-   <row>
-    <entry><token>NOTIFY</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NOTNULL</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>NULL</token></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>
-   </row>
-   <row>
-    <entry><token>NULLIF</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>NUMBER</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>OBJECT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OCTET_LENGTH</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>OFF</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OFFSET</token></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OIDS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OLD</token></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>
-   </row>
-   <row>
-    <entry><token>ONLY</token></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>
-   </row>
-   <row>
-    <entry><token>OPERATION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OPERATOR</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OPTION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OPTIONS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OR</token></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>
-   </row>
-   <row>
-    <entry><token>ORDINALITY</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OUT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OUTER</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OUTPUT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OVERLAPS</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>OVERLAY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OVERRIDING</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>OWNER</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PAD</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETERS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_MODE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_ORDINAL_POSITION</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_SPECIFIC_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_SPECIFIC_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARAMETER_SPECIFIC_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PARTIAL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PASCAL</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>PASSWORD</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PATH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PENDANT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PLI</token></entry>
-    <entry></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>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>POSTFIX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PRECISION</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PREFIX</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PREORDER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>PREPARE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PRESERVE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PRIMARY</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PRIOR</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PRIVILEGES</token></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>
-   </row>
-   <row>
-    <entry><token>PROCEDURE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>PUBLIC</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>READ</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>READS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REAL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>RECURSIVE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REF</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REFERENCES</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>REFERENCING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REINDEX</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RELATIVE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>RENAME</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REPEATABLE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>REPLACE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RESET</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RESTRICT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>RESULT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RETURN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>RETURNED_LENGTH</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>RETURNED_SQLSTATE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>RETURNS</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>REVOKE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>RIGHT</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ROLE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROLLBACK</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ROLLUP</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROUTINE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROUTINE_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROUTINE_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROUTINE_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROW</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>ROWS</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>RULE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SAVEPOINT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SCALE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>SCHEMA</token></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>
-   </row>
-   <row>
-    <entry><token>SCOPE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SCROLL</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SEARCH</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SECOND</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SECTION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SECURITY</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SELECT</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SELF</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SENSITIVE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SEQUENCE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SERIALIZABLE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>SERVER_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>SESSION</token></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>
-   </row>
-   <row>
-    <entry><token>SET</token></entry>
-    <entry>non-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>
-   </row>
-   <row>
-    <entry><token>SETS</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SHARE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SHOW</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SIMILAR</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SIMPLE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SIZE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SMALLINT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SOME</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SOURCE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SPACE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SPECIFIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SPECIFICTYPE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SPECIFIC_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SQL</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SQLCODE</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SQLERROR</token></entry>
-    <entry></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SQLEXCEPTION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SQLSTATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SQLWARNING</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>START</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STATEMENT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STATIC</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STATISTICS</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STDIN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STDOUT</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STRUCTURE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>STYLE</token></entry>
-    <entry></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>
-   </row>
-   <row>
-    <entry><token>SUBLIST</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SUBSTRING</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SUM</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>SYMMETRIC</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SYSID</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SYSTEM</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>SYSTEM_USER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TABLE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TABLE_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>TEMP</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TEMPLATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TEMPORARY</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TERMINATE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>THAN</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>THEN</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TIME</token></entry>
-    <entry>non-reserved (cannot be function or type)</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>
-   </row>
-   <row>
-    <entry><token>TIMEZONE_HOUR</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TIMEZONE_MINUTE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TO</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TOAST</token></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>
-   </row>
-   <row>
-    <entry><token>TRANSACTION</token></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></entry>
-   </row>
-   <row>
-    <entry><token>TRANSACTIONS_ROLLED_BACK</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSACTION_ACTIVE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSFORM</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSFORMS</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRANSLATE</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TRANSLATION</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TREAT</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIGGER</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIGGER_CATALOG</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIGGER_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIGGER_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRIM</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TRUE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>TRUNCATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TRUSTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>TYPE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNCOMMITTED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNDER</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNENCRYPTED</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNION</token></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>
-   </row>
-   <row>
-    <entry><token>UNKNOWN</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNLISTEN</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNNAMED</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>non-reserved</entry>
-   </row>
-   <row>
-    <entry><token>UNNEST</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UNTIL</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>UPDATE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>UPPER</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>USAGE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>USER</token></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></entry>
-   </row>
-   <row>
-    <entry><token>USER_DEFINED_TYPE_NAME</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>USER_DEFINED_TYPE_SCHEMA</token></entry>
-    <entry></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>USING</token></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>
-   </row>
-   <row>
-    <entry><token>VALID</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VALUE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VALUES</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VARCHAR</token></entry>
-    <entry>non-reserved (cannot be function or type)</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VARIABLE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VARYING</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>VERBOSE</token></entry>
-    <entry>reserved (can be function)</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VERSION</token></entry>
-    <entry>non-reserved</entry>
-    <entry></entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>VIEW</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WHEN</token></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>
-   </row>
-   <row>
-    <entry><token>WHERE</token></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WITH</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WITHOUT</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry></entry>
-   </row>
-   <row>
-    <entry><token>WORK</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>WRITE</token></entry>
-    <entry></entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>YEAR</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-   <row>
-    <entry><token>ZONE</token></entry>
-    <entry>non-reserved</entry>
-    <entry>reserved</entry>
-    <entry>reserved</entry>
-   </row>
-  </tbody>
- </tgroup>
-</table>
-
-
-</appendix>
diff --git a/doc/src/sgml/legal.sgml b/doc/src/sgml/legal.sgml
deleted file mode 100644
index 2bba7a6e78b..00000000000
--- a/doc/src/sgml/legal.sgml
+++ /dev/null
@@ -1,105 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/legal.sgml,v 1.14 2002/06/20 20:29:24 momjian Exp $
--->
-
-<copyright>
- <year>1996-2002</year>
- <holder>The PostgreSQL Global Development Group</holder>
-</copyright>
-
-<legalnotice>
- <title>Legal Notice</title>
-
- <para>
-  <productname>PostgreSQL</productname> is Copyright &copy; 1996-2002
-  by the PostgreSQL Global Development Group and is distributed under
-  the terms of the license of the University of California below.
- </para>
-
- <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.
- </para>
-
-<!--
-How to keep track of all the trademarks? I'll try the strategy used at
-www.qnx.com - thomas
---
-
---
-There is no legal requirement to make trademark acknowledgements in
-references to third party products that happen to have trademarked
-names.
-
-The exception would be if <productname>PostgreSQL</>
- were to license a particular
-trademark and the trademark holder makes this requirement (as in the
-case of UNIX and Java).
-
-What is not allowed, however, is to use a trademark name in a way that
-could lead people to believe that they label <productname>PostgreSQL</> products.
-E.g., "the <productname>PostgreSQL</> UNIX database system" would probably be illegal,
-whereas "<productname>PostgreSQL</>, which runs on many UNIX computer systems" is
-fine.  This is independent of whether a trademark acknowledgement is
-made.
-
-- petere
-
- <para>
-  <acronym>Unix</acronym> is a trademark of X/Open, Ltd.  Sun4,  SPARC,  SunOS
-  and  Solaris  are trademarks of Sun Microsystems, Inc.  DEC,
-  DECstation, Alpha AXP and ULTRIX are trademarks  of Compaq, formerly Digital
-  Equipment   Corp.   PA-RISC  and  HP-UX  are  trademarks  of
-  Hewlett-Packard Co.  OSF/1 is a trademark of the Open  
-  Software Foundation.
- </para>
--->
-
-<!--
- <para>
-  All trademarks are the property of their respective owners.
- </para>
--->
-</legalnotice>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/libpgeasy.sgml b/doc/src/sgml/libpgeasy.sgml
deleted file mode 100644
index 4bb1b7949bd..00000000000
--- a/doc/src/sgml/libpgeasy.sgml
+++ /dev/null
@@ -1,152 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpgeasy.sgml,v 2.9 2002/03/04 18:50:20 momjian Exp $
--->
-
- <chapter id="pgeasy">
-  <title><application>libpgeasy</application> - Simplified C Library</title>
-
-  <note>
-   <title>Author</title>
-
-   <para>
-    Written by Bruce Momjian
-    (<email>pgman@candle.pha.pa.us</email>)
-    and last updated 2002-03-04
-   </para>
-  </note>
-
-  <para>
-   <application>pgeasy</application> allows you to cleanly interface
-   to the <application>libpq</application> library, more like a 4GL
-   SQL interface.  Refer to <xref linkend="libpq"> for more
-   information about <application>libpq</application>.
-  </para>
-
-  <para>
-   It consists of a set of simplified C functions that encapsulate the
-   functionality of <application>libpq</application>. The functions are:
-
-   <itemizedlist>
-    <listitem>
-<synopsis>
-PGresult   *doquery(char *query);
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-PGconn     *connectdb(char *options);
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-void        disconnectdb();
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-int         fetch(void *param,...);
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-int         fetchwithnulls(void *param,...);
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-void        reset_fetch();
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-void        on_error_continue();
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-void        on_error_stop();
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-PGresult   *get_result();
-</synopsis>
-    </listitem>
-
-    <listitem>
-<synopsis>
-void        set_result(PGresult *newres);
-</synopsis>
-    </listitem>
-
-   </itemizedlist>
-  </para>
-
-  <para>
-   Many functions return a structure or value, so you can work
-   with the result if required.
-  </para>
-
-  <para>
-   You basically connect to the database with
-   <function>connectdb</function>, issue your query with
-   <function>doquery</function>, fetch the results with
-   <function>fetch</function>, and finish with
-   <function>disconnectdb</function>.
-  </para>
-
-  <para>
-   For <literal>SELECT</literal> queries, <function>fetch</function>
-   allows you to pass pointers as parameters, and on return the
-   variables are filled with data from the binary cursor you opened.
-   These binary cursors cannot be used if you are running the
-   <application>pgeasy</application> client on a system with a different
-   architecture than the database server. If you pass a NULL pointer
-   parameter, the column is skipped. <function>fetchwithnulls</function>
-   allows you to retrieve the NULL status of the field by passing an
-   <literal>int*</literal> after each result pointer, which returns true
-   or false to indicate if the field is null. You can always use
-   <application>libpq</application> functions on the
-   <structname>PGresult</structname> pointer returned by
-   <function>doquery</function>. <function>reset_fetch</function> starts
-   the fetch back at the beginning.
-  </para>
-
-  <para>
-   <function>get_result</function> and <function>set_result</function>
-   allow you to handle multiple open result sets. Use
-   <function>get_result</function> to save a result into an application
-   variable. You can then later use <function>set_result</function> to
-   return to the previously save result.
-  </para>
-
-  <para>
-   There are several demonstration programs in
-   <filename>pgsql/src/interfaces/libpgeasy/examples</>.
-  </para>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/libpgtcl.sgml b/doc/src/sgml/libpgtcl.sgml
deleted file mode 100644
index 3bebbc327f8..00000000000
--- a/doc/src/sgml/libpgtcl.sgml
+++ /dev/null
@@ -1,2239 +0,0 @@
-<chapter id="pgtcl">
- <title><application>pgtcl</application> - Tcl Binding Library</title>
-
- <indexterm zone="pgtcl">
-  <primary>libpgtcl</primary>
- </indexterm>
-
- <indexterm zone="pgtcl">
-  <primary>Tcl</primary>
- </indexterm>
-
- <sect1 id="pgtcl-intro">
-  <title>Introduction</title>
-
-  <para>
-   <application>pgtcl</application> is a Tcl package for client
-   programs to interface with <ProductName>PostgreSQL</ProductName>
-   servers.  It makes most of the functionality of
-   <application>libpq</application> available to Tcl scripts.
-  </para>
-
-  <para>
-   This package was originally written by Jolly Chen.
-  </para>
-
-  <para>
-   <xref linkend="pgtcl-commands-table"> gives an overview over the
-   commands available in <application>pgtcl</application>. These
-   commands are described further on subsequent pages.
-  </para>
-
-
-<TABLE TOCENTRY="1" id="pgtcl-commands-table">
-<TITLE><literal>pgtcl</literal> Commands</TITLE>
-<TGROUP COLS="2">
-<THEAD>
-  <ROW>
-    <ENTRY>Command</ENTRY>
-    <ENTRY>Description</ENTRY>
-  </ROW>
-</THEAD>
-<TBODY>
-  <ROW>
-    <ENTRY><function>pg_connect</function></ENTRY>
-    <ENTRY>opens a connection to the backend server</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_disconnect</function></ENTRY>
-    <ENTRY>closes a connection</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_conndefaults</function></ENTRY>
-    <ENTRY>get connection options and their defaults</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_exec</function></ENTRY>
-    <ENTRY>send a query to the backend</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_result</function></ENTRY>
-    <ENTRY>manipulate the results of a query</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_select</function></ENTRY>
-    <ENTRY>loop over the result of a SELECT statement</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_execute</function></ENTRY>
-    <ENTRY>send a query and optionally loop over the results</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_listen</function></ENTRY>
-    <ENTRY>establish a callback for NOTIFY messages</ENTRY>
-  </ROW>
-
-  <ROW>
-    <ENTRY><function>pg_lo_creat</function></ENTRY>
-    <ENTRY>create a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_open</function></ENTRY>
-    <ENTRY>open a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_close</function></ENTRY>
-    <ENTRY>close a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_read</function></ENTRY>
-    <ENTRY>read a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_write</function></ENTRY>
-    <ENTRY>write a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_lseek</function></ENTRY>
-    <ENTRY>seek to a position in a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_tell</function></ENTRY>
-    <ENTRY>return the current seek position of a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_unlink</function></ENTRY>
-    <ENTRY>delete a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_import</function></ENTRY>
-    <ENTRY>import a Unix file into a large object</ENTRY>
-  </ROW>
-  <ROW>
-    <ENTRY><function>pg_lo_export</function></ENTRY>
-    <ENTRY>export a large object into a Unix file</ENTRY>
-  </ROW>
-</TBODY>
-</TGROUP>
-</TABLE>
-
-  <para>
-   The <function>pg_lo_*</function> routines are interfaces to the
-   large object features of <ProductName>PostgreSQL</ProductName>.
-   The functions are designed to mimic the analogous file system
-   functions in the standard Unix file system interface.  The
-   <function>pg_lo_*</function> routines should be used within a
-   <command>BEGIN</command>/<command>COMMIT</command> transaction
-   block because the file descriptor returned by
-   <function>pg_lo_open</function> is only valid for the current
-   transaction.  <function>pg_lo_import</function> and
-   <function>pg_lo_export</function> <emphasis>must</emphasis> be used
-   in a <command>BEGIN</command>/<command>COMMIT</command> transaction
-   block.
-  </para>
-
-  <para>
-   <xref linkend="pgtcl-example"> shows a small example of how to use
-   the routines.
-  </para>
-
-  <example id="pgtcl-example">
-   <title><application>pgtcl</application> Example Program</title>
-
-<programlisting>
-# getDBs :
-#   get the names of all the databases at a given host and port number
-#   with the defaults being the localhost and port 5432
-#   return them in alphabetical order
-proc getDBs { {host "localhost"} {port "5432"} } {
-    # datnames is the list to be result
-    set conn [pg_connect template1 -host $host -port $port]
-    set res [pg_exec $conn "SELECT datname FROM pg_database ORDER BY datname"]
-    set ntups [pg_result $res -numTuples]
-    for {set i 0} {$i < $ntups} {incr i} {
-	lappend datnames [pg_result $res -getTuple $i]
-    }
-    pg_result $res -clear
-    pg_disconnect $conn
-    return $datnames
-}
-</programlisting>
-  </example>
- </sect1>
-
-<Sect1 id="libpgtcl-loading">
-<Title>Loading <application>pgtcl</application> into your application</Title>
-
-   <para>
-    Before using <application>pgtcl</application> commands, you must load
-    <filename>libpgtcl</> into your Tcl application.  This is normally
-    done with the Tcl <literal>load</> command.  Here is an example:
-
-<programlisting>
-load libpgtcl[info sharedlibextension]
-</programlisting>
-
-    The use of <literal>info sharedlibextension</> is recommended in
-    preference to hard-wiring <literal>.so</> or  <literal>.sl</> into
-    the program.
-   </para>
-
-   <para>
-    The <literal>load</> command will fail unless the system's dynamic
-    loader knows where to look for the <filename>libpgtcl</> shared
-    library file.  You may need to work with <command>ldconfig</>, or
-    set the environment variable <envar>LD_LIBRARY_PATH</>, or use
-    some equivalent facility for your platform to make it work.  Refer
-    to the <productname>PostgreSQL</> installation instructions for
-    more information.
-   </para>
-
-   <para>
-    <filename>libpgtcl</> in turn depends on <filename>libpq</>, so the
-    dynamic loader must also be able to find the <filename>libpq</> shared
-    library.  In practice this is seldom an issue, since both of these
-    shared libraries are normally stored in the same directory, but it
-    can be a stumbling block in some configurations.
-   </para>
-
-   <para>
-    If you use a custom executable for your application, you might choose
-    to statically bind <filename>libpgtcl</> into the executable and thereby
-    avoid the <literal>load</> command and the potential problems of dynamic
-    linking.  See the source code for <application>pgtclsh</> for an example.
-   </para>
-
-</Sect1>
-
-<Sect1 id="libpgtcl-ref">
-<Title><application>pgtcl</application> Command Reference Information</Title>
-
-<REFENTRY ID="PGTCL-PGCONNECT">
-<REFMETA>
-<REFENTRYTITLE>pg_connect</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Connection Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_connect
-</REFNAME>
-<REFPURPOSE>open a connection to the backend server
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGCONNECT-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGCONNECT-2"><PRIMARY>pg_connect</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_connect -conninfo <REPLACEABLE CLASS="PARAMETER">connectOptions</REPLACEABLE>
-pg_connect <REPLACEABLE CLASS="PARAMETER">dbName</REPLACEABLE> <OPTIONAL>-host <REPLACEABLE CLASS="PARAMETER">hostName</REPLACEABLE></OPTIONAL>
-  <OPTIONAL>-port <REPLACEABLE
-  CLASS="PARAMETER">portNumber</REPLACEABLE></OPTIONAL> <OPTIONAL>-tty <REPLACEABLE
-  CLASS="PARAMETER">pqtty</REPLACEABLE></OPTIONAL>
-  <OPTIONAL>-options <REPLACEABLE
-  CLASS="PARAMETER">optionalBackendArgs</REPLACEABLE></OPTIONAL>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGCONNECT-1">
-<REFSECT2INFO>
-<DATE>1998-10-07</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs (new style)
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">connectOptions</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>A string of connection options, each written in the form keyword = value.
-A list of valid options can be found in <filename>libpq</>'s
-<function>PQconnectdb()</> manual entry.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGCONNECT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs (old style)
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">dbName</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database name.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <OPTIONAL>-host <REPLACEABLE CLASS="PARAMETER">hostName</REPLACEABLE></OPTIONAL>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the domain name of the backend server for <REPLACEABLE CLASS="PARAMETER">dbName</REPLACEABLE>.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <OPTIONAL>-port <REPLACEABLE CLASS="PARAMETER">portNumber</REPLACEABLE></OPTIONAL>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the IP port number of the backend server for <REPLACEABLE CLASS="PARAMETER">dbName</REPLACEABLE>.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <OPTIONAL>-tty <REPLACEABLE CLASS="PARAMETER">pqtty</REPLACEABLE></OPTIONAL>
-</TERM>
-<LISTITEM>
-<PARA>Specifies file or <acronym>tty</acronym> for optional debug output from backend.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <OPTIONAL>-options <REPLACEABLE CLASS="PARAMETER">optionalBackendArgs</REPLACEABLE></OPTIONAL>
-</TERM>
-<LISTITEM>
-<PARA>Specifies options for the backend server for <REPLACEABLE CLASS="PARAMETER">dbName</REPLACEABLE>.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGCONNECT-3">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-If successful, a handle for a database connection is returned.
-Handles start with the prefix <literal>pgsql</literal>.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<!-- ********************************************************** -->
-
-<REFSECT1 ID="R1-PGTCL-PGCONNECT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_connect</FUNCTION> opens a connection to the
-<ProductName>PostgreSQL</ProductName> backend.
-</Para>
-
-<para>
-Two syntaxes are available.  In the older one, each possible option
-has a separate option switch in the pg_connect statement.  In the
-newer form, a single option string is supplied that can contain
-multiple option values.  See <FUNCTION>pg_conndefaults</FUNCTION>
-for info about the available options in the newer syntax.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGCONNECT-2">
-<TITLE>Usage
-</TITLE>
-<comment>
- XXX thomas 1997-12-24
-</comment>
-</REFSECT1>
-</REFENTRY>
-
-<REFENTRY ID="PGTCL-PGDISCONNECT">
-<REFMETA>
-<REFENTRYTITLE>pg_disconnect</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Connection Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_disconnect
-</REFNAME>
-<REFPURPOSE>close a connection to the backend server
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGDISCONNECT-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGDISCONNECT-2"><PRIMARY>pg_connect</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_disconnect <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGDISCONNECT-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database handle.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGDISCONNECT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  None
-</TERM>
-<LISTITEM>
-<PARA>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGDISCONNECT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_disconnect</FUNCTION> closes a connection to the <ProductName>PostgreSQL</ProductName> backend.
-</PARA>
-</REFSECT1>
-
-</REFENTRY>
-
-
-
-
-<REFENTRY ID="PGTCL-PGCONNDEFAULTS">
-<REFMETA>
-<REFENTRYTITLE>pg_conndefaults</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Connection Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_conndefaults
-</REFNAME>
-<REFPURPOSE>obtain information about default connection parameters
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGCONNDEFAULTS-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGCONNDEFAULTS-2"><PRIMARY>pg_conndefaults</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1998-10-07</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_conndefaults
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGCONNDEFAULTS-1">
-<REFSECT2INFO>
-<DATE>1998-10-07</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<PARA>
-None.
-</PARA>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGCONNDEFAULTS-2">
-<REFSECT2INFO>
-<DATE>1998-10-07</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">option list</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-The result is a list describing the possible connection options and their
-current default values.
-Each entry in the list is a sublist of the format:
-</Para>
-<screen>
-{optname label dispchar dispsize value}
-</screen>
-<Para>
-where the <replaceable>optname</> is usable as an option in
-<FUNCTION>pg_connect -conninfo</FUNCTION>.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGCONNDEFAULTS-1">
-<REFSECT1INFO>
-<DATE>1998-10-07</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-
-<para>
-<FUNCTION>pg_conndefaults</FUNCTION> returns info about the connection
-options available in <FUNCTION>pg_connect -conninfo</FUNCTION> and the
-current default value for each option.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGCONNDEFAULTS-2">
-<TITLE>Usage
-</TITLE>
-<PARA><literal>pg_conndefaults</>
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<REFENTRY ID="PGTCL-PGEXEC">
-<REFMETA>
-<REFENTRYTITLE>pg_exec</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Query Processing</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_exec
-</REFNAME>
-<REFPURPOSE>
-send a command string to the server
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGEXEC-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGEXEC-2"><PRIMARY>pg_connect</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_exec <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">queryString</REPLACEABLE>
-</SYNOPSIS>
-
-<!-- ********************************************************** -->
-
-<REFSECT2 ID="R2-PGTCL-PGEXEC-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database handle.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">queryString</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid SQL query.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGEXEC-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">resultHandle</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-A Tcl error will be returned if <application>pgtcl</application> was unable to obtain a backend
-response.  Otherwise, a query result object is created and a handle for
-it is returned.  This handle can be passed to <FUNCTION>pg_result</FUNCTION>
-to obtain the results of the query.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2></REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGEXEC-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>pg_exec</FUNCTION> submits a query to the <ProductName>PostgreSQL</ProductName> backend and returns a result.
-
-Query result handles start with the connection handle and add a period
-and a result number.
-</Para>
-
-<PARA>
-Note that lack of a Tcl error is not proof that the query succeeded!
-An error message returned by the backend will be processed
-as a query result with failure status, not by generating a Tcl error
-in pg_exec.
-</PARA>
-</REFSECT1>
-</refentry>
-
-<REFENTRY ID="PGTCL-PGRESULT">
-<REFMETA>
-<REFENTRYTITLE>pg_result</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Query Processing</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_result
-</REFNAME>
-<REFPURPOSE>
-get information about a query result
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGRESULT-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGRESULT-2"><PRIMARY>pg_connect</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_result <REPLACEABLE CLASS="PARAMETER">resultHandle</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">resultOption</REPLACEABLE>
-</SYNOPSIS>
-<REFSECT2 ID="R2-PGTCL-PGRESULT-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">resultHandle</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-  The handle for a query result.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">resultOption</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Specifies one of several possible options.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-
-<REFSECT3>
-<TITLE>Options</TITLE>
-
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-<option>-status</option>
-</TERM>
-<LISTITEM>
-<PARA>
-the status of the result.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-error</option>
-</TERM>
-<LISTITEM>
-<PARA>
-the error message, if the status indicates error; otherwise an empty string.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-conn</option>
-</TERM>
-<LISTITEM>
-<PARA>
-the connection that produced the result.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-oid</option>
-</TERM>
-<LISTITEM>
-<PARA>
-if the command was an INSERT, the OID of the 
-inserted tuple; otherwise an empty string.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-numTuples</option>
-</TERM>
-<LISTITEM>
-<PARA>
-the number of tuples returned by the query.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-numAttrs</option>
-</TERM>
-<LISTITEM>
-<PARA>
-the number of attributes in each tuple.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-assign arrayName</option>
-</TERM>
-<LISTITEM>
-<PARA>
-assign the results to an array, using subscripts of the form
-<literal>(tupno,attributeName)</literal>.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-assignbyidx arrayName ?appendstr?</option>
-</TERM>
-<LISTITEM>
-<PARA>
-assign the results to an array using the first attribute's value and
-the remaining attributes' names as keys.  If <parameter>appendstr</> is given then
-it is appended to each key.  In short, all but the first field of each
-tuple are stored into the array, using subscripts of the form
-<literal>(firstFieldValue,fieldNameAppendStr)</literal>.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-getTuple tupleNumber</option>
-</TERM>
-<LISTITEM>
-<PARA>
-returns the fields of the indicated tuple in a list.  Tuple numbers
-start at zero.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-tupleArray tupleNumber arrayName</option>
-</TERM>
-<LISTITEM>
-<PARA>
-stores the fields of the tuple in array <parameter>arrayName</parameter>, indexed by field names.
-Tuple numbers start at zero.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-attributes</option>
-</TERM>
-<LISTITEM>
-<PARA>
-returns a list of the names of the tuple attributes.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-lAttributes</option>
-</TERM>
-<LISTITEM>
-<PARA>
-returns a list of sublists, <literal>{name ftype fsize}</literal> for each tuple attribute.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<option>-clear</option>
-</TERM>
-<LISTITEM>
-<PARA>
-clear the result query object.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT3>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGRESULT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<PARA>
-The result depends on the selected option, as described above.
-</PARA>
-</REFSECT2></REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGRESULT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>pg_result</FUNCTION> returns information about a query result
-created by a prior <FUNCTION>pg_exec</FUNCTION>.
-</Para>
-
-<para>
-You can keep a query result around for as long as you need it, but when
-you are done with it, be sure to free it by
-executing <FUNCTION>pg_result -clear</FUNCTION>.  Otherwise, you have
-a memory leak, and <application>Pgtcl</> will eventually start complaining that you've
-created too many query result objects.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGSELECT">
-<REFMETA>
-<REFENTRYTITLE>pg_select</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Query Processing</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_select
-</REFNAME>
-<REFPURPOSE>
-loop over the result of a SELECT statement
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGSELECT-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGSELECT-2"><PRIMARY>pg_connect</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_select <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">queryString</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">arrayVar</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">queryProcedure</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGSELECT-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database handle.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">queryString</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid SQL select query.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">arrayVar</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Array variable for tuples returned.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">queryProcedure</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Procedure run on each tuple found.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGSELECT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<Para>
-None.
-</Para>
-</REFSECT2></REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGSELECT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>pg_select</FUNCTION> submits a SELECT query to the
-<ProductName>PostgreSQL</ProductName> backend, and executes a
-given chunk of code for each tuple in the result.
-  The <REPLACEABLE CLASS="PARAMETER">queryString</REPLACEABLE>
-  must be a SELECT statement.  Anything else returns an error.
-  The <REPLACEABLE CLASS="PARAMETER">arrayVar</REPLACEABLE>
-  variable is an array name used in the loop.  For each tuple,
-  <REPLACEABLE CLASS="PARAMETER">arrayVar</REPLACEABLE> is filled in
-  with the tuple field values, using the field names as the array
-  indexes.  Then the
-  <REPLACEABLE CLASS="PARAMETER">queryProcedure</REPLACEABLE>
-  is executed.
-</PARA>
-
-<PARA>
- In addition to the field values, the following special entries are
-made in the array:
-
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM><literal>.headers</></TERM>
-<LISTITEM>
-<PARA>A list of the column names returned by the SELECT.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM><literal>.numcols</></TERM>
-<LISTITEM>
-<PARA>The number of columns returned by the SELECT.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM><literal>.tupno</></TERM>
-<LISTITEM>
-<PARA>The current tuple number, starting at zero and incrementing
-for each iteration of the loop body.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</PARA>
-
-</REFSECT1>
-
-<REFSECT1 ID="R1-PGTCL-PGSELECT-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-This would work if table <classname>table</> has fields <structfield>control</> and <structfield>name</>
-(and, perhaps, other fields):
-<ProgramListing>
-	pg_select $pgconn "SELECT * FROM table" array {
-		puts [format "%5d %s" $array(control) $array(name)]
-	}
-</ProgramListing>
-</PARA>
-</REFSECT1>
-
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGEXECUTE">
-<REFMETA>
-<REFENTRYTITLE>pg_execute</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Query Processing</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_execute
-</REFNAME>
-<REFPURPOSE>
-send a query and optionally loop over the results
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGEXECUTE-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>query</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGEXECUTE-2"><PRIMARY>pg_execute</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2002-03-06</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_execute <OPTIONAL>-array <REPLACEABLE CLASS="PARAMETER">arrayVar</REPLACEABLE></OPTIONAL> <OPTIONAL>-oid <REPLACEABLE CLASS="PARAMETER">oidVar</REPLACEABLE></OPTIONAL> <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">queryString</REPLACEABLE> <OPTIONAL><REPLACEABLE CLASS="PARAMETER">queryProcedure</REPLACEABLE></OPTIONAL>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGEXECUTE-1">
-<REFSECT2INFO>
-<DATE>2002-03-06</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <OPTIONAL>-array <REPLACEABLE CLASS="PARAMETER">arrayVar</REPLACEABLE></OPTIONAL>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the name of an array variable where result tuples are stored,
-indexed by the field names.
-This is ignored if queryString is not a SELECT statement. For SELECT
-statements, if this option is not used, result tuples values are stored
-in individual variables named according to the field names in the result.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <OPTIONAL>-oid <REPLACEABLE CLASS="PARAMETER">oidVar</REPLACEABLE></OPTIONAL>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the name of a variable into which the OID from an INSERT
-statement will be stored.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database handle.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">queryString</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid SQL query.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <OPTIONAL><REPLACEABLE CLASS="PARAMETER">queryProcedure</REPLACEABLE></OPTIONAL>
-</TERM>
-<LISTITEM>
-<PARA>Optional command to execute for each result tuple of a SELECT statement.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGEXECUTE-2">
-<REFSECT2INFO>
-<DATE>2002-03-06</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">ntuples</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-The number of tuples affected or returned by the query.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2></REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGEXECUTE-1">
-<REFSECT1INFO>
-<DATE>2002-03-06</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>pg_execute</FUNCTION> submits a query to the PostgreSQL backend.
-</PARA>
-<PARA>
-If the query is not a SELECT statement, the query is executed and the
-number of tuples affected by the query is returned.  If the query is an
-INSERT and a single tuple is inserted, the OID of the inserted tuple is
-stored in the oidVar variable if the optional <PARAMETER>-oid</PARAMETER>
-argument is supplied.
-</PARA>
-<PARA>
-If the query is a SELECT statement, the query is executed. For each tuple
-in the result, the tuple field values are stored in the
-<PARAMETER>arrayVar</PARAMETER> variable,
-if supplied, using the field names as the array indexes, else in variables
-named by the field names, and then the optional
-<PARAMETER>queryProcedure</PARAMETER> is executed if supplied.
-(Omitting the <PARAMETER>queryProcedure</PARAMETER> probably makes sense
-only if the query will return a single tuple.)
-The number of tuples selected is returned.
-</PARA>
-<PARA>
-The <PARAMETER>queryProcedure</PARAMETER> can use the Tcl
-<LITERAL>break</LITERAL>, <LITERAL>continue</LITERAL>, and
-<LITERAL>return</LITERAL> commands, with the expected behavior.
-Note that if the <PARAMETER>queryProcedure</PARAMETER> executes
-<LITERAL>return</LITERAL>, <FUNCTION>pg_execute</FUNCTION> does
-not return <PARAMETER>ntuples</PARAMETER>.
-</PARA>
-<PARA>
-<FUNCTION>pg_execute</FUNCTION> is a newer function which provides a
-superset of the features of <FUNCTION>pg_select</FUNCTION>, and can
-replace <FUNCTION>pg_exec</FUNCTION> in many cases where access to
-the result handle is not needed.
-</PARA>
-<PARA>
-For backend-handled errors, <FUNCTION>pg_execute</FUNCTION> will
-throw a Tcl error and return two element list. The first element
-is an error code such as <LITERAL>PGRES_FATAL_ERROR</LITERAL>, and
-the second element is the backend error text. For more serious
-errors, such as failure to communicate with the backend,
-<FUNCTION>pg_execute</FUNCTION> will throw a Tcl error and return
-just the error message text.
-</PARA>
-
-</REFSECT1>
-
-<REFSECT1 ID="R1-PGTCL-PGEXECUTE-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-In the following examples, error checking with <LITERAL>catch</LITERAL>
-has been omitted for clarity.
-</PARA>
-<PARA>
-Insert a row and save the OID in result_oid:
-<ProgramListing>
-    pg_execute -oid result_oid $pgconn "insert into mytable values (1)"
-</ProgramListing>
-</PARA>
-<PARA>
-Print the item and value fields from each row:
-<ProgramListing>
-    pg_execute -array d $pgconn "select item, value from mytable" {
-       puts "Item=$d(item) Value=$d(value)"
-    }
-</ProgramListing>
-</PARA>
-<PARA>
-Find the maximum and minimum values and store them in $s(max) and $s(min):
-<ProgramListing>
-    pg_execute -array s $pgconn "select max(value) as max,\
-      min(value) as min from mytable"
-</ProgramListing>
-</PARA>
-<PARA>
-Find the maximum and minimum values and store them in $max and $min:
-<ProgramListing>
-    pg_execute $pgconn "select max(value) as max, min(value) as min from mytable"
-</ProgramListing>
-</PARA>
-</REFSECT1>
-
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLISTEN">
-<REFMETA>
-<REFENTRYTITLE>pg_listen</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Asynchronous Notify</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_listen
-</REFNAME>
-<REFPURPOSE>set or change a callback for asynchronous NOTIFY messages
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLISTEN-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>notify</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLISTEN-2"><PRIMARY>notify</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1998-5-22</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_listen <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">notifyName</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">callbackCommand</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLISTEN-1">
-<REFSECT2INFO>
-<DATE>1998-5-22</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">dbHandle</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database handle.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">notifyName</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the notify condition name to start or stop listening to.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">callbackCommand</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>If present and not empty, provides the command string to execute
-when a matching notification arrives.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLISTEN-2">
-<REFSECT2INFO>
-<DATE>1998-5-22</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  None
-</TERM>
-<LISTITEM>
-<PARA>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLISTEN-1">
-<REFSECT1INFO>
-<DATE>1998-5-22</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_listen</FUNCTION> creates, changes, or cancels a request
-to listen for asynchronous NOTIFY messages from the
-<ProductName>PostgreSQL</ProductName> backend.  With a <parameter>callbackCommand</>
-parameter, the request is established, or the command string of an already
-existing request is replaced.  With no <parameter>callbackCommand</> parameter, a prior
-request is canceled.
-</PARA>
-
-<para>
-After a <FUNCTION>pg_listen</FUNCTION> request is established,
-the specified command string is executed whenever a NOTIFY message bearing
-the given name arrives from the backend.  This occurs when any
-<ProductName>PostgreSQL</ProductName> client application issues a NOTIFY command
-referencing that name.  (Note that the name can be, but does not have to be,
-that of an existing relation in the database.)
-The command string is executed from the Tcl idle loop.  That is the normal
-idle state of an application written with Tk.  In non-Tk Tcl shells, you can
-execute <FUNCTION>update</FUNCTION> or <FUNCTION>vwait</FUNCTION> to cause
-the idle loop to be entered.
-</Para>
-
-<para>
-You should not invoke the SQL statements <command>LISTEN</command> or <command>UNLISTEN</command> directly when
-using <FUNCTION>pg_listen</FUNCTION>.  <application>Pgtcl</application> takes care of issuing those
-statements for you.  But if you want to send a NOTIFY message yourself,
-invoke the SQL NOTIFY statement using <FUNCTION>pg_exec</FUNCTION>.
-</PARA>
-</REFSECT1>
-
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOCREAT">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_creat</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_creat
-</REFNAME>
-<REFPURPOSE>create a large object
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOCREAT-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>creating</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOCREAT-2"><PRIMARY>pg_lo_creat</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_creat <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">mode</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOCREAT-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">mode</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the access mode for the large object</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOCREAT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">objOid</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-The OID of the large object created.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOCREAT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_creat</FUNCTION> creates an Inversion Large Object.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOCREAT-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-mode can be any or'ing together of <literal>INV_READ</> and <literal>INV_WRITE</>.
-The <quote>or</quote> operator is <literal>|</literal>.
-<ProgramListing>
-[pg_lo_creat $conn "INV_READ|INV_WRITE"]
-</ProgramListing>
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOOPEN">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_open</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_open
-</REFNAME>
-<REFPURPOSE>open a large object
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOOPEN-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>opening</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOOPEN-2"><PRIMARY>pg_lo_open</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_open <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">objOid</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">mode</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOOPEN-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">objOid</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid large object OID.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">mode</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the access mode for the large object</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOOPEN-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-A file descriptor for use in later pg_lo* routines.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOOPEN-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_open</FUNCTION> open an Inversion Large Object.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOOPEN-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-Mode can be either <literal>r</>, <literal>w</>, or <literal>rw</>.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOCLOSE">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_close</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_close
-</REFNAME>
-<REFPURPOSE>close a large object
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOCLOSE-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>closing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOCLOSE-2"><PRIMARY>pg_lo_close</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_close <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOCLOSE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-A file descriptor for use in later pg_lo* routines.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOCLOSE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<PARA>None</PARA>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOCLOSE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_close</FUNCTION> closes an Inversion Large Object.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOCLOSE-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOREAD">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_read</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_read
-</REFNAME>
-<REFPURPOSE>read a large object
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOREAD-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>reading</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOREAD-2"><PRIMARY>pg_lo_read</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_read <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">bufVar</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">len</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOREAD-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-File descriptor for the large object from pg_lo_open.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">bufVar</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid buffer variable to contain the large object segment.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">len</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the maximum allowable size of the large object segment.</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOREAD-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<PARA>None</PARA>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOREAD-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_read</FUNCTION> reads 
-at most <REPLACEABLE CLASS="PARAMETER">len</REPLACEABLE> bytes from a large object into a variable
- named <REPLACEABLE CLASS="PARAMETER">bufVar</REPLACEABLE>.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOREAD-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-<REPLACEABLE CLASS="PARAMETER">bufVar</REPLACEABLE> must be a valid variable name.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOWRITE">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_write</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_write
-</REFNAME>
-<REFPURPOSE>write a large object
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOWRITE-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>writing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOWRITE-2"><PRIMARY>pg_lo_write</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_write <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">buf</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">len</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOWRITE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-File descriptor for the large object from pg_lo_open.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">buf</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid string variable to write to the large object.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">len</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies the maximum size of the string to write.</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOWRITE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<PARA>None</PARA>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOWRITE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_write</FUNCTION> writes 
-at most <REPLACEABLE CLASS="PARAMETER">len</REPLACEABLE> bytes to a large object from a variable
- <REPLACEABLE CLASS="PARAMETER">buf</REPLACEABLE>.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOWRITE-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-<REPLACEABLE CLASS="PARAMETER">buf</REPLACEABLE> must be 
-the actual string to write, not a variable name.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOLSEEK">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_lseek</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_lseek
-</REFNAME>
-<REFPURPOSE>seek to a position in a large object
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOLSEEK-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>positioning</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOLSEEK-2"><PRIMARY>pg_lo_lseek</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_lseek <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">offset</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">whence</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOLSEEK-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-File descriptor for the large object from pg_lo_open.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">offset</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a zero-based offset in bytes.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">whence</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA> whence can be <literal>SEEK_CUR</>, <literal>SEEK_END</>, or <literal>SEEK_SET</> </PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOLSEEK-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<PARA>None</PARA>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOLSEEK-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_lseek</FUNCTION> positions 
-to <REPLACEABLE CLASS="PARAMETER">offset</REPLACEABLE> bytes from the beginning of the large object.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOLSEEK-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-<REPLACEABLE CLASS="PARAMETER">whence</REPLACEABLE> 
-can be <literal>SEEK_CUR</literal>, <literal>SEEK_END</>, or <literal>SEEK_SET</literal>.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOTELL">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_tell</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_tell
-</REFNAME>
-<REFPURPOSE>return the current seek position of a large object
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOTELL-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>positioning</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOTELL-2"><PRIMARY>pg_lo_tell</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_tell <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOTELL-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">fd</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-File descriptor for the large object from pg_lo_open.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOTELL-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">offset</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>A zero-based offset in bytes suitable for input to <Function>pg_lo_lseek</Function>.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOTELL-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_tell</FUNCTION> returns the current
-to <REPLACEABLE CLASS="PARAMETER">offset</REPLACEABLE> in bytes from the beginning of the large object.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOTELL-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOUNLINK">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_unlink</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_unlink
-</REFNAME>
-<REFPURPOSE>delete a large object
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOUNLINK-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>delete</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOUNLINK-2"><PRIMARY>pg_lo_unlink</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_unlink <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">lobjId</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOUNLINK-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">lobjId</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Identifier for a large object.
-<comment>
- XXX Is this the same as <parameter>objOid</parameter> in other calls?? - thomas 1998-01-11
-</comment>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOUNLINK-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<PARA>
-None
-</PARA>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOUNLINK-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_unlink</FUNCTION> deletes the specified large object.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOUNLINK-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOIMPORT">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_import</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_import
-</REFNAME>
-<REFPURPOSE>import a large object from a file
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOIMPORT-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>import</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOIMPORT-2"><PRIMARY>pg_lo_import</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_import <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">filename</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOIMPORT-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">filename</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Unix file name.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOIMPORT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<PARA>
-None
-<comment>
- XXX Does this return a lobjId? Is that the same as the objOid in other calls? thomas - 1998-01-11
-</comment>
-</PARA>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOIMPORT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_import</FUNCTION> reads the specified file and places the contents into a large object.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOIMPORT-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-  <Function>pg_lo_import</Function> must be called within a BEGIN/END transaction block.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- ********************************************************** -->
-
-<REFENTRY ID="PGTCL-PGLOEXPORT">
-<REFMETA>
-<REFENTRYTITLE>pg_lo_export</REFENTRYTITLE>
-<REFMISCINFO>PGTCL - Large Objects</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>pg_lo_export
-</REFNAME>
-<REFPURPOSE>export a large object to a file
-</REFPURPOSE>
-<INDEXTERM ID="IX-PGTCL-PGLOEXPORT-1"><PRIMARY>pgtcl</PRIMARY><SECONDARY>export</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-PGTCL-PGLOEXPORT-2"><PRIMARY>pg_lo_export</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-pg_lo_export <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">lobjId</REPLACEABLE> <REPLACEABLE CLASS="PARAMETER">filename</REPLACEABLE>
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-PGTCL-PGLOEXPORT-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">conn</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>Specifies a valid database connection.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">lobjId</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Large object identifier.
-<comment>
- XXX Is this the same as the objOid in other calls?? thomas - 1998-01-11
-</comment>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-  <REPLACEABLE CLASS="PARAMETER">filename</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Unix file name.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-PGTCL-PGLOEXPORT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<PARA>
-None
-<comment>
- XXX Does this return a lobjId? Is that the same as the objOid in other calls? thomas - 1998-01-11
-</comment>
-</PARA>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-PGTCL-PGLOEXPORT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA><FUNCTION>pg_lo_export</FUNCTION> writes the specified large object into a Unix file.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-PGTCL-PGLOEXPORT-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-  <Function>pg_lo_export</Function> must be called within a BEGIN/END transaction block.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-</Sect1>
-</Chapter>
diff --git a/doc/src/sgml/libpq++.sgml b/doc/src/sgml/libpq++.sgml
deleted file mode 100644
index cd6d2a6a911..00000000000
--- a/doc/src/sgml/libpq++.sgml
+++ /dev/null
@@ -1,840 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpq++.sgml,v 1.41 2002/03/22 19:20:12 petere Exp $
--->
-
- <chapter id="libpqplusplus">
-  <title><application>libpq++</application> - C++ Binding Library</title>
-
- <indexterm zone="libpqplusplus">
-  <primary>libpq++</primary>
- </indexterm>
- <indexterm zone="libpqplusplus">
-  <primary>C++</primary>
- </indexterm>
-  
- <sect1 id="libpqpp-introduction">
-  <title>Introduction</title>
-
-  <para>
-   <application>libpq++</application> is the C++ API to 
-   <productname>PostgreSQL</productname>.
-   <application>libpq++</application>  is a set of classes that allow
-   client programs to connect to the 
-   <productname>PostgreSQL</productname> backend server. These connections
-   come in two forms: a database class and a large object class.
-  </para>
-
-  <para>
-   The database class is intended for manipulating a database. You can
-   send all sorts of SQL queries and commands to the <productname>PostgreSQL</productname> 
-   backend server and retrieve the responses of the server.
-  </para>
-
-  <para>
-   The large object class is intended for manipulating a large object
-   in a database. Although a large object instance can send normal
-   queries to the <productname>PostgreSQL</productname> backend server 
-   it is only intended for simple
-   queries that do not return any data. A large object should be seen
-   as a file stream. In the future it should behave much like the C++ file
-   streams
-   <literal>cin</literal>,
-   <literal>cout</literal>
-   and
-   <literal>cerr</literal>.
-  </para>
-
-  <para>
-   This chapter is based on the documentation for the
-   <application>libpq</application> C library (see <xref
-   linkend="libpq">).  There
-   are several examples of <application>libpq++</application>
-   applications in
-   <filename>src/interfaces/libpq++/examples</filename> in the source
-   distribution.
-  </para>
- </sect1>
-
-  <sect1 id="libpqpp-init">
-   <title>Control and Initialization</title>
-    
-   <sect2>
-    <title>Environment Variables</title>
-    <para>
-     The following environment variables can be used to set up default
-     values for an environment and to avoid hard-coding database names into
-     an application program:
-     <note>
-      <para>
-       Refer to <xref linkend="libpq-envars"> for a complete
-       list of available connection options.
-      </para>
-     </note>
-    </para>
-
-    <para>
-     The following environment variables can be used to select default
-     connection parameter values, which will be used by
-     <function>PQconnectdb</> or
-     <function>PQsetdbLogin</> if no value is directly specified by the calling code.
-     These are useful to avoid hard-coding database names into simple
-     application programs.
-     <note>
-      <para>
-       <filename>libpq++</filename> uses only environment variables or
-       <filename>libpq</>'s <function>PQconnectdb</>
-       <parameter>conninfo</parameter> style strings.
-      </para>
-     </note>
-	  
-     <itemizedlist>
-      <listitem>
-       <para>
-	<envar>PGHOST</envar> sets the default server 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 (default <filename>/tmp</filename>).
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<envar>PGPORT</envar> sets the default TCP port number or Unix-domain
-	socket file extension for communicating with the
-	<productname>PostgreSQL</productname> backend.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<envar>PGDATABASE</envar>  sets the default 
-	<productname>PostgreSQL</productname> database name.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<envar>PGUSER</envar>
-	sets the user name used to connect to the database and for authentication.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<envar>PGPASSWORD</envar>
-	sets the password used if the backend demands password
-	authentication. This is not recommended because the password can
-	be read by others using the <command>ps</command> command with special options
-	on some platforms.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<envar>PGREALM</envar> sets the Kerberos realm to  use  with  
-	<productname>PostgreSQL</productname>,
-	if  it is different from the local realm.  If
-	<envar>PGREALM</envar> is set, <productname>PostgreSQL</productname> 
-	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 backend.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<envar>PGOPTIONS</envar> sets additional run-time  options  for  
-	the <productname>PostgreSQL</productname> backend.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<envar>PGTTY</envar> sets the file or <acronym>tty</acronym> on which  debugging  
-	messages from the backend server are displayed.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-	
-    <para>
-     The following environment variables can be used to specify user-level default
-     behavior for every <productname>PostgreSQL</productname> session:
-	  
-     <itemizedlist>
-      <listitem>
-       <para>
-	<envar>PGDATESTYLE</envar>
-	sets the default style of date/time representation.
-       </para>
-      </listitem>
-      <listitem>
-       <para>
-	<envar>PGTZ</envar>
-	sets the default time zone.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-    
-    <para>
-     The following environment variables can be used to specify default internal
-     behavior for every <productname>PostgreSQL</productname> session:
-     
-     <itemizedlist>
-      <listitem>
-       <para>
-	<envar>PGGEQO</envar>
-	sets the default mode for the genetic optimizer.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-	
-    <para>
-     Refer to the <command>SET</command> <acronym>SQL</acronym> command
-     for information on correct values for these environment variables.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="libpqpp-classes">
-   <title><application>libpq++</application> Classes</title>
-
-   <sect2>
-    <title>Connection Class: <classname>PgConnection</classname></title>
-
-    <para>
-     The connection class makes the actual connection to the database and is inherited
-     by all of the access classes.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Database Class: <classname>PgDatabase</classname></title>
-
-    <para>
-     The database class provides C++ objects that have a connection
-     to a backend server. To create such an object one first needs
-     the appropriate environment for the backend to access.
-     The following constructors deal with making a connection to a backend
-     server from a C++ program.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="libpqpp-connect">
-   <title>Database Connection Functions</title>
-   <para>
-    <itemizedlist>
-     <listitem>
-      <para>
-       <function>PgConnection</function>
-       makes a new connection to a backend database server.
-<synopsis>
-PgConnection::PgConnection(const char *conninfo)
-</synopsis>
-       The <parameter>conninfo</> string is the same as for the underlying
-       <application>libpq</> <function>PQconnectdb</> function.
-      </para>
-
-      <para>
-       Although typically called from one of the access classes, a connection to
-       a backend server is possible by creating a <classname>PgConnection</> object.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>ConnectionBad</function>
-       returns whether or not the connection to the backend server succeeded or
-       failed.  
-<synopsis>
-bool PgConnection::ConnectionBad() const
-</synopsis>
-       Returns true if the connection failed.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>Status</function>
-       returns the status of the connection to the backend server.
-<synopsis>
-ConnStatusType PgConnection::Status()
-</synopsis>
-       Returns either <symbol>CONNECTION_OK</> or
-       <symbol>CONNECTION_BAD</> depending on the state of the
-       connection.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>PgDatabase</function>
-       makes a new connection to a backend database server.
-<synopsis>
-PgDatabase(const char *conninfo)
-</synopsis>
-       After a <classname>PgDatabase</classname> has been created it should be checked to make sure
-       the connection to the database succeeded before sending
-       queries to the object. This can easily be done by
-       retrieving the current status of the <classname>PgDatabase</classname> object with the
-       <function>Status</function> or <function>ConnectionBad</function> methods.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>DBName</function>
-       returns the name of the current database.
-<synopsis>
-const char *PgConnection::DBName()
-</synopsis>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>Notifies</function>
-       returns the next notification from a list of unhandled notification messages 
-       received from the backend.
-<synopsis>
-PGnotify* PgConnection::Notifies()
-</synopsis>
-       See <function>PQnotifies</function> in <application>libpq</> for details.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-  </sect1>
-
-  <sect1 id="libpqpp-exec">
-   <title>Query Execution Functions</title>
-
-<sect2 id="libpqpp-exec-main">
-  <title>Main Routines</title>
-   <para>  
-    <itemizedlist>
-     <listitem>
-      <para>
-       <function>Exec</function>
-       sends a command to the backend server.  It's probably more desirable to
-       use one of the next two functions.
-<synopsis>
-ExecStatusType PgConnection::Exec(const char* query)
-</synopsis>
-       Returns the result status of the command. The following status
-       results can be expected:
-       
-       <simplelist>
-	<member>
-	 <symbol>PGRES_EMPTY_QUERY</symbol>
-	</member>
-	<member>
-	 <symbol>PGRES_COMMAND_OK</symbol>, if the command was not a query
-	</member>
-	<member>
-	 <symbol>PGRES_TUPLES_OK</symbol>, if the query successfully returned tuples
-	</member>
-	<member>
-	 <symbol>PGRES_COPY_OUT</symbol>
-	</member>
-	<member>
-	 <symbol>PGRES_COPY_IN</symbol>
-	</member>
-	<member>
-	 <symbol>PGRES_BAD_RESPONSE</symbol>, if an unexpected response was received
-	</member>
-	<member>
-	 <symbol>PGRES_NONFATAL_ERROR</symbol>
-	</member>
-	<member>
-	 <symbol>PGRES_FATAL_ERROR</symbol>
-	</member>
-       </simplelist>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>ExecCommandOk</function> sends a non-query command
-       (one that does not return rows) to the backend server.
-<synopsis>
-int PgConnection::ExecCommandOk(const char *query)
-</synopsis>
-       Returns true (1) if the command succeeds.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>ExecTuplesOk</function>
-       Sends a query command (one that returns rows) to the backend server.
-<synopsis>
-int PgConnection::ExecTuplesOk(const char *query)
-</synopsis>
-       Returns true (1) if the query succeeds.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>ErrorMessage</function>
-       returns the last error message text.
-<synopsis>
-const char *PgConnection::ErrorMessage()
-</synopsis>
-      </para>
-     </listitem>
-    </itemizedlist>
- </para>
-</sect2>
-
-<sect2 id="libpqpp-exec-select-info">
-  <title>Retrieving SELECT Result Information</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <function>Tuples</function>
-      returns the number of tuples (rows) in the query result. 
-<synopsis>
-int PgDatabase::Tuples() const
-</synopsis>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>Fields</function>
-      returns the number of fields (rows) in each tuple of the query result. 
-<synopsis>
-int PgDatabase::Fields()
-</synopsis>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>FieldName</function>
-      returns the field (column) name associated with the given field index. 
-      Field indices start at 0. 
-<synopsis>
-const char *PgDatabase::FieldName(int field_num) const
-</synopsis>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>FieldNum</function>
-      returns the field (column) index associated with 
-      the given field name. 
-<synopsis>
-int PgDatabase::FieldNum(const char* field_name) const
-</synopsis>
-      -1 is returned if the given name does not match any field.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>FieldType</function>
-      returns the field type associated with the given field index. The 
-      integer returned is an internal coding of the type. Field indices
-      start at 0. 
-<synopsis>
-Oid PgDatabase::FieldType(int field_num) const
-</synopsis>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>FieldType</function>
-      returns the field type associated with the given field name. The 
-      integer returned is an internal coding of the type. Field indices
-      start at 0. 
-<synopsis>
-Oid PgDatabase::FieldType(const char* field_name) const
-</synopsis>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>FieldSize</function>
-      returns the size in bytes of the field associated with the given 
-      field index. Field indices start at 0. 
-<synopsis>
-int PgDatabase::FieldSize(int field_num) const
-</synopsis>
-      Returns the space allocated for this field in a database tuple
-      given the field number. In other words the size of the server's
-      binary representation of the data type. -1 is returned if the
-      field is variable size.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>FieldSize</function>
-      returns the size in bytes of the field associated with the given 
-      field index. Field indices start at 0. 
-<synopsis>
-int PgDatabase::FieldSize(const char *field_name) const
-</synopsis>
-      Returns the space allocated for this field in a database tuple
-      given the field name. In other words the size of the server's
-      binary representation of the data type. -1 is returned if the
-      field is variable size.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect2>
-
-
-<sect2 id="libpqpp-exec-select-values">
-  <title>Retrieving SELECT Result Values</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <function>GetValue</function> returns a single field (column)
-      value of one tuple of a <structname>PGresult</structname>.
-      Tuple and field indices start at 0.
-<synopsis>
-const char *PgDatabase::GetValue(int tup_num, int field_num) const
-</synopsis>
-      For most queries, the value returned by
-      <function>GetValue</function> is a null-terminated string
-      representation of the attribute value. But if
-      <function>BinaryTuples</function> is true, the value returned by
-      <function>GetValue</function> is the binary representation of
-      the type in the internal format of the backend server (but not
-      including the size word, if the field is variable-length). It is
-      then the programmer's responsibility to cast and convert the
-      data to the correct C type. The pointer returned by
-      <function>GetValue</function> points to storage that is part of
-      the <structname>PGresult</structname> structure. One should not
-      modify it, and one must explicitly copy the value into other
-      storage if it is to be used past the lifetime of the
-      <structname>PGresult</structname> structure itself.
-      <function>BinaryTuples</function> is not yet implemented.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>GetValue</function> returns a single field (column)
-      value of one tuple of a <structname>PGresult</structname>.
-      Tuple and field indices start at 0.
-<synopsis>
-const char *PgDatabase::GetValue(int tup_num, const char *field_name) const
-</synopsis>
-      For most queries, the value returned by
-      <function>GetValue</function> is a null-terminated string
-      representation of the attribute value. But if
-      <function>BinaryTuples</function> is true, the value returned by
-      <function>GetValue</function> is the binary representation of
-      the type in the internal format of the backend server (but not
-      including the size word, if the field is variable-length). It is
-      then the programmer's responsibility to cast and convert the
-      data to the correct C type. The pointer returned by
-      <function>GetValue</function> points to storage that is part of
-      the <structname>PGresult</structname> structure. One should not
-      modify it, and one must explicitly copy the value into other
-      storage if it is to be used past the lifetime of the
-      <structname>PGresult</structname> structure itself.
-      <function>BinaryTuples</function> is not yet implemented.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>GetLength</function> returns the length of a field
-      (column) in bytes. Tuple and field indices start at 0.
-<synopsis>
-int PgDatabase::GetLength(int tup_num, int field_num) const
-</synopsis>
-      This is the actual data length for the particular data value,
-      that is the size of the object pointed to by
-      <function>GetValue</function>. Note that for
-      character-represented values, this size has little to do with
-      the binary size reported by <function>PQfsize</function>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>GetLength</function> returns the length of a field
-      (column) in bytes. Tuple and field indices start at 0.
-<synopsis>
-int PgDatabase::GetLength(int tup_num, const char* field_name) const
-</synopsis>
-      This is the actual data length for the particular data value,
-      that is the size of the object pointed to by
-      <function>GetValue</function>. Note that for
-      character-represented values, this size has little to do with
-      the binary size reported by <function>PQfsize</function>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>GetIsNull</function>
-      returns whether a field has the null value.
-<synopsis>
-bool GetIsNull(int tup_num, int field_num) const
-</synopsis>
-      Note that <function>GetValue</function> will return the empty
-      string for null fields, not the NULL pointer.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>GetIsNull</function> returns whether a field has the
-      null value.
-<synopsis>
-bool GetIsNull(int tup_num, const char *field_name) const
-</synopsis>
-      Note that <function>GetValue</function> will return the empty
-      string for null fields, not the NULL pointer.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>DisplayTuples</function> prints out all the tuples
-      and, optionally, the attribute names to the specified output
-      stream.
-<synopsis>
-void PgDatabase::DisplayTuples(FILE *out = 0, bool fillAlign = true, 
-const char* fieldSep = "|", bool printHeader = true, bool quiet = false) const
-</synopsis>
-      This function is obsolescent.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>PrintTuples</function> prints out all the tuples and,
-      optionally, the attribute names to the specified output stream.
-<synopsis>
-void PgDatabase::PrintTuples(FILE *out = 0, bool printAttName = true, 
-bool terseOutput = false, bool fillAlign = false) const
-</synopsis>
-      This function is obsolescent.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect2>
-
-<sect2 id="libpqpp-exec-nonselect">
-  <title>Retrieving Non-SELECT Result Information</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      <function>CmdTuples</function> returns the number of rows
-      affected after an <command>INSERT</command>,
-      <command>UPDATE</command>, or <command>DELETE</command>.  If the
-      command was anything else, it returns -1.
-<synopsis>
-int PgDatabase::CmdTuples() const
-</synopsis>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <function>OidStatus</function>
-<synopsis>
-const char *PgDatabase::OidStatus() const
-</synopsis>
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect2>
-
- </sect1>
-
-  <sect1 id="libpqpp-notify">
-   <title>Asynchronous Notification</title>
-    
-   <para>
-    <productname>PostgreSQL</productname> supports asynchronous
-    notification via the <command>LISTEN</command> and
-    <command>NOTIFY</command> commands.  A backend registers its
-    interest in a particular notification condition with the
-    <command>LISTEN</command> command.  All backends that are
-    listening on a particular condition will be notified
-    asynchronously when a <command>NOTIFY</command> of that name is
-    executed by another backend.  No additional information is passed
-    from the notifier to the listener.  Thus, typically, any actual
-    data that needs to be communicated is transferred through a
-    relation.
-   </para>
-
-   <para>
-    <application>libpq++</application> applications are notified whenever a 
-    connected backend has
-    received an asynchronous notification.  However, the communication from
-    the backend to the frontend is not asynchronous.  
-    The <application>libpq++</application> application
-    must poll the backend to see if there is any pending notification
-    information.  After the execution of a command, a frontend may call 
-    <function>PgDatabase::Notifies</function>
-    to see if any notification data is currently available from the backend. 
-    <function>PgDatabase::Notifies</function>
-    returns the notification from a list of unhandled notifications from the
-    backend. The function returns <symbol>NULL</symbol> if there are no pending notifications 
-    from the backend.   
-    <function>PgDatabase::Notifies</function>
-    behaves like the popping of a stack.  Once a notification is returned
-    from <function>PgDatabase::Notifies</function>,
-    it is considered handled and will be removed from the list of
-    notifications.
-    
-    <itemizedlist>
-     <listitem>
-      <para>
-       <function>PgDatabase::Notifies</function>
-       retrieves pending notifications from the server.
-       
-<synopsis>
-PGnotify* PgDatabase::Notifies()
-</synopsis>
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-   <para>
-    The second sample program gives an example of the use of asynchronous
-    notification.
-   </para>
-  </sect1>
-
-  <sect1 id="libpqpp-copy">
-   <title>Functions Associated with the COPY Command</title>
-   
-   <para>
-    The <command>COPY</command> command in <productname>PostgreSQL</productname> 
-    has options to read from or write to the network
-    connection used by <application>libpq++</application>.  
-    Therefore, functions are necessary to
-    access this network connection directly so applications may take full
-    advantage of this capability.
-    
-    <itemizedlist>
-     <listitem>
-      <para>
-       <function>PgDatabase::GetLine</function>
-       reads a newline-terminated line of characters (transmitted by the
-       backend server) into a buffer 
-       <replaceable class="parameter">string</replaceable>
-       of size <replaceable class="parameter">length</replaceable>.
-<synopsis>
-int PgDatabase::GetLine(char* string, int length)
-</synopsis>
-      </para>
-
-      <para>
-       Like the Unix system routine
-       <function>fgets()</function>,
-       this routine copies up to 
-       <literal><replaceable class="parameter">length</replaceable>-1</literal>
-       characters into 
-       <replaceable class="parameter">string</replaceable>.
-       It is like 
-       <function>gets()</function>,
-       however, in that it converts the terminating newline into a zero byte.
-      </para>
-      <para>
-       <function>PgDatabase::GetLine</function>
-       returns <symbol>EOF</symbol> at end of file, 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>
-       Notice that the application must check to see if a new line consists
-       of a backslash followed by a period (<literal>\.</>), which indicates
-       that the backend
-       server has finished sending the results of the 
-       <command>COPY</command>.
-       Therefore, if the application ever expects to receive lines
-       that are more than
-       <literal><replaceable class="parameter">length</replaceable>-1</literal>
-       characters long, the application must be sure to check the return
-       value of <function>PgDatabase::GetLine</function> very carefully.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <function>PgDatabase::PutLine</function>
-       Sends a null-terminated <replaceable class="parameter">string</replaceable>
-       to the backend server.
-<synopsis>
-void PgDatabase::PutLine(char* string)
-</synopsis>
-      </para>
-      <para>
-       The application must explicitly send the characters <literal>\.</literal>
-       to indicate to the backend that it has finished sending its data.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       <function>PgDatabase::EndCopy</function>
-       synchronizes with the backend.
-<synopsis>
-int PgDatabase::EndCopy()
-</synopsis>
-       This function waits until the backend has
-       finished processing the <command>COPY</command>.
-       It should either be issued when the
-       last string has been sent to the backend using
-       <function>PgDatabase::PutLine</function>
-       or when the last string has been received from the backend using
-       <function>PgDatabase::GetLine</function>.
-       It must be issued or the backend may get <quote>out of sync</quote> with
-       the frontend.  Upon return from this function, the backend is ready to
-       receive the next command.
-      </para>	    
-      <para>
-       The return value is 0 on successful completion, nonzero otherwise.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    As an example:
-    
-<programlisting>
-PgDatabase data;
-data.Exec("CREATE TABLE foo (a int4, b char(16), d double precision)");
-data.Exec("COPY foo FROM STDIN");
-data.PutLine("3\tHello World\t4.5\n");
-data.PutLine("4\tGoodbye World\t7.11\n");
-...
-data.PutLine("\\.\n");
-data.EndCopy();
-</programlisting>
-   </para>
-  </sect1>
-
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
deleted file mode 100644
index 1fb6519806a..00000000000
--- a/doc/src/sgml/libpq.sgml
+++ /dev/null
@@ -1,2738 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.90 2002/03/22 19:20:13 petere Exp $
--->
-
- <chapter id="libpq">
-  <title><application>libpq</application> - C Library</title>
-
-  <indexterm zone="libpq">
-   <primary>libpq</primary>
-  </indexterm>
-
- <sect1 id="libpq-intro">
-  <title>Introduction</title>
-
-  <para>
-   <application>libpq</application> is the <acronym>C</acronym>
-   application programmer's interface to
-   <productname>PostgreSQL</productname>.  <application>libpq</application> is a set
-   of library routines that allow client programs to pass queries to the
-   <productname>PostgreSQL</productname> backend server and to receive the
-   results of these queries.  <application>libpq</application> is also the
-   underlying engine for several other <productname>PostgreSQL</productname>
-   application interfaces, including <application>libpq++</application> (C++),
-   <filename>libpgtcl</filename> (Tcl), <productname>Perl</productname>, and
-   <filename>ecpg</filename>.  So some aspects of <application>libpq</>'s behavior will be
-   important to you if you use one of those packages.
-  </para>
-
-  <para>
-   Three short programs are included at the end of this section to show how
-   to write programs that use <filename>libpq</filename>.  There are several
-   complete examples of <filename>libpq</filename> applications in the
-   following directories:
-
-   <simplelist>
-    <member><filename>src/test/examples</filename></member>
-    <member><filename>src/bin/psql</filename></member>
-   </simplelist>
-  </para>
-
-  <para>
-   Frontend programs that use <filename>libpq</filename> must include the
-   header file <filename>libpq-fe.h</filename> and must link with the
-   <filename>libpq</filename> library.
-  </para>
- </sect1>
-
- <sect1 id="libpq-connect">
-  <title>Database Connection Functions</title>
-
-  <para>
-   The following routines deal with making a connection to a
-   <productname>PostgreSQL</productname> backend server.  The
-   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</> object which is obtained from
-   <function>PQconnectdb</> 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.
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       <function>PQconnectdb</function> 
-       Makes a new connection to the database server.
-       <synopsis>
-PGconn *PQconnectdb(const char *conninfo)
-       </synopsis>
-
-   This routine opens a new database connection using the parameters taken
-   from the string <literal>conninfo</literal>.  Unlike <function>PQsetdbLogin</> below,
-   the parameter set can be extended without changing the function signature,
-   so use either of this routine or the nonblocking analogues <function>PQconnectStart</>
-   and <function>PQconnectPoll</function> is preferred for application programming.  The passed string
-   can be empty to use all default parameters, or it can contain one or more
-   parameter settings separated by whitespace.
-   </para>
-
-   <para>
-   Each parameter setting is in the form <literal>keyword = value</literal>.
-   (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, e.g., <literal>\'</literal> or <literal>\\</literal>.)
-   Spaces around the equal sign are optional.  The currently recognized
-   parameter keywords are:
-
-   <variablelist>
-    <varlistentry>
-     <term><literal>host</literal></term>
-     <listitem>
-     <para>
-      Name of host to connect to. 
-      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 is to connect to a Unix-domain socket in
-      <filename>/tmp</filename>.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>hostaddr</literal></term>
-     <listitem>
-     <para>
-      IP address of host to connect to. This should be in standard
-      numbers-and-dots form, as used by the BSD functions <function>inet_aton</> et al. If
-      a nonzero-length string is specified, TCP/IP communication is used.
-     </para>
-     <para>
-      Using <literal>hostaddr</> instead of host allows the application to avoid a host
-      name look-up, which may be important in applications with time
-      constraints. However, Kerberos authentication requires the host
-      name. The following therefore applies. If host is specified without
-      <literal>hostaddr</>, a host name lookup is forced. If <literal>hostaddr</> is specified without
-      host, the value for <literal>hostaddr</> gives the remote address; if Kerberos is
-      used, this causes a reverse name query. If both host and <literal>hostaddr</> are
-      specified, the value for <literal>hostaddr</> gives the remote address; the value
-      for host is ignored, unless Kerberos is used, in which case that value
-      is used for Kerberos authentication. Note that authentication is likely
-      to fail if <application>libpq</application> is passed a host name that is not the name of the
-      machine at <literal>hostaddr</>.
-     </para>
-     <para>
-      Without either a host name or host address, <application>libpq</application> will connect using a
-      local Unix domain socket.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <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.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>dbname</literal></term>
-     <listitem>
-     <para>
-      The database name.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>user</literal></term> 
-     <listitem>
-     <para>
-      User name to connect as.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>password</literal></term>
-     <listitem>
-     <para>
-      Password to be used if the server demands password authentication.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>options</literal></term>
-     <listitem>
-      <para>
-       Trace/debug options to be sent to the server.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>tty</literal></term>
-     <listitem>
-     <para>
-      A file or <acronym>tty</acronym> for optional debug output from the backend.
-     </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><literal>requiressl</literal></term>
-     <listitem>
-     <para>
-      Set to 1 to require SSL connection to the backend. <application>Libpq</>
-      will then refuse to connect if the server does not support
-      SSL. Set to 0 (default) to negotiate with server.
-     </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 hardwired defaults are used.
-   The return value is a pointer to an abstract struct
-   representing the connection to the backend.
-   </para>
-  </listitem>
-
-  <listitem>
-   <para>
-   <function>PQsetdbLogin</function>
-       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>
-
-   This is the predecessor of <function>PQconnectdb</function> with a fixed number
-   of parameters but the same functionality.   
-   </para>
-  </listitem>
-
-  <listitem>
-   <para>
-   <function>PQsetdb</function> Makes a new connection to the database server.
-<synopsis>
-PGconn *PQsetdb(char *pghost,
-                char *pgport,
-                char *pgoptions,
-                char *pgtty,
-                char *dbName)
-</synopsis>
-   This is a macro that calls <function>PQsetdbLogin</function> with null pointers
-   for the <parameter>login</> and <parameter>pwd</> parameters.  It is provided primarily
-   for backward compatibility with old programs.
-   </para>
-  </listitem>
-
- <listitem>
-  <para>
-   <function>PQconnectStart</function>,
-   <function>PQconnectPoll</function>
-   <indexterm><primary>nonblocking connection</primary></indexterm>
-   Make a connection to the database server in a nonblocking manner.
-<synopsis>
-PGconn *PQconnectStart(const char *conninfo)
-</synopsis>
-<synopsis>
-PostgresPollingStatusType PQconnectPoll(PGconn *conn)
-</synopsis>
-   These two routines 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.
-  </para>
-  <para>
-   The database connection is made using the parameters taken from the string
-   <literal>conninfo</literal>, passed to <function>PQconnectStart</function>. This string is in
-   the same format as described above for <function>PQconnectdb</function>.
-  </para>
-  <para>
-   Neither <function>PQconnectStart</function> nor <function>PQconnectPoll</function> will block, as 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>PQconnectdb</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 for yourself that the socket is in the appropriate state
-      before calling <function>PQconnectPoll</function>, as described below.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   To begin, 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 status 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 may
-   proceed with the connection sequence.  Loop thus: Consider a connection
-   <quote>inactive</quote> by default. If <function>PQconnectPoll</function> last returned <symbol>PGRES_POLLING_ACTIVE</>,
-   consider it <quote>active</quote> instead. If <function>PQconnectPoll(conn)</function> last returned
-   <symbol>PGRES_POLLING_READING</symbol>, perform a <function>select()</> for reading on <function>PQsocket(conn)</function>. If
-   it last returned <symbol>PGRES_POLLING_WRITING</symbol>, perform a <function>select()</> for writing on
-   <function>PQsocket(conn)</function>. If you have yet to call <function>PQconnectPoll</function>, i.e. after the call
-   to <function>PQconnectStart</function>, behave as if it last returned <symbol>PGRES_POLLING_WRITING</symbol>.  If
-   the <function>select()</> shows that the socket is ready, consider it <quote>active</quote>. If it has
-   been decided that this connection is <quote>active</quote>, call <function>PQconnectPoll(conn)</function>
-   again. If this call returns <symbol>PGRES_POLLING_FAILED</symbol>, the connection procedure
-   has failed.  If this call returns <symbol>PGRES_POLLING_OK</symbol>, the connection has been
-   successfully made.
-  </para>
-
-  <para>
-    Note that the use of <function>select()</function> to ensure that the socket is ready is merely
-    a (likely) example; those with other facilities available, such as a
-    <function>poll()</function> call, may of course use that instead.
-  </para>
-
-  <para>
-    At any time during connection, the status of the connection may be
-    checked, by calling <function>PQstatus</>. If this is <symbol>CONNECTION_BAD</>, then the
-    connection procedure has failed; if this is <function>CONNECTION_OK</>, then the
-    connection is ready.  Either of these states should be equally detectable
-    from the return value of <function>PQconnectPoll</>, as above. Other states may be
-    shown during (and only during) an asynchronous connection procedure. These
-    indicate the current stage of the connection procedure, and may be useful
-    to provide feedback to the user for example. These statuses may include:
-
-    <variablelist>
-     <varlistentry>
-      <term><symbol>CONNECTION_STARTED</symbol></term>
-      <listitem>
-       <para>
-        Waiting for connection to be made.
-       </para>
-      </listitem>
-     </varlistentry> 
-
-     <varlistentry>
-      <term><symbol>CONNECTION_MADE</symbol></term>
-      <listitem>
-       <para>
-        Connection OK; waiting to send.
-       </para>
-      </listitem>
-     </varlistentry>  
-
-     <varlistentry>
-      <term><symbol>CONNECTION_AWAITING_RESPONSE</symbol></term>
-      <listitem>
-       <para>
-        Waiting for a response from the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><symbol>CONNECTION_AUTH_OK</symbol></term>
-      <listitem>
-       <para>
-        Received authentication; waiting for connection start-up to continue.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><symbol>CONNECTION_SETENV</symbol></term>
-
-      <listitem>
-       <para>
-        Negotiating environment (part of the connection start-up).
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    Note that, although these constants will remain (in order to maintain
-    compatibility), an application should never rely upon these appearing in a
-    particular order, or at all, or on the status always being one of these
-    documented values. An application may 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>
-   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 a
-   call to <function>PQconnectStart</function> or <function>PQconnectPoll</function> failed.
-  </para>
-
-  <para>
-   <function>PQconnectPoll</function> will currently block if
-   <application>libpq</> is compiled with <symbol>USE_SSL</symbol>
-   defined. This restriction may be removed in the future.
-  </para>
-
-  <para>
-   These functions leave the socket in a nonblocking state as if 
-   <function>PQsetnonblocking</function> had been called.
-  </para>
- </listitem>
-
-  <listitem>
-   <para>
-   <function>PQconndefaults</function> Returns the default connection options.
-<synopsis>
-PQconninfoOption *PQconndefaults(void)
-
-struct PQconninfoOption
-{
-    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;  /* Character to display for 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 */
-}
-</synopsis>
-   Returns a connection options array.  This may
-   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> structs, which ends with an entry having a NULL
-   keyword pointer.  Note that the 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>
-
-   <para>
-    In <productname>PostgreSQL</productname> versions before 7.0, <function>PQconndefaults</function> returned a pointer
-    to a static array, rather than a dynamically allocated array.  That
-    was not thread-safe, so the behavior has been changed.
-   </para>
-  </listitem>
-
-  <listitem>
-   <para>
-   <function>PQfinish</function>
-   Close  the  connection to the backend.  Also frees
-   memory used by the <structname>PGconn</structname> object.
-<synopsis>
-void PQfinish(PGconn *conn)
-</synopsis>
-   Note that even if the backend 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 should not be used after <function>PQfinish</function> has been called.
-   </para>
-  </listitem>
-
-  <listitem>
-   <para>
-   <function>PQreset</function>
-   Reset the communication  port  with  the  backend.
-<synopsis>
-void PQreset(PGconn *conn)
-</synopsis>
-   This function will close the connection
-   to the backend and attempt to  reestablish  a  new
-   connection to the same server, using all the same
-   parameters previously used.  This may be useful for
-   error recovery if a working connection is lost.
-   </para>
-  </listitem>
-
-  <listitem>
-   <para>
-   <function>PQresetStart</function>
-   <function>PQresetPoll</function>
-   Reset the communication  port  with  the  backend, in a nonblocking manner.
-<synopsis>
-int PQresetStart(PGconn *conn);
-</synopsis>
-<synopsis>
-PostgresPollingStatusType PQresetPoll(PGconn *conn);
-</synopsis>
-    These functions will close the connection to the backend and attempt to
-    reestablish a new connection to the same server, using all the same
-    parameters previously used. This may 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>PQconnectStart</> and <function>PQconnectPoll</>.
-   </para>
-   <para>
-    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>
-
- </itemizedlist>
-</para>
-
-<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 below to get
-at the contents of <structname>PGconn</structname>.  Avoid directly referencing the fields of the
-<structname>PGconn</> structure because they are subject to change in the future.
-(Beginning in <productname>PostgreSQL</productname> release 6.4, the
-definition of struct <structname>PGconn</structname> is not even provided in <filename>libpq-fe.h</filename>.
-If you have old code that accesses <structname>PGconn</structname> fields directly, you can keep using it
-by including <filename>libpq-int.h</filename> too, but you are encouraged to fix the code
-soon.)
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQdb</function>  
-         Returns the database name of the connection.
-<synopsis>
-char *PQdb(const PGconn *conn)
-</synopsis>
-<function>PQdb</> and the next several functions return the values established
-at connection.  These values are fixed for the life of the <structname>PGconn</>
-object.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQuser</function>
-         Returns the user name of the connection.
-<synopsis>
-char *PQuser(const PGconn *conn)
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQpass</function>
-         Returns the password of the connection.
-<synopsis>
-char *PQpass(const PGconn *conn)
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQhost</function>
-         Returns the server host name of the connection.
-<synopsis>
-char *PQhost(const PGconn *conn)
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQport</function>
-         Returns the port of the connection.
-<synopsis>
-char *PQport(const PGconn *conn)
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQtty</function>
-         Returns the debug <acronym>tty</acronym> of the connection.
-<synopsis>
-char *PQtty(const PGconn *conn)
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQoptions</function>
-       Returns the backend options used in  the  connection.
-<synopsis>
-char *PQoptions(const PGconn *conn)
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQstatus</function>
-         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> or
-       <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>PQconnectStart</> and <function>PQconnectPoll</> with regards
-       to other status codes
-       that might be seen.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>PQerrorMessage</function>
-       <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
-       <function>PQerrorMessage</function> if they fail.
-       Note that by <application>libpq</application> convention, a non-empty
-       <function>PQerrorMessage</function> will
-       include a trailing newline.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>PQbackendPID</function>
-       Returns the process <acronym>ID</acronym> of the backend server 
-      handling this connection.
-       <synopsis>
-int PQbackendPID(const PGconn *conn);
-       </synopsis>
-       The backend <acronym>PID</acronym> is useful for debugging
-       purposes and for comparison
-       to NOTIFY messages (which include the <acronym>PID</acronym> of
-       the notifying backend).
-       Note that the <acronym>PID</acronym> belongs to a process
-       executing on the database
-       server host, not the local host!
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       <function>PQgetssl</function>
-       <indexterm><primary>SSL</></>
-       Returns the SSL structure used in the connection, or NULL
-       if SSL is not in use. 
-       <synopsis>
-SSL *PQgetssl(const PGconn *conn);
-       </synopsis>
-       This structure can be used to verify encryption levels, check
-       server certificate and more. Refer to the SSL documentation
-       for information about this structure.
-      </para>
-      <para>
-       You must define <literal>USE_SSL</literal> in order to get the
-       prototype for this function. Doing this will also 
-       automatically include <filename>ssl.h</filename> from <productname>OpenSSL</productname>.
-      </para>
-     </listitem>
-
-    </itemizedlist>
-   </para>
-  </sect1>
-
-<sect1 id="libpq-exec">
-<title>Command Execution Functions</title>
-
-<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 Routines</title>
-<itemizedlist>
-<listitem>
-<para>
-<function>PQexec</function>
-          Submit a command to the server
-          and wait for the result.
-<synopsis>
-PGresult *PQexec(PGconn *conn,
-                 const char *query);
-</synopsis>
-          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 backend.
-          If a NULL is returned, it
-	  should be treated like a <symbol>PGRES_FATAL_ERROR</symbol> result.  Use
-	  <function>PQerrorMessage</function> to get more information about the error.
-</para>
-</listitem>
-</itemizedlist>
-
-<para>
-The <function>PGresult</function> structure encapsulates the result
-returned by the backend.
-<filename>libpq</filename> 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.
-(Beginning in <productname>PostgreSQL</productname> 6.4, the
-definition of struct <structname>PGresult</structname> is not even provided in <filename>libpq-fe.h</>.  If you
-have old code that accesses <structname>PGresult</structname> fields directly, you can keep using it
-by including <filename>libpq-int.h</filename> too, but you are encouraged to fix the code
-soon.)
-</para>
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQresultStatus</function>
-          Returns the result status of the command.
-<synopsis>
-ExecStatusType PQresultStatus(const PGresult *res)
-</synopsis>
-<function>PQresultStatus</function> can return one of the following values:
-
-<itemizedlist>
- <listitem>
-  <para><literal>PGRES_EMPTY_QUERY</literal> -- The string sent to the backend was empty.</para>
- </listitem>
- <listitem>
-  <para><literal>PGRES_COMMAND_OK</literal> -- Successful completion of a command returning no data</para>
- </listitem>
- <listitem>
-  <para><literal>PGRES_TUPLES_OK</literal> -- The query successfully executed</para>
- </listitem>
- <listitem>
-  <para><literal>PGRES_COPY_OUT</literal> -- Copy Out (from server) data transfer started</para>
- </listitem>
- <listitem>
-  <para><literal>PGRES_COPY_IN</literal> -- Copy In (to server) data transfer started</para>
- </listitem>
- <listitem>
-  <para><literal>PGRES_BAD_RESPONSE</literal> -- The server's response was not understood</para>
- </listitem>
- <listitem>
-  <para><literal>PGRES_NONFATAL_ERROR</literal></para>
- </listitem>
- <listitem>
-  <para><literal>PGRES_FATAL_ERROR</literal></para>
- </listitem>
-</itemizedlist>
-
-If  the result status is <literal>PGRES_TUPLES_OK</literal>, then the
-routines described below can be  used  to  retrieve  the
-rows returned by the query.  Note that a SELECT 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
-(INSERT, UPDATE, etc.). A response of <literal>PGRES_EMPTY_QUERY</literal> often
-exposes a bug in the client software.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQresStatus</function>
-	Converts the enumerated type returned by PQresultStatus into
-	a string constant describing the status code.
-<synopsis>
-char *PQresStatus(ExecStatusType status);
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQresultErrorMessage</function>
-returns the error message associated with the query, or an empty string
-if there was no error.
-<synopsis>
-char *PQresultErrorMessage(const PGresult *res);
-</synopsis>
-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>
-
-<listitem>
-<para>
-<function>PQclear</function>
-          Frees  the  storage  associated with the <structname>PGresult</structname>.
-          Every query result should be freed via <function>PQclear</function> when
-          it  is  no  longer needed.
-<synopsis>
-void PQclear(PQresult *res);
-</synopsis>
-          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 query,
-          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  the  frontend  application.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQmakeEmptyPGresult</function>
-          Constructs an empty <structname>PGresult</structname> object with the given status.
-<synopsis>
-PGresult* PQmakeEmptyPGresult(PGconn *conn, ExecStatusType status);
-</synopsis>
-This is <application>libpq</>'s internal routine to allocate and initialize an empty
-<structname>PGresult</structname> object.  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 status indicates an error,
-the connection's current errorMessage is copied into the <structname>PGresult.</structname>
-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>
-</itemizedlist>
-</sect2>
-
-<sect2 id="libpq-exec-escape-string">
-  <title>Escaping strings for inclusion in SQL queries</title>
-
-   <indexterm zone="libpq-exec-escape-string"><primary>escaping strings</></>
-
-<para>
-<function>PQescapeString</function>
-          Escapes a string for use within an SQL query.
-<synopsis>
-size_t PQescapeString (char *to, const char *from, size_t length);
-</synopsis>
-If you want to include strings that have been received
-from a source that is not trustworthy (for example, because a random user
-entered them), you cannot directly include them in SQL
-queries for security reasons.  Instead, you have to quote special
-characters that are otherwise interpreted by the SQL parser.
-</para>
-<para>
-<function>PQescapeString</> performs this operation.  The
-<parameter>from</> points to the first character of the string that
-is to be escaped, and the <parameter>length</> parameter counts the
-number of characters in this string (a terminating zero byte is
-neither necessary nor counted).  <parameter>to</> shall point to a
-buffer that is able to hold at least one more character than twice
-the value of <parameter>length</>, otherwise the behavior is
-undefined.  A call to <function>PQescapeString</> writes an escaped
-version of the <parameter>from</> string to the <parameter>to</>
-buffer, replacing special characters so that they cannot cause any
-harm, and adding a terminating zero byte.  The single quotes that
-must surround <productname>PostgreSQL</> string literals are not part of the result
-string.
-</para>
-<para>
-<function>PQescapeString</> returns the number of characters written
-to <parameter>to</>, not including the terminating zero byte.
-Behavior is undefined when the <parameter>to</> and <parameter>from</>
-strings overlap.
-</para>
-</sect2>
-
-
- <sect2 id="libpq-exec-escape-bytea">
-  <title>Escaping binary strings for inclusion in SQL queries</title>
-  <indexterm zone="libpq-exec-escape-bytea">
-   <primary>escaping binary strings</primary>
-  </indexterm>
-  <para>
-   <function>PQescapeBytea</function>
-   Escapes a binary string (<type>bytea</type> type) for use within an SQL query.
-   <synopsis>
-    unsigned char *PQescapeBytea(unsigned char *from,
-                                         size_t from_length,
-                                         size_t *to_length);
-   </synopsis>
-
-   Certain <acronym>ASCII</acronym> characters <emphasis>must</emphasis>
-   be escaped (but all characters <emphasis>may</emphasis> be escaped)
-   when used as part of a <type>bytea</type>
-   string literal in an <acronym>SQL</acronym> statement. In general, to
-   escape a character, it is converted into the three digit octal number
-   equal to the decimal <acronym>ASCII</acronym> value, and preceded by
-   two backslashes. The single quote (') and backslash (\) characters have
-   special alternate escape sequences. See the <citetitle>User's Guide</citetitle>
-   for more information. <function>PQescapeBytea
-   </function> performs this operation, escaping only the minimally
-   required characters.
-  </para>
-
-  <para>
-   The <parameter>from</parameter> parameter points to the first
-   character of the string that is to be escaped, and the
-   <parameter>from_length</parameter> parameter reflects the number of
-   characters in this binary string (a terminating zero byte is
-   neither necessary nor counted).  The <parameter>to_length</parameter>
-   parameter shall point to a buffer suitable to hold the resultant
-   escaped string length. The result string length does not
-   include the terminating zero byte of the result.
-  </para>
-
-  <para>
-   <function>PQescapeBytea</> returns an escaped version of the
-   <parameter>from</parameter> parameter binary string, to a caller-provided
-    buffer. The return string has all special characters replaced
-   so that they can be properly processed by the PostgreSQL string literal
-   parser, and the <type>bytea</type> input function. A terminating zero
-   byte is also added.  The single quotes that must surround
-   PostgreSQL string literals are not part of the result string.
-  </para>
-
-  <para>
-   <function>PQunescapeBytea</function>
-   Converts an escaped string representation of binary data into binary
-   data - the reverse of <function>PQescapeBytea</function>.
-   <synopsis>
-    unsigned char *PQunescapeBytea(unsigned char *from, size_t *to_length);
-   </synopsis>
-
-   The <parameter>from</parameter> parameter points to an escaped string
-   such as might be returned by <function>PQgetvalue</function> of a
-   <type>BYTEA</type> column. <function>PQunescapeBytea</function> converts
-   this NUL terminated string representation into binary, filling a buffer.
-   It returns a pointer to the buffer which is NULL on error, and the size
-   of the buffer in <parameter>to_length</parameter>. The pointer may
-   subsequently be used as an argument to the function
-   <function>free(3)</function>.
-  </para>
-   
- </sect2>
-
-
-<sect2 id="libpq-exec-select-info">
-  <title>Retrieving SELECT Result Information</title>
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQntuples</function>
-          Returns the number of tuples (rows)
-          in the query result.
-<synopsis>
-int PQntuples(const PGresult *res);
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQnfields</function>
-          Returns   the   number    of    fields
-          (columns) in each row of the query result.
-<synopsis>
-int PQnfields(const PGresult *res);
-</synopsis>
-</para>
-</listitem>
-
-
-<listitem>
-<para>
-<function>PQfname</function>
- Returns the field (column) name associated with the given field index.
- Field  indices start at 0.
-<synopsis>
-char *PQfname(const PGresult *res,
-                    int field_index);
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQfnumber</function>
-            Returns  the  field  (column)  index
-          associated with the given field name.
-<synopsis>
-int PQfnumber(const PGresult *res,
-              const char *field_name);
-</synopsis>
-</para>
-
-<para>
-        -1 is returned if the given name does not match any field.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQftype</function>
-            Returns the field type associated with the
-          given  field  index.  The  integer  returned is an
-          internal coding of the type.  Field indices  start
-          at 0.
-<synopsis>
-Oid PQftype(const PGresult *res,
-            int field_index);
-</synopsis>
-You can query the system table <literal>pg_type</literal> to obtain
-the name and properties of the various data types. The <acronym>OID</acronym>s
-of the built-in data types are defined in <filename>src/include/catalog/pg_type.h</filename>
-in the source tree.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQfmod</function>
-          Returns  the type-specific modification data of the field
-          associated with the given field index.
-          Field indices start at 0.
-<synopsis>
-int PQfmod(const PGresult *res,
-           int field_index);
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQfsize</function>
-          Returns  the  size  in bytes of the field
-          associated with the given field index.
-          Field indices start at 0.
-<synopsis>
-int PQfsize(const PGresult *res,
-            int field_index);
-</synopsis>
-	<function>PQfsize</> returns the space allocated for this field in a database
-	tuple, in other words the size of the server's binary representation
-	of the data type.  -1 is returned if the field is variable size.
-</para>
-
-</listitem>
-
-<listitem>
-<para>
-<function>PQbinaryTuples</function>
-          Returns 1 if the PGresult contains binary tuple data,
-	  0 if it contains ASCII data.
-<synopsis>
-int PQbinaryTuples(const PGresult *res);
-</synopsis>
-Currently, binary tuple data can only be returned by a query that
-extracts data from a binary cursor.
-</para>
-</listitem>
-</itemizedlist>
-</sect2>
-
-<sect2 id="libpq-exec-select-values">
-  <title>Retrieving SELECT Result Values</title>
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQgetvalue</function>
-            Returns a single field  (column)  value of one tuple (row)
-	    of a <structname>PGresult</structname>.
-	    Tuple and field indices start at 0.
-<synopsis>
-char* PQgetvalue(const PGresult *res,
-                 int tup_num,
-                 int field_num);
-</synopsis>
-For most queries, the value returned by <function>PQgetvalue</function>
-is a null-terminated character string  representation
-of the attribute value.  But if <function>PQbinaryTuples()</function> is 1,
-the  value  returned  by <function>PQgetvalue</function>  is  the  binary
-representation of the
-type in the internal format of the backend server
-(but not including the size word, if the field is variable-length).
-It  is then the programmer's responsibility to cast and
-convert the data to the correct C type.  The pointer
-returned  by  <function>PQgetvalue</function> points to storage that is
-part of the <structname>PGresult</structname> structure.  One should not modify it,
-and one must explicitly 
-copy the value into other storage if it is to
-be used past the lifetime of the  <structname>PGresult</structname>  structure itself.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQgetisnull</function>
-           Tests a field for a NULL entry.
-           Tuple and field indices start at 0.
-<synopsis>
-int PQgetisnull(const PGresult *res,
-                int tup_num,
-                int field_num);
-</synopsis>
-            This function returns  1 if the field contains a NULL, 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>
-
-<listitem>
-<para>
-<function>PQgetlength</function>
-          Returns   the   length  of  a  field (attribute) value in bytes.
-          Tuple and field indices start at 0.
-<synopsis>
-int PQgetlength(const PGresult *res,
-                int tup_num,
-                int field_num);
-</synopsis>
-This is the actual data length for the particular data value, that is the
-size of the object pointed to by <function>PQgetvalue</function>.  Note that for character-represented
-values, this size has little to do with the binary size reported by <function>PQfsize</function>.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQprint</function>
-          Prints out all the  tuples  and,  optionally,  the
-          attribute  names  to  the specified output stream.
-       <synopsis>
-void PQprint(FILE* fout,      /* output stream */
-             const PGresult *res,
-             const PQprintOpt *po);
-
-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;   /* insert to HTML <replaceable>table ...</replaceable> */
-    char    *caption;    /* HTML <replaceable>caption</replaceable> */
-    char    **fieldName; /* null terminated array of replacement field names */
-} PQprintOpt;
-       </synopsis>
-This function was formerly used by <application>psql</application>
-to print query results, but this is no longer the case and this
-function is no longer actively supported.
-</para>
-</listitem>
-</itemizedlist>
-</sect2>
-
-<sect2 id="libpq-exec-nonselect">
-  <title>Retrieving Non-SELECT Result Information</title>
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQcmdStatus</function>
-          Returns the command status string from the SQL command that
-	  generated the <structname>PGresult</structname>.
-<synopsis>
-char * PQcmdStatus(const PGresult *res);
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQcmdTuples</function>
-	  Returns the number of rows affected by the SQL command.
-<synopsis>
-char * PQcmdTuples(const PGresult *res);
-</synopsis>
-          If the <acronym>SQL</acronym> command that generated the
-	  <structname>PGresult</structname> was INSERT, UPDATE or DELETE, this returns a
-	  string containing the number of rows affected.  If the
-          command was anything else, it returns the empty string.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQoidValue</function>
-          Returns the object ID of the inserted row, if the
-	  <acronym>SQL</acronym> command was an INSERT
-	  that inserted exactly one row into a table that has OIDs.
-          Otherwise, returns <literal>InvalidOid</literal>.
-<synopsis>
-Oid PQoidValue(const PGresult *res);
-</synopsis>
-          The type <type>Oid</type> and the constant <literal>InvalidOid</literal>
-          will be defined if you include the <application>libpq</application>
-          header file. They will both be some integer type.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQoidStatus</function>
-          Returns a string with the object ID of the inserted row, if the
-	  <acronym>SQL</acronym> command was an INSERT.
-	  (The string will be <literal>0</> if the INSERT did not insert exactly one
-	  row, or if the target table does not have OIDs.)  If the command
-	  was not an INSERT, returns an empty string.
-<synopsis>
-char * PQoidStatus(const PGresult *res);
-</synopsis>
-This function is deprecated in favor of <function>PQoidValue</function>
-and is not thread-safe.
-</para>
-</listitem>
-</itemizedlist>
-
-</sect2>
-</sect1>
-
-<sect1 id="libpq-async">
-<title>Asynchronous Query Processing</title>
-
-  <indexterm zone="libpq-async"><primary>nonblocking connection</></>
-
-<para>
-The <function>PQexec</function> function is adequate for submitting commands in
-simple synchronous
-applications.  It has a couple of major deficiencies however:
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQexec</function> waits for the command to be completed.  The application may 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 control is buried inside <function>PQexec</function>, it is hard for the frontend
-to decide 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>.
-</para>
-<para>
-Older programs that used this functionality as well as 
-<function>PQputline</function> and <function>PQputnbytes</function>
-could block waiting to send data to the backend. To
-address that issue, the function <function>PQsetnonblocking</function>
-was added.
-</para>
-<para>
-Old applications can neglect to use <function>PQsetnonblocking</function>
-and get the older potentially blocking behavior.  Newer programs can use 
-<function>PQsetnonblocking</function> to achieve a completely nonblocking
-connection to the backend.
-
-<itemizedlist>
- <listitem>
-   <para>
-    <function>PQsetnonblocking</function> Sets the nonblocking status of the
-    connection.
-<synopsis>
-int PQsetnonblocking(PGconn *conn, int arg)
-</synopsis>
-    Sets the state of the connection to nonblocking if <parameter>arg</parameter> is 1,
-    blocking if <parameter>arg</parameter> is 0.  Returns 0 if OK, -1 if error.
-   </para>
-   <para>
-    In the nonblocking state, calls to
-    <function>PQputline</function>, <function>PQputnbytes</function>,
-    <function>PQsendQuery</function> and <function>PQendcopy</function>
-    will not block but instead return an error if they need to be called
-    again.
-   </para>
-   <para>
-    When a database connection has been set to nonblocking mode and
-    <function>PQexec</function> is called, it will temporarily set the state
-    of the connection to blocking until the <function>PQexec</function> 
-    completes. 
-   </para>
-   <para>
-    More of <application>libpq</application> is expected to be made safe for 
-    <function>PQsetnonblocking</function> functionality in the near future.
-  </para>
- </listitem>
-
-<listitem>
-<para>
-<function>PQisnonblocking</function>
-       Returns the blocking status of the database connection.
-<synopsis>
-int PQisnonblocking(const PGconn *conn)
-</synopsis>
-       Returns 1 if the connection is set to nonblocking mode,
-       0 if blocking.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQsendQuery</function>
-          Submit a command to the server without
-	  waiting for the result(s).  1 is returned if the command was
-	  successfully dispatched, 0 if not (in which case, use
-	  <function>PQerrorMessage</> to get more information about the failure).
-<synopsis>
-int PQsendQuery(PGconn *conn,
-                const char *query);
-</synopsis>
-	  After successfully calling <function>PQsendQuery</function>, call
-          <function>PQgetResult</function> one or more
-	  times to obtain the results.  <function>PQsendQuery</function> may not be called
-	  again (on the same connection) until <function>PQgetResult</function> has returned NULL,
-	  indicating that the command is done.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQgetResult</function>
-          Wait for the next result from a prior <function>PQsendQuery</function>,
-	  and return it.  NULL is returned when the query is complete
-	  and there will be no more results.
-<synopsis>
-PGresult *PQgetResult(PGconn *conn);
-</synopsis>
-	  <function>PQgetResult</function> must be called repeatedly until it returns NULL,
-	  indicating that the command is done.  (If called when no command is
-	  active, <function>PQgetResult</function> will just return NULL at once.)
-	  Each non-NULL result from <function>PQgetResult</function> should be processed using
-	  the same 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 query is active and the
-	  necessary response data has not yet been read by <function>PQconsumeInput</function>.
-</para>
-</listitem>
-
-</itemizedlist>
-</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 frontend can be handling the
-results of one query while the backend is still working on later
-queries in the same command string.)  However, calling <function>PQgetResult</function> will
-still cause the frontend to block until the backend completes the
-next <acronym>SQL</acronym> command.  This can be avoided by proper use of three more
-functions:
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQconsumeInput</function>
-	  If input is available from the backend, consume it.
-<synopsis>
-int PQconsumeInput(PGconn *conn);
-</synopsis>
-<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> is set).  Note that the result does not say
-whether any input data was actually collected. After calling
-<function>PQconsumeInput</function>, the application may check
-<function>PQisBusy</function> and/or <function>PQnotifies</function> to see if
-their state has changed.
-</para>
-<para>
-<function>PQconsumeInput</function> may be called even if the application is not
-prepared to deal with a result or notification just yet.  The
-routine 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>
-
-<listitem>
-<para>
-<function>PQisBusy</function>
-Returns 1 if a query 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>
-<function>PQisBusy</function> will not itself attempt to read data from the backend;
-therefore <function>PQconsumeInput</function> must be invoked first, or the busy
-state will never end.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQflush</function> Attempt to flush any data queued to the backend,
-returns 0 if successful (or if the send queue is empty) or <symbol>EOF</symbol> if it failed for
-some reason.
-<synopsis>
-int PQflush(PGconn *conn);
-</synopsis>
-<function>PQflush</function> needs to be called on a nonblocking connection 
-before calling <function>select()</function> to determine if a response has
-arrived.  If 0 is returned it ensures that there is no data queued to the 
-backend that has not actually been sent.  Only applications that have used
-<function>PQsetnonblocking</function> have a need for this.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQsocket</function>
-	  Obtain the file descriptor number for the backend connection socket.
-	  A valid descriptor will be &gt;= 0; a result of -1 indicates that
-	  no backend connection is currently open.
-<synopsis>
-int PQsocket(const PGconn *conn);
-</synopsis>
-<function>PQsocket</function> should be used to obtain the backend socket descriptor
-in preparation for executing <function>select()</function>.  This allows an
-application using a blocking connection to wait for either backend responses or
-other conditions.
-If the result of <function>select()</function> indicates that data can be read from
-the backend socket, then <function>PQconsumeInput</function> should be called to read the
-data; after which, <function>PQisBusy</function>, <function>PQgetResult</function>,
-and/or <function>PQnotifies</function> can be used to process the response.
-</para>
-<para>
-Nonblocking connections (that have used <function>PQsetnonblocking</function>)
-should not use <function>select()</function> until <function>PQflush</function>
-has returned 0 indicating that there is no buffered data waiting to be sent
-to the backend.
-</para>
-</listitem>
-
-</itemizedlist>
-</para>
-
-<para>
-A typical frontend using these functions will have a main loop that uses
-<function>select</function> to wait for all the conditions that it must
-respond to.  One of the conditions will be input available from the backend,
-which in <function>select</function>'s terms is 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 NOTIFY messages (see <xref linkend="libpq-notify">).
-</para>
-
-<para>
-A frontend that uses <function>PQsendQuery</function>/<function>PQgetResult</function>
-can also attempt to cancel a command that is still being processed by the backend.
-</para>
-
-<para>
-<itemizedlist>
-<listitem>
-<para>
-<function>PQrequestCancel</function>
-	  Request that <productname>PostgreSQL</productname> abandon
-	  processing of the current command.
-<synopsis>
-int PQrequestCancel(PGconn *conn);
-</synopsis>
-The return value is 1 if the cancel request was successfully
-dispatched, 0 if not.  (If not, <function>PQerrorMessage</function> tells why not.)
-Successful dispatch is no guarantee that the request will have any
-effect, however.  Regardless of the return value of <function>PQrequestCancel</function>,
-the application must continue with the normal result-reading
-sequence using <function>PQgetResult</function>.  If the cancellation
-is effective, the current command will terminate early and return
-an error result.  If the cancellation fails (say, because the
-backend was already done processing the command), then there will
-be no visible result at all.
-</para>
-</listitem>
-</itemizedlist>
-</para>
-
-<para>
-Note that if the current command is part of a transaction, cancellation
-will abort the whole transaction.
-</para>
-
-<para>
-<function>PQrequestCancel</function> can safely be invoked from a signal handler.
-So, it is also possible to use it in conjunction with plain
-<function>PQexec</function>, if the decision to cancel can be made in a signal
-handler.  For example, <application>psql</application> invokes
-<function>PQrequestCancel</function> from a <systemitem>SIGINT</> signal handler, thus allowing
-interactive cancellation of queries that it issues through <function>PQexec</function>.
-Note that <function>PQrequestCancel</function> will have no effect if the connection
-is not currently open or the backend is not currently processing a command.
-</para>
-
-</sect1>
-
-<sect1 id="libpq-fastpath">
-<title>The Fast-Path Interface</title>
-
-<para>
-<productname>PostgreSQL</productname> provides a fast-path interface to send
-function calls to the backend.  This is a trapdoor into system internals and
-can be a potential security hole.  Most users will not need this feature.
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQfn</function>
-	Request execution of a backend 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);
-</synopsis>
-     The <parameter>fnid</> argument is the object identifier of the function to be
-     executed.
-     <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 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
-     tells <application>libpq</> to byte-swap the value if necessary, so that it is
-     delivered as a proper int value for the client machine.  When
-     <parameter>result_is_int</> is 0, the byte string sent by the backend is returned
-     unmodified.)
-     <parameter>args</> and <parameter>nargs</> specify the arguments to be passed to the function.
-<synopsis>
-typedef struct {
-    int len;
-    int isint;
-    union {
-        int *ptr;
-        int integer;
-    } u;
-} PQArgBlock;
-</synopsis>
-     <function>PQfn</function> always returns a valid <structname>PGresult*</structname>. The resultStatus
-     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>
-</listitem>
-</itemizedlist>
-</para>
-
-</sect1>
-
-<sect1 id="libpq-notify">
-<title>Asynchronous Notification</title>
-
-  <indexterm zone="libpq-notify"><primary>NOTIFY</primary></indexterm>
-
-<para>
-<productname>PostgreSQL</productname> supports asynchronous notification via the
-<command>LISTEN</command> and <command>NOTIFY</command> commands.  A backend registers its interest in a particular
-notification condition with the <command>LISTEN</command> command (and can stop listening
-with the <command>UNLISTEN</command> command).  All backends listening on a
-particular condition will be notified asynchronously when a <command>NOTIFY</command> of that
-condition name is executed by any backend.  No additional information is
-passed from the notifier to the listener.  Thus, typically, any actual data
-that needs to be communicated is transferred through a database relation.
-Commonly the condition name is the same as the associated relation, but it is
-not necessary for there to be any associated relation.
-</para>
-
-<para>
-<filename>libpq</filename> applications submit <command>LISTEN</command> and <command>UNLISTEN</command>
-commands as ordinary SQL command.  Subsequently, arrival of <command>NOTIFY</command>
-messages can be detected by calling <function>PQnotifies</function>.
-
-<itemizedlist>
-<listitem>
-<para>
-<function>PQnotifies</function>
-          Returns  the next notification from a list of unhandled
-          notification messages received from the backend.  Returns NULL if
-          there are no pending notifications.  Once a notification is
-	  returned from PQnotifies, it is considered handled and will be
-	  removed from the list of notifications.
-<synopsis>
-PGnotify* PQnotifies(PGconn *conn);
-
-typedef struct pgNotify {
-    char relname[NAMEDATALEN];       /* name of relation
-                                      * containing data */
-    int  be_pid;                     /* process id of backend */
-} PGnotify;
-</synopsis>
-After processing a <structname>PGnotify</structname> object returned by <function>PQnotifies</function>,
-be sure to free it with <function>free()</function> to avoid a memory leak.
-</para>
-<note>
-<para>
- In <productname>PostgreSQL</productname> 6.4 and later,
- the <literal>be_pid</literal> is that of the notifying backend,
- whereas in earlier versions it was always the <acronym>PID</acronym> of your own backend.
-</para>
-</note>
-</listitem>
-</itemizedlist>
-</para>
-
-<para>
-The  second  sample program gives an example of the use
-of asynchronous notification.
-</para>
-
-<para>
-<function>PQnotifies()</function> does not actually read backend data; 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 NOTIFY messages was to constantly submit queries,
-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 NOTIFY
-messages when you have no useful queries to make is to call
-<function>PQconsumeInput()</function>, then check
-<function>PQnotifies()</function>.
-You can use <function>select()</function> to wait for backend data to
-arrive, 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 queries 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 query.
-</para>
-
-</sect1>
-
-<sect1 id="libpq-copy">
-<title>Functions Associated with the COPY Command</title>
-
-<indexterm zone="libpq-copy">
- <primary>COPY</primary>
- <secondary>with libpq</secondary>
-</indexterm>
-
-<para>
- The COPY command in <productname>PostgreSQL</productname> has options to  read  from
- or  write  to  the  network  connection  used by <filename>libpq</filename>.
- Therefore, functions are necessary to access this  network
- connection directly so applications may take advantage of this capability.
-</para>
-
-<para>
- These functions should be executed only after obtaining a <literal>PGRES_COPY_OUT</literal>
- or <literal>PGRES_COPY_IN</literal> result object from <function>PQexec</function>
- or <function>PQgetResult</function>.
-</para>
-
-<para>
-<itemizedlist>
-<listitem>
-<para>
-<function>PQgetline</function>
-          Reads  a  newline-terminated  line  of  characters
-          (transmitted  by the backend server) into a buffer
-          string of size length.
-<synopsis>
-int PQgetline(PGconn *conn,
-              char *string,
-              int length)
-</synopsis>
-Like <function>fgets</function>,  this  routine copies up to length-1 characters
-into string. It is like <function>gets</function>, however, in that it 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>
-Notice that the application must check to see if a
-new line consists of  the  two characters  <literal>\.</literal>,
-which  indicates  that the backend server has finished sending
-the results  of  the  copy  command.
-If  the  application might
-receive lines that are more than length-1  characters  long,
-care is needed to be sure one recognizes the <literal>\.</literal> line correctly
-(and does not, for example, mistake the end of a long data line
-for a terminator line).
-The code in
-<filename>
-src/bin/psql/copy.c
-</filename>
-contains example routines that correctly handle the  copy protocol.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQgetlineAsync</function>
-          Reads  a  newline-terminated  line  of  characters
-          (transmitted  by the backend server) into a buffer
-          without blocking.
-<synopsis>
-int PQgetlineAsync(PGconn *conn,
-                   char *buffer,
-                   int bufsize)
-</synopsis>
-This routine is similar to <function>PQgetline</function>, but it can be used
-by applications
-that must read COPY data asynchronously, that is without blocking.
-Having issued the COPY 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.  Unlike <function>PQgetline</function>, this routine takes
-responsibility for detecting end-of-data.
-On each call, <function>PQgetlineAsync</function> will return data if a complete newline-
-terminated data line is available in <application>libpq</>'s input buffer, or if the
-incoming data line is too long to fit in the buffer offered by the caller.
-Otherwise, no data is returned until the rest of the line arrives.
-</para>
-<para>
-The routine 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.
-The data returned will not extend beyond a newline character.  If possible
-a whole line will be returned at one time.  But if the buffer offered by
-the caller is too small to hold a line sent by the backend, then a partial
-data line will be returned.  This can be detected by testing whether the
-last returned byte is <literal>\n</literal> or not.
-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>
-
-<listitem>
-<para>
-<function>PQputline</function>
-Sends  a  null-terminated  string  to  the backend server.
-Returns 0 if OK, <symbol>EOF</symbol> if unable to send the string.
-<synopsis>
-int PQputline(PGconn *conn,
-              const char *string);
-</synopsis>
-Note the application must explicitly  send  the  two
-characters  <literal>\.</literal> on a final line  to indicate to
-the backend that it has finished sending its data.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQputnbytes</function>
-Sends  a  non-null-terminated  string  to  the backend server.
-Returns 0 if OK, <symbol>EOF</symbol> if unable to send the string.
-<synopsis>
-int PQputnbytes(PGconn *conn,
-                const char *buffer,
-                int nbytes);
-</synopsis>
-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.
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQendcopy</function>
- Synchronizes with the backend.  This function waits until
- the  backend  has  finished  the  copy.  It should
- either be issued when the  last  string  has  been
- sent  to  the  backend using <function>PQputline</function> or when the
- last string has been  received  from  the  backend
- using <function>PGgetline</function>.  It must be issued or the backend
- may get <quote>out of sync</quote> with  the  frontend.   Upon
- return from this function, the backend is ready to
- receive the next SQL command.
- The return value is 0  on  successful  completion,
- nonzero otherwise.
-<synopsis>
-int PQendcopy(PGconn *conn);
-</synopsis>
-</para>
-
-<para>
-As an example:
-
-<programlisting>
-PQexec(conn, "CREATE TABLE foo (a int4, b char(16), d double precision)");
-PQexec(conn, "COPY foo FROM STDIN");
-PQputline(conn, "3\thello world\t4.5\n");
-PQputline(conn,"4\tgoodbye world\t7.11\n");
-...
-PQputline(conn,"\\.\n");
-PQendcopy(conn);
-</programlisting>
-</para>
-</listitem>
-</itemizedlist>
-</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 NULL. 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 copy in or copy out command embedded in a series of <acronym>SQL</acronym> commands
-will be executed correctly.
-</para>
-<para>
-Older applications are likely to submit a copy in or copy out
-via <function>PQexec</function> and assume that the transaction is done after
-<function>PQendcopy</function>.
-This will work correctly only if the copy in/out is the only
-<acronym>SQL</acronym> command in the command string.
-</para>
-
-</sect1>
-
-<sect1 id="libpq-trace">
-<title><application>libpq</application> Tracing Functions</title>
-
-<para>
-<itemizedlist>
-<listitem>
-<para>
-<function>PQtrace</function>
-          Enable  tracing of the frontend/backend communication to a debugging file stream.
-<synopsis>
-void PQtrace(PGconn *conn
-             FILE *debug_port)
-</synopsis>
-</para>
-</listitem>
-
-<listitem>
-<para>
-<function>PQuntrace</function>
-          Disable tracing started by <function>PQtrace</function>.
-<synopsis>
-void PQuntrace(PGconn *conn)
-</synopsis>
-</para>
-</listitem>
-</itemizedlist>
-</para>
-
-</sect1>
-
-<sect1 id="libpq-control">
-<title><application>libpq</application> Control Functions</title>
-
-<para>
-<itemizedlist>
-<listitem>
-<para>
-<function>PQsetNoticeProcessor</function>
-<indexterm><primary>notice processor</></>
-Control reporting of notice and warning messages generated by libpq.
-<synopsis>
-typedef void (*PQnoticeProcessor) (void *arg, const char *message);
-
-PQnoticeProcessor
-PQsetNoticeProcessor(PGconn *conn,
-                     PQnoticeProcessor proc,
-                     void *arg);
-</synopsis>
-</para>
-</listitem>
-</itemizedlist>
-</para>
-
-<para>
-By default, <application>libpq</application> prints notice
-messages from the backend on <filename>stderr</filename>,
-as well as a few error messages that it generates by itself.
-This behavior can be overridden by supplying a callback function that
-does something else with the messages.  The callback function is passed
-the text of the error message (which includes 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.)
-The default notice processor is simply
-<programlisting>
-static void
-defaultNoticeProcessor(void * arg, const char * message)
-{
-    fprintf(stderr, "%s", message);
-}
-</programlisting>
-To use a special notice processor, call
-<function>PQsetNoticeProcessor</function> just after
-creation of a new <structname>PGconn</> object.
-</para>
-
-<para>
-The return value is the pointer to the previous notice processor.
-If you supply a callback function pointer of NULL, no action is taken,
-but the current pointer is returned.
-</para>
-
-<para>
-Once you have set a notice 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 processor pointer is copied into the <structname>PGresult</> for possible use by
-routines like <function>PQgetvalue</function>.
-</para>
-
-</sect1>
-
-<sect1 id="libpq-envars">
-<title>Environment Variables</title>
-
-<indexterm zone="libpq-envars">
- <primary>environment variables</primary>
-</indexterm>
-
-<para>
-The following environment variables can be used to select default
-connection parameter values, which will be used by <function>PQconnectdb</function> or
-<function>PQsetdbLogin</function> if no value is directly specified by the calling code.
-These are useful to avoid hard-coding database names into simple
-application programs.
-
-<itemizedlist>
-<listitem>
-<para>
-<indexterm>
- <primary><envar>PGHOST</envar></primary>
-</indexterm>
-<envar>PGHOST</envar> sets the default server 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 (default <filename>/tmp</filename>).
-</para>
-</listitem>
-<listitem>
-<para>
-<indexterm>
- <primary><envar>PGPORT</envar></primary>
-</indexterm>
-<envar>PGPORT</envar> sets the default TCP port number or Unix-domain
-socket file extension for communicating with the
-<productname>PostgreSQL</productname> backend.
-</para>
-</listitem>
-<listitem>
-<para>
-<indexterm>
- <primary><envar>PGDATABASE</envar></primary>
-</indexterm>
-<envar>PGDATABASE</envar>  sets the default 
-<productname>PostgreSQL</productname> database name.
-</para>
-</listitem>
-<listitem>
-<para>
-<indexterm>
- <primary><envar>PGUSER</envar></primary>
-</indexterm>
-<envar>PGUSER</envar>
-sets the user name used to connect to the database and for authentication.
-</para>
-</listitem>
-<listitem>
-<para>
-<indexterm>
- <primary><envar>PGPASSWORD</envar></primary>
-</indexterm>
-<envar>PGPASSWORD</envar>
-sets the password used if the backend demands password
-authentication. This is not recommended because the password can
-be read by others using the <command>ps</command> command with special options
-on some platforms.
-</para>
-</listitem>
-<listitem>
-<para>
-<envar>PGREALM</envar> sets the Kerberos realm to  use  with  
-<productname>PostgreSQL</productname>, if  it is different from the local realm.
-If <envar>PGREALM</envar> is set, <productname>PostgreSQL</productname> 
-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 backend.
-</para>
-</listitem>
-<listitem>
-<para>
-<envar>PGOPTIONS</envar> sets additional run-time  options  for  
-the <productname>PostgreSQL</productname> backend.
-</para>
-</listitem>
-<listitem>
-<para>
-<envar>PGTTY</envar> sets the file or tty on which  debugging  
-messages from the backend server are displayed.
-</para>
-</listitem>
-</itemizedlist>
-</para>
-
-<para>
-The following environment variables can be used to specify user-level default
-behavior for every <productname>PostgreSQL</productname> session:
-
-<itemizedlist>
-<listitem>
-<para>
-<envar>PGDATESTYLE</envar>
-sets the default style of date/time representation.
-</para>
-</listitem>
-<listitem>
-<para>
-<envar>PGTZ</envar>
-sets the default time zone.
-</para>
-</listitem>
-<listitem>
-<para>
-<envar>PGCLIENTENCODING</envar>
-sets the default client encoding (if multibyte support was selected
-when configuring <productname>PostgreSQL</productname>).
-</para>
-</listitem>
-</itemizedlist>
-</para>
-
-<para>
-The following environment variables can be used to specify default internal
-behavior for every <productname>PostgreSQL</productname> session:
-
-<itemizedlist>
-<listitem>
-<para>
-<envar>PGGEQO</envar>
-sets the default mode for the genetic optimizer.
-</para>
-</listitem>
-</itemizedlist>
-</para>
-
-<para>
-Refer to the <command>SET</command> <acronym>SQL</acronym> command
-for information on correct values for these environment variables.
-</para>
-
-</sect1>
-
-<sect1 id="libpq-threading">
-<title>Threading Behavior</title>
-
-<indexterm zone="libpq-threading">
- <primary>threads</primary>
- <secondary>with libpq</secondary>
-</indexterm>
-
-<para>
-<filename>libpq</filename> is thread-safe as of
-<productname>PostgreSQL</productname> 7.0, so long as no two threads
-attempt to manipulate the same <structname>PGconn</> object at the same
-time. In particular, you cannot issue concurrent queries from different
-threads through the same connection object. (If you need to run
-concurrent queries, start up 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>PQoidStatus</function> and
-<function>fe_setauthsvc</function> are not thread-safe and should not be
-used in multithread programs.  <function>PQoidStatus</function> can be
-replaced by <function>PQoidValue</function>.  There is no good reason to
-call <function>fe_setauthsvc</function> at all.
-</para>
-
-<para>
-<filename>Libpq</filename> clients using the <literal>crypt</literal>
-encryption method rely on the <literal>crypt()</literal> operating
-system function, which is often not thread-safe. It is better to use
-<literal>MD5</literal> encryption, which is thread-safe on all
-platforms.
-</para>
-</sect1>
-
-
- <sect1 id="libpq-build">
-  <title>Building <application>Libpq</application> Programs</title>
-
-  <para>
-   To build (i.e., compile and link) your <application>libpq</application> programs 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>
-      Point your compiler to the directory where the <productname>PostgreSQL</> header
-      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>
-      <indexterm><primary>pg_config</></>
-      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> 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 it 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> or did not specify
-      the right path.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   <indexterm><primary>libpq-int.h</></>
-   If your codes references the header file
-   <filename>libpq-int.h</filename> and you refuse to fix your code to
-   not use it, starting in <productname>PostgreSQL</> 7.2, this file will be found in
-   <filename><replaceable>includedir</replaceable>/postgresql/internal/libpq-int.h</filename>,
-   so you need to add the appropriate <option>-I</option> option to
-   your compiler command line.
-  </para>
-
- </sect1>
-
-
- <sect1 id="libpq-example">
-  <title>Example Programs</title>
-
-  <example id="libpq-example-1">
-   <title><application>libpq</application> Example Program 1</title>
-
-<programlisting>
-/*
- * testlibpq.c
- *
- * Test the C version of libpq, the <productname>PostgreSQL</> frontend
- * library.
- */
-#include &lt;stdio.h&gt;
-#include &lt;libpq-fe.h&gt;
-
-void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-main()
-{
-    char       *pghost,
-               *pgport,
-               *pgoptions,
-               *pgtty;
-    char       *dbName;
-    int         nFields;
-    int         i,
-                j;
-
-    /* FILE *debug; */
-
-    PGconn     *conn;
-    PGresult   *res;
-
-    /*
-     * begin, by setting the parameters for a backend connection if the
-     * parameters are null, then the system will try to use reasonable
-     * defaults by looking up environment variables or, failing that,
-     * using hardwired constants
-     */
-    pghost = NULL;              /* host name of the backend server */
-    pgport = NULL;              /* port of the backend server */
-    pgoptions = NULL;           /* special options to start up the backend
-                                 * server */
-    pgtty = NULL;               /* debugging tty for the backend server */
-    dbName = "template1";
-
-    /* make a connection to the database */
-    conn = PQsetdb(pghost, pgport, pgoptions, pgtty, dbName);
-
-    /*
-     * check to see that the backend connection was successfully made
-     */
-    if (PQstatus(conn) == CONNECTION_BAD)
-    {
-        fprintf(stderr, "Connection to database '%s' failed.\n", dbName);
-        fprintf(stderr, "%s", PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    /* debug = fopen("/tmp/trace.out","w"); */
-    /* PQtrace(conn, debug);  */
-
-    /* start a transaction block */
-    res = PQexec(conn, "BEGIN");
-    if (!res || PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "BEGIN command failed\n");
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /*
-     * should PQclear PGresult whenever it is no longer needed to avoid
-     * memory leaks
-     */
-    PQclear(res);
-
-    /*
-     * fetch rows from the pg_database, the system catalog of
-     * databases
-     */
-    res = PQexec(conn, "DECLARE mycursor CURSOR FOR SELECT * FROM pg_database");
-    if (!res || PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "DECLARE CURSOR command failed\n");
-        PQclear(res);
-        exit_nicely(conn);
-    }
-    PQclear(res);
-    res = PQexec(conn, "FETCH ALL in mycursor");
-    if (!res || PQresultStatus(res) != PGRES_TUPLES_OK)
-    {
-        fprintf(stderr, "FETCH ALL command didn't return tuples properly\n");
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /* first, print out the attribute names */
-    nFields = PQnfields(res);
-    for (i = 0; i &lt; nFields; i++)
-        printf("%-15s", PQfname(res, i));
-    printf("\n\n");
-
-    /* next, print out the rows */
-    for (i = 0; i &lt; PQntuples(res); i++)
-    {
-        for (j = 0; j &lt; nFields; j++)
-            printf("%-15s", PQgetvalue(res, i, j));
-        printf("\n");
-    }
-    PQclear(res);
-
-    /* close the cursor */
-    res = PQexec(conn, "CLOSE mycursor");
-    PQclear(res);
-
-    /* commit the transaction */
-    res = PQexec(conn, "COMMIT");
-    PQclear(res);
-
-    /* close the connection to the database and cleanup */
-    PQfinish(conn);
-
-    /* fclose(debug); */
-    return 0;
-
-}
-</programlisting>
-  </example>
-
-  <example id="libpq-example-2">
-   <title><application>libpq</application> Example Program 2</title>
-
-<programlisting>
-/*
- * testlibpq2.c
- *  Test of the asynchronous notification interface
- *
- * Start this program, then from psql in another window do
- *   NOTIFY TBL2;
- *
- * Or, if you want to get fancy, try this:
- * Populate a database with the following:
- *
- *   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
- *
- *   INSERT INTO TBL1 values (10);
- *
- */
-#include &lt;stdio.h&gt;
-#include "libpq-fe.h"
-
-void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-main()
-{
-    char       *pghost,
-               *pgport,
-               *pgoptions,
-               *pgtty;
-    char       *dbName;
-    int         nFields;
-    int         i,
-                j;
-
-    PGconn     *conn;
-    PGresult   *res;
-    PGnotify   *notify;
-
-    /*
-     * begin, by setting the parameters for a backend connection if the
-     * parameters are null, then the system will try to use reasonable
-     * defaults by looking up environment variables or, failing that,
-     * using hardwired constants
-     */
-    pghost = NULL;              /* host name of the backend server */
-    pgport = NULL;              /* port of the backend server */
-    pgoptions = NULL;           /* special options to start up the backend
-                                 * server */
-    pgtty = NULL;               /* debugging tty for the backend server */
-    dbName = getenv("USER");    /* change this to the name of your test
-                                 * database */
-
-    /* make a connection to the database */
-    conn = PQsetdb(pghost, pgport, pgoptions, pgtty, dbName);
-
-    /*
-     * check to see that the backend connection was successfully made
-     */
-    if (PQstatus(conn) == CONNECTION_BAD)
-    {
-        fprintf(stderr, "Connection to database '%s' failed.\n", dbName);
-        fprintf(stderr, "%s", PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    res = PQexec(conn, "LISTEN TBL2");
-    if (!res || PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "LISTEN command failed\n");
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /*
-     * should PQclear PGresult whenever it is no longer needed to avoid
-     * memory leaks
-     */
-    PQclear(res);
-
-    while (1)
-    {
-
-        /*
-         * wait a little bit between checks; waiting with select()
-         * would be more efficient.
-         */
-        sleep(1);
-        /* collect any asynchronous backend messages */
-        PQconsumeInput(conn);
-        /* check for asynchronous notify messages */
-        while ((notify = PQnotifies(conn)) != NULL)
-        {
-            fprintf(stderr,
-                 "ASYNC NOTIFY of '%s' from backend pid '%d' received\n",
-                    notify-&gt;relname, notify-&gt;be_pid);
-            free(notify);
-        }
-    }
-
-    /* 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</>
-
-<programlisting>
-/*
- * testlibpq3.c Test the C version of Libpq, the <productname>PostgreSQL</> frontend
- * library. tests the binary cursor interface
- *
- *
- *
- * populate a database by doing the following:
- *
- * CREATE TABLE test1 (i int4, d real, p polygon);
- *
- * INSERT INTO test1 values (1, 3.567, polygon '(3.0, 4.0, 1.0, 2.0)');
- *
- * INSERT INTO test1 values (2, 89.05, polygon '(4.0, 3.0, 2.0, 1.0)');
- *
- * the expected output is:
- *
- * tuple 0: got i = (4 bytes) 1, d = (4 bytes) 3.567000, p = (4
- * bytes) 2 points   boundbox = (hi=3.000000/4.000000, lo =
- * 1.000000,2.000000) tuple 1: got i = (4 bytes) 2, d = (4 bytes)
- * 89.050003, p = (4 bytes) 2 points   boundbox =
- * (hi=4.000000/3.000000, lo = 2.000000,1.000000)
- *
- *
- */
-#include &lt;stdio.h&gt;
-#include "libpq-fe.h"
-#include "utils/geo_decls.h"    /* for the POLYGON type */
-
-void
-exit_nicely(PGconn *conn)
-{
-    PQfinish(conn);
-    exit(1);
-}
-
-main()
-{
-    char       *pghost,
-               *pgport,
-               *pgoptions,
-               *pgtty;
-    char       *dbName;
-    int         nFields;
-    int         i,
-                j;
-    int         i_fnum,
-                d_fnum,
-                p_fnum;
-    PGconn     *conn;
-    PGresult   *res;
-
-    /*
-     * begin, by setting the parameters for a backend connection if the
-     * parameters are null, then the system will try to use reasonable
-     * defaults by looking up environment variables or, failing that,
-     * using hardwired constants
-     */
-    pghost = NULL;              /* host name of the backend server */
-    pgport = NULL;              /* port of the backend server */
-    pgoptions = NULL;           /* special options to start up the backend
-                                 * server */
-    pgtty = NULL;               /* debugging tty for the backend server */
-
-    dbName = getenv("USER");    /* change this to the name of your test
-                                 * database */
-
-    /* make a connection to the database */
-    conn = PQsetdb(pghost, pgport, pgoptions, pgtty, dbName);
-
-    /*
-     * check to see that the backend connection was successfully made
-     */
-    if (PQstatus(conn) == CONNECTION_BAD)
-    {
-        fprintf(stderr, "Connection to database '%s' failed.\n", dbName);
-        fprintf(stderr, "%s", PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    /* start a transaction block */
-    res = PQexec(conn, "BEGIN");
-    if (!res || PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "BEGIN command failed\n");
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    /*
-     * should PQclear PGresult whenever it is no longer needed to avoid
-     * memory leaks
-     */
-    PQclear(res);
-
-    /*
-     * fetch rows from the pg_database, the system catalog of
-     * databases
-     */
-    res = PQexec(conn, "DECLARE mycursor BINARY CURSOR FOR SELECT * FROM test1");
-    if (!res || PQresultStatus(res) != PGRES_COMMAND_OK)
-    {
-        fprintf(stderr, "DECLARE CURSOR command failed\n");
-        PQclear(res);
-        exit_nicely(conn);
-    }
-    PQclear(res);
-
-    res = PQexec(conn, "FETCH ALL in mycursor");
-    if (!res || PQresultStatus(res) != PGRES_TUPLES_OK)
-    {
-        fprintf(stderr, "FETCH ALL command didn't return tuples properly\n");
-        PQclear(res);
-        exit_nicely(conn);
-    }
-
-    i_fnum = PQfnumber(res, "i");
-    d_fnum = PQfnumber(res, "d");
-    p_fnum = PQfnumber(res, "p");
-
-    for (i = 0; i &lt; 3; i++)
-    {
-        printf("type[%d] = %d, size[%d] = %d\n",
-               i, PQftype(res, i),
-               i, PQfsize(res, i));
-    }
-    for (i = 0; i &lt; PQntuples(res); i++)
-    {
-        int        *ival;
-        float      *dval;
-        int         plen;
-        POLYGON    *pval;
-
-        /* we hard-wire this to the 3 fields we know about */
-        ival = (int *) PQgetvalue(res, i, i_fnum);
-        dval = (float *) PQgetvalue(res, i, d_fnum);
-        plen = PQgetlength(res, i, p_fnum);
-
-        /*
-         * plen doesn't include the length field so need to
-         * increment by VARHDSZ
-         */
-        pval = (POLYGON *) malloc(plen + VARHDRSZ);
-        pval-&gt;size = plen;
-        memmove((char *) &amp;pval-&gt;npts, PQgetvalue(res, i, p_fnum), plen);
-        printf("tuple %d: got\n", i);
-        printf(" i = (%d bytes) %d,\n",
-               PQgetlength(res, i, i_fnum), *ival);
-        printf(" d = (%d bytes) %f,\n",
-               PQgetlength(res, i, d_fnum), *dval);
-        printf(" p = (%d bytes) %d points \tboundbox = (hi=%f/%f, lo = %f,%f)\n",
-               PQgetlength(res, i, d_fnum),
-               pval-&gt;npts,
-               pval-&gt;boundbox.xh,
-               pval-&gt;boundbox.yh,
-               pval-&gt;boundbox.xl,
-               pval-&gt;boundbox.yl);
-    }
-    PQclear(res);
-
-    /* close the cursor */
-    res = PQexec(conn, "CLOSE mycursor");
-    PQclear(res);
-
-    /* commit the transaction */
-    res = PQexec(conn, "COMMIT");
-    PQclear(res);
-
-    /* close the connection to the database and cleanup */
-    PQfinish(conn);
-
-    return 0;
-}
-</programlisting>
-  </example>
-
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/lobj.sgml b/doc/src/sgml/lobj.sgml
deleted file mode 100644
index 246fbbfea27..00000000000
--- a/doc/src/sgml/lobj.sgml
+++ /dev/null
@@ -1,590 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.27 2002/04/18 14:28:14 momjian Exp $
--->
-
- <chapter id="largeObjects">
-  <title id="largeObjects-title">Large Objects</title>
-
-  <indexterm zone="largeobjects"><primary>large object</></>
-  <indexterm><primary>BLOB</><see>large object</></>
-
-  <sect1 id="lo-intro">
-   <title>Introduction</title>
-
-   <para>
-    In <productname>PostgreSQL</productname> releases prior to 7.1,
-    the size of any row in the database could not exceed the size of a
-    data page.  Since the size of a data page is 8192 bytes (the
-    default, which can be raised up to 32768), the upper limit on the
-    size of a data value was relatively low. To support the storage of
-    larger atomic values, <productname>PostgreSQL</productname>
-    provided and continues to provide a large object interface.  This
-    interface provides file-oriented access to user data that has been
-    declared to be a large object.
-   </para>
-
-   <para>
-    <productname>POSTGRES 4.2</productname>, the indirect predecessor
-    of <productname>PostgreSQL</productname>, supported three standard
-    implementations of large objects: as files external to the
-    <productname>POSTGRES</productname> server, as external files
-    managed by the <productname>POSTGRES</productname> server, and as
-    data stored within the <productname>POSTGRES</productname>
-    database. This caused considerable confusion among users. As a
-    result, only support for large objects as data stored within the
-    database is retained in <productname>PostgreSQL</productname>.
-    Even though this is slower to access, it provides stricter data
-    integrity.  For historical reasons, this storage scheme is
-    referred to as <firstterm>Inversion large
-    objects</firstterm>. (You will see the term Inversion used
-    occasionally to mean the same thing as large object.)  Since
-    <productname>PostgreSQL 7.1</productname>, all large objects are
-    placed in one system table called
-    <classname>pg_largeobject</classname>.
-   </para>
-
-   <para>
-    <indexterm><primary>TOAST</></>
-    <indexterm><primary>sliced bread</><see>TOAST</></indexterm>
-    <productname>PostgreSQL 7.1</productname> introduced a mechanism
-    (nicknamed <quote><acronym>TOAST</acronym></quote>) that allows
-    data rows to be much larger than individual data pages.  This
-    makes the large object interface partially obsolete.  One
-    remaining advantage of the large object interface is that it
-    allows random access to the data, i.e., the ability to read or
-    write small chunks of a large value.  It is planned to equip
-    <acronym>TOAST</acronym> with such functionality in the future.
-   </para>
-
-   <para>
-    This section 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 section, but most programming
-    interfaces native to <productname>PostgreSQL</productname> support
-    equivalent functionality.  Other interfaces may use the large
-    object interface internally to provide generic support for large
-    values.  This is not described here.
-   </para>
-
-  </sect1>
-
-  <sect1 id="lo-implementation">
-   <title>Implementation Features</title>
-
-   <para>
-    The large object implementation breaks  large
-    objects  up  into  <quote>chunks</quote>  and  stores  the chunks in
-    tuples in the database.  A B-tree index guarantees fast
-    searches for the correct chunk number when doing random
-    access reads and writes.
-   </para>
-  </sect1>
-
-  <sect1 id="lo-interfaces">
-   <title>Interfaces</title>
-
-   <para>
-    The  facilities  <productname>PostgreSQL</productname> provides  to
-    access large objects,  both  in  the backend as part of user-defined
-    functions or the front end as part  of  an  application
-    using  the   interface, are described below. For users
-    familiar with <productname>POSTGRES 4.2</productname>,
-    <productname>PostgreSQL</productname> has a new set of
-    functions  providing  a  more  coherent  interface.
-
-    <note>
-     <para>
-      All large object manipulation <emphasis>must</emphasis> take
-      place within an SQL transaction. This requirement is strictly
-      enforced as of <productname>PostgreSQL 6.5</>, though it has been an
-      implicit requirement in previous versions, resulting in
-      misbehavior if ignored.
-     </para>
-    </note>
-   </para>
-
-   <para>
-    The  <productname>PostgreSQL</productname>  large  object interface is modeled after
-    the <acronym>Unix</acronym>  file-system  interface,  with  analogues  of
-    <function>open(2)</function>,  <function>read(2)</function>,
-    <function>write(2)</function>,
-    <function>lseek(2)</function>, etc.  User 
-    functions call these routines to retrieve only the data  of
-    interest  from a large object.  For example, if a large
-    object type called <type>mugshot</type>  existed  that  stored  
-    photographs  of  faces, then a function called <function>beard</function> could
-    be declared on <type>mugshot</type> data.  <function>beard</> could look  at  the
-    lower third of a photograph, and determine the color of
-    the beard that appeared  there,  if  any.   The  entire
-    large-object value need not be buffered, or even 
-    examined, by the <function>beard</function> function.
-    Large objects may be accessed from dynamically-loaded <acronym>C</acronym>
-    functions  or  database  client  programs that link the
-    library.  <productname>PostgreSQL</productname> provides a set of routines that 
-    support opening, reading, writing, closing, and seeking on
-    large objects.
-   </para>
-
-   <sect2>
-    <title>Creating a Large Object</title>
-
-    <para>
-     The routine
-<synopsis>
-Oid lo_creat(PGconn *<replaceable class="parameter">conn</replaceable>, int <replaceable class="parameter">mode</replaceable>)
-</synopsis>
-     creates a new large  object.  
-     <replaceable class="parameter">mode</replaceable>  is  a  bit mask
-     describing  several  different  attributes  of  the new
-     object.  The symbolic constants listed here are defined
-     in the header file <filename>libpq/libpq-fs.h</filename>.
-     The access type (read, write, or both) is controlled by
-     or'ing together the bits <symbol>INV_READ</symbol>  and
-     <symbol>INV_WRITE</symbol>.  The low-order sixteen bits of the mask have
-     historically been used at Berkeley to designate the storage  manager  number on which the large object
-     should reside.  These
-     bits should always be zero now.
-     The commands below create a large object:
-<programlisting>
-inv_oid = lo_creat(INV_READ|INV_WRITE);
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Importing a Large Object</title>
-
-    <para>
-     To import an operating system file as a large object, call
-<synopsis>
-Oid lo_import(PGconn *<replaceable class="parameter">conn</replaceable>, const char *<replaceable class="parameter">filename</replaceable>)
-</synopsis>
-    <replaceable class="parameter">filename</replaceable> 
-     specifies the operating system name of
-     the file to be imported as a large object.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Exporting a Large Object</title>
-
-    <para>
-     To export a large object
-     into an operating system file, call
-<synopsis>
-int lo_export(PGconn *<replaceable class="parameter">conn</replaceable>, Oid <replaceable class="parameter">lobjId</replaceable>, const char *<replaceable class="parameter">filename</replaceable>)
-</synopsis>
-     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 name of the file.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Opening an Existing Large Object</title>
-
-    <para>
-     To open an existing large object, call
-<synopsis>
-int lo_open(PGconn *conn, Oid lobjId, int mode)
-</synopsis>
-     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.
-     A  large  object cannot be opened before it is created.
-     <function>lo_open</function> returns a 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>.
-</para>
-</sect2>
-
-<sect2>
-<title>Writing Data to a Large Object</title>
-
-<para>
-     The routine
-<programlisting>
-int lo_write(PGconn *conn, int fd, const char *buf, size_t len)
-</programlisting>
-     writes <parameter>len</parameter> bytes from <parameter>buf</parameter> to large object <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>
-<title>Reading Data from a Large Object</title>
-
-<para>
-     The routine
-<programlisting>
-int lo_read(PGconn *conn, int fd, char *buf, size_t len)
-</programlisting>
-     reads <parameter>len</parameter> bytes from large object <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>
-<title>Seeking on a Large Object</title>
-
-<para>
-     To change the current read or write location on a large
-     object, call
-<programlisting>
-int lo_lseek(PGconn *conn, int fd, int offset, int whence)
-</programlisting>
-     This routine moves the current location pointer for the
-     large object described by <parameter>fd</> to the new location specified 
-     by <parameter>offset</>.  The valid values for <parameter>whence</> are
-     <symbol>SEEK_SET</>, <symbol>SEEK_CUR</>, and <symbol>SEEK_END</>.
-</para>
-</sect2>
-
-<sect2>
-<title>Closing a Large Object Descriptor</title>
-
-<para>
-     A large object may be closed by calling
-<programlisting>
-int lo_close(PGconn *conn, int fd)
-</programlisting>
-     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>
-</sect2>
-
-   <sect2>
-    <title>Removing a Large Object</title>
-
-    <para>
-     To remove a large object from the database, call
-<synopsis>
-int lo_unlink(PGconn *<replaceable class="parameter">conn</replaceable>, Oid lobjId)
-</synopsis>
-     The <parameter>lobjId</parameter> argument specifies  the  OID  of  the  large
-     object  to  remove.  In the event of an error, the return value is negative.
-    </para>
-   </sect2>
-
-
-</sect1>
-
-<sect1 id="lo-funcs">
-<title>Server-side Built-in Functions</title>
-
-<para>
-     There  are two built-in registered functions, <function>lo_import</function>
-     and <function>lo_export</function> which  are  convenient  for  use
-    in  <acronym>SQL</acronym>
-     queries.
-     Here is an example of their use
-<programlisting>
-CREATE TABLE image (
-    name            text,
-    raster          oid
-);
-
-INSERT INTO image (name, raster)
-    VALUES ('beautiful image', lo_import('/etc/motd'));
-
-SELECT lo_export(image.raster, '/tmp/motd') FROM image
-    WHERE name = 'beautiful image';
-</programlisting>
-</para>
-</sect1>
-
-<sect1 id="lo-libpq">
-<title>Accessing Large Objects from <application>Libpq</application></title>
-
-<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 be found in
-     <filename>src/test/examples/testlo.c</filename> in the source distribution.
-     Frontend 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>
-
-  <example id="lo-example">
-   <title>Large Objects with <application>Libpq</application> Example Program</title>
-<programlisting>
-/*--------------------------------------------------------------
- *
- * testlo.c--
- *    test using large objects with libpq
- *
- * Copyright (c) 1994, Regents of the University of California
- *
- *--------------------------------------------------------------
- */
-#include &lt;stdio.h&gt;
-#include &quot;libpq-fe.h&quot;
-#include &quot;libpq/libpq-fs.h&quot;
-
-#define BUFSIZE          1024
-
-/*
- * importFile
- *    import file &quot;in_filename&quot; into database as large object &quot;lobjOid&quot;
- *
- */
-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 &lt; 0)
-    {                           /* error */
-        fprintf(stderr, &quot;can't open unix file %s\n&quot;, filename);
-    }
-
-    /*
-     * create the large object
-     */
-    lobjId = lo_creat(conn, INV_READ | INV_WRITE);
-    if (lobjId == 0)
-        fprintf(stderr, &quot;can't create large object\n&quot;);
-
-    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)) &gt; 0)
-    {
-        tmp = lo_write(conn, lobj_fd, buf, nbytes);
-        if (tmp &lt; nbytes)
-            fprintf(stderr, &quot;error while reading large object\n&quot;);
-    }
-
-    (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 &lt; 0)
-    {
-        fprintf(stderr, &quot;can't open large object %d\n&quot;,
-                lobjId);
-    }
-
-    lo_lseek(conn, lobj_fd, start, SEEK_SET);
-    buf = malloc(len + 1);
-
-    nread = 0;
-    while (len - nread &gt; 0)
-    {
-        nbytes = lo_read(conn, lobj_fd, buf, len - nread);
-        buf[nbytes] = ' ';
-        fprintf(stderr, &quot;&gt;&gt;&gt; %s&quot;, buf);
-        nread += nbytes;
-    }
-    free(buf);
-    fprintf(stderr, &quot;\n&quot;);
-    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_READ);
-    if (lobj_fd &lt; 0)
-    {
-        fprintf(stderr, &quot;can't open large object %d\n&quot;,
-                lobjId);
-    }
-
-    lo_lseek(conn, lobj_fd, start, SEEK_SET);
-    buf = malloc(len + 1);
-
-    for (i = 0; i &lt; len; i++)
-        buf[i] = 'X';
-    buf[i] = ' ';
-
-    nwritten = 0;
-    while (len - nwritten &gt; 0)
-    {
-        nbytes = lo_write(conn, lobj_fd, buf + nwritten, len - nwritten);
-        nwritten += nbytes;
-    }
-    free(buf);
-    fprintf(stderr, &quot;\n&quot;);
-    lo_close(conn, lobj_fd);
-}
-
-/*
- * exportFile *    export large object &quot;lobjOid&quot; to file &quot;out_filename&quot;
- *
- */
-void
-exportFile(PGconn *conn, Oid lobjId, char *filename)
-{
-    int         lobj_fd;
-    char        buf[BUFSIZE];
-    int         nbytes,
-                tmp;
-    int         fd;
-
-    /*
-     * create an inversion &quot;object&quot;
-     */
-    lobj_fd = lo_open(conn, lobjId, INV_READ);
-    if (lobj_fd &lt; 0)
-    {
-        fprintf(stderr, &quot;can't open large object %d\n&quot;,
-                lobjId);
-    }
-
-    /*
-     * open the file to be written to
-     */
-    fd = open(filename, O_CREAT | O_WRONLY, 0666);
-    if (fd &lt; 0)
-    {                           /* error */
-        fprintf(stderr, &quot;can't open unix file %s\n&quot;,
-                filename);
-    }
-
-    /*
-     * read in from the Unix file and write to the inversion file
-     */
-    while ((nbytes = lo_read(conn, lobj_fd, buf, BUFSIZE)) &gt; 0)
-    {
-        tmp = write(fd, buf, nbytes);
-        if (tmp &lt; nbytes)
-        {
-            fprintf(stderr, &quot;error while writing %s\n&quot;,
-                    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, &quot;Usage: %s database_name in_filename out_filename\n&quot;,
-                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, &quot;Connection to database '%s' failed.\n&quot;, database);
-        fprintf(stderr, &quot;%s&quot;, PQerrorMessage(conn));
-        exit_nicely(conn);
-    }
-
-    res = PQexec(conn, &quot;begin&quot;);
-    PQclear(res);
-
-    printf(&quot;importing file %s\n&quot;, in_filename);
-/*  lobjOid = importFile(conn, in_filename); */
-    lobjOid = lo_import(conn, in_filename);
-/*
-    printf(&quot;as large object %d.\n&quot;, lobjOid);
-
-    printf(&quot;picking out bytes 1000-2000 of the large object\n&quot;);
-    pickout(conn, lobjOid, 1000, 1000);
-
-    printf(&quot;overwriting bytes 1000-2000 of the large object with X's\n&quot;);
-    overwrite(conn, lobjOid, 1000, 1000);
-*/
-
-    printf(&quot;exporting large object to file %s\n&quot;, out_filename);
-/*    exportFile(conn, lobjOid, out_filename); */
-    lo_export(conn, lobjOid, out_filename);
-
-    res = PQexec(conn, &quot;end&quot;);
-    PQclear(res);
-    PQfinish(conn);
-    exit(0);
-}
-</programlisting>
-</example>
-
-</sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
deleted file mode 100644
index b2fa6febc49..00000000000
--- a/doc/src/sgml/maintenance.sgml
+++ /dev/null
@@ -1,441 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/maintenance.sgml,v 1.14 2002/06/13 05:15:22 momjian Exp $
--->
-
-<chapter id="maintenance">
- <title>Routine Database Maintenance Tasks</title>
-
- <sect1 id="maintenance-general">
-  <title>General Discussion</Title>
-
-  <para>
-   There are a few routine maintenance chores that must be performed on
-   a regular basis to keep a <productname>PostgreSQL</productname>
-   installation running smoothly.  The tasks discussed here are repetitive
-   in nature and can easily be automated using standard Unix tools such
-   as <filename>cron</filename> scripts.  But it is the database
-   administrator's responsibility to set up appropriate scripts, and to
-   check that they execute successfully.
-  </para>
-
-  <para>
-   One obvious maintenance task is 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>
-
-  <para>
-   The other main category of maintenance task is periodic <quote>vacuuming</>
-   of the database.  This activity is discussed in
-   <xref linkend="routine-vacuuming">.
-  </para>
-
-  <para>
-   Something else that might need periodic attention is log file management.
-   This is discussed in <xref linkend="logfile-maintenance">.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname> is low-maintenance compared to
-   some other database products.  Nonetheless, appropriate attention to
-   these tasks will go far towards ensuring a pleasant and productive
-   experience with the system.
-  </para>
-
- </sect1>
-
- <sect1 id="routine-vacuuming">
-  <title>Routine Vacuuming</title>
-
-  <indexterm zone="routine-vacuuming">
-   <primary>vacuum</primary>
-  </indexterm>
-
-  <para>
-   <productname>PostgreSQL</productname>'s <command>VACUUM</> command must be
-   run on a regular basis for several reasons:
-
-    <orderedlist>
-     <listitem>
-      <simpara>To recover disk space occupied by updated or deleted
-      rows.</simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>To update data statistics used by the
-      <productname>PostgreSQL</productname> query planner.</simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>To protect against loss of very old data due to
-      <firstterm>transaction ID wraparound</>.</simpara>
-     </listitem>
-    </orderedlist>
-
-   The frequency and scope of <command>VACUUM</>s performed for each of
-   these reasons will vary depending on the needs of each installation.
-   Therefore, database administrators must understand these issues and
-   develop an appropriate maintenance strategy.  This section concentrates
-   on explaining the high-level issues; for details about command syntax
-   and so on, see the <command>VACUUM</> command reference page.
-  </para>
-
-  <para>
-   Beginning in <productname>PostgreSQL</productname> 7.2, the standard form
-   of <command>VACUUM</> can run in parallel with normal database operations
-   (selects, inserts, updates, deletes, but not changes to table schemas).
-   Routine vacuuming is therefore not nearly as intrusive as it was in prior
-   releases, and it's not as critical to try to schedule it at low-usage
-   times of day.
-  </para>
-
-  <sect2 id="vacuum-for-space-recovery">
-   <title>Recovering disk space</title>
-
-   <indexterm zone="vacuum-for-space-recovery">
-    <primary>disk space</primary>
-   </indexterm>
-
-   <para>
-    In normal <productname>PostgreSQL</productname> operation, an <command>UPDATE</> or
-    <command>DELETE</> of a row does not immediately remove the old <firstterm>tuple</>
-    (version of the row).  This approach is necessary to gain the benefits
-    of multiversion concurrency control (see the <citetitle>User's Guide</>):
-    the tuple must not be deleted while 
-    it is still potentially visible to other transactions.  But eventually,
-    an outdated or deleted tuple is no longer of interest to any transaction.
-    The space it occupies must be reclaimed for reuse by new tuples, to avoid
-    infinite growth of disk space requirements.  This is done by running
-    <command>VACUUM</>.
-   </para>
-
-   <para>
-    Clearly, a table that receives frequent updates or deletes will need
-    to be vacuumed more often than tables that are seldom updated.  It may
-    be useful to set up periodic <application>cron</> tasks that vacuum only selected tables,
-    skipping tables that are known not to change often.  This is only likely
-    to be helpful if you have both large heavily-updated tables and large
-    seldom-updated tables --- the extra cost of vacuuming a small table
-    isn't enough to be worth worrying about.
-   </para>
-
-   <para>
-    The standard form of <command>VACUUM</> is best used with the goal of
-    maintaining a fairly level steady-state usage of disk space.  The standard
-    form finds old tuples and makes their space available for re-use within
-    the table, but it does not try very hard to shorten the table file and
-    return disk space to the operating system.  If you need to return disk
-    space to the operating system you can use <command>VACUUM FULL</> ---
-    but what's the point of releasing disk space that will only have to be
-    allocated again soon?  Moderately frequent standard <command>VACUUM</>s
-    are a better approach than infrequent <command>VACUUM FULL</>s for
-    maintaining heavily-updated tables.
-   </para>
-
-   <para>
-    Recommended practice for most sites is to schedule a database-wide
-    <command>VACUUM</> once a day at a low-usage time of day, supplemented
-    by more frequent vacuuming of heavily-updated tables if necessary.
-    (If you have multiple databases in an installation, don't forget to
-    vacuum each one; the <filename>vacuumdb</> script may be helpful.)
-    Use plain <command>VACUUM</>, not <command>VACUUM FULL</>, for routine
-    vacuuming for space recovery.
-   </para>
-
-   <para>
-    <command>VACUUM FULL</> is recommended for cases where you know you have
-    deleted the majority of tuples in a table, so that the steady-state size
-    of the table can be shrunk substantially with <command>VACUUM FULL</>'s
-    more aggressive approach.
-   </para>
-
-   <para>
-    If you have a table whose contents are deleted completely every so often,
-    consider doing it with <command>TRUNCATE</> rather than using
-    <command>DELETE</> followed by <command>VACUUM</>.
-   </para>
-  </sect2>
-
-  <sect2 id="vacuum-for-statistics">
-   <title>Updating planner statistics</title>
-
-   <para>
-    The <productname>PostgreSQL</productname> query planner relies on
-    statistical information about the contents of tables in order to
-    generate good plans for queries.  These statistics are gathered by
-    the <command>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 may
-    degrade database performance.
-   </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 may 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 may 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, the usefulness of this feature is doubtful.
-    Beginning in <productname>PostgreSQL</productname> 7.2,
-    <command>ANALYZE</> is a fairly fast operation even on large tables,
-    because it uses a statistical random sampling of the rows of a table
-    rather than reading every single row.  So it's probably much simpler
-    to just run it over the whole database every so often.
-   </para>
-
-   <tip>
-    <para>
-     Although per-column tweaking of <command>ANALYZE</> frequency may not be
-     very productive, you may well 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 WHERE clauses
-     and have highly irregular data distributions may require a finer-grain
-     data histogram than other columns.  See <command>ALTER TABLE SET
-     STATISTICS</>.
-    </para>
-   </tip>
-
-   <para>
-    Recommended practice for most sites is to schedule a database-wide
-    <command>ANALYZE</> once a day at a low-usage time of day; this can
-    usefully be combined with a nightly <command>VACUUM</>.  However,
-    sites with relatively slowly changing table statistics may find that
-    this is overkill, and that less-frequent <command>ANALYZE</> runs
-    are sufficient.
-   </para>
-  </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>
-
-   <para>
-    <productname>PostgreSQL</productname>'s MVCC transaction semantics
-    depend on being able to compare transaction ID (<firstterm>XID</>)
-    numbers: a tuple with an insertion XID newer 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 at this writing) an installation that runs for a long time (more
-    than 4 billion transactions) will 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 --- which
-    means their outputs become invisible.  In short, catastrophic data loss.
-    (Actually the data is still there, but that's cold comfort if you can't
-    get at it.)
-   </para>
-
-   <para>
-    Prior to <productname>PostgreSQL</productname> 7.2, the only defense
-    against XID wraparound was to re-<command>initdb</> at least every 4 billion
-    transactions.  This of course was not very satisfactory for high-traffic
-    sites, so a better solution has been devised.  The new approach allows an
-    installation to remain up indefinitely, without <command>initdb</> or any sort of
-    restart.  The price is this maintenance requirement:
-    <emphasis>every table in the database must be vacuumed at least once every
-    billion transactions</emphasis>.
-   </para>
-
-   <para>
-    In practice this isn't an onerous requirement, but since the consequences
-    of failing to meet it can be complete data loss (not just wasted disk
-    space or slow performance), some special provisions have been made to help
-    database administrators keep track of the time since the last
-    <command>VACUUM</>.  The remainder of this section gives the details.
-   </para>
-
-   <para>
-    The new approach to XID comparison distinguishes two special XIDs, numbers
-    1 and 2 (<literal>BootstrapXID</> and <literal>FrozenXID</>).  These two
-    XIDs are always considered older than every normal XID.  Normal XIDs (those
-    greater than 2) 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 tuple has been created with a particular normal XID, the
-    tuple 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
-    tuple still exists after more than two billion transactions, it will
-    suddenly appear to be in the future.  To prevent data loss, old tuples
-    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 tuples will be
-    good until deleted, no matter how long that is.  This reassignment of
-    XID is handled by <command>VACUUM</>.
-   </para>
-
-   <para>
-    <command>VACUUM</>'s normal policy is to reassign <literal>FrozenXID</>
-    to any tuple with a normal XID more than one billion transactions in the
-    past.  This policy preserves the original insertion XID until it is not
-    likely to be of interest anymore (in fact, most tuples will probably
-    live and die without ever being <quote>frozen</>).  With this policy,
-    the maximum safe interval between <command>VACUUM</>s of any table
-    is exactly one billion transactions: if you wait longer, it's possible
-    that a tuple that was not quite old enough to be reassigned last time
-    is now more than two billion transactions old and has wrapped around
-    into the future --- ie, is lost to you.  (Of course, it'll reappear
-    after another two billion transactions, but that's no help.)
-   </para>
-
-   <para>
-    Since periodic <command>VACUUM</>s are needed anyway for the reasons
-    described earlier, it's unlikely that any table would not be vacuumed
-    for as long as a billion transactions.  But to help administrators ensure
-    this constraint is met, <command>VACUUM</> stores transaction ID
-    statistics in the system table <filename>pg_database</>.  In particular,
-    the <filename>datfrozenxid</> field of a database's
-    <filename>pg_database</> row is updated at the completion of any
-    database-wide vacuum operation (ie, <command>VACUUM</> that does not
-    name a specific table).  The value stored in this field is the freeze
-    cutoff XID that was used by that <command>VACUUM</> command.  All normal
-    XIDs older than this cutoff XID are guaranteed to have been replaced by
-    <literal>FrozenXID</> within that database.  A convenient way to
-    examine this information is to execute the query
-    <informalexample>
-<programlisting>
-SELECT datname, age(datfrozenxid) FROM pg_database;
-</programlisting>
-    </informalexample>
-    The <literal>age</> column measures the number of transactions from the
-    cutoff XID to the current transaction's XID.
-   </para>
-
-   <para>
-    With the standard freezing policy, the <literal>age</> column will start
-    at one billion for a freshly-vacuumed database.  When the <literal>age</>
-    approaches two billion, the database must be vacuumed again to avoid
-    risk of wraparound failures.  Recommended practice is to vacuum each
-    database at least once every half-a-billion (500 million) transactions,
-    so as to provide plenty of safety margin.  To help meet this rule,
-    each database-wide <command>VACUUM</> automatically delivers a warning
-    if there are any <filename>pg_database</> entries showing an
-    <literal>age</> of more than 1.5 billion transactions, for example:
-    <informalexample>
-<programlisting>
-play=# vacuum;
-WARNING:  Some databases have not been vacuumed in 1613770184 transactions.
-        Better vacuum them within 533713463 transactions,
-        or you may have a wraparound failure.
-VACUUM
-</programlisting>
-    </informalexample>
-   </para>
-
-   <para>
-    <command>VACUUM</> with the <command>FREEZE</> option uses a more
-    aggressive freezing policy: tuples are frozen if they are old enough
-    to be considered good by all open transactions.  In particular, if
-    a <command>VACUUM FREEZE</> is performed in an otherwise-idle database,
-    it is guaranteed that <emphasis>all</> tuples in that database will be
-    frozen.  Hence, as long as the database is not modified in any way, it
-    will not need subsequent vacuuming to avoid transaction ID wraparound
-    problems.  This technique is used by <filename>initdb</> to prepare the
-    <filename>template0</> database.  It should also be used to prepare any
-    user-created databases that are to be marked <literal>datallowconn</> =
-    <literal>false</> in <filename>pg_database</>, since there isn't any
-    convenient way to vacuum a database that you can't connect to.  Note
-    that <command>VACUUM</command>'s automatic warning message about unvacuumed databases will
-    ignore  <filename>pg_database</> entries with <literal>datallowconn</> =
-    <literal>false</>, so as to avoid giving false warnings about these
-    databases; therefore it's up to you to ensure that such databases are
-    frozen correctly.
-   </para>
-
-  </sect2>
- </sect1>
-
-
- <sect1 id="logfile-maintenance">
-  <title>Log File Maintenance</title>
-
-  <indexterm zone="logfile-maintenance">
-   <primary>log files</primary>
-  </indexterm>
-
-  <para>
-   It's a good idea to save the database server's log output somewhere,
-   rather than just routing it to <filename>/dev/null</>.  The log output
-   is invaluable when it comes time to diagnose problems.  However, the
-   log output tends to be voluminous (especially at higher debug levels)
-   and you won't want to save it indefinitely.  You need to <quote>rotate</>
-   the log files so that new log files are started and old ones thrown
-   away every so often.
-  </para>
-
-  <para>
-   If you simply direct the postmaster's <systemitem>stderr</> into a file, the only way
-   to truncate the log file is to stop and restart the postmaster.  This
-   may be OK for development setups but you won't want to run a production
-   server that way.
-  </para>
-
-  <para>
-   The simplest production-grade approach to managing log output is to send it
-   all to <application>syslog</> and let <application>syslog</> deal with file
-   rotation.  To do this, make sure <productname>PostgreSQL</> was built with
-   the <option>--enable-syslog</> configure option, and set
-   <literal>syslog</> to 2
-   (log to 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.
-  </para>
-
-  <para>
-   On many systems, however, syslog is not very reliable, particularly
-   with large log messages; it may truncate or drop messages just when
-   you need them the most.  You may find it more useful to pipe the
-   <application>postmaster</>'s <systemitem>stderr</> to some type of log rotation script.
-   If you start the postmaster with <application>pg_ctl</>, then the
-   postmaster's <systemitem>stderr</> is already redirected to <systemitem>stdout</>, so you just need a
-   pipe command:
-   
-<screen>
-<userinput>pg_ctl start | logrotate</userinput>
-</screen>
-
-   The <productname>PostgreSQL</> distribution doesn't include a suitable
-   log rotation program, but there are many available on the net;
-   one is included in the Apache distribution, for example.
-  </para>
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/manage-ag.sgml b/doc/src/sgml/manage-ag.sgml
deleted file mode 100644
index 15ece75a398..00000000000
--- a/doc/src/sgml/manage-ag.sgml
+++ /dev/null
@@ -1,347 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/manage-ag.sgml,v 2.20 2001/11/28 20:49:10 petere Exp $
--->
-
-<chapter id="managing-databases">
- <title>Managing Databases</title>
-
- <indexterm zone="managing-databases"><primary>database</></>
-
- <para>
-  A database is a named collection of SQL objects (<quote>database
-  objects</quote>).  Generally, every database object (tables, functions,
-  etc.) belongs to one and only one database.  (But there are a few system
-  catalogs, for example <literal>pg_database</>, that belong to a whole
-  installation and are accessible from each database within the
-  installation.)
-  An application that connects
-  to the database server specifies 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. (But an application
-  is not restricted in the number of connections it opens to the same
-  or other databases.)
- </para>
-
- <note>
-  <para>
-   <acronym>SQL</> calls databases <quote>catalogs</>, but there is no
-   difference in practice.
-  </para>
- </note>
-
- <para>
-  In order to create or drop databases, the <productname>PostgreSQL</>
-  <application>postmaster</> must be up and running (see <xref
-  linkend="postmaster-start">).
- </para>
-
- <sect1 id="manage-ag-createdb">
-  <title>Creating a Database</title>
-
-  <para>
-   Databases are created with the query language command
-   <command>CREATE DATABASE</command>:
-<synopsis>
-CREATE DATABASE <replaceable>name</>
-</synopsis>
-   where <replaceable>name</> follows the usual rules for SQL identifiers.
-   The current user automatically becomes
-   the owner of the new database. It is the privilege of the owner of
-   a database to remove it later on (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="user-attributes"> for how to grant permission.
-  </para>
-
-  <formalpara>
-   <title>Bootstrapping:</title>
-   <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">.) By convention
-    this database is called <literal>template1</>. So
-    to create the first <quote>real</> database you can connect to
-    <literal>template1</>.
-   </para>
-  </formalpara>
-
-  <para>
-   The name <quote>template1</quote> is no accident: When a new
-   database is created, the template database is essentially cloned.
-   This means that any changes you make in <literal>template1</> are
-   propagated to all subsequently created databases. This implies that
-   you should not use the template database for real work, but when
-   used judiciously this feature can be convenient.  More details appear
-   below.
-  </para>
-
-  <para>
-   As an extra convenience, there is also a program that you can
-   execute from the shell to create new databases,
-   <filename>createdb</>.
-
-<synopsis>
-createdb <replaceable class="parameter">dbname</replaceable>
-</synopsis>
-
-   <command>createdb</> does no magic. It connects to the template1
-   database and issues the <command>CREATE DATABASE</> command,
-   exactly as described above. It uses the <application>psql</> program
-   internally. The reference page on <command>createdb</> contains the invocation
-   details. Note that <command>createdb</> without any arguments will create
-   a database with the current user name, which may or may not be what
-   you want.
-  </para>
-
-  <sect2 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</>.  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 <literal>plpgsql</> in <literal>template1</>, it will
-   automatically be available in user databases without any extra action
-   being taken when those databases are made.
-  </para>
-
-  <para>
-   There is a second standard system database named <literal>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 <productname>PostgreSQL</productname>.
-     <literal>template0</> should never be changed 
-   after <literal>initdb</>.  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 any conflicts with
-   additions that may now be present in <literal>template1</>.
-  </para>
-
-  <para>
-   It is possible to create additional template databases, and indeed
-   one might copy any database in an installation 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>COPY DATABASE</quote> facility.  In particular, it is
-   essential that the source database be idle (no data-altering transactions
-   in progress)
-   for the duration of the copying operation.  <command>CREATE DATABASE</>
-   will check
-   that no backend processes (other than itself) are connected to
-   the source database at the start of the operation, but this does not
-   guarantee that changes cannot be made while the copy proceeds, which
-   would result in an inconsistent copied database.  Therefore,
-   we recommend that databases used as templates be treated as read-only.
-  </para>
-
-  <para>
-   Two useful flags exist in <literal>pg_database</literal> for each
-   database: <literal>datistemplate</literal> and
-   <literal>datallowconn</literal>.  <literal>datistemplate</literal>
-   may be set to indicate that a database is intended as a template for
-   <command>CREATE DATABASE</>.  If this flag is set, the database may be
-   cloned by 
-   any user with <literal>CREATEDB</> privileges; if it is not set, only superusers
-   and the owner of the database may clone it.
-   If <literal>datallowconn</literal> is false, then no new connections
-   to that database will be allowed (but existing sessions are not killed
-   simply by setting the flag false).  The <literal>template0</literal>
-   database is normally marked <literal>datallowconn</literal> =
-   <literal>false</> to prevent modification of it.
-   Both <literal>template0</literal> and <literal>template1</literal>
-   should always be marked with <literal>datistemplate</literal> =
-   <literal>true</>.
-  </para>
-
-  <para>
-   After preparing a template database, or making any changes to one,
-   it is a good idea to perform
-   <command>VACUUM FREEZE</> or <command>VACUUM FULL FREEZE</> in that
-   database.  If this is done when there are no other open transactions
-   in the same database, then it is guaranteed that all tuples in the
-   database are <quote>frozen</> and will not be subject to transaction
-   ID wraparound problems.  This is particularly important for a database
-   that will have <literal>datallowconn</literal> set to false, since it
-   will be impossible to do routine maintenance <command>VACUUM</>s on
-   such a database.
-   See <xref linkend="vacuum-for-wraparound"> for more information.
-  </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</> and the default
-    database-to-connect-to for various scripts such as <literal>createdb</>.
-    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</>.
-   </para>
-  </note>
-
-  </sect2>
-
-  <sect2 id="manage-ag-alternate-locs">
-   <title>Alternative Locations</title>
-
-   <para>
-    It is possible to create a database in a location other than the
-    default location for the installation. Remember that all database access
-    occurs through the 
-    database server, so any location specified must be
-    accessible by the server.
-   </para>
-
-   <para>
-    Alternative database locations are referenced by an environment
-    variable which gives the absolute path to the intended storage
-    location. This environment variable must be present in the server's
-    environment, so it must have been defined before the server
-    was started.  (Thus, the set of available alternative locations is
-    under the site administrator's control; ordinary users can't
-    change it.)  Any valid environment variable name may
-    be used to reference an alternative location, although using
-    variable names with a prefix of <literal>PGDATA</> is recommended
-    to avoid confusion and conflict with other variables.
-   </para>
-
-   <para>
-    To create the variable in the environment of the server process
-    you must first shut down the server, define the variable,
-    initialize the data area, and finally restart the server. (See
-    <xref linkend="postmaster-shutdown"> and <xref
-    linkend="postmaster-start">.) To set an environment variable, type
-    <informalexample>
-<programlisting>
-PGDATA2=/home/postgres/data
-export PGDATA2
-</programlisting>
-    </informalexample>
-    in Bourne shells, or
-    <informalexample>
-<programlisting>
-setenv PGDATA2 /home/postgres/data
-</programlisting>
-    </informalexample>
-    in <application>csh</> or <application>tcsh</>. You have to make sure that this environment
-    variable is always defined in the server environment, otherwise
-    you won't be able to access that database. Therefore you probably
-    want to set it in some sort of shell start-up file or server
-    start-up script.
-   </para>
-
-   <para>
-    <indexterm><primary>initlocation</></>
-    To create a data storage area in <envar>PGDATA2</>, ensure that
-    the containing directory (here, <filename>/home/postgres</filename>)
-    already exists and is writable
-    by the user account that runs the server (see <xref
-    linkend="postgres-user">). Then from the command line, type
-    <informalexample>
-<programlisting>
-initlocation PGDATA2
-</programlisting>
-    </informalexample>
-    Then you can restart the server.
-   </para>
-
-   <para>
-    To create a database within the new location, use the command
-<synopsis>
-CREATE DATABASE <replaceable>name</> WITH LOCATION = '<replaceable>location</>'
-</synopsis>
-    where <replaceable>location</> is the environment variable you
-    used, <envar>PGDATA2</> in this example. The <command>createdb</>
-    command has the option <option>-D</> for this purpose.
-   </para>
-
-   <para>
-    Databases created in alternative locations can be
-    accessed and dropped like any other database.
-   </para>
-
-   <note>
-    <para>
-     It can also be possible to specify absolute paths directly to the
-     <command>CREATE DATABASE</> command without defining environment
-     variables. This is disallowed by default because it is a security
-     risk. To allow it, you must compile <productname>PostgreSQL</> with
-     the C preprocessor macro <literal>ALLOW_ABSOLUTE_DBPATHS</>
-     defined. One way to do this is to run the compilation step like
-     this:
-<programlisting>
-gmake CPPFLAGS=-DALLOW_ABSOLUTE_DBPATHS all
-</programlisting>
-    </para>
-   </note>
-
-  </sect2>
- </sect1>
-
- <sect1 id="manage-ag-dropdb">
-  <title>Destroying a Database</title>
-
-  <para>
-   Databases are destroyed with the command <command>DROP DATABASE</command>:
-<synopsis>
-DROP DATABASE <replaceable>name</>
-</synopsis>
-   Only the owner of the database (i.e., the user that created it), 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, 
-   which 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:
-<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>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/manage.sgml b/doc/src/sgml/manage.sgml
deleted file mode 100644
index 43dd8d5a955..00000000000
--- a/doc/src/sgml/manage.sgml
+++ /dev/null
@@ -1,228 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/manage.sgml,v 1.21 2002/01/20 22:19:56 petere Exp $
--->
-
- <Chapter Id="manage">
-  <Title>Managing a Database</Title>
-
-  <comment>
-   This section is currently a thinly disguised copy of the
-   Tutorial. Needs to be augmented.
-    - thomas 1998-01-12
-  </comment>
-
-  <Para>
-   Although the <FirstTerm>site administrator</FirstTerm> is responsible for overall management 
-   of the <ProductName>PostgreSQL</ProductName> installation, some databases within the
-   installation may be managed by another person, 
-   designated the <FirstTerm>database administrator</FirstTerm>.
-   This assignment of responsibilities occurs when a database is created. 
-   A user may be assigned explicit privileges to create databases and/or to create new users. 
-   A user assigned both privileges can perform most administrative tasks
-   within <ProductName>PostgreSQL</ProductName>, but will
-   not by default have the same operating system privileges as the site administrator.
-  </Para>
-
-  <Para>
-   The <citetitle>Administrator's Guide</> covers these topics in
-   more detail.
-  </Para>
-
-  <Sect1 id="db-creation">
-   <Title>Database Creation</Title>
-
-   <Para>
-    Databases are created by the <Command>CREATE DATABASE</Command>
-    command issued from within
-    <ProductName>PostgreSQL</ProductName>. <Application>createdb</Application>
-    is a shell script provided to give the same functionality from the
-    Unix command line.
-   </Para>
-
-   <Para>
-    The <ProductName>PostgreSQL</ProductName> backend must be running for either method
-    to succeed, and the user issuing the command must be the <ProductName>PostgreSQL</ProductName>
-    <FirstTerm>superuser</FirstTerm> or have been assigned database creation privileges by the
-    superuser.
-   </Para>
-
-   <Para>
-    To create a new database named <literal>mydb</literal> from the command line, type
-<ProgramListing>
-% createdb mydb
-</ProgramListing>
-
-    and to do the same from within <Application>psql</Application> type
-<ProgramListing>
-=> CREATE DATABASE mydb;
-</ProgramListing>
-   </Para>
-
-   <Para>
-    If you do not have the privileges required to create a database, you will see
-    the following:
-<ProgramListing>
-ERROR:  CREATE DATABASE: Permission denied.
-</ProgramListing>
-   </Para>
-
-   <Para>
-    You  automatically  become  the
-    database  administrator  of  the database you just created.  
-    Database names must  have  an  alphabetic  first
-    character and are limited to 31 characters in length.
-    <ProductName>PostgreSQL</ProductName>  allows  you to create any number of
-    databases at a  given  site.  
-   </Para>
-
-  <Para>
-   The <citetitle>Administrator's Guide</> discusses database creation
-   in more detail, including advanced options of the <command>CREATE
-   DATABASE</> command.
-  </Para>
-
-  </Sect1>
-
-<Sect1 id="db-accessing">
-<Title>Accessing a Database</Title>
-
-<Para>
-     Once you have constructed a database, you can access it
-     by:
-
-    <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       Running the <productname>PostgreSQL</productname> interactive
-       terminal program, called <application>psql</application>, which allows you
-       to interactively enter, edit, and execute
-       <acronym>SQL</acronym> commands.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Using an existing graphical frontend tool like
-       <application>PgAccess</application> or
-       <application>ApplixWare</application> (via
-       <acronym>ODBC</acronym>) 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 <citetitle>The PostgreSQL Programmer's
-       Guide</citetitle>.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-You probably want to start up <Application>psql</Application>, 
-to try out the examples in this manual.
- It can be activated for the <Database>mydb</Database>
-     database by typing the command:
-<ProgramListing>
-% psql mydb
-</ProgramListing>
-
-     You will be greeted with the following message:
-<ProgramListing>
-Welcome to psql, the PostgreSQL interactive terminal.
- 
-Type:  \copyright for distribution terms
-       \h for help with SQL commands
-       \? for help on internal slash commands
-       \g or terminate with semicolon to execute query
-       \q to quit
-
-mydb=>
-</ProgramListing>
-</Para>
-
-<Para>
-This prompt indicates that <command>psql</command> is listening
-  to you and that you can type <Acronym>SQL</Acronym> queries into a
-     work space maintained by the terminal monitor.
-The <Application>psql</Application> program itself responds to special
-commands  that  begin
-     with  the  backslash  character, <literal>\</literal>.  For example, you
-     can get help on the syntax of various
- <ProductName>PostgreSQL</ProductName> <Acronym>SQL</Acronym> commands by typing:
-<ProgramListing>
-mydb=> \h
-</ProgramListing>
-
-     Once  you  have finished entering your queries into the
-     work space, you can pass the contents of  the  work space
-     to the <ProductName>PostgreSQL</ProductName> server by typing:
-<ProgramListing>
-mydb=> \g
-</ProgramListing>
-
-     This  tells  the  server  to process the query.  If you
-     terminate your query with a semicolon, the  <literal>\g</literal> is  not
-     necessary.   
-<Application>psql</Application> will automatically process semicolon terminated queries.
-     To read queries from a file,  say  <filename>myFile</filename>,  instead  of
-     entering them interactively, type:
-<ProgramListing>
-mydb=> \i myFile
-</ProgramListing>
-
-     To get out of <Application>psql</Application> and return to Unix, type
-<ProgramListing>
-mydb=> \q
-</ProgramListing>
-
-     and  <Application>psql</Application>  will  quit  and  return  you to your command
-     shell. (For more escape codes, type <Command>\?</Command> at  the  <command>psql</command>
-     prompt.)
-     White  space  (i.e.,  spaces, tabs and newlines) may be
-     used freely in <Acronym>SQL</Acronym> queries.  Single-line comments  are  denoted  by
-     <literal>--</literal>.   Everything  after the dashes up to the end of the
-     line is ignored. Multiple-line comments, and comments within a line,
-     are denoted by <literal>/* ... */</literal>.
-</Para>
-
-</Sect1>
-     
-<Sect1 id="db-destroy">
-<Title>Destroying a Database</Title>
-
-<Para>
-     If you are the owner of the  database
-     <Database>mydb</Database>,  you can destroy it using the SQL command
-<ProgramListing>
-=> DROP DATABASE mydb;
-</ProgramListing>
-     or the Unix shell script
-<ProgramListing>
-% dropdb mydb
-</ProgramListing>
-     This action physically removes all of the Unix files
-     associated  with  the database and cannot be undone, so
-     this should only be done with a great deal of forethought.
-</Para>
-</Sect1>
-
-</Chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
deleted file mode 100644
index 88b7e29a924..00000000000
--- a/doc/src/sgml/monitoring.sgml
+++ /dev/null
@@ -1,555 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/monitoring.sgml,v 1.7 2002/03/22 19:20:14 petere Exp $
--->
-
-<chapter id="monitoring">
- <title>Monitoring Database Activity</title>
-
- <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 <firstterm>statistics collector</>,
-   but one should not neglect regular Unix monitoring programs such as
-   <command>ps</> and <command>top</>.  Also, once one has identified a
-   poorly-performing query, further investigation may be needed using
-   <productname>PostgreSQL</productname>'s <command>EXPLAIN</> command.
-   The <citetitle>User's Guide</citetitle> 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>
-
-  <para>
-   On most 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 postmaster -i
-postgres   963  0.0  1.1  7084 1472 pts/1    SN   13:17   0:00 postgres: stats buffer 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
-   <firstterm>postmaster</>, the master server process.  The command arguments
-   shown for it are the same ones given when it was launched.  The next two
-   processes implement the statistics collector, which will be described in
-   detail in the next section.  (These 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 connection source host items remain the same for
-  the life of the client connection, but the activity indicator changes.
-  The activity may be <literal>idle</> (ie, waiting for a client command),
-  <literal>idle in transaction</> (waiting for client inside a BEGIN block),
-  or a command type name such as <literal>SELECT</>.  Also,
-  <literal>waiting</> is attached if the server is presently waiting
-  on a lock held by another server process.  In the above example we can infer
-  that process 1003 is waiting for process 1016 to complete its transaction and
-  thereby release some lock or other.
-  </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 <command>w</command>
-  flags, not just one. In addition, your original invocation of the
-  <application>postmaster</application> must have a shorter
-  <command>ps</command> status display than that provided by each
-  backend.   If you fail to do all three things, the <command>ps</>
-  output for each backend will be the original <application>postmaster</>
-  command line.
-  </para>
-  </tip>
-
-
-
- </sect1>
-
- <sect1 id="monitoring-stats">
-  <title>Statistics Collector</Title>
-
-  <indexterm zone="monitoring-stats">
-   <primary>statistics</primary>
-  </indexterm>
-
-  <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 supports
-   determining the exact query currently being executed by other server
-   processes.
-  </para>
-
- <sect2 id="monitoring-stats-setup">
-  <title>Statistics Collection Configuration</Title>
-
-  <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 variables that are normally set in
-   <filename>postgresql.conf</> (see <xref linkend="runtime-config"> for
-   details about setting configuration variables).
-  </para>
-
-  <para>
-   The variable <varname>STATS_START_COLLECTOR</varname> must be set to
-   <literal>true</> for the statistics collector to
-   be launched at all.  This is the default and recommended setting,
-   but it may be turned off if you have no interest in statistics and
-   want to squeeze out every last drop of overhead.  (The savings is
-   likely to be small, however.)  Note that this option
-   cannot be changed while the server is running.
-  </para>
-
-  <para>
-   The variables <varname>STATS_COMMAND_STRING</varname>,
-   <varname>STATS_BLOCK_LEVEL</varname>,
-   and <varname>STATS_ROW_LEVEL</varname> control how much information is
-   actually sent to the collector, and thus determine how much run-time
-   overhead occurs.  These respectively determine whether a server process
-   sends its current command string, disk-block-level access statistics, and
-   row-level access statistics to the collector.  Normally these variables 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 server
-   processes using the <command>SET</> command.  (To prevent ordinary users
-   from hiding their activity from the administrator, only superusers are
-   allowed to change these variables with <command>SET</>.)
-  </para>
-
-   <important>
-    <para>
-     Since the variables <varname>STATS_COMMAND_STRING</varname>,
-     <varname>STATS_BLOCK_LEVEL</varname>,
-     and <varname>STATS_ROW_LEVEL</varname>
-     default to <literal>false</>, no statistics are actually collected
-     in the default configuration!  You must turn one or more of them on
-     before you will get useful results from the statistical display
-     functions.
-    </para>
-   </important>
-
- </sect2>
-
- <sect2 id="monitoring-stats-views">
-  <title>Viewing Collected Statistics</Title>
-
-  <para>
-   Several predefined views 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 access counts to the collector
-   just before waiting for another client command; so a query still in
-   progress does not affect the displayed totals.  Also, the collector itself
-   emits new totals at most once per PGSTAT_STAT_INTERVAL (500 milliseconds
-   by default).  So the displayed totals lag behind actual activity.
-  </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 totals emitted by
-   the collector process.  It then continues to use this snapshot for all
-   statistical views and functions until the end of its current transaction.
-   So the statistics will appear not to change as long as you continue the
-   current 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.
-  </para>
-
-  <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</></entry>
-      <entry>One row per server process, showing process PID, database,
-      user, and current query.  The current query column is only available
-      to superusers; for others it reads as NULL.  (Note that because of
-      the collector's reporting delay, current query will only be up-to-date
-      for long-running queries.)</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_database</></entry>
-      <entry>One row per database, showing number of active backends,
-      total transactions committed and total rolled back in that database,
-      total disk blocks read, and total number of buffer hits (ie, block
-      read requests avoided by finding the block already in buffer cache).
-     </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_all_tables</></entry>
-      <entry>For each table in the current database, total numbers of
-      sequential and index scans, total numbers of tuples returned by
-      each type of scan, and totals of tuple insertions, updates,
-      and deletes.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_sys_tables</></entry>
-      <entry>Same as pg_stat_all_tables, except that only system tables
-      are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_user_tables</></entry>
-      <entry>Same as pg_stat_all_tables, except that only user tables
-      are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_all_indexes</></entry>
-      <entry>For each index in the current database, the total number
-      of index scans that have used that index, the number of index tuples
-      read, and the number of successfully fetched heap tuples (this may
-      be less when there are index entries pointing to expired heap tuples).
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_sys_indexes</></entry>
-      <entry>Same as pg_stat_all_indexes, except that only indexes on
-      system tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_stat_user_indexes</></entry>
-      <entry>Same as pg_stat_all_indexes, except that only indexes on
-      user tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_all_tables</></entry>
-      <entry>For each table in the current database, the total number of disk
-      blocks read from that table, the number of buffer hits, the numbers of
-      disk blocks read and buffer hits in all the indexes of that table,
-      the numbers of disk blocks read and buffer hits from the table's
-      auxiliary TOAST table (if any), and the numbers of disk blocks read
-      and buffer hits for the TOAST table's index.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_sys_tables</></entry>
-      <entry>Same as pg_statio_all_tables, except that only system tables
-      are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_user_tables</></entry>
-      <entry>Same as pg_statio_all_tables, except that only user tables
-      are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_all_indexes</></entry>
-      <entry>For each index in the current database, the numbers of
-      disk blocks read and buffer hits in that index.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_sys_indexes</></entry>
-      <entry>Same as pg_statio_all_indexes, except that only indexes on
-      system tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_user_indexes</></entry>
-      <entry>Same as pg_statio_all_indexes, except that only indexes on
-      user tables are shown.</entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_all_sequences</></entry>
-      <entry>For each sequence object in the current database, the numbers
-      of disk blocks read and buffer hits in that sequence.
-      </entry>
-     </row>
-
-     <row>
-      <entry><structname>pg_statio_sys_sequences</></entry>
-      <entry>Same as 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</></entry>
-      <entry>Same as pg_statio_all_sequences, except that only user
-      sequences are shown.</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>
-   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.
-  </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.  The per-database access functions accept a database OID to
-   identify which database to report on.  The per-table and per-index
-   functions accept a table or index OID (note that only tables and indexes
-   in the current
-   database can be seen with these functions).  The per-backend access
-   functions accept a backend ID number, which ranges from one to the number
-   of currently active backends.
-  </para>
-
-  <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><function>pg_stat_get_db_numbackends</function>(<type>oid</type>)</entry>
-      <entry><type>integer</type></entry>
-      <entry>
-       Number of active backends in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_db_xact_commit</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Transactions committed in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_db_xact_rollback</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Transactions rolled back in database
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_db_blocks_fetched</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block fetch requests for database
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_db_blocks_hit</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block requests found in cache for database
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_numscans</function>(<type>oid</type>)</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><function>pg_stat_get_tuples_returned</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples read by sequential scans when argument is a table,
-       or number of index tuples read when argument is an index
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_tuples_fetched</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of valid (unexpired) table tuples fetched by sequential scans
-       when argument is a table, or fetched by index scans using this index
-       when argument is an index
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_tuples_inserted</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples inserted into table
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_tuples_updated</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples updated in table
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_tuples_deleted</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of tuples deleted from table
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_blocks_fetched</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block fetch requests for table or index
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_blocks_hit</function>(<type>oid</type>)</entry>
-      <entry><type>bigint</type></entry>
-      <entry>
-       Number of disk block requests found in cache for table or index
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_backend_idset</function>()</entry>
-      <entry><type>set of integer</type></entry>
-      <entry>
-       Set of currently active backend IDs (from 1 to N where N is the
-       number of active backends).  See usage example below.
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_backend_pid</function>(<type>integer</type>)</entry>
-      <entry><type>integer</type></entry>
-      <entry>
-       PID of backend process
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_backend_dbid</function>(<type>integer</type>)</entry>
-      <entry><type>oid</type></entry>
-      <entry>
-       Database ID of backend process
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_backend_userid</function>(<type>integer</type>)</entry>
-      <entry><type>oid</type></entry>
-      <entry>
-       User ID of backend process
-      </entry>
-     </row>
-
-     <row>
-      <entry><function>pg_stat_get_backend_activity</function>(<type>integer</type>)</entry>
-      <entry><type>text</type></entry>
-      <entry>
-       Current query of backend process (NULL if caller is not superuser)
-      </entry>
-     </row>
-    </tbody>
-   </tgroup>
-  </table>
-
-  <para>
-  Note: blocks_fetched minus blocks_hit gives the number of kernel read()
-  calls issued for the table, index, or database; but the actual number of
-  physical reads is usually lower due to kernel-level buffering.
-  </para>
-
-  <para>
-   The function <function>pg_stat_get_backend_idset</function> provides
-   a convenient way to generate one row for each active backend.  For
-   example, to show the PIDs and current queries of all backends:
-
-<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>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
deleted file mode 100644
index 7c65bb35305..00000000000
--- a/doc/src/sgml/mvcc.sgml
+++ /dev/null
@@ -1,845 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v 2.25 2002/05/30 20:45:18 tgl Exp $
--->
-
- <chapter id="mvcc">
-  <title>Multiversion Concurrency Control</title>
-
-  <indexterm>
-   <primary>concurrency</primary>
-  </indexterm>
-
-  <abstract>
-   <para>
-    Multiversion Concurrency Control
-    (MVCC)
-    is an advanced technique for improving database performance in a
-    multiuser environment. 
-    Vadim Mikheev (<email>vadim@krs.ru</email>) provided
-    the implementation for <productname>PostgreSQL</productname>.
-   </para>
-  </abstract>
-
-  <sect1 id="mvcc-intro">
-   <title>Introduction</title>
-
-   <para>
-    Unlike most other database systems which use locks for concurrency control,
-    <productname>PostgreSQL</productname>
-    maintains data consistency by using a multiversion model. 
-    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.
-   </para>
-
-   <para>
-    The main difference between multiversion and lock models is that
-    in MVCC locks acquired for querying (reading) data don't conflict
-    with locks acquired for writing data, and so reading never blocks
-    writing and writing never blocks reading.
-   </para>
-
-   <para>
-    Table- and row-level locking facilities are also available in
-    <productname>PostgreSQL</productname> for applications that cannot
-    adapt easily to MVCC behavior.  However, proper use of MVCC will
-    generally provide better performance than locks.
-   </para>
-  </sect1>
-
-  <sect1 id="transaction-iso">
-   <title>Transaction Isolation</title>
-
-   <para>
-    The <acronym>ANSI</acronym>/<acronym>ISO</acronym> <acronym>SQL</acronym>
-    standard defines four levels of transaction
-    isolation in terms of three phenomena that must be prevented 
-    between concurrent transactions.
-    These undesirable phenomena are:
-
-    <variablelist>
-     <varlistentry>
-      <term>
-       dirty reads
-       <indexterm><primary>dirty reads</primary></indexterm>
-      </term>
-     <listitem>
-      <para>
-	A transaction reads data written by a concurrent uncommitted transaction.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       non-repeatable reads
-       <indexterm><primary>non-repeatable reads</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 reads</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>isolation levels</primary>
-    </indexterm>
-    The four transaction isolation levels and the corresponding
-    behaviors are described in <xref linkend="mvcc-isolevel-table">.
-
-    <table tocentry="1" id="mvcc-isolevel-table">
-     <title><acronym>SQL</acronym> Transaction Isolation Levels</title>
-     <titleabbrev>Isolation Levels</titleabbrev>
-     <tgroup cols="4">
-      <thead>
-       <row>
-	<entry>
-         Isolation Level
-	</entry>
-	<entry>
-	 Dirty Read
-	</entry>
-	<entry>
-	 Non-Repeatable 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>
-
-   <para>
-    <productname>PostgreSQL</productname>
-    offers the read committed and serializable isolation levels.
-   </para>
-  </sect1>
-
-  <sect1 id="xact-read-committed">
-   <title>Read Committed Isolation Level</title>
-
-   <indexterm>
-    <primary>isolation levels</primary>
-    <secondary>read committed</secondary>
-   </indexterm>
-
-   <para>
-    <firstterm>Read Committed</firstterm>
-    is the default isolation level in <productname>PostgreSQL</productname>. 
-    When a transaction runs on this isolation level,
-    a <command>SELECT</command> query sees only data committed before the
-    query began; it never sees either uncommitted data or changes committed
-    during query execution by concurrent transactions.  (However, the
-    <command>SELECT</command> does see the effects of previous updates
-    executed within its own transaction, even though they are not yet
-    committed.)  In effect, a <command>SELECT</command> query
-    sees a snapshot of the database as of the instant that that query
-    begins to run.  Notice that two successive <command>SELECT</command>s 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> and <command>SELECT
-    FOR UPDATE</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 query start time.  However, such a target
-    row may have already been updated (or deleted or marked for update) 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 query search condition (<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,
-    starting from the updated version of the row.
-   </para>
-
-   <para>
-    Because of the above rule, it is possible for updating queries to see
-    inconsistent snapshots --- they can see the effects of concurrent updating
-    queries that affected the same rows they are trying to update, but they
-    do not see effects of those queries on other rows in the database.
-    This behavior makes Read Committed mode unsuitable for queries 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 from the updated
-    version of the account's row.  Because each query is affecting only a
-    predetermined row, letting it see the updated version of the row does
-    not create any troublesome inconsistency.
-   </para>
-
-   <para>
-    Since in Read Committed mode each new query starts with a new snapshot
-    that includes all transactions committed up to that instant, subsequent
-    queries in the same transaction will see the effects of the committed
-    concurrent transaction in any case.  The point at issue here is whether
-    or not within a <emphasis>single</> query we see 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, for applications that do complex queries and updates, it may
-    be necessary to guarantee a more rigorously consistent view of the
-    database than the Read Committed mode provides.
-   </para>
-  </sect1>
-
-  <sect1 id="xact-serializable">
-   <title>Serializable Isolation Level</title>
-
-   <indexterm>
-    <primary>isolation levels</primary>
-    <secondary>read serializable</secondary>
-   </indexterm>
-
-   <para>
-    <firstterm>Serializable</firstterm> 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, applications using this level must
-    be prepared to retry transactions due to serialization failures.
-   </para>
-
-   <para>
-    When a transaction is on the serializable level,
-    a <command>SELECT</command> query sees only data committed before the
-    transaction began; it never sees either uncommitted data or changes
-    committed
-    during transaction execution by concurrent transactions.  (However, the
-    <command>SELECT</command> does see the effects of previous updates
-    executed within its own transaction, even though they are not yet
-    committed.)  This is different from Read Committed in that the
-    <command>SELECT</command>
-    sees a snapshot as of the start of the transaction, not as of the start
-    of the current query within the transaction.  Successive
-    <command>SELECT</command>s within a single transaction always see the same
-    data.
-   </para>
-
-   <para>
-    <command>UPDATE</command>, <command>DELETE</command> and <command>SELECT
-    FOR UPDATE</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 may have already been updated (or deleted or marked for update) by
-    another concurrent transaction by the time it is found.  In this case, the
-    serializable 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 serializable transaction can proceed
-    with updating the originally found row.  But if the first updater commits
-    (and actually updated or deleted the row, not just selected it for update)
-    then the serializable transaction will be rolled back with the message
-
-<screen>
-ERROR:  Can't serialize access due to concurrent update
-</screen>
-
-    because a serializable transaction cannot modify rows changed by
-    other transactions after the serializable transaction began.
-   </para>
-
-   <para>
-    When the application receives this error message, it should abort
-    the current transaction and then retry the whole transaction from
-    the beginning.  The second time through, the transaction sees 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 may need to be retried --- read-only
-    transactions will never have serialization conflicts.
-   </para>
-
-   <para>
-    The Serializable mode provides a rigorous guarantee that each
-    transaction sees a wholly consistent view of the database.  However,
-    the application has to be prepared to retry transactions when concurrent
-    updates make it impossible to sustain the illusion of serial execution.
-    Since the cost of redoing complex transactions may be significant,
-    this mode is recommended only when updating transactions contain logic
-    sufficiently complex that they may give wrong answers in Read
-    Committed mode.  Most commonly, Serializable mode is necessary when
-    a transaction performs several successive queries that must see
-    identical views of the database.
-   </para>
-  </sect1>
-
-  <sect1 id="explicit-locking">
-   <title>Explicit Locking</title>
-
-   <indexterm>
-    <primary>locking</primary>
-   </indexterm>
-
-   <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 MVCC
-    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>ALTER TABLE</> cannot be executed
-    concurrently with other operations on the same table.)
-   </para>
-
-  <sect2 id="locking-tables">
-   <title>Table-Level Locks</title>
-
-   <para>
-    The list below shows the available lock modes and the contexts in
-    which they are used automatically by
-    <productname>PostgreSQL</productname>.
-    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 --- 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.  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 may acquire
-    <literal>ACCESS EXCLUSIVE</literal> lock and later acquire
-    <literal>ACCESS SHARE</literal> lock on the same table.)  Nonconflicting
-    lock modes may be held concurrently by many transactions.  Notice in
-    particular that some lock modes are self-conflicting (for example,
-    <literal>ACCESS EXCLUSIVE</literal> cannot be held by more than one
-    transaction at a time) while others are not self-conflicting (for example,
-    <literal>ACCESS SHARE</literal> can be held by multiple transactions).
-    Once acquired, a lock mode is held till end of transaction.
-   </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 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> command acquires 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</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
-	 query that modifies the 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 VACUUMs.
-	</para>
-
-	<para>
-	 Acquired by <command>VACUUM</command> (without <option>FULL</option>).
-	</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>.
-	</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.
-	</para>
-
-	<para>
-         This lock mode is not automatically acquired by any
-         <productname>PostgreSQL</productname> 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>,
-	 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 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>ALTER TABLE</command>, <command>DROP
-	 TABLE</command>, and <command>VACUUM FULL</command> commands.
-	 This is also the default lock mode for <command>LOCK TABLE</command>
-         statements that do not specify a mode explicitly.
-	</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-
-     <note>
-      <para>
-       Only an <literal>ACCESS EXCLUSIVE</literal> lock blocks a
-       <command>SELECT</command> (without <option>FOR UPDATE</option>)
-       statement.
-      </para>
-     </note>
-
-   </sect2>
-
-   <sect2 id="locking-rows">
-    <title>Row-Level Locks</title>
-
-    <para>
-     In addition to table-level locks, there are row-level locks.
-     A row-level lock on a specific row is automatically acquired when the
-     row is updated (or deleted or marked for update).  The lock is held
-     until the transaction commits or rolls back.
-     Row-level locks don't affect data
-     querying; they block <emphasis>writers to the same row</emphasis>
-     only.  To acquire a row-level lock on a row without actually
-     modifying the row, select the row with <command>SELECT FOR
-     UPDATE</command>.  Note that once a particular row-level lock is
-     acquired, the transaction may update the row multiple times without
-     fear of conflicts.
-    </para>
-
-    <para>
-     <productname>PostgreSQL</productname> doesn't remember any
-     information about modified rows in memory, so it has no limit to
-     the number of rows locked at one time.  However, locking a row
-     may cause a disk write; thus, for example, <command>SELECT FOR
-     UPDATE</command> will modify selected rows to mark them 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 tuple is fetched or
-     updated.  Application writers normally need not be concerned with
-     page-level locks, but we mention them for completeness.
-    </para>
-
-   </sect2>
-
-   <sect2 id="locking-deadlocks">
-    <title>Deadlocks</title>
-
-    <para>
-     Use of explicit locking can cause <firstterm>deadlocks</>, wherein
-     two (or more) transactions each hold locks that the other wants.
-     For example, if transaction 1 acquires exclusive lock on table A
-     and then tries to acquire exclusive lock on table B, while transaction
-     2 has already exclusive-locked table B and now wants 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 on.)
-    </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.  One should also ensure that the first
-     lock acquired on an object in a transaction is the highest mode that
-     will be needed for that object.  If it is not feasible to verify this
-     in advance, then deadlocks may be handled on-the-fly by retrying
-     transactions that are aborted due to deadlock.
-    </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>
-   </sect2>
-  </sect1>
-
-  <sect1 id="applevel-consistency">
-   <title>Data consistency checks at the application level</title>
-
-   <para>
-    Because readers in <productname>PostgreSQL</productname>
-    don't lock data, regardless of
-    transaction isolation level, data read by one transaction can be
-    overwritten by another concurrent transaction. In other words,
-    if a row is returned by <command>SELECT</command> it doesn't mean that
-    the row is still current at the instant it is returned (i.e., sometime
-    after the current query began).  The row might have been modified or
-    deleted by an already-committed transaction that committed after this one
-    started.
-    Even if the row is still valid <quote>now</quote>, it could be changed or
-    deleted
-    before the current transaction does a commit or rollback.
-   </para>
-
-   <para>
-    Another way to think about it is that each
-    transaction sees a snapshot of the database contents, and concurrently
-    executing transactions may very well see different snapshots.  So the
-    whole concept of <quote>now</quote> is somewhat suspect anyway.
-    This is not normally
-    a big problem if the client applications are isolated from each other,
-    but if the clients can communicate via channels outside the database
-    then serious confusion may ensue.
-   </para>
-
-   <para>
-    To ensure the current validity 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.
-    (<command>SELECT FOR UPDATE</command> locks 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.
-
-    <note>
-     <para>
-      Before version 6.5 <productname>PostgreSQL</productname>
-      used read-locks and so the
-      above consideration is also the case
-      when upgrading to 6.5 (or higher) from previous
-      <productname>PostgreSQL</productname> versions.
-     </para>
-    </note>
-   </para>
-
-   <para>
-    Global validity checks require extra thought under MVCC.  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 SELECT SUM(...) commands will not work reliably under
-    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 serializable transaction will give an accurate picture of the
-    effects of transactions that committed before the serializable transaction
-    started --- but one might legitimately wonder whether the answer is still
-    relevant by the time it is delivered.  If the serializable 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 locks to prevent concurrent changes, one should use
-    Read Committed mode, or in Serializable mode be careful to obtain the
-    lock(s) before performing queries.  An explicit lock obtained in a
-    serializable 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 may predate some now-committed
-    changes in the table.  A serializable transaction's snapshot is actually
-    frozen at the start of its first query (SELECT/INSERT/UPDATE/DELETE), so
-    it's possible to obtain explicit locks before the snapshot is
-    frozen.
-   </para>
-  </sect1>
-
-  <sect1 id="locking-indexes">
-   <title>Locking and Indexes</title>
-
-   <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>.
-   </para>
-
-   <para>
-    The various index types are handled as follows:
-
-    <variablelist>
-     <varlistentry>
-      <term>
-       <acronym>GiST</acronym> and R-Tree indexes
-      </term>
-      <listitem>
-       <para>
-	Share/exclusive index-level locks are used for read/write access.
-	Locks are released after statement is done.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       Hash indexes
-      </term>
-      <listitem>
-       <para>
-	Share/exclusive page-level locks are used for read/write access.
-	Locks are released after page is processed.
-       </para>
-
-       <para>
-	Page-level locks provide better concurrency than index-level ones
-	but are subject to deadlocks.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       B-tree indexes
-      </term>
-      <listitem>
-       <para>
-	Short-term share/exclusive page-level locks are used for
-	read/write access. Locks are released immediately after each index
-	tuple is fetched/inserted.
-       </para>
-
-       <para>
-	B-tree indexes provide the highest concurrency without deadlock
-	conditions.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    In short, B-tree indexes are the recommended index type for concurrent
-    applications.
-   </para>
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/nls.sgml b/doc/src/sgml/nls.sgml
deleted file mode 100644
index 75dc5859cd9..00000000000
--- a/doc/src/sgml/nls.sgml
+++ /dev/null
@@ -1,489 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/nls.sgml,v 1.4 2002/03/22 19:20:15 petere Exp $ -->
-
-<chapter id="nls">
- <docinfo>
-  <author>
-   <firstname>Peter</firstname>
-   <surname>Eisentraut</surname>
-  </author>
- </docinfo>
-
- <title>Native Language Support</title>
-
- <sect1 id="nls-translator">
-  <title>For the Translator</title>
-
-  <para>
-   <productname>PostgreSQL</>
-   programs (server and client) can issue their messages in
-   your favorite language -- 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
-   the <productname>PostgreSQL</> effort.  You do not have to be a
-   programmer at all
-   to do this.  This section explains how to help.
-  </para>
-
-  <sect2>
-   <title>Requirements</title>
-
-   <para>
-    We won't judge your language skills -- 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 libintl 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>.  (From CVS, you will still need
-    it.)  GNU gettext 0.10.36 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>
-
-   <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 may 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>
-
-   <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://lcweb.loc.gov/standards/iso639-2/englangn.html">ISO
-    639-1</ulink> two-letter language code (in lower case), 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
-    may also be named
-    <filename><replaceable>language</replaceable>_<replaceable>region</replaceable>.po</filename>
-    where <replaceable>region</replaceable> is the <ulink
-    url="http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1/en_listp1.html">ISO
-    3166-1</ulink> two-letter country code (in upper case), 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>.  What does the T stand for?  I
-    don't know.)  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 may appear, of course.)
-   </para>
-
-   <para>
-    As the underlying program or library changes, messages may 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.  For the case
-    where something went really wrong, the old PO file is saved with a
-    <filename>.po.old</filename> extension.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Editing the PO files</title>
-
-   <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, may 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 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 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 this case you can use this format:
-<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 % and come before any other format manipulators.
-       (This feature really exists in the <function>printf</function>
-       family of functions.  You may not have heard of it 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 may 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).
-      </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>
-
-  <para>
-   This section describes how to support native language support in a
-   program or library that is part of the
-   <productname>PostgreSQL</> distribution.
-   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 no NLS is
-     configured.)
-    </para>
-
-    <para>
-     This may tend to add a lot of clutter.  One common shortcut is to
-<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>elog()</function> in the backend.  Then you make this
-     function call <function>gettext</function> internally on all
-     input values.
-    </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>CATALOG_NAME</term>
-
-       <listitem>
-        <para>
-         The program name, as provided in the
-         <function>textdomain()</function> call.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>AVAIL_LANGUAGES</term>
-
-       <listitem>
-        <para>
-         List of provided translations -- empty in the beginning.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>GETTEXT_FILES</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>GETTEXT_TRIGGERS</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).
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </step>
-
-  </procedure>
-
-  <para>
-   The build system will automatically take care of building and
-   installing the message catalogs.
-  </para>
-
-  <para>
-   To ease the translation of messages, here are some guidelines:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Do not construct sentences at run-time out of laziness, like
-<programlisting>
-printf("Files where %s.\n", flag ? "copied" : "removed");
-</programlisting>
-      The word order within the sentence may be different in other
-      languages.
-     </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.  We may have a solution for this in
-      the future, but for now this is best avoided altogether.  You
-      could write:
-<programlisting>
-printf("number of copied files: %d", n);
-</programlisting>
-     </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>
- </sect1>
-
-</chapter>
diff --git a/doc/src/sgml/notation.sgml b/doc/src/sgml/notation.sgml
deleted file mode 100644
index e95735e11e1..00000000000
--- a/doc/src/sgml/notation.sgml
+++ /dev/null
@@ -1,76 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.19 2001/11/23 22:06:20 tgl Exp $
--->
-
-<sect1 id="notation">
- <title>Terminology and Notation</title>
-
- <para>
-  The terms <quote>PostgreSQL</quote> and <quote>Postgres</quote> will be
-  used interchangeably to refer to the software that accompanies this
-  documentation.
- </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
-  <productname>PostgreSQL</productname> system.  These terms should not
-  be interpreted too narrowly; this documentation set does not have fixed
-  presumptions about system administration procedures.
- </para>
-
- <para>
-  We use <filename>/usr/local/pgsql/</filename> as the root
-  directory of the installation and <filename>/usr/local/pgsql/data</filename>
-  as the directory with the database files.  These directories may vary
-  on your site, details can be derived in the <citetitle>Administrator's Guide</citetitle>.
- </para>
-
- <para>
-  In a command synopsis, brackets
-  (<literal>[</literal> and <literal>]</literal>) indicate an optional phrase or keyword.
-  Anything in braces
-  (<literal>{</literal> and <literal>}</literal>) and containing vertical bars
-  (<literal>|</literal>)
-  indicates that you must choose one alternative.
- </para>
-
- <para>
-  Examples will show commands executed from various accounts and programs.
-  Commands executed from a Unix shell may be preceded with a dollar sign
-  (<quote><literal>$</literal></quote>).  Commands executed from particular user
-  accounts such as <systemitem>root</> or <systemitem>postgres</> are specially flagged and explained.
-  <acronym>SQL</acronym> commands may be preceded with
-  <quote><literal>=&gt;</literal></quote>
-  or will have no leading prompt, depending on the context.
- </para>
-
- <note>
-  <para>
-   The notation for
-   flagging commands is not universally consistent throughout the
-   documentation set.
-   Please report problems to the documentation mailing list
-   <email>pgsql-docs@postgresql.org</email>.
-  </para>
- </note>
-
-</sect1>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/odbc.sgml b/doc/src/sgml/odbc.sgml
deleted file mode 100644
index cbc40624767..00000000000
--- a/doc/src/sgml/odbc.sgml
+++ /dev/null
@@ -1,805 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/odbc.sgml,v 1.30 2002/03/22 19:20:16 petere Exp $
--->
-
- <chapter id="odbc">
-  <docinfo>
-   <authorgroup>
-    <author>
-     <firstname>Tim</firstname>
-     <surname>Goeke</surname>
-    </author>
-    <author>
-     <firstname>Thomas</firstname>
-     <surname>Lockhart</surname>
-    </author>
-   </authorgroup>
-   <date>1998-10-21</date>
-  </docinfo>
-
-  <title>ODBC Interface</title>
-
-  <indexterm zone="odbc">
-   <primary>ODBC</primary>
-  </indexterm>
-
- <sect1 id="odbc-intro">
-  <title>Introduction</title>
-
-  <note>
-   <para>
-    Background information originally by Tim Goeke
-    (<email>tgoeke@xpressway.com</email>)
-   </para>
-  </note>
-
-  <para>
-   <acronym>ODBC</acronym> (Open Database Connectivity) is an abstract 
-   <acronym>API</acronym> 
-   that allows you to write applications that can interoperate
-   with various <acronym>RDBMS</acronym> servers.
-   <acronym>ODBC</acronym> provides a product-neutral interface 
-   between frontend applications and database servers,
-   allowing a user or developer to write applications that are 
-   portable between servers from different manufacturers..
-  </para>
-
-   <para>
-    The <acronym>ODBC</acronym> <acronym>API</acronym> matches up 
-    on the backend to an <acronym>ODBC</acronym>-compatible data source.
-    This could be anything from a text file to an Oracle or 
-    <productname>PostgreSQL</productname> <acronym>RDBMS</acronym>.
-   </para>
-
-   <para>
-    The backend access comes from <acronym>ODBC</acronym> drivers, 
-    or vendor-specific drivers that
-    allow data access.   <productname>psqlODBC</productname>, which is included in the <productname>PostgreSQL</> distribution, is such a driver,
-    along with others that are
-    available, such as the <productname>OpenLink</productname> <acronym>ODBC</acronym> drivers.
-   </para>
-
-   <para>
-    Once you write an <acronym>ODBC</acronym> application, 
-    you <emphasis>should</emphasis> be able to connect to <emphasis>any</emphasis>
-    back-end database, regardless of the vendor, as long as the database schema
-    is the same.
-   </para>
-
-   <para>
-    For example. you could have <productname>MS SQL Server</productname>
-    and <productname>PostgreSQL</productname> servers that have
-    exactly the same data.  Using <acronym>ODBC</acronym>, 
-    your Windows application would make exactly the
-    same calls and the back-end data source would look the same (to the Windows
-    application).
-   </para>
-  </sect1>
-
-  <sect1 id="odbc-install">
-   <title>Installation</title>
-
-   <para>
-    In order to make use of an <acronym>ODBC</> driver there must
-    exist a <firstterm>driver manager</> on the system where the
-    <acronym>ODBC</> driver is to be used.  There are two free
-    <acronym>ODBC</> driver managers for Unix-like operating systems
-    known to us: <indexterm><primary>iODBC</primary></indexterm>
-    <ulink url="http://www.iodbc.org"><productname>iODBC</></ulink>
-    and <indexterm><primary>unixODBC</primary></indexterm> <ulink
-    url="http://www.unixodbc.org"><productname>unixODBC</></ulink>.
-    Instructions for installing these driver managers are to be found
-    in the respective distribution.  Software that provides database
-    access through <acronym>ODBC</acronym> should provide its own
-    driver manager (which may well be one of these two).  Having said
-    that, any driver manager that you can find for your platform
-    should support the <productname>PostgreSQL</> <acronym>ODBC</>
-    driver, or any other <acronym>ODBC</> driver for that matter.
-   </para>
-
-   <note>
-    <para>
-     The <productname>unixODBC</> distribution ships with a
-     <productname>PostgreSQL</> <acronym>ODBC</> driver of its own,
-     which is similar to the one contained in the
-     <productname>PostgreSQL</> distribution.  It is up to you which
-     one you want to use.  We plan to coordinate the development of
-     both drivers better in the future.
-    </para>
-   </note>
-
-   <para>
-    To install the <acronym>ODBC</> you simply need to supply the
-    <option>--enable-odbc</> option to the <filename>configure</>
-    script when you are building the entire <productname>PostgreSQL</>
-    distribution. The library will then automatically be built and
-    installed with the rest of the programs. If you forget that option
-    or want to build the ODBC driver later you can change into the
-    directory <filename>src/interfaces/odbc</> and do <literal>make</>
-    and <literal>make install</> there.
-   </para>
-
-   <para>
-    It is also possible to build the driver to be specifically tuned
-    for use with <productname>iODBC</> or <productname>unixODBC</>.
-    This means in particular that the driver will use the driver
-    manager's routines to process the configuration files, which is
-    probably desirable since it creates a more consistent
-    <acronym>ODBC</> environment on your system.  If you want to do
-    that, then supply the <filename>configure</> options
-    <option>--with-iodbc</> or <option>--with-unixodbc</> (but not
-    both).
-   </para>
-
-   <para>
-    If you build a <quote>stand-alone</quote> driver (not tied to
-    <productname>iODBC</> or <productname>unixODBC</>), then you can
-    specify where the driver should look for the configuration file
-    <filename>odbcinst.ini</>.  By default it will be the directory
-    <filename>/usr/local/pgsql/etc/</>, or equivalent, depending on
-    what <option>--prefix</> and/or <option>--sysconfdir</> options
-    you supplied to <filename>configure</>.  To select a specific
-    location outside the <productname>PostgreSQL</> installation
-    layout, use the <option>--with-odbcinst</> option.  To be most
-    useful, it should be arranged that the driver and the driver
-    manager read the same configuration file.
-   </para>
-
-   <para>
-    <indexterm><primary>odbc.sql</></>
-    Additionally, you should install the ODBC catalog extensions.  That will
-    provide a number of functions mandated by the ODBC standard that are not
-    supplied by <productname>PostgreSQL</> by default. The file
-    <filename>/usr/local/pgsql/share/odbc.sql</> (in the default installation layout)
-    contains the appropriate definitions, which you can install as follows:
-<programlisting>
-psql -d template1 -f <replaceable>LOCATION</>/odbc.sql
-</programlisting>
-    where specifying <literal>template1</literal> as the target
-    database will ensure that all subsequent new databases will have
-    these same definitions.  If for any reason you want to remove
-    these functions again, run the file
-    <filename>odbc-drop.sql</filename> through
-    <command>psql</command>.
-   </para>
-  </sect1>
-
-  <sect1 id="odbc-config">
-   <title>Configuration Files</title>
-
-   <indexterm zone="odbc-config"><primary>.odbc.ini</></>
-
-   <para>
-    <filename>~/.odbc.ini</filename> contains user-specified access information 
-    for the <productname>psqlODBC</productname> driver. 
-    The file uses conventions typical for <productname>Windows</productname> 
-    Registry files.
-   </para>
-
-   <para>
-    The <filename>.odbc.ini</filename> file has three required sections. 
-    The first is <literal>[ODBC Data Sources]</literal>
-    which is a list of arbitrary names and descriptions for each database 
-    you wish to access. The second required section is the 
-    Data Source Specification and there will be one of these sections
-    for each database. 
-    Each section must be labeled with the name given in 
-    <literal>[ODBC Data Sources]</literal> and must contain the following entries: 
-
-<programlisting>
-Driver = <replaceable>prefix</replaceable>/lib/libpsqlodbc.so
-Database = <replaceable>DatabaseName</replaceable>
-Servername = localhost
-Port = 5432
-</programlisting>
-
-    <tip>
-     <para>
-      Remember that the <productname>PostgreSQL</productname> database name is
-      usually a single word, without path names of any sort. 
-      The <productname>PostgreSQL</productname> server manages the actual access
-      to the database, and you need only specify the name from the client.
-     </para>
-    </tip>
-
-    Other entries may be inserted to control the format of the display. 
-    The third required section is <literal>[ODBC]</literal> 
-    which must contain the <literal>InstallDir</literal> keyword 
-    and which may contain other options.
-   </para>
-
-   <para>
-    Here is an example <filename>.odbc.ini</filename> file, 
-    showing access information for three databases:
-
-<programlisting>
-[ODBC Data Sources]
-DataEntry = Read/Write Database
-QueryOnly = Read-only Database
-Test = Debugging Database
-Default = Postgres Stripped
-
-[DataEntry]
-ReadOnly = 0
-Servername = localhost
-Database = Sales
-
-[QueryOnly]
-ReadOnly = 1
-Servername = localhost
-Database = Sales
-
-[Test]
-Debug = 1
-CommLog = 1
-ReadOnly = 0
-Servername = localhost
-Username = tgl
-Password = "no$way"
-Port = 5432
-Database = test
-
-[Default]
-Servername = localhost
-Database = tgl
-Driver = /opt/postgres/current/lib/libpsqlodbc.so
-
-[ODBC]
-InstallDir = /opt/applix/axdata/axshlib
-</programlisting>
-   </para>
-  </sect1>
-
-  <sect1 id="odbc-windows">
-   <title><productname>Windows</productname> Applications</title>
-
-   <para>
-    In the real world, differences in drivers and the level of 
-    <acronym>ODBC</acronym> support
-    lessens the potential of <acronym>ODBC</acronym>:
-
-    <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       Access, Delphi, and Visual Basic all support <acronym>ODBC</acronym> directly.
-      </para>
-     </listitem>
-     <listitem>
-      <para>
-       Under C++, such as Visual C++, 
-       you can use the C++ <acronym>ODBC</acronym> <acronym>API</acronym>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In Visual C++, you can use the <classname>CRecordSet</classname> class, which wraps the 
-       <acronym>ODBC</acronym> <acronym>API</acronym>
-       set within an <application>MFC</application> 4.2 class.  This is the easiest route if you are doing
-       Windows C++ development under Windows NT.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <sect2>
-    <title>Writing Applications</title>
-
-    <para>
-     <quote>
-      If I write an application for <productname>PostgreSQL</productname> 
-      can I write it using <acronym>ODBC</acronym> calls
-      to the <productname>PostgreSQL</productname> server, 
-      or is that only when another database program 
-      like MS SQL Server or Access needs to access the data?
-     </quote>
-    </para>
-    <para>
-     The <acronym>ODBC</acronym> <acronym>API</acronym>
-     is the way to go.
-     For <productname>Visual C++</productname> coding you can find out more at
-     Microsoft's web site or in your <productname>Visual C++</productname>
-     documentation.
-    </para>
-
-    <para>
-     Visual Basic and the other <acronym>RAD</acronym> tools have <classname>Recordset</classname> objects 
-     that use <acronym>ODBC</acronym>
-     directly to access data.  Using the data-aware controls, you can quickly
-     link to the <acronym>ODBC</acronym> back-end database 
-     (<emphasis>very</emphasis> quickly).
-    </para>
-
-    <para>
-     Playing around with <productname>MS Access</> will help you sort this out.  Try using
-     <menuchoice><guimenu>File</><guimenuitem>Get External Data</></menuchoice>.
-    </para>
-
-    <tip>
-     <para>
-      You'll have to set up a <acronym>DSN</acronym> first.
-     </para>
-    </tip>
-
-   </sect2>
-  </sect1>
-
-  <sect1 id="odbc-applixware">
-   <title><application>ApplixWare</application></title>
-
-   <indexterm zone="odbc-applixware">
-    <primary>Applixware</primary>
-   </indexterm>
-
-   <para>
-    <productname>Applixware</productname> has an 
-    <acronym>ODBC</acronym> database interface
-    supported on at least some platforms. 
-    <productname>Applixware</productname> 4.4.2 has been
-    demonstrated under Linux with <productname>PostgreSQL</productname> 7.0 
-    using the <productname>psqlODBC</productname>
-    driver contained in the <productname>PostgreSQL</productname> distribution.
-   </para>
-
-   <sect2>
-    <title>Configuration</title>
-
-    <para>
-     <productname>Applixware</productname> must be configured correctly
-     in order for it to
-     be able to access the <productname>PostgreSQL</productname>
-     <acronym>ODBC</acronym> software drivers.
-    </para>
-
-    <procedure>
-     <title>Enabling <application>Applixware</application> Database Access</title>
-
-     <para>
-      These instructions are for the 4.4.2 release of
-      <productname>Applixware</productname> on <productname>Linux</productname>.
-      Refer to the <citetitle>Linux Sys Admin</citetitle> on-line book
-      for more detailed information.
-     </para>
-
-     <step performance="required">
-      <para>
-       You must modify <filename>axnet.cnf</filename> so that
-       <filename>elfodbc</filename> can
-       find <filename>libodbc.so</filename>
-       (the <acronym>ODBC</acronym> driver manager) shared library.
-       This library is included with the <application>Applixware</application> distribution,
-       but <filename>axnet.cnf</filename> needs to be modified to point to the 
-       correct location.
-      </para>
-
-      <para>
-       As root, edit the file
-       <filename><replaceable>applixroot</replaceable>/applix/axdata/axnet.cnf</filename>.
-      </para>
-
-      <substeps>
-
-       <step performance="required">
-	<para>
-	 At the bottom of <filename>axnet.cnf</filename>,
-	 find the line that starts with
-
-<programlisting>
-#libFor elfodbc /ax/<replaceable>...</replaceable>
-</programlisting>
-	</para>
-       </step>
-       <step performance="required">
-	<para>
-	 Change line to read
-
-<programlisting>
-libFor elfodbc <replaceable>applixroot</replaceable>/applix/axdata/axshlib/lib
-</programlisting>
-
-	 which will tell <literal>elfodbc</literal> to look in this directory
-	 for the <acronym>ODBC</acronym> support library.
-	 Typically <productname>Applix</productname> is installed in
-	 <filename>/opt</filename> so the full path would be
-	 <filename>/opt/applix/axdata/axshlib/lib</filename>,
-	 but if you have installed <productname>Applix</productname>
-	 somewhere else then change the path accordingly.
-	</para>
-       </step>
-      </substeps>
-     </step>
-
-     <step performance="required">
-      <para>
-       Create <filename>.odbc.ini</filename> as 
-       described in <xref linkend="odbc-config">.  You may also want to add the flag
-
-<programlisting>
-TextAsLongVarchar=0
-</programlisting>
-
-       to the database-specific portion of <filename>.odbc.ini</filename>
-       so that text fields will not be shown as <literal>**BLOB**</literal>.
-      </para>
-     </step>
-    </procedure>
-
-    <procedure>
-     <title>Testing <application>Applixware</application> ODBC Connections</title>
-
-     <step performance="required">
-      <para>
-       Bring up <application>Applix Data</application>
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Select the <productname>PostgreSQL</productname> database of interest.
-      </para>
-
-      <substeps>
-
-       <step performance="required">
-	<para>
-	 Select <menuchoice><guimenu>Query</guimenu><guimenuitem>Choose Server</guimenuitem></menuchoice>.  
-	</para>
-       </step>
-       <step performance="required">
-	<para>
-	 Select <guimenuitem>ODBC</guimenuitem>, and click <guibutton>Browse</guibutton>.
-	 The database you configured in <filename>.odbc.ini</filename>
-	 should be shown.  Make sure that the <guilabel>Host:</guilabel> field
-	 is empty (if it is not, <literal>axnet</> will try to contact <literal>axnet</> on another machine
-	 to look for the database).
-	</para>
-       </step>
-       <step performance="required">
-	<para>
-	 Select the database in the box that was launched by <guibutton>Browse</guibutton>,
-	 then click <guibutton>OK</guibutton>.
-	</para>
-       </step>
-       <step performance="required">
-	<para>
-	 Enter user name and password in the login identification dialog,
-	 and click <guibutton>OK</guibutton>.
-	</para>
-       </step>
-      </substeps>
-
-      <para>
-       You should see <guilabel>Starting elfodbc server</guilabel>
-       in the lower left corner of the
-       data window.  If you get an error dialog box, see the debugging section
-       below.
-      </para>
-     </step>
-     <step performance="required">
-      <para>
-       The <quote>Ready</quote> message will appear in the lower left corner of the data
-       window.  This indicates that you can now enter queries.
-      </para>
-     </step>
-     <step performance="required">
-      <para>
-       Select a table from
-       <menuchoice><guimenu>Query</><guimenuitem>Choose
-       tables</></menuchoice>, and then select
-       <menuchoice><guimenu>Query</><guimenuitem>Query</></menuchoice>
-       to access the database.  The first 50 or so rows from the table
-       should appear.
-      </para>
-     </step>
-    </procedure>
-   </sect2>
-
-   <sect2>
-    <title>Common Problems</title>
-
-    <para>
-     The following messages can appear while trying to make an
-     <acronym>ODBC</acronym> connection through 
-     <productname>Applix Data</productname>:
-
-     <variablelist>
-      <varlistentry>
-       <term>
-	<computeroutput>Cannot launch gateway on server</computeroutput>
-       </term>
-       <listitem>
-	<para>
-	 <literal>elfodbc</literal> can't find <filename>libodbc.so</filename>.  
-	 Check your <filename>axnet.cnf</filename>.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><computeroutput>
-	Error from ODBC Gateway:
-	IM003::[iODBC][Driver Manager]Specified driver could not be loaded</computeroutput>
-       </term>
-       <listitem>
-	<para>
-	 <filename>libodbc.so</filename> cannot find the driver listed in
-	 <filename>.odbc.ini</filename>. Verify the settings.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-	<computeroutput>Server: Broken Pipe</computeroutput>
-       </term>
-
-       <listitem>
-	<para>
-	 The driver process has terminated due to some other
-	 problem.  You might not have an up-to-date version
-	 of the <productname>PostgreSQL</productname>
-	 <acronym>ODBC</acronym> package.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-	<computeroutput>setuid to 256: failed to launch gateway</computeroutput>
-       </term>
-
-       <listitem>
-	<para>
-	 The September release of <application>Applixware</application> 4.4.1 (the first release with official
-	 <acronym>ODBC</acronym> support under Linux) shows problems when user names
-	 exceed eight (8) characters in length.
-	 Problem description contributed by Steve Campbell
-	 (<email>scampbell@lear.com</email>).
-	</para>
-       </listitem>
-      </varlistentry>
-
-     </variablelist>
-    </para>
-
-    <para>
-     <note>
-      <title>Author</title>
-
-      <para>
-       Contributed by Steve Campbell (<email>scampbell@lear.com</email>),
-       1998-10-20
-      </para>
-     </note>
-
-     The <application>axnet</application> program's security system
-     seems a little suspect. <application>axnet</application> does things
-     on behalf of the user and on a true
-     multiuser system it really should be run with root security 
-     (so it can read/write in each user's directory).  
-     I would hesitate to recommend this, however, since we have no idea what 
-     security holes this creates.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Debugging <application>Applixware</application> ODBC Connections</title>
-
-    <para>
-     One good tool for debugging connection problems uses the Unix system
-     utility <application>strace</application>.
-    </para>
-    <procedure>
-     <title>Debugging with <command>strace</command></title>
-
-     <step performance="required">
-      <para>
-       Start <application>Applixware</application>.
-      </para>
-     </step>
-     <step performance="required">
-      <para>
-       Start an <application>strace</application> on
-       the <literal>axnet</literal> process.  For example, if
-
-<screen>
-<prompt>$</prompt> <userinput>ps -aucx | grep ax</userinput>
-</screen>
-
-       shows
-
-<screen>
-cary   10432  0.0  2.6  1740   392  ?  S  Oct  9  0:00 axnet
-cary   27883  0.9 31.0 12692  4596  ?  S   10:24  0:04 axmain
-</screen>
-      </para>
-
-      <para>
-       Then run
-
-<screen>
-<prompt>$</prompt> <userinput>strace -f -s 1024 -p 10432</userinput>
-</screen>
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Check the <command>strace</command> output.
-      </para>
-      <note>
-       <title>Note from Cary</title>
-
-       <para>
-	Many of the error messages from <productname>Applixware</productname>
-	go to <filename>stderr</filename>, 
-	but I'm not sure where <filename>stderr</filename>
-	is sent, so <command>strace</command> is the way to find out.
-       </para>
-      </note>
-     </step>
-    </procedure>
-
-    <para>
-     For example, after getting
-     a <errorname>Cannot launch gateway on server</errorname>, 
-     I ran <command>strace</command> on <literal>axnet</literal> and got
-
-<screen>
-[pid 27947] open("/usr/lib/libodbc.so", O_RDONLY) = -1 ENOENT (No such file or directory)
-[pid 27947] open("/lib/libodbc.so", O_RDONLY) = -1 ENOENT (No such file or directory)
-[pid 27947] write(2, "/usr2/applix/axdata/elfodbc: can't load library 'libodbc.so'\n", 61) = -1 EIO (I/O error)
-</screen>  
-     So what is happening is that <literal>applix elfodbc</literal> is searching for <filename>libodbc.so</filename>, but it
-     cannot find it.  That is why <filename>axnet.cnf</filename> needed to be changed.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Running the <application>Applixware</application> Demo</title>
-
-    <comment>I think the condition this refers to is gone. -- petere 2002-01-07</comment>
-
-    <para>
-     In order to go through the 
-     <citetitle>Applixware Data Tutorial</citetitle>, you need to create
-     the sample tables that the Tutorial refers to.  The ELF Macro used to
-     create the tables tries to use a NULL condition 
-     on many of the database columns,
-     and <productname>PostgreSQL</productname> does not currently allow this option.
-    </para>
-
-    <para>
-     To get around this problem, you can do the following:
-    </para>
-
-    <procedure>
-     <title>Modifying the <application>Applixware</application> Demo</title>
-
-     <step performance="required">
-      <para>
-       Copy <filename>/opt/applix/axdata/eng/Demos/sqldemo.am</filename>
-       to a local directory.
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Edit this local copy of <filename>sqldemo.am</filename>:
-      </para>
-
-      <substeps>
-
-       <step performance="required">
-	<para>
-	 Search for <literal>null_clause = "NULL"</literal>.
-	</para>
-       </step>
-
-       <step performance="required">
-	<para>
-	 Change this to <literal>null_clause = ""</literal>.
-	</para>
-       </step>
-
-      </substeps>
-     </step>
-     <step performance="required">
-      <para>
-       Start <application>Applix Macro Editor</application>.
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Open the <filename>sqldemo.am</filename> file from the <application>Macro Editor</application>.
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Select <menuchoice><guimenu>File</><guimenuitem>Compile and Save</></menuchoice>.
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Exit <application>Macro Editor</application>.
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Start <application>Applix Data</application>.
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Select <menuchoice><guimenu>*</><guimenuitem>Run Macro</guimenuitem></menuchoice>.
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       Enter the value <literal>sqldemo</literal>, then click <guibutton>OK</guibutton>.
-      </para>
-
-      <para>
-       You should see the progress in the status line of the data window
-       (in the lower left corner).
-      </para>
-     </step>
-
-     <step performance="required">
-      <para>
-       You should now be able to access the demo tables.
-      </para>
-     </step>
-    </procedure>
-   </sect2>
-
-   <sect2>
-    <title>Useful Macros</title>
-
-    <para>
-     You can add information about your
-     database login and password to the standard <application>Applix</application> start-up
-     macro file. This is an example 
-     <filename>~/axhome/macros/login.am</filename> file:
-
-<programlisting>
-macro login
-set_set_system_var@("sql_username@","tgl")
-set_system_var@("sql_passwd@","no$way")
-endmacro
-</programlisting>
-
-     <caution>
-      <para>
-       You should be careful about the file protections on any file containing
-       user name and password information.
-      </para>
-     </caution>
-    </para>
-   </sect2>
-
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/page.sgml b/doc/src/sgml/page.sgml
deleted file mode 100644
index bb82142e611..00000000000
--- a/doc/src/sgml/page.sgml
+++ /dev/null
@@ -1,155 +0,0 @@
-<chapter id="page">
-
-<title>Page Files</title>
-
-<abstract>
-<para>
-A description of the database file default page format.
-</para>
-</abstract>
-
-<para>
-This section provides an overview of the page format used by <productname>PostgreSQL</productname>
-tables.  User-defined access methods need not use this page format.
-</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 data that is stored in <productname>PostgreSQL</productname> tables.
-</para>
-
-<para>
-<xref linkend="page-table"> shows how pages in both normal <productname>PostgreSQL</productname> tables
- and <productname>PostgreSQL</productname> indexes
-(e.g., a B-tree index) are structured.
-</para>
-
-<table tocentry="1" id="page-table">
-<title>Sample Page Layout</title>
-<titleabbrev>Page Layout</titleabbrev>
-<tgroup cols="2">
-<thead>
-<row>
-<entry>
-Item
-</entry>
-<entry>Description</entry>
-</row>
-</thead>
-
-<tbody>
-
-<row>
-<entry>itemPointerData</entry>
-</row>
-
-<row>
-<entry>filler</entry>
-</row>
-
-<row>
-<entry>itemData...</entry>
-</row>
-
-<row>
-<entry>Unallocated Space</entry>
-</row>
-
-<row>
-<entry>ItemContinuationData</entry>
-</row>
-
-<row>
-<entry>Special Space</entry>
-</row>
-
-<row>
-<entry><quote>ItemData 2</quote></entry>
-</row>
-
-<row>
-<entry><quote>ItemData 1</quote></entry>
-</row>
-
-<row>
-<entry>ItemIdData</entry>
-</row>
-
-<row>
-<entry>PageHeaderData</entry>
-</row>
-
-</tbody>
-</tgroup>
-</table>
-
-<!--
-.\" Running
-.\" .q .../bin/dumpbpages
-.\" or
-.\" .q .../src/support/dumpbpages
-.\" as the postgres superuser
-.\" with the file paths associated with
-.\" (heap or B-tree index) classes,
-.\" .q .../data/base/<database-name>/<class-name>,
-.\" will display the page structure used by the classes.
-.\" Specifying the
-.\" .q -r
-.\" flag will cause the classes to be
-.\" treated as heap classes and for more information to be displayed.
--->
-
-<para>
-The first 8 bytes of each page consists of a page header
-(PageHeaderData).
-Within the header, the first three 2-byte integer fields
-(<firstterm>lower</firstterm>,
-<firstterm>upper</firstterm>,
-and
-<firstterm>special</firstterm>)
-represent byte offsets to the start of unallocated space, to the end
-of unallocated space, and to the start of <firstterm>special space</firstterm>.
-Special space is a region at the end of the page that is allocated at
-page initialization time and contains information specific to an
-access method.  The last 2 bytes of the page header,
-<firstterm>opaque</firstterm>,
-encode the page size and information on the internal fragmentation of
-the page.  Page size is stored in each page because frames in the
-buffer pool may be subdivided into equal sized pages on a frame by
-frame basis within a table.  The internal fragmentation information is
-used to aid in determining when page reorganization should occur.
-</para>
-
-<para>
-Following the page header are item identifiers
-(<firstterm>ItemIdData</firstterm>).
-New item identifiers are allocated from the first four bytes of
-unallocated space.  Because an item identifier is never moved until it
-is freed, its index may be used to indicate the location of an item on
-a page.  In fact, every pointer to an item
-(<firstterm>ItemPointer</firstterm>)
-created by <productname>PostgreSQL</productname> consists of a frame number and an index of an item
-identifier.  An item identifier contains a byte-offset to the start of
-an item, its length in bytes, and a set of attribute bits which affect
-its interpretation.
-</para>
-
-<para>
-The items themselves are stored in space allocated backwards from
-the end of unallocated space.  Usually, the items are not interpreted.
-However when the item is too long to be placed on a single page or
-when fragmentation of the item is desired, the item is divided and
-each piece is handled as distinct items in the following manner.  The
-first through the next to last piece are placed in an item
-continuation structure
-(<firstterm>ItemContinuationData</firstterm>).
-This structure contains
-itemPointerData
-which points to the next piece and the piece itself.  The last piece
-is handled normally.
-</para>
-
-</chapter>
diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml
deleted file mode 100644
index 17c8a348d0f..00000000000
--- a/doc/src/sgml/perform.sgml
+++ /dev/null
@@ -1,729 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/perform.sgml,v 1.20 2002/03/24 17:11:37 tgl Exp $
--->
-
- <chapter id="performance-tips">
-  <title>Performance Tips</title>
-
-  <para>
-   Query performance can be affected by many things. Some of these can 
-   be manipulated 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>
-
-  <sect1 id="using-explain">
-   <title>Using <command>EXPLAIN</command></title>
-
-   <para>
-    <productname>PostgreSQL</productname> devises a <firstterm>query
-    plan</firstterm> for each query it is given.  Choosing the right
-    plan to match the query structure and the properties of the data
-    is absolutely critical for good performance.  You can use the
-    <command>EXPLAIN</command> command to see what query plan the system
-    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 numbers that are currently quoted by <command>EXPLAIN</command> are:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Estimated start-up cost (time expended before output scan can start,
-       e.g., time to do the sorting in a SORT node).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Estimated total cost (if all tuples are retrieved, which they may not
-       be --- a query with a LIMIT will stop short of paying the total cost,
-       for example).
-      </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 units of disk page fetches.  (CPU effort
-    estimates are converted into disk-page units using some
-    fairly arbitrary fudge-factors. If you want to experiment with these
-    factors, see the list of run-time configuration parameters in the
-    <citetitle>Administrator's Guide</citetitle>.)
-   </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/optimizer cares about.
-    In particular, the cost does not consider the time spent transmitting
-    result tuples to the frontend --- which could be a pretty dominant
-    factor in the true elapsed time, but the planner ignores it because
-    it cannot change it by altering the plan.  (Every correct plan will
-    output the same tuple set, we trust.)
-   </para>
-
-   <para>
-    Rows output is a little tricky because it is <emphasis>not</emphasis> the
-    number of rows
-    processed/scanned by the query --- it is usually less, reflecting the
-    estimated selectivity of any WHERE-clause constraints that are being
-    applied at this node.  Ideally the top-level rows estimate will
-    approximate the number of rows actually returned, updated, or deleted
-    by the query.
-   </para>
-
-   <para>
-    Here are some examples (using the regress test database after a
-    vacuum analyze, and 7.3 development sources):
-
-    <programlisting>
-regression=# EXPLAIN SELECT * FROM tenk1;
-                         QUERY PLAN
--------------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..333.00 rows=10000 width=148)
-    </programlisting>
-   </para>
-
-   <para>
-    This is about as straightforward as it gets.  If you do
-
-    <programlisting>
-SELECT * FROM pg_class WHERE relname = 'tenk1';
-    </programlisting>
-
-    you will find out that <classname>tenk1</classname> has 233 disk
-    pages and 10000 tuples.  So the cost is estimated at 233 page
-    reads, defined as 1.0 apiece, plus 10000 * <varname>cpu_tuple_cost</varname> which is
-    currently 0.01 (try <command>show cpu_tuple_cost</command>).
-   </para>
-
-   <para>
-    Now let's modify the query to add a WHERE condition:
-
-    <programlisting>
-regression=# EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 1000;
-                         QUERY PLAN
-------------------------------------------------------------
- Seq Scan on tenk1  (cost=0.00..358.00 rows=1033 width=148)
-   Filter: (unique1 &lt; 1000)
-    </programlisting>
-
-    The estimate of output rows has gone down because of the 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 to reflect the extra CPU
-    time spent checking the WHERE condition.
-   </para>
-
-   <para>
-    The actual number of rows this query would select is 1000, but the
-    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>
-    Modify the query to restrict the condition even more:
-
-    <programlisting>
-regression=# EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 50;
-                                   QUERY PLAN
--------------------------------------------------------------------------------
- Index Scan using tenk1_unique1 on tenk1  (cost=0.00..179.33 rows=49 width=148)
-   Index Cond: (unique1 &lt; 50)
-    </programlisting>
-
-    and you will see that if we make the WHERE condition selective
-    enough, the planner will
-    eventually decide that an index scan is cheaper than a sequential scan.
-    This plan will only have to visit 50 tuples because of the index,
-    so it wins despite the fact that each individual fetch is more expensive
-    than reading a whole disk page sequentially.
-   </para>
-
-   <para>
-    Add another clause to the WHERE condition:
-
-    <programlisting>
-regression=# EXPLAIN SELECT * FROM tenk1 WHERE unique1 &lt; 50 AND
-regression-# stringu1 = 'xxx';
-                                  QUERY PLAN
--------------------------------------------------------------------------------
- Index Scan using tenk1_unique1 on tenk1  (cost=0.00..179.45 rows=1 width=148)
-   Index Cond: (unique1 &lt; 50)
-   Filter: (stringu1 = 'xxx'::name)
-    </programlisting>
-
-    The added clause <literal>stringu1 = 'xxx'</literal> reduces the
-    output-rows estimate, but not the cost because we still have to visit the
-    same set of tuples.  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
-    a little bit to reflect this extra checking.
-   </para>
-
-   <para>
-    Let's try joining two tables, using the fields we have been discussing:
-
-    <programlisting>
-regression=# EXPLAIN SELECT * FROM tenk1 t1, tenk2 t2 WHERE t1.unique1 &lt; 50
-regression-# AND t1.unique2 = t2.unique2;
-                               QUERY PLAN
-----------------------------------------------------------------------------
- Nested Loop  (cost=0.00..327.02 rows=49 width=296)
-   -&gt;  Index Scan using tenk1_unique1 on tenk1 t1
-                                      (cost=0.00..179.33 rows=49 width=148)
-         Index Cond: (unique1 &lt; 50)
-   -&gt;  Index Scan using tenk2_unique2 on tenk2 t2
-                                      (cost=0.00..3.01 rows=1 width=148)
-         Index Cond: ("outer".unique2 = t2.unique2)
-    </programlisting>
-   </para>
-
-   <para>
-    In this nested-loop join, the outer scan is the same index scan we had
-    in the example before last, and so its cost and row count are the same
-    because we are applying the <literal>unique1 &lt; 50</literal> WHERE clause at that node.
-    The <literal>t1.unique2 = t2.unique2</literal> clause is not relevant yet, so it doesn't
-    affect row count of the outer scan.  For the inner scan, the unique2 value of the
-    current
-    outer-scan tuple is plugged into the inner index scan
-    to produce an index condition like
-    <literal>t2.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 tuple (49 * 3.01, here), plus a little CPU
-     time for join processing.
-   </para>
-
-   <para>
-    In this example the loop's output row count is the same as the product
-    of the two scans' row counts, but that's not true in general, because
-    in general you can have WHERE clauses that mention both relations 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 winner, using the enable/disable
-    flags for each plan type.  (This is a crude tool, but useful.  See
-    also <xref linkend="explicit-joins">.)
-
-    <programlisting>
-regression=# set enable_nestloop = off;
-SET VARIABLE
-regression=# EXPLAIN SELECT * FROM tenk1 t1, tenk2 t2 WHERE t1.unique1 &lt; 50
-regression-# AND t1.unique2 = t2.unique2;
-                               QUERY PLAN
---------------------------------------------------------------------------
- Hash Join  (cost=179.45..563.06 rows=49 width=296)
-   Hash Cond: ("outer".unique2 = "inner".unique2)
-   -&gt;  Seq Scan on tenk2 t2  (cost=0.00..333.00 rows=10000 width=148)
-   -&gt;  Hash  (cost=179.33..179.33 rows=49 width=148)
-         -&gt;  Index Scan using tenk1_unique1 on tenk1 t1
-                                    (cost=0.00..179.33 rows=49 width=148)
-               Index Cond: (unique1 &lt; 50)
-    </programlisting>
-
-    This plan proposes to extract the 50 interesting rows of <classname>tenk1</classname>
-    using ye same olde 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> at each <classname>tenk2</classname> tuple.
-    The cost to read <classname>tenk1</classname> and set up the hash table is entirely start-up
-    cost for the hash join, since we won't get any tuples out until we can
-    start reading <classname>tenk2</classname>.  The total time estimate for the join also
-    includes a hefty charge for CPU time to probe the hash table
-    10000 times.  Note, however, that we are NOT charging 10000 times 179.33;
-    the hash table setup is only done once in this plan type.
-   </para>
-
-   <para>
-    It is possible to check on the accuracy of the planner's estimated costs
-    by using 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 EXPLAIN shows.
-    For example, we might get a result like this:
-
-<screen>
-regression=# EXPLAIN ANALYZE
-regression-# SELECT * FROM tenk1 t1, tenk2 t2
-regression-# WHERE t1.unique1 &lt; 50 AND t1.unique2 = t2.unique2;
-                                   QUERY PLAN
--------------------------------------------------------------------------------
- Nested Loop  (cost=0.00..327.02 rows=49 width=296)
-                                 (actual time=1.18..29.82 rows=50 loops=1)
-   -&gt;  Index Scan using tenk1_unique1 on tenk1 t1
-                  (cost=0.00..179.33 rows=49 width=148)
-                                 (actual time=0.63..8.91 rows=50 loops=1)
-         Index Cond: (unique1 &lt; 50)
-   -&gt;  Index Scan using tenk2_unique2 on tenk2 t2
-                  (cost=0.00..3.01 rows=1 width=148)
-                                 (actual time=0.29..0.32 rows=1 loops=50)
-         Index Cond: ("outer".unique2 = t2.unique2)
- Total runtime: 31.60 msec
-</screen>
-
-    Note that the <quote>actual time</quote> values are in milliseconds of
-    real time, whereas the <quote>cost</quote> estimates are expressed in
-    arbitrary units of disk fetches; so they are unlikely to match up.
-    The thing to pay attention to is the ratios.
-   </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
-    tuple in the above nested-loop plan.  In such cases, the
-    <quote>loops</quote> 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 <quote>loops</quote> 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 shutdown time, as well as time spent processing
-    the result tuples.  It does not include parsing, rewriting, or planning
-    time.  For a SELECT query, the total run time will normally be just a
-    little larger than the total time reported for the top-level plan node.
-    For INSERT, UPDATE, and DELETE queries, the total run time may be
-    considerably larger, because it includes the time spent processing the
-    result tuples.  In these queries, the time for the top plan node
-    essentially is the time spent computing the new tuples and/or locating
-    the old ones, but it doesn't include the time spent making the changes.
-   </para>
-
-   <para>
-    It is worth noting that EXPLAIN results should not be extrapolated
-    to situations other than the one you are actually testing; for example,
-    results on a toy-sized table can't be assumed to apply to large tables.
-    The planner's cost estimates are not linear and so it may well 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>
-
-  <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
-   <structname>pg_class</structname>'s <structfield>reltuples</structfield>
-   and <structfield>relpages</structfield> columns.  We can look at it
-   with queries similar to this one:
-
-<screen>
-regression=# select relname, relkind, reltuples, relpages from pg_class
-regression-# where relname like 'tenk1%';
-    relname    | relkind | reltuples | relpages
----------------+---------+-----------+----------
- tenk1         | r       |     10000 |      233
- tenk1_hundred | i       |     10000 |       30
- tenk1_unique1 | i       |     10000 |       30
- tenk1_unique2 | i       |     10000 |       30
-(4 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 only approximate values (which is good
-   enough for the planner's purposes).  They are initialized with dummy
-   values (presently 1000 and 10 respectively) when a table is created.
-   They are updated by certain commands, presently <command>VACUUM</>,
-   <command>ANALYZE</>, and <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.
-  </para>
-
-  <para>
-   Most queries retrieve only a fraction of the rows in a table, due
-   to having WHERE clauses that restrict the rows to be examined.
-   The planner thus needs to make an estimate of the
-   <firstterm>selectivity</> of WHERE clauses, that is, the fraction of
-   rows that match each clause of the WHERE condition.  The information
-   used for this task is stored in the <structname>pg_statistic</structname>
-   system catalog.  Entries in <structname>pg_statistic</structname> are
-   updated by <command>ANALYZE</> and <command>VACUUM ANALYZE</> commands,
-   and are always approximate even when freshly updated.
-  </para>
-
-  <para>
-   Rather than look at <structname>pg_statistic</structname> directly,
-   it's better to look at its view <structname>pg_stats</structname>
-   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 the 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>
-regression=# select attname, n_distinct, most_common_vals from pg_stats where tablename = 'road';
- attname | n_distinct |                                                                                                                                                                                  most_common_vals                                                                                                                                                                                   
----------+------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
- name    |  -0.467008 | {"I- 580                        Ramp","I- 880                        Ramp","Sp Railroad                       ","I- 580                            ","I- 680                        Ramp","I- 80                         Ramp","14th                          St  ","5th                           St  ","Mission                       Blvd","I- 880                            "}
- thepath |         20 | {"[(-122.089,37.71),(-122.0886,37.711)]"}
-(2 rows)
-regression=#
-</screen>
-
-   As of <productname>PostgreSQL</productname> 7.2 the following columns exist
-   in <structname>pg_stats</structname>:
-  </para>
-
-  <table>
-   <title><structname>pg_stats</structname> Columns</title>
-
-   <tgroup cols=3>
-    <thead>
-     <row>
-      <entry>Name</entry>
-      <entry>Type</entry>
-      <entry>Description</entry>
-     </row>
-    </thead>
-
-    <tbody>
-     <row>
-      <entry><literal>tablename</literal></entry>
-      <entry><type>name</type></entry>
-      <entry>Name of table containing column</entry>
-     </row>
-
-     <row>
-      <entry><literal>attname</literal></entry>
-      <entry><type>name</type></entry>
-      <entry>Column described by this row</entry>
-     </row>
-
-     <row>
-      <entry><literal>null_frac</literal></entry>
-      <entry><type>real</type></entry>
-      <entry>Fraction of column's entries that are NULL</entry>
-     </row>
-
-     <row>
-      <entry><literal>avg_width</literal></entry>
-      <entry><type>integer</type></entry>
-      <entry>Average width in bytes of column's entries</entry>
-     </row>
-
-     <row>
-      <entry><literal>n_distinct</literal></entry>
-      <entry><type>real</type></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 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><literal>most_common_vals</literal></entry>
-      <entry><type>text[]</type></entry>
-      <entry>A list of the most common values in the column. (Omitted if
-      no values seem to be more common than any others.)</entry>
-     </row>
-
-     <row>
-      <entry><literal>most_common_freqs</literal></entry>
-      <entry><type>real[]</type></entry>
-      <entry>A list of the frequencies of the most common values,
-      ie, number of occurrences of each divided by total number of rows.
-     </entry>
-     </row>
-
-     <row>
-      <entry>histogram_bounds</entry>
-      <entry><type>text[]</type></entry>
-      <entry>A list of values that divide the column's values into
-      groups of approximately equal population.  The 
-      <structfield>most_common_vals</>, if present, are omitted from the
-      histogram calculation.  (Omitted if 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>correlation</entry>
-      <entry><type>real</type></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.  (Omitted if 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.  The default limit is presently 10 entries.  Raising the limit
-   may 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 may be
-   appropriate for columns with simple data distributions.
-  </para>
-
- </sect1>
-
- <sect1 id="explicit-joins">
-  <title>Controlling the Planner with Explicit JOINs</title>
-
-  <para>
-   Beginning with <productname>PostgreSQL</productname> 7.1 it is possible
-   to control the query planner to some extent by using explicit 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 WHERE clause
-   a.id = b.id, and then joins C to this joined table, using the other
-   WHERE clause.  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 --- but that would
-   be inefficient, since the full Cartesian product of A and C would have
-   to be formed, there being no applicable WHERE clause to allow optimization
-   of the join.
-   (All joins in the <productname>PostgreSQL</productname> executor happen
-   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 may have hugely
-   different execution costs.  Therefore, the planner will explore all of them
-   to try to find the most efficient query plan.
-  </para>
-
-  <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 may take an
-   annoyingly long time.  When there are too many input tables, the
-   <productname>PostgreSQL</productname> planner will switch from exhaustive
-   search to a <firstterm>genetic</firstterm> probabilistic search
-   through a limited number of possibilities.  (The switch-over threshold is
-   set by the <varname>GEQO_THRESHOLD</varname> run-time
-   parameter described in the <citetitle>Administrator's Guide</citetitle>.)
-   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 much 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.
-  </para>
-
-  <para>
-   In <productname>PostgreSQL</productname> 7.1, the planner treats all
-   explicit JOIN syntaxes as constraining the join order, even though
-   it is not logically necessary to make such a constraint for inner
-   joins.  Therefore, although all of these queries give the same result:
-    <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>
-   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>
-   You do not need to constrain the join order completely in order to
-   cut search time, because it's OK to use JOIN operators in a plain
-   FROM list.  For example,
-    <programlisting>
-SELECT * FROM a CROSS JOIN b, c, d, e WHERE ...;
-    </programlisting>
-   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>
-   If you have a mix of outer and inner joins in a complex query, you
-   might not want to constrain the planner's search for a good ordering
-   of inner joins inside an outer join.  You can't do that directly in the
-   JOIN syntax, but you can get around the syntactic limitation by using
-   subselects.  For example,
-    <programlisting>
-SELECT * FROM d LEFT JOIN
-        (SELECT * FROM a, b, c WHERE ...) AS ss
-        ON (...);
-    </programlisting>
-   Here, joining D must be the last step in the query plan, but the
-   planner is free to consider various join orders for A,B,C.
-  </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 JOIN syntax --- assuming
-   that you know of a better order, that is.  Experimentation is recommended.
-  </para>
- </sect1>
-
- <sect1 id="populate">
-  <title>Populating a Database</title>
-
-  <para>
-   One may need to do a large number of table insertions when first
-   populating a database. Here are some tips and techniques for making that as
-   efficient as possible.
-  </para>
-
-  <sect2 id="disable-autocommit">
-   <title>Disable Autocommit</title>
-
-   <para>
-    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 may 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,
-    <productname>PostgreSQL</productname> is doing a lot of work for each
-    record added.
-   </para>
-  </sect2>
-
-  <sect2 id="populate-copy-from">
-   <title>Use COPY FROM</title>
-
-   <para>
-    Use <command>COPY FROM STDIN</command> to load all the records in one
-    command, instead of using
-    a series of <command>INSERT</command> commands.  This reduces parsing,
-    planning, etc.
-    overhead a great deal. If you do this then it is not necessary to turn
-    off autocommit, since it is only one command anyway.
-   </para>
-  </sect2>
-
-  <sect2 id="populate-rm-indexes">
-   <title>Remove Indexes</title>
-
-   <para>
-    If you are loading a freshly created table, the fastest way is to
-    create the table, bulk-load with <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 record is loaded.
-   </para>
-
-   <para>
-    If you are augmenting an existing table, you can <command>DROP
-    INDEX</command>, load the table, then recreate the index. Of
-    course, the database performance for other users may be adversely 
-    affected during the time that the index is missing.  One should also
-    think twice before dropping unique indexes, since the error checking
-    afforded by the unique constraint will be lost while the index is missing.
-   </para>
-  </sect2>
-
-  <sect2 id="populate-analyze">
-   <title>ANALYZE Afterwards</title>
-
-   <para>
-    It's a good idea to run <command>ANALYZE</command> or <command>VACUUM
-    ANALYZE</command> anytime you've added or updated a lot of data,
-    including just after initially populating a table.  This ensures that
-    the planner has up-to-date statistics about the table.  With no statistics
-    or obsolete statistics, the planner may make poor choices of query plans,
-    leading to bad performance on queries that use your table.
-   </para>
-  </sect2>
-  </sect1>
-
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/plperl.sgml b/doc/src/sgml/plperl.sgml
deleted file mode 100644
index c04ff95d929..00000000000
--- a/doc/src/sgml/plperl.sgml
+++ /dev/null
@@ -1,333 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/plperl.sgml,v 2.16 2002/03/06 19:05:57 momjian Exp $
--->
-
- <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>
-
-  <para>
-   PL/Perl is a loadable procedural language
-   that enables the <ulink url="http://www.perl.com">Perl</ulink> programming
-   language to be used to write 
-   <productname>PostgreSQL</productname> functions.
-  </para>
-
-  <!-- **** PL/Perl overview **** -->
-
-  <sect1 id="plperl-overview">
-   <title>Overview</title>
-
-   <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 backend or to gain OS-level access under the permissions of the
-    <productname>PostgreSQL</productname> user ID, as a C function can do.
-    Thus, any unprivileged database user may be
-    permitted to use this language.
-   </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 named <literal>plperlu</>).
-    In this case the full Perl language is available.  The writer of a 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>
- </sect1>
-
- <sect1 id="plperl-install">
-  <title>Building and Installing PL/Perl</title>
-
-  <para>
-   If the <option>--with-perl</option> option was supplied to the
-   <indexterm><primary><filename>configure</filename></primary></indexterm>
-   <filename>configure</filename> script,
-   the <productname>PostgreSQL</productname> build process will attempt to
-   build the PL/Perl shared library and install it in the 
-   <productname>PostgreSQL</productname> library directory.
-  </para>
-
-  <para>
-   On most platforms, since PL/Perl is a shared library, the
-   <indexterm><primary>libperl</primary></indexterm>
-   <filename>libperl</filename> library must be a shared library also.
-   At the time of this writing, this is almost never the case in prebuilt
-   Perl packages.  If this difficulty arises in your situation, a
-   message like this will appear during the build to point out this
-   fact:
-<screen>
-<computeroutput>
-*** 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.
-</computeroutput>
-</screen>
-   If you see this, you will have to re-build and install
-   <productname>Perl</productname> manually to be able to build
-   PL/Perl.  During the configuration process for
-   <productname>Perl</productname>, request a shared library.
-  </para>
-
-  <para>
-   After having reinstalled Perl, change to the directory
-   <filename>src/pl/plperl</filename> in the
-   <productname>PostgreSQL</productname> source tree and issue the commands
-<programlisting>
-gmake clean
-gmake all
-gmake install
-</programlisting>
-   to complete the build and installation of the PL/Perl shared library.
-  </para>
-
-   <para>
-    To install
-    PL/Perl and/or PL/PerlU in a particular database, use the
-    <filename>createlang</filename> script, for example
-    <literal>createlang plperl <replaceable>dbname</></literal> or
-    <literal>createlang plperlu <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>
-  </sect1>
-
-  <!-- **** PL/Perl description **** -->
-
-  <sect1 id="plperl-description">
-   <title>Description</title>
-
-   <sect2>
-    <title>PL/Perl Functions and Arguments</title>
-
-    <para>
-     To create a function in the PL/Perl language, use the standard syntax
-
-     <programlisting>
-CREATE FUNCTION <replaceable>funcname</replaceable> (<replaceable>argument-types</replaceable>) RETURNS <replaceable>return-type</replaceable> AS '
-    # PL/Perl function body
-' LANGUAGE plperl;
-     </programlisting>
-
-     PL/PerlU is the same, except that the language should be specified as
-     <literal>plperlu</>.
-    </para>
-
-    <para>
-     The body of the function is ordinary Perl code.  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.  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] > $_[1]) { return $_[0]; }
-    return $_[1];
-' LANGUAGE plperl;
-     </programlisting>
-
-     If a NULL 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>WITH (isStrict)</>
-     to the function definition to make <productname>PostgreSQL</productname>
-     do something more reasonable: if a NULL 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 perl_max
-     with one null and one non-null argument to return the non-null
-     argument, rather than NULL:
-
-     <programlisting>
-CREATE FUNCTION perl_max (integer, integer) RETURNS integer AS '
-    my ($a,$b) = @_;
-    if (! defined $a) {
-        if (! defined $b) { return undef; }
-        return $b;
-    }
-    if (! defined $b) { return $a; }
-    if ($a > $b) { return $a; }
-    return $b;
-' LANGUAGE plperl;
-     </programlisting>
-    </para>
-
-    <para>
-     As shown above,
-     to return a NULL from a PL/Perl function, return an undefined
-     value.  This can be done whether the function is strict or not.
-    </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->{''basesalary''} + $emp->{''bonus''};
-' LANGUAGE plperl;
-
-SELECT name, empcomp(employee) FROM employee;
-     </programlisting>
-    </para>
-
-    <para>
-     There is not currently any support for returning a composite-type
-     result value.
-    </para>
-
-  <tip>
-   <para>
-    Because the function body is passed as an SQL string literal to
-    <command>CREATE FUNCTION</command>, you have to escape single
-    quotes and backslashes within your Perl source, typically by doubling them
-    as shown in the above example.  Another possible approach is to
-    avoid writing single quotes by using Perl's extended quoting functions
-    (<literal>q[]</literal>, <literal>qq[]</literal>,
-    <literal>qw[]</literal>).
-   </para>
-  </tip>
-
-  <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 '
-    open(TEMP, ">/tmp/badfile");
-    print TEMP "Gotcha!\n";
-    return 1;
-' LANGUAGE plperl;
-</programlisting>
-   The creation of the function will succeed, but executing it will not.
-  </para>
-  <para>
-   Note that if the same function was created by a superuser using language 
-   <literal>plperlu</>, execution would succeed.
-  </para>
-
-   </sect2>
-
-   <sect2>
-    <title>Data Values in PL/Perl</title>
-
-    <para>
-     The argument values supplied to a PL/Perl function's script are simply
-     the input arguments converted to text form (just as if they had been
-     displayed by a SELECT statement).  Conversely, the <literal>return</>
-     command will accept any string that is acceptable input format for
-     the function's declared return type.  So, the PL/Perl programmer can
-     manipulate data values as if they were just text.
-    </para>
-
-   </sect2>
-
-   <sect2>
-    <title>Database Access from PL/Perl</title>
-
-  <para>
-   Access to the database itself from your Perl function can be done via
-   an experimental module <ulink
-   url="http://www.cpan.org/modules/by-module/DBD/APILOS/"><literal>DBD::PgSPI</literal></ulink>
-   (also available at <ulink url="http://www.cpan.org/SITES.html">CPAN
-   mirror sites</ulink>). This module makes available a
-   <acronym>DBI</>-compliant database-handle named
-   <varname>$pg_dbh</varname> that can be used to perform queries
-   with normal <acronym>DBI</> syntax.
-  </para>
-
-    <para>
-     PL/Perl itself presently provides only one additional Perl command:
-    </para>
-
-    <variablelist>
-     <varlistentry>
-      <indexterm>
-       <primary>elog</primary>
-      </indexterm>
-      <term><function>elog</> <replaceable>level</replaceable>, <replaceable>msg</replaceable></term>
-      <listitem>
-       <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: further execution
-	of the function is abandoned, and the current transaction is
-	aborted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-   </sect2>
-
-   <sect2>
-    <title>Missing Features</title>
-
-    <para>
-     PL/Perl functions cannot call each other directly (because they
-     are anonymous subroutines inside Perl).  There's presently
-     no way for them to share global variables, either.
-    </para>
-
-    <para>
-     PL/Perl cannot currently be used to write trigger functions.
-    </para>
-
-    <para>
-     DBD::PgSPI or similar capability should be integrated
-     into the standard <productname>PostgreSQL</productname> distribution.
-    </para>
-
-   </sect2>
-
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
deleted file mode 100644
index 2e38a5c7917..00000000000
--- a/doc/src/sgml/plpython.sgml
+++ /dev/null
@@ -1,223 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/plpython.sgml,v 1.10 2002/03/22 19:20:18 petere Exp $ -->
-
-<chapter id="plpython">
- <title>PL/Python - Python Procedural Language</title>
-
- <indexterm zone="plpython"><primary>PL/Python</></>
- <indexterm zone="plpython"><primary>Python</></>
-
- <sect1 id="plpython-intro">
-  <title>Introduction</title>
-
-  <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</ulink> language.
-  </para>
-
-  <para>
-   The current version of <application>PL/Python</application>
-   functions as a trusted language only; access to the file system and
-   other local resources is disabled.  Specifically,
-   <application>PL/Python</application> uses the Python restricted
-   execution environment, further restricts it to prevent the use of
-   the file <function>open</> call, and allows only modules from a
-   specific list to be imported.  Presently, that list includes:
-   array, bisect, binascii, calendar, cmath, codecs, errno, marshal,
-   math, md5, mpz, operator, pcre, pickle, random, re, regex, sre,
-   sha, string, StringIO, struct, time, whrandom, and zlib.
-  </para>
-
-  <para>
-   In the current version, any database error encountered while
-   running a <application>PL/Python</application> function will result
-   in the immediate termination of that function by the server.  It is
-   not possible to trap error conditions using Python <literal>try
-   ... catch</literal> constructs.  For example, a syntax error in an
-   SQL statement passed to the <literal>plpy.execute()</literal> call
-   will terminate the function.  This behavior may be changed in a
-   future release.
-  </para>
- </sect1>
-
- <sect1 id="plpython-install">
-  <title>Installation</title>
-
-  <para>
-   To build PL/Python, the <option>--with-python</option> option needs
-   to be specified when running <filename>configure</filename>.  If
-   after building and installing 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 Python installation
-   to supply this shared library.
-  </para>
-
-  <para>
-   The catch is that the Python distribution or the Python maintainers
-   do not provide any direct way to do this.  The closest thing we can
-   offer you is the information in <ulink
-   url="http://www.python.org/doc/FAQ.html#3.30">Python FAQ
-   3.30</ulink>.  On some operating systems you don't really have to
-   build a shared library, but then you will have to convince the
-   PostgreSQL build system of this.  Consult the
-   <filename>Makefile</filename> in the
-   <filename>src/pl/plpython</filename> directory for details.
-  </para>
- </sect1>
-
- <sect1 id="plpython-using">
-  <title>Using PL/Python</title>
-
-  <para>
-   There are sample functions in
-   <filename>plpython_function.sql</filename>.  The Python code you
-   write gets transformed into a function.  E.g.,
-<programlisting>
-CREATE FUNCTION myfunc(text) RETURNS text AS
-'return args[0]'
-LANGUAGE 'plpython';
-</programlisting>
-
-   gets transformed into
-
-<programlisting>
-def __plpython_procedure_myfunc_23456():
-	return args[0]
-</programlisting>
-
-   where 23456 is the OID of the function.
-  </para>
-
-  <para>
-   If you do not provide a return value, Python returns the default
-   <symbol>None</symbol> which may or may not be what you want.  The
-   language module translates Python's None into SQL NULL.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</> function variables are available in the global
-   <varname>args</varname> list.  In the <function>myfunc</function>
-   example, <varname>args[0]</> contains whatever was passed in as the text
-   argument.  For <literal>myfunc2(text, integer)</literal>, <varname>args[0]</>
-   would contain the <type>text</type> variable and <varname>args[1]</varname> the <type>integer</type> variable.
-  </para>
-
-  <para>
-   The global dictionary SD is available to store data between
-   function calls.  This variable is private static data.  The global
-   dictionary GD is public data, available to all python functions
-   within a backend.  Use with care.
-  </para>
-
-  <para>
-   Each function gets its own restricted execution object 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 GD
-   dictionary, as mentioned above.
-  </para>
-
-  <para>
-   When a function is used in a trigger, the dictionary TD contains
-   transaction related values.  The trigger tuples are in <literal>TD["new"]</>
-   and/or <literal>TD["old"]</> depending on the trigger event.  <literal>TD["event"]</>
-   contains the event as a string (<literal>INSERT</>, <literal>UPDATE</>, <literal>DELETE</>, or
-   <literal>UNKNOWN</>).  TD["when"] contains one of (<literal>BEFORE</>, <literal>AFTER</>, or
-   <literal>UNKNOWN</>).  <literal>TD["level"]</> contains one of <literal>ROW</>, <literal>STATEMENT</>, or
-   <literal>UNKNOWN</>.  <literal>TD["name"]</> contains the trigger name, and <literal>TD["relid"]</>
-   contains the relation id of the table on which the trigger occurred.
-   If the trigger was called with arguments they are available
-   in <literal>TD["args"][0]</> to <literal>TD["args"][(n -1)]</>.
-  </para>
-
-  <para>
-   If the trigger <quote>when</quote> is <literal>BEFORE</>, you may return <literal>None</literal> or <literal>"OK"</literal>
-   from the Python function to indicate the tuple is unmodified,
-   <literal>"SKIP"</> to abort the event, or <literal>"MODIFIED"</> to indicate you've
-   modified the tuple.
-  </para>
-
-  <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>.  At present
-   <literal>plpy</literal> implements the functions
-   <literal>plpy.debug("msg")</literal>, 
-   <literal>plpy.log("msg")</literal>,
-   <literal>plpy.info("msg")</literal>,
-   <literal>plpy.notice("msg")</literal>,
-   <literal>plpy.warning("msg")</literal>,
-   <literal>plpy.error("msg")</literal>, and
-   <literal>plpy.fatal("msg")</literal>.  They are mostly equivalent
-   to calling <literal>elog(<replaceable>LEVEL</>, "msg")</literal>.
-   <function>plpy.error</function> and <function>plpy.fatal</function>
-   actually raise a Python exception which, if uncaught, causes the
-   PL/Python module to call <literal>elog(ERROR, msg)</literal> when
-   the function handler returns from the Python interpreter.  Long
-   jumping out of the Python interpreter is probably not good.
-   <literal>raise plpy.ERROR("msg")</literal> and <literal>raise
-   plpy.FATAL("msg")</literal> are equivalent to calling
-   <function>plpy.error</function> or <function>plpy.fatal</function>.
-  </para>
-
-  <para>
-   Additionally, 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 returned in a result object.  The result object emulates a
-   list or dictionary object.  The result object can be accessed by
-   row number, and field 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_exec</function> return variable.  The result object
-   can be modified.
-
-<programlisting>
-rv = plpy.execute("SELECT * FROM my_table", 5)
-</programlisting>
-   returns up to 5 rows from my_table.  Ff my_table has a column
-   my_field it would be accessed as
-<programlisting>
-foo = rv[i]["my_field"]
-</programlisting>
-   The second function <function>plpy.prepare</function> is called
-   with a query string, and a list of argument types if you have bind
-   variables in the query.
-<programlisting>
-plan = plpy.prepare("SELECT last_name FROM my_users WHERE first_name = $1", [ "text" ])
-</programlisting>
-   text is the type of the variable you will be passing as $1.  After
-   preparing you use the function <function>plpy.execute</function> to
-   run it.
-<programlisting>
-rv = plpy.execute(plan, [ "name" ], 5)
-</programlisting>
-   The limit argument is optional in the call to
-   <function>plpy.execute</function>.
-  </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.  The take
-   home message is if you do
-<programlisting>
-plan = plpy.prepare("SOME QUERY")
-plan = plpy.prepare("SOME OTHER QUERY")
-</programlisting>
-   you are leaking memory, as I know of no way to free a saved plan.
-   The alternative of using unsaved plans it even more painful (for
-   me).
-  </para>
- </sect1>
-
-</chapter>
diff --git a/doc/src/sgml/plsql.sgml b/doc/src/sgml/plsql.sgml
deleted file mode 100644
index 91e96c77f06..00000000000
--- a/doc/src/sgml/plsql.sgml
+++ /dev/null
@@ -1,3003 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/plsql.sgml,v 2.59 2002/06/15 19:34:51 momjian Exp $
--->
-
-<chapter id="plpgsql"> 
-  <title><application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language</title>
-
- <indexterm zone="plpgsql">
-  <primary>PL/pgSQL</primary>
- </indexterm>
-
- <para>
-  <application>PL/pgSQL</application> is a loadable procedural language for the
-  <productname>PostgreSQL</productname> database system.
- </para>
-   
- <para>
-  This package was originally written by Jan Wieck. This
-  documentation was in part written 
-  by Roberto Mello (<email>rmello@fslc.usu.edu</email>).
- </para>
-
-  <sect1 id="plpgsql-overview">
-   <title>Overview</title>
-
-   <para>
-    The design goals of <application>PL/pgSQL</> were to create a loadable procedural
-    language that
-    <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>
-    The <application>PL/pgSQL</> call handler parses the function's source text and
-    produces an internal binary instruction tree the first time the
-    function is called (within any one backend process).  The instruction tree
-    fully translates the 
-    <application>PL/pgSQL</> statement structure, but individual
-    <acronym>SQL</acronym> expressions and <acronym>SQL</acronym> queries
-    used in the function are not translated immediately.
-   </para>
-   <para>
-    As each expression and <acronym>SQL</acronym> query is first used
-    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 query re-use 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 provide a considerable savings of parsing
-    activity.  A disadvantage is that errors in a specific expression
-    or query may not be detected until that part of the function is
-    reached in execution.
-   </para>
-  <para>
-   Once <application>PL/pgSQL</> has made a query plan for a particular
-   query in a function, it will re-use that plan for the life of the
-   database connection.  This is usually a win for performance, but it
-   can cause some problems if you dynamically
-   alter your database schema. For example:
-
-<programlisting>
-CREATE FUNCTION populate() RETURNS INTEGER AS '
-DECLARE
-    -- Declarations
-BEGIN
-    PERFORM my_function();
-END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-    If you execute the above function, it will reference the OID for
-    <function>my_function()</function> in the query plan produced for
-    the PERFORM statement. Later, if you
-    drop and re-create <function>my_function()</function>, then
-    <function>populate()</function> will not be able to find
-    <function>my_function()</function> anymore. You would then have to
-    re-create <function>populate()</function>, or at least start a new
-    database session so that it will be compiled afresh.
-   </para>
-
-   <para>
-    Because <application>PL/pgSQL</application> saves execution plans in this way, queries that appear
-    directly in a <application>PL/pgSQL</application> function must refer to the same tables and fields
-    on every execution; that is, you cannot use a parameter as the name of
-    a table or field in a query.  To get around
-    this restriction, you can construct dynamic queries using the <application>PL/pgSQL</application>
-    EXECUTE statement --- at the price of constructing a new query plan
-    on every execution.
-   </para>
-   <para>
-    Except for input/output conversion and calculation functions
-    for user defined types, anything that can be defined in C language
-    functions can also be done with <application>PL/pgSQL</application>. It is possible to
-    create complex conditional computation functions and later use
-    them to define operators or use them in functional indexes.
-   </para>
-  <sect2 id="plpgsql-advantages">
-   <title>Advantages of Using PL/pgSQL</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Better performance (see <xref linkend="plpgsql-advantages-performance">)
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      SQL support (see <xref linkend="plpgsql-advantages-sqlsupport">)
-     </para>
-    </listitem> 
-
-    <listitem>
-     <para>
-      Portability (see <xref linkend="plpgsql-advantages-portability">)
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   <sect3 id="plpgsql-advantages-performance">
-    <title>Better Performance</title>
-
-    <para>
-     <acronym>SQL</acronym> is the language <productname>PostgreSQL</> (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 process it,
-     receive the results, do some computation, then send
-     other queries to the server. All this incurs inter-process communication
-     and may 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 saving lots of
-     time because you don't have the whole client/server
-     communication overhead. This can make for a
-     considerable performance increase.
-    </para>
-   </sect3>
-
-   <sect3 id="plpgsql-advantages-sqlsupport">
-    <title>SQL Support</title>
-
-    <para>
-     <application>PL/pgSQL</application> adds the power of a procedural language to the
-     flexibility and ease of <acronym>SQL</acronym>. With
-     <application>PL/pgSQL</application> you can use all the data types, columns, operators
-     and functions of SQL.    
-    </para>
-   </sect3>
-
-   <sect3 id="plpgsql-advantages-portability">
-    <title>Portability</title>
-
-    <para>
-     Because <application>PL/pgSQL</application> functions run inside <productname>PostgreSQL</>, these
-     functions will run on any platform where <productname>PostgreSQL</>
-     runs. Thus you can reuse code and have less development costs.
-    </para>
-   </sect3>
-  </sect2>
-
-  <sect2 id="plpgsql-overview-developing-in-plpgsql">
-   <title>Developing in <application>PL/pgSQL</application></title>
-
-   <para>
-    Developing in <application>PL/pgSQL</application> is pretty straight forward, especially
-    if you have developed in other database procedural languages,
-    such as Oracle's <application>PL/SQL</application>. Two good ways of developing in
-    <application>PL/pgSQL</application> are:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Using a text editor and reloading the file with <command>psql</command>
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Using <productname>PostgreSQL</>'s GUI Tool: <application>PgAccess</>
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <para>
-    One good way to develop in <application>PL/pgSQL</> is to simply use the text
-    editor of your choice to create your functions, and in another
-    console, use <command>psql</command> (PostgreSQL's interactive monitor) to load
-    those functions. If you are doing it this way, it is a good
-    idea to write the function using <command>CREATE OR REPLACE
-    FUNCTION</command>. That way you can reload the file to update
-    the function definition.  For example:
-<programlisting>
-CREATE OR REPLACE FUNCTION testfunc(INTEGER) RETURNS INTEGER AS '
-    ....
-end;
-' LANGUAGE 'plpgsql';
-</programlisting>
-   </para>
-
-   <para>
-    While running <command>psql</command>, 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 using
-    <productname>PostgreSQL</>'s GUI tool: <application>PgAccess</>. It does some
-    nice things for you, like escaping single-quotes, and making
-    it easy to recreate and debug functions.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="plpgsql-structure">
-  <title>Structure of <application>PL/pgSQL</application></title>
-
-    <para>
-     <application>PL/pgSQL</application> is a <emphasis>block
-     structured</emphasis> language.  The complete text of a function
-     definition must be a <firstterm>block</>. A block is defined as:
-
-<synopsis>
-<optional> &lt;&lt;label&gt;&gt; </optional>
-<optional> DECLARE
-    <replaceable>declarations</replaceable> </optional>
-BEGIN
-    <replaceable>statements</replaceable>
-END;
-</synopsis>
-    </para>
-
-    <para>
-     Any <firstterm>statement</> in the statement section of a block
-     can be a <firstterm>sub-block</>.  Sub-blocks can be used for
-     logical grouping or to localize variables to a small group
-     of statements.
-    </para>
-
-    <para>
-     The variables declared in the declarations section preceding a
-     block are initialized to their default values every time the
-     block is entered, not only once per function call. For example:
-<programlisting>
-CREATE FUNCTION somefunc() RETURNS INTEGER AS '
-DECLARE
-   quantity INTEGER := 30;
-BEGIN
-   RAISE NOTICE ''Quantity here is %'',quantity;  -- Quantity here is 30
-   quantity := 50;
-   --
-   -- Create a sub-block
-   --
-   DECLARE
-      quantity INTEGER := 80;
-   BEGIN
-      RAISE NOTICE ''Quantity here is %'',quantity;  -- Quantity here is 80
-   END;
-
-   RAISE NOTICE ''Quantity here is %'',quantity;  -- Quantity here is 50
-
-   RETURN quantity;
-END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-    </para>
-
-    <para>
-     It is important not to confuse the use of BEGIN/END for
-     grouping statements in <application>PL/pgSQL</> with the database commands for
-     transaction control.  <application>PL/pgSQL</>'s BEGIN/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
-     --- they cannot start or commit transactions, since
-     <productname>PostgreSQL</productname> does not have nested transactions.
-    </para>
-
-   <sect2>
-    <title>Lexical Details</title>
-
-    <para>
-     Each statement and declaration within a block is terminated
-     by a semicolon.
-    </para>
-
-    <para>
-     All keywords and identifiers can be written in mixed upper- and
-     lower-case.  Identifiers are implicitly converted to lower-case
-     unless double-quoted.
-    </para>
-
-    <para>
-     There are two types of comments in <application>PL/pgSQL</>. 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 next occurrence of <literal>*/</literal>.
-     Block comments cannot be nested, but double dash comments can be
-     enclosed into a block comment and a double dash can hide
-     the block comment delimiters <literal>/*</literal> and <literal>*/</literal>.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="plpgsql-declarations">
-    <title>Declarations</title>
-
-    <para>
-     All variables, rows and records used in a block must be declared in the
-     declarations section of the block. 
-     (The only exception is that the loop variable of a FOR loop iterating
-     over a range of integer values is automatically declared as an integer
-     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.fieldname%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> NOT NULL </optional> <optional> { DEFAULT | := } <replaceable>expression</replaceable> </optional>;
-</synopsis>
-     </para>
-
-     <para>
-      The DEFAULT clause, if given, specifies the initial value assigned
-      to the variable when the block is entered.  If the DEFAULT clause
-      is not given then the variable is initialized to the
-     <acronym>SQL</acronym> NULL value. 
-     </para>
-
-     <para>
-      The CONSTANT option prevents the variable from being assigned to,
-      so that its value remains constant for the duration of the block.
-      If NOT NULL
-      is specified, an assignment of a NULL value results in a run-time
-      error. All variables declared as NOT NULL
-      must have a non-NULL default value specified.
-     </para>
-
-     <para>
-      The default value is evaluated every time the block is entered. 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 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-aliases">
-     <title>Aliases for Function Parameters</title>
-
-    <para>
-<synopsis>
-<replaceable>name</replaceable> ALIAS FOR <replaceable>$n</replaceable>;
-</synopsis>
-    </para>
-
-     <para>
-      Parameters passed to functions are named with the identifiers
-      <literal>$1</literal>, <literal>$2</literal>,
-      etc.  Optionally, aliases can be declared for <literal>$n</literal>
-      parameter names for increased readability.  Either the alias or the
-      numeric identifier can then be used to refer to the parameter value.
-      Some examples:
-<programlisting>
-CREATE FUNCTION sales_tax(REAL) RETURNS REAL AS '
-DECLARE
-    subtotal ALIAS FOR $1;
-BEGIN
-    return subtotal * 0.06;
-END;
-' LANGUAGE 'plpgsql';
-
-
-CREATE FUNCTION instr(VARCHAR,INTEGER) RETURNS INTEGER AS '
-DECLARE
-    v_string ALIAS FOR $1;
-    index ALIAS FOR $2;
-BEGIN
-    -- Some computations here
-END;
-' LANGUAGE 'plpgsql';
-
-
-CREATE FUNCTION use_many_fields(tablename) RETURNS TEXT AS '
-DECLARE
-    in_t ALIAS FOR $1;
-BEGIN
-    RETURN in_t.f1 || in_t.f3 || in_t.f5 || in_t.f7;
-END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-     </para>
-    </sect2>
-
-    <sect2 id="plpgsql-declaration-rowtypes">
-     <title>Row Types</title>
-
-    <para>
-<synopsis>
-<replaceable>name</replaceable> <replaceable>tablename</replaceable><literal>%ROWTYPE</literal>;
-</synopsis>
-    </para>
-
-   <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 SELECT or 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>
-    Presently, a row variable can only be declared using the
-    <literal>%ROWTYPE</literal> notation; although one might expect a
-    bare table name to work as a type declaration, it won't be accepted
-    within <application>PL/pgSQL</application> functions.
-   </para>
-
-   <para>
-    Parameters to a function can be
-    composite types (complete table rows). In that case, the
-    corresponding identifier $n 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 attributes of a table row are accessible in a
-    row-type variable, not OID or other system attributes (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(n)</type>.
-<programlisting>
-CREATE FUNCTION use_two_tables(tablename) RETURNS TEXT AS '
-DECLARE
-    in_t ALIAS FOR $1;
-    use_t table2name%ROWTYPE;
-BEGIN
-    SELECT * INTO use_t FROM table2name WHERE ... ;
-    RETURN in_t.f1 || use_t.f3 || in_t.f5 || use_t.f7;
-END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-   </para>
-  </sect2>
-
-    <sect2 id="plpgsql-declaration-records">
-     <title>Records</title>
-
-    <para>
-<synopsis>
-<replaceable>name</replaceable> RECORD;
-</synopsis>
-    </para>
-
-   <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 SELECT or 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, <emphasis>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.
-    Thus, for example, one cannot declare a function returning
-    <literal>RECORD</>.
-   </para>
-  </sect2>
-
-    <sect2 id="plpgsql-declaration-attributes">
-     <title>Attributes</title>
-
-     <para>
-      Using the <type>%TYPE</type> and <type>%ROWTYPE</type>
-      attributes, you can declare variables with the same
-      data type or structure as another database item (e.g: a
-      table field).
-     </para>
-
-     <variablelist>
-      <varlistentry>
-       <term>
-        <replaceable>variable</replaceable>%TYPE
-       </term>
-       <listitem>
-        <para>
-         <type>%TYPE</type> provides the data type of a
-         variable or database column. You can use this to
-         declare variables that will hold database
-         values. For example, let's say you have a column
-         named <type>user_id</type> in your
-         <type>users</type> table. To declare a variable with
-         the same data type as <structname>users</>.<structfield>user_id</> you write:
-<programlisting>
-user_id   users.user_id%TYPE;
-</programlisting>
-        </para>
-
-        <para>
-         By using <type>%TYPE</type> you don't need to know
-         the data type of the structure you are referencing,
-         and most important, if the data type of the
-         referenced item changes in the future (e.g: you
-         change your table definition of user_id from INTEGER to
-         REAL), you may not need to change your function
-         definition.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>
-        <literal><replaceable>table</replaceable>%ROWTYPE</literal>
-       </term>
-       <listitem>
-        <para>
-	 <type>%ROWTYPE</type> provides the composite data type corresponding
-	 to a whole row of the specified table.
-	 <replaceable>table</replaceable> must be an existing
-	 table or view name of the database.
-        </para>
-
-<programlisting>
-DECLARE
-    users_rec users%ROWTYPE;
-    user_id users.user_id%TYPE;
-BEGIN
-    user_id := users_rec.user_id;
-    ...
-
-CREATE FUNCTION does_view_exist(INTEGER) RETURNS bool AS '
-   DECLARE
-        key ALIAS FOR $1;
-        table_data cs_materialized_views%ROWTYPE;
-   BEGIN
-        SELECT INTO table_data * FROM cs_materialized_views
-               WHERE sort_key=key;
-
-        IF NOT FOUND THEN
-           RETURN false;
-        END IF;
-        RETURN true;
-   END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </sect2>
-
-    <sect2 id="plpgsql-declaration-renaming-vars">
-     <title>RENAME</title>
-
-     <para>
-<synopsis>
-RENAME <replaceable>oldname</replaceable> TO <replaceable>newname</replaceable>;
-</synopsis>
-
-      Using the RENAME declaration you can change the name of a variable,
-      record or row. This is primarily useful if NEW or OLD should be
-      referenced by another name inside a trigger procedure.  See also ALIAS.
-     </para>
-
-     <para>
-      Examples:
-<programlisting>
-RENAME id TO user_id;
-RENAME this_var TO that_var;
-</programlisting>
-     </para>
-
-    <note>
-    <para>
-     RENAME appears to be broken as of PostgreSQL 7.2.  Fixing this is
-     of low priority, since ALIAS covers most of the practical uses of
-     RENAME.
-    </para>
-    </note>
-
-    </sect2>
-  </sect1>
-
-  <sect1 id="plpgsql-expressions">
-  <title>Expressions</title>
-
-    <para>
-     All expressions used in <application>PL/pgSQL</application> statements
-     are processed using the server's regular SQL executor. Expressions that
-     appear to contain 
-     constants may in fact require run-time evaluation
-     (e.g. <literal>'now'</literal>  for the 
-     <type>timestamp</type> type) so
-     it is impossible for the <application>PL/pgSQL</application> parser
-     to identify real constant values other than the NULL keyword. All
-     expressions are evaluated internally by executing a query
-<synopsis>
-SELECT <replaceable>expression</replaceable>
-</synopsis>
-     using the <acronym>SPI</acronym> manager. In the expression, occurrences
-     of <application>PL/pgSQL</application> variable 
-     identifiers are replaced by parameters and the actual values from
-     the variables are passed to the executor in the parameter array.
-     This allows the query plan for the SELECT to be prepared just once
-     and then re-used for subsequent evaluations.
-    </para>
-
-    <para>
-     The evaluation done by the <productname>PostgreSQL</productname>
-     main parser has some side
-     effects on the interpretation of constant values. In detail there
-     is a difference between what these two functions do:
-
-<programlisting>
-CREATE FUNCTION logfunc1 (TEXT) RETURNS TIMESTAMP AS '
-    DECLARE
-        logtxt ALIAS FOR $1;
-    BEGIN
-        INSERT INTO logtable VALUES (logtxt, ''now'');
-        RETURN ''now'';
-    END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-
-     and
-
-<programlisting>
-CREATE FUNCTION logfunc2 (TEXT) RETURNS TIMESTAMP AS '
-    DECLARE
-        logtxt ALIAS FOR $1;
-        curtime timestamp;
-    BEGIN
-        curtime := ''now'';
-        INSERT INTO logtable VALUES (logtxt, curtime);
-        RETURN curtime;
-    END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-
-     In the case of <function>logfunc1()</function>, the 
-     <productname>PostgreSQL</productname> main parser knows when 
-     preparing the plan for the INSERT, that the string 
-     <literal>'now'</literal> should be interpreted as 
-     <type>timestamp</type> because the target field of <classname>logtable</classname>
-     is of that type. Thus, it will make a constant from it at this
-     time and this constant value is then used in all invocations of 
-     <function>logfunc1()</function> during the lifetime of the
-     backend. Needless to say that this isn't what the
-     programmer wanted.
-    </para>
-
-    <para>
-     In the case of <function>logfunc2()</function>, the 
-     <productname>PostgreSQL</productname> main parser does not know
-     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>
-
-    <para>
-     The mutable nature of record variables presents a 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 between calls of one and the same expression,
-     since the expression will be planned using the data type that is present
-     when the expression is first reached.
-     Keep this in mind when writing trigger procedures that handle events
-     for more than one table.  (EXECUTE can be used to get around this
-     problem when necessary.)
-    </para>
-  </sect1>
-
-  <sect1 id="plpgsql-statements">
-  <title>Basic Statements</title>
-
-   <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 query, and is sent to the main database engine to execute
-    (after substitution for any <application>PL/pgSQL</application> variables
-    used in the statement).  Thus,
-    for example, SQL <command>INSERT</>, <command>UPDATE</>, and
-    <command>DELETE</> commands may be considered to be statements of
-    <application>PL/pgSQL</application>.  But they are not specifically
-    listed here.
-   </para>
-   
-   <sect2 id="plpgsql-statements-assignment">
-    <title>Assignment</title>
-
-    <para>
-     An assignment of a value to a variable or row/record field is
-     written as:
-<synopsis>
-<replaceable>identifier</replaceable> := <replaceable>expression</replaceable>;
-</synopsis>
-     As explained above, 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.
-    </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>
-user_id := 20;
-tax := subtotal * 0.06;
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-select-into">
-    <title>SELECT INTO</title>
-
-    <para>
-     The result of a SELECT command yielding multiple columns (but
-     only one row) can be assigned to a record variable, row-type
-     variable, or list of scalar variables.  This is done by:
-
-<synopsis>
-SELECT INTO <replaceable>target</replaceable> <replaceable>expressions</replaceable> FROM ...;
-</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. Note that this is quite different from
-     <productname>PostgreSQL</>'s normal interpretation of SELECT INTO, which is that the
-     INTO target is a newly created table.  (If you want to create a
-     table from a SELECT result inside a <application>PL/pgSQL</application> function, use the
-     syntax <command>CREATE TABLE ... AS SELECT</command>.)
-    </para>
-
-    <para>
-     If a row or a variable list is used as target, the selected values
-     must exactly match the structure of the target(s), or 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>
-     Except for the INTO clause, the SELECT statement is the same as a normal
-     SQL SELECT query and can use the full power of SELECT.
-    </para>
-
-    <para>
-     If the SELECT query returns zero rows, NULLs are assigned to the
-     target(s).  If the SELECT query returns multiple rows, the first
-     row is assigned to the target(s) and the rest are discarded.
-     (Note that <quote>the first row</> is not well-defined unless you've
-     used ORDER BY.)
-    </para>
-
-    <para>
-     At present, the INTO clause can appear almost anywhere in the SELECT
-     query, but it is recommended to place it immediately after the SELECT
-     keyword as depicted above.  Future versions of
-     <application>PL/pgSQL</application> may be less forgiving about
-     placement of the INTO clause.
-    </para>
-
-    <para>
-     There is a special variable named FOUND of type
-     <type>boolean</type> that can be used immediately after a SELECT
-     INTO to check if an assignment had success (that is, at least one
-     row was returned by the SELECT).  For example,
-  
-<programlisting>
-SELECT INTO myrec * FROM EMP WHERE empname = myname;
-IF NOT FOUND THEN
-    RAISE EXCEPTION ''employee % not found'', myname;
-END IF;
-</programlisting>
-
-     Alternatively, you can use the IS NULL (or ISNULL) conditional to
-     test for NULLity of a RECORD/ROW result.  Note that there is no
-     way to tell whether any additional rows might have been discarded.
-    </para>
-
-    <para>
-<programlisting>
-DECLARE
-    users_rec RECORD;
-    full_name varchar;
-BEGIN
-    SELECT INTO users_rec * FROM users WHERE user_id=3;
-
-    IF users_rec.homepage IS NULL THEN
-        -- user entered no homepage, return "http://"
-
-        RETURN ''http://'';
-    END IF;
-END;
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-statements-perform">
-    <title>Executing an expression or query with no result</title>
-
-    <para>
-     Sometimes one wishes to evaluate an expression or query but discard
-     the result (typically because one is calling a function that has
-     useful side-effects but no useful result value).  To do this in
-     <application>PL/pgSQL</application>, use the PERFORM statement:
-
-<synopsis>
-PERFORM <replaceable>query</replaceable>;
-</synopsis>
-
-     This executes a <literal>SELECT</literal>
-     <replaceable>query</replaceable> and discards the
-     result. <application>PL/pgSQL</application> variables are substituted
-     in the query as usual.
-    </para>
-
-    <note>
-    <para>
-     One might expect that SELECT with no INTO clause would accomplish
-     this result, but at present the only accepted way to do it is PERFORM.
-    </para>
-    </note>
-
-    <para>
-     An example:
-<programlisting>
-PERFORM create_mv(''cs_session_page_requests_mv'',''
-     SELECT   session_id, page_id, count(*) AS n_hits,
-              sum(dwell_time) AS dwell_time, count(dwell_time) AS dwell_count
-     FROM     cs_fact_table
-     GROUP BY session_id, page_id '');
-</programlisting>
-    </para>
-   </sect2>
-   
-   <sect2 id="plpgsql-statements-executing-dyn-queries">
-    <title>Executing dynamic queries</title>
-    
-    <para>
-     Oftentimes you will want to generate dynamic queries inside
-     your <application>PL/pgSQL</application> functions, that is,
-     queries 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 queries will not work in such
-     scenarios.  To handle this sort of problem, the EXECUTE statement
-     is provided:
-
-<synopsis>
-EXECUTE <replaceable class="command">query-string</replaceable>;
-</synopsis>
-
-     where <replaceable>query-string</replaceable> is an expression
-     yielding a string (of type
-     <type>text</type>) containing the <replaceable>query</replaceable>
-     to be executed.  This string is fed literally to the SQL engine.
-    </para>
-
-    <para>
-     Note in particular that no substitution of <application>PL/pgSQL</>
-     variables is done on the query string.  The values of variables must
-     be inserted in the query string as it is constructed.
-    </para>
-
-    <para>
-    When working with dynamic queries you will have to face
-    escaping of single quotes in <application>PL/pgSQL</>. Please refer to the
-    table in <xref linkend="plpgsql-porting">
-    for a detailed explanation that will save you some effort.
-    </para>
-     
-    <para>
-     Unlike all other queries in <application>PL/pgSQL</>, a
-     <replaceable>query</replaceable> run by an EXECUTE statement is
-     not prepared and saved just once during the life of the server.
-     Instead, the <replaceable>query</replaceable> is prepared each
-     time the statement is run. The
-     <replaceable>query-string</replaceable> can be dynamically
-     created within the procedure to perform actions on variable
-     tables and fields.
-    </para>
-  
-    <para>
-     The results from SELECT queries are discarded by EXECUTE, and
-     SELECT INTO is not currently supported within EXECUTE.  So, the
-     only way to extract a result from a dynamically-created SELECT is
-     to use the FOR-IN-EXECUTE form described later.
-    </para>
-
-    <para>
-     An example:
-<synopsis>
-EXECUTE ''UPDATE tbl SET ''
-        || quote_ident(fieldname)
-        || '' = ''
-        || quote_literal(newvalue)
-        || '' WHERE ...'';
-</synopsis>
-    </para>
-
-    <para>
-     This example shows use of the functions
-     <function>quote_ident</function>(<type>TEXT</type>) and
-     <function>quote_literal</function>(<type>TEXT</type>).
-     Variables containing field and table identifiers should be
-     passed to function <function>quote_ident()</function>.
-     Variables containing literal elements of the dynamic query
-     string should be passed to
-     <function>quote_literal()</function>.  Both take the
-     appropriate steps to return the input text enclosed in single
-     or double quotes and with any embedded special characters
-     properly escaped.
-    </para>
-
-    <para>
-     Here is a much larger example of a dynamic query and EXECUTE:
-<programlisting>
-CREATE FUNCTION cs_update_referrer_type_proc() RETURNS INTEGER AS '
-DECLARE
-    referrer_keys RECORD;  -- Declare a generic record to be used in a FOR
-    a_output varchar(4000);
-BEGIN 
-    a_output := ''CREATE FUNCTION cs_find_referrer_type(varchar,varchar,varchar) 
-                  RETURNS VARCHAR AS '''' 
-                     DECLARE 
-                         v_host ALIAS FOR $1; 
-                         v_domain ALIAS FOR $2; 
-                         v_url ALIAS FOR $3;
-                     BEGIN ''; 
-
-    -- 
-    -- Notice how we scan through the results of a query in a FOR loop
-    -- using the FOR &lt;record&gt; construct.
-    --
-
-    FOR referrer_keys IN SELECT * FROM cs_referrer_keys ORDER BY try_order LOOP
-        a_output := a_output || '' IF v_'' || referrer_keys.kind || '' LIKE '''''''''' 
-                 || referrer_keys.key_string || '''''''''' THEN RETURN '''''' 
-                 || referrer_keys.referrer_type || ''''''; END IF;''; 
-    END LOOP; 
-  
-    a_output := a_output || '' RETURN NULL; END; '''' LANGUAGE ''''plpgsql'''';''; 
- 
-    -- This works because we are not substituting any variables
-    -- Otherwise it would fail. Look at PERFORM for another way to run functions
-    
-    EXECUTE a_output; 
-END; 
-' LANGUAGE 'plpgsql';
-</programlisting>
-    </para>
-   </sect2>
-
-   <sect2 id="plpgsql-statements-diagnostics">
-    <title>Obtaining result status</title>
-
-    <para>
-<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 keyword 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> query sent down to
-     the <acronym>SQL</acronym> engine; and <varname>RESULT_OID</>,
-     the OID of the last row inserted by the most recent
-     <acronym>SQL</acronym> query.  Note that <varname>RESULT_OID</>
-     is only useful after an INSERT query.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="plpgsql-control-structures">
-   <title>Control Structures</title>
-
-   <para>
-    Control structures are probably the most useful (and
-    important) part of <application>PL/pgSQL</>. With
-    <application>PL/pgSQL</>'s control structures,
-    you can manipulate <productname>PostgreSQL</> data in a very
-    flexible and powerful way. 
-   </para>
-   
-   <sect2 id="plpgsql-statements-returning">
-    <title>Returning from a function</title>
-
-    <para>
-<synopsis>
-RETURN <replaceable>expression</replaceable>;
-</synopsis>
-
-     The function terminates and the value of
-     <replaceable>expression</replaceable> will be returned to the
-     upper executor.
-     The expression's result will be automatically cast into the
-     function's return type as described for assignments.
-    </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 RETURN statement, a run-time error
-     will occur.
-    </para>
-   </sect2>
-    
-   <sect2 id="plpgsql-conditionals">
-    <title>Conditionals</title>
-
-    <para>
-     <function>IF</function> statements let you execute commands based on
-      certain conditions.
-      <application>PL/pgSQL</> has four forms of IF: IF-THEN, IF-THEN-ELSE,
-      IF-THEN-ELSE IF, and IF-THEN-ELSIF-THEN-ELSE.
-    </para>
-
-    <sect3>
-     <title>IF-THEN</title>
-
-       <para>
-<synopsis>
-IF <replaceable>boolean-expression</replaceable> THEN
-    <replaceable>statements</replaceable>
-END IF;
-</synopsis>
-
-        IF-THEN statements are the simplest form of IF. The
-        statements between THEN and END IF will be executed if
-        the condition is true. Otherwise, they are skipped.
-
-<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>IF-THEN-ELSE</title>
-
-       <para>
-<synopsis>
-IF <replaceable>boolean-expression</replaceable> THEN
-    <replaceable>statements</replaceable>
-ELSE
-    <replaceable>statements</replaceable>
-END IF;
-</synopsis>
-
-        IF-THEN-ELSE statements add to IF-THEN by letting you
-        specify an alternative set of statements that should be executed if
-	the condition evaluates to FALSE.
-
-<programlisting>
-IF parentid IS NULL or parentid = ''''
-THEN 
-    return fullname;
-ELSE
-    return hp_true_filename(parentid) || ''/'' || fullname;
-END IF;
-
-
-IF v_count > 0 THEN 
-    INSERT INTO users_count(count) VALUES(v_count);
-    return ''t'';
-ELSE 
-    return ''f'';
-END IF;
-</programlisting>
-       </para>
-     </sect3>
-
-     <sect3>
-      <title>IF-THEN-ELSE IF</title>
-
-       <para>
-        IF statements can be nested, 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>
-        When you use this form, you are actually
-        nesting an IF statement inside the ELSE part of an outer IF
-        statement. Thus you need one END IF statement for each
-        nested IF and one for the parent IF-ELSE.
-        This is workable but grows tedious when there are many
-	alternatives to be checked.
-       </para>
-     </sect3>
-
-     <sect3>
-      <title>IF-THEN-ELSIF-ELSE</title>
-
-       <para>
-<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>
-
-        IF-THEN-ELSIF-ELSE provides a more convenient method of checking
-	many alternatives in one statement.  Formally it is equivalent
-	to nested IF-THEN-ELSE-IF-THEN commands, but only one END IF
-	is needed.
-       </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 final ELSE section is optional.
-       </para>
-
-     </sect3>
-   </sect2>
-
-   <sect2 id="plpgsql-control-structures-loops">
-    <title>Simple Loops</title>
-
-    <para>
-     With the LOOP, EXIT, WHILE and FOR statements, you can arrange
-     for your <application>PL/pgSQL</application> function to repeat
-     a series of commands.
-    </para>
-
-     <sect3>
-      <title>LOOP</title>
-
-       <para>
-<synopsis>
-<optional>&lt;&lt;label&gt;&gt;</optional>
-LOOP
-    <replaceable>statements</replaceable>
-END LOOP;
-</synopsis>
-
-        LOOP defines an unconditional loop that is repeated indefinitely
-	until terminated by an EXIT or RETURN statement.
-	The optional label can be used by
-        EXIT statements in nested loops to specify which level of
-        nesting should be terminated.
-       </para>
-     </sect3>
-
-     <sect3>
-      <title>EXIT</title>
-
-       <para>
-<synopsis>
-EXIT <optional> <replaceable>label</replaceable> </optional> <optional> WHEN <replaceable>expression</replaceable> </optional>;
-</synopsis>
-
-        If no <replaceable>label</replaceable> is given,
-        the innermost loop is terminated and the
-        statement following 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
-        END.
-       </para>
-
-       <para>
-        If WHEN is present, loop exit occurs only if the specified condition
-	is true, otherwise control passes to the statement after EXIT.
-       </para>
-
-       <para>
-        Examples:
-<programlisting>
-LOOP
-    -- some computations
-    IF count > 0 THEN
-        EXIT;  -- exit loop
-    END IF;
-END LOOP;
-
-LOOP
-    -- some computations
-    EXIT WHEN count > 0;
-END LOOP;
-
-BEGIN
-    -- some computations
-    IF stocks > 100000 THEN
-        EXIT;  -- illegal. Can't use EXIT outside of a LOOP
-    END IF;
-END;
-</programlisting>
-       </para>
-     </sect3>
-
-     <sect3>
-      <title>WHILE</title>
-
-       <para>
-<synopsis>
-<optional>&lt;&lt;label&gt;&gt;</optional>
-WHILE <replaceable>expression</replaceable> LOOP
-    <replaceable>statements</replaceable>
-END LOOP;
-</synopsis>
-
-        The WHILE statement repeats a
-        sequence of statements so long as the condition expression
-	evaluates to true.  The condition is checked just before
-	each entry to the loop body.
-       </para>
-
-       <para>
-        For example:
-<programlisting>
-WHILE amount_owed > 0 AND gift_certificate_balance > 0 LOOP
-    -- some computations here
-END LOOP;
-
-WHILE NOT boolean_expression LOOP
-    -- some computations here
-END LOOP;
-</programlisting>
-       </para>
-     </sect3>
-
-     <sect3>
-      <title>FOR (integer for-loop)</title>
-
-       <para>
-<synopsis>
-<optional>&lt;&lt;label&gt;&gt;</optional>
-FOR <replaceable>name</replaceable> IN <optional> REVERSE </optional> <replaceable>expression</replaceable> .. <replaceable>expression</replaceable> LOOP
-    <replaceable>statements</replaceable>
-END LOOP;
-</synopsis>
-
-        This form of FOR creates a loop that iterates over a range of integer
-	values. The variable 
-        <replaceable>name</replaceable> is automatically defined as type
-        integer and exists only inside the loop. The two expressions giving
-        the lower and upper bound of the range are evaluated once when entering
-        the loop. The iteration step is normally 1, but is -1 when REVERSE is
-	specified.
-       </para>
-
-       <para>
-        Some examples of integer FOR loops:
-<programlisting>
-FOR i IN 1..10 LOOP
-  -- some expressions here
-
-    RAISE NOTICE ''i is %'',i;
-END LOOP;
-
-FOR i IN REVERSE 10..1 LOOP
-    -- some expressions here
-END LOOP;
-</programlisting>
-       </para>
-     </sect3>
-   </sect2>
-
-   <sect2 id="plpgsql-records-iterating">
-    <title>Looping Through Query Results</title>
-
-    <para>
-     Using a different type of FOR loop, you can iterate through
-     the results of a query and manipulate that data
-     accordingly. The syntax is:
-<synopsis>
-<optional>&lt;&lt;label&gt;&gt;</optional>
-FOR <replaceable>record | row</replaceable> IN <replaceable>select_query</replaceable> LOOP
-    <replaceable>statements</replaceable>
-END LOOP;
-</synopsis>
-     The record or row variable is successively assigned all the rows 
-     resulting from the SELECT query and the loop body is executed 
-     for each row. Here is an example:
-    </para>
-
-    <para>
-<programlisting>
-CREATE FUNCTION cs_refresh_mviews () RETURNS INTEGER AS '
-DECLARE
-     mviews RECORD;
-BEGIN
-     PERFORM cs_log(''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
-
-         PERFORM cs_log(''Refreshing materialized view '' || 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;
-
-     PERFORM cs_log(''Done refreshing materialized views.'');
-     RETURN 1;
-end;
-' LANGUAGE 'plpgsql';
-</programlisting>
-
-     If the loop is terminated by an EXIT statement, the last
-     assigned row value is still accessible after the loop.
-    </para>
-
-    <para>
-     The FOR-IN-EXECUTE statement is another way to iterate over
-     records:
-<synopsis>
-<optional>&lt;&lt;label&gt;&gt;</optional>
-FOR <replaceable>record | row</replaceable> IN EXECUTE <replaceable>text_expression</replaceable> LOOP 
-    <replaceable>statements</replaceable>
-END LOOP;
-</synopsis>
-     This is like the previous form, except that the source SELECT
-     statement is specified as a string expression, which is evaluated
-     and re-planned on each entry to the FOR loop.  This allows the
-     programmer to choose the speed of a pre-planned query or the
-     flexibility of a dynamic query, just as with a plain EXECUTE
-     statement.
-    </para>
-
-    <note>
-    <para>
-     The <application>PL/pgSQL</> parser presently distinguishes the
-     two kinds of FOR loops (integer or record-returning) by checking
-     whether the target variable mentioned just after FOR has been
-     declared as a record/row variable.  If not, it's presumed to be
-     an integer FOR loop.  This can cause rather nonintuitive error
-     messages when the true problem is, say, that one has
-     misspelled the FOR variable name.
-    </para>
-    </note>
-  </sect2>
-  </sect1>
-
-  <sect1 id="plpgsql-cursors">
-   <title>Cursors</title>
-
-   <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 don't normally need
-    to worry about that, since FOR loops automatically use a cursor
-    internally to avoid memory problems.) A more interesting usage is to
-    return a reference to a cursor that it has created, allowing the
-    caller to read the rows. This provides a way to return row sets
-    from functions.
-   </para>
-   
-   <sect2 id="plpgsql-cursor-declarations">
-    <title>Declaring Cursor Variables</title>
-
-    <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> CURSOR <optional> ( <replaceable>arguments</replaceable> ) </optional> FOR <replaceable>select_query</replaceable> ;
-</synopsis>
-     (<literal>FOR</> may be replaced by <literal>IS</> for Oracle
-     compatibility.)  <replaceable>arguments</replaceable>, if any,
-     are a comma-separated list of <replaceable>name</replaceable>
-     <replaceable>datatype</replaceable> pairs 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 int) IS SELECT * from tenk1 where unique1 = key;
-</programlisting>
-     All three of these variables have the data type <type>refcursor</>,
-     but the first may 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>
-
-    <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
-     four forms of the OPEN statement, two of which use unbound cursor
-     variables and the other two use bound cursor variables.
-    </para>
-
-    <sect3>
-     <title>OPEN FOR SELECT</title>
-
-       <para>
-<synopsis>
-OPEN <replaceable>unbound-cursor</replaceable> FOR SELECT ...;
-</synopsis>
-
-        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 (that is, as a simple
-	<type>refcursor</> variable).  The SELECT query is treated
-	in the same way as other SELECTs in <application>PL/pgSQL</>:
-	<application>PL/pgSQL</> variable names are substituted,
-	and the query plan is cached for possible re-use.
-
-<programlisting>
-OPEN curs1 FOR SELECT * FROM foo WHERE key = mykey;
-</programlisting>
-       </para>
-     </sect3>
-
-    <sect3>
-     <title>OPEN FOR EXECUTE</title>
-
-       <para>
-<synopsis>
-OPEN <replaceable>unbound-cursor</replaceable> FOR EXECUTE <replaceable class="command">query-string</replaceable>;
-</synopsis>
-
-        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 (that is, as a simple
-	<type>refcursor</> variable).  The query is specified as a
-	string expression in the same way as in the EXECUTE command.
-	As usual, this gives flexibility so the query can vary
-	from one run to the next.
-
-<programlisting>
-OPEN curs1 FOR EXECUTE ''SELECT * FROM '' || quote_ident($1);
-</programlisting>
-       </para>
-     </sect3>
-
-    <sect3>
-     <title>OPENing a bound cursor</title>
-
-       <para>
-<synopsis>
-OPEN <replaceable>bound-cursor</replaceable> <optional> ( <replaceable>argument_values</replaceable> ) </optional>;
-</synopsis>
-
-        This form of OPEN 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 EXECUTE in this case.
-
-<programlisting>
-OPEN curs2;
-OPEN curs3(42);
-</programlisting>
-       </para>
-     </sect3>
-   </sect2>
-
-   <sect2 id="plpgsql-cursor-using">
-    <title>Using Cursors</title>
-
-    <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 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 useful to reference an open cursor
-     only until the end of the transaction.
-    </para>
-
-    <sect3>
-     <title>FETCH</title>
-
-       <para>
-<synopsis>
-FETCH <replaceable>cursor</replaceable> INTO <replaceable>target</replaceable>;
-</synopsis>
-
-        FETCH retrieves the next row from the cursor into a target,
-	which may be a row variable, a record variable, or a comma-separated
-	list of simple variables, just like SELECT INTO.  As with
-	SELECT INTO, the special variable FOUND may be checked to see
-	whether a row was obtained or not.
-
-<programlisting>
-FETCH curs1 INTO rowvar;
-FETCH curs2 INTO foo,bar,baz;
-</programlisting>
-       </para>
-     </sect3>
-
-    <sect3>
-     <title>CLOSE</title>
-
-       <para>
-<synopsis>
-CLOSE <replaceable>cursor</replaceable>;
-</synopsis>
-
-        CLOSE 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.
-
-<programlisting>
-CLOSE curs1;
-</programlisting>
-       </para>
-     </sect3>
- 
-    <sect3>
-     <title>Returning Cursors</title>
-
-       <para>
-
-        <application>PL/pgSQL</> functions can return cursors to the
-        caller. This is used to return multiple rows or columns from the
-        function. The function opens the cursor and returns the cursor
-        name 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 cursor name returned by the function can be specified by the
-        caller or automatically generated. The following example shows
-        how 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';
-
-BEGIN;
-SELECT reffunc2();
-  
-        reffunc2      
-  --------------------
-   &lt;unnamed cursor 1&gt;
-  (1 row)
-
-FETCH ALL IN "&lt;unnamed cursor 1&gt;";
-COMMIT;
-</programlisting>
-       </para>
-     </sect3>
-   </sect2>
-  </sect1>
-
-  <sect1 id="plpgsql-errors-and-messages">
-   <title>Errors and Messages</title>
-
-   <para>
-    Use the RAISE statement to report messages and raise errors.
-
-<synopsis>
-RAISE <replaceable class="parameter">level</replaceable> '<replaceable class="parameter">format</replaceable>' <optional>, <replaceable class="parameter">variable</replaceable> <optional>...</optional></optional>;
-</synopsis>
-
-    Possible levels are DEBUG (write the message into the postmaster log),
-    NOTICE (write the message into the postmaster log and forward it to
-    the client application) and EXCEPTION (raise an error,
-    aborting the transaction).
-   </para>
-
-   <para>
-    Inside the format string, <literal>%</literal> is replaced by the next
-    optional argument's external representation.
-    Write <literal>%%</literal> to emit a literal <literal>%</literal>.
-    Note that the optional arguments must presently
-    be simple variables, not expressions, and the format must be a simple
-    string literal.
-   </para>
-
-   <!--
-   This example should work, but does not:
-   	RAISE NOTICE ''Id number '' || key || '' not found!'';
-   Put it back when we allow non-string-literal formats.
-    -->
-
-   <para>
-    Examples:
-<programlisting>
-RAISE NOTICE ''Calling cs_create_job(%)'',v_job_id;
-</programlisting>
-    In this example, the value of v_job_id will replace the % in the
-    string.
-   </para>
-
-   <para>
-<programlisting>
-RAISE EXCEPTION ''Inexistent ID --> %'',user_id;
-</programlisting>
-    This will abort the transaction with the given error message.
-   </para>
-
-  <sect2 id="plpgsql-exceptions">
-   <title>Exceptions</title>
-
-    <para>
-     <productname>PostgreSQL</productname> does not have a very smart
-     exception handling model. Whenever the parser, planner/optimizer
-     or executor decide that a statement cannot be processed any longer,
-     the whole transaction gets aborted and the system jumps back
-     into the main loop to get the next query from the client application.
-    </para>
-
-    <para>
-     It is possible to hook into the error mechanism to notice that this
-     happens. But currently it is impossible to tell what really
-     caused the abort (input/output conversion error, floating-point
-     error, parse error). And it is possible that the database backend
-     is in an inconsistent state at this point so returning to the upper
-     executor or issuing more commands might corrupt the whole database.
-    </para>
-
-    <para>
-     Thus, the only thing <application>PL/pgSQL</application> currently does when it encounters
-     an abort during execution of a function or trigger
-     procedure is to write some additional NOTICE level log messages
-     telling in which function and where (line number and type of
-     statement) this happened.  The error always stops execution of
-     the function.
-    </para>
-  </sect2>
- </sect1>
-
- <sect1 id="plpgsql-trigger">
-  <title>Trigger Procedures</title>
-
-  <para>
-   <application>PL/pgSQL</application> can be used to define trigger
-   procedures. A trigger procedure is created with the <command>CREATE
-   FUNCTION</command> command as a function with no arguments and a return
-   type of <type>OPAQUE</type>.  Note that the function must be declared
-   with no arguments even if it expects to receive arguments specified
-   in <command>CREATE TRIGGER</> --- 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 INSERT/UPDATE
-       operations in ROW level triggers.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><varname>OLD</varname></term>
-     <listitem>
-      <para>
-       Data type <type>RECORD</type>; variable holding the old database row for UPDATE/DELETE
-       operations in ROW level triggers.
-      </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 either 
-              <literal>BEFORE</literal> or <literal>AFTER</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> 
-              or <literal>DELETE</literal> telling
-       for which operation the trigger is 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.
-      </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 and can be given as an expression. Invalid
-       indices (&lt; 0 or &gt;= tg_nargs) result in a NULL value.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-   <para>
-    A trigger function must return either NULL or a record/row value
-    having exactly the structure of the table the trigger was fired for.
-    Triggers fired BEFORE may return NULL to signal the trigger manager
-    to skip the rest of the operation for this row (ie, subsequent triggers
-    are not fired, and the INSERT/UPDATE/DELETE does not occur for this
-    row).  If a non-NULL value is returned then the operation proceeds with
-    that row value.  Note that returning a row value different from the
-    original value of NEW alters the row that will be inserted or updated.
-    It is possible to replace single values directly
-    in NEW and return that, or to build a complete new record/row to
-    return.
-   </para>
-
-   <para>
-    The return value of a trigger fired AFTER is ignored; it may as well
-    always return a NULL value.  But an AFTER trigger can still abort the
-    operation by raising an error.
-   </para>
-
-   <example>
-    <title>A <application>PL/pgSQL</application> Trigger Procedure Example</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 ensures that an employee's name is given and that the
-     salary is a positive value.
-
-<programlisting>
-CREATE TABLE emp (
-    empname text,
-    salary integer,
-    last_date timestamp,
-    last_user text
-);
-
-CREATE FUNCTION emp_stamp () RETURNS OPAQUE AS '
-    BEGIN
-        -- Check that empname and salary are given
-        IF NEW.empname ISNULL THEN
-            RAISE EXCEPTION ''empname cannot be NULL value'';
-        END IF;
-        IF NEW.salary ISNULL THEN
-            RAISE EXCEPTION ''% cannot have NULL salary'', NEW.empname;
-        END IF;
-
-        -- Who works for us when she must pay for?
-        IF NEW.salary < 0 THEN
-            RAISE EXCEPTION ''% cannot have a negative salary'', NEW.empname;
-        END IF;
-
-        -- Remember who changed the payroll when
-        NEW.last_date := ''now'';
-        NEW.last_user := current_user;
-        RETURN NEW;
-    END;
-' LANGUAGE 'plpgsql';
-
-CREATE TRIGGER emp_stamp BEFORE INSERT OR UPDATE ON emp
-    FOR EACH ROW EXECUTE PROCEDURE emp_stamp();
-</programlisting>
-    </para>
-   </example>
-  </sect1>
-
-  <!-- **** PL/pgSQL Examples **** -->
-
-  <sect1 id="plpgsql-examples">
-   <title>Examples</title>
-
-   <para>
-    Here are only a few functions to demonstrate how easy it is to
-    write <application>PL/pgSQL</>
-    functions. For more complex examples the programmer
-    might look at the regression test for <application>PL/pgSQL</>.
-   </para>
-
-   <para>
-    One painful detail in writing functions in <application>PL/pgSQL</application> is the handling
-    of single quotes. The function's source text in <command>CREATE FUNCTION</command> must
-    be a literal string. Single quotes inside of literal strings must be
-    either doubled or quoted with a backslash. We are still looking for
-    an elegant alternative. In the meantime, doubling the single quotes
-    as in the examples below should be used. Any solution for this
-    in future versions of <productname>PostgreSQL</productname> will be
-    forward compatible.
-   </para>
-
-   <para>
-    For a detailed explanation and examples of how to escape single
-    quotes in different situations, please see <xref linkend="plpgsql-quote">.
-   </para>
-
-   <example>
-    <title>A Simple <application>PL/pgSQL</application> Function to Increment an Integer</title>
-
-    <para>
-     The following two <application>PL/pgSQL</application> functions are identical to their
-     counterparts from the C language function discussion. This
-     function receives an <type>integer</type> and increments it by
-     one, returning the incremented value.
-    </para>
-
-<programlisting>
-CREATE FUNCTION add_one (integer) RETURNS INTEGER AS '
-    BEGIN
-        RETURN $1 + 1;
-    END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-   </example>
-
-   <example>
-    <title>A Simple <application>PL/pgSQL</application> Function to Concatenate Text</title>
-
-    <para>
-     This function receives two <type>text</type> parameters and
-     returns the result of concatenating them.
-    </para>
-
-<programlisting>
-CREATE FUNCTION concat_text (TEXT, TEXT) RETURNS TEXT AS '
-    BEGIN
-        RETURN $1 || $2;
-    END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-   </example>
-
-   <example>
-    <title>A <application>PL/pgSQL</application> Function on Composite Type</title>
-
-    <para>
-     In this example, we take <literal>EMP</> (a table) and an
-     <type>integer</type> as arguments to our function, which returns
-     a <type>boolean</type>. If the <structfield>salary</> field of the <structname>EMP</> table is
-     <literal>NULL</literal>, we return <literal>f</>. Otherwise we compare with
-     that field with the <type>integer</type> passed to the function
-     and return the <type>boolean</type> result of the comparison (t
-     or f). This is the <application>PL/pgSQL</application> equivalent to the example from the C
-     functions.
-    </para>
-
-<programlisting>
-CREATE FUNCTION c_overpaid (EMP, INTEGER) RETURNS BOOLEAN AS '
-    DECLARE
-        emprec ALIAS FOR $1;
-        sallim ALIAS FOR $2;
-    BEGIN
-        IF emprec.salary ISNULL THEN
-            RETURN ''f'';
-        END IF;
-        RETURN emprec.salary > sallim;
-    END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-   </example>
-  </sect1>
-
-  <!-- **** Porting from Oracle PL/SQL **** -->
-
- <sect1 id="plpgsql-porting">
-
-  <sect1info>
-   <date>
-    February 2001
-   </date>
-   <author>
-    <firstname>Roberto</firstname>
-    <surname>Mello</surname>
-    <affiliation>
-     <address>
-      <email>rmello@fslc.usu.edu</email>
-     </address>
-    </affiliation>
-   </author>
-<!--
-  Breaks HTML manifest file
-   <legalnotice>
-    <para>
-     Except for portions of this document quoted from other sources,
-     this document is licensed under the BSD License.
-    </para>
-   </legalnotice>
--->
-  </sect1info> 
-
-  <title>Porting from Oracle PL/SQL</title>
-
-  <indexterm zone="plpgsql-porting">
-   <primary>Oracle</primary>
-  </indexterm>
-
-  <indexterm zone="plpgsql-porting">
-   <primary>PL/SQL</primary>
-  </indexterm>
-
-  <note>
-   <title>Author</title>
-   <para>
-    Roberto Mello (<email>rmello@fslc.usu.edu</email>)
-   </para>
-  </note>
-
-  <para>
-   This section explains differences between Oracle's PL/SQL and
-   <productname>PostgreSQL</>'s <application>PL/pgSQL</application> languages in the hopes of helping developers
-   port applications from Oracle to <productname>PostgreSQL</>.  Most of the code here
-   is from the <ulink url="http://www.arsdigita.com">ArsDigita</ulink>
-   <ulink url="http://www.arsdigita.com/asj/clickstream">Clickstream
-   module</ulink> that I ported to <productname>PostgreSQL</> when I took an
-   internship with <ulink url="http://www.openforce.net">OpenForce
-   Inc.</ulink> in the Summer of 2000.
-  </para>
-
-  <para>
-   <application>PL/pgSQL</application> is similar to PL/SQL in many aspects. It is a block
-   structured, imperative language (all variables have to be
-   declared). PL/SQL has many more features than its <productname>PostgreSQL</>
-   counterpart, but <application>PL/pgSQL</application> allows for a great deal of functionality
-   and it is being improved constantly.
-  </para>
-
-  <sect2>
-   <title>Main Differences</title>
-
-   <para>
-    Some things you should keep in mind when porting from Oracle to <productname>PostgreSQL</>:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       No default parameters in <productname>PostgreSQL</>.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       You can overload functions in <productname>PostgreSQL</>. This is often used to work 
-       around the lack of default parameters.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Assignments, loops and conditionals are similar. 
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       No need for cursors in <productname>PostgreSQL</>, just put the query in the FOR 
-       statement (see example below)
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       In <productname>PostgreSQL</> you <emphasis>need</emphasis> to escape single
-       quotes. See <xref linkend="plpgsql-quote">.
-      </para>
-     </listitem>
-    </itemizedlist>
-   </para>
-
-   <sect3 id="plpgsql-quote">
-    <title>Quote Me on That: Escaping Single Quotes</title>
-
-    <para>
-     In <productname>PostgreSQL</> you need to escape single quotes inside your
-     function definition. This can lead to quite amusing code at
-     times, especially if you are creating a function that generates
-     other function(s), as in 
-     <xref linkend="plpgsql-porting-nastyquote">.  
-     One thing to keep in mind
-     when escaping lots of single quotes is that, except for the
-     beginning/ending quotes, all the others will come in even
-     quantity.
-    </para>
-
-    <para>
-     <xref linkend="plpgsql-quoting-table"> gives the scoop.  (You'll
-     love this little chart.)
-    </para>
-
-    <table id="plpgsql-quoting-table">
-     <title>Single Quotes Escaping Chart</title>
-
-     <tgroup cols="4">
-      <thead>
-       <row>
-        <entry>No. of Quotes</entry>
-        <entry>Usage</entry>
-        <entry>Example</entry>
-        <entry>Result</entry>
-       </row>
-      </thead>
-
-      <tbody>
-       <row>
-        <entry>1</entry>
-        <entry>To begin/terminate function bodies</entry>
-        <entry><programlisting>
-CREATE FUNCTION foo() RETURNS INTEGER AS '...'
-LANGUAGE 'plpgsql';
-</programlisting></entry>
-        <entry>as is</entry>
-       </row>
-
-       <row>
-        <entry>2</entry>
-        <entry>In assignments, SELECTs, to delimit strings, etc.</entry>
-        <entry><programlisting>
-a_output := ''Blah'';
-SELECT * FROM users WHERE f_name=''foobar'';
-</programlisting></entry>
-        <entry><literal>SELECT * FROM users WHERE f_name='foobar';</literal></entry>
-       </row>
-
-       <row>
-        <entry>4</entry>
-        <entry>
-         When you need two single quotes in your resulting string
-         without terminating that string.
-        </entry>
-        <entry><programlisting>
-a_output := a_output || '' AND name 
-    LIKE ''''foobar'''' AND ...''
-</programlisting></entry>
-        <entry><literal>AND name LIKE 'foobar' AND ...</literal></entry>
-       </row>
-
-       <row>
-        <entry>6</entry>
-        <entry>
-         When you want double quotes in your resulting string
-         <emphasis>and</emphasis> terminate that string.
-        </entry>
-        <entry><programlisting>
-a_output := a_output || '' AND name 
-    LIKE ''''foobar''''''
-</programlisting></entry>
-        <entry>
-         <literal>AND name LIKE 'foobar'</literal>
-        </entry>
-       </row>
-
-       <row>
-        <entry>10</entry>
-        <entry>
-         When you want two single quotes in the resulting string
-         (which accounts for 8 quotes) <emphasis>and</emphasis>
-         terminate that string (2 more).  You will probably only need
-         that if you were using a function to generate other functions
-         (like in <xref linkend="plpgsql-porting-nastyquote">).
-        </entry>
-        <entry><programlisting>
-a_output := a_output || '' if v_'' || 
-    referrer_keys.kind || '' like '''''''''' 
-    || referrer_keys.key_string || '''''''''' 
-    then return ''''''  || referrer_keys.referrer_type 
-    || ''''''; end if;''; 
-</programlisting></entry>
-        <entry>
-         <literal>if v_<...> like ''<...>'' then return ''<...>''; end if;</literal>
-        </entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-   </sect3>
-  </sect2>  
-
-  <sect2 id="plpgsql-porting-functions">
-   <title>
-    Porting Functions
-   </title>
-
-   <example>
-    <title>
-     A Simple Function
-    </title>
-
-    <para>
-     Here is an Oracle function:
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_fmt_browser_version(v_name IN varchar, v_version IN 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 to <application>PL/pgSQL</>:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-        <productname>PostgreSQL</productname> does not have named
-        parameters. You have to explicitly alias them inside your
-        function.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Oracle can have <literal>IN</literal>, <literal>OUT</literal>,
-        and <literal>INOUT</literal> parameters passed to functions.
-        The <literal>INOUT</literal>, for example, means that the
-        parameter will receive a value and return another. <productname>PostgreSQL</>
-        only has <quote>IN</quote> parameters and functions can return
-        only a single value.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The <literal>RETURN</literal> key word in the function
-        prototype (not the function body) becomes
-        <literal>RETURNS</literal> in <productname>PostgreSQL</>.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        On <productname>PostgreSQL</> functions are created using single quotes as
-        delimiters, so you have to escape single quotes inside your
-        functions (which can be quite annoying at times; see <xref
-        linkend="plpgsql-quote">).
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        The <literal>/show errors</literal> command does not exist in
-        <productname>PostgreSQL</>.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <para>
-     So let's see how this function would look when ported to
-     <productname>PostgreSQL</>:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_fmt_browser_version(VARCHAR, VARCHAR)
-RETURNS VARCHAR AS '
-DECLARE
-    v_name ALIAS FOR $1;
-    v_version ALIAS FOR $2;
-BEGIN
-    IF v_version IS NULL THEN
-        return v_name;
-    END IF;
-    RETURN v_name || ''/'' || v_version;
-END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-    </para>
-   </example>
- 
-   <example id="plpgsql-porting-nastyquote">
-    <title>
-     A Function that Creates Another Function
-    </title>
-
-    <para>
-     The following procedure grabs rows from a
-     <literal>SELECT</literal> statement and builds a large function
-     with the results in <literal>IF</literal> statements, for the
-     sake of efficiency. Notice particularly the differences in
-     cursors, <literal>FOR</literal> loops, and the need to escape
-     single quotes in <productname>PostgreSQL</>.
-
-<programlisting>
-CREATE OR REPLACE PROCEDURE cs_update_referrer_type_proc IS
-    CURSOR referrer_keys IS 
-        SELECT * FROM cs_referrer_keys 
-        ORDER BY try_order;
-
-    a_output VARCHAR(4000); 
-BEGIN 
-    a_output := '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 
-        a_output := a_output || ' IF v_' || referrer_key.kind || ' LIKE ''' || 
-referrer_key.key_string || ''' THEN RETURN ''' || referrer_key.referrer_type || 
-'''; END IF;'; 
-    END LOOP; 
-
-    a_output := a_output || ' RETURN NULL; END;'; 
-    EXECUTE IMMEDIATE a_output; 
-END; 
-/ 
-show errors
-</programlisting>
-    </para>
-
-    <para>
-     Here is how this function would end up in <productname>PostgreSQL</>:
-
-<programlisting>
-CREATE FUNCTION cs_update_referrer_type_proc() RETURNS INTEGER AS '
-DECLARE
-    referrer_keys RECORD;  -- Declare a generic record to be used in a FOR
-    a_output varchar(4000);
-BEGIN 
-    a_output := ''CREATE FUNCTION cs_find_referrer_type(VARCHAR,VARCHAR,VARCHAR) 
-                  RETURNS VARCHAR AS '''' 
-                     DECLARE 
-                         v_host ALIAS FOR $1; 
-                         v_domain ALIAS FOR $2; 
-                         v_url ALIAS FOR $3;
-                     BEGIN ''; 
-
-    -- 
-    -- Notice how we scan through the results of a query in a FOR loop
-    -- using the FOR &lt;record&gt; construct.
-    --
-
-    FOR referrer_keys IN SELECT * FROM cs_referrer_keys ORDER BY try_order LOOP
-        a_output := a_output || '' IF v_'' || referrer_keys.kind || '' LIKE '''''''''' 
-                 || referrer_keys.key_string || '''''''''' THEN RETURN '''''' 
-                 || referrer_keys.referrer_type || ''''''; END IF;''; 
-    END LOOP; 
-  
-    a_output := a_output || '' RETURN NULL; END; '''' LANGUAGE ''''plpgsql'''';''; 
- 
-    -- This works because we are not substituting any variables
-    -- Otherwise it would fail. Look at PERFORM for another way to run functions
-    
-    EXECUTE a_output; 
-END; 
-' LANGUAGE 'plpgsql';
-</programlisting>
-    </para>
-   </example>
- 
-   <example>
-    <title>
-     A Procedure with a lot of String Manipulation and OUT Parameters
-    </title>
-
-    <para>
-     The following Oracle PL/SQL procedure is used to parse a URL and
-     return several elements (host, path and query). It is an
-     procedure because in <application>PL/pgSQL</application> functions only one value can be returned
-     (see <xref linkend="plpgsql-porting-procedures">).  In
-     <productname>PostgreSQL</>, one way to work around this is to split the procedure
-     in three different functions: one to return the host, another for
-     the path and another for the query.
-    </para>
-
-<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, '//'); -- <productname>PostgreSQL</> doesn't have an instr function
-
-    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>
-     Here is how this procedure could be translated for <productname>PostgreSQL</>:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_parse_url_host(VARCHAR) RETURNS VARCHAR AS ' 
-DECLARE 
-    v_url ALIAS FOR $1; 
-    v_host VARCHAR; 
-    v_path VARCHAR; 
-    a_pos1 INTEGER; 
-    a_pos2 INTEGER; 
-    a_pos3 INTEGER; 
-BEGIN 
-    v_host := NULL; 
-    a_pos1 := instr(v_url,''//''); 
-
-    IF a_pos1 = 0 THEN 
-        RETURN '''';  -- Return a blank
-    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 v_host; 
-    END IF; 
-
-    v_host := substr(v_url, a_pos1 + 2, a_pos2 - a_pos1 - 2 ); 
-    RETURN v_host; 
-END; 
-' LANGUAGE 'plpgsql';
-</programlisting>
-    </para>
-   </example>
-
-   <note>
-    <para>
-     <productname>PostgreSQL</> does not have an <function>instr</function> function,
-     so you can work around it using a combination of other functions.
-     I got tired of doing this and created my own
-     <function>instr</function> functions that behave exactly like
-     Oracle's (it makes life easier). See the <xref
-     linkend="plpgsql-porting-appendix"> for the code.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="plpgsql-porting-procedures">
-   <title>
-    Procedures
-   </title>
-
-   <para>
-    Oracle procedures give a little more flexibility to the developer
-    because nothing needs to be explicitly returned, but it can be
-    through the use of <literal>INOUT</> or <literal>OUT</> parameters.
-   </para>
-
-   <para>
-    An example:
-
-<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 > 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<co id="co.plpgsql-porting-exception">
-    END;
-    COMMIT;
-END;
-/
-show errors
-</programlisting>
-   </para>
-
-   <para>
-    Procedures like this can be easily converted into <productname>PostgreSQL</>
-    functions returning an <type>INTEGER</type>. This procedure in
-    particular is interesting because it can teach us some things:
-
-    <calloutlist>
-     <callout arearefs="co.plpgsql-porting-pragma">
-      <para>
-       There is no <literal>pragma</literal> statement in <productname>PostgreSQL</>.
-      </para>
-     </callout>
-
-     <callout arearefs="co.plpgsql-porting-locktable">
-      <para>
-       If you do a <literal>LOCK TABLE</literal> 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 also cannot have transactions in <application>PL/pgSQL</application> procedures. The
-       entire function (and other functions called from therein) is
-       executed in a transaction and <productname>PostgreSQL</> rolls back the results if
-       something goes wrong. Therefore only one
-       <literal>BEGIN</literal> statement is allowed.
-      </para>
-     </callout>
-
-     <callout arearefs="co.plpgsql-porting-exception">
-      <para>
-       The exception when would have to be replaced by an
-       <literal>IF</literal> statement.
-      </para>
-     </callout>
-    </calloutlist>
-   </para>
-
-   <para>
-    So let's see one of the ways we could port this procedure to <application>PL/pgSQL</>:
-
-<programlisting>
-CREATE OR REPLACE FUNCTION cs_create_job(INTEGER) RETURNS INTEGER AS '
-DECLARE
-    v_job_id ALIAS FOR $1;
-    a_running_job_count INTEGER;
-    a_num INTEGER;
-    -- PRAGMA AUTONOMOUS_TRANSACTION;
-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 > 0
-    THEN
-        -- COMMIT; -- free lock
-        RAISE EXCEPTION ''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);
-
-    SELECT count(*) into a_num 
-    FROM cs_jobs 
-    WHERE job_id=v_job_id;
-    IF NOT FOUND THEN  -- If nothing was returned in the last query
-        -- This job is not in the table so lets insert it.
-        INSERT INTO cs_jobs(job_id, start_stamp) VALUES (v_job_id, sysdate());
-        RETURN 1;
-    ELSE
-        RAISE NOTICE ''Job already running.'';<co id="co.plpgsql-porting-raise">
-    END IF;
-
-    RETURN 0;
-END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-
-    <calloutlist>
-     <callout arearefs="co.plpgsql-porting-raise">
-      <para>
-       Notice how you can raise notices (or errors) in <application>PL/pgSQL</>.
-      </para>
-     </callout>
-    </calloutlist>
-   </para>
-  </sect2>
-
-  <sect2 id="plpgsql-porting-packages">
-   <title>
-    Packages
-   </title>
-
-   <note>
-    <para>
-     I haven't done much with packages myself, so if there are
-     mistakes here, please let me know.
-    </para>
-   </note>
-
-   <para>
-    Packages are a way Oracle gives you to encapsulate PL/SQL
-    statements and functions into one entity, like Java classes, where
-    you define methods and objects. You can access these
-    objects/methods with a <quote><literal>.</literal></quote>
-    (dot). Here is an example of an Oracle package from ACS 4 (the
-    <ulink url="http://www.arsdigita.com/doc/">ArsDigita Community
-    System</ulink>):
-
-<programlisting>
-CREATE OR REPLACE PACKAGE BODY acs
-AS
-  FUNCTION add_user (
-    user_id     IN users.user_id%TYPE DEFAULT NULL,
-    object_type     IN acs_objects.object_type%TYPE DEFAULT 'user',
-    creation_date   IN acs_objects.creation_date%TYPE DEFAULT sysdate,
-    creation_user   IN acs_objects.creation_user%TYPE DEFAULT NULL,
-    creation_ip     IN acs_objects.creation_ip%TYPE DEFAULT NULL,
-  ...
-  ) RETURN users.user_id%TYPE
-  IS
-    v_user_id       users.user_id%TYPE;
-    v_rel_id        membership_rels.rel_id%TYPE;
-  BEGIN
-    v_user_id := acs_user.new (user_id, object_type, creation_date,
-                creation_user, creation_ip, email, ...
-    RETURN v_user_id;
-  END;
-END acs;
-/
-show errors
-</programlisting>
-   </para>
-
-   <para>
-    We port this to <productname>PostgreSQL</> by creating the different objects of
-    the Oracle package as functions with a standard naming
-    convention. We have to pay attention to some other details, like
-    the lack of default parameters in <productname>PostgreSQL</> functions. The above
-    package would become something like this:
- 
-<programlisting>
-CREATE FUNCTION acs__add_user(INTEGER,INTEGER,VARCHAR,TIMESTAMP,INTEGER,INTEGER,...)
-RETURNS INTEGER AS '
-DECLARE
-    user_id ALIAS FOR $1;
-    object_type ALIAS FOR $2;
-    creation_date ALIAS FOR $3;
-    creation_user ALIAS FOR $4;
-    creation_ip ALIAS FOR $5;
-    ...
-    v_user_id users.user_id%TYPE;
-    v_rel_id membership_rels.rel_id%TYPE;
-BEGIN
-    v_user_id := acs_user__new(user_id,object_type,creation_date,creation_user,creation_ip, ...);
-    ...
-
-    RETURN v_user_id;
-END;
-' LANGUAGE 'plpgsql';
-</programlisting>
-   </para>
-  </sect2>
-
-  <sect2 id="plpgsql-porting-other">
-   <title>
-    Other Things to Watch For
-   </title>
-
-   <sect3>
-    <title>EXECUTE</title>
-
-    <para>
-     The <productname>PostgreSQL</> version of <literal>EXECUTE</literal> works
-     nicely, but you have to remember to use
-     <function>quote_literal(TEXT)</function> and
-     <function>quote_string(TEXT)</function> as described in <xref
-     linkend="plpgsql-statements-executing-dyn-queries">.  Constructs of the type
-     <literal>EXECUTE ''SELECT * from $1'';</literal> will not work
-     unless you use these functions.
-    </para>
-   </sect3>
-
-   <sect3 id="plpgsql-porting-optimization">
-    <title>Optimizing <application>PL/pgSQL</application> Functions</title>
-
-    <para>
-     <productname>PostgreSQL</> gives you two function creation modifiers to optimize
-     execution: <literal>iscachable</literal> (function always returns
-     the same result when given the same arguments) and
-     <literal>isstrict</literal> (function returns NULL if any
-     argument is NULL).  Consult the <command>CREATE
-     FUNCTION</command> reference for details.
-    </para>
-
-    <para>
-     To make use of these optimization attributes, you have to use the
-     <literal>WITH</literal> modifier in your <command>CREATE
-     FUNCTION</command> statement.  Something like:
-
-<programlisting>
-CREATE FUNCTION foo(...) RETURNS INTEGER AS '
-...
-' LANGUAGE 'plpgsql'
-WITH (isstrict, iscachable);
-</programlisting>
-    </para>
-   </sect3>
-  </sect2>
-
-  <sect2 id="plpgsql-porting-appendix">
-   <title>
-    Appendix
-   </title>
-
-   <sect3>
-    <title>
-     Code for my <function>instr</function> functions
-    </title>
-
-    <comment>
-     This function should probably be integrated into the core.
-    </comment>
-
-<programlisting>
---
--- instr functions that mimic Oracle's counterpart
--- Syntax: instr(string1,string2,[n],[m]) where [] denotes optional params.
--- 
--- 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).
---
--- by Roberto Mello (rmello@fslc.usu.edu)
--- modified by Robert Gaszewski (graszew@poland.com)
--- Licensed under the GPL v2 or later.
---
-
-CREATE FUNCTION instr(VARCHAR,VARCHAR) RETURNS INTEGER AS '
-DECLARE
-    pos integer;
-BEGIN
-    pos:= instr($1,$2,1);
-    RETURN pos;
-END;
-' LANGUAGE 'plpgsql';
-
-
-CREATE FUNCTION instr(VARCHAR,VARCHAR,INTEGER) RETURNS INTEGER AS '
-DECLARE
-    string ALIAS FOR $1;
-    string_to_search ALIAS FOR $2;
-    beg_index ALIAS FOR $3;
-    pos integer NOT NULL DEFAULT 0;
-    temp_str VARCHAR;
-    beg INTEGER;
-    length INTEGER;
-    ss_length INTEGER;
-BEGIN
-    IF beg_index > 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 > 0 LOOP
-           temp_str := substring(string FROM beg FOR ss_length);
-	         pos := position(string_to_search IN temp_str);
-
-	         IF pos > 0 THEN
-		           RETURN beg;
-	         END IF;
-
-	         beg := beg - 1;
-       END LOOP;
-       RETURN 0;
-    END IF;
-END;
-' LANGUAGE 'plpgsql';
-
---
--- Written by Robert Gaszewski (graszew@poland.com)
--- Licensed under the GPL v2 or later.
---
-CREATE FUNCTION instr(VARCHAR,VARCHAR,INTEGER,INTEGER) RETURNS INTEGER AS '
-DECLARE
-    string ALIAS FOR $1;
-    string_to_search ALIAS FOR $2;
-    beg_index ALIAS FOR $3;
-    occur_index ALIAS FOR $4;
-    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 > 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 > 0 LOOP
-            temp_str := substring(string FROM beg FOR ss_length);
-            pos := position(string_to_search IN temp_str);
-
-            IF pos > 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';
-</programlisting>
-   </sect3>
-  </sect2>
-  
- </sect1>
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/pltcl.sgml b/doc/src/sgml/pltcl.sgml
deleted file mode 100644
index a6109b0195d..00000000000
--- a/doc/src/sgml/pltcl.sgml
+++ /dev/null
@@ -1,704 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/pltcl.sgml,v 2.20 2002/03/22 19:20:21 petere Exp $
--->
-
- <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>
-
-  <para>
-   PL/Tcl is a loadable procedural language for the
-   <productname>PostgreSQL</productname> database system
-   that enables the Tcl language to be used to write functions and
-   trigger procedures.
-  </para>
-
-  <para>
-   This package was originally written by Jan Wieck.
-  </para>
-
-  <!-- **** PL/Tcl overview **** -->
-
-  <sect1 id="pltcl-overview">
-   <title>Overview</title>
-
-   <para>
-    PL/Tcl offers most of the capabilities a function
-    writer has in the C language, except for some restrictions.
-   </para>
-   <para>
-    The good restriction is that everything is executed in a safe
-    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()</>. There is no way to access internals of the
-    database backend or to gain OS-level access under the permissions of the
-    <productname>PostgreSQL</productname> user ID, as a C function can do.
-    Thus, any unprivileged database user may be
-    permitted to use this language.
-   </para>
-   <para>
-    The other, implementation restriction is that Tcl procedures 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
-    mail.  To handle these cases, there is a variant of PL/Tcl called PL/TclU
-    (for untrusted Tcl).  This is the exact same language except that a full
-    Tcl interpreter is used.  <emphasis>If 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 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 for the PL/Tcl and PL/TclU call handlers is
-    automatically built and installed in the
-    <productname>PostgreSQL</productname> 
-    library directory if Tcl/Tk support is specified
-    in the configuration step of the installation procedure.  To install
-    PL/Tcl and/or PL/TclU in a particular database, use the
-    <filename>createlang</filename> script, for example
-    <literal>createlang pltcl <replaceable>dbname</></literal> or
-    <literal>createlang pltclu <replaceable>dbname</></literal>.
-   </para>
-  </sect1>
-
-  <!-- **** PL/Tcl description **** -->
-
-  <sect1 id="pltcl-description">
-   <title>Description</title>
-
-   <sect2>
-    <title>PL/Tcl Functions and Arguments</title>
-
-    <para>
-     To create a function in the PL/Tcl language, use the standard syntax
-
-     <programlisting>
-CREATE FUNCTION <replaceable>funcname</replaceable> (<replaceable>argument-types</replaceable>) RETURNS <replaceable>return-type</replaceable> AS '
-    # PL/Tcl function body
-' LANGUAGE 'pltcl';
-     </programlisting>
-
-     PL/TclU is the same, except that the language should 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>$n</literal> to the
-     Tcl script.  The result is returned
-     from the Tcl code in the usual way, with a <literal>return</literal>
-     statement.  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 > $2} {return $1}
-    return $2
-' LANGUAGE 'pltcl' WITH (isStrict);
-     </programlisting>
-
-     Note the clause <literal>WITH (isStrict)</>, which saves us from
-     having to think about NULL input values: if a NULL is passed, the
-     function will not be called at all, but will just return a NULL
-     result automatically.
-    </para>
-
-    <para>
-     In a non-strict function,
-     if the actual value of an argument is NULL, the corresponding
-     <literal>$n</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 non-null argument to return the non-null
-     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 > $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 procedure 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 that defines the overpaid_2 function (as found in the
-     older <productname>PostgreSQL</productname> documentation) in PL/Tcl:
-
-     <programlisting>
-CREATE FUNCTION overpaid_2 (EMP) RETURNS bool AS '
-    if {200000.0 < $1(salary)} {
-        return "t"
-    }
-    if {$1(age) < 30 && 100000.0 < $1(salary)} {
-        return "t"
-    }
-    return "f"
-' LANGUAGE 'pltcl';
-     </programlisting>
-    </para>
-
-    <para>
-     There is not currently any support for returning a composite-type
-     result value.
-    </para>
-
-   </sect2>
-
-   <sect2>
-    <title>Data Values in PL/Tcl</title>
-
-    <para>
-     The argument values supplied to a PL/Tcl function's script are simply
-     the input arguments converted to text form (just as if they had been
-     displayed by a SELECT statement).  Conversely, the <literal>return</>
-     command will accept any string that is acceptable input format for
-     the function's declared return type.  So, the PL/Tcl programmer can
-     manipulate data values as if they were just text.
-    </para>
-
-   </sect2>
-
-   <sect2>
-    <title>Global Data in PL/Tcl</title>
-
-    <para>
-     Sometimes it
-     is useful to have some global status data that is held between two
-     calls to a procedure or is shared between different procedures.
-     This is easily done since
-     all PL/Tcl procedures executed in one backend share the same
-     safe Tcl interpreter.  So, any global Tcl variable is accessible to
-     all PL/Tcl procedure calls, and will persist for the duration of the
-     SQL client connection.  (Note that PL/TclU functions likewise share
-     global data, but they are in a different Tcl interpreter and cannot
-     communicate with PL/Tcl functions.)
-    </para>
-    <para>
-     To help protect PL/Tcl procedures from unintentionally interfering
-     with each other, a global
-     array is made available to each procedure via the <function>upvar</>
-     command. The global name of this variable is the procedure's internal
-     name and the local name is <literal>GD</>.  It is recommended that
-     <literal>GD</> be used
-     for private status data of a procedure.  Use regular Tcl global variables
-     only for values that you specifically intend to be shared among multiple
-     procedures.
-    </para>
-
-    <para>
-     An example of using <literal>GD</> appears in the
-     <function>spi_execp</function> example below.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Database Access from PL/Tcl</title>
-
-    <para>
-     The following commands are available to access the database from
-     the body of a PL/Tcl procedure:
-    </para>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><function>spi_exec</function> <literal>?-count <replaceable>n</replaceable>? ?-array <replaceable>name</replaceable>? <replaceable>query</replaceable> ?<replaceable>loop-body</replaceable>?</literal></term>
-      <listitem>
-       <para>
-	Execute an SQL query given as a string.  An error in the query
-	causes an error to be raised.  Otherwise, the command's return value
-	is the number of rows processed (selected, inserted, updated, or
-	deleted) by the query, or zero if the query is a utility
-	statement.  In addition, if the query is a 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 query.  The effect of this is comparable to
-	setting up the query as a cursor and then saying <literal>FETCH n</>.
-       </para>
-       <para>
-	If the query is a SELECT statement, the values of the SELECT's
-	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 SELECT
-	column names used as array indexes.
-       </para>
-       <para>
-        If the query is a 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 store occurs
-	if the 
-	SELECT 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 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
-	SELECT result (note: <replaceable>loop-body</> is ignored if the given
-	query is not a SELECT).  The values of the current row's fields
-	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 DEBUG log message for every row of 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 field of a SELECT 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>
-      <listitem>
-       <para>
-	Prepares and saves a query plan for later execution.  The saved plan
-	will be retained for the life of the current backend.
-       </para>
-       <para>
-        The query may use <firstterm>arguments</>, which are placeholders for
-	values to be supplied whenever the plan is actually executed.
-	In the query string, refer to arguments
-	by the symbols <literal>$1</literal> ... <literal>$n</literal>.
-	If the query uses arguments, the names of the argument types
-	must be given as a Tcl list.  (Write an empty list for
-	<replaceable>typelist</replaceable> if no arguments are used.)
-	Presently, the argument types must be identified by the internal
-	type names shown in pg_type; for example <literal>int4</> not
-	<literal>integer</>.
-       </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>
-
-     <varlistentry>
-      <term><function>spi_execp</> <literal>?-count <replaceable>n</replaceable>? ?-array <replaceable>name</replaceable>? ?-nulls <replaceable>string</replaceable>? <replaceable>queryid</replaceable> ?<replaceable>value-list</replaceable>? ?<replaceable>loop-body</replaceable>?</literal></term>
-      <listitem>
-       <para>
-	Execute a query previously prepared with <function>spi_prepare</>.
-	<replaceable>queryid</replaceable> is the ID returned by
-	<function>spi_prepare</>.  If the query references arguments,
-	a <replaceable>value-list</replaceable> must be supplied: this
-	is a Tcl list of actual values for the arguments.  This must be
-	the same length as the argument type list previously given to
-	<function>spi_prepare</>.  Omit <replaceable>value-list</replaceable>
-	if the query has no arguments.
-       </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 arguments are NULLs. If given, it must have exactly the
-	same length as the <replaceable>value-list</replaceable>.  If it
-	is not given, all the argument values are non-NULL.
-       </para>
-       <para>
-        Except for the way in which the query and its arguments 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>
-
-	Note that each backslash that Tcl should see must be doubled when
-	we type in the function, since the main parser processes
-	backslashes too in CREATE FUNCTION.  We need backslashes inside
-	the query string given to <function>spi_prepare</> to ensure that
-	the <literal>$n</> markers will be passed through to
-	<function>spi_prepare</> as-is, and not
-	replaced by Tcl variable substitution.
-       </para>
-      </listitem>
-     </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</>'d or <function>spi_execp</>'d query,
-	if that query was a single-row INSERT.  (If not, you get zero.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><function>quote</> <replaceable>string</replaceable></term>
-      <listitem>
-       <para>
-	Duplicates all occurrences of single quote and backslash characters
-	in the given string.  This may be used to safely quote strings
-	that are to be inserted into SQL queries given
-	to <function>spi_exec</function> or
-	<function>spi_prepare</function>.
-	For example, think about a query string like
-
-<programlisting>
-"SELECT '$val' AS ret"
-</programlisting>
-
-	where the Tcl variable val actually contains
-	<literal>doesn't</literal>. This would result
-	in the final query string
-
-<programlisting>
-SELECT 'doesn't' AS ret
-</programlisting>
-
-	which would cause a parse error during
-	<function>spi_exec</function> or
-	<function>spi_prepare</function>.
-	The submitted query should contain
-
-<programlisting>
-SELECT 'doesn''t' AS ret
-</programlisting>
-
-	which can be formed in PL/Tcl as
-
-<programlisting>
-"SELECT '[ quote $val ]' AS ret"
-</programlisting>
-
-        One advantage of <function>spi_execp</function> is that you don't
-	have to quote argument values like this, since the arguments are never
-	parsed as part of an SQL query string.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>elog</primary>
-      </indexterm>
-      <term><function>elog</> <replaceable>level</replaceable> <replaceable>msg</replaceable></term>
-      <listitem>
-       <para>
-	Emit a log or error message. Possible levels are
-	<literal>DEBUG</>, <literal>LOG</>, <literal>INFO</>,
-	<literal>NOTICE</>, <literal>WARNING</>, <literal>ERROR</>, and
-	<literal>FATAL</>. Most simply emit the given message just like
-	the <literal>elog</> backend C function. <literal>ERROR</>
-	raises an error condition: further execution of the function is
-	abandoned, and the current transaction is aborted.
-	<literal>FATAL</> aborts the transaction and causes the current
-	backend to shut down (there is probably no good reason to use
-	this error level in PL/Tcl functions, but it's provided for
-	completeness).
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-   </sect2>
-
-   <sect2>
-    <title>Trigger Procedures in PL/Tcl</title>
-
-    <indexterm>
-     <primary>triggers</primary>
-     <secondary>in PL/Tcl</secondary>
-    </indexterm>
-
-    <para>
-     Trigger procedures can be written in PL/Tcl.  As is customary in
-     <productname>PostgreSQL</productname>, a procedure that's to be called
-     as a trigger must be declared as a function with no arguments
-     and a return type of <literal>opaque</>.
-    </para>
-    <para>
-     The information from the trigger manager is passed to the procedure body
-     in the following variables:
-
-     <variablelist>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$TG_name</replaceable></term>
-       <listitem>
-	<para>
-	 The name of the trigger from the CREATE TRIGGER statement.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$TG_relid</replaceable></term>
-       <listitem>
-	<para>
-	 The object ID of the table that caused the trigger procedure
-	 to be invoked.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$TG_relatts</replaceable></term>
-       <listitem>
-	<para>
-	 A Tcl list of the table field names, prefixed with an empty list
-         element. So looking up an element name in the list with Tcl's
-         <function>lsearch</> command returns the element's number starting
-	 with 1 for the first column, the same way the fields are customarily
-	 numbered in <productname>PostgreSQL</productname>.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$TG_when</replaceable></term>
-       <listitem>
-	<para>
-	 The string <literal>BEFORE</> or <literal>AFTER</> depending on the
-	 type of trigger call.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$TG_level</replaceable></term>
-       <listitem>
-	<para>
-	 The string <literal>ROW</> or <literal>STATEMENT</> depending on the
-	 type of trigger call.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$TG_op</replaceable></term>
-       <listitem>
-	<para>
-	 The string <literal>INSERT</>, <literal>UPDATE</> or
-	 <literal>DELETE</> depending on the type of trigger call.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$NEW</replaceable></term>
-       <listitem>
-	<para>
-	 An associative array containing the values of the new table row for
-	 INSERT/UPDATE actions, or empty for DELETE.  The array is indexed
-	 by field name.  Fields that are NULL will not appear in the array!
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$OLD</replaceable></term>
-       <listitem>
-	<para>
-	 An associative array containing the values of the old table row for
-	 UPDATE/DELETE actions, or empty for INSERT.  The array is indexed
-	 by field name.  Fields that are NULL will not appear in the array!
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable class="Parameter">$args</replaceable></term>
-       <listitem>
-	<para>
-	 A Tcl list of the arguments to the procedure as given in the
-	 CREATE TRIGGER statement. These arguments are also accessible as
-	 <literal>$1</literal> ... <literal>$n</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 (INSERT/UPDATE/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 that will be inserted
-     instead of the one given in $NEW (this works for INSERT/UPDATE
-     only). Needless to say that all this is only meaningful when the trigger
-     is BEFORE and FOR EACH ROW; otherwise the return value is ignored.
-    </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 OPAQUE 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 re-used with different tables.
-    </para>
-   </sect2>
-
-   <sect2>
-       <title> Modules and the <function>unknown</> command</title>
-       <para>
-	PL/Tcl has support for auto-loading 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 after creating
-	the interpreter.
-       </para>
-       <para>
-        While the <literal>unknown</> module could actually contain any
-	initialization script you need, it normally defines a Tcl
-	<quote>unknown</> procedure that is invoked whenever Tcl does
-	not recognize an invoked procedure name.  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>
-        The <productname>PostgreSQL</productname> distribution includes
-	support scripts to maintain these tables:
-	<command>pltcl_loadmod</>, <command>pltcl_listmod</>,
-	<command>pltcl_delmod</>, as well as source for the standard
-	unknown module <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.
-       </para>
-   </sect2>
-
-   <sect2>
-    <title>Tcl Procedure Names</title>
-
-    <para>
-     In <productname>PostgreSQL</productname>, one and the 
-     same function name can be used for
-     different functions 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 procedure's pg_proc row as part of their name. Thus,
-     <productname>PostgreSQL</productname> functions with the same name
-     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>
-
-   </sect2>
-
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/postgres.sgml b/doc/src/sgml/postgres.sgml
deleted file mode 100644
index 37d2f052d66..00000000000
--- a/doc/src/sgml/postgres.sgml
+++ /dev/null
@@ -1,58 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/postgres.sgml,v 1.47 2001/11/21 05:53:41 thomas Exp $
--->
-
-<!doctype set PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
-
-<!entity % version SYSTEM "version.sgml">
-%version;
-<!entity % filelist SYSTEM "filelist.sgml">
-%filelist;
-
-<!entity % set-of-books "INCLUDE">
-<!entity % single-book "IGNORE">
-
-<!entity admin      SYSTEM "admin.sgml">
-<!entity developer  SYSTEM "developer.sgml">
-<!entity programmer SYSTEM "programmer.sgml">
-<!entity reference  SYSTEM "reference.sgml">
-<!entity tutorial   SYSTEM "tutorial.sgml">
-<!entity user       SYSTEM "user.sgml">
-
-]>
-
-<set id="postgres">
- <title>PostgreSQL &version; Documentation</title>
-
- <setinfo>
-  <corpauthor>The PostgreSQL Global Development Group</corpauthor>
-  &legal;
- </setinfo>
-
- &tutorial;
- &user;
- &admin;
- &programmer;
- &reference;
- &developer; 
- &setindex;
-
-</set>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-tabs-mode:nil
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/share/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/problems.sgml b/doc/src/sgml/problems.sgml
deleted file mode 100644
index 91626d90b25..00000000000
--- a/doc/src/sgml/problems.sgml
+++ /dev/null
@@ -1,356 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/problems.sgml,v 2.13 2002/01/20 22:19:56 petere Exp $
--->
-
-<sect1 id="bug-reporting">
- <title>Bug Reporting Guidelines</title>
-
- <para>
-  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.
- </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 it 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 the 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>
-      <productname>PostgreSQL</productname> fails to compile, build, or
-      install according to the instructions on supported platforms.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   Here <quote>program</quote> refers to any executable, not only the backend server.
-  </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>
-
-  <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>
- </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 select statement without the
-      preceding create table and insert 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.
-      The best format for a test case for
-      query-language 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 start at 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>mid-size 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>
-       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 concerned
-      environment variables or configuration files that you changed from the
-      default. Again, be exact. 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>
-      The <productname>PostgreSQL</productname> version. You can run the command
-      <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>postmaster --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.  You can also look into the
-      <filename>README</filename> file 
-      in the source directory or at the
-      name of your distribution file or package name.
-      If you run a prepackaged version, such as RPMs, say so, including any
-      subversion the package may have. If you are talking about a CVS
-      snapshot, mention that, including its date and time.
-     </para>
-
-     <para>
-      If your version is older than &version; we will almost certainly tell
-      you to upgrade. There are tons
-      of bug fixes in each new release, that is why we make new releases.
-     </para>
-     <para>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Platform information. This includes the kernel name and version, C library,
-      processor, memory information. 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 Pentiums. If
-      you have installation problems then information about compilers, make,
-      etc. is also necessary.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   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.
-  </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>
-
-  <para>
-   When writing a bug report, please choose non-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 server, mention that, do not
-   just say <quote>PostgreSQL crashes</quote>.  A crash of a single
-   backend server process is quite different from crash of the parent
-   <quote>postmaster</> process; please don't say <quote>the postmaster
-   crashed</> when you mean a single backend 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>
- </sect2>
-
- <sect2>
-  <title>Where to report bugs</title>
-
-  <para>
-   In general, send bug reports to the bug report mailing list at
-   <email>pgsql-bugs@postgresql.org</email>.
-   You are requested to use a descriptive subject for your email
-   message, perhaps parts of the error message.
-  </para>
-
-  <para> 
-   Another method is to fill in the bug report web-form available
-   at the project's web site
-   <ulink url="http://www.postgresql.org/">http://www.postgresql.org/</ulink>.
-   Entering a bug report this way causes it to be mailed to the
-   <email>pgsql-bugs@postgresql.org</email> mailing list.
-  </para>
-
-  <para> 
-   Do not send bug reports to any of the user mailing lists, such as
-   <email>pgsql-sql@postgresql.org</email> or
-   <email>pgsql-general@postgresql.org</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.
-  </para>
-
-  <para>
-   Also, please do <emphasis>not</emphasis> send reports to
-   the developers' mailing list <email>pgsql-hackers@postgresql.org</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>
-
-  <para>
-   If you have a problem with the documentation, the best place to report it
-   is the documentation mailing list <email>pgsql-docs@postgresql.org</email>.
-   Please be specific about what part of the documentation you are unhappy
-   with.
-  </para>
- 
-  <para>
-   If your bug is a portability problem on a non-supported platform,
-   send mail to <email>pgsql-ports@postgresql.org</email>,
-   so we (and you) can work on
-   porting <productname>PostgreSQL</productname> to your platform.
-  </para>
-
-  <note>
-   <para>
-    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>majordomo@postgresql.org</email>
-    with the single word <literal>help</> in the body of the message.
-   </para>
-  </note>
- </sect2>
-</sect1>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/programmer.sgml b/doc/src/sgml/programmer.sgml
deleted file mode 100644
index 0777979e8ba..00000000000
--- a/doc/src/sgml/programmer.sgml
+++ /dev/null
@@ -1,111 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/programmer.sgml,v 1.39 2002/01/07 02:29:13 petere Exp $
-
-PostgreSQL Programmer's Guide.
--->
-
-<book id="programmer">
-
- <title>PostgreSQL &version; Programmer's Guide</title>
- <bookinfo>
-  <corpauthor>The PostgreSQL Global Development Group</corpauthor>
-  &legal;
- </bookinfo>
-
-<![%single-book[
-  &intro;
-]]>
-
- <part id="programmer-client">
-  <title>Client Interfaces</title>
-
-  <partintro>
-   <para>
-    This part of the manual is the description of the client-side
-    programming interfaces and support libraries for various
-    languages.
-   </para>
-  </partintro>
-
-  &libpq;
-  &lobj;
-  &libpqpp;
-  &libpgtcl;
-  &libpgeasy;
-  &ecpg;
-  &odbc;
-  &jdbc;
-  &pygresql;
- </part>
-
- <part id="programmer-server">
-  <title>Server Programming</title>
-
-  <partintro>
-   <para>
-    This second part of the manual explains the
-    <productname>PostgreSQL</productname> approach to extensibility
-    and describe how users can extend
-    <productname>PostgreSQL</productname> by adding user-defined
-    types, operators, aggregates, and both query language and
-    programming language functions.  After a discussion of the
-    <productname>PostgreSQL</productname> rule system, we discuss the
-    trigger and SPI interfaces.
-   </para>
-  </partintro>
-
-  &arch-pg;
-  &extend;
-  &xfunc;
-  &xtypes;
-  &xoper;
-  &xaggr;
-  &rules;
-  &xindex;
-  &indexcost;
-  &gist;
-  &trigger;
-  &spi;
- </part>
-
- <part id="programmer-pl">
-  <title>Procedural Languages</title>
-
-  <partintro>
-   <para>
-    This part documents the procedural languages available in the
-    <productname>PostgreSQL</productname> distribution as well as
-    general issues concerning procedural languages.
-   </para>
-  </partintro>
-
-  &xplang;
-  &plsql;
-  &pltcl;
-  &plperl;
-  &plpython;
- </part>
-
-<![%single-book;[
- &biblio;
- &bookindex;
-]]>
-
-</book>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml
deleted file mode 100644
index 06901a8e335..00000000000
--- a/doc/src/sgml/protocol.sgml
+++ /dev/null
@@ -1,2102 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.24 2002/03/22 19:20:21 petere Exp $ -->
-
-<chapter id="protocol">
- <title>Frontend/Backend Protocol</title>
-
- <note>
-  <para>
-   Written by Phil Thompson (<email>phil@river-bank.demon.co.uk</email>).
-   Updates for protocol 2.0 by Tom Lane (<email>tgl@sss.pgh.pa.us</email>).
-  </para>
- </note>
-
- <para>
-  <application>PostgreSQL</application> uses a message-based protocol
-  for communication between frontends and backends.  The protocol is
-  implemented over <acronym>TCP/IP</acronym> and also on Unix domain
-  sockets.  <productname>PostgreSQL</productname> 6.3 introduced
-  version numbers into the protocol.  This was done in such a way as
-  to still allow connections from earlier versions of frontends, but
-  this document does not cover the protocol used by those earlier
-  versions.
- </para>
-
- <para>
-  This document describes version 2.0 of the protocol, implemented in
-  <application>PostgreSQL</application> 6.4 and later.
- </para>
-
- <para>
-  Higher level features built on this protocol (for example, how
-  <application>libpq</application> passes certain environment
-  variables after the connection is established) are covered
-  elsewhere.
- </para>
-
- <sect1 id="protocol-overview">
-  <title>Overview</title>
-
-  <para>
-   A frontend opens a connection to the server and sends a start-up
-   packet.  This includes the names of the user and of the database the
-   user wants to connect to.  The server then uses this, and the
-   information in the <filename>pg_hba.conf</filename> file to
-   determine what further authentication information it requires the
-   frontend to send (if any) and responds to the frontend accordingly.
-  </para>
-
-  <para>
-   The frontend then sends any required authentication information.
-   Once the server validates this it responds to the frontend that it
-   is authenticated and sends a message indicating successful start-up
-   (normal case) or failure (for example, an invalid database name).
-  </para>
-
-  <para>
-   In order to serve multiple clients efficiently, the server launches
-   a new <quote>backend</> process for each client.  This is transparent
-   to the protocol, however.  In the current implementation, a new child
-   process is created immediately after an incoming connection is detected.
-  </para>
-
-  <para>
-   When the frontend wishes to disconnect it sends an appropriate packet and
-   closes the connection without waiting for a response from the backend.
-  </para>
-
-  <para>
-   Packets are sent as a data stream.  The first byte determines what
-   should be expected in the rest of the packet.  The exceptions are
-   packets sent as part of the start-up and authentication exchange,
-   which comprise a packet length followed by the packet itself.  The
-   difference is historical.
-  </para>
- </sect1>
-
- <sect1 id="protocol-protocol">
-  <title>Protocol</title>
-
-  <para>
-   This section describes the message flow.  There are four different
-   types of flows depending on the state of the connection: start-up,
-   query, function call, and termination.  There are also special
-   provisions for notification responses and command cancellation,
-   which can occur at any time after the start-up phase.
-  </para>
-
-  <sect2>
-   <title>Start-up</Title>
-
-   <para>
-    Initially, the frontend sends a StartupPacket.  The server uses
-    this info and the contents of the <filename>pg_hba.conf</filename>
-    file to determine what authentication method the frontend must
-    use.  The server then responds with one of the following messages:
-
-    <variablelist>
-     <varlistentry>
-      <term>ErrorResponse</term>
-      <listitem>
-       <para>
-        The server then immediately closes the connection.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationOk</term>
-      <listitem>
-       <para>
-        The authentication exchange is completed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>AuthenticationKerberosV4</Term>
-      <listitem>
-       <para>
-        The frontend must then take part in a Kerberos V4
-        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>AuthenticationKerberosV5</Term>
-      <ListItem>
-       <Para>
-        The frontend must then 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 then send a PasswordPacket 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>AuthenticationCryptPassword</Term>
-      <ListItem>
-       <Para>
-        The frontend must then send a PasswordPacket containing the
-	password encrypted via crypt(3), using the 2-character salt
-	specified in the AuthenticationCryptPassword packet.  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 then send a PasswordPacket containing the
-	password encrypted via MD5, using the 4-character salt
-	specified in the AuthenticationMD5Password packet.  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 method 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.
-       </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 should wait
-    for further messages from the server.  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>ReadyForQuery</Term>
-      <ListItem>
-       <Para>
-        Start-up is completed.  The frontend may now issue query or
-        function call messages.
-       </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 query cycle.  Depending on the coding needs of
-    the frontend, it is reasonable to consider ReadyForQuery as
-    starting a query cycle (and then BackendKeyData indicates
-    successful conclusion of the start-up phase), or to consider
-    ReadyForQuery as ending the start-up phase and each subsequent
-    query cycle.
-   </para>
-  </sect2>
-
-  <Sect2>
-   <Title>Query</Title>
-
-   <Para>
-    A Query cycle is initiated by the frontend sending a Query message
-    to the backend.  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 may safely send a new query or
-    function call.
-   </para>
-
-   <Para>
-    The possible response messages from the backend are:
-
-    <VariableList>
-     <VarListEntry>
-      <Term>CompletedResponse</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.  The frontend should then send a CopyDataRows message.
-        The backend will then respond with a CompletedResponse message
-        with a tag of <literal>COPY</literal>.
-       </Para>
-      </ListItem>
-     </VarListEntry>
-
-     <VarListEntry>
-      <Term>CopyOutResponse</Term>
-      <ListItem>
-       <Para>
-        The backend is ready to copy data from a table to the
-        frontend.  It then sends a CopyDataRows message, and then a
-        CompletedResponse message with a tag of <literal>COPY</literal>.
-       </Para>
-      </ListItem>
-     </VarListEntry>
-
-     <VarListEntry>
-      <Term>CursorResponse</Term>
-      <ListItem>
-       <Para>
-        Beginning of the response to a <command>SELECT</command>,
-        <command>FETCH</command>, <command>INSERT</command>,
-        <command>UPDATE</command>, or <command>DELETE</command>
-        query.  In the <command>FETCH</command> case the name of the
-	cursor being fetched from is included in the message.  Otherwise
-	the message always mentions the <quote>blank</> cursor.
-       </Para>
-      </ListItem>
-     </VarListEntry>
-
-     <VarListEntry>
-      <Term>RowDescription</Term>
-      <ListItem>
-       <Para>
-        Indicates that rows are about to be returned in response to
-	a <command>SELECT</command> or <command>FETCH</command> query.
-	The message contents describe the layout of the rows.  This
-	will be followed by an AsciiRow or BinaryRow message (depending on
-	whether a binary cursor was specified) for each row being returned
-        to the frontend.
-       </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 may
-        contain multiple SQL commands.  (CompletedResponse 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</> or <command>FETCH</> query
-    normally consists of CursorResponse, RowDescription, zero or more
-    AsciiRow or BinaryRow messages, and finally CompletedResponse.
-    <command>INSERT</command>, <command>UPDATE</command>, and
-    <command>DELETE</command> queries produce CursorResponse followed by
-    CompletedResponse.
-    <command>COPY</> to or from the frontend invokes special protocol
-    as mentioned above.
-    All other query types normally produce only
-    a CompletedResponse 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.
-    (The need to specially distinguish this case is historical.)
-   </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
-    may occur partway through the sequence of messages generated by an
-    individual query.
-   </Para>
-
-   <para>
-    A frontend must be prepared to accept ErrorResponse and
-    NoticeResponse messages whenever it is expecting any other type of
-    message.
-   </para>
-
-   <Para>
-    Actually, it is possible for NoticeResponse to arrive even when
-    the frontend is not expecting any kind of message, that is, the
-    backend is nominally idle.  (In particular, the backend can be
-    commanded to terminate by its parent process.  In that case it will
-    send a NoticeResponse before closing the connection.)  It is
-    recommended that the frontend check for such asynchronous notices
-    just before issuing any new command.
-   </para>
-
-   <Para>
-    Also, if the frontend issues any <command>LISTEN</command>
-    commands then it must be prepared to accept NotificationResponse
-    messages at any time; see below.
-   </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>
-   <Title>Function Call</Title>
-
-   <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 may 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>FunctionResultResponse</Term>
-      <ListItem>
-       <Para>
-        The function call was executed and returned a result.
-       </Para>
-      </ListItem>
-     </VarListEntry>
-
-     <VarListEntry>
-      <Term>FunctionVoidResponse</Term>
-      <ListItem>
-       <Para>
-        The function call was executed and returned no result.
-       </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>
-
-   <para>
-    A frontend must be prepared to accept ErrorResponse and
-    NoticeResponse messages whenever it is expecting any other type of
-    message.  Also, if it issues any <command>LISTEN</command>
-    commands then it must be prepared to accept NotificationResponse
-    messages at any time; see below.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Notification Responses</title>
-
-   <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
-    notification name.
-   </para>
-
-   <para>
-    Notification responses are permitted at any point in the protocol
-    (after start-up), except within another backend message.  Thus,
-    the frontend must be prepared to recognize a NotificationResponse
-    message whenever it is expecting any message.  Indeed, it should
-    be able to handle NotificationResponse messages even when it is
-    not engaged in a query.
-
-    <VariableList>
-     <VarListEntry>
-      <Term>NotificationResponse</Term>
-      <ListItem>
-       <Para>
-        A <command>NOTIFY</command> command has been executed for a
-        name for which a previous <command>LISTEN</command> command
-        was executed.  Notifications may be sent at any time.
-       </Para>
-      </ListItem>
-     </VarListEntry>
-    </VariableList>
-   </Para>
-
-   <para>
-    It may be worth pointing out that the names used in listen and
-    notify commands need not have anything to do with names of
-    relations (tables) in the SQL database.  Notification names are
-    simply arbitrarily chosen condition names.
-   </para>
-  </sect2>
-
-  <Sect2>
-   <Title>Cancelling Requests in Progress</Title>
-
-   <Para>
-    During the processing of a query, the frontend may 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
-    StartupPacket 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 may or may not have any effect --- 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 may have some benefits of flexibility in 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>
-
-   <Para>
-    The normal, graceful termination procedure is that the frontend
-    sends a Terminate message and immediately closes the connection.
-    On receipt of the message, the backend immediately closes the
-    connection and terminates.
-   </para>
-
-   <Para>
-    An ungraceful termination may occur due to software failure (i.e.,
-    core dump) at either end.  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.
-   </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 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 may be committed
-    before the disconnection is recognized.
-   </para>
-  </sect2>
-
-  <Sect2>
-   <Title>SSL Session Encryption</Title>
-
-   <Para>
-    Recent releases of <productname>PostgreSQL</> allow frontend/backend
-    communication to be encrypted using SSL.  This provides communication
-    security in environments where attackers might be able to capture the
-    session traffic.
-   </para>
-
-   <para>
-    To initiate an SSL-encrypted connection, the frontend initially sends
-    an SSLRequest message rather than a StartupPacket.  The server then
-    responds with a single byte containing <literal>Y</> or <literal>N</>,
-    indicating that it is willing or unwilling to perform SSL, respectively.
-    The frontend may close the connection at this point if it is dissatisfied
-    with the response.  To continue after <literal>Y</>, perform an SSL
-    startup handshake (not described here, part of the SSL specification)
-    with the server.  If this is successful, continue with
-    sending the usual StartupPacket.  In this case the StartupPacket and
-    all subsequent data will be SSL-encrypted.  To continue after
-    <literal>N</>, send the usual StartupPacket 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 SSL support to <productname>PostgreSQL</>.
-    In this case the connection must be closed, but the frontend may choose
-    to open a fresh connection and proceed without requesting SSL.
-   </para>
-
-   <para>
-    An initial SSLRequest may 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 SSL encryption, the administrator may configure the server to
-    reject unencrypted sessions as a byproduct of authentication checking.
-   </para>
-  </sect2>
- </sect1>
-
-<Sect1 id="protocol-message-types">
-<Title>Message Data Types</Title>
-
-<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.
-                If <Replaceable>i</Replaceable> is specified it
-                is the literal value.  Eg. Int16, Int32(42).
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        LimString<Replaceable>n</Replaceable>(<Replaceable>s</Replaceable>)
-</Term>
-<ListItem>
-<Para>
-                A character array of exactly <Replaceable>n</Replaceable> bytes interpreted as a
-                null-terminated string.  The zero-byte is omitted if there is
-                insufficient room.  If <Replaceable>s</Replaceable> is specified it is the literal value.
-                Eg. LimString32, LimString64("user").
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        String(<Replaceable>s</Replaceable>)
-</Term>
-<ListItem>
-<Para>
-                A conventional C null-terminated string with no length
-                limitation.
-                If <Replaceable>s</Replaceable> is specified it is the literal value.
-                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 <Replaceable>c</Replaceable> is specified it is the literal
-                value.  Eg. Byte, Byte1('\n').
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-</Para>
-</sect1>
-
-<Sect1 id="protocol-message-formats">
-<Title>Message Formats</Title>
-
-<Para>
-This section describes the detailed format of each message.  Each can be sent
-by either a frontend (F), a backend (B), or both (F & B).
-</para>
-
-<VariableList>
-<VarListEntry>
-<Term>
-AsciiRow (B)
-</Term>
-<ListItem>
-<Para>
-<VariableList>
-<VarListEntry>
-<Term>
-        Byte1('D')
-</Term>
-<ListItem>
-<Para>
-                Identifies the message as an <Acronym>ASCII</Acronym> data row.
-                (A prior RowDescription message defines the number of
-                fields in the row and their data types.)
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Byte<Replaceable>n</Replaceable>
-</Term>
-<ListItem>
-<Para>
-                A bit map with one bit for each field in the row.  The 1st
-                field corresponds to bit 7 (MSB) of the 1st byte, the 2nd
-                field corresponds to bit 6 of the 1st byte, the 8th field
-                corresponds to bit 0 (LSB) of the 1st byte, the 9th field
-                corresponds to bit 7 of the 2nd byte, and so on.  Each bit
-                is set if the value of the corresponding field is not NULL.
-                If the number of fields is not a multiple of 8, the remainder
-                of the last byte in the bit map is wasted.
-</Para>
-<Para>
-        Then, for each field with a non-NULL value, there is the following:
-<VariableList>
-<VarListEntry>
-<Term>
-                Int32
-</Term>
-<ListItem>
-<Para>
-                        Specifies the size of the value of the field, including
-                        this size.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-                Byte<Replaceable>n</Replaceable>
-</Term>
-<ListItem>
-<Para>
-                        Specifies the value of the field itself in <Acronym>ASCII</Acronym>
-                        characters.  <Replaceable>n</Replaceable> is the above
-                        size minus 4.
-                        There is no trailing zero-byte in the field data; the front
-                        end must add one if it wants one.
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-</Para>
-</ListItem>
-</VarListEntry>
-<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(0)
-</Term>
-<ListItem>
-<Para>
-                Specifies that the authentication was successful.
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-AuthenticationKerberosV4 (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(1)
-</Term>
-<ListItem>
-<Para>
-                Specifies that Kerberos V4 authentication is required.
-</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(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(3)
-</Term>
-<ListItem>
-<Para>
-                Specifies that a cleartext password is required.
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry>
-<Term>
-AuthenticationCryptPassword (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(4)
-</Term>
-<ListItem>
-<Para>
-                Specifies that a crypt()-encrypted password is required.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Byte2
-</Term>
-<ListItem>
-<Para>
-                The salt to use when encrypting the password.
-</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(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(6)
-</Term>
-<ListItem>
-<Para>
-                Specifies that an SCM credentials message is required.
-</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
-</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>
-BinaryRow (B)
-</Term>
-<ListItem>
-<Para>
-
-<VariableList>
-<VarListEntry>
-<Term>
-        Byte1('B')
-</Term>
-<ListItem>
-<Para>
-                Identifies the message as a binary data row.
-                (A prior RowDescription message defines the number of
-                fields in the row and their data types.)
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Byte<Replaceable>n</Replaceable>
-</Term>
-<ListItem>
-<Para>
-                A bit map with one bit for each field in the row.  The 1st
-                field corresponds to bit 7 (MSB) of the 1st byte, the 2nd
-                field corresponds to bit 6 of the 1st byte, the 8th field
-                corresponds to bit 0 (LSB) of the 1st byte, the 9th field
-                corresponds to bit 7 of the 2nd byte, and so on.  Each bit
-                is set if the value of the corresponding field is not NULL.
-                If the number of fields is not a multiple of 8, the remainder
-                of the last byte in the bit map is wasted.
-</Para>
-<Para>
-        Then, for each field with a non-NULL value, there is the following:
-<VariableList>
-<VarListEntry>
-<Term>
-                Int32
-</Term>
-<ListItem>
-<Para>
-                        Specifies the size of the value of the field, excluding
-                        this size.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-                Byte<Replaceable>n</Replaceable>
-</Term>
-<ListItem>
-<Para>
-                        Specifies the value of the field itself in binary
-                        format.  <Replaceable>n</Replaceable> is the above size.
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-CancelRequest (F)
-</Term>
-<ListItem>
-<Para>
-
-<VariableList>
-<VarListEntry>
-<Term>
-        Int32(16)
-</Term>
-<ListItem>
-<Para>
-                The size of the packet in bytes.
-</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>
-CompletedResponse (B)
-</Term>
-<ListItem>
-<Para>
-
-<VariableList>
-<VarListEntry>
-<Term>
-        Byte1('C')
-</Term>
-<ListItem>
-<Para>
-                Identifies the message as a completed response.
-</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, and <replaceable>oid</replaceable> is the object ID
-        of the inserted row if <Replaceable>rows</Replaceable> is 1,
-        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>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-CopyDataRows (B & F)
-</Term>
-<ListItem>
-<Para>
-        This is a stream of rows where each row is terminated by a Byte1('\n').
-        This is then followed by the sequence Byte1('\\'), Byte1('.'),
-        Byte1('\n').
-</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 a CopyDataRows message.
-</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 a CopyDataRows message.
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-CursorResponse (B)
-</Term>
-<ListItem>
-<Para>
-
-<VariableList>
-<VarListEntry>
-<Term>
-        Byte1('P')
-</Term>
-<ListItem>
-<Para>
-                Identifies the message as a cursor response.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        String
-</Term>
-<ListItem>
-<Para>
-                The name of the cursor.  This will be <quote>blank</> if the cursor is
-                implicit.
-</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.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        String("")
-</Term>
-<ListItem>
-<Para>
-                Unused.
-</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>
-        String
-</Term>
-<ListItem>
-<Para>
-                The error message itself.
-</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>
-        String("")
-</Term>
-<ListItem>
-<Para>
-                Unused.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Int32
-</Term>
-<ListItem>
-<Para>
-                Specifies the object ID of the function to call.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Int32
-</Term>
-<ListItem>
-<Para>
-                Specifies the number of arguments being supplied to the
-                function.
-</Para>
-<Para>
-        Then, for each argument, there is the following:
-<VariableList>
-<VarListEntry>
-<Term>
-                Int32
-</Term>
-<ListItem>
-<Para>
-                        Specifies the size of the value of the argument,
-                        excluding this size.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-                Byte<Replaceable>n</Replaceable>
-</Term>
-<ListItem>
-<Para>
-                        Specifies the value of the field itself in binary
-                        format.  <Replaceable>n</Replaceable> is the above size.
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-</Para>
-
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-FunctionResultResponse (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>
-        Byte1('G')
-</Term>
-<ListItem>
-<Para>
-                Specifies that a nonempty result was returned.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Int32
-</Term>
-<ListItem>
-<Para>
-                Specifies the size of the value of the result, excluding this
-                size.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Byte<Replaceable>n</Replaceable>
-</Term>
-<ListItem>
-<Para>
-                Specifies the value of the result itself in binary format.
-                <Replaceable>n</Replaceable> is the above size.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Byte1('0')
-</Term>
-<ListItem>
-<Para>
-                Unused.  (Strictly speaking, FunctionResultResponse and
-                FunctionVoidResponse are the same thing but with some optional
-                parts to the message.)
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-FunctionVoidResponse (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>
-        Byte1('0')
-</Term>
-<ListItem>
-<Para>
-                Specifies that an empty result was returned.
-</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>
-        String
-</Term>
-<ListItem>
-<Para>
-                The notice message itself.
-</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>
-                The process ID of the notifying backend process.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        String
-</Term>
-<ListItem>
-<Para>
-                The name of the condition that the notify has been raised on.
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry>
-<Term>
-PasswordPacket (F)
-</Term>
-<ListItem>
-<Para>
-
-<VariableList>
-<VarListEntry>
-<Term>
-        Int32
-</Term>
-<ListItem>
-<Para>
-                The size of the packet in bytes.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        String
-</Term>
-<ListItem>
-<Para>
-                The password (encrypted, if requested).
-</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 query.
-</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>
-</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>
-        Int16
-</Term>
-<ListItem>
-<Para>
-                Specifies the number of fields in a row (may be zero).
-</Para>
-<Para>
-        Then, for each field, there is the following:
-<VariableList>
-<VarListEntry>
-<Term>
-                String
-</Term>
-<ListItem>
-<Para>
-                        Specifies the field name.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-                Int32
-</Term>
-<ListItem>
-<Para>
-                        Specifies the object ID of the field type.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-                Int16
-</Term>
-<ListItem>
-<Para>
-                        Specifies the type size.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-                Int32
-</Term>
-<ListItem>
-<Para>
-                        Specifies the type modifier.
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-</Para>
-</ListItem>
-</VarListEntry>
-</VariableList>
-
-
-</Para>
-</ListItem>
-</VarListEntry>
-
-<VarListEntry>
-<Term>
-SSLRequest (F)
-</Term>
-<ListItem>
-<Para>
-
-<VariableList>
-<VarListEntry>
-<Term>
-        Int32(8)
-</Term>
-<ListItem>
-<Para>
-                The size of the packet in bytes.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Int32(80877103)
-</Term>
-<ListItem>
-<Para>
-                The SSL 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>
-StartupPacket (F)
-</Term>
-<ListItem>
-<Para>
-
-<VariableList>
-<VarListEntry>
-<Term>
-        Int32(296)
-</Term>
-<ListItem>
-<Para>
-                The size of the packet in bytes.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        Int32
-</Term>
-<ListItem>
-<Para>
-                The protocol version number.  The most significant 16 bits are
-                the major version number.  The least 16 significant bits are
-                the minor version number.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        LimString64
-</Term>
-<ListItem>
-<Para>
-                The database name, defaults to the user name if empty.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        LimString32
-</Term>
-<ListItem>
-<Para>
-                The user name.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        LimString64
-</Term>
-<ListItem>
-<Para>
-                Any additional command line arguments to be passed to the
-                backend child process by the server.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        LimString64
-</Term>
-<ListItem>
-<Para>
-                Unused.
-</Para>
-</ListItem>
-</VarListEntry>
-<VarListEntry>
-<Term>
-        LimString64
-</Term>
-<ListItem>
-<Para>
-                The optional tty the backend should use for debugging messages.
-		(Currently, this field is unsupported and ignored.)
-</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>
-</VariableList>
-
-
-</Para>
-</ListItem>
-</VarListEntry>
-
-</VariableList>
-
-</sect1>
-</Chapter>
diff --git a/doc/src/sgml/pygresql.sgml b/doc/src/sgml/pygresql.sgml
deleted file mode 100644
index 540379029dc..00000000000
--- a/doc/src/sgml/pygresql.sgml
+++ /dev/null
@@ -1,4484 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/Attic/pygresql.sgml,v 1.6 2002/03/27 19:19:22 petere Exp $ -->
-
-<chapter id="pygresql">
- <title><application>PyGreSQL</application> - <application>Python</application> Interface</title>
-
- <note>
-  <title>Author</title>
-  <para>
-   Written by D'Arcy J.M. Cain (<email>darcy@druid.net</email>).
-   Based heavily on code written by Pascal Andre
-   <email>andre@chimay.via.ecp.fr</email>.  Copyright &copy; 1995,
-   Pascal Andre.  Further modifications Copyright &copy; 1997-2000 by
-   D'Arcy J.M. Cain.
-  </para>
- </note>
-
-
-<![IGNORE[
- <sect1 id="pygresql-install">
-  <title>Installation</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     If you are on <acronym>NetBSD</acronym>, look in the packages
-     directory under databases. If it isn't there yet, it should be
-     there shortly.  You can also pick up the package files from
-     <ulink url="ftp://ftp.druid.net/pub/distrib/pygresql.pkg.tgz"
-     >ftp://ftp.druid.net/pub/distrib/pygresql.pkg.tgz</ulink>.  There
-     is also a package in the <acronym>FreeBSD</acronym> ports
-     collection but as I write this it is at version 2.1.  I will try
-     to get that updated as well.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     For Linux installation look at <filename>README.linux</filename>.
-     If you're on an <acronym>x86</acronym> system that uses
-     <acronym>RPMs</acronym>, then you can pick up an
-     <acronym>RPM</acronym> at <ulink
-     url="ftp://ftp.druid.net/pub/distrib/pygresql.i386.rpm"
-     >ftp://ftp.druid.net/pub/distrib/pygresql.i386.rpm</ulink>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Note that if you are using the <acronym>DB-API</acronym> module
-     you must also install <acronym>mxDateTime</acronym> from <ulink
-     url="http://starship.python.net/~lemburg/mxDateTime.html"
-     >http://starship.python.net/~lemburg/mxDateTime.html</ulink>.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     Also, check out <filename>setup.py</filename> for an alternate
-     method of installing the package using Python's Distutils.
-    </para>
-   </listitem>
-
-  </itemizedlist>
-    
-  <para>
-   You have two options. You can compile
-   <productname>PyGreSQL</productname> as a stand-alone module or you
-   can build it into the <productname>Python</productname>
-   interpreter.
-  </para>
-
-  <sect2>
-   <title>General</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      You must first have installed <productname>Python</productname>
-      and <productname>PostgreSQL</productname> on your system.  The
-      header files and developer's libraries for both
-      <productname>Python</productname> and
-      <productname>PostgreSQL</productname> must be installed on your
-      system before you can build <productname>PyGreSQL</productname>.
-      If you built both <productname>Python</productname> and
-      <productname>PostgreSQL</productname> from source, you should be
-      fine.  If your system uses some package mechanism (such as
-      <acronym>RPM</acronym> or <acronym>NetBSD</acronym> packages),
-      then you probably need to install packages such as
-      <acronym>Python-devel</acronym> in addition to the
-      <productname>Python</productname> package.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <productname>PyGreSQL</productname> is implemented as three
-      parts, a C module labeled <acronym>_pg</acronym> and two
-      <productname>Python</productname> wrappers called
-      <filename>pg.py</filename> and <filename>pgdb.py</filename>.
-      This changed between 2.1 and 2.2 and again in 3.0.  These
-      changes should not affect any existing programs but the
-      installation is slightly different.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Download and unpack the <productname>PyGreSQL</productname>
-      tarball if you haven't already done so.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </sect2>
-
-  <sect2>
-   <title>Stand-alone</title>
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      In the directory containing <filename>pgmodule.c</filename>, run
-      the following command
-
-<programlisting>
-cc -fpic -shared -o _pg.so -I[pyInc] -I[pgInc] -L[pgLib] -lpq pgmodule.c
-</programlisting>
-
-      where:
-      <itemizedlist>
-       <listitem>
-        <para>
-         [pyInc] = path of the <productname>Python</productname>
-         include (usually <filename>Python.h</filename>)
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         [pgInc] = path of the <productname>PostgreSQL</productname>
-         include (usually <filename>postgres.h</filename>)
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         [pgLib] = path of the <productname>PostgreSQL</productname>
-         libraries (usually <filename>libpq.so</filename> or
-         <filename>libpq.a</filename>)
-        </para>
-       </listitem>
-      </itemizedlist>
-
-      Some options may be added to this line:
-      <itemizedlist>
-       <listitem>
-        <para>
-         <literal>-DNO_DEF_VAR</literal> - no default variables
-         support
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         <literal>-DNO_DIRECT</literal>   - no direct access methods
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         <literal>-DNO_LARGE</literal>    - no large object support
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         <literal>-DNO_SNPRINTF</literal> - if running a system with
-         no snprintf call
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         <literal>-DNO_PQSOCKET</literal> - if running an older
-         <productname>PostgreSQL</productname>
-        </para>
-       </listitem>
-      </itemizedlist>
-
-      On some systems you may need to include
-      <literal>-lcrypt</literal> in the list of libraries to make it
-      compile.
-
-      Define <literal>DNO_PQSOCKET</literal> if you are using a
-      version of <productname>PostgreSQL</productname> before 6.4 that
-      does not have the <function>PQsocket</function> function.  The
-      other options will be described in the next sections.
-     </para>
-    </listitem>
-   <listitem>
-
-   <para>
-    Test the new module.  Something like the following should work.
-<screen>
-<prompt>$</prompt> <userinput>python</userinput>
-
-<prompt>&gt;&gt;&gt;</prompt> <userinput>import _pg</userinput>
-<prompt>&gt;&gt;&gt;</prompt> <userinput>db = _pg.connect('thilo', 'localhost')</userinput>
-<prompt>&gt;&gt;&gt;</prompt> <userinput>db.query("INSERT INTO test VALUES ('ping', 'pong');")</userinput>
-18304
-<prompt>&gt;&gt;&gt;</prompt> <userinput>db.query("SELECT * FROM test;")</userinput>
- eins | zwei
-------+------
- ping | pong
-(1 row)
-</screen>
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            Finally, move the <filename>_pg.so</filename>,
-            <filename>pg.py</filename>, and <filename>pgdb.py</filename>
-            to a directory in your <literal>PYTHONPATH</literal>.
-            A good place would be
-            <filename>/usr/lib/python1.5/site-python</filename>
-            if your <productname>Python</productname> modules are in
-            <filename>/usr/lib/python1.5</filename>.
-          </para>
-        </listitem>
-      </itemizedlist>
-    </sect2>
-
-
-    <sect2>
-      <title>Built-in to python interpreter</title>
-
-      <itemizedlist>
-        <listitem>
-          <para>
-            Find the directory where your <filename>Setup</filename>
-            file lives (usually <filename>??/Modules</filename>) in 
-            the <productname>Python</productname> source hierarchy and
-            copy or symlink the <filename>pgmodule.c</filename> file there.
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            Add the following line to your Setup file
-            <ProgramListing>
-_pg  pgmodule.c -I[pgInc] -L[pgLib] -lpq # -lcrypt # needed on some systems
-            </ProgramListing>
-            where:
-            <itemizedlist>
-              <listitem>
-                <para>
-                  [pgInc] = path of the <productname>PostgreSQL</productname>
-                  include (usually <filename>postgres.h</filename>)
-                </para>
-              </listitem>
-              <listitem>
-                <para>
-                  [pgLib] = path of the <productname>PostgreSQL</productname>
-                  libraries (usually <filename>libpq.so</filename>
-                  or <filename>libpq.a</filename>)
-                </para>
-              </listitem>
-            </itemizedlist>
-            Some options may be added to this line:
-            <itemizedlist>
-              <listitem>
-                <para>
-                  <literal>-DNO_DEF_VAR</literal>  - no default variables
-                  support
-                </para>
-              </listitem>
-              <listitem>
-                <para>
-                  <literal>-DNO_DIRECT</literal>   - no direct access methods
-                </para>
-              </listitem>
-              <listitem>
-                <para>
-                  <literal>-DNO_LARGE</literal>    - no large object support
-                </para>
-              </listitem>
-              <listitem>
-                <para>
-                  <literal>-DNO_SNPRINTF</literal> - if running a system with
-                  no snprintf call
-                </para>
-              </listitem>
-              <listitem>
-                <para>
-                  <literal>-DNO_PQSOCKET</literal> - if running an older
-                  <productname>PostgreSQL</productname>
-                </para>
-              </listitem>
-            </itemizedlist>
-
-            Define <literal>DNO_PQSOCKET</literal> if you are using a version of
-            <productname>PostgreSQL</productname> before 6.4
-            that does not have the <function>PQsocket</function> function.
-            The other options will be described in the next sections.
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            If you want a shared module, make sure that the 
-            <literal>*shared*</literal> keyword is uncommented and
-            add the above line below it. You used to need to install
-            your shared modules with <literal>make sharedinstall</> but this no
-            longer seems to be true.
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            Copy <filename>pg.py</filename> to the lib directory where
-            the rest of your modules are. For example, that's
-            <filename>/usr/local/lib/Python</filename> on my system.
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            Rebuild <productname>Python</productname> from the root
-            directory of the <productname>Python</productname> source
-            hierarchy by running
-            <ProgramListing>
-make -f Makefile.pre.in boot
-make && make install
-            </ProgramListing>
-          </para>
-        </listitem>
-        <listitem>
-          <para>
-            For more details read the documentation at the top of
-            <filename>Makefile.pre.in</filename>
-          </para>
-        </listitem>
-      </itemizedlist>
-    </sect2>
-
-  </sect1>
-
-]]>
-
- <sect1 id="pygresql-pg">
-  <title>The <literal>pg</literal> Module</title>
-
-  <para>
-   You may either choose to use the old mature interface provided by
-   the <literal>pg</literal> module or otherwise the newer
-   <literal>pgdb</literal> interface compliant with the <ulink
-   url="http://www.python.org/topics/database/DatabaseAPI-2.0.html"
-   ><acronym>DB-API 2.0</acronym></ulink> specification developed by
-   the <productname>Python</productname> <acronym>DB-SIG</acronym>.
-  </para>
-
-  <para>
-   Here we describe only the older <literal>pg</literal>
-   <acronym>API</acronym>. As long as
-   <productname>PyGreSQL</productname> does not contain a description
-   of the <acronym>DB-API</acronym> you should read about the
-   <acronym>API</acronym> at <ulink
-   url="http://www.python.org/topics/database/DatabaseAPI-2.0.html"
-   >http://www.python.org/topics/database/DatabaseAPI-2.0.html</ulink>.
-  </para>
-
-  <para>
-   A tutorial-like introduction to the <acronym>DB-API</acronym> can
-   be found at <ulink
-   url="http://www2.linuxjournal.com/lj-issues/issue49/2605.html"
-   >http://www2.linuxjournal.com/lj-issues/issue49/2605.html</ulink>
-  </para>
-
-  <para>
-   The <literal>pg</literal> module defines three objects:
-   <itemizedlist>
-    <listitem>
-     <para>
-      <classname>pgobject</classname>, which handles the connection and all the
-      requests to the database,
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <classname>pglargeobject</classname>, which handles all the accesses
-      to <productname>PostgreSQL</productname> large objects, and
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <literal>pgqueryobject</literal> that handles query results.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   If you want to see a simple example of the use of some of these
-   functions, see <ulink url="http://www.druid.net/rides"
-   >http://www.druid.net/rides</ulink> where I have a link at the
-   bottom to the actual <productname>Python</productname> code for the
-   page.
-  </para>
-
-  <sect2>
-   <title>Constants</title>
-
-   <para>
-    Some constants are defined in the <literal>pg</literal> module
-    dictionary.  They are intended to be used as a parameters for
-    methods calls.  You should refer to the <literal>libpq</literal>
-    description (<xref linkend="libpq">) for more information about
-    them. These constants are:
-
-    <variablelist>
-     <varlistentry>
-      <term><varname>INV_READ</varname></term>
-      <term><varname>INV_WRITE</varname></term>
-      <listitem>
-       <para>
-        large objects access modes, used by
-        <function>(pgobject.)locreate</function> and
-        <function>(pglarge.)open</function>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SEEK_SET</varname></term>
-      <term><varname>SEEK_CUR</varname></term>
-      <term><varname>SEEK_END</varname></term>
-      <listitem>
-       <para>
-        positional flags, used by <function>(pglarge.)seek</function>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>version</varname></term>
-      <term><varname>__version__</varname></term>
-      <listitem>
-       <para>
-        constants that give the current version
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="pygresql-pg-functions">
-  <title><literal>pg</literal> Module Functions</title>
-
-  <para>
-   <literal>pg</literal> module defines only a few methods that allow
-   to connect to a database and to define <quote>default
-   variables</quote> that override the environment variables used by
-   <productname>PostgreSQL</productname>.
-  </para>
-
-  <para>
-   These <quote>default variables</quote> were designed to allow you
-   to handle general connection parameters without heavy code in your
-   programs. You can prompt the user for a value, put it in the
-   default variable, and forget it, without having to modify your
-   environment. The support for default variables can be disabled by
-   setting the <option>-DNO_DEF_VAR</option> option in the Python
-   Setup file. Methods relative to this are specified by te tag [DV].
-  </para>
-
-  <para>
-   All variables are set to <symbol>None</symbol> at module
-   initialization, specifying that standard environment variables
-   should be used.
-  </para>
-
-  <refentry id="pygresql-connect">
-   <refmeta>
-    <refentrytitle>connect</refentrytitle>
-    <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-   </refmeta>
-
-   <refnamediv>
-    <refname>connect</refname>
-    <refpurpose>opens a connection to the database server</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-connect(<optional><replaceable>dbname</replaceable></optional>, <optional><replaceable>host</replaceable></optional>, <optional><replaceable>port</replaceable></optional>, <optional><replaceable>opt</replaceable></optional>, <optional><replaceable>tty</replaceable></optional>, <optional><replaceable>user</replaceable></optional>, <optional><replaceable>passwd</replaceable></optional>)
-</synopsis>
-
-    <refsect2 id="pygresql-connect-parameters">
-     <title>Parameters</title>
-          
-     <variablelist>
-      <varlistentry>
-       <term><replaceable>dbname</replaceable></term>
-
-       <listitem>
-        <para>Name of connected database (string/None).</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable>host</replaceable></term>
-
-       <listitem>
-        <para>Name of the server host (string/None).</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable>port</replaceable></term>
-
-       <listitem>
-        <para>Port used by the database server (integer/-1).</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable>opt</replaceable></term>
-
-       <listitem>
-        <para>
-         Options for the server (string/None).
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable>tty</replaceable></term>
-
-       <listitem>
-        <para>
-         File or tty for optional debug output from backend
-         (string/None).
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable>user</replaceable></term>
-
-       <listitem>
-        <para>
-         <productname>PostgreSQL</productname> user (string/None).
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><replaceable>passwd</replaceable></term>
-
-       <listitem>
-        <para>Password for user (string/None).</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </refsect2>
-        
-    <refsect2 id="pygresql-connect-return">
-     <title>Return Type</title>
-
-     <variablelist>
-      <varlistentry>
-       <term><replaceable>pgobject</replaceable></term>
-
-       <listitem>
-        <para>
-         If successful, an object handling a database connection is returned.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </refsect2>
-        
-    <refsect2 id="pygresql-connect-exceptions">
-     <title>Exceptions</title>
-
-     <variablelist>
-      <varlistentry>
-       <term><errorname>TypeError</errorname></term>
-
-       <listitem>
-        <para>
-         Bad argument type, or too many arguments.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><errorname>SyntaxError</errorname></term>
-
-       <listitem>
-        <para>
-         Duplicate argument definition.
-        </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><errorname>pg.error</errorname></term>
-
-       <listitem>
-        <para>
-         Some error occurred during pg connection definition.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-
-     <para>
-      (+ all exceptions relative to object allocation)
-     </para>
-    </refsect2>
-   </refsynopsisdiv>
-      
-   <refsect1 id="pygresql-connect-description">
-    <title>Description</title>
-
-    <para>
-     This method opens a connection to a specified database on a given
-     <productname>PostgreSQL</productname> server. You can use
-     keywords here, as described in the
-     <productname>Python</productname> tutorial.  The names of the
-     keywords are the name of the parameters given in the syntax
-     line. For a precise description of the parameters, please refer
-     to the <productname>PostgreSQL</productname> user manual.
-    </para>
-   </refsect1>
-      
-   <refsect1 id="pygresql-connect-examples">
-    <title>Examples</title>
-
-    <para>
-<programlisting>
-import pg
-
-con1 = pg.connect('testdb', 'myhost', 5432, None, None, 'bob', None)
-con2 = pg.connect(dbname='testdb', host='localhost', user='bob')
-</programlisting>
-    </para>
-   </refsect1>
-      
-  </refentry>
-
-
-  <refentry id="pygresql-get-defhost">
-   <refmeta>
-    <refentrytitle>get_defhost</refentrytitle>
-    <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-   </refmeta>
-
-   <refnamediv>
-    <refname>get_defhost</refname>
-    <refpurpose>get default host name [DV]</refpurpose>
-   </refnamediv>
-
-   <refsynopsisdiv>
-<synopsis>
-get_defhost()
-</synopsis>
-
-    <refsect2 id="pygresql-get-defhost-parameters">
-     <title>Parameters</title>
-
-     <para>
-      none
-     </para>
-    </refsect2>
-
-    <refsect2 id="pygresql-get-defhost-return">
-     <title>Return Type</title>
-
-     <variablelist>
-      <varlistentry>
-       <term>string or None</term>
-
-       <listitem>
-        <para>
-         Default host specification
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </refsect2>
-
-    <refsect2 id="pygresql-get-defhost-exceptions">
-     <title>Exceptions</title>
-
-     <variablelist>
-      <varlistentry>
-       <term><errorname>SyntaxError</errorname></term>
-
-       <listitem>
-        <para>
-         Too many arguments.
-        </para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </refsect2>
-
-   </refsynopsisdiv>
-
-   <refsect1 id="pygresql-get-defhost-description">
-    <title>Description</title>
-
-    <para>
-     <function>get_defhost()</function> returns the current default
-     host specification, or None if the environment variables should
-     be used. Environment variables will not be looked up.
-    </para>
-   </refsect1>
-
-  </refentry>
-
-
-  <refentry id="pygresql-set-defhost">
-    <refmeta>
-      <refentrytitle>set_defhost</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>set_defhost</refname>
-      <refpurpose>set default host name [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-set_defhost(<replaceable>host</replaceable>)
-</synopsis>
-
-      <refsect2 id="pygresql-set-defhost-parameters">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>host</replaceable>
-            </term>
-            <listitem>
-              <para>New default host (string/None).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="pygresql-set-defhost-return">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string or None
-            </term>
-            <listitem>
-              <para>
-                Previous default host specification.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="pygresql-set-defhost-exceptions">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="pygresql-set-defhost-description">
-      <title>Description</title>
-      <para>
-        <function>set_defhost()</function> sets the default host value
-        for new connections. If None is supplied as parameter, environment
-        variables will be used in future connections. It returns the 
-        previous setting for default host.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="pygresql-get-defport">
-    <refmeta>
-      <refentrytitle>get_defport</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>get_defport</refname>
-      <refpurpose>get default port [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-get_defport()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFPORT-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFPORT-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              integer or None
-            </term>
-            <listitem>
-              <para>
-                Default port specification
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFPORT-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-GET-DEFPORT-1">
-      <title>Description</title>
-      <para>
-        <function>get_defport()</function> returns the current default
-        port specification, or None if the environment variables should
-        be used. Environment variables will not be looked up.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-SET-DEFPORT">
-    <refmeta>
-      <refentrytitle>set_defport</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>set_defport</refname>
-      <refpurpose>set default port [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-set_defport(<replaceable>port</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFPORT-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>port</replaceable>
-            </term>
-            <listitem>
-              <para>New default host (integer/-1).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFPORT-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              integer or None
-            </term>
-            <listitem>
-              <para>
-                Previous default port specification.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFPORT-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-SET-DEFPORT-1">
-      <title>Description</title>
-      <para>
-        <function>set_defport()</function> sets the default port value
-        for new connections. If -1 is supplied as parameter, environment
-        variables will be used in future connections. It returns the 
-        previous setting for default port.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-GET-DEFOPT">
-    <refmeta>
-      <refentrytitle>get_defopt</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>get_defopt</refname>
-      <refpurpose>get default options specification [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-get_defopt()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFOPT-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFOPT-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string or None
-            </term>
-            <listitem>
-              <para>
-                Default options specification
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFOPT-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-GET-DEFOPT-1">
-      <title>Description</title>
-      <para>
-        <function>get_defopt()</function> returns the current default
-        connection options specification, or None if the environment variables should
-        be used. Environment variables will not be looked up.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-SET-DEFOPT">
-    <refmeta>
-      <refentrytitle>set_defopt</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>set_defopt</refname>
-      <refpurpose>set options specification [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-set_defopt(<replaceable>options</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFOPT-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>options</replaceable>
-            </term>
-            <listitem>
-              <para>New default connection options (string/None).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFOPT-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string or None
-            </term>
-            <listitem>
-              <para>
-                Previous default opt specification.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFOPT-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-SET-DEFOPT-1">
-      <title>Description</title>
-      <para>
-        <function>set_defopt()</function> sets the default connection options value
-        for new connections. If None is supplied as parameter, environment
-        variables will be used in future connections. It returns the 
-        previous setting for default options.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-GET-DEFTTY">
-    <refmeta>
-      <refentrytitle>get_deftty</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>get_deftty</refname>
-      <refpurpose>get default connection debug terminal specification [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-get_deftty()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFTTY-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFTTY-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string or None
-            </term>
-            <listitem>
-              <para>
-                Default debug terminal specification
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFTTY-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-GET-DEFTTY-1">
-      <title>Description</title>
-      <para>
-        <function>get_deftty()</function> returns the current default
-        debug terminal specification, or None if the environment variables should
-        be used. Environment variables will not be looked up.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-SET-DEFTTY">
-    <refmeta>
-      <refentrytitle>set_deftty</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>set_deftty</refname>
-      <refpurpose>set default debug terminal specification [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-set_deftty(<replaceable>terminal</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFTTY-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>terminal</replaceable>
-            </term>
-            <listitem>
-              <para>New default debug terminal (string/None).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFTTY-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string or None
-            </term>
-            <listitem>
-              <para>
-                Previous default debug terminal specification.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFTTY-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-SET-DEFTTY-1">
-      <title>Description</title>
-      <para>
-        <function>set_deftty()</function> sets the default terminal value
-        for new connections. If None is supplied as parameter, environment
-        variables will be used in future connections. It returns the 
-        previous setting for default terminal.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-GET-DEFBASE">
-    <refmeta>
-      <refentrytitle>get_defbase</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>get_defbase</refname>
-      <refpurpose>get default database name specification [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-get_defbase()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFBASE-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFBASE-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string or None
-            </term>
-            <listitem>
-              <para>
-                Default debug database name specification
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GET-DEFBASE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-GET-DEFBASE-1">
-      <title>Description</title>
-      <para>
-        <function>get_defbase()</function> returns the current default
-        database name specification, or None if the environment variables should
-        be used. Environment variables will not be looked up.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-SET-DEFBASE">
-    <refmeta>
-      <refentrytitle>set_defbase</refentrytitle>
-      <refmiscinfo>PYGRESQL - Connection Management</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>set_defbase</refname>
-      <refpurpose>set default database name specification [DV]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-set_defbase(<replaceable>database</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFBASE-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>database</replaceable>
-            </term>
-            <listitem>
-              <para>New default database name (string/None).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFBASE-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string or None
-            </term>
-            <listitem>
-              <para>
-                Previous default database name specification.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-SET-DEFBASE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-SET-DEFBASE-1">
-      <title>Description</title>
-      <para>
-        <function>set_defbase()</function> sets the default database name
-        for new connections. If None is supplied as parameter, environment
-        variables will be used in future connections. It returns the 
-        previous setting for default database name.
-      </para>
-    </refsect1>
-
-  </refentry>
-
- </sect1>
-
-
- <sect1 id="pygresql-pg-pgobject">
-  <title>Connection object: <classname>pgobject</classname></title>
-
-  <para>
-   This object handles a connection to the
-   <productname>PostgreSQL</productname> database.  It embeds and
-   hides all the parameters that define this connection, leaving just
-   really significant parameters in function calls.
-  </para>
-
-  <para>
-   Some methods give direct access to the connection socket. They are
-   specified by the tag [DA].  <emphasis>Do not use them unless you
-   really know what you are doing.</emphasis> If you prefer disabling
-   them, set the <literal>-DNO_DIRECT</literal> option in the
-   <productname>Python</productname> <filename>Setup</filename> file.
-  </para>
-
-  <para>
-   Some other methods give access to large objects.  if you want to
-   forbid access to these from the module, set the
-   <literal>-DNO_LARGE</literal> option in the
-   <productname>Python</productname> <filename>Setup</filename> file.
-   These methods are specified by the tag [LO].
-  </para>
-
-  <para>
-   Every <literal>pgobject</literal> defines a set of read-only
-   attributes that describe the connection and its status. These
-   attributes are:
-
-   <variablelist>
-    <varlistentry>
-     <term>host</term>    
-     <listitem>
-      <para>
-       the host name of the server (string)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>port</term>
-     <listitem>
-      <para>
-       the port of the server (integer)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>db</term>
-     <listitem>
-      <para>
-       the selected database (string)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>options</term>
-     <listitem>
-      <para>
-       the connection options (string)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>tty</term>
-     <listitem>
-      <para>
-       the connection debug terminal (string)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>user</term>
-     <listitem>
-      <para>
-       user name on the database system (string)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>status</term>
-     <listitem>
-      <para>
-       the status of the connection (integer: 1 - OK, 0 - BAD)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>error</term>
-     <listitem>
-      <para>
-       the last warning/error message from the server (string)
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-
-  <refentry id="PYGRESQL-QUERY">
-    <refmeta>
-      <refentrytitle>query</refentrytitle>
-      <refmiscinfo>PYGRESQL - Query</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>query</refname>
-      <refpurpose>executes a SQL command</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-query(<replaceable>command</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-QUERY-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>command</replaceable>
-            </term>
-            <listitem>
-              <para>SQL command (string).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-QUERY-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              pgqueryobject or None
-            </term>
-            <listitem>
-              <para>
-                Result values.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-QUERY-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>ValueError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Empty SQL query.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Error during query processing, or invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-QUERY-1">
-      <title>Description</title>
-      <para>
-        <function>query()</function> method sends a <acronym>SQL</acronym>
-        query to the database. If the query is an insert statement, the return
-        value is the <acronym>OID</acronym> of the newly inserted row.
-        If it is otherwise a query that does not return a result
-        (i.e., is not a some kind of <literal>SELECT</literal> statement), it returns None.
-        Otherwise, it returns a <literal>pgqueryobject</literal> that can be accessed via the
-        <function>getresult()</function> or <function>dictresult()</function>
-          methods or simply printed.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-RESET">
-    <refmeta>
-      <refentrytitle>reset</refentrytitle>
-      <refmiscinfo>PYGRESQL - Reset</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>reset</refname>
-      <refpurpose>resets the connection</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-reset()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-RESET-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-RESET-2">
-        <title>Return Type</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-RESET-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many (any) arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-RESET-1">
-      <title>Description</title>
-      <para>
-        <function>reset()</function> method resets the current database.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-CLOSE">
-    <refmeta>
-      <refentrytitle>close</refentrytitle>
-      <refmiscinfo>PYGRESQL - Close</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>close</refname>
-      <refpurpose>close the database connection</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-close()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-CLOSE-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-CLOSE-2">
-        <title>Return Type</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-CLOSE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many (any) arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-CLOSE-1">
-      <title>Description</title>
-      <para>
-        <function>close()</function> method closes the database connection.
-        The connection will be closed in any case when the connection is deleted but this
-        allows you to explicitly close it.  It is mainly here to allow
-        the DB-SIG API wrapper to implement a close function.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-FILENO">
-    <refmeta>
-      <refentrytitle>fileno</refentrytitle>
-      <refmiscinfo>PYGRESQL - Fileno</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>fileno</refname>
-      <refpurpose>returns the socket used to connect to the database</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-fileno()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-FILENO-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-FILENO-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              socket id
-            </term>
-            <listitem>
-              <para>
-                The underlying socket id used to connect to the database.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-FILENO-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many (any) arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-FILENO-1">
-      <title>Description</title>
-      <para>
-        <function>fileno()</function> method returns the underlying socket id used to connect
-        to the database. This is useful for use in <function>select</function> calls, etc.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-GETNOTIFY">
-    <refmeta>
-      <refentrytitle>getnotify</refentrytitle>
-      <refmiscinfo>PYGRESQL - Getnotify</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>getnotify</refname>
-      <refpurpose>gets the last notify from the server</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-getnotify()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-GETNOTIFY-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GETNOTIFY-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              tuple, None
-            </term>
-            <listitem>
-              <para>
-                Last notify from server
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GETNOTIFY-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many (any) arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-GETNOTIFY-1">
-      <title>Description</title>
-      <para>
-        <function>getnotify()</function> method tries to get a notify from
-        the server (from the <literal>SQL</literal> statement <literal>NOTIFY</literal>).
-        If the server returns no notify, the methods returns None. 
-        Otherwise, it returns a tuple (couple) <literal>(relname, pid)</literal>,
-        where <literal>relname</literal> is the name of the notify and <literal>pid</literal>
-        the process id of the connection that triggered the notify.
-        Remember to do a listen query first otherwise getnotify will always return None.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-INSERTTABLE">
-    <refmeta>
-      <refentrytitle>inserttable</refentrytitle>
-      <refmiscinfo>PYGRESQL - Inserttable</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>inserttable</refname>
-      <refpurpose>inserts a list into a table</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-inserttable(<replaceable>table</replaceable>, <replaceable>values</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-INSERTTABLE-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>table</replaceable>
-            </term>
-            <listitem>
-              <para>The table name (string).</para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <replaceable>values</replaceable>
-            </term>
-            <listitem>
-              <para>The list of rows values to insert (list).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-INSERTTABLE-2">
-        <title>Return Type</title>
-          <para>
-            none
-          </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-INSERTTABLE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type or too many (any) arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-INSERTTABLE-1">
-      <title>Description</title>
-      <para>
-        <function>inserttable()</function> method allows to quickly
-        insert large blocks of data in a table: it inserts the whole
-        values list into the given table. The list is a list of
-        tuples/lists that define the values for each inserted row. The
-        rows values may contain string, integer, long or double (real)
-        values.  <emphasis>Be very careful:</emphasis> this method
-        does not typecheck the fields according to the table
-        definition; it just look whether or not it knows how to handle
-        such types.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PUTLINE">
-    <refmeta>
-      <refentrytitle>putline</refentrytitle>
-      <refmiscinfo>PYGRESQL - Putline</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>putline</refname>
-      <refpurpose>writes a line to the server socket [DA]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-putline(<replaceable>line</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PUTLINE-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>line</replaceable>
-            </term>
-            <listitem>
-              <para>Line to be written (string).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PUTLINE-2">
-        <title>Return Type</title>
-          <para>
-            none
-          </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PUTLINE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type or too many (any) arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PUTLINE-1">
-      <title>Description</title>
-      <para>
-        <function>putline()</function> method allows to directly write a string to the server socket.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-GETLINE">
-    <refmeta>
-      <refentrytitle>getline</refentrytitle>
-      <refmiscinfo>PYGRESQL - Getline</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>getline</refname>
-      <refpurpose>gets a line from server socket [DA]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-getline()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-GETLINE-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GETLINE-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string
-            </term>
-            <listitem>
-              <para>
-                The line read.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GETLINE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type or too many (any) arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-GETLINE-1">
-      <title>Description</title>
-      <para>
-        <function>getline()</function> method allows to directly read a string from the server socket.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-ENDCOPY">
-    <refmeta>
-      <refentrytitle>endcopy</refentrytitle>
-      <refmiscinfo>PYGRESQL - Endcopy</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>endcopy</refname>
-      <refpurpose>synchronizes client and server [DA]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-endcopy()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-ENDCOPY-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-ENDCOPY-2">
-        <title>Return Type</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-ENDCOPY-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type or too many (any) arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-ENDCOPY-1">
-      <title>Description</title>
-      <para>
-        The use of direct access methods may desynchronize client and server. This
-        method ensure that client and server will be synchronized.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-LOCREATE">
-    <refmeta>
-      <refentrytitle>locreate</refentrytitle>
-      <refmiscinfo>PYGRESQL - Locreate</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>locreate</refname>
-      <refpurpose>creates of large object in the database [LO]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-locreate(<replaceable>mode</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-LOCREATE-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>mode</replaceable>
-            </term>
-            <listitem>
-              <para>Large object create mode.</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-LOCREATE-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              pglarge
-            </term>
-            <listitem>
-              <para>
-                Object handling the <productname>PostgreSQL</productname> large object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-LOCREATE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid connection, or creation error.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-LOCREATE-1">
-      <title>Description</title>
-      <para>
-        <function>locreate()</function> method creates a large object in the database.
-        The mode can be defined by OR-ing the constants defined in the pg module
-        (<literal>INV_READ and INV_WRITE</literal>).
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-GETLO">
-    <refmeta>
-      <refentrytitle>getlo</refentrytitle>
-      <refmiscinfo>PYGRESQL - Getlo</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>getlo</refname>
-      <refpurpose>builds a large object from given <literal>oid</literal> [LO]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-getlo(<replaceable>oid</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-GETLO-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>oid</replaceable>
-            </term>
-            <listitem>
-              <para><literal>OID</literal> of the existing large object (integer).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GETLO-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              pglarge
-            </term>
-            <listitem>
-              <para>
-                Object handling the <productname>PostgreSQL</productname> large object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-GETLO-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-GETLO-1">
-      <title>Description</title>
-      <para>
-        <function>getlo()</function> method allows to reuse a formerly
-        created large object through the <classname>pglarge</classname> interface, providing
-        the user have its <literal>oid</literal>.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-LOIMPORT">
-    <refmeta>
-      <refentrytitle>loimport</refentrytitle>
-      <refmiscinfo>PYGRESQL - Loimport</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>loimport</refname>
-      <refpurpose>imports a file to a <productname>PostgreSQL</productname> large object [LO]</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-loimport(<replaceable>filename</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-LOIMPORT-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>filename</replaceable>
-            </term>
-            <listitem>
-              <para>The name of the file to be imported (string).</para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-LOIMPORT-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              pglarge
-            </term>
-            <listitem>
-              <para>
-                Object handling the <productname>PostgreSQL</productname> large object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-LOIMPORT-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid connection, or error during file import.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-LOIMPORT-1">
-      <title>Description</title>
-      <para>
-        <function>loimport()</function> method allows to create large objects
-        in a very simple way. You just give the name of a file containing the
-        data to be use.
-      </para>
-    </refsect1>
-
-    </refentry>
-
- </sect1>
-
-
- <sect1 id="pygresql-pg-DB">
-  <title>Database wrapper class: <classname>DB</classname></title>
-
-  <para>
-   <classname>pg</classname> module contains a class called
-   <classname>DB</classname>.  All <classname>pgobject</classname>
-   methods are included in this class also.  A number of additional
-   <classname>DB</classname> class methods are described below.  The
-   preferred way to use this module is as follows (See description of
-   the initialization method below.):
-
-<programlisting>
-import pg
-
-db = pg.DB(...)
-
-for r in db.query(
-    "SELECT foo,bar
-       FROM foo_bar_table
-      WHERE foo !~ bar"
-    ).dictresult():
-
-    print '%(foo)s %(bar)s' % r
-</programlisting>
-
-   The following describes the methods and variables of this class.
-  </para>
-
-  <para>
-   The <classname>DB</classname> class is initialized with the same
-   arguments as the <function>pg.connect</function> method.  It also
-   initializes a few internal variables.  The statement <literal>db =
-   DB()</literal> will open the local database with the name of the
-   user just like <function>pg.connect()</function> does.
-  </para>
-
-    <refentry id="PYGRESQL-DB-PKEY">
-      <refmeta>
-        <refentrytitle>pkey</refentrytitle>
-        <refmiscinfo>PYGRESQL - Pkey</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>pkey</refname>
-        <refpurpose>returns the primary key of a table</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-pkey(<replaceable>table</replaceable>)
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-PKEY-1">
-          <title>Parameters</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                <replaceable>table</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  name of table.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-PKEY-2">
-          <title>Return Type</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                string
-              </term>
-              <listitem>
-                <para>
-                  Name of field which is the primary key of the table.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-PKEY-1">
-        <title>Description</title>
-        <para>
-          <function>pkey()</function> method returns the primary key
-          of a table.  Note that this raises an exception if the table
-          does not have a primary key.
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-DB-GET-DATABASES">
-      <refmeta>
-        <refentrytitle>get_databases</refentrytitle>
-        <refmiscinfo>PYGRESQL - Get_databases</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>get_databases</refname>
-        <refpurpose>get list of databases in the system</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-get_databases()
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-GET-DATABASES-1">
-          <title>Parameters</title>
-          <para>
-            none
-          </para>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-GET-DATABASES-2">
-          <title>Return Type</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                list
-              </term>
-              <listitem>
-                <para>
-                  List of databases in the system.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-GET-DATABASES-1">
-        <title>Description</title>
-        <para>
-          Although you can do this with a simple select,
-          it is added here for convenience
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-DB-GET-TABLES">
-      <refmeta>
-        <refentrytitle>get_tables</refentrytitle>
-        <refmiscinfo>PYGRESQL - get_tables</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>get_tables</refname>
-        <refpurpose>get list of tables in connected database</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-get_tables()
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-GET-TABLES-1">
-          <title>Parameters</title>
-          <para>
-            none
-          </para>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-GET-TABLES-2">
-          <title>Return Type</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                list
-              </term>
-              <listitem>
-                <para>
-                  List of tables in connected database.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-GET-TABLES-1">
-        <title>Description</title>
-        <para>
-          Although you can do this with a simple select,
-          it is added here for convenience
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-DB-GET-ATTNAMES">
-      <refmeta>
-        <refentrytitle>get_attnames</refentrytitle>
-        <refmiscinfo>PYGRESQL - Get_Attnames</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>get_attnames</refname>
-        <refpurpose>returns the attribute names of a table</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-get_attnames(<replaceable>table</replaceable>)
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-GET-ATTNAMES-1">
-          <title>Parameters</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                <replaceable>table</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  name of table.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-GET-ATTNAMES-2">
-          <title>Return Type</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                dictionary
-              </term>
-              <listitem>
-                <para>
-		 The dictionary's keys are
-		 the attribute names, the values are the type names of
-		 the attributes.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-GET-ATTNAMES-1">
-        <title>Description</title>
-        <para>
-          Given the name of a table, digs out the set of attribute names
-	  and types.
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-DB-GET">
-      <refmeta>
-        <refentrytitle>get</refentrytitle>
-        <refmiscinfo>PYGRESQL - Get</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>get</refname>
-        <refpurpose>get a tuple from a database table</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-get(<replaceable>table</replaceable>, <replaceable>arg</replaceable>, <optional><replaceable>keyname</replaceable></optional>)
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-GET-1">
-          <title>Parameters</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                <replaceable>table</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  Name of table.
-                </para>
-              </listitem>
-            </varlistentry>
-            <varlistentry>
-              <term>
-                <replaceable>arg</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  Either a dictionary or the value to be looked up.
-                </para>
-              </listitem>
-            </varlistentry>
-            <varlistentry>
-              <term>
-                <optional><replaceable>keyname</replaceable></optional>
-              </term>
-              <listitem>
-                <para>
-                  Name of field to use as key (optional).
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-GET-2">
-          <title>Return Type</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                dictionary
-              </term>
-              <listitem>
-                <para>
-                  A dictionary mapping attribute names to row values.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-GET-1">
-        <title>Description</title>
-        <para>
-          This method is the basic mechanism to get a single row.  It assumes
-          that the key specifies a unique row.  If keyname is not specified
-          then the primary key for the table is used.  If arg is a dictionary
-          then the value for the key is taken from it and it is modified to
-          include the new values, replacing existing values where necessary.
-          The oid is also put into the dictionary but in order to allow the
-          caller to work with multiple tables, the attribute name is munged
-          to make it unique.  It consists of the string <literal>oid_</literal> followed by
-          the name of the table.
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-DB-INSERT">
-      <refmeta>
-        <refentrytitle>insert</refentrytitle>
-        <refmiscinfo>PYGRESQL - Insert</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>insert</refname>
-        <refpurpose>insert a tuple into a database table</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-insert(<replaceable>table</replaceable>, <replaceable>a</replaceable>)
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-INSERT-1">
-          <title>Parameters</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                <replaceable>table</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  Name of table.
-                </para>
-              </listitem>
-            </varlistentry>
-            <varlistentry>
-              <term>
-                <replaceable>a</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  A dictionary of values.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-INSERT-2">
-          <title>Return Type</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                integer
-              </term>
-              <listitem>
-                <para>
-                  The OID of the newly inserted row.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-INSERT-1">
-        <title>Description</title>
-        <para>
-          This method inserts values into the table specified filling in the
-          values from the dictionary.  It then reloads the dictionary with the
-          values from the database.  This causes the dictionary to be updated
-          with values that are modified by rules, triggers, etc.
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-DB-UPDATE">
-      <refmeta>
-        <refentrytitle>update</refentrytitle>
-        <refmiscinfo>PYGRESQL - Update</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>update</refname>
-        <refpurpose>update a database table</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-update(<replaceable>table</replaceable>, <replaceable>a</replaceable>)
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-UPDATE-1">
-          <title>Parameters</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                <replaceable>table</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  Name of table.
-                </para>
-              </listitem>
-            </varlistentry>
-            <varlistentry>
-              <term>
-                <replaceable>a</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  A dictionary of values.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-UPDATE-2">
-          <title>Return Type</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                integer
-              </term>
-              <listitem>
-                <para>
-                  The OID of the newly updated row.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-UPDATE-1">
-        <title>Description</title>
-        <para>
-          Similar to insert but updates an existing row.  The update is based
-          on the OID value as munged by get.  The array returned is the
-          one sent modified to reflect any changes caused by the update due
-          to triggers, rules, defaults, etc.
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-DB-CLEAR">
-      <refmeta>
-        <refentrytitle>clear</refentrytitle>
-        <refmiscinfo>PYGRESQL - Clear</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>clear</refname>
-        <refpurpose>clear a database table</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-clear(<replaceable>table</replaceable>, <optional><replaceable>a</replaceable></optional>)
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-CLEAR-1">
-          <title>Parameters</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                <replaceable>table</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  Name of table.
-                </para>
-              </listitem>
-            </varlistentry>
-            <varlistentry>
-              <term>
-                <optional><replaceable>a</replaceable></optional>
-              </term>
-              <listitem>
-                <para>
-                  A dictionary of values.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-CLEAR-2">
-          <title>Return Type</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                dictionary
-              </term>
-              <listitem>
-                <para>
-                  A dictionary with an empty row.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-CLEAR-1">
-        <title>Description</title>
-        <para>
-          This method clears all the attributes to values determined by the types.
-          Numeric types are set to 0, dates are set to <literal>'today'</literal> and everything
-          else is set to the empty string.  If the array argument is present,
-          it is used as the array and any entries matching attribute names
-          are cleared with everything else left unchanged.
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-DB-DELETE">
-      <refmeta>
-        <refentrytitle>delete</refentrytitle>
-        <refmiscinfo>PYGRESQL - Delete</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>delete</refname>
-        <refpurpose>deletes the row from a table</refpurpose>
-      </refnamediv>
-
-      <refsynopsisdiv>
-<synopsis>
-delete(<replaceable>table</replaceable>, <optional><replaceable>a</replaceable></optional>)
-</synopsis>
-
-        <refsect2 id="R2-PYGRESQL-DB-DELETE-1">
-          <title>Parameters</title>
-          <variablelist>
-            <varlistentry>
-              <term>
-                <replaceable>table</replaceable>
-              </term>
-              <listitem>
-                <para>
-                  Name of table.
-                </para>
-              </listitem>
-            </varlistentry>
-            <varlistentry>
-              <term>
-                <optional><replaceable>a</replaceable></optional>
-              </term>
-              <listitem>
-                <para>
-                  A dictionary of values.
-                </para>
-              </listitem>
-            </varlistentry>
-          </variablelist>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-DB-DELETE-2">
-          <title>Return Type</title>
-          <para>
-            none
-          </para>
-        </refsect2>
-
-      </refsynopsisdiv>
-
-      <refsect1 id="R1-PYGRESQL-DB-DELETE-1">
-        <title>Description</title>
-        <para>
-          This method deletes the row from a table.  It deletes based on the OID
-          as munged as described above.
-        </para>
-      </refsect1>
-
-    </refentry>
-
-    <!-- ********************************************************** -->
-
-  </sect1>
-
-  <!-- ********************************************************** -->
-  <!-- ********************************************************** -->
-
-  <sect1 id="pygresql-pg-pgqueryobject">
-    <title>Query result object: <literal>pgqueryobject</literal></title>
-
-    <!-- ********************************************************** -->
-
-    <refentry id="PYGRESQL-PGQUERYOBJECT-GETRESULT">
-      <refmeta>
-        <refentrytitle>getresult</refentrytitle>
-        <refmiscinfo>PYGRESQL - Getresult</refmiscinfo>
-      </refmeta>
-      <refnamediv>
-        <refname>getresult</refname>
-        <refpurpose>gets the values returned by the query</refpurpose>
-      </refnamediv>
-      
-      <refsynopsisdiv>
-<synopsis>
-getresult()
-</synopsis>
-        
-        <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-GETRESULT-1">
-          <title>Parameters</title>
-          <para>
-            none
-          </para>
-        </refsect2>
-
-        <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-GETRESULT-2">
-          <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              list
-            </term>
-            <listitem>
-              <para>
-                List of tuples.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-GETRESULT-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid previous result.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGQUERYOBJECT-GETRESULT-1">
-      <title>Description</title>
-      <para>
-        <function>getresult()</function> method returns the list of the values returned by the query.
-        More information about this result may be accessed using <function>listfields</function>,
-        <function>fieldname</function> and <function>fieldnum</function> methods.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGQUERYOBJECT-DICTRESULT">
-    <refmeta>
-      <refentrytitle>dictresult</refentrytitle>
-      <refmiscinfo>PYGRESQL - Dictresult</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>dictresult</refname>
-      <refpurpose>like getresult but returns a list of dictionaries</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-dictresult()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-DICTRESULT-1">
-        <title>Parameters</title>
-          <para>
-            none
-          </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-DICTRESULT-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              list
-            </term>
-            <listitem>
-              <para>
-                List of dictionaries.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-DICTRESULT-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid previous result.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGQUERYOBJECT-DICTRESULT-1">
-      <title>Description</title>
-      <para>
-        <function>dictresult()</function> method returns the list of the values returned by the query
-        with each tuple returned as a dictionary with the field names
-        used as the dictionary index.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGQUERYOBJECT-LISTFIELDS">
-    <refmeta>
-      <refentrytitle>listfields</refentrytitle>
-      <refmiscinfo>PYGRESQL - Listfields</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>listfields</refname>
-      <refpurpose>lists the fields names of the query result</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-listfields()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-LISTFIELDS-1">
-        <title>Parameters</title>
-          <para>
-            none
-          </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-LISTFIELDS-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              list
-            </term>
-            <listitem>
-              <para>
-                field names
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-LISTFIELDS-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid query result, or invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGQUERYOBJECT-LISTFIELDS-1">
-      <title>Description</title>
-      <para>
-        <function>listfields()</function> method returns the list of field names defined for the
-        query result. The fields are in the same order as the result values.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGQUERYOBJECT-FIELDNAME">
-    <refmeta>
-      <refentrytitle>fieldname</refentrytitle>
-      <refmiscinfo>PYGRESQL - Fieldname</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>fieldname</refname>
-      <refpurpose>field number-name conversion</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-fieldname(<replaceable>i</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-FIELDNAME-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>i</replaceable>
-            </term>
-            <listitem>
-              <para>
-                field number (integer).
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-FIELDNAME-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string
-            </term>
-            <listitem>
-              <para>
-                field name.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-FIELDNAME-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad parameter type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <replaceable>ValueError</replaceable>
-            </term>
-            <listitem>
-              <para>
-                Invalid field number.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid query result, or invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGQUERYOBJECT-FIELDNAME-1">
-      <title>Description</title>
-      <para>
-        <function>fieldname()</function> method allows to find a field name from its rank number. It can be 
-        useful for displaying a result. The fields are in the same order than the
-        result values.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGQUERYOBJECT-FIELDNUM">
-    <refmeta>
-      <refentrytitle>fieldnum</refentrytitle>
-      <refmiscinfo>PYGRESQL - Fieldnum</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>fieldnum</refname>
-      <refpurpose>field name-number conversion</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-fieldnum(<replaceable>name</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-FIELDNUM-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>name</replaceable>
-            </term>
-            <listitem>
-              <para>
-                field name (string).
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-FIELDNUM-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              integer
-            </term>
-            <listitem>
-              <para>
-                field number (integer).
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-FIELDNUM-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad parameter type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <replaceable>ValueError</replaceable>
-            </term>
-            <listitem>
-              <para>
-                Unknown field name.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid query result, or invalid connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGQUERYOBJECT-FIELDNUM-1">
-      <title>Description</title>
-      <para>
-        <function>fieldnum()</function> method returns a field number from its name.
-        It can be used to build a function that converts result list strings to their correct
-        type, using a hardcoded table definition.  The number returned is the
-        field rank in the result values list.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGQUERYOBJECT-NTUPLES">
-    <refmeta>
-      <refentrytitle>ntuples</refentrytitle>
-      <refmiscinfo>PYGRESQL - Ntuples</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>ntuples</refname>
-      <refpurpose>returns the number of tuples in query object</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-ntuples()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-NTUPLES-1">
-        <title>Parameters</title>
-          <para>
-            none
-          </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-NTUPLES-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              integer
-            </term>
-            <listitem>
-              <para>
-                The number of tuples in query object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGQUERYOBJECT-NTUPLES-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGQUERYOBJECT-NTUPLES-1">
-      <title>Description</title>
-      <para>
-        <function>ntuples()</function> method returns the number of tuples found in a query.
-      </para>
-    </refsect1>
-
-  </refentry>
-
- </sect1>
-
-
- <sect1 id="pygresql-pg-pglarge">
-  <title>Large Object: <classname>pglarge</classname></title>
-
-  <para>
-   This object handles all the request concerning a
-   <productname>PostgreSQL</productname> large object. It embeds and
-   hides all the <quote>recurrent</quote> variables (object oid and
-   connection), exactly in the same way
-   <classname>pgobject</classname>s do, thus only keeping significant
-   parameters in function calls. It keeps a reference to the <classname>pgobject</classname>
-   used for its creation, sending requests though with its
-   parameters. Any modification but dereferencing the
-   <classname>pgobject</classname> will thus affect the
-   <classname>pglarge</classname> object.  Dereferencing the initial
-   <classname>pgobject</classname> is not a problem since
-   <application>Python</application> will not deallocate it before the
-   large object dereference it.  All functions return a generic error
-   message on call error, whatever the exact error was. The
-   <structfield>error</structfield> attribute of the object allows to
-   get the exact error message.
-  </para>
-
-  <para>
-   <classname>pglarge</classname> objects define a read-only set of
-   attributes that allow to get some information about it. These
-   attributes are:
-
-   <variablelist>
-    <varlistentry>
-     <term>oid</term>
-     <listitem>
-      <para>
-       the oid associated with the object
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>pgcnx</term>
-     <listitem>
-      <para>
-       the <classname>pgobject</classname> associated with the object
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>error</term>
-     <listitem>
-      <para>
-       the last warning/error message of the connection
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   <note>
-    <title>Be careful</title>
-
-    <para>
-     In multithreaded environments, <structfield>error</structfield>
-     may be modified by another thread using the same
-     <classname>pgobject</classname>. Remember these object are
-     shared, not duplicated; you should provide some locking to be
-     able if you want to check this.  The oid attribute is very
-     interesting because it allow you reuse the oid later, creating
-     the <classname>pglarge</classname> object with a <classname>pgobject</classname>
-     <function>getlo()</function> method call.
-    </para>
-   </note>
-  </para>
-
-  <para>
-   See also <xref linkend="largeobjects"> for more information about the
-   <productname>PostgreSQL</productname> large object interface.
-  </para>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-OPEN">
-    <refmeta>
-      <refentrytitle>open</refentrytitle>
-      <refmiscinfo>PYGRESQL - Open</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>open</refname>
-      <refpurpose>opens a large object</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-open(<replaceable>mode</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-OPEN-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>mode</replaceable>
-            </term>
-            <listitem>
-              <para>
-                open mode definition (integer).
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-OPEN-2">
-        <title>Return Type</title>
-          <para>
-            none
-          </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-OPEN-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad parameter type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Already opened object, or open error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-OPEN-1">
-      <title>Description</title>
-      <para>
-        <function>open()</function> method opens a large object for reading/writing,
-        in the same way than the <acronym>UNIX</acronym> <function>open()</function>
-        function. The mode value can be obtained by OR-ing the constants defined in
-        the pg module (<literal>INV_READ, INV_WRITE</literal>).
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-CLOSE">
-    <refmeta>
-      <refentrytitle>close</refentrytitle>
-      <refmiscinfo>PYGRESQL - Close</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>close</refname>
-      <refpurpose>closes the large object</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-close()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-CLOSE-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-CLOSE-2">
-        <title>Return Type</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-CLOSE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Object is not opened, or close error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-CLOSE-1">
-      <title>Description</title>
-      <para>
-        <function>close()</function> method closes previously opened large object,
-        in the same way than the <acronym>UNIX</acronym> <function>close()</function> function.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-READ">
-    <refmeta>
-      <refentrytitle>read</refentrytitle>
-      <refmiscinfo>PYGRESQL - Read</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>read</refname>
-      <refpurpose>reads from the large object</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-read(<replaceable>size</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-READ-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>size</replaceable>
-            </term>
-            <listitem>
-              <para>
-                Maximal size of the buffer to be read (integer).
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-READ-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              string
-            </term>
-            <listitem>
-              <para>
-                The read buffer.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-READ-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad parameter type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Object is not opened, or read error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection or invalid object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-READ-1">
-      <title>Description</title>
-      <para>
-        <function>read()</function> method allows to read data from the large object,
-        starting at current position.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-WRITE">
-    <refmeta>
-      <refentrytitle>write</refentrytitle>
-      <refmiscinfo>PYGRESQL - Write</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>write</refname>
-      <refpurpose>writes to the large object</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-write(<replaceable>string</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-WRITE-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>string</replaceable>
-            </term>
-            <listitem>
-              <para>
-                Buffer to be written (string).
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-WRITE-2">
-        <title>Return Type</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-WRITE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad parameter type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Object is not opened, or write error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection or invalid object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-WRITE-1">
-      <title>Description</title>
-      <para>
-        <function>write()</function> method allows to write data to the large object,
-        starting at current position.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-SEEK">
-    <refmeta>
-      <refentrytitle>seek</refentrytitle>
-      <refmiscinfo>PYGRESQL - Seek</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>seek</refname>
-      <refpurpose>change current position in the large object</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-seek(<replaceable>offset</replaceable>, <replaceable>whence</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-SEEK-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>offset</replaceable>
-            </term>
-            <listitem>
-              <para>
-                Position offset (integer).
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <replaceable>whence</replaceable>
-            </term>
-            <listitem>
-              <para>
-                Positional parameter (integer).
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-SEEK-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              integer
-            </term>
-            <listitem>
-              <para>
-                New current position in the object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-SEEK-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad parameter type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Object is not opened, or seek error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection or invalid object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-SEEK-1">
-      <title>Description</title>
-      <para>
-        <function>seek()</function> method allows to move the cursor position
-        in the large object. The whence parameter can be obtained by OR-ing the constants defined in the 
-        <literal>pg</literal> module (<literal>SEEK_SET, SEEK_CUR, SEEK_END</literal>).
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-TELL">
-    <refmeta>
-      <refentrytitle>tell</refentrytitle>
-      <refmiscinfo>PYGRESQL - Tell</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>tell</refname>
-      <refpurpose>returns current position in the large object</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-tell()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-TELL-1">
-        <title>Parameters</title>
-          <para>
-            none
-          </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-TELL-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              integer
-            </term>
-            <listitem>
-              <para>
-                Current position in the object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-TELL-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Object is not opened, or seek error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection or invalid object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-TELL-1">
-      <title>Description</title>
-      <para>
-        <function>tell()</function> method allows to get the current position in the large object.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-UNLINK">
-    <refmeta>
-      <refentrytitle>unlink</refentrytitle>
-      <refmiscinfo>PYGRESQL - Unlink</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>unlink</refname>
-      <refpurpose>deletes the large object</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-unlink()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-UNLINK-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-UNLINK-2">
-        <title>Return Type</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-UNLINK-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Object is not closed, or unlink error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection or invalid object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-UNLINK-1">
-      <title>Description</title>
-      <para>
-        <function>unlink()</function> method unlinks (deletes) the large object.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-SIZE">
-    <refmeta>
-      <refentrytitle>size</refentrytitle>
-      <refmiscinfo>PYGRESQL - Size</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>size</refname>
-      <refpurpose>gives the large object size</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-size()
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-SIZE-1">
-        <title>Parameters</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-SIZE-2">
-        <title>Return Type</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              integer
-            </term>
-            <listitem>
-              <para>
-                The large object size.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-SIZE-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>SyntaxError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Object is not opened, or seek/tell error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection or invalid object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-SIZE-1">
-      <title>Description</title>
-      <para>
-        <function>size()</function> method allows to get the size of
-        the large object. It was implemented because this function 
-        is very useful for a WWW interfaced database.
-        Currently the large object needs to be opened.
-      </para>
-    </refsect1>
-
-  </refentry>
-
-<!-- ********************************************************** -->
-
-  <refentry id="PYGRESQL-PGLARGEOBJECT-EXPORT">
-    <refmeta>
-      <refentrytitle>export</refentrytitle>
-      <refmiscinfo>PYGRESQL - Export</refmiscinfo>
-    </refmeta>
-    <refnamediv>
-      <refname>export</refname>
-      <refpurpose>saves the large object to file</refpurpose>
-    </refnamediv>
-
-    <refsynopsisdiv>
-<synopsis>
-export(<replaceable>filename</replaceable>)
-</synopsis>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-EXPORT-1">
-        <title>Parameters</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <replaceable>filename</replaceable>
-            </term>
-            <listitem>
-              <para>
-                The file to be created.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-EXPORT-2">
-        <title>Return Type</title>
-        <para>
-          none
-        </para>
-      </refsect2>
-
-      <refsect2 id="R2-PYGRESQL-PGLARGEOBJECT-EXPORT-3">
-        <title>Exceptions</title>
-        <variablelist>
-          <varlistentry>
-            <term>
-              <errorname>TypeError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Bad argument type, or too many arguments.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>IOError</errorname>
-            </term>
-            <listitem>
-              <para>
-                Object is not closed, or export error.
-              </para>
-            </listitem>
-          </varlistentry>
-          <varlistentry>
-            <term>
-              <errorname>pg.error</errorname>
-            </term>
-            <listitem>
-              <para>
-                Invalid  connection or invalid object.
-              </para>
-            </listitem>
-          </varlistentry>
-        </variablelist>
-      </refsect2>
-
-    </refsynopsisdiv>
-
-    <refsect1 id="R1-PYGRESQL-PGLARGEOBJECT-EXPORT-1">
-      <title>Description</title>
-      <para>
-        <function>export()</function> method allows to dump the
-        content of a large object in a very simple way.
-        The exported file is created on the host of the program,
-        not the server host.
-      </para>
-    </refsect1>
-
-  </refentry>
-
- </sect1>
-
-
- <sect1 id="pygresql-db-api">
-  <title><acronym>DB-API</acronym> Interface</title>
-
-  <comment>
-   This section needs to be written.
-  </comment>
-
-  <para>
-   See <ulink
-   url="http://www.python.org/topics/database/DatabaseAPI-2.0.html"
-   >http://www.python.org/topics/database/DatabaseAPI-2.0.html</ulink>
-   for a description of the <acronym>DB-API</acronym> 2.0.
-  </para>
- </sect1>
-
-</chapter>
diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml
deleted file mode 100644
index 66bb25a3af1..00000000000
--- a/doc/src/sgml/queries.sgml
+++ /dev/null
@@ -1,958 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/queries.sgml,v 1.15 2002/04/25 20:14:43 tgl Exp $ -->
-
-<chapter id="queries">
- <title>Queries</title>
-
- <sect1 id="queries-overview">
-  <title>Overview</title>
-
- <para>
-  A <firstterm>query</firstterm> is the process of retrieving or the command
-  to retrieve data from a database.  In SQL the <command>SELECT</command>
-  command is used to specify queries.  The general syntax of the
-  <command>SELECT</command> command is
-<synopsis>
-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.  The simplest kind of
-  query has the form
-<programlisting>
-SELECT * FROM table1;
-</programlisting>
-  Assuming that there is a table called table1, this command would
-  retrieve all rows and all columns from table1.  (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, client libraries will offer functions to
-  retrieve individual rows and columns.)  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 even make calculations on the
-  columns before retrieving them; see <xref
-  linkend="queries-select-lists">.  For example, if table1 has columns
-  named a, b, and c (and perhaps others) you can make the following
-  query:
-<programlisting>
-SELECT a, b + c FROM table1;
-</programlisting>
-  (assuming that b and c are of a numeric data type).
- </para>
-
- <para>
-  <literal>FROM table1</literal> is a particularly simple kind of
-  table expression.  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 SELECT 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>
-
-  <para>
-   A <firstterm>table expression</firstterm> specifies a table.  The
-   table expression contains a FROM clause that is optionally followed
-   by WHERE, GROUP BY, and 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 WHERE, GROUP BY, and HAVING clauses in the table expression
-   specify a pipeline of successive transformations performed on the
-   table derived in the FROM clause.  The derived table that is produced by
-   all these transformations provides the input rows used to compute output
-   rows as specified by the select list of column value expressions.
-  </para>
-	
-  <sect2 id="queries-from">
-   <title>FROM clause</title>
- 
-   <para>
-    The FROM clause 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 may 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 FROM clause they are
-    cross-joined (see below) to form the derived table that may then
-    be subject to transformations by the WHERE, GROUP BY, and HAVING
-    clauses and is finally the result of the overall table expression.
-   </para>
-
-   <para>
-    When a table reference names a table that is the
-    supertable of a table inheritance hierarchy, the table reference
-    produces rows of not only that table but all of its subtable successors,
-    unless the keyword ONLY precedes the table name.  However, the reference
-    produces only the columns that appear in the named table --- any columns
-    added in subtables are ignored.
-   </para>
-
-   <sect3 id="queries-join">
-    <title>Joined Tables</title>
-
-    <indexterm zone="queries-join">
-     <primary>joins</primary>
-    </indexterm>
-
-    <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 JOIN are supported.
-    </para>
-
-    <variablelist>
-     <title>Join Types</title>
-
-     <varlistentry>
-      <term>CROSS JOIN</term>
-
-      <indexterm>
-       <primary>joins</primary>
-       <secondary>cross</secondary>
-      </indexterm>
-
-      <listitem>
-<synopsis>
-<replaceable>T1</replaceable> CROSS JOIN <replaceable>T2</replaceable>
-</synopsis>
-
-       <para>
-        For each combination of rows from
-        <replaceable>T1</replaceable> and
-        <replaceable>T2</replaceable>, the derived 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.  A cross join is equivalent to an
-        <literal>INNER JOIN ON TRUE</literal>.
-       </para>
-
-       <tip>
-        <para>
-         <literal>FROM <replaceable>T1</replaceable> CROSS JOIN
-         <replaceable>T2</replaceable></literal> is equivalent to
-         <literal>FROM <replaceable>T1</replaceable>,
-         <replaceable>T2</replaceable></literal>.
-        </para>
-       </tip>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Qualified joins</term>
-
-      <indexterm>
-       <primary>joins</primary>
-       <secondary>outer</secondary>
-      </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 <token>INNER</token> and <token>OUTER</token> are
-        optional for all joins.  <token>INNER</token> is the default;
-        <token>LEFT</token>, <token>RIGHT</token>, and
-        <token>FULL</token> imply an OUTER JOIN.
-       </para>
-
-       <para>
-        The <firstterm>join condition</firstterm> is specified in the
-        ON or USING clause, or implicitly by the word 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 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 WHERE
-	clause.  A pair of rows from T1 and T2 match if the ON expression
-	evaluates to TRUE for them.
-       </para>
-
-       <para>
-        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
-	a JOIN USING has one column for each of the equated pairs of
-	input columns, followed by all of the other 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 ON is used there will be two columns a, b, and c in the
-        result, whereas with USING there will be only one of each.
-       </para>
-
-       <para>
-        <indexterm>
-	 <primary>joins</primary>
-	 <secondary>natural</secondary>
-	</indexterm>
-        Finally, NATURAL is a shorthand form of USING: it forms a USING
-	list consisting of exactly those column names that appear in both
-	input tables.  As with USING, these columns appear only once in
-	the output table.
-       </para>
-
-       <para>
-        The possible types of qualified JOIN are:
-       </para>
-
-       <variablelist>
-        <varlistentry>
-         <term>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>LEFT OUTER JOIN</term>
-
-         <indexterm>
-          <primary>joins</primary>
-          <secondary>left</secondary>
-         </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 returned with NULL values in columns of
-           T2.  Thus, the joined table unconditionally has at least one
-	   row for each row in T1.
-          </para>
-         </listitem>
-        </varlistentry>
-         
-        <varlistentry>
-         <term>RIGHT OUTER JOIN</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, a joined row is returned with NULL values in columns of
-           T1.  This is the converse of a left join: the result table will
-           unconditionally have a row for each row in T2.
-          </para>
-         </listitem>
-        </varlistentry>
-         
-        <varlistentry>
-         <term>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 returned 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 returned.
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    <para>
-     Joins of all types can be chained together or nested: either
-     or both of <replaceable>T1</replaceable> and
-     <replaceable>T2</replaceable> may be joined tables.  Parentheses
-     may be used around JOIN clauses to control the join order.  In the
-     absence of parentheses, JOIN clauses nest left-to-right.
-    </para>
-   </sect3>
-
-   <sect3 id="queries-subqueries">
-    <title>Subqueries</title>
-
-    <indexterm zone="queries-subqueries">
-     <primary>subqueries</primary>
-    </indexterm>
-
-    <para>
-     Subqueries specifying a derived table must be enclosed in
-     parentheses and <emphasis>must</emphasis> be named using an AS
-     clause.  (See <xref linkend="queries-table-aliases">.)
-    </para>
-
-<programlisting>
-FROM (SELECT * FROM table1) AS alias_name
-</programlisting>
-
-    <para>
-     This example is equivalent to <literal>FROM table1 AS
-     alias_name</literal>.  More interesting cases, which can't be
-     reduced to a plain join, arise when the subquery involves grouping
-     or aggregation.
-    </para>
-   </sect3>
-
-   <sect3 id="queries-table-aliases">
-    <title>Table and Column Aliases</title>
-
-    <indexterm zone="queries-table-aliases">
-     <primary>label</primary>
-     <secondary>table</secondary>
-    </indexterm>
-
-    <indexterm>
-     <primary>alias</primary>
-     <see>label</see>
-    </indexterm>
-
-    <para>
-     A temporary name can be given to tables and complex table
-     references to be used for references to the derived table in
-     further processing.  This is called a <firstterm>table
-     alias</firstterm>.
-<synopsis>
-FROM <replaceable>table_reference</replaceable> AS <replaceable>alias</replaceable>
-</synopsis>
-     Here, <replaceable>alias</replaceable> can be any regular
-     identifier.  The alias becomes the new name of the table
-     reference for the current query -- it is no longer possible to
-     refer to the table by the original name.  Thus
-<programlisting>
-SELECT * FROM my_table AS m WHERE my_table.a > 5;
-</programlisting>
-     is not valid SQL syntax.  What will actually happen (this is a
-     <productname>PostgreSQL</productname> extension to the standard)
-     is that an implicit
-     table reference is added to the FROM clause, so the query is
-     processed as if it were written as
-<programlisting>
-SELECT * FROM my_table AS m, my_table AS my_table WHERE my_table.a > 5;
-</programlisting>
-     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 my_table AS a CROSS JOIN my_table AS b ...
-</programlisting>
-     Additionally, an alias is required if the table reference is a
-     subquery.
-    </para>
-
-    <para>
-     Parentheses are used to resolve ambiguities.  The following
-     statement will assign the alias <literal>b</literal> to the
-     result of the join, unlike the previous example:
-<programlisting>
-SELECT * FROM (my_table AS a CROSS JOIN my_table) AS b ...
-</programlisting>
-    </para>
-
-    <para>
-<synopsis>
-FROM <replaceable>table_reference</replaceable> <replaceable>alias</replaceable>
-</synopsis>
-     This form is equivalent to the previously treated one; the
-     <token>AS</token> key word is noise.
-    </para>
-
-    <para>
-<synopsis>
-FROM <replaceable>table_reference</replaceable> <optional>AS</optional> <replaceable>alias</replaceable> ( <replaceable>column1</replaceable> <optional>, <replaceable>column2</replaceable> <optional>, ...</optional></optional> )
-</synopsis>
-     In this form,
-     in addition to renaming the table as described above, the columns
-     of the table are also given temporary names for use by the surrounding
-     query.  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 JOIN clause, using any of
-     these forms, the alias hides the original names within the 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 A is not visible outside the alias C.
-    </para>
-   </sect3>
-
-   <sect3 id="queries-table-expression-examples">
-    <title>Examples</title>
-
-    <para>
-<programlisting>
-FROM T1 INNER JOIN T2 USING (C)
-FROM T1 LEFT OUTER JOIN T2 USING (C)
-FROM (T1 RIGHT OUTER JOIN T2 ON (T1.C1=T2.C1)) AS DT1
-FROM (T1 FULL OUTER JOIN T2 USING (C)) AS DT1 (DT1C1, DT1C2)
-
-FROM T1 NATURAL INNER JOIN T2
-FROM T1 NATURAL LEFT OUTER JOIN T2
-FROM T1 NATURAL RIGHT OUTER JOIN T2
-FROM T1 NATURAL FULL OUTER JOIN T2
-
-FROM (SELECT * FROM T1) DT1 CROSS JOIN T2, T3
-FROM (SELECT * FROM T1) DT1, T2, T3
-</programlisting>
-
-     Above are some examples of joined tables and complex derived
-     tables.  Notice how the AS clause renames or names a derived
-     table and how the optional comma-separated list of column names
-     that follows renames the columns.  The last two
-     FROM clauses produce the same derived table from T1, T2, and T3.
-     The AS keyword was omitted in naming the subquery as DT1.  The
-     keywords OUTER and INNER are noise that can be omitted also.
-    </para>
-   </sect3>
-
-  </sect2>
-
-  <sect2 id="queries-where">
-   <title>WHERE clause</title>
-
-   <indexterm zone="queries-where">
-    <primary>where</primary>
-   </indexterm>
-
-   <para>
-    The syntax of the WHERE clause is
-<synopsis>
-WHERE <replaceable>search_condition</replaceable>
-</synopsis>
-    where <replaceable>search_condition</replaceable> is any value
-    expression as defined in <xref linkend="sql-expressions"> that
-    returns a value of type <type>boolean</type>.
-   </para>
-
-   <para>
-    After the processing of the FROM clause is done, each row of the
-    derived table is checked against the search condition.  If the
-    result of the condition is true, the row is kept in the output
-    table, otherwise (that is, if the result is false or NULL) it is
-    discarded.  The search condition typically references at least some
-    column in the table generated in the FROM clause; this is not
-    required, but otherwise the WHERE clause will be fairly useless.
-   </para>
-
-   <note>
-    <para>
-     Before the implementation of the JOIN syntax, it was necessary to
-     put the join condition of an inner join in the WHERE 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 JOIN
-     syntax in the FROM clause is probably not as portable to other
-     products.  For outer joins there is no choice in any case:  they
-     must be done in the FROM clause.  A ON/USING clause of an outer join
-     is <emphasis>not</> equivalent to a WHERE condition, because it
-     determines the addition of rows (for unmatched input rows) as well
-     as the removal of rows from the final result.
-    </para>
-   </note>
-
-<programlisting>
-FROM FDT WHERE
-    C1 > 5
-
-FROM FDT WHERE
-    C1 IN (1, 2, 3)
-FROM FDT WHERE
-    C1 IN (SELECT C1 FROM T2)
-FROM FDT WHERE
-    C1 IN (SELECT C3 FROM T2 WHERE C2 = FDT.C1 + 10)
-
-FROM FDT WHERE
-    C1 BETWEEN (SELECT C3 FROM T2 WHERE C2 = FDT.C1 + 10) AND 100
-
-FROM FDT WHERE
-    EXISTS (SELECT C1 FROM T2 WHERE C2 > FDT.C1)
-</programlisting>
-
-   <para>
-    In the examples above, <literal>FDT</literal> is the table derived
-    in the FROM clause. Rows that do not meet the search condition of
-    the 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 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.  Qualifying the column name adds
-    clarity even when it is not needed.  This shows how the column
-    naming scope of an outer query extends into its inner queries.
-   </para>
-  </sect2>
-
-
-  <sect2 id="queries-group">
-   <title>GROUP BY and HAVING clauses</title>	   
-
-   <indexterm zone="queries-group">
-    <primary>group</primary>
-   </indexterm>
-
-   <para>
-    After passing the WHERE filter, the derived input table may be
-    subject to grouping, using the GROUP BY clause, and elimination of
-    group rows using the 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>
-
-   <para>
-    The GROUP BY clause is used to group together rows in a table that
-    share the same values in all the columns listed. The order in
-    which the columns are listed does not matter (as opposed to an
-    ORDER BY clause).  The purpose is to reduce each group of rows
-    sharing common values into one group row that is representative of
-    all rows in the group.  This is done to eliminate redundancy in
-    the output and/or obtain aggregates that apply to these groups.
-   </para>
-	  
-   <para>
-    Once a table is grouped, columns that are not used in the
-    grouping cannot be referenced except in aggregate expressions,
-    since a specific value in those columns is ambiguous - which row
-    in the group should it come from?  The grouped-by columns can be
-    referenced in select list column expressions since they have a
-    known constant value per group.  Aggregate functions on the
-    ungrouped columns provide values that span the rows of a group,
-    not of the whole table.  For instance, a
-    <function>sum(sales)</function> on a table grouped by product code
-    gives the total sales for each product, not the total sales on all
-    products.  Aggregates computed on the ungrouped columns are
-    representative of the group, whereas individual values of an ungrouped
-    column are not.
-   </para>
-
-   <para>
-    Example:
-<programlisting>
-SELECT pid, p.name, (sum(s.units) * p.price) AS sales
-  FROM products p LEFT JOIN sales s USING ( pid )
-  GROUP BY pid, p.name, p.price;
-</programlisting>
-    In this example, the columns <literal>pid</literal>, <literal>p.name</literal>, and <literal>p.price</literal> must be in
-    the GROUP BY clause since they are referenced in the query select
-    list.  The column s.units does not have to be in the GROUP BY list
-    since it is only used in an aggregate expression
-    (<function>sum()</function>), which represents the group of sales
-    of a product.  For each product, a summary row is returned about
-    all sales of the product.
-   </para>
-
-   <para>
-    In strict SQL, GROUP BY can only group by columns of the source
-    table but <productname>PostgreSQL</productname> extends this to also allow GROUP BY to group by
-    select columns in the query select list.  Grouping by value
-    expressions instead of simple column names is also allowed.
-   </para>
-
-   <para>
-<synopsis>
-SELECT <replaceable>select_list</replaceable> FROM ... <optional>WHERE ...</optional> GROUP BY ... HAVING <replaceable>boolean_expression</replaceable>
-</synopsis>
-    If a table has been grouped using a GROUP BY clause, but then only
-    certain groups are of interest, the HAVING clause can be used,
-    much like a WHERE clause, to eliminate groups from a grouped
-    table.  <productname>PostgreSQL</productname> allows a HAVING clause to be
-    used without a GROUP BY, in which case it acts like another WHERE
-    clause, but the point in using HAVING that way is not clear.  A good
-    rule of thumb is that a HAVING condition should refer to the results
-    of aggregate functions.  A restriction that does not involve an
-    aggregate is more efficiently expressed in the WHERE clause.
-   </para>
-
-   <para>
-    Example:
-<programlisting>
-SELECT pid    AS "Products",
-       p.name AS "Over 5000",
-       (sum(s.units) * (p.price - p.cost)) AS "Past Month Profit"
-  FROM products p LEFT JOIN sales s USING ( pid )
-  WHERE s.date > CURRENT_DATE - INTERVAL '4 weeks'
-  GROUP BY pid, p.name, p.price, p.cost
-    HAVING sum(p.price * s.units) > 5000;
-</programlisting>
-    In the example above, the WHERE clause is selecting rows by a
-    column that is not grouped, while the HAVING clause
-    restricts the output to groups with total gross sales over 5000.
-   </para>
-  </sect2>
- </sect1>
-
-
- <sect1 id="queries-select-lists">
-  <title>Select Lists</title>
-
-  <indexterm>
-   <primary>select</primary>
-   <secondary>select list</secondary>
-  </indexterm>
-
-  <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.  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 a, b, and c are either the actual names of the
-   columns of tables referenced in the 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
-   WHERE clause (unless grouping is used, in which case it is the same
-   as in the HAVING clause).  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.b, tbl1.c 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 retrieved
-   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 FROM clause; they could be
-   constant arithmetic expressions as well, for instance.
-  </para>
-
-  <sect2 id="queries-column-labels">
-   <title>Column Labels</title>
-
-   <indexterm zone="queries-column-labels">
-    <primary>label</primary>
-    <secondary>column</secondary>
-   </indexterm>
-
-   <para>
-    The entries in the select list can be assigned names for further
-    processing.  The <quote>further processing</quote> in this case is
-    an optional sort specification and the client application (e.g.,
-    column headers for display).  For example:
-<programlisting>
-SELECT a AS value, b + c AS sum FROM ...
-</programlisting>
-   </para>
-
-   <para>
-    If no output column name is specified via AS, the system assigns a
-    default 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>
-
-   <note>
-    <para>
-     The naming of output columns here is different from that done in
-     the FROM clause (see <xref linkend="queries-table-aliases">).  This
-     pipeline will in fact allow you to rename the same column twice,
-     but the name chosen in the select list is the one that will be
-     passed on.
-    </para>
-   </note>
-  </sect2>
-
-  <sect2 id="queries-distinct">
-   <title>DISTINCT</title>
-
-   <indexterm zone="queries-distinct">
-    <primary>distinct</primary>
-   </indexterm>
-
-   <para>
-    After the select list has been processed, the result table may
-    optionally be subject to the elimination of duplicates.  The
-    <token>DISTINCT</token> key word is written directly after the
-    <token>SELECT</token> to enable this:
-<synopsis>
-SELECT DISTINCT <replaceable>select_list</replaceable> ...
-</synopsis>
-    (Instead of <token>DISTINCT</token> the word <token>ALL</token>
-    can be used to select the default behavior of retaining all rows.)
-   </para>
-
-   <para>
-    Obviously, two rows are considered distinct if they differ in at
-    least one column value.  NULLs 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 DISTINCT filter.  (DISTINCT ON processing
-    occurs after ORDER BY sorting.)
-   </para>
-
-   <para>
-    The 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 GROUP BY and subselects in
-    FROM the construct can be avoided, but it is very 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>intersection</primary>
-  </indexterm>
-  <indexterm zone="queries-union">
-   <primary>except</primary>
-  </indexterm>
-
-  <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 really says
-<synopsis>
-(<replaceable>query1</replaceable> UNION <replaceable>query2</replaceable>) UNION <replaceable>query3</replaceable>
-</synopsis>
-  </para>
-
-  <para>
-   <command>UNION</command> 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 all duplicate rows, in the sense of DISTINCT,
-   unless ALL is specified.
-  </para>
-
-  <para>
-   <command>INTERSECT</command> 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 ALL is specified.
-  </para>
-
-  <para>
-   <command>EXCEPT</command> returns all rows that are in the result
-   of <replaceable>query1</replaceable> but not in the result of
-   <replaceable>query2</replaceable>.  Again, duplicates are
-   eliminated unless ALL is specified.
-  </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 both return the same number of columns, and
-   that 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>
-   <secondary>query results</secondary>
-  </indexterm>
-	   
-  <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 random 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 ORDER BY clause specifies the sort order:
-<synopsis>
-SELECT <replaceable>select_list</replaceable>
-    FROM <replaceable>table_expression</replaceable>
-    ORDER BY <replaceable>column1</replaceable> <optional>ASC | DESC</optional> <optional>, <replaceable>column2</replaceable> <optional>ASC | DESC</optional> ...</optional>
-</synopsis>
-   <replaceable>column1</replaceable>, etc., refer to select list
-   columns.  These can be either the output name of a column (see
-   <xref linkend="queries-column-labels">) or the number of a column.  Some
-   examples:
-<programlisting>
-SELECT a, b FROM table1 ORDER BY a;
-SELECT a + b AS sum, c FROM table1 ORDER BY sum;
-SELECT a, sum(b) FROM table1 GROUP BY a ORDER BY 1;
-</programlisting>
-  </para>
-
-  <para>
-   As an extension to the SQL standard, <productname>PostgreSQL</productname> also allows ordering
-   by arbitrary expressions:
-<programlisting>
-SELECT a, b FROM table1 ORDER BY a + b;
-</programlisting>
-   References to column names in the FROM clause that are renamed in
-   the select list are also allowed:
-<programlisting>
-SELECT a AS b FROM table1 ORDER BY a;
-</programlisting>
-   But these extensions do not work in queries involving UNION, INTERSECT,
-   or EXCEPT, and are not portable to other <acronym>DBMS</acronym>.
-  </para>
-
-  <para>
-   Each column specification may be followed by an optional <token>ASC</token> or
-   <token>DESC</token> to set the sort direction.  <token>ASC</token> is 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.
-  </para>
-
-  <para>
-   If more than one sort column is specified, the later entries are
-   used to sort rows that are equal under the order imposed by the
-   earlier sort specifications.
-  </para>
- </sect1>
-
- <sect1 id="queries-limit">
-  <title>LIMIT and OFFSET</title>
-
-  <indexterm zone="queries-limit">
-   <primary>limit</primary>
-  </indexterm>
-
-  <indexterm zone="queries-limit">
-   <primary>offset</primary>
-   <secondary>with query results</secondary>
-  </indexterm>
-
-<synopsis>
-SELECT <replaceable>select_list</replaceable>
-    FROM <replaceable>table_expression</replaceable>
-    <optional>LIMIT { <replaceable>number</replaceable> | ALL }</optional> <optional>OFFSET <replaceable>number</replaceable></optional>
-</synopsis>
-
-  <para>
-   LIMIT allows you to retrieve just a portion of the rows that are
-   generated by the rest of the query.  If a limit count is given, no
-   more than that many rows will be returned.
-   LIMIT ALL is the same as omitting a LIMIT clause.
-  </para>
-
-  <para>
-   OFFSET says to skip that many rows before beginning to return rows
-   to the client.  OFFSET 0 is the same as omitting an OFFSET clause.
-   If both OFFSET and LIMIT appear, then OFFSET rows are skipped before
-   starting to count the LIMIT rows that are returned.
-  </para>
-
-  <para>
-   When using LIMIT, it is a good idea to use an 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 may be asking
-   for the tenth through twentieth rows, but tenth through twentieth
-   in what ordering?  The ordering is unknown, unless you specified
-   ORDER BY.
-  </para>
-
-  <para>
-   The query optimizer takes 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 give for LIMIT and
-   OFFSET.  Thus, using different LIMIT/OFFSET values to select
-   different subsets of a query result <emphasis>will give
-   inconsistent results</emphasis> unless you enforce a predictable
-   result ordering with 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 ORDER
-   BY is used to constrain the order.
-  </para>
- </sect1>
-
-</chapter>
diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml
deleted file mode 100644
index 7a37e7b99af..00000000000
--- a/doc/src/sgml/query.sgml
+++ /dev/null
@@ -1,819 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.25 2002/01/20 22:19:56 petere Exp $
--->
-
- <chapter id="tutorial-sql">
-  <title>The <acronym>SQL</acronym> Language</title>
-
-  <sect1 id="tutorial-sql-intro">
-   <title>Introduction</title>
-
-   <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>SQL92</acronym>, including <xref
-    linkend="MELT93"> and <xref linkend="DATE97">.
-    You should be aware that some <productname>PostgreSQL</productname>
-    language features are extensions to the standard.
-   </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 started <application>psql</application>.
-   </para>
-
-   <para>
-    Examples in this manual can also be found in the
-    <productname>PostgreSQL</productname> source distribution
-    in the directory <filename>src/tutorial/</filename>.  Refer to the
-    <filename>README</filename> file in that directory for how to use
-    them.  To start the tutorial, do the following:
-
-<screen>
-<prompt>$</prompt> <userinput>cd <replaceable>....</replaceable>/src/tutorial</userinput>
-<prompt>$</prompt> <userinput>psql -s mydb</userinput>
-<computeroutput>
-...
-</computeroutput>
-
-<prompt>mydb=&gt;</prompt> <userinput>\i basics.sql</userinput>
-</screen>
-
-    The <literal>\i</literal> command reads in commands from the
-    specified file. The <literal>-s</literal> option puts you in
-    single step mode which pauses before sending each query 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>
-
-    <productname>PostgreSQL</productname> is a <firstterm>relational
-    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>cluster</primary></indexterm>
-
-    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>.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-table">
-   <title>Creating a New Table</title>
-
-   <indexterm zone="tutorial-table">
-    <primary>CREATE TABLE</primary>
-   </indexterm>
-
-   <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) may 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 <literal>date</literal>.
-    This may be convenient or confusing -- you choose.)
-   </para>
-
-   <para>
-    <productname>PostgreSQL</productname> supports the usual
-    <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.
-    <productname>PostgreSQL</productname> can be customized with an
-    arbitrary number of user-defined data types.  Consequently, type
-    names are not syntactical keywords, 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
-    <productname>PostgreSQL</productname>-specific data type.
-   </para>
-
-   <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>
-
-   <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> column 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>
-
-    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 to the
-    backend server machine, not the client, since the backend server
-    reads the file directly.  You can read more about the
-    <command>COPY</command> command in the <citetitle>Reference
-    Manual</citetitle>.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-select">
-   <title>Querying a Table</title>
-
-   <para>
-    <indexterm><primary>query</primary></indexterm>
-    <indexterm><primary>SELECT</primary></indexterm>
-
-    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
-    <classname>weather</classname>, type:
-<programlisting>
-SELECT * FROM weather;
-</programlisting>
-    (here <literal>*</literal> means <quote>all columns</quote>) and
-    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 may specify any arbitrary expressions in the target 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.  (It is optional.)
-   </para>
-
-   <para>
-    Arbitrary Boolean operators (<literal>AND</literal>,
-    <literal>OR</literal>, and <literal>NOT</literal>) are allowed in
-    the qualification of a query.  For example, the following
-    retrieves the weather of San Francisco on rainy days:
-
-<programlisting>
-SELECT * FROM weather
-    WHERE city = 'San Francisco'
-    AND prcp > 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>
-    <indexterm><primary>DISTINCT</primary></indexterm>
-    <indexterm><primary>duplicate</primary></indexterm>
-
-    As a final note, you can request that the results of a select can
-    be returned in sorted order or with duplicate rows removed.  (Just
-    to make sure the following won't confuse you,
-    <literal>DISTINCT</literal> and <literal>ORDER BY</literal> can be
-    used separately.)
-
-<programlisting>
-SELECT DISTINCT city
-    FROM weather
-    ORDER BY city;
-</programlisting>
-
-<screen>
-     city
----------------
- Hayward
- San Francisco
-(2 rows)
-</screen>
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-join">
-   <title>Joins Between Tables</title>
-
-   <indexterm zone="tutorial-join">
-    <primary>join</primary>
-   </indexterm>
-
-   <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 city column of
-    each row of the weather table with the name column of all rows in
-    the cities table, and select the pairs of rows where these values match.
-    <note>
-     <para>
-      This  is only a conceptual model.  The actual join may
-      be performed in a more efficient manner, 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
-       <classname>cities</classname> table for Hayward, so the join
-       ignores the unmatched rows in the 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 of the
-       <classname>weather</classname> and the
-       <classname>cities</classname> table 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 find out 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 out which table they belong to, but it is good
-    style to fully qualify column names in join queries:
-
-<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>
-   </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
-    <classname>weather</classname> table and for each row to find the
-    matching <classname>cities</classname> row.  If no matching row is
-    found we want some <quote>empty values</quote> to be substituted
-    for the <classname>cities</classname> 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 <classname>weather</classname> row to the
-    <structfield>temp_lo</structfield> and
-    <structfield>temp_hi</structfield> columns of all other
-    <classname>weather</classname> 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 < W2.temp_lo
-    AND W1.temp_hi > 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</primary>
-   </indexterm>
-
-   <para>
-    <indexterm><primary>average</primary></indexterm>
-    <indexterm><primary>count</primary></indexterm>
-    <indexterm><primary>max</primary></indexterm>
-    <indexterm><primary>min</primary></indexterm>
-    <indexterm><primary>sum</primary></indexterm>
-
-    Like  most  other relational database products, 
-    <productname>PostgreSQL</productname> supports
-    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>
-
-   <para>
-    <indexterm><primary>subquery</primary></indexterm>
-
-    If we want 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 the rows that will
-    go into the aggregation stage; so it has to be evaluated before
-    aggregate functions are computed.)
-    However, as is often the case
-    the query can be restated to accomplish the intended 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 sub-select is an independent computation
-    that computes its own aggregate separately from what is happening
-    in the outer select.
-   </para>
-
-   <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.
-    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) < 40;
-</programlisting>
-
-<screen>
-  city   | max
----------+-----
- Hayward |  37
-(1 row)
-</screen>
-
-    which gives us the same results for only the cities that have all
-    <literal>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%'
-    GROUP BY city
-    HAVING max(temp_lo) < 40;
-</programlisting>
-   </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,
-    <literal>HAVING</literal> clauses always contain aggregate functions.
-    (Strictly speaking, you are allowed to write a <literal>HAVING</literal>
-    clause that doesn't use aggregates, but it's wasteful: The same condition
-    could be used more efficiently at the <literal>WHERE</literal> stage.)
-   </para>
-
-   <para>
-    Observe that 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.
-   </para>
-  </sect1>
-
-
-  <sect1 id="tutorial-update">
-   <title>Updates</title>
-
-   <indexterm zone="tutorial-update">
-    <primary>UPDATE</primary>
-   </indexterm>
-
-   <para>
-    You can update existing rows using the
-    <command>UPDATE</command> command. 
-    Suppose you discover the temperature readings are
-    all  off  by 2 degrees as of November 28, you may update the
-    data as follows:
-
-<programlisting>
-UPDATE weather
-    SET temp_hi = temp_hi - 2,  temp_lo = temp_lo - 2
-    WHERE date > '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>
-
-   <para>
-    Suppose you are no longer interested in the weather of Hayward,
-    then you can do the following to delete those rows from the table.
-    Deletions are performed using the <command>DELETE</command>
-    command:
-<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 queries 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>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/recovery.sgml b/doc/src/sgml/recovery.sgml
deleted file mode 100644
index aa10b8cf640..00000000000
--- a/doc/src/sgml/recovery.sgml
+++ /dev/null
@@ -1,104 +0,0 @@
-<chapter Id="failure">
- <title>Database Failures</title>
-
- <para>
-  Database failures (or the possibility of such) must be assumed to be
-  lurking, ready to strike at some time in the future. A prudent
-  database administrator will plan for the inevitability of failures
-  of all possible kinds, and will have appropriate plans and
-  procedures in place <emphasis>before</emphasis> the failure occurs.
- </para>
-
- <para>
-  Database recovery is necessary in the event of hardware or software
-  failure. There are several categories of failures; some of these
-  require relatively minor adjustments to the database, while others
-  may depend on the existence of previously prepared database dumps
-  and other recovery data sets. It should be emphasized that if your
-  data is important and/or difficult to regenerate, then you should
-  have considered and prepared for various failure scenarios.
- </para>
-
- <sect1 id="failure-disk-full">
-  <title>Disk Filled</title>
-
-  <para>
-   A filled data disk may result in subsequent corruption of database
-   indexes, but not of the fundamental data tables. If the WAL files
-   are on the same disk (as is the case for a default configuration)
-   then a filled disk during database initialization may result in
-   corrupted or incomplete WAL files. This failure condition is
-   detected and the database will refuse to start up. You must free
-   up additional space on the disk (or move the WAL area to another
-   disk; see <xref linkend="wal-configuration">) and then restart the
-   <application>postmaster</application> to recover from this condition.
-  </para>
- </sect1>
-
- <sect1 id="failure-disk-failed">
-  <title>Disk Failed</title>
-
-  <para>
-   Failure of any disk (or of a logical storage device such as a RAID
-   subsystem) involved with an active database will require
-   that the database be recovered from a previously prepared database
-   dump. This dump must be prepared using
-   <application>pg_dumpall</application>, and updates to the database
-   occurring after the database installation was dumped will be lost. 
-  </para>
- </sect1>
-
-<!--
- <sect1>
-  <title>File Corrupted</title>
-
-  <para>
-  </para>
- </sect1>
-
- <sect1>
-  <title>Table Corrupted</title>
-
-  <para>
-  </para>
- </sect1>
-
- <sect1>
-  <title></title>
-
-  <para>
-  </para>
- </sect1>
-
- <sect1>
-  <title></title>
-
-  <para>
-  </para>
- </sect1>
-
- <sect1>
-  <title></title>
-
-  <para>
-  </para>
- </sect1>
--->
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document: ("postgres.sgml" "set" "book" "chapter")
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/abort.sgml b/doc/src/sgml/ref/abort.sgml
deleted file mode 100644
index 1e5b9bf890c..00000000000
--- a/doc/src/sgml/ref/abort.sgml
+++ /dev/null
@@ -1,154 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/abort.sgml,v 1.11 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ABORT">
- <refmeta>
-  <refentrytitle id="sql-abort-title">ABORT</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   ABORT
-  </refname>
-  <refpurpose>
-   abort the current transaction
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-ABORT [ WORK | TRANSACTION ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-ABORT-1">
-   <refsect2info>
-    <date>1998-09-27</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-
-   <para>
-    None.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-ABORT-2">
-   <refsect2info>
-    <date>1998-09-27</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-ROLLBACK
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  ROLLBACK: no transaction in progress
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If there is not any transaction currently in progress.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-ABORT-1">
-  <refsect1info>
-   <date>1998-09-27</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <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 <acronym>SQL92</acronym> command <command>ROLLBACK</command>,
-   and is present only for historical reasons.
-  </para>
-  <refsect2 id="R2-SQL-ABORT-3">
-   <refsect2info>
-    <date>1998-09-27</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    Use <command>COMMIT</command> to successfully
-    terminate a transaction.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-ABORT-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To abort all changes:
-   <programlisting>
-ABORT WORK;
-   </programlisting>
-  </para>
-
- </refsect1>
-
- <refsect1 id="R1-SQL-ABORT-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-ABORT-4">
-   <refsect2info>
-    <date>1998-09-27</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    This command is a <productname>PostgreSQL</productname> extension present
-    for historical reasons. <command>ROLLBACK</command> is the <acronym>SQL92</acronym>
-    equivalent command.
-   </para>
-  </refsect2>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/allfiles.sgml b/doc/src/sgml/ref/allfiles.sgml
deleted file mode 100644
index c039f661b0c..00000000000
--- a/doc/src/sgml/ref/allfiles.sgml
+++ /dev/null
@@ -1,136 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/allfiles.sgml,v 1.39 2002/04/25 21:47:07 tgl Exp $
-PostgreSQL documentation
-Complete list of usable sgml source files in this directory.
--->
-
-<!-- these will go into the "operators" reference chapter -->
-<!entity all                system "all.sgml">
-<!entity any                system "any.sgml">
-<!entity between            system "between.sgml">
-<!entity in                 system "in.sgml">
-<!entity like               system "like.sgml">
-
-<!-- these will go into the "functions" reference chapter -->
-<!entity avg                system "avg.sgml">
-<!entity cast               system "cast.sgml">
-<!entity charLength         system "char_length.sgml">
-<!entity count              system "count.sgml">
-<!entity currentDate        system "current_date.sgml">
-<!entity currentTime        system "current_time.sgml">
-<!entity currentTimestamp   system "current_timestamp.sgml">
-<!entity currentUser        system "current_user.sgml">
-<!entity exists             system "exists.sgml">
-<!entity extract            system "extract.sgml">
-<!entity initcap            system "initcap.sgml">
-<!entity lower              system "lower.sgml">
-<!entity lpad               system "lpad.sgml">
-<!entity max                system "max.sgml">
-<!entity min                system "min.sgml">
-<!entity position           system "position.sgml">
-<!entity rpad               system "rpad.sgml">
-<!entity substring          system "substring.sgml">
-<!entity sum                system "sum.sgml">
-<!entity translate          system "translate.sgml">
-<!entity trim               system "trim.sgml">
-<!entity upper              system "upper.sgml">
-
-<!-- SQL commands -->
-<!entity abort              system "abort.sgml">
-<!entity alterDatabase      system "alter_database.sgml">
-<!entity alterGroup         system "alter_group.sgml">
-<!entity alterTable         system "alter_table.sgml">
-<!entity alterTrigger       system "alter_trigger.sgml">
-<!entity alterUser          system "alter_user.sgml">
-<!entity analyze            system "analyze.sgml">
-<!entity begin              system "begin.sgml">
-<!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 copyTable          system "copy.sgml">
-<!entity createAggregate    system "create_aggregate.sgml">
-<!entity createConstraint   system "create_constraint.sgml">
-<!entity createDatabase     system "create_database.sgml">
-<!entity createDomain       system "create_domain.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">
-<!entity createOperator     system "create_operator.sgml">
-<!entity createRule         system "create_rule.sgml">
-<!entity createSchema       system "create_schema.sgml">
-<!entity createSequence     system "create_sequence.sgml">
-<!entity createTable        system "create_table.sgml">
-<!entity createTableAs      system "create_table_as.sgml">
-<!entity createTrigger      system "create_trigger.sgml">
-<!entity createType         system "create_type.sgml">
-<!entity createUser         system "create_user.sgml">
-<!entity createView         system "create_view.sgml">
-<!entity declare            system "declare.sgml">
-<!entity delete             system "delete.sgml">
-<!entity dropAggregate      system "drop_aggregate.sgml">
-<!entity dropDatabase       system "drop_database.sgml">
-<!entity dropDomain         system "drop_domain.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">
-<!entity dropOperator       system "drop_operator.sgml">
-<!entity dropRule           system "drop_rule.sgml">
-<!entity dropSequence       system "drop_sequence.sgml">
-<!entity dropTable          system "drop_table.sgml">
-<!entity dropTrigger        system "drop_trigger.sgml">
-<!entity dropType           system "drop_type.sgml">
-<!entity dropUser           system "drop_user.sgml">
-<!entity dropView           system "drop_view.sgml">
-<!entity end                system "end.sgml">
-<!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">
-<!entity reindex            system "reindex.sgml">
-<!entity reset              system "reset.sgml">
-<!entity revoke             system "revoke.sgml">
-<!entity rollback           system "rollback.sgml">
-<!entity select             system "select.sgml">
-<!entity selectInto         system "select_into.sgml">
-<!entity set                system "set.sgml">
-<!entity setConstraints     system "set_constraints.sgml">
-<!entity setSessionAuth     system "set_session_auth.sgml">
-<!entity setTransaction     system "set_transaction.sgml">
-<!entity show               system "show.sgml">
-<!entity truncate           system "truncate.sgml">
-<!entity unlisten           system "unlisten.sgml">
-<!entity update             system "update.sgml">
-<!entity vacuum             system "vacuum.sgml">
-
-<!-- applications and utilities -->
-<!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">
-<!entity initlocation       system "initlocation.sgml">
-<!entity ipcclean           system "ipcclean.sgml">
-<!entity pgAccess           system "pgaccess-ref.sgml">
-<!entity pgConfig           system "pg_config-ref.sgml">
-<!entity pgCtl              system "pg_ctl-ref.sgml">
-<!entity pgDump             system "pg_dump.sgml">
-<!entity pgDumpall          system "pg_dumpall.sgml">
-<!entity pgRestore          system "pg_restore.sgml">
-<!entity pgTclSh            system "pgtclsh.sgml">
-<!entity pgTkSh             system "pgtksh.sgml">
-<!entity postgres           system "postgres-ref.sgml">
-<!entity postmaster         system "postmaster.sgml">
-<!entity psqlRef            system "psql-ref.sgml">
-<!entity vacuumdb           system "vacuumdb.sgml">
diff --git a/doc/src/sgml/ref/alter_database.sgml b/doc/src/sgml/ref/alter_database.sgml
deleted file mode 100644
index 76a4ac014af..00000000000
--- a/doc/src/sgml/ref/alter_database.sgml
+++ /dev/null
@@ -1,171 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_database.sgml,v 1.3 2002/05/17 01:19:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERDATABASE">
- <refmeta>
-  <refentrytitle id="sql-alterdatabase-title">ALTER DATABASE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER DATABASE</refname>
-  <refpurpose>change a database</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> SET <replaceable>variable</replaceable> { TO | = } { <replaceable>value</replaceable> | DEFAULT }
-ALTER DATABASE <replaceable class="PARAMETER">name</replaceable> RESET <replaceable>variable</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>ALTER DATABASE</command> is used to change the session
-   default of a run-time configuration variable for a
-   <productname>PostgreSQL</productname> 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 postmaster.
-  </para>
-
-  <para>
-   Only a superuser or the database owner can change the session defaults for a
-   database.
-  </para>
-
-  <refsect2>
-   <title>Parameters</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of the database whose session defaults are to be altered.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>variable</replaceable></term>
-      <term><replaceable>value</replaceable></term>
-      <listitem>
-       <para>
-        Set the session default for this database of the specified
-        configuration variable to the given value.  If
-        <replaceable>value</replaceable> is <literal>DEFAULT</literal>
-        or, equivalently, <literal>RESET</literal> is used, the
-        database-specific variable setting is removed and the system-wide
-	default
-        setting will be inherited in new sessions.  Use <literal>RESET
-        ALL</literal> to clear all settings.
-       </para>
-
-       <para>
-        See <xref linkend="sql-set" endterm="sql-set-title"> and the
-        <citetitle>Administrator's Guide</citetitle> for more
-        information about allowed variable names and values.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><computeroutput>ALTER DATABASE</computeroutput></term>
-     <listitem>
-      <para>
-       Message returned if the alteration was successful.
-      </para>
-     </listitem>
-    </varlistentry>
-     
-    <varlistentry>
-     <term><computeroutput>ERROR:  database "dbname" does not exist</computeroutput></term>
-     <listitem>
-      <para>
-       Error message returned if the specified database is not known
-       to the system.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Using <xref linkend="sql-alteruser" endterm="sql-alteruser-title">,
-   it is also possible to tie a session default to a specific user
-   rather than a database.  User-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
-   <productname>PostgreSQL</productname> extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteruser" endterm="sql-alteruser-title"></member>
-   <member><xref linkend="sql-createdatabase" endterm="sql-createdatabase-title"></member>
-   <member><xref linkend="sql-dropdatabase" endterm="sql-dropdatabase-title"></member>
-   <member><xref linkend="sql-set" endterm="sql-set-title"></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/alter_group.sgml b/doc/src/sgml/ref/alter_group.sgml
deleted file mode 100644
index 946fbc86e01..00000000000
--- a/doc/src/sgml/ref/alter_group.sgml
+++ /dev/null
@@ -1,160 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_group.sgml,v 1.8 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERGROUP">
- <refmeta>
-  <refentrytitle id="SQL-ALTERGROUP-title">ALTER GROUP</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   ALTER GROUP
-  </refname>
-  <refpurpose>
-   add users to a group or remove users from a group
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-01-14</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-ALTER GROUP <replaceable class="PARAMETER">name</replaceable> ADD USER <replaceable class="PARAMETER">username</replaceable> [, ... ]
-ALTER GROUP <replaceable class="PARAMETER">name</replaceable> DROP USER <replaceable class="PARAMETER">username</replaceable> [, ... ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-ALTERGROUP-1">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of the group to modify.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">username</replaceable></term>
-      <listitem>
-       <para>
-        Users which are to be added or removed from the group. The user
-        names must exist.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-    
-  <refsect2 id="R2-SQL-ALTERGROUP-2">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>ALTER GROUP</computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the alteration was successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-ALTERGROUP-1">
-  <refsect1info>
-   <date>2000-01-14</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>ALTER GROUP</command> is used to add or remove users from a
-   group. Only database superusers can use this command.
-   Adding a user to a group does not create the user. Similarly, removing
-   a user from a group does not drop the user itself.
-  </para>
-  <para>
-   Use <xref linkend="SQL-CREATEGROUP" endterm="SQL-CREATEGROUP-title">
-   to create a new group and <xref linkend="SQL-DROPGROUP"
-   endterm="SQL-DROPGROUP-title"> to remove a group.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-ALTERGROUP-2">
-  <title>
-   Usage
-  </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 id="R1-SQL-ALTERGROUP-3">
-  <title>
-   Compatibility
-  </title>
-    
-  <refsect2 id="R2-SQL-ALTERGROUP-4">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>ALTER GROUP</command> statement in
-    <acronym>SQL92</acronym>. The concept of roles is
-    similar.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
deleted file mode 100644
index 4966eb757b8..00000000000
--- a/doc/src/sgml/ref/alter_table.sgml
+++ /dev/null
@@ -1,497 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.45 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTABLE">
- <refmeta>
-  <refentrytitle id="sql-altertable-title">ALTER TABLE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   ALTER TABLE
-  </refname>
-  <refpurpose>
-   change the definition of a table
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ * ]
-    ADD [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> <replaceable class="PARAMETER">type</replaceable> [ <replaceable class="PARAMETER">column_constraint</replaceable> [ ... ] ]
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ * ]
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> { SET DEFAULT <replaceable class="PARAMETER">value</replaceable> | DROP DEFAULT }
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ * ]
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> { SET | DROP } NOT NULL
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ * ]
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> SET STATISTICS <replaceable class="PARAMETER">integer</replaceable>
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ * ]
-    ALTER [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> SET STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN }
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ * ]
-    RENAME [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> TO <replaceable
-    class="PARAMETER">new_column</replaceable>
-ALTER TABLE <replaceable class="PARAMETER">table</replaceable>
-    RENAME TO <replaceable class="PARAMETER">new_table</replaceable>
-ALTER TABLE <replaceable class="PARAMETER">table</replaceable>
-    ADD <replaceable class="PARAMETER">table_constraint_definition</replaceable>
-ALTER TABLE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> 
-	DROP CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> { RESTRICT | CASCADE }
-ALTER TABLE <replaceable class="PARAMETER">table</replaceable>
-	OWNER TO <replaceable class="PARAMETER">new_owner</replaceable> 
-  </synopsis>
-
-  <refsect2 id="R2-SQL-ALTERTABLE-1">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER"> table </replaceable></term>
-      <listitem>
-       <para>
-	The name (possibly schema-qualified) of an existing 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"> type </replaceable></term>
-      <listitem>
-       <para>
-	Type of the new 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_table </replaceable></term>
-      <listitem>
-       <para>
-	New name for the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER"> table_constraint_definition </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><replaceable class="PARAMETER">new_owner </replaceable></term>
-      <listitem>
-       <para>
-	The user name of the new owner of the table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-ALTERTABLE-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>ALTER TABLE</computeroutput></term>
-      <listitem>
-       <para>
-	Message returned from column or table renaming.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>ERROR</computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if table or column is not available.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-ALTERTABLE-1">
-  <refsect1info>
-   <date>1998-04-15</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>ALTER TABLE</command> changes the definition of an existing table.
-   There are several sub-forms:
-  </para>
-
-  <variablelist>
-
-   <varlistentry>
-    <term>ADD COLUMN</term>
-    <listitem>
-     <para>
-      This form adds a new column to the table using the same syntax as
-      <xref linkend="SQL-CREATETABLE" endterm="SQL-CREATETABLE-TITLE">.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SET/DROP DEFAULT</term>
-    <listitem>
-     <para>
-      These forms set or remove the default value for a column. Note
-      that defaults only apply to subsequent <command>INSERT</command>
-      commands; they do not cause rows already in the table to change.
-      Defaults may also be created for views, in which case they are
-      inserted into <command>INSERT</> statements on the view before
-      the view's ON INSERT rule is applied.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SET/DROP NOT NULL</term>
-    <listitem>
-     <para>
-      These forms change whether a column is marked to allow NULL
-      values or to reject NULL values.  You may only <literal>SET NOT NULL</>
-      when the table contains no NULLs in the column.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SET STATISTICS</term>
-    <listitem>
-     <para>
-      This form
-      sets the per-column statistics-gathering target for subsequent
-      <xref linkend="sql-analyze" endterm="sql-analyze-title"> operations.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SET STORAGE</term>
-    <listitem>
-     <para>
-      This form sets the storage mode for a column. This controls whether this
-      column is held inline or in a supplementary table, and whether the data
-      should be compressed or not. <literal>PLAIN</literal> must be used
-      for fixed-length values such as <literal>INTEGER</literal> 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 all
-      datatypes that support it.  The use of <literal>EXTERNAL</literal> will
-      make substring operations on a TEXT column faster, at the penalty of
-      increased storage space.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>RENAME</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>ADD <replaceable class="PARAMETER">table_constraint_definition</replaceable></term>
-    <listitem>
-     <para>
-      This form adds a new constraint to a table using the same syntax as
-      <xref linkend="SQL-CREATETABLE" endterm="SQL-CREATETABLE-TITLE">. 
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>DROP CONSTRAINT</term>
-    <listitem>
-     <para>
-      This form drops constraints on a table (and its children).
-      Currently, constraints on tables are not required to have unique
-      names, so there may be more than one constraint matching the specified
-      name.  All such constraints will be dropped.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>OWNER</term>
-    <listitem>
-     <para>
-      This form changes the owner of the table, index, sequence or view to the
-      specified user.
-     </para>
-    </listitem>
-   </varlistentry>
-
-  </variablelist>
-
-  <para>
-   You must own the table to use <command>ALTER TABLE</>; except for
-   <command>ALTER TABLE OWNER</>, which may only be executed by a superuser.
-  </para>
-
-  <refsect2 id="R2-SQL-ALTERTABLE-3">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Notes
-</title>
-   <para>
-    The keyword <literal>COLUMN</literal> is noise and can be omitted.
-   </para>
-
-   <para>
-    In the current implementation of <literal>ADD COLUMN</literal>,
-    default and NOT NULL clauses for the new column are not supported.
-    The new column always comes into being with all values NULL.
-    You can use the <literal>SET DEFAULT</literal> form
-    of <command>ALTER TABLE</command> to set the default afterwards.
-    (You may also want to update the already existing rows to the
-    new default value, using
-    <xref linkend="sql-update" endterm="sql-update-title">.)
-    If you want to mark the column non-null, use the <literal>SET NOT NULL</>
-    form after you've entered non-null values for the column in all rows.
-   </para>
-
-   <para>
-    In DROP CONSTRAINT, the RESTRICT keyword is required, although
-    dependencies are not yet checked.  The CASCADE option is unsupported.  
-    Currently DROP CONSTRAINT only handles CHECK constraints.
-    To remove a PRIMARY or UNIQUE constraint, drop the 
-    relevant index using the <xref linkend="SQL-DROPINDEX" endterm="sql-dropindex-title"> command.
-    To remove FOREIGN KEY constraints you need to recreate
-    and reload the table, using other parameters to the
-    <xref linkend="SQL-CREATETABLE" endterm="sql-createtable-title"> command.
-   </para>
-   <para>
-    For example, to drop all constraints on a table <literal>distributors</literal>:
-    <programlisting>
-CREATE TABLE temp AS SELECT * FROM distributors;
-DROP TABLE distributors;
-CREATE TABLE distributors AS SELECT * FROM temp;
-DROP TABLE temp;
-    </programlisting>
-   </para>
-
-   <para>
-    Changing any  part  of  the schema of a system
-    catalog is not permitted.
-   </para>
-
-   <para>
-    Refer to <command>CREATE TABLE</command> for a further description
-    of valid arguments.
-    The <citetitle>PostgreSQL User's Guide</citetitle> has further
-    information on inheritance.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-ALTERTABLE-2">
-  <title>
-   Usage
-  </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 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:
-   <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 RESTRICT;
-   </programlisting>
-  </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>
- </refsect1>
-
- <refsect1 id="R1-SQL-ALTERTABLE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-ALTERTABLE-4">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>SQL92</title>
-    <para>
-     The <literal>ADD COLUMN</literal> form is compliant with the exception that
-     it does not support defaults and NOT NULL constraints, as explained above.
-     The <literal>ALTER COLUMN</literal> form is in full compliance.
-    </para>
-
-    <para>
-     SQL92 specifies some additional capabilities for <command>ALTER TABLE</command>
-     statement which are not yet directly supported by <productname>PostgreSQL</productname>:
-
-    <variablelist>
-    <varlistentry>
-     <term>
-      <synopsis>
-ALTER TABLE <replaceable class="PARAMETER">table</replaceable> DROP [ COLUMN ] <replaceable class="PARAMETER">column</replaceable> { RESTRICT | CASCADE }
-      </synopsis>
-     </term>
-     <listitem>
-      <para>
-       Removes a column from a table.
-       Currently, to remove an existing column the table must be
-       recreated and reloaded:
-       <programlisting>
-CREATE TABLE temp AS SELECT did, city FROM distributors;    
-DROP TABLE distributors;
-CREATE TABLE distributors (
-    did      DECIMAL(3)  DEFAULT 1,
-    name     VARCHAR(40) NOT NULL
-);
-INSERT INTO distributors SELECT * FROM temp;
-DROP TABLE temp;
-       </programlisting>
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-   </para>
-
-   <para>
-    The clauses to rename tables, columns, indexes, and sequences are
-    <productname>PostgreSQL</productname> extensions from SQL92.
-   </para>
- 
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/alter_trigger.sgml b/doc/src/sgml/ref/alter_trigger.sgml
deleted file mode 100644
index cdfbb792c74..00000000000
--- a/doc/src/sgml/ref/alter_trigger.sgml
+++ /dev/null
@@ -1,178 +0,0 @@
-<!--
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERTRIGGER">
- <refmeta>
-  <refentrytitle id="sql-altertrigger-title">
-   ALTER TRIGGER
-  </refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   ALTER TRIGGER
-  </refname>
-  <refpurpose>
-   change the definition of a trigger
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2002-04-19</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-ALTER TRIGGER <replaceable class="PARAMETER">trigger</replaceable> ON <replaceable class="PARAMETER">table</replaceable>
-    RENAME TO <replaceable class="PARAMETER">newname</replaceable>
-  </synopsis>
-
-  <refsect2 id="R2-SQL-ALTERTRIGGER-1">
-   <refsect2info>
-    <date>2002-04-19</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER"> trigger </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"> newname </replaceable></term>
-      <listitem>
-       <para>
-	New name for the existing trigger.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-ALTERTRIGGER-2">
-   <refsect2info>
-    <date>2002-04-19</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>ALTER TRIGGER</computeroutput></term>
-      <listitem>
-       <para>
-	Message returned from trigger renaming.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>ERROR</computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if trigger is not available, or new name is a duplicate of another existing trigger on the table.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-ALTERTRIGGER-1">
-  <refsect1info>
-   <date>2002-04-19</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>ALTER TRIGGER</command> changes the definition of an existing trigger.
-   The <literal>RENAME</literal> clause causes the name of a trigger on the given table
-   to change without otherwise changing the trigger definition.
-  </para>
-
-  <para>
-   You must own the table on which the trigger acts in order to change its properties.
-  </para>
-
-  <refsect2 id="R2-SQL-ALTERTRIGGER-3">
-   <refsect2info>
-    <date>2002-04-19</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    Refer to <command>CREATE TRIGGER</command> for a further description
-    of valid arguments.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-ALTERTRIGGER-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To rename an existing trigger:
-   <programlisting>
-ALTER TRIGGER emp_stamp ON emp RENAME TO emp_track_chgs;
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-ALTERTRIGGER-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-ALTERTRIGGER-4">
-   <refsect2info>
-    <date>2002-04-19</date>
-   </refsect2info>
-   <title>SQL92</title>
-   <para>
-    The clause to rename triggers is a
-    <productname>PostgreSQL</productname> extension from SQL92.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/alter_user.sgml b/doc/src/sgml/ref/alter_user.sgml
deleted file mode 100644
index 3cc82371aa9..00000000000
--- a/doc/src/sgml/ref/alter_user.sgml
+++ /dev/null
@@ -1,280 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/alter_user.sgml,v 1.22 2002/05/17 01:19:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ALTERUSER">
- <refmeta>
-  <refentrytitle id="sql-alteruser-title">ALTER USER</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ALTER USER</refname>
-  <refpurpose>change a database user account</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-ALTER USER <replaceable class="PARAMETER">username</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-where <replaceable class="PARAMETER">option</replaceable> can be:
-
-      [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>' 
-    | CREATEDB | NOCREATEDB
-    | CREATEUSER | NOCREATEUSER 
-    | VALID UNTIL '<replaceable class="PARAMETER">abstime</replaceable>'
-
-ALTER USER <replaceable class="PARAMETER">username</replaceable> SET <replaceable>variable</replaceable> { TO | = } { <replaceable>value</replaceable> | DEFAULT }
-ALTER USER <replaceable class="PARAMETER">username</replaceable> RESET <replaceable>variable</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>ALTER USER</command> is used to change the attributes of a
-   <productname>PostgreSQL</productname> user account.  Attributes not
-   mentioned in the command retain their previous settings.
-  </para>
-
-  <para>
-   The first variant of this command in the synopsis changes certain
-   global user privileges and authentication settings.  (See below for
-   details.)  Only a database superuser can change privileges and
-   password expiration with this command.  Ordinary users can only
-   change their own password.
-  </para>
-
-  <para>
-   The second and the third variant change a user's session default for
-   a specified configuration variable.  Whenever the user 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 postmaster.
-   Ordinary users can change their own session defaults.
-   Superusers can change anyone's session defaults.
-  </para>
-
-  <refsect2>
-   <title>Parameters</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">username</replaceable></term>
-      <listitem>
-       <para>
-	The name of the user whose attributes are to be altered.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">password</replaceable></term>
-      <listitem>
-       <para>
-	The new password to be used for this account.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ENCRYPTED</literal></term>
-      <term><literal>UNENCRYPTED</literal></term>
-      <listitem>
-       <para>
-	These key words control whether the password is stored
-	encrypted in <literal>pg_shadow</>.  (See
-	<xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title">
-	for more information about this choice.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CREATEDB</literal></term>
-      <term><literal>NOCREATEDB</literal></term>
-      <listitem>
-       <para>
-	These clauses define a user's ability to create databases.  If
-	<literal>CREATEDB</literal> is specified, the user being
-	defined will be allowed to create his own databases. Using
-	<literal>NOCREATEDB</literal> will deny a user the ability to
-	create databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CREATEUSER</literal></term>
-      <term><literal>NOCREATEUSER</literal></term>
-      <listitem>
-       <para>
-	These clauses determine whether a user will be permitted to
-	create new users himself. This option will also make the user
-	a superuser who can override all access restrictions.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">abstime</replaceable></term>
-      <listitem>
-       <para>
-	The date (and, optionally, the time)
-	at which this user's password is to expire.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>variable</replaceable></term>
-      <term><replaceable>value</replaceable></term>
-      <listitem>
-       <para>
-        Set this user's session default for the specified configuration
-        variable to the given value.  If
-        <replaceable>value</replaceable> is <literal>DEFAULT</literal>
-        or, equivalently, <literal>RESET</literal> is used, the
-        user-specific variable setting is removed and the user will
-        inherit the system-wide default setting in new sessions.  Use
-        <literal>RESET ALL</literal> to clear all settings.
-       </para>
-
-       <para>
-        See <xref linkend="sql-set" endterm="sql-set-title"> and the
-        <citetitle>Administrator's Guide</citetitle> for more
-        information about allowed variable names and values.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><computeroutput>ALTER USER</computeroutput></term>
-     <listitem>
-      <para>
-       Message returned if the alteration was successful.
-      </para>
-     </listitem>
-    </varlistentry>
-     
-    <varlistentry>
-     <term><computeroutput>ERROR:  ALTER USER: user "username" does not exist</computeroutput></term>
-     <listitem>
-      <para>
-       Error message returned if the specified user is not known to
-       the database.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title">
-   to add new users, and <xref linkend="SQL-DROPUSER"
-   endterm="SQL-DROPUSER-title"> to remove a user.
-  </para>
-
-  <para>
-   <command>ALTER USER</command> cannot change a user's group memberships.
-   Use <xref linkend="SQL-ALTERGROUP" endterm="SQL-ALTERGROUP-title">
-   to do that.
-  </para>
-
-  <para>
-   Using <xref linkend="sql-alterdatabase"
-   endterm="sql-alterdatabase-title">, it is also possible to tie a
-   session default to a specific database rather than a user.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-  <para>
-   Change a user password:
-
-<programlisting>
-ALTER USER davide WITH PASSWORD 'hu8jmn3';
-</programlisting>
-  </para>
-
-  <para>
-   Change a user's valid until date:
-
-<programlisting>
-ALTER USER manuel VALID UNTIL 'Jan 31 2030';
-</programlisting>
-  </para>
-
-  <para>
-   Change a user's valid until date, specifying that his
-   authorization should expire at midday on 4th May 1998 using
-   the time zone which is one hour ahead of UTC:
-<programlisting>
-ALTER USER chris VALID UNTIL 'May 4 12:00:00 1998 +1';
-</programlisting>
-  </para>
-
-  <para>
-   Give a user the ability to create other users and new databases:
-
-<programlisting>
-ALTER USER miriam CREATEUSER CREATEDB;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-    
-  <para>
-   The <command>ALTER USER</command> statement is a
-   <productname>PostgreSQL</productname> extension.  The SQL standard
-   leaves the definition of users to the implementation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createuser" endterm="sql-createuser-title"></member>
-   <member><xref linkend="sql-dropuser" endterm="sql-dropuser-title"></member>
-   <member><xref linkend="sql-set" endterm="sql-set-title"></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/analyze.sgml b/doc/src/sgml/ref/analyze.sgml
deleted file mode 100644
index 5fbef560dec..00000000000
--- a/doc/src/sgml/ref/analyze.sgml
+++ /dev/null
@@ -1,220 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/analyze.sgml,v 1.8 2002/04/23 02:07:15 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ANALYZE">
- <refmeta>
-  <refentrytitle id="sql-analyze-title">ANALYZE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   ANALYZE
-  </refname>
-  <refpurpose>
-   collect statistics about a database
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2001-05-04</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ (<replaceable class="PARAMETER">column</replaceable> [, ...] ) ] ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-ANALYZE-1">
-   <refsect2info>
-    <date>2001-05-04</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term>VERBOSE</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>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-ANALYZE-2">
-   <refsect2info>
-    <date>2001-05-04</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-<returnvalue>ANALYZE</returnvalue>
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The command is complete.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-ANALYZE-1">
-  <refsect1info>
-   <date>2001-05-04</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>ANALYZE</command> collects statistics about the contents of
-   <productname>PostgreSQL</productname> tables, and stores the results in
-   the system table <literal>pg_statistic</literal>.  Subsequently,
-   the query planner uses the 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 updated.
-  </para>
-
-  <refsect2 id="R2-SQL-ANALYZE-3">
-   <refsect2info>
-    <date>2001-05-04</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-  <para>
-   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" endterm="sql-vacuum-title">
-   and <command>ANALYZE</command> once a day during a low-usage time of day.
-  </para>
-
-  <para>
-   Unlike <command>VACUUM FULL</command>,
-   <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>
-   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 may result in small changes in the planner's
-   estimated costs shown by <command>EXPLAIN</command>.
-  </para>
-
-  <para>
-   The collected statistics 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 may 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 the <citetitle>User's
-   Guide</citetitle>.
-  </para>
-
-  <para>
-   The extent of analysis can be controlled by adjusting the per-column
-   statistics target with <command>ALTER TABLE ALTER COLUMN SET
-   STATISTICS</command> (see
-   <xref linkend="sql-altertable" endterm="sql-altertable-title">).  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 10, 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 may be useful to do that for columns that
-   are never used as part of the WHERE, GROUP BY, or 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>
-
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-ANALYZE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-ANALYZE-4">
-   <refsect2info>
-    <date>2001-05-04</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>ANALYZE</command> statement in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/begin.sgml b/doc/src/sgml/ref/begin.sgml
deleted file mode 100644
index 53899f85560..00000000000
--- a/doc/src/sgml/ref/begin.sgml
+++ /dev/null
@@ -1,229 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/begin.sgml,v 1.17 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-BEGIN">
- <refmeta>
-  <refentrytitle id="SQL-BEGIN-TITLE">BEGIN</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   BEGIN
-  </refname>
-  <refpurpose>
-   start a transaction block
-  </refpurpose>
-  
-  </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>  
-BEGIN [ WORK | TRANSACTION ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-BEGIN-1">
-   <refsect2info>
-    <date>1999-06-11</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>WORK</term>
-      <term>TRANSACTION</term>
-      <listitem>
-       <para>
-	Optional keywords. They have no effect.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-BEGIN-2">
-   <refsect2info>
-    <date>1999-06-11</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-BEGIN
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This signifies that a new transaction has been started.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  BEGIN: already a transaction in progress
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This indicates that a transaction was already in progress.
-	The current transaction is not affected.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-SQL-BEGIN-1">
-  <refsect1info>
-   <date>1999-06-11</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   By default, <productname>PostgreSQL</productname> executes transactions
-   in <firstterm>unchained mode</firstterm>
-   (also known as <quote>autocommit</quote> in other database
-   systems).
-   In other words, each user 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).
-   <command>BEGIN</command> initiates a user transaction in chained mode,
-   i.e., all user statements after <command>BEGIN</command> command will
-   be executed in a single transaction until an explicit 
-   <xref linkend="sql-commit" endterm="sql-commit-title">,
-   <xref linkend="sql-rollback" endterm="sql-rollback-title">,
-   or execution abort. Statements in chained mode are executed much faster, 
-   because transaction start/commit requires significant CPU and disk 
-   activity. Execution of multiple statements inside a transaction
-   is also required for consistency when changing several
-   related tables.
-  </para>
-
-  <para>
-   The default transaction isolation level in
-   <productname>PostgreSQL</productname>
-   is READ COMMITTED, where queries inside the transaction see only changes
-   committed before query execution. So, you have to use 
-   <command>SET TRANSACTION ISOLATION LEVEL SERIALIZABLE</command>
-   just after <command>BEGIN</command> if you need more rigorous transaction isolation. 
-   In SERIALIZABLE mode queries will see only changes committed before
-   the entire
-   transaction began (actually, before execution of the first DML statement
-   in a serializable transaction).
-  </para>
-
-  <para>
-   If the transaction is committed, <productname>PostgreSQL</productname> 
-   will ensure either that all updates are done or else that none of
-   them are done. Transactions have the standard <acronym>ACID</acronym>
-   (atomic, consistent, isolatable, and durable) property.
-  </para>
-  
-  <refsect2 id="R2-SQL-BEGIN-3">
-   <refsect2info>
-    <date>1999-06-11</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    Refer to <xref linkend="sql-lock" endterm="sql-lock-title">
-    for further information
-    about locking tables inside a transaction.
-   </para>
-   
-   <para>
-    Use <xref linkend="SQL-COMMIT" endterm="SQL-COMMIT-TITLE">
-    or
-    <xref linkend="SQL-ROLLBACK" endterm="SQL-ROLLBACK-TITLE">
-    to terminate a transaction.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-BEGIN-2">
-  <title>
-   Usage
-  </title>
-
-  <para>
-   To begin a user transaction:
-
-  <programlisting>
-BEGIN WORK;
-  </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-BEGIN-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-BEGIN-4">
-     <refsect2info>
-    <date>1999-06-11</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    <command>BEGIN</command>
-    is a <productname>PostgreSQL</productname> language extension.
-    There is no explicit <command>BEGIN</command>
-    command in <acronym>SQL92</acronym>;
-    transaction initiation is always implicit and it terminates either 
-    with a <command>COMMIT</command> or <command>ROLLBACK</command> statement.
-
-    <note>
-     <para>
-      Many relational database systems offer an autocommit feature as a
-      convenience.
-     </para>
-    </note>
-   </para>
-
-   <para>
-    Incidentally, the <literal>BEGIN</literal> keyword is used for a different
-    purpose in embedded SQL. You are advised to be careful about the transaction
-    semantics when porting database applications.
-   </para>
-
-   <para>
-    <acronym>SQL92</acronym> also requires SERIALIZABLE to be the default
-    transaction isolation level.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
- 
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/checkpoint.sgml b/doc/src/sgml/ref/checkpoint.sgml
deleted file mode 100644
index 2ac485f4c4b..00000000000
--- a/doc/src/sgml/ref/checkpoint.sgml
+++ /dev/null
@@ -1,63 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/checkpoint.sgml,v 1.6 2002/04/21 19:02:39 thomas Exp $ -->
-
-<refentry id="sql-checkpoint">
- <refmeta>
-  <refentrytitle id="sql-checkpoint-title">CHECKPOINT</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CHECKPOINT</refname>
-  <refpurpose>force a transaction log checkpoint</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-CHECKPOINT
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <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 <parameter>CHECKPOINT_SEGMENTS</parameter>
-   and <parameter>CHECKPOINT_TIMEOUT</parameter>.)
-   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 the
-   <citetitle>PostgreSQL Administrator's Guide</citetitle> for more
-   information about the WAL system.
-  </para>
-
-  <para>
-   Only superusers may call <command>CHECKPOINT</command>.  The command is
-   not intended for use during normal operation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <citetitle>PostgreSQL Administrator's Guide</citetitle>
-  </para>
- </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/src/sgml/ref/close.sgml b/doc/src/sgml/ref/close.sgml
deleted file mode 100644
index e82bb4d90ed..00000000000
--- a/doc/src/sgml/ref/close.sgml
+++ /dev/null
@@ -1,167 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/close.sgml,v 1.13 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CLOSE">
- <refmeta>
-  <refentrytitle id="SQL-CLOSE-TITLE">CLOSE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CLOSE
-  </refname>
-  <refpurpose>
-   close a cursor
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CLOSE <replaceable class="PARAMETER">cursor</replaceable>
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-CLOSE-1">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">cursor</replaceable></term>
-      <listitem>
-       <para>
-	The name of an open cursor to close.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-CLOSE-2">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CLOSE CURSOR
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the cursor is successfully closed.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  PerformPortalClose: portal "<replaceable class="PARAMETER">cursor</replaceable>" not found
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This warning is given if
-	<replaceable class="PARAMETER">cursor</replaceable> is not
-	declared or has already been closed.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CLOSE-1">
-  <refsect1info>
-   <date>1998-09-08</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <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>
-   An implicit close is executed for every open cursor when a
-   transaction is terminated by <command>COMMIT</command>
- or <command>ROLLBACK</command>.
-  </para>
-  
-  <refsect2 id="R2-SQL-CLOSE-3">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <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 <command>DECLARE</command> statement to declare a cursor.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CLOSE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Close the cursor <literal>liahona</literal>:
-  </para>
-  <programlisting>
-CLOSE liahona;
-  </programlisting>
- </refsect1>
- 
- <refsect1 id="R1-SQL-CLOSE-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-CLOSE-4">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <command>CLOSE</command> is fully compatible with SQL92.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml
deleted file mode 100644
index c8499ca0581..00000000000
--- a/doc/src/sgml/ref/cluster.sgml
+++ /dev/null
@@ -1,246 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/cluster.sgml,v 1.16 2002/04/23 02:07:15 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CLUSTER">
- <refmeta>
-  <refentrytitle id="sql-cluster-title">CLUSTER</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CLUSTER
-  </refname>
-  <refpurpose>
-   cluster a table according to an index
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CLUSTER <replaceable class="PARAMETER">indexname</replaceable> ON <replaceable class="PARAMETER">tablename</replaceable>
-  </synopsis>
-
-  <refsect2 id="R2-SQL-CLUSTER-1">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-   </para>
-   <variablelist>
-    <varlistentry>
-     <term><replaceable class="PARAMETER">indexname</replaceable></term>
-     <listitem>
-      <para>
-       The name of an index.
-      </para>
-     </listitem>
-    </varlistentry>
-    <varlistentry>
-     <term><replaceable class="PARAMETER">table</replaceable></term>
-     <listitem>
-      <para>
-       The name (possibly schema-qualified) of a table.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CLUSTER-2">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CLUSTER
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The clustering was done successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: relation &lt;<replaceable class="PARAMETER">tablerelation_number</replaceable>&gt; inherits "<replaceable class="PARAMETER">table</replaceable>"
-       </computeroutput></term>
-      <listitem>
-       <para>
-	<comment>
-	 This is not documented anywhere. It seems not to be possible to
-	 cluster a table that is inherited.
-	</comment>
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: Relation <replaceable class="PARAMETER">table</replaceable> does not exist!
-       </computeroutput></term>
-      <listitem>
-       <para>
-	<comment>
-	 The specified relation was not shown in the error message,
-	 which contained a random string instead of the relation name.
-	</comment>
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CLUSTER-1">
-  <refsect1info>
-   <date>1998-09-08</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CLUSTER</command> instructs <productname>PostgreSQL</productname> 
-   to cluster the table specified
-   by <replaceable class="parameter">table</replaceable> approximately
-   based on the index specified by
-   <replaceable class="parameter">indexname</replaceable>. The index must
-   already have been defined on 
-   <replaceable class="parameter">tablename</replaceable>.
-  </para>
-
-  <para>
-   When a table is clustered, it is physically reordered
-   based on the index information. The clustering is static.
-   In other words, as the table is updated, the changes are
-   not clustered. No attempt is made to keep new instances or
-   updated tuples clustered.  If one wishes, one can
-   re-cluster manually by issuing the command again.
-  </para>
-
-  <refsect2 id="R2-SQL-CLUSTER-3">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    The table is actually copied to a temporary table in index
-    order, then renamed back to the original name.  For this
-    reason, all grant permissions and other indexes are lost
-    when clustering is performed.
-   </para>
-
-   <para>
-    In cases where you are accessing single rows randomly
-    within a table, the actual order of the data in the heap
-    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>.
-   </para>
-
-   <para> 
-    Another place where <command>CLUSTER</command> is helpful is in
-    cases where you use an
-    index to pull out several rows from a table. 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
-    heap page for the first row that matches, all other rows
-    that match are probably already on the same heap page,
-    saving disk accesses and speeding up the query.
-   </para>
-
-   <para>
-    There are two ways to cluster data. The first is with the
-    <command>CLUSTER</command> command, which reorders the original table with
-    the ordering of the index you specify. This can be slow
-    on large tables because the rows are fetched from the heap
-    in index order, and if the heap table is unordered, the
-    entries are on random pages, so there is one disk page
-    retrieved for every row moved. <productname>PostgreSQL</productname> has a cache,
-    but the majority of a big table will not fit in the cache.
-   </para>
-
-   <para> 
-    Another way to cluster data is to use
-
-    <programlisting>
-SELECT <replaceable class="parameter">columnlist</replaceable> INTO TABLE <replaceable class="parameter">newtable</replaceable>
-     FROM <replaceable class="parameter">table</replaceable> ORDER BY <replaceable class="parameter">columnlist</replaceable>
-    </programlisting>
-
-    which uses the <productname>PostgreSQL</productname> sorting code in 
-    the ORDER BY clause to match the index, and which is much faster for
-    unordered data. You then drop the old table, use
-    <command>ALTER TABLE...RENAME</command>
-    to rename <replaceable class="parameter">newtable</replaceable> to the old name, and
-    recreate the table's indexes. The only problem is that <acronym>OID</acronym>s
-    will not be preserved. From then on, <command>CLUSTER</command> should be
-    fast because most of the heap data has already been
-    ordered, and the existing index is used.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CLUSTER-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Cluster the employees relation on the basis of its salary attribute:
-  </para>
-  <programlisting>
-CLUSTER emp_ind ON emp;
-  </programlisting>
- </refsect1>
-
- <refsect1 id="R1-SQL-CLUSTER-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-CLUSTER-4">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>CLUSTER</command> statement in SQL92.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/comment.sgml b/doc/src/sgml/ref/comment.sgml
deleted file mode 100644
index 3d4041ba8ee..00000000000
--- a/doc/src/sgml/ref/comment.sgml
+++ /dev/null
@@ -1,213 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/comment.sgml,v 1.19 2002/05/13 17:45:30 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-COMMENT">
- <refmeta>
-  <refentrytitle id="SQL-COMMENT-TITLE">COMMENT</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   COMMENT
-  </refname>
-  <refpurpose>
-   define or change the comment of an object
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-COMMENT 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>) |
-  DATABASE <replaceable class="PARAMETER">object_name</replaceable> |
-  DOMAIN <replaceable class="PARAMETER">object_name</replaceable> |
-  FUNCTION <replaceable class="PARAMETER">func_name</replaceable> (<replaceable class="PARAMETER">arg1_type</replaceable>, <replaceable class="PARAMETER">arg2_type</replaceable>, ...) |
-  INDEX <replaceable class="PARAMETER">object_name</replaceable> |
-  OPERATOR <replaceable class="PARAMETER">op</replaceable> (<replaceable class="PARAMETER">leftoperand_type</replaceable>, <replaceable class="PARAMETER">rightoperand_type</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> |
-  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>
-
-  <refsect2 id="R2-SQL-COMMENT-1">
-   <refsect2info>
-    <date>1999-10-25</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">object_name,
-      table_name.column_name, agg_name, func_name, op, rule_name, trigger_name</replaceable></term>
-      <listitem>
-       <para>
-	The name of the object to be be commented.  Names of tables,
-	aggregates, domains, functions, indexes, operators, sequences, types,
-	and views
-	may be schema-qualified.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">text</replaceable></term>
-      <listitem>
-       <para>
-	The comment to add.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-COMMENT-2">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-COMMENT
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the table is successfully commented.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-COMMENT-1">
-  <refsect1info>
-   <date>1998-10-25</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>COMMENT</command> stores a comment about a database object.
-    Comments can be
-    easily retrieved with <command>psql</command>'s
-    <command>\dd</command>, <command>\d+</command>, or <command>\l+</command>
-    commands.  Other user interfaces to retrieve comments can be built atop
-    the same built-in functions that <command>psql</command> uses, namely
-    <function>obj_description()</> and <function>col_description()</>.
-  </para>
-
-  <para>
-    To modify a comment, issue a new <command>COMMENT</> command for the
-    same object.  Only one comment string is stored for each object.
-    To remove a comment, write <literal>NULL</literal> in place of the text
-    string.
-    Comments are automatically dropped when the object is dropped.
-  </para>
-
-  <note>
-  <para>
-    There is presently no security mechanism
-    for comments: any user connected to a database can see all the comments
-    for objects in that database (although only superusers can change
-    comments for objects that they don't own).  Therefore, don't put
-    security-critical information in comments.
-  </para>
-  </note>
- </refsect1>
-
- <refsect1 id="R1-SQL-COMMENT-2">
-  <title>
-   Usage
-  </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 COLUMN my_table.my_field IS 'Employee ID number';
-COMMENT ON DATABASE my_database IS 'Development Database';
-COMMENT ON DOMAIN my_domain IS 'Email Address Domain';
-COMMENT ON FUNCTION my_function (timestamp) IS 'Returns Roman Numeral';
-COMMENT ON INDEX my_index IS 'Enforces uniqueness on employee id';
-COMMENT ON OPERATOR ^ (text, text) IS 'Performs intersection of two texts';
-COMMENT ON OPERATOR ^ (NONE, text) IS 'This is a prefix operator on text';
-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 TABLE my_schema.my_table IS 'Employee Information';
-COMMENT ON TRIGGER my_trigger ON my_table IS 'Used for R.I.';
-COMMENT ON TYPE complex IS 'Complex Number datatype';
-COMMENT ON VIEW my_view IS 'View of departmental costs';
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-COMMENT-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-COMMENT-4">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>COMMENT</command> in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/commit.sgml b/doc/src/sgml/ref/commit.sgml
deleted file mode 100644
index 77c56238ebb..00000000000
--- a/doc/src/sgml/ref/commit.sgml
+++ /dev/null
@@ -1,164 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/commit.sgml,v 1.14 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-COMMIT">
- <refmeta>
-  <refentrytitle id="SQL-COMMIT-TITLE">COMMIT</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   COMMIT
-  </refname>
-  <refpurpose>
-   commit the current transaction
-  </refpurpose>
- </refnamediv>  
-  
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-COMMIT [ WORK | TRANSACTION ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-COMMIT-1">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>WORK</term>
-      <term>TRANSACTION</term>
-      <listitem>
-       <para>
-	Optional keywords. They have no effect.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-   
-  <refsect2 id="R2-SQL-COMMIT-2">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-COMMIT
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the transaction is successfully committed.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  COMMIT: no transaction in progress
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If there is no transaction in progress.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-  
- <refsect1 id="R1-SQL-COMMIT-1">
-  <refsect1info>
-   <date>1998-09-08</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <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>
-  
-  <refsect2 id="R2-SQL-COMMIT-3">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    The keywords WORK and TRANSACTION are noise and can be omitted.
-   </para>
-
-   <para>
-    Use <xref linkend="SQL-ROLLBACK" endterm="SQL-ROLLBACK-TITLE">
-    to abort a transaction.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-COMMIT-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To make all changes permanent:
-   <programlisting>
-COMMIT WORK;
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-COMMIT-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-COMMIT-4">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <acronym>SQL92</acronym> only specifies the two forms <literal>COMMIT</literal>
-    and <literal>COMMIT WORK</literal>. Otherwise full compatibility.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
deleted file mode 100644
index 28ca264c65c..00000000000
--- a/doc/src/sgml/ref/copy.sgml
+++ /dev/null
@@ -1,703 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.32 2002/06/20 16:00:43 momjian Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-COPY">
- <refmeta>
-  <refentrytitle id="sql-copy-title">COPY</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   COPY
-  </refname>
-  <refpurpose>
-   copy data between files and tables
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-12-11</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-COPY <replaceable class="parameter">table</replaceable>
-    FROM { '<replaceable class="parameter">filename</replaceable>' | <filename>stdin</filename> }
-    [ [ WITH ] 
-          [ BINARY ] 
-          [ OIDS ]
-          [ DELIMITER [ AS ] '<replaceable class="parameter">delimiter</replaceable>' ]
-          [ NULL [ AS ] '<replaceable class="parameter">null string</replaceable>' ] ]
-COPY <replaceable class="parameter">table</replaceable>
-    TO { '<replaceable class="parameter">filename</replaceable>' | <filename>stdout</filename> }
-    [ [ WITH ] 
-          [ BINARY ]
-          [ OIDS ]
-          [ DELIMITER [ AS ] '<replaceable class="parameter">delimiter</replaceable>' ]
-          [ NULL [ AS ] '<replaceable class="parameter">null string</replaceable>' ] ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-COPY-1">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">table</replaceable></term>
-      <listitem>
-       <para>
-	The name (possibly schema-qualified) of an existing table.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">filename</replaceable></term>
-      <listitem>
-       <para>
-	The absolute Unix path name of the input or output file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><filename>stdin</filename></term>
-      <listitem>
-       <para>
-	Specifies that input comes from the client application.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><filename>stdout</filename></term>
-      <listitem>
-       <para>
-	Specifies that output goes to the client application.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>BINARY</term>
-      <listitem>
-       <para>
-	Changes the behavior of field formatting, forcing all data to be
-	stored or read in binary format rather than as text. You can not
-	specify DELIMITER or NULL in binary mode.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>OIDS</term>
-      <listitem>
-       <para>
-	Specifies copying the internal object id (OID) for each row.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">delimiter</replaceable></term>
-      <listitem>
-       <para>
-	The character that separates fields within each row (line) of the file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">null string</replaceable></term>
-      <listitem>
-       <para>
-        The string that represents a NULL value. The default is
-        <quote><literal>\N</literal></quote> (backslash-N). You might
-        prefer an empty string, for example.
-       </para>
-       <note>
-        <para>
-         On a copy in, 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 on copy out.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-COPY-2">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-COPY
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The copy completed successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: <replaceable>reason</replaceable>
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The copy failed for the reason stated in the error message.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-SQL-COPY-1">
-  <refsect1info>
-   <date>2001-01-02</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>COPY</command> moves data between
-   <productname>PostgreSQL</productname> tables and standard file-system
-   files.
-
-   <command>COPY TO</command> copies the entire 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).
-  </para>
-
-  <para>
-   <command>COPY</command> with a file name instructs the
-   <productname>PostgreSQL</productname> backend to directly read from
-   or write to a file. The file must be accessible to the backend and
-   the name must be specified from the viewpoint of the backend. When
-   <filename>stdin</filename> or <filename>stdout</filename> is
-   specified, data flows through the client frontend to the backend.
-    
-    <tip>
-     <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 backend when <command>\copy</command> is used.
-     </para>
-    </tip>
-   </para>
-
-  <refsect2 id="R2-SQL-COPY-3">
-   <refsect2info>
-    <date>2001-01-02</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-   <command>COPY</command> can only be used with plain tables, not with
-   views.
-   </para>
-
-   <para>
-    The BINARY keyword will force all data to be
-    stored/read as binary format rather than as text.  It is
-    somewhat faster than the normal copy command, but a binary copy
-    file is not portable across machine architectures.
-    </para>
-
-    <para>
-    By default, a text copy uses a tab ("\t") character as a delimiter
-    between fields. The field delimiter may be changed to any other
-    single character with the keyword DELIMITER. Characters in data
-    fields that happen to match the delimiter character will be
-    backslash quoted.
-   </para>
-   
-   <para>
-    You must have <firstterm>select privilege</firstterm> on any table
-    whose values are read by <command>COPY TO</command>, and
-    <firstterm>insert privilege</firstterm> on a table into which values
-    are being inserted by <command>COPY FROM</command>. The backend also
-    needs appropriate Unix permissions for any file read or written by
-    <command>COPY</command>.
-   </para>
-
-   <para>
-    <command>COPY FROM</command> neither invokes rules nor acts on column
-    defaults.  It does invoke triggers and check constraints.
-   </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 relation 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 may
-    amount to a considerable amount of wasted disk space if the failure
-    happened well into a large copy operation. You may wish to invoke
-    <command>VACUUM</command> to recover the wasted space.
-   </para>
-
-   <para>
-    Files named in a <command>COPY</command> command are read or written
-    directly by the backend, 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
-    by the <application>PostgreSQL</application> user (the user ID the
-    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 backend has privileges to access.
-    
-    <tip>
-     <para>
-      The
-      <application>psql</application> instruction <command>\copy</command>
-      reads or writes files on the client machine with the client's
-      permissions, so it is not restricted to superusers.
-     </para>
-    </tip>
-   </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
-    backend 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 backend's working directory (somewhere below
-    <filename>$PGDATA</filename>), not the client's working directory.
-   </para>
-  </refsect2>
- </refsect1>
- 
- <refsect1 id="R1-SQL-COPY-2">
-  <refsect1info>
-   <date>2001-01-02</date>
-  </refsect1info>
-  <title>File Formats</title>
-  <refsect2>
-   <refsect2info>
-    <date>2002-02-12</date>
-   </refsect2info>
-   <title>Text Format</title>
-   <para>
-    When <command>COPY</command> is used without the BINARY option,
-    the file read or written is a text file with one line per table row.
-    Columns (attributes) in a row are separated by the delimiter character.
-    The attribute values themselves are strings generated by the
-    output function, or acceptable to the input function, of each
-    attribute's data type.  The specified null-value string is used in
-    place of attributes that are NULL.
-   </para>
-   <para>
-    If OIDS is specified, the OID is read or written as the first column,
-    preceding the user data columns.  (An error is raised if OIDS is
-    specified for a table that does not have OIDs.)
-   </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 Unix file, since the end of file
-    serves perfectly well; but an end marker must be provided when copying
-    data to or from a client application.
-   </para>
-   <para>
-    Backslash characters (<literal>\</>) may 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 an attribute value: backslash itself,
-    newline, and the current delimiter character.
-   </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>
-     </tbody>
-    </tgroup>
-   </informaltable>
-
-    Presently, <command>COPY TO</command> will never emit an octal-digits
-    backslash sequence, but it does use the other sequences listed above
-    for those control characters.
-   </para>
-   <para>
-    Never put a backslash before a data character <literal>N</> or period
-    (<literal>.</>). Such pairs will be mistaken for the default null string
-    or the end-of-data marker, respectively.  Any other backslashed character
-    that is not mentioned in the above table will be taken to represent itself.
-   </para>
-   <para>
-    It is strongly recommended that applications generating COPY data convert
-    data newlines and carriage returns to the <literal>\n</> and
-    <literal>\r</> sequences respectively.  At present
-    (<productname>PostgreSQL</productname> 7.2 and older versions) it is
-    possible to represent a data carriage return without any special quoting,
-    and to represent a data newline by a backslash and newline.  However,
-    these representations will not be accepted by default in future releases.
-   </para>
-   <para>
-    Note that the end of each row is marked by a Unix-style newline
-    ("\n").  Presently, <command>COPY FROM</command> will not behave as
-    desired if given a file containing DOS- or Mac-style newlines.
-    This is expected to change in future releases.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <refsect2info>
-    <date>2001-01-02</date>
-   </refsect2info>
-   <title>Binary Format</title>
-   <para>
-    The file format used for <command>COPY BINARY</command> changed in
-    <application>PostgreSQL</application> v7.1. The new format consists
-    of a file header, zero or more tuples, and a file trailer.
-   </para>
-
-   <refsect3>
-    <refsect3info>
-     <date>2001-01-02</date>
-    </refsect3info>
-    <title>
-     File Header
-    </title>
-    <para>
-     The file header consists of 24 bytes of fixed fields, followed
-     by a variable-length header extension area.  The fixed fields are:
-
-    <variablelist>
-     <varlistentry>
-      <term>Signature</term>
-      <listitem>
-       <para>
-12-byte sequence <literal>PGBCOPY\n\377\r\n\0</> --- note that the null
-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 newline-translation
-filters, dropped nulls, dropped high bits, or parity changes.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Integer layout field</term>
-      <listitem>
-       <para>
-int32 constant 0x01020304 in source's byte order. Potentially, a reader
-could engage in byte-flipping of subsequent fields if the wrong byte
-order is detected here.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Flags field</term>
-      <listitem>
-       <para>
-int32 bit mask to denote important aspects of the file format. Bits are
-numbered from 0 (LSB) to 31 (MSB) --- note that this field is stored
-with source's endianness, as are all subsequent integer fields. 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 dump; if 0, not
-           </para>
-          </listitem>
-         </varlistentry>
-        </variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>Header extension area length</term>
-      <listitem>
-       <para>
-int32 length in bytes of remainder of header, not including self.  In
-the initial version this will be 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>
-    <refsect3info>
-     <date>2001-01-02</date>
-    </refsect3info>
-    <title>
-     Tuples
-    </title>
-    <para>
-Each tuple begins with an int16 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 an int16 typlen word possibly followed by field data.
-The typlen field is interpreted thus:
-
-    <variablelist>
-     <varlistentry>
-      <term>Zero</term>
-      <listitem>
-       <para>
-	Field is NULL.  No data follows.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>&gt; 0</term>
-      <listitem>
-       <para>
-        Field is a fixed-length data type.  Exactly N
-	bytes of data follow the typlen word.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-1</term>
-      <listitem>
-       <para>
-	Field is a varlena data type.  The next four
-	bytes are the varlena header, which contains
-	the total value length including itself.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>&lt; -1</term>
-      <listitem>
-       <para>
-	Reserved for future use.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-    </para>
-
-    <para>
-For non-NULL fields, the reader can check that the typlen matches the
-expected typlen for the destination column.  This provides a simple
-but very useful check that the data is as expected.
-    </para>
-
-    <para>
-There is no alignment padding or any other extra data between fields.
-Note also that the format does not distinguish whether a data type is
-pass-by-reference or pass-by-value.  Both of these provisions are
-deliberate: they might help improve portability of the files (although
-of course endianness and floating-point-format issues can still keep
-you from moving a binary file across machines).
-    </para>
-
-    <para>
-If OIDs are included in the dump, 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 typlen --- 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>
-    <refsect3info>
-     <date>2001-01-02</date>
-    </refsect3info>
-    <title>
-     File Trailer
-    </title>
-    <para>
-     The file trailer consists of an int16 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 id="R1-SQL-COPY-3">
-  <title>
-   Usage
-  </title>
-  <para>
-The following example copies a table to standard output,
- using a vertical bar (|) as the field
- delimiter:
-  </para>
-  <programlisting>
-COPY country TO <filename>stdout</filename> WITH DELIMITER '|';
-  </programlisting>
-  <para>
-   To copy data from a Unix file into a table country:
-  </para>
-  <programlisting>
-COPY country FROM '/usr1/proj/bray/sql/country_data';
-  </programlisting>
-  <para>
-   Here is a sample of data suitable for copying into a table from
-   <filename>stdin</filename> (so it has the termination sequence on the
-   last line):
-  </para>
-  <programlisting>
-AF      AFGHANISTAN
-AL      ALBANIA
-DZ      ALGERIA
-ZM      ZAMBIA
-ZW      ZIMBABWE
-\.
-  </programlisting>
-  <para>
-   Note that the white space on each line is actually a TAB.
-  </para>
-  <para>
-   The following is the same data, output in binary format on a
-   Linux/i586 machine. The data is shown after filtering through the
-   Unix utility <command>od -c</command>. The table has three fields;
-   the first is <type>char(2)</type>, the second is <type>text</type>,
-   and the third is <type>integer</type>. All the rows have a null value
-   in the third field.
-  </para>
-  <programlisting>
-0000000   P   G   B   C   O   P   Y  \n 377  \r  \n  \0 004 003 002 001
-0000020  \0  \0  \0  \0  \0  \0  \0  \0 003  \0 377 377 006  \0  \0  \0
-0000040   A   F 377 377 017  \0  \0  \0   A   F   G   H   A   N   I   S
-0000060   T   A   N  \0  \0 003  \0 377 377 006  \0  \0  \0   A   L 377
-0000100 377  \v  \0  \0  \0   A   L   B   A   N   I   A  \0  \0 003  \0
-0000120 377 377 006  \0  \0  \0   D   Z 377 377  \v  \0  \0  \0   A   L
-0000140   G   E   R   I   A  \0  \0 003  \0 377 377 006  \0  \0  \0   Z
-0000160   M 377 377  \n  \0  \0  \0   Z   A   M   B   I   A  \0  \0 003
-0000200  \0 377 377 006  \0  \0  \0   Z   W 377 377  \f  \0  \0  \0   Z
-0000220   I   M   B   A   B   W   E  \0  \0 377 377
-  </programlisting>
- </refsect1>
- 
- <refsect1 id="R1-SQL-COPY-6">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-COPY-4">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>COPY</command> statement in SQL92.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_aggregate.sgml b/doc/src/sgml/ref/create_aggregate.sgml
deleted file mode 100644
index 21c547f6b67..00000000000
--- a/doc/src/sgml/ref/create_aggregate.sgml
+++ /dev/null
@@ -1,316 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_aggregate.sgml,v 1.20 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEAGGREGATE">
- <refmeta>
-  <refentrytitle id="sql-createaggregate-title">CREATE AGGREGATE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>
-   CREATE AGGREGATE
-  </refname>
-  <refpurpose>
-   define a new aggregate function
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-07-16</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE AGGREGATE <replaceable class="PARAMETER">name</replaceable> ( BASETYPE = <replaceable class="PARAMETER">input_data_type</replaceable>,
-    SFUNC = <replaceable class="PARAMETER">sfunc</replaceable>, STYPE = <replaceable class="PARAMETER">state_type</replaceable>
-    [ , FINALFUNC = <replaceable class="PARAMETER">ffunc</replaceable> ]
-    [ , INITCOND = <replaceable class="PARAMETER">initial_condition</replaceable> ] )
-  </synopsis>
-
-  <refsect2 id="R2-SQL-CREATEAGGREGATE-1">
-   <refsect2info>
-    <date>2000-07-16</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of an aggregate function to
-	create.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">input_data_type</replaceable></term>
-      <listitem>
-       <para>
-	The input data type on which this aggregate function operates.
-	This can be specified as ANY for an aggregate that does not
-	examine its input values
-	(an example is <function>count(*)</function>).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">sfunc</replaceable></term>
-      <listitem>
-       <para>
-	The name of the state transition function
-	to be called for each input data value.
-	This is normally a function of two arguments, the first being of
-	type <replaceable class="PARAMETER">state_type</replaceable>
-	and the second of
-	type <replaceable class="PARAMETER">input_data_type</replaceable>.
-	Alternatively, for an aggregate that does not examine its input
-	values, the function takes just one argument of
-	type <replaceable class="PARAMETER">state_type</replaceable>.
-	In either case the function must return a value of
-	type <replaceable class="PARAMETER">state_type</replaceable>.
-	This function takes the current state value and the current
-	input data item, and returns the next state value.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">state_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>
-       <para>
-	The name of the final function called to compute the aggregate's
-	result after all input data has been traversed.  The function
-	must take a single argument of type
-	<replaceable class="PARAMETER">state_type</replaceable>.
-	The output 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 output type is
-	<replaceable class="PARAMETER">state_type</replaceable>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">initial_condition</replaceable></term>
-      <listitem>
-       <para>
-	The initial setting for the state value.  This must be a literal
-	constant in the form accepted for the data type
-	<replaceable class="PARAMETER">state_type</replaceable>.
-	If not specified, the state value starts out NULL.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATEAGGREGATE-2">
-   <refsect2info>
-    <date>1998-09-09</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE AGGREGATE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the command completes successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATEAGGREGATE-1">
-  <refsect1info>
-   <date>2000-07-16</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CREATE AGGREGATE</command> 
-   allows a user or programmer to extend <productname>PostgreSQL</productname>
-   functionality by defining new aggregate functions. Some aggregate functions
-   for base types such as <function>min(integer)</function>
-   and <function>avg(double precision)</function> are already provided in the base
-   distribution. 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 (the one
-   at the front of the search path; see <literal>CURRENT_SCHEMA()</>).
-  </para>
-  <para>
-   An  aggregate  function is identified by its name and input data type.
-   Two aggregates in the same schema can have the same name if they operate on
-   different input types.  The
-   name and input data type 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>
-   An  aggregate function is made from one or two ordinary
-   functions:
-   a state transition function
-   <replaceable class="PARAMETER">sfunc</replaceable>,
-   and an optional final calculation function
-   <replaceable class="PARAMETER">ffunc</replaceable>.
-   These are used as follows:
-   <programlisting>
-<replaceable class="PARAMETER">sfunc</replaceable>( internal-state, next-data-item ) ---> next-internal-state
-<replaceable class="PARAMETER">ffunc</replaceable>( internal-state ) ---> aggregate-value
-   </programlisting>
-  </para>
-  <para>
-   <productname>PostgreSQL</productname> creates a temporary variable
-   of data type <replaceable class="PARAMETER">stype</replaceable>
-   to hold the current internal state of the aggregate.  At each input
-   data item,
-   the state transition function is invoked to calculate a new
-   internal state value.  After all the data has been processed,
-   the final function is invoked once to calculate the aggregate's output
-   value.  If there is no final function then the ending state value
-   is returned as-is.
-  </para>
-  
-  <para>
-   An aggregate function may provide an initial condition,
-   that is, an initial value for the internal state value.
-   This is specified and stored in the database as a field of type
-   <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>
-  
-  <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.  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 the first
-   non-NULL input value replaces the state value, and the transition
-   function is invoked beginning with the second non-NULL input value.
-   This is handy for implementing aggregates like <function>max</function>.
-   Note that this behavior is only available when
-   <replaceable class="PARAMETER">state_type</replaceable>
-   is the same as
-   <replaceable class="PARAMETER">input_data_type</replaceable>.
-   When these types are different, you must supply a non-NULL initial
-   condition or use a non-strict transition function.
-  </para>
-  
-  <para>
-   If the state transition function is not strict, then it will be called
-   unconditionally at each input value, 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 NULLs.
-  </para>
-  
-  <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 output automatically.  (Of course this is just the normal
-   behavior of strict functions.)  In any case the final function has
-   the option of returning NULL.  For example, the final function for
-   <function>avg</function> returns NULL when it sees there were zero
-   input tuples.
-  </para>
-  
-  <refsect2 id="R2-SQL-CREATEAGGREGATE-3">
-   <refsect2info>
-    <date>2000-07-16</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    Use <command>DROP AGGREGATE</command>
-    to drop aggregate functions.
-   </para>
-
-   <para>
-    The parameters of <command>CREATE AGGREGATE</command> can be written
-    in any order, not just the order illustrated above.
-   </para>
-
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATEAGGREGATE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Refer to the chapter on aggregate functions
-   in the <citetitle>PostgreSQL Programmer's Guide</citetitle> for
-   complete examples of usage.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATEAGGREGATE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-CREATEAGGREGATE-4">
-   <refsect2info>
-    <date>1998-09-09</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <command>CREATE AGGREGATE</command> 
-    is a <productname>PostgreSQL</productname> language extension.
-    There is no <command>CREATE AGGREGATE</command> in SQL92.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_constraint.sgml b/doc/src/sgml/ref/create_constraint.sgml
deleted file mode 100644
index 0e86c93f01e..00000000000
--- a/doc/src/sgml/ref/create_constraint.sgml
+++ /dev/null
@@ -1,149 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_constraint.sgml,v 1.8 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATECONSTRAINT">
- <refmeta>
-  <refentrytitle id="sql-createconstraint-title">CREATE CONSTRAINT TRIGGER</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE CONSTRAINT TRIGGER
-  </refname>
-  <refpurpose>
-   define a new constraint trigger
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-04-13</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE CONSTRAINT TRIGGER <replaceable class="parameter">name</replaceable>
-    AFTER <replaceable class="parameter">events</replaceable> ON
-    <replaceable class="parameter">relation</replaceable> <replaceable class="parameter">constraint</replaceable> <replaceable class="parameter">attributes</replaceable>
-    FOR EACH ROW EXECUTE PROCEDURE <replaceable class="parameter">func</replaceable> '(' <replaceable class="parameter">args</replaceable> ')'
-  </synopsis>
-
-  <refsect2 id="R2-SQL-CREATECONSTRAINT-1">
-   <title>
-    Inputs
-   </title>
-   <para>
-		
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of the constraint trigger.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">events</replaceable></term>
-      <listitem>
-       <para>
-	The event categories for which this trigger should be fired.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">relation</replaceable></term>
-      <listitem>
-       <para>
-	The name (possibly schema-qualified) of the relation in which
-	the triggering events occur.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">constraint</replaceable></term>
-      <listitem>
-       <para>
-	Actual constraint specification.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">attributes</replaceable></term>
-      <listitem>
-       <para>
-	Constraint attributes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">func</replaceable>(<replaceable class="PARAMETER">args</replaceable>)</term>
-      <listitem>
-       <para>
-	Function to call as part of the trigger processing.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATECONSTRAINT-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-    
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE TRIGGER
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if successful.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATECONSTRAINT-1">
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CREATE CONSTRAINT TRIGGER</command> is used within
-   <command>CREATE/ALTER TABLE</command> and by
-   <application>pg_dump</application>  to  create  the  special  triggers  for
-   referential  integrity.
-  </para>
-
-  <para>
-   It is not intended for general use.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_database.sgml b/doc/src/sgml/ref/create_database.sgml
deleted file mode 100644
index b7879c3a0bb..00000000000
--- a/doc/src/sgml/ref/create_database.sgml
+++ /dev/null
@@ -1,368 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_database.sgml,v 1.28 2002/06/17 05:40:32 momjian Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEDATABASE">
- <refmeta>
-  <refentrytitle id="sql-createdatabase-title">CREATE DATABASE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE DATABASE
-  </refname>
-  <refpurpose>
-   create a new database
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-12-11</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
-    [ [ WITH ] [ OWNER [=] <replaceable class="parameter">dbowner</replaceable> ]
-           [ LOCATION [=] '<replaceable class="parameter">dbpath</replaceable>' ]
-           [ TEMPLATE [=] <replaceable class="parameter">template</replaceable> ]
-           [ ENCODING [=] <replaceable class="parameter">encoding</replaceable> ] ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-CREATEDATABASE-1">
-   <refsect2info>
-    <date>1999-12-11</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <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">dbowner</replaceable></term>
-      <listitem>
-       <para>
-        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">dbpath</replaceable></term>
-      <listitem>
-       <para>
-	An alternate file-system location in which to store the new database,
-	specified as a string literal;
-	or <literal>DEFAULT</literal> to use the default location.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">template</replaceable></term>
-      <listitem>
-       <para>
-        Name of 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>
-        Multibyte encoding method to use in the new database.  Specify
-	a string literal name (e.g., <literal>'SQL_ASCII'</literal>),
-	or an integer encoding number, or <literal>DEFAULT</literal>
-	to use the default encoding.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATEDATABASE-2">
-   <refsect2info>
-    <date>1999-12-11</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>CREATE DATABASE</computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the command completes successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>ERROR:  user '<replaceable class="parameter">username</replaceable>' is not allowed to create/drop databases</computeroutput></term>
-      <listitem>
-       <para>
-        You must have the special CREATEDB privilege to create databases.
-        See <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><computeroutput>ERROR:  createdb: database "<replaceable class="parameter">name</replaceable>" already exists</computeroutput></term>
-      <listitem>
-       <para>
-	This occurs if a database with the <replaceable class="parameter">name</replaceable>
-        specified already exists.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>ERROR:  database path may not contain single quotes</computeroutput></term>
-      <listitem>
-       <para>
-	The database location
-        <replaceable class="parameter">dbpath</replaceable> cannot contain
-        single quotes. This is required so that the shell commands that
-        create the database directory can execute safely.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>ERROR:  CREATE DATABASE: may not be called in a transaction block</computeroutput></term>
-      <listitem>
-       <para>
-        If you have an explicit transaction block in progress you cannot call
-        <command>CREATE DATABASE</command>. You must finish the transaction first.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>ERROR:  Unable to create database directory '<replaceable>path</replaceable>'.</computeroutput></term>
-      <term><computeroutput>ERROR:  Could not initialize database directory.</computeroutput></term>
-      <listitem>
-       <para>
-        These are most likely related to insufficient permissions on the data
-        directory, a full disk, or other file system problems. The user under
-        which the database server is running must have access to the location.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATEDATABASE-1">
-  <refsect1info>
-   <date>1999-12-11</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CREATE DATABASE</command> creates a new
-   <productname>PostgreSQL</productname> database.
-  </para>
-
-  <para>
-   Normally, the creator becomes the owner of the new database.
-   Superusers can create databases owned by other users using the
-   <option>OWNER</> clause. They can even create databases owned by
-   users with no special privileges. Non-superusers with CREATEDB
-   privilege can only create databases owned by themselves.
-  </para>
-
-  <para>
-   An alternate location can be specified in order to,
-   for example, store the database on a different disk.
-   The path must have been prepared with the 
-   <xref linkend="APP-INITLOCATION" endterm="APP-INITLOCATION-title">
-   command.
-  </para>
-  <para>
-   If the path name does not contain a slash, it is interpreted
-   as an environment variable name, which must be known to the
-   server process. This way the database administrator can
-   exercise control over locations in which databases can be created.
-   (A customary choice is, e.g., <envar>PGDATA2</envar>.)
-   If the server is compiled with <literal>ALLOW_ABSOLUTE_DBPATHS</literal>
-   (not so by default), absolute path names, as identified by
-   a leading slash
-   (e.g., <filename>/usr/local/pgsql/data</filename>),
-   are allowed as well.
-  </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>.  In particular,
-   by writing <literal>TEMPLATE = template0</>, you can create a virgin
-   database containing only the standard objects predefined by your
-   version of <application>PostgreSQL</application>.  This is useful
-   if you wish to avoid copying
-   any installation-local objects that may have been added to
-   <literal>template1</>. 
-  </para>
-
-  <para>
-   The optional encoding parameter allows selection of the database encoding,
-   if your server was compiled with multibyte encoding support.  When not
-   specified, it defaults to the encoding used by the selected template
-   database.
-  </para>
-
-  <para>
-   Optional parameters can be written in any order, not only the order
-   illustrated above.
-  </para>
-
-  <refsect2 id="R2-SQL-CREATEDATABASE-3">
-   <refsect2info>
-    <date>1999-12-11</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    <command>CREATE DATABASE</command> is a <productname>PostgreSQL</productname>
-    language extension.
-   </para>
-   <para>
-    Use <xref linkend="SQL-DROPDATABASE" endterm="SQL-DROPDATABASE-title"> to remove a database.
-   </para>
-   <para>
-    The program <xref linkend="APP-CREATEDB" endterm="APP-CREATEDB-title"> is a
-    shell script wrapper around this command, provided for convenience.
-   </para>
-
-   <para>
-    There are security and data integrity issues
-    involved with using alternate database locations
-    specified with absolute path names, and by default
-    only an environment variable known to the backend may be
-    specified for an alternate location.
-    See the Administrator's Guide for more information.
-   </para>
-
-<!--
-comment from Olly; response from Thomas...
-  <comment>
-   initlocation does not create a PG_VERSION file in the specified location.
-   How will PostgreSQL handle the situation if it is upgraded to an 
-   incompatible database version?
-  </comment>
-   Hmm. This isn't an issue since the upgrade would do
-   a dump/reload from the main database area also.
-   Not sure if the dump/reload would guarantee that
-   the alternate data area gets refreshed though...
--->
-
-  <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 COPY DATABASE facility.
-   We recommend that databases used as templates be treated as read-only.
-   See the <citetitle>Administrator's Guide</> for more information.
-  </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATEDATABASE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To create a new database:
-
-   <programlisting>
-<prompt>olly=></prompt> <userinput>create database lusiadas;</userinput>
-   </programlisting>
-  </para>
-
-  <para>
-   To create a new database in an alternate area <filename>~/private_db</filename>:
-
-   <programlisting>
-<prompt>$</prompt> <userinput>mkdir private_db</userinput>
-<prompt>$</prompt> <userinput>initlocation ~/private_db</userinput>
-    <computeroutput>
-The location will be initialized with username "olly".
-This user will own all the files and must also own the server process.
-Creating directory /home/olly/private_db
-Creating directory /home/olly/private_db/base
-
-initlocation is complete.
-    </computeroutput>
-   
-<prompt>$</prompt> <userinput>psql olly</userinput>
-<computeroutput>
-Welcome to psql, the PostgreSQL interactive terminal.
- 
-Type:  \copyright for distribution terms
-       \h for help with SQL commands
-       \? for help on internal slash commands
-       \g or terminate with semicolon to execute query
-       \q to quit
-
-<prompt>olly=></prompt></computeroutput> <userinput>CREATE DATABASE elsewhere WITH LOCATION = '/home/olly/private_db';</userinput>
-<computeroutput>CREATE DATABASE</computeroutput>
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATEDATABASE-4">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-CREATEDATABASE-4">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>CREATE DATABASE</command> statement in SQL92.
-    Databases are equivalent to catalogs, whose creation is
-    implementation-defined.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_domain.sgml b/doc/src/sgml/ref/create_domain.sgml
deleted file mode 100644
index 6a8401a62b3..00000000000
--- a/doc/src/sgml/ref/create_domain.sgml
+++ /dev/null
@@ -1,242 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.5 2002/04/23 02:07:15 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEDOMAIN">
- <refmeta>
-  <refentrytitle id="sql-createdomian-title">
-   CREATE DOMAIN
-  </refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE DOMAIN
-  </refname>
-  <refpurpose>
-   define a new domain
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2002-02-24</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE DOMAIN <replaceable class="parameter">domainname</replaceable> [AS] <replaceable class="parameter">data_type</replaceable>
-    [ DEFAULT <replaceable>default_expr</> ]
-    [ <replaceable class="PARAMETER">constraint</replaceable> [, ... ] ]
-
-where <replaceable class="PARAMETER">constraint</replaceable> is:
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ NOT NULL | NULL }
-  </synopsis>
-
-  <refsect2 id="R2-SQL-CREATEDOMAIN-1">
-   <refsect2info>
-    <date>2002-02-24</date>
-   </refsect2info>
-   <title>
-    Parameters
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">domainname</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 may include array
-	specifiers.
-        Refer to the <citetitle>User's Guide</citetitle> for further
-        information about data types and arrays.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>DEFAULT
-      <replaceable>default_expr</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 subselects are not allowed).
-	The
-        data type of the default expression must match the data type of the
-        domain.
-       </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 domain, then the default is NULL.
-       </para>
-
-       <note>
-        <para>
-         If a default value is specified 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>
-       </note>
-      </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 not allowed to be NULL.  This is
-        equivalent to the column constraint <literal>CHECK (<replaceable
-        class="PARAMETER">column</replaceable> NOT NULL)</literal>.
-       </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 available for compatibility with
-        non-standard SQL databases.  Its use is discouraged in new
-        applications.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATEDOMAIN-2">
-   <refsect2info>
-    <date>2002-02-24</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE DOMAIN
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the domain is successfully created.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATEDOMAIN-1">
-  <refsect1info>
-   <date>2002-02-24</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>CREATE DOMAIN</command>  allows  the user to register a new
-   data domain with <productname>PostgreSQL</> for use in the
-   current data base.   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 one
-   at the front of the search path; see <literal>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 fields between tables into
-   a single location for maintenance.  An email address column may be used
-   in several tables, all with the same properties.  Define a domain and
-   use that rather than setting up each table's constraints individually.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-  <para>
-   This example creates the <type>country_code</type> data type and then uses the
-   type in a table definition:
-<programlisting>
-CREATE DOMAIN country_code char(2) NOT NULL;
-CREATE TABLE countrylist (id INT4, country country_code);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATEDOMAIN-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   SQL99 defines CREATE DOMAIN, but says that the only allowed constraint
-   type is CHECK constraints.  CHECK constraints for domains are not yet
-   supported by <productname>PostgreSQL</productname>.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATEDOMAIN-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-dropdomain"></member>
-   <member><citetitle>PostgreSQL Programmer's Guide</citetitle></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml
deleted file mode 100644
index b2d2314a733..00000000000
--- a/doc/src/sgml/ref/create_function.sgml
+++ /dev/null
@@ -1,570 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.39 2002/05/18 13:47:59 petere Exp $
--->
-
-<refentry id="SQL-CREATEFUNCTION">
- <refmeta>
-  <refentrytitle id="SQL-CREATEFUNCTION-TITLE">CREATE FUNCTION</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE FUNCTION</refname>
-  <refpurpose>define a new function</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ OR REPLACE ] FUNCTION <replaceable class="parameter">name</replaceable> ( [ <replaceable class="parameter">argtype</replaceable> [, ...] ] )
-    RETURNS <replaceable class="parameter">rettype</replaceable>
-  { LANGUAGE <replaceable class="parameter">langname</replaceable>
-    | IMMUTABLE | STABLE | VOLATILE
-    | CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT
-    | IMPLICIT CAST
-    | [EXTERNAL] SECURITY INVOKER | [EXTERNAL] SECURITY DEFINER
-    | 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>
-
-  <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.
-  </para>
-
-  <para>
-   The user that creates the function becomes the owner of the function.
-  </para>
-
-   <variablelist>
-    <title>Parameters</title>
-
-    <varlistentry>
-     <term><replaceable class="parameter">name</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of a function to create.  If a schema name is included,
-       then the function is created in the
-       specified schema.  Otherwise it is created in the current schema (the
-       one at the front of the search path; see <literal>CURRENT_SCHEMA()</>).
-       The name of the new function must not match any existing function
-       with the same argument types in the same schema.  However, functions of
-       different argument types may share a name (this is called
-       <firstterm>overloading</>).
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">argtype</replaceable></term>
-
-     <listitem>
-      <para>
-       The data type(s) of the function's arguments, if any.  The
-       input types may be base or complex types,
-       <literal>opaque</literal>, or the same as the type of an
-       existing column.  <literal>Opaque</literal> indicates
-       that the function accepts arguments of a non-SQL type such as
-       <type>char *</type>.
-	The type of a column is indicated using <replaceable
-	class="parameter">tablename</replaceable>.<replaceable
-	class="parameter">columnname</replaceable><literal>%TYPE</literal>;
-	using this can sometimes help make a function independent from
-	changes to the definition of a table.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">rettype</replaceable></term>
-
-     <listitem>
-      <para>
-       The return data type.  The return type may be specified as a
-       base type, complex type, <literal>setof</literal> type,
-       <literal>opaque</literal>, or the same as the type of an
-       existing column.
-       The <literal>setof</literal>
-       modifier indicates that the function will return a set of
-       items, rather than a single item.  Functions with a declared
-       return type of <literal>opaque</literal> do not return a value.
-       These cannot be called directly; trigger functions make use of
-       this feature.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">langname</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the language that the function is implemented in.
-       May be <literal>SQL</literal>, <literal>C</literal>,
-       <literal>internal</literal>, or the name of a user-defined
-       procedural language.  (See also <xref linkend="app-createlang"
-       endterm="app-createlang-title">.)  For backward compatibility,
-       the name may be enclosed by single quotes.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>IMMUTABLE</term>
-     <term>STABLE</term>
-     <term>VOLATILE</term>
-
-     <listitem>
-      <para>
-       These attributes inform the system whether it is safe to
-       replace multiple evaluations of the function with a single
-       evaluation, for run-time optimization.  At most one choice
-       should be specified.  If none of these appear,
-       <literal>VOLATILE</literal> is the default assumption.
-      </para>
-
-      <para>
-       <literal>IMMUTABLE</literal> indicates that the function 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 parameter 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 within a single table scan
-       the function 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.  Also note
-       that the <literal>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()</>.  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>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>CALLED ON NULL INPUT</term>
-     <term>RETURNS NULL ON NULL INPUT</term>
-     <term>STRICT</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 NULLs 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>IMPLICIT CAST</literal</term>
-
-     <listitem>
-      <para>
-       Indicates that the function may be used for implicit type
-       conversions.  See <xref linkend="sql-createfunction-cast-functions"
-       endterm="sql-createfunction-cast-functions-title"> for more detail.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   <varlistentry>
-    <term><optional>EXTERNAL</optional> SECURITY INVOKER</term>
-    <term><optional>EXTERNAL</optional> SECURITY DEFINER</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 present for SQL
-      compatibility but is optional since, unlike in SQL, this feature
-      does not only apply to external functions.
-     </para>
-    </listitem>
-   </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">definition</replaceable></term>
-
-     <listitem>
-      <para>
-       A string defining the function; the meaning depends on the
-       language.  It may be an internal function name, the path to an
-       object file, an SQL query, or text in a procedural language.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><replaceable class="parameter">obj_file</replaceable>, <replaceable class="parameter">link_symbol</replaceable></term>
-
-     <listitem>
-      <para>
-       This form of the <literal>AS</literal> clause is used for
-       dynamically linked 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
-       object's link symbol, that is, the name of the function in the C
-       language source code.
-      </para>
-     </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 may appear here:
-
-      <variablelist>
-       <varlistentry>
-        <term>isStrict</term>
-        <listitem>
-         <para>
-          Equivalent to <literal>STRICT</literal> or <literal>RETURNS NULL ON NULL INPUT</literal>
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term>isImmutable</term>
-        <term>isCachable</term>
-        <term>isStable</term>
-        <term>isVolatile</term>
-        <listitem>
-         <para>
-          Equivalent to <literal>IMMUTABLE</literal>,
-          <literal>STABLE</literal>, <literal>VOLATILE</literal>.
-          <literal>isCachable</literal> is an obsolete equivalent of
-          <literal>isImmutable</literal>; it's still accepted for
-          backwards-compatibility reasons.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term>implicitCoercion</term>
-        <listitem>
-         <para>
-          Same as <literal>IMPLICIT CAST</literal>
-         </para>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-
-      Attribute names are not case-sensitive.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   </variablelist>
-
- </refsect1>
-
- <refsect1 id="sql-createfunction-notes">
-  <title>Notes</title>
-
-   <para>
-    Refer to the chapter in the
-    <citetitle>PostgreSQL Programmer's Guide</citetitle>
-    on the topic of extending
-    <productname>PostgreSQL</productname> via functions 
-    for further information on writing external functions.
-   </para>
-
-   <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>numeric</type> types) 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>
-    <productname>PostgreSQL</productname> allows function <firstterm>overloading</firstterm>;
-    that is, the same name can be used for several different functions
-    so long as they have distinct argument types.  This facility must
-    be used with caution for internal and C-language functions, however.    
-   </para>
-
-   <para>
-    Two <literal>internal</literal>
-    functions cannot have the same C name without causing
-    errors at link time.  To get around that, give them different C names
-    (for example, use the argument types as part of the C names), then
-    specify those names in the AS clause of <command>CREATE FUNCTION</command>.
-    If the AS clause is left empty, then <command>CREATE FUNCTION</command>
-    assumes the C name of the function is the same as the SQL name.
-   </para>
-
-   <para>
-    Similarly, when overloading SQL function names with multiple C-language
-    functions, give
-    each C-language instance of the function a distinct name, then use
-    the alternative form of the <command>AS</command> clause in the
-    <command>CREATE FUNCTION</command> syntax to select the appropriate
-    C-language implementation of each overloaded SQL function.
-   </para>
-
-   <para>
-    When repeated <command>CREATE FUNCTION</command> calls refer to
-    the same object file, the file is only loaded once.  To unload and
-    reload the file (perhaps during development), use the <xref
-    linkend="sql-load" endterm="sql-load-title"> command.
-   </para>
-
-   <para>
-    Use <command>DROP FUNCTION</command>
-    to remove user-defined functions.
-   </para>
-
-   <para>
-    To update the definition of an existing function, use
-    <command>CREATE OR REPLACE FUNCTION</command>.  Note that it is
-    not possible to change the name or argument types of a function
-    this way (if you tried, you'd just 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 re-create the function.
-   </para>
-
-   <para>
-    If you drop and then re-create a function, the new function is not
-    the same entity as the old; you will break existing rules, views,
-    triggers, etc that referred to the old function.  Use 
-    <command>CREATE OR REPLACE FUNCTION</command> to change a function
-    definition without breaking objects that refer to the function.
-   </para>
-
-  <para>
-   To be able to define a function, the user must have the
-   <literal>USAGE</literal> privilege on the language.
-  </para>
-
-  <para>
-   By default, only the owner (creator) of the function has the right
-   to execute it.  Other users must be granted the
-   <literal>EXECUTE</literal> privilege on the function to be able to
-   use it.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createfunction-cast-functions">
-  <title id="sql-createfunction-cast-functions-title">
-   Type Cast Functions
-  </title>
-  <para>
-   A function that has one argument and is named the same as its return
-   data type (including the schema name) is considered to be a <firstterm>type
-   casting function</>: it can be invoked to convert a value of its input
-   data type into a value 
-   of its output datatype.  For example,
-<programlisting>
-SELECT CAST(42 AS text);
-</programlisting>
-   converts the integer constant 42 to text by invoking a function
-   <literal>text(int4)</>, if such a function exists and returns type
-   text.  (If no suitable conversion function can be found, the cast fails.)
-  </para>
-
-  <para>
-   If a potential cast function is marked <literal>IMPLICIT CAST</>,
-   then it can be invoked implicitly in any context where the
-   conversion it defines is required.  Cast functions not so marked
-   can be invoked only by explicit <literal>CAST</>,
-   <replaceable>x</><literal>::</><replaceable>typename</>, or
-   <replaceable>typename</>(<replaceable>x</>) constructs.  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 <literal>text(int4)</> is marked
-   <literal>IMPLICIT CAST</>, otherwise not.
-  </para>
-
-  <para>
-   It is wise to be conservative about marking cast functions as
-   implicit casts.  An overabundance of implicit casting paths can
-   cause <productname>PostgreSQL</productname> to choose surprising
-   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 cast implicitly invokable only for
-   information-preserving transformations between types in the same
-   general type category.  For example, <type>int2</type> to
-   <type>int4</type> casts can reasonably be implicit, but be wary of
-   marking <type>int4</type> to <type>text</type> or
-   <type>float8</type> to <type>int4</type> as implicit casts.
-  </para>
- </refsect1>
-  
- <refsect1 id="sql-createfunction-examples">
-  <title>Examples</title>
-
-  <para>
-   To create a simple SQL function:
-
-<programlisting>
-CREATE FUNCTION one() RETURNS integer
-    AS 'SELECT 1 AS RESULT;'
-    LANGUAGE SQL;
-
-SELECT one() AS answer;
-<computeroutput>
- answer 
---------
-      1
-</computeroutput>
-</programlisting>
-  </para>
-
-  <para>
-   The next example creates a C function by calling a routine from a
-   user-created shared library named <filename>funcs.so</> (the extension
-   may vary across platforms).  The shared library file is sought in the
-   server's dynamic library search path.  This particular routine calculates
-   a check digit and returns true if the check digit in the function
-   parameters is correct.  It is intended for use in a CHECK
-   constraint.
-
-<programlisting>
-CREATE FUNCTION ean_checkdigit(char, char) RETURNS boolean
-    AS 'funcs' LANGUAGE C;
-    
-CREATE TABLE product (
-    id        char(8) PRIMARY KEY,
-    eanprefix char(8) CHECK (eanprefix ~ '[0-9]{2}-[0-9]{5}')
-                      REFERENCES brandname(ean_prefix),
-    eancode   char(6) CHECK (eancode ~ '[0-9]{6}'),
-    CONSTRAINT ean    CHECK (ean_checkdigit(eanprefix, eancode))
-);
-</programlisting>
-  </para>
-
-  <para>
-   The next example creates a function that does type conversion from the
-   user-defined type complex to the built-in type point.  The
-   function is implemented by a dynamically loaded object that was
-   compiled from C source (we illustrate the now-deprecated alternative
-   of specifying the absolute file name to the shared object file).
-   For <productname>PostgreSQL</productname> to
-   find a type conversion function automatically, the SQL function has
-   to have the same name as the return type, and so overloading is
-   unavoidable.  The function name is overloaded by using the second
-   form of the <command>AS</command> clause in the SQL definition:
-
-<programlisting>
-CREATE FUNCTION point(complex) RETURNS point
-    AS '/home/bernie/pgsql/lib/complex.so', 'complex_to_point'
-    LANGUAGE C STRICT;
-</programlisting>
-
-  The C declaration of the function could be:
-
-<programlisting>
-Point * complex_to_point (Complex *z)
-{
-	Point *p;
-
-	p = (Point *) palloc(sizeof(Point));
-	p->x = z->x;
-	p->y = z->y;
-		
-	return p;
-}
-</programlisting>
-
-   Note that the function is marked <quote>strict</>; this allows us
-   to skip checking for NULL input in the function body.
-  </para>    
- </refsect1>
-
- 
- <refsect1 id="sql-createfunction-compat">
-  <title>Compatibility</title>
-
-  <para>
-   A <command>CREATE FUNCTION</command> command is defined in SQL99.
-   The <application>PostgreSQL</application> version is similar but
-   not fully compatible.  The attributes are not portable, neither are the
-   different available languages.
-  </para>
- </refsect1>
-
-
- <refsect1 id="sql-createfunction-seealso">
-  <title>See Also</title>
-
-  <para>
-   <xref linkend="sql-dropfunction" endterm="sql-dropfunction-title">,
-   <xref linkend="sql-grant" endterm="sql-grant-title">,
-   <xref linkend="sql-load" endterm="sql-load-title">,
-   <xref linkend="sql-revoke" endterm="sql-revoke-title">,
-   <xref linkend="app-createlang">,
-   <citetitle>PostgreSQL Programmer's Guide</citetitle>
-  </para>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_group.sgml b/doc/src/sgml/ref/create_group.sgml
deleted file mode 100644
index 7992756cb48..00000000000
--- a/doc/src/sgml/ref/create_group.sgml
+++ /dev/null
@@ -1,176 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_group.sgml,v 1.8 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEGROUP">
- <refmeta>
-  <refentrytitle id="sql-creategroup-title">CREATE GROUP</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE GROUP
-  </refname>
-  <refpurpose>
-   define a new user group
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-01-14</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE GROUP <replaceable class="PARAMETER">name</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-where <replaceable class="PARAMETER">option</replaceable> can be:
-
-     SYSID <replaceable class="PARAMETER">gid</replaceable>
-   | USER  <replaceable class="PARAMETER">username</replaceable> [, ...]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-CREATEGROUP-1">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of the group.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">gid</replaceable></term>
-      <listitem>
-       <para>
-        The <literal>SYSID</literal> clause can be used to choose
-        the <productname>PostgreSQL</productname> group id of the new
-        group. It is not necessary to do so, however.
-       </para>
-       <para>
-        If this is not specified, the highest assigned group id plus one,
-        starting at 1, will be used as default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-        A list of users to include in the group. The users must already exist.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-CREATEGROUP-2">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>CREATE GROUP</computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the command completes successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATEGROUP-1">
-  <refsect1info>
-   <date>2000-01-14</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   CREATE GROUP will create a new group in the database installation.
-   Refer to the <citetitle>Administrator's Guide</citetitle> for information about using groups
-   for authentication.
-   You must be a database superuser to use this command.
-  </para>
-  <para>
-   Use <xref linkend="SQL-ALTERGROUP" endterm="SQL-ALTERGROUP-title">
-   to change a group's membership, and <xref linkend="SQL-DROPGROUP"
-   endterm="SQL-DROPGROUP-title"> to remove a group.
-  </para>  
- </refsect1> 
- <refsect1 id="R1-SQL-CREATEGROUP-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Create an empty group:
-<programlisting>
-CREATE GROUP staff;
-</programlisting>
-  </para>
-
-  <para>
-   Create a group with members:
-<programlisting>
-CREATE GROUP marketing WITH USER jonathan, david;
-</programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-CREATEGROUP-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-CREATEGROUP-4">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    There is no <command>CREATE GROUP</command> statement in SQL92.
-    Roles are similar in concept to groups.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
deleted file mode 100644
index a3af001006a..00000000000
--- a/doc/src/sgml/ref/create_index.sgml
+++ /dev/null
@@ -1,458 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.31 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEINDEX">
- <refmeta>
-  <refentrytitle id="sql-createindex-title">CREATE INDEX</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE INDEX
-  </refname>
-  <refpurpose>
-   define a new index
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2001-07-15</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable> ON <replaceable class="parameter">table</replaceable>
-    [ USING <replaceable class="parameter">acc_method</replaceable> ] ( <replaceable class="parameter">column</replaceable> [ <replaceable class="parameter">ops_name</replaceable> ] [, ...] )
-    [ WHERE <replaceable class="parameter">predicate</replaceable> ]
-CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable> ON <replaceable class="parameter">table</replaceable>
-    [ USING <replaceable class="parameter">acc_method</replaceable> ] ( <replaceable class="parameter">func_name</replaceable>( <replaceable class="parameter">column</replaceable> [, ... ]) [ <replaceable class="parameter">ops_name</replaceable> ] )
-    [ WHERE <replaceable class="parameter">predicate</replaceable> ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-CREATEINDEX-1">
-   <refsect2info>
-    <date>1998-09-09</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>UNIQUE</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><replaceable class="parameter">index_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
-	table.
-       </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">acc_method</replaceable></term>
-      <listitem>
-       <para>
-	The name of the access method to be used for the index. The
-	default access method is <literal>BTREE</literal>.
-	<application>PostgreSQL</application> provides four access
-	methods for indexes:
-
-	<variablelist>
-	 <varlistentry>
-	  <term><literal>BTREE</></term>
-	  <listitem>
-	   <para>
-	    an implementation of Lehman-Yao
-	    high-concurrency B-trees.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term><literal>RTREE</></term>
-	  <listitem>
-	   <para>implements standard R-trees using Guttman's
-	    quadratic split algorithm.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term><literal>HASH</></term>
-	  <listitem>
-	   <para>
-	    an implementation of Litwin's linear hashing.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term><literal>GIST</></term>
-	  <listitem>
-	   <para>
-	    Generalized Index Search Trees.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-	</variablelist>
-       </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">ops_name</replaceable></term>
-      <listitem>
-       <para>
-	An associated operator class. See below for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">func_name</replaceable></term>
-      <listitem>
-       <para>
-	A function, which returns a value that can be indexed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">predicate</replaceable></term>
-      <listitem>
-       <para>
-	Defines the constraint expression for a partial index.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATEINDEX-2">
-   <refsect2info>
-    <date>1998-09-09</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE INDEX
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the index is successfully created.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-ERROR: Cannot create index: 'index_name' already exists.
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This error occurs if it is impossible to create the index.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATEINDEX-1">
-  <refsect1info>
-   <date>1998-09-09</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CREATE INDEX</command> constructs an index 
-   <replaceable class="parameter">index_name</replaceable>
-   on the specified <replaceable class="parameter">table</replaceable>.
-
-   <tip>
-    <para>
-     Indexes are primarily used to enhance database performance.
-     But inappropriate use will result in slower performance.
-    </para>
-   </tip>
-  </para>
-
-  <para>
-   In the first syntax shown above, the key field(s) for the
-   index are specified as column names.
-   Multiple fields can be specified if the index access method supports
-   multicolumn indexes.
-  </para>
-
-  <para>
-   In the second syntax shown above, an index is defined on the result
-   of a user-specified function <replaceable
-   class="parameter">func_name</replaceable> applied to one or more
-   columns of a single table. These <firstterm>functional
-   indexes</firstterm> can be used to obtain fast access to data based
-   on operators that would normally require some transformation to apply
-   them to the base data. For example, a functional index on
-   <literal>upper(col)</> would allow the clause
-   <literal>WHERE upper(col) = 'JIM'</> to use an index.
-  </para>
-
-  <para>
-   <application>PostgreSQL</application> provides B-tree, R-tree, hash,
-   and GiST access methods for indexes. The B-tree access method is an
-   implementation of Lehman-Yao high-concurrency B-trees. The R-tree
-   access method implements standard R-trees using Guttman's quadratic
-   split algorithm. The hash access method is an implementation of
-   Litwin's linear hashing. We mention the algorithms used solely to
-   indicate that all of these access methods are fully dynamic and do
-   not have to be optimized periodically (as is the case with, for
-   example, static hash access methods).
-  </para>
-
-  <para>
-    When the <command>WHERE</command> 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 somehow more interesting 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 <command>WHERE</command> with
-    <command>UNIQUE</command> to enforce uniqueness over a subset of a
-    table.
-  </para>
-
-  <para>
-    The expression used in the <command>WHERE</command> clause may refer
-    only to columns of the underlying table (but it can use all columns,
-    not only the one(s) being indexed).  Presently, sub-SELECTs and
-    aggregate expressions are also forbidden in <command>WHERE</command>.
-  </para>
-
-  <para>
-   All functions and operators used in an index definition must be
-   <firstterm>immutable</>, that is, their results must depend only on
-   their input 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, remember to mark the function immutable
-   when you create it.
-  </para>
-
-  <para>
-   Use <xref linkend="sql-dropindex" endterm="sql-dropindex-title">
-   to remove an index.
-  </para>
-
-  <refsect2 id="R2-SQL-CREATEINDEX-3">
-   <refsect2info>
-    <date>1998-09-09</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    The <productname>PostgreSQL</productname>
-    query optimizer will consider using a B-tree index whenever
-    an indexed attribute is involved in a comparison using one of:
-
-    <simplelist type="inline">
-     <member>&lt;</member>
-     <member>&lt;=</member>
-     <member>=</member>
-     <member>&gt;=</member>
-     <member>&gt;</member>
-    </simplelist>
-   </para>
-
-   <para>
-    The <productname>PostgreSQL</productname>
-    query optimizer will consider using an R-tree index whenever
-    an indexed attribute is involved in a comparison using one of:
-
-    <simplelist type="inline">
-     <member>&lt;&lt;</member>
-     <member>&amp;&lt;</member>
-     <member>&amp;&gt;</member>
-     <member>&gt;&gt;</member>
-     <member>@</member>
-     <member>~=</member>
-     <member>&amp;&amp;</member>
-    </simplelist>
-   </para>
-
-   <para>
-    The <productname>PostgreSQL</productname>
-    query optimizer will consider using a hash index whenever
-    an indexed attribute is involved in a comparison using
-    the <literal>=</literal> operator.
-   </para>
-
-   <para>
-    Currently, only the B-tree and gist access methods support multicolumn
-    indexes. Up to 16 keys may be specified by default (this limit
-    can be altered when building
-    <application>PostgreSQL</application>).  Only B-tree currently 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 field'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. There are also some operator
-   classes with special purposes:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      The operator classes <literal>box_ops</literal> and
-      <literal>bigbox_ops</literal> both support R-tree indexes on the
-      <literal>box</literal> data type.
-      The difference between them is that <literal>bigbox_ops</literal>
-      scales box coordinates down, to avoid floating-point exceptions from
-      doing multiplication, addition, and subtraction on very large
-      floating-point coordinates.  (Note: this was true some time ago,
-      but currently the two operator classes both use floating point
-      and are effectively identical.)
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-   <para>
-    The following query shows all defined operator classes:
-
-    <programlisting>
-SELECT am.amname AS acc_method,
-       opc.opcname AS ops_name,
-       opr.oprname AS ops_comp
-    FROM pg_am am, pg_opclass opc, pg_amop amop, pg_operator opr
-    WHERE opc.opcamid = am.oid AND
-          amop.amopclaid = opc.oid AND
-          amop.amopopr = opr.oid
-    ORDER BY acc_method, ops_name, ops_comp;
-    </programlisting>
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATEINDEX-2">
-  <title>
-   Usage
-  </title>
-  <para>To create a B-tree index on the field <literal>title</literal>
-   in the table <literal>films</literal>:
-  </para>
-  <programlisting>
-CREATE UNIQUE INDEX title_idx
-    ON films (title);
-  </programlisting>
-
-<!--
-<comment>
-Is this example correct?
-</comment>
-  <para>
-   To create a R-tree index on a point attribute so that we
-   can efficiently use box operators on the result of the
-   conversion function:
-  </para>
-  <programlisting>
-CREATE INDEX pointloc
-    ON points USING RTREE (point2box(location) box_ops);
-SELECT * FROM points
-    WHERE point2box(points.pointloc) = boxes.box;
-  </programlisting>
--->
-
- </refsect1>
- 
- <refsect1 id="R1-SQL-CREATEINDEX-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-CREATEINDEX-4">
-   <refsect2info>
-    <date>1998-09-09</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    CREATE INDEX is a <productname>PostgreSQL</productname> language extension.
-   </para>
-   <para>
-    There is no <command>CREATE INDEX</command> command in SQL92.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_language.sgml b/doc/src/sgml/ref/create_language.sgml
deleted file mode 100644
index 1871da57e56..00000000000
--- a/doc/src/sgml/ref/create_language.sgml
+++ /dev/null
@@ -1,314 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_language.sgml,v 1.25 2002/06/20 15:44:06 momjian Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATELANGUAGE">
- <refmeta>
-  <refentrytitle id="sql-createlanguage-title">CREATE LANGUAGE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE LANGUAGE</refname>
-  <refpurpose>define a new procedural language</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ TRUSTED ] [ PROCEDURAL ] LANGUAGE <replaceable class="parameter">langname</replaceable>
-    HANDLER <replaceable class="parameter">call_handler</replaceable> [ VALIDATOR <replaceable>valfunction</replaceable> ]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-createlanguage-description">
-  <title>Description</title>
-
-  <para>
-   Using <command>CREATE LANGUAGE</command>, a
-   <productname>PostgreSQL</productname> user can register a new
-   procedural language with a <productname>PostgreSQL</productname>
-   database.  Subsequently, functions and trigger procedures can be
-   defined in this new language.  The user must have the
-   <productname>PostgreSQL</productname> superuser privilege to
-   register a new language.
-  </para>
-
-  <para>
-   <command>CREATE LANGUAGE</command> effectively associates the
-   language name with a call handler that is responsible for executing
-   functions written in the language.  Refer to the
-   <citetitle>Programmer's Guide</citetitle> for more information
-   about language call handlers.
-  </para>
-
-  <para>
-   Note that procedural languages are local to individual databases.
-   To make a language available in all databases by default, it should
-   be installed into the <literal>template1</literal> database.
-  </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 call handler for
-       the language is safe, that is, it does not offer an
-       unprivileged user any functionality to bypass access
-       restrictions. If this keyword is omitted when registering the
-       language, only users with the
-       <productname>PostgreSQL</productname> superuser privilege can
-       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">langname</replaceable></term>
-
-     <listitem>
-      <para>
-       The name of the new procedural language.  The language name is
-       case insensitive. A procedural language cannot override one of
-       the built-in languages of <productname>PostgreSQL</productname>.
-      </para>
-
-      <para>
-       For backward compatibility, the name may 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 functions.  The call
-       handler for a procedural language must be written in a compiled
-       language such as C with version 1 call convention and
-       registered with <productname>PostgreSQL</productname> as a
-       function taking no arguments and returning the
-       <type>opaque</type> type, a placeholder for unspecified or
-       undefined types.
-      </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.  The validator function must take one argument of
-       type <type>oid</type>, which will be the OID of the
-       to-be-created function, and can have any return type.  If no
-       validator function is specified, then a new function will not
-       be checked when it is created.
-      </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>elog()</function>
-       function.  The return value of the function is ignored.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
- </refsect1>
-
- <refsect1 id="sql-createlanguage-diagnostics">
-  <title>Diagnostics</title>
-
-  <msgset>
-   <msgentry>
-    <msg>
-     <msgmain>
-      <msgtext>
-<screen>
-CREATE LANGUAGE
-</screen>
-      </msgtext>
-     </msgmain>
-    </msg>
- 
-    <msgexplan>
-     <para>
-      This message is returned if the language is successfully
-      created.
-     </para>
-    </msgexplan>
-   </msgentry>
-
-   <msgentry>
-    <msg>
-     <msgmain>
-      <msgtext>
-<screen>
-ERROR:  PL handler function <replaceable class="parameter">funcname</replaceable>() doesn't exist
-</screen>
-      </msgtext>
-     </msgmain>
-    </msg>
-
-    <msgexplan>
-     <para>
-      This error is returned if the function <replaceable
-      class="parameter">funcname</replaceable>() is not found.
-     </para>
-    </msgexplan>
-   </msgentry>
-  </msgset>
- </refsect1>
-
- <refsect1 id="sql-createlanguage-notes">
-  <title>Notes</title>
-
-  <para>
-   This command normally should not be executed directly by users.
-   For the procedural languages supplied in the
-   <productname>PostgreSQL</productname> distribution, the <xref
-   linkend="app-createlang"> script should be used, which will also
-   install the correct call handler.  (<command>createlang</command>
-   will call <command>CREATE LANGUAGE</command> internally.)
-  </para>
-
-  <para>
-   Use the <xref linkend="sql-createfunction" endterm="sql-createfunction-title"> command to create a new
-   function.
-  </para>
-
-  <para>
-   Use <xref linkend="sql-droplanguage" endterm="sql-droplanguage-title">, or better yet the <xref
-   linkend="app-droplang"> script, to drop procedural languages.
-  </para>
-
-  <para>
-   The system catalog <classname>pg_language</classname> records
-   information about the currently installed procedural languages.
-
-<screen>
-        Table "pg_language"
-   Attribute   |   Type    | Modifier
----------------+-----------+----------
- lanname       | name      |
- lanispl       | boolean   |
- lanpltrusted  | boolean   |
- lanplcallfoid | oid       |
- lanvalidator  | oid       |
- lancompiler   | text      |
- lanacl        | aclitem[] |
-
-   lanname   | lanispl | lanpltrusted | lanplcallfoid | lanvalidator | lancompiler | lanacl
--------------+---------+--------------+---------------+--------------+-------------+--------
- internal    | f       | f            |             0 |         2246 | n/a         |
- c           | f       | f            |             0 |         2247 | /bin/cc     |
- sql         | f       | t            |             0 |         2248 | postgres    | {=U}
-</screen>
-  </para>
-
-  <para>
-   At present, with the exception of the permissions, the definition 
-   of a procedural language cannot be changed once it has been created.
-  </para>
-
-  <para>
-   To be able to use a procedural language, a user must be granted the
-   <literal>USAGE</literal> privilege.  The
-   <command>createlang</command> program automatically grants
-   permissions to everyone if the language is known to be trusted.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-createlanguage-examples">
-  <title>Examples</title>
-
-  <para>
-   The following two commands executed in sequence will register a new
-   procedural language and the associated call handler.
-<programlisting>
-CREATE FUNCTION plsample_call_handler () RETURNS opaque
-    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
-   <productname>PostgreSQL</productname> extension.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>History</title>
-
-  <para>
-   The <command>CREATE LANGUAGE</command> command first appeared in
-   <productname>PostgreSQL</productname> 6.3.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <simplelist type="inline">
-    <member><xref linkend="app-createlang"></member>
-    <member><xref linkend="sql-createfunction"></member>
-    <member><xref linkend="app-droplang"></member>
-    <member><xref linkend="sql-droplanguage"></member>
-    <member><xref linkend="sql-grant"></member>
-    <member><xref linkend="sql-revoke"></member>
-    <member><citetitle>PostgreSQL Programmer's Guide</citetitle></member>
-   </simplelist>
-  </para>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_operator.sgml b/doc/src/sgml/ref/create_operator.sgml
deleted file mode 100644
index 82ea44921d9..00000000000
--- a/doc/src/sgml/ref/create_operator.sgml
+++ /dev/null
@@ -1,506 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.29 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEOPERATOR">
- <refmeta>
-  <refentrytitle id="sql-createoperator-title">CREATE OPERATOR</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE OPERATOR
-  </refname>
-  <refpurpose>
-   define a new operator
-  </refpurpose>
-  </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-03-25</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE OPERATOR <replaceable>name</replaceable> ( PROCEDURE = <replaceable class="parameter">func_name</replaceable>
-     [, LEFTARG = <replaceable class="parameter">lefttype</replaceable>
-     ] [, RIGHTARG = <replaceable class="parameter">righttype</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 ]
-     [, SORT1 = <replaceable class="parameter">left_sort_op</replaceable> ] [, SORT2 = <replaceable class="parameter">right_sort_op</replaceable> ]
-     [, LTCMP = <replaceable class="parameter">less_than_op</replaceable> ] [, GTCMP = <replaceable class="parameter">greater_than_op</replaceable> ] )
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-CREATEOPERATOR-1">
-   <refsect2info>
-    <date>2000-03-25</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-	The operator to be defined. See below for allowable characters.
-	The name may be schema-qualified, for example
-	<literal>CREATE OPERATOR myschema.+ (...)</>.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">func_name</replaceable></term>
-      <listitem>
-       <para>
-	The function used to implement this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">lefttype</replaceable></term>
-      <listitem>
-       <para>
-	The type of the left-hand argument of the operator, if any.
-	This option would be omitted for a left-unary operator.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">righttype</replaceable></term>
-      <listitem>
-       <para>
-	The type of the right-hand argument of the operator, 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>HASHES</term>
-      <listitem>
-       <para>
-       Indicates this operator can support a hash join.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>MERGES</term>
-      <listitem>
-       <para>
-       Indicates this operator can support a merge join.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">left_sort_op</replaceable></term>
-      <listitem>
-       <para>
-	If this operator can support a merge join, the less-than
-	operator that sorts the left-hand data type of this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">right_sort_op</replaceable></term>
-      <listitem>
-       <para>
-	If this operator can support a merge join, the less-than
-	operator that sorts the right-hand data type of this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">less_than_op</replaceable></term>
-      <listitem>
-       <para>
-	If this operator can support a merge join, the less-than
-	operator that compares the input data types of this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">greater_than_op</replaceable></term>
-      <listitem>
-       <para>
-	If this operator can support a merge join, the greater-than
-	operator that compares the input data types of this operator.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATEOPERATOR-2">
-   <refsect2info>
-    <date>2000-03-25</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE OPERATOR
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the operator is successfully created.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATEOPERATOR-1">
-  <refsect1info>
-   <date>2000-03-25</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CREATE OPERATOR</command>  defines a new operator,
-   <replaceable class="parameter">name</replaceable>.
-   The user who defines an operator becomes its owner.
-  </para>
-  <para>
-   If a schema name is given then the operator is created in the
-   specified schema.  Otherwise it is created in the current schema (the one
-   at the front of the search path; see <literal>CURRENT_SCHEMA()</>).
-  </para>
-  <para>
-   Two operators in the same schema can have the same name if they operate on
-   different data types.  This is called <firstterm>overloading</>.  The
-   system will attempt to pick the intended operator based on the actual
-   input data types when there is ambiguity.
-  </para>
-
-  <para>
-   The operator <replaceable class="parameter">name</replaceable>
-   is a sequence of up to <symbol>NAMEDATALEN</>-1 (31 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> cannot be defined as a single-character operator,
-     although it can be part of a multicharacter operator name.
-     </para>
-    </listitem>
-    <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.
-     This restriction allows <productname>PostgreSQL</productname> to
-     parse SQL-compliant queries without requiring spaces between tokens.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   <note>
-    <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
-     <productname>PostgreSQL</productname> reads it as two operator names
-     not one.
-     </para>
-   </note>   
-  </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 LEFTARG and RIGHTARG must be defined.  For
-   binary operators, both should be defined. For right  unary
-   operators,  only  LEFTARG  should  be defined, while for left
-   unary operators only RIGHTARG should be defined.
-  </para>
-  <para>
-   The
-   <replaceable class="parameter">func_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 commutator operator should be identified if one exists,
-   so that <productname>PostgreSQL</productname> can
-   reverse the order of the operands if it wishes.
-   For example, the operator area-less-than, &lt;&lt;&lt;,
-   would probably have a commutator
-   operator, area-greater-than, &gt;&gt;&gt;.
-   Hence, the query optimizer could freely  convert:
-
-   <programlisting>
-box '((0,0), (1,1))'  &gt;&gt;&gt; MYBOXES.description
-   </programlisting>
-
-   to
-
-   <programlisting>
-MYBOXES.description &lt;&lt;&lt; box '((0,0), (1,1))'
-   </programlisting>
-  </para>
-  <para>
-   This  allows  the  execution code to always use the latter
-   representation and simplifies the  query  optimizer  somewhat.
-  </para>
-  <para>
-   Similarly, if there is a negator operator then it should be
-   identified.
-   Suppose  that  an
-   operator,  area-equal, ===, exists, as well as an area not
-   equal, !==.
-   The negator link allows the query optimizer to simplify
-   <programlisting>
-NOT MYBOXES.description === box '((0,0), (1,1))'
-   </programlisting>
-   to
-   <programlisting>
-MYBOXES.description !== box '((0,0), (1,1))'
-   </programlisting>
-  </para>
-  <para>
-   If  a  commutator  operator  name  is  supplied,  
-   <productname>PostgreSQL</productname>
-   searches  for  it  in  the catalog.  If it is found and it
-   does not yet have a commutator itself, then the commutator's
-   entry is updated to have the newly created operator as its
-   commutator.  This applies to the negator, as well.
-   This  is to allow the definition of two operators that are
-   the commutators or the negators of each other.  The  first
-   operator should be defined without a commutator or negator
-   (as appropriate).  When the second  operator  is  defined,
-   name  the  first  as the commutator or negator.  The first
-   will be updated as a side effect.  (As of
-   <application>PostgreSQL</application> <literal>6.5</literal>, 
-   it also works to just have both operators refer to each other.)
-  </para>
-  <para>
-   The HASHES, MERGES, SORT1, SORT2, LTCMP, and GTCMP options are present to
-   support the query optimizer in performing joins.
-   <productname>PostgreSQL</productname> can always evaluate a join (i.e.,
-   processing a clause with two tuple variables separated by an operator that
-   returns a <type>boolean</type>) by iterative substitution [WONG76].  In
-   addition, <productname>PostgreSQL</productname> can use a hash-join
-   algorithm along the lines of [SHAP86]; however, it must know whether this
-   strategy is applicable.  The current hash-join algorithm is only correct
-   for operators that represent equality tests; furthermore, equality of the
-   data type must mean bitwise equality of the representation of the type.
-   (For example, a data type that contains unused bits that don't matter for
-   equality tests could not be hash-joined.)  The HASHES flag indicates to the
-   query optimizer that a hash join may safely be used with this
-   operator.
-  </para>
-  <para>
-   Similarly, the MERGES flag indicates whether merge-sort is a usable join
-   strategy for this operator.  A merge join requires that the two input
-   datatypes have consistent orderings, and that the mergejoin operator
-   behave like equality with respect to that ordering.  For example, it is
-   possible to merge-join equality between an integer and a float variable by
-   sorting both inputs in ordinary 
-   numeric order.  Execution of a merge join requires that the system be
-   able to identify four operators related to the mergejoin equality operator:
-   less-than comparison for the left input datatype,
-   less-than comparison for the right input datatype,
-   less-than comparison between the two datatypes, and
-   greater-than comparison between the two datatypes.  It is possible to
-   specify these by name, as the SORT1, SORT2, LTCMP, and GTCMP options
-   respectively.  The system will fill in the default names <literal>&lt;</>,
-   <literal>&lt;</>, <literal>&lt;</>, <literal>&gt;</> respectively if
-   any of these are omitted when MERGES is specified.  Also, MERGES will
-   be assumed to be implied if any of these four operator options appear.
-  </para>
-  <para>
-   If  other join strategies are found to be practical,
-   <productname>PostgreSQL</productname>
-   will change the optimizer and run-time system to  use
-   them  and  will  require  additional specification when an
-   operator is defined.  Fortunately, the research  community
-   invents  new  join  strategies infrequently, and the added
-   generality of user-defined join strategies was not felt to
-   be worth the complexity involved.
-  </para>
-  <para>
-   The RESTRICT and JOIN options assist the query optimizer in estimating
-   result sizes.  If a clause of the form:
-   <programlisting>
-MYBOXES.description &lt;&lt;&lt; box '((0,0), (1,1))'
-   </programlisting>
-   is present in the qualification,
-   then <productname>PostgreSQL</productname> may have to
-   estimate the fraction of the  instances  in  MYBOXES  that
-   satisfy  the clause.  The function
-   <replaceable class="parameter">res_proc</replaceable>
-   must be a registered function (meaning  it  is  already  defined  using
-   <command>CREATE FUNCTION</command>) which accepts arguments of the correct
-   data types and returns a floating-point number.   The
-   query  optimizer  simply  calls this function, passing the
-   parameter <literal>((0,0), (1,1))</literal> and multiplies the result by the relation
-   size to get the expected number of instances.
-  </para>
-  <para>
-   Similarly, when the operands of the operator both  contain
-   instance  variables, the query optimizer must estimate the
-   size of the resulting join.  The function  join_proc  will
-   return  another floating-point number which will be multiplied
-   by the cardinalities of the two tables involved  to
-   compute the expected result size.
-  </para>
-  <para>
-   The difference between the function
-   <programlisting>
-my_procedure_1 (MYBOXES.description, box '((0,0), (1,1))')
-   </programlisting>
-   and the operator
-   <programlisting>
-MYBOXES.description === box '((0,0), (1,1))'
-   </programlisting>
-   is  that  <productname>PostgreSQL</productname>
-   attempts to optimize operators and can
-   decide to use an index to restrict the search  space  when
-   operators  are  involved.  However, there is no attempt to
-   optimize functions, and they are performed by brute force.
-   Moreover, functions can have any number of arguments while
-   operators are restricted to one or two.
-  </para>
-  
-  <refsect2 id="R2-SQL-CREATEOPERATOR-3">
-   <refsect2info>
-    <date>2000-03-25</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    Refer to the chapter on operators in the
-    <citetitle>PostgreSQL User's Guide</citetitle>
-    for further information.
-    Refer to <command>DROP OPERATOR</command> to delete
-    user-defined operators from a database.
-   </para>
-  </refsect2>
- </refsect1>
-  
- <refsect1 id="R1-SQL-CREATEOPERATOR-2">
-  <title>
-   Usage
-  </title>
-  <para>The following command defines a new operator,
-   area-equality, for the BOX data type:
-  </para>
-  <programlisting>
-CREATE OPERATOR === (
-   LEFTARG = box,
-   RIGHTARG = box,
-   PROCEDURE = area_equal_procedure,
-   COMMUTATOR = ===,
-   NEGATOR = !==,
-   RESTRICT = area_restriction_procedure,
-   JOIN = area_join_procedure,
-   HASHES,
-   SORT1 = &lt;&lt;&lt;,
-   SORT2 = &lt;&lt;&lt;
-   -- Since sort operators were given, MERGES is implied.
-   -- LTCMP and GTCMP are assumed to be &lt; and &gt; respectively
-);
-  </programlisting>  
- </refsect1>
- 
- <refsect1 id="R1-SQL-CREATEOPERATOR-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-CREATEOPERATOR-4">
-   <refsect2info>
-    <date>2000-03-25</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    <command>CREATE OPERATOR</command>
-    is a <productname>PostgreSQL</productname> extension.
-    There is no <command>CREATE OPERATOR</command>
-    statement in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml
deleted file mode 100644
index 86046359b4a..00000000000
--- a/doc/src/sgml/ref/create_rule.sgml
+++ /dev/null
@@ -1,344 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_rule.sgml,v 1.36 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATERULE">
- <refmeta>
-  <refentrytitle id="sql-createrule-title">CREATE RULE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE RULE
-  </refname>
-  <refpurpose>
-   define a new rewrite rule
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2001-01-05</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE 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 [ INSTEAD ] <replaceable class="parameter">action</replaceable>
-
-where <replaceable class="PARAMETER">action</replaceable> can be:
-
-NOTHING
-|
-<replaceable class="parameter">query</replaceable>
-|
-( <replaceable class="parameter">query</replaceable> ; <replaceable class="parameter">query</replaceable> ... )
-  </synopsis>
-
-  <refsect2 id="R2-SQL-CREATERULE-1">
-   <refsect2info>
-    <date>2001-01-05</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <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.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">event</replaceable></term>
-      <listitem>
-       <para>
-	Event is one of <literal>SELECT</literal>,
-	<literal>UPDATE</literal>, <literal>DELETE</literal>
-	or <literal>INSERT</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 SQL conditional expression (returning <type>boolean</type>).  The condition expression may not
-	refer to any tables except <literal>new</literal> and
-	<literal>old</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">query</replaceable></term>
-      <listitem>
-       <para>
-        The query or queries making up the
-	<replaceable class="PARAMETER">action</replaceable>
-	can be any SQL <literal>SELECT</literal>, <literal>INSERT</literal>,
-	<literal>UPDATE</literal>, <literal>DELETE</literal>, or
-	<literal>NOTIFY</literal> statement.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    Within the <replaceable class="parameter">condition</replaceable>
-    and <replaceable class="PARAMETER">action</replaceable>, the special
-    table names <literal>new</literal> and <literal>old</literal> may be
-    used to refer to values in the referenced table.
-    <literal>new</literal> is valid in ON INSERT and ON UPDATE rules
-    to refer to the new row being inserted or updated.
-    <literal>old</literal> is valid in ON UPDATE and ON DELETE
-    rules to refer to the existing row being updated or deleted.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATERULE-2">
-   <refsect2info>
-    <date>1998-09-11</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE RULE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the rule is successfully created.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATERULE-1">
-  <refsect1info>
-   <date>1998-09-11</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   The <productname>PostgreSQL</productname> 
-   <firstterm>rule system</firstterm> allows one to define an
-   alternate action to be performed on inserts, updates, or deletions
-   from database tables. Rules are used to
-   implement table views as well.
-  </para>
-
-  <para>
-   The semantics of a rule is that at the time an individual instance (row)
-   is
-   accessed, inserted, updated, or deleted, there is an old instance (for
-   selects, updates and deletes) and a new instance (for inserts and
-   updates).  All the rules for the given event type and the given target
-   table are examined successively (in order by name).  If the
-   <replaceable class="parameter">condition</replaceable> specified in the
-   WHERE clause (if any) is true, the 
-   <replaceable class="parameter">action</replaceable> part of the rule is
-   executed.  The <replaceable class="parameter">action</replaceable> is
-   done instead of the original query if INSTEAD is specified; otherwise
-   it is done after the original query in the case of ON INSERT, or before
-   the original query in the case of ON UPDATE or ON DELETE.
-   Within both the <replaceable class="parameter">condition</replaceable>
-   and <replaceable class="parameter">action</replaceable>, values from
-   fields in the old instance and/or the new instance are substituted for
-   <literal>old.</literal><replaceable class="parameter">attribute-name</replaceable>
-   and <literal>new.</literal><replaceable class="parameter">attribute-name</replaceable>.
-  </para>
-
-  <para>
-   The <replaceable class="parameter">action</replaceable> part of the
-   rule can consist of one or more queries. To write multiple queries,
-   surround them with parentheses. Such queries will be performed in the
-   specified order. The <replaceable
-   class="parameter">action</replaceable> can also be NOTHING indicating
-   no action. Thus, a DO INSTEAD NOTHING rule suppresses the original
-   query from executing (when its condition is true); a DO NOTHING rule
-   is useless.
-  </para>
-
-  <para>
-   The <replaceable class="parameter">action</replaceable> part of the rule
-   executes with the same command and transaction identifier as the user
-   command that caused activation.
-  </para>
-
-  <para>
-   It is important to realize that a rule is really a query transformation
-   mechanism, or query macro.  The entire query is processed to convert it
-   into a series of queries that include the rule actions.  This occurs
-   before evaluation of the query starts.  So, conditional rules are
-   handled by adding the rule condition to the WHERE clause of the action(s)
-   derived from the rule.  The above description of a rule as an operation
-   that executes for each row is thus somewhat misleading.  If you actually
-   want an operation that fires independently for each physical row, you
-   probably want to use a trigger not a rule.  Rules are most useful for
-   situations that call for transforming entire queries independently of
-   the specific data being handled.
-  </para>
-  
-  <refsect2 id="R2-SQL-CREATERULE-3">
-   <refsect2info>
-    <date>2001-11-06</date>
-   </refsect2info>
-   <title>
-    Rules and Views
-   </title>
-   <para>
-    Presently, ON SELECT rules must be unconditional INSTEAD rules and must
-    have actions that consist of a single SELECT query.  Thus, an ON SELECT
-    rule effectively turns the table into a view, whose visible
-    contents are the rows returned by the rule's SELECT query rather than
-    whatever had been stored in the table (if anything).  It is considered
-    better style to write a CREATE VIEW command than to create a real table
-    and define an ON SELECT rule for it.
-   </para>
-
-   <para>
-    <xref linkend="sql-createview"> creates a dummy table (with no underlying
-    storage) and associates an ON SELECT rule with it.  The system will not
-    allow updates to the view, since it knows there is no real table there.
-    You can create the
-    illusion of an updatable view by defining ON INSERT, ON UPDATE, and
-    ON DELETE 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.
-   </para>
-
-   <para>
-    There is a catch if you try to use conditional
-    rules for view updates: there <emphasis>must</> be an unconditional
-    INSTEAD rule for each action you wish to allow on the view.  If the
-    rule is conditional, or is not INSTEAD, 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 in some cases.
-    If you want to
-    handle all the useful cases in conditional rules, you can; just add an
-    unconditional DO INSTEAD NOTHING rule to ensure that the system
-    understands it will never be called on to update the dummy table.  Then
-    make the conditional rules non-INSTEAD; in the cases where they fire,
-    they add to the default INSTEAD NOTHING action.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATERULE-4">
-   <refsect2info>
-    <date>2001-01-05</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    You must have rule definition access to a table in order
-    to define a rule on it. Use <command>GRANT</command>
-    and <command>REVOKE</command> to change permissions.
-   </para>
-
-   <para>
-    It is very important to take care to avoid circular rules.
-    For example, though each
-    of the following two rule definitions are accepted by
-    <productname>PostgreSQL</productname>, the
-    select command will cause <productname>PostgreSQL</productname> to 
-    report an error because the query cycled too many times:
-
-<programlisting>
-CREATE RULE "_RETURN" AS
-    ON SELECT TO emp
-    DO INSTEAD 
-	SELECT * FROM toyemp;
-
-CREATE RULE "_RETURN" AS
-    ON SELECT TO toyemp
-    DO INSTEAD 
-	SELECT * FROM emp;
-</programlisting>
-
-      This attempt to select from <literal>EMP</literal> will cause
-      <productname>PostgreSQL</productname> to issue an error
-      because the queries cycled too many times:
-
- <programlisting>
-SELECT * FROM emp;
-</programlisting>
-   </para>
-
-   <para>
-    Presently, if a rule contains a NOTIFY query, the NOTIFY will be executed
-    unconditionally --- that is, the NOTIFY 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 NOTIFY mytable;
-
-UPDATE mytable SET name = 'foo' WHERE id = 42;
-      </programlisting>
-    one NOTIFY event will be sent during the UPDATE, whether or not there
-    are any rows with id = 42.  This is an implementation restriction that
-    may be fixed in future releases.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATERULE-4">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-CREATERULE-5">
-   <refsect2info>
-    <date>1998-09-11</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    <command>CREATE RULE</command> statement is a <productname>PostgreSQL</productname>
-    language extension.
-    There is no <command>CREATE RULE</command> statement in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_schema.sgml b/doc/src/sgml/ref/create_schema.sgml
deleted file mode 100644
index daecc3b0d40..00000000000
--- a/doc/src/sgml/ref/create_schema.sgml
+++ /dev/null
@@ -1,240 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_schema.sgml,v 1.2 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATESCHEMA">
- <refmeta>
-  <refentrytitle id="sql-createschema-title">CREATE SCHEMA</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE SCHEMA
-  </refname>
-  <refpurpose>
-   define a new schema
-  </refpurpose>
- </refnamediv> 
- <refsynopsisdiv>
-  <synopsis>
-CREATE SCHEMA <replaceable class="parameter">schemaname</replaceable> [ AUTHORIZATION <replaceable class="parameter">username</replaceable> ] [ <replaceable class="parameter">schema_element</replaceable> [ ... ] ]
-CREATE SCHEMA AUTHORIZATION <replaceable class="parameter">username</replaceable> [ <replaceable class="parameter">schema_element</replaceable> [ ... ] ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-CREATESCHEMA-1">
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">schemaname</replaceable></term>
-      <listitem>
-       <para>
-	The name of a schema to be created.  If this is omitted, the username
-	is used as the schema name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">username</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
-	may 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</>, 
-	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>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATESCHEMA-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE SCHEMA
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the command is successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  namespace "<replaceable class="parameter">schemaname</replaceable>" already exists
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If the schema specified already exists.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATESCHEMA-1">
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CREATE SCHEMA</command> will enter 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, datatypes, functions, and operators)
-   whose names may 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).
-  </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>
-
-  <refsect2 id="R2-SQL-CREATESCHEMA-3">
-   <title>
-    Notes
-   </title>
-
-   <para>
-    To create a schema, the invoking user must have <literal>CREATE</>
-    privilege for the current database.  (Of course, superusers bypass
-    this check.)
-   </para>
-
-   <para>
-    Use <command>DROP SCHEMA</command> to remove a schema.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATESCHEMA-2">
-  <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 id="R1-SQL-CREATESCHEMA-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-CREATESCHEMA-4">
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    SQL92 allows a <literal>DEFAULT CHARACTER SET</> clause in
-    <command>CREATE SCHEMA</command>, as well as more subcommand types
-    than are presently accepted by <productname>PostgreSQL</productname>.
-   </para>
-
-   <para>
-    SQL92 specifies that the subcommands in <command>CREATE SCHEMA</command>
-    may appear in any order.  The present
-    <productname>PostgreSQL</productname> implementation does not handle all
-    cases of forward references in subcommands; it may sometimes be necessary
-    to reorder the subcommands to avoid forward references.
-   </para>
-
-   <para>
-    In SQL92, the owner of a schema always owns all objects within it.
-    <productname>PostgreSQL</productname> allows schemas to contain objects
-    owned by users other than the schema owner.  This can happen only if the
-    schema owner grants <literal>CREATE</> rights on his schema to someone
-    else.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml
deleted file mode 100644
index 3db79850c8a..00000000000
--- a/doc/src/sgml/ref/create_sequence.sgml
+++ /dev/null
@@ -1,398 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_sequence.sgml,v 1.28 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATESEQUENCE">
- <refmeta>
-  <refentrytitle id="sql-createsequence-title">CREATE SEQUENCE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE SEQUENCE
-  </refname>
-  <refpurpose>
-   define a new sequence generator
-  </refpurpose>
- </refnamediv> 
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE [ TEMPORARY | TEMP ] SEQUENCE <replaceable class="parameter">seqname</replaceable> [ INCREMENT <replaceable class="parameter">increment</replaceable> ]
-    [ MINVALUE <replaceable class="parameter">minvalue</replaceable> ] [ MAXVALUE <replaceable class="parameter">maxvalue</replaceable> ]
-    [ START <replaceable class="parameter">start</replaceable> ] [ CACHE <replaceable class="parameter">cache</replaceable> ] [ CYCLE ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-CREATESEQUENCE-1">
-   <refsect2info>
-    <date>1998-09-11</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>TEMPORARY or TEMP</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">seqname</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of a sequence to be created.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">increment</replaceable></term>
-      <listitem>
-       <para>
-	The
-	<option>INCREMENT <replaceable class="parameter">increment</replaceable></option>
-	clause is optional. A positive value will make an
-	ascending sequence, a negative one a descending sequence.
-	The default value is one (1).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">minvalue</replaceable></term>
-      <listitem>
-       <para>
-	The optional clause <option>MINVALUE
-	 <replaceable class="parameter">minvalue</replaceable></option>
-	determines the minimum value
-	a sequence can generate. The defaults are 1 and -2^63-1 for
-	ascending and descending sequences, respectively.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">maxvalue</replaceable></term>
-      <listitem>
-       <para>
-	The optional clause <option>MAXVALUE
-	 <replaceable class="parameter">maxvalue</replaceable></option>
-	determines the maximum
-	value for the sequence. The defaults are 2^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 <option>START
-	 <replaceable class="parameter">start</replaceable>
-	 clause</option> enables 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 <option>CACHE <replaceable class="parameter">cache</replaceable></option> option
-	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)
-	and this is also the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>CYCLE</term>
-      <listitem>
-       <para>
-	The optional CYCLE keyword may 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.
-	Without CYCLE, after the limit is reached <function>nextval</> calls
-	will return an error.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATESEQUENCE-2">
-   <refsect2info>
-    <date>1998-09-11</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE SEQUENCE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the command is successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  Relation '<replaceable class="parameter">seqname</replaceable>' already exists
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If the sequence specified already exists.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  DefineSequence: MINVALUE (<replaceable class="parameter">start</replaceable>) can't be >= MAXVALUE (<replaceable class="parameter">max</replaceable>)
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If the specified starting value is out of range.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  DefineSequence: START value (<replaceable class="parameter">start</replaceable>) can't be < MINVALUE (<replaceable class="parameter">min</replaceable>)
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If the specified starting value is out of range.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  DefineSequence: MINVALUE (<replaceable class="parameter">min</replaceable>) can't be >= MAXVALUE (<replaceable class="parameter">max</replaceable>)
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If the minimum and maximum values are inconsistent.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATESEQUENCE-1">
-  <refsect1info>
-   <date>1998-09-11</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CREATE SEQUENCE</command> will enter a new sequence number generator
-   into the current database. This involves creating and initializing a
-   new single-row
-   table with the name <replaceable class="parameter">seqname</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 (the one
-   at the front of the search path; see <literal>CURRENT_SCHEMA()</>).
-   TEMP sequences exist in a special schema, so a schema name may not be
-   given when creating a TEMP sequence.
-   The sequence name must be distinct from the name of any other sequence,
-   table, index, or view 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
-   the <citetitle>User's Guide</citetitle>.
-  </para>
-
-  <para>
-   Although you cannot update a sequence directly, you can use a query like
-
-   <programlisting>
-SELECT * FROM <replaceable>seqname</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 backend process.  (Of course, this value may be obsolete
-   by the time it's printed, if other processes are actively doing
-   <function>nextval</> calls.)
-  </para>
-
-  <caution>
-   <para>
-    Unexpected results may 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
-    backends.  Each backend 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 backend simply return the preallocated values without touching
-    the shared object.  So, any numbers allocated but not used within a session
-    will be lost when that session ends.  Furthermore, although multiple backends are guaranteed to
-    allocate distinct sequence values, the values may be generated out of
-    sequence when all the backends are considered.  (For example, with a <replaceable class="parameter">cache</replaceable>
-    setting of 10, backend A might reserve values 1..10 and return <function>nextval</function>=1, 
-    then
-    backend B might reserve values 11..20 and return <function>nextval</function>=11 before backend
-    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 backend,
-    whether or not it has yet been returned by <function>nextval</>.
-    Another consideration is that a <function>setval</> executed on such a sequence
-    will not be noticed by other backends until they have used up any
-    preallocated values they have cached.
-   </para>
-  </caution>
-
-  <refsect2 id="R2-SQL-CREATESEQUENCE-3">
-   <refsect2info>
-    <date>1998-09-11</date>
-   </refsect2info>
-   <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 may be no compiler support for eight-byte integers, in which case
-    sequences use regular <type>integer</> arithmetic (range
-    -2147483648 to +2147483647).
-   </para>
-
-   <para>
-    When <replaceable class="parameter">cache</replaceable> is greater than
-    one, each backend uses its own cache to store preallocated numbers.
-    Numbers that are cached but not used in the current session will be
-    lost, resulting in <quote>holes</quote> in the sequence.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATESEQUENCE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Create an ascending sequence called <literal>serial</literal>, starting at 101:
-  </para>
-  <programlisting>
-CREATE SEQUENCE serial START 101;
-  </programlisting>
-  <para>
-   Select the next number from this sequence:
-   <programlisting>
-SELECT nextval('serial');
-    
-nextval
--------
-    114
-   </programlisting>
-  </para>
-  <para>
-   Use this sequence in an INSERT:
-   <programlisting>
-INSERT INTO distributors VALUES (nextval('serial'), 'nothing');
-   </programlisting>
-  </para>
-
-  <para>
-   Update the sequence value after a COPY FROM:
-   <programlisting>
-BEGIN;
-    COPY distributors FROM 'input_file';
-    SELECT setval('serial', max(id)) FROM distributors;
-END;
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATESEQUENCE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-CREATESEQUENCE-4">
-   <refsect2info>
-    <date>1998-09-11</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    <command>CREATE SEQUENCE</command> is a <productname>PostgreSQL</productname>
-    language extension.
-    There is no <command>CREATE SEQUENCE</command> statement
-    in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
deleted file mode 100644
index 5ef7a5d6e70..00000000000
--- a/doc/src/sgml/ref/create_table.sgml
+++ /dev/null
@@ -1,904 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table.sgml,v 1.55 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETABLE">
- <refmeta>
-  <refentrytitle id="sql-createtable-title">CREATE TABLE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TABLE</refname>
-  <refpurpose>define a new table</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ [ LOCAL ] { TEMPORARY | TEMP } ] TABLE <replaceable class="PARAMETER">table_name</replaceable> (
-    { <replaceable class="PARAMETER">column_name</replaceable> <replaceable class="PARAMETER">data_type</replaceable> [ DEFAULT <replaceable>default_expr</> ] [ <replaceable class="PARAMETER">column_constraint</replaceable> [, ... ] ]
-    | <replaceable>table_constraint</replaceable> }  [, ... ]
-)
-[ INHERITS ( <replaceable>parent_table</replaceable> [, ... ] ) ]
-[ WITH OIDS | WITHOUT OIDS ]
-
-where <replaceable class="PARAMETER">column_constraint</replaceable> is:
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ NOT NULL | NULL | UNIQUE | PRIMARY KEY |
-  CHECK (<replaceable class="PARAMETER">expression</replaceable>) |
-  REFERENCES <replaceable class="PARAMETER">reftable</replaceable> [ ( <replaceable class="PARAMETER">refcolumn</replaceable> ) ] [ MATCH FULL | MATCH PARTIAL ]
-    [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ] }
-[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-
-and <replaceable class="PARAMETER">table_constraint</replaceable> is:
-
-[ CONSTRAINT <replaceable class="PARAMETER">constraint_name</replaceable> ]
-{ UNIQUE ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) |
-  PRIMARY KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) |
-  CHECK ( <replaceable class="PARAMETER">expression</replaceable> ) |
-  FOREIGN KEY ( <replaceable class="PARAMETER">column_name</replaceable> [, ... ] ) REFERENCES <replaceable class="PARAMETER">reftable</replaceable> [ ( <replaceable class="PARAMETER">refcolumn</replaceable> [, ... ] ) ]
-    [ MATCH FULL | MATCH PARTIAL ] [ ON DELETE <replaceable class="parameter">action</replaceable> ] [ ON UPDATE <replaceable class="parameter">action</replaceable> ] }
-[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
-</synopsis>
-  
- </refsynopsisdiv>
-
- <refsect1 id="SQL-CREATETABLE-description">
-  <title>Description</title>
-
-  <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 (the one
-   at the front of the search path; see <literal>CURRENT_SCHEMA()</>).
-   TEMP tables exist in a special schema, so a schema name may not be
-   given when creating a TEMP table.
-   The table name must be distinct from the name of any other table,
-   sequence, index, or view in the same schema.
-  </para>
-
-  <para>
-   <command>CREATE TABLE</command> also automatically creates a data
-   type that represents the tuple type (structure 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>
-   A table cannot have more than 1600 columns.  (In practice, the
-   effective limit is lower because of tuple-length constraints).
-  </para>
-
-  <para>
-   The optional constraint clauses specify constraints (or tests) that
-   new or updated rows must satisfy for an insert or update operation
-   to succeed.  A constraint is a named rule: an SQL object which
-   helps define valid sets of values by putting limits on the results
-   of insert, update, or delete operations performed on a table.
-  </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 if the
-   constraint only affects one column.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Parameters</title>
-
-  <variablelist>
-
-   <varlistentry>
-    <term><literal>[LOCAL] TEMPORARY</> or <literal>[LOCAL] 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.  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 <literal>LOCAL</literal> word is optional.  But see under
-      <xref linkend="sql-createtable-compatibility"
-      endterm="sql-createtable-compatibility-title">.
-     </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 may include array specifiers.
-      Refer to the <citetitle>User's Guide</citetitle> for further
-      information about data types and arrays.
-     </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 (subselects 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>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.  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 that is also inherited, the data type must
-      likewise match the inherited column(s), and the column
-      definitions are merged into one.  However, inherited and new
-      column declarations of the same name need not specify identical
-      constraints: all constraints provided from any declaration are
-      merged together and all are applied to the new table.  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>
-<!--
-     <para>
-      <application>PostgreSQL</application> automatically allows the
-     created table to inherit
-      functions on tables above it in the inheritance hierarchy; that
-      is, if we create table <literal>foo</literal> inheriting from
-      <literal>bar</literal>, then functions that accept the tuple
-      type <literal>bar</literal> can also be applied to instances of
-      <literal>foo</literal>.  (Currently, this works reliably for
-      functions on the first or only parent table, but not so well for
-      functions on additional parents.)
-     </para>
--->
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>WITH OIDS</> or <literal>WITHOUT OIDS</></term>
-    <listitem>
-     <para>
-      This optional clause specifies whether rows of the new table
-      should have OIDs (object identifiers) assigned to them.  The
-      default is to have OIDs.  (If the new table inherits from any
-      tables that have OIDs, then <literal>WITH OIDS</> is forced even
-      if the command says <literal>WITHOUT OIDS</>.)
-     </para>
-
-     <para>
-      Specifying <literal>WITHOUT OIDS</> allows the user to suppress
-      generation of OIDs for rows of a table.  This may be worthwhile
-      for large tables, since it will reduce OID consumption and
-      thereby postpone wraparound of the 32-bit OID counter.  Once the
-      counter wraps around, uniqueness of OIDs can no longer be
-      assumed, which considerably reduces their usefulness.
-     </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 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.  This is
-      equivalent to the column constraint <literal>CHECK (<replaceable
-      class="PARAMETER">column</replaceable> NOT NULL)</literal>.
-     </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 available for compatibility with
-      non-standard SQL databases.  Its use is discouraged in new
-      applications.
-     </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 a rule that a
-      group of one or more distinct columns of a table may 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>
-
-     <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
-      may contain only unique (non-duplicate), non-NULL 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
-      meta-data about the design of the schema, as a primary key
-      implies that other tables
-      may 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>
-
-     <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>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>CHECK (<replaceable class="PARAMETER">expression</replaceable>)</literal></term>
-    <listitem>
-     <para>
-      <literal>CHECK</> clauses specify integrity constraints or tests
-      which new or updated rows must satisfy for an insert or update
-      operation to succeed. Each constraint must be an expression
-      producing a Boolean result.  A condition appearing within a
-      column definition should reference that column's value only,
-      while a condition appearing as a table constraint may reference
-      multiple columns.
-     </para>
-
-     <para>
-      Currently, <literal>CHECK</literal> expressions cannot contain
-      subselects nor refer to variables other than columns of the
-      current row.
-     </para>
-
-    </listitem>
-   </varlistentry>
-
-
-   <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>
-      The <literal>REFERENCES</literal> column constraint specifies
-      that a group of one or more columns of the new table must only
-      contain values which match against values in the referenced
-      column(s) <replaceable class="parameter">refcolumn</replaceable>
-      of the referenced table <replaceable
-      class="parameter">reftable</replaceable>.  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 unique or primary
-      key constraint in the referenced table.
-     </para>
-
-     <para>
-      A value added to these columns 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 a default match type if
-      none is specified. <literal>MATCH FULL</> will not allow one
-      column of a multicolumn foreign key to be NULL unless all
-      foreign key columns are NULL. The default match type 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 do 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.  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.  This is
-          the default action.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>RESTRICT</literal></term>
-        <listitem>
-         <para>
-          Same as <literal>NO ACTION</literal>.
-         </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 values to NULL.
-         </para>
-        </listitem>
-       </varlistentry>
-
-       <varlistentry>
-        <term><literal>SET DEFAULT</literal></term>
-        <listitem>
-         <para>
-          Set the referencing column values to their default value.
-         </para>
-        </listitem>
-       </varlistentry>
-      </variablelist>
-     </para>
-     <para>
-      If primary key column is updated frequently, it may be wise to
-      add an index to the <literal>REFERENCES</literal> column so that
-      <literal>NO ACTION</literal> and <literal>CASCADE</literal>
-      actions associated with the <literal>REFERENCES</literal>
-      column can be more efficiently performed.
-     </para>
-
-    </listitem>
-   </varlistentry>
-   
-   <varlistentry>
-    <term><literal>DEFERRABLE</literal> or <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 may be postponed until the end of the transaction
-      (using the <xref linkend="sql-set-constraints" endterm="sql-set-constraints-title"> command).
-      <literal>NOT DEFERRABLE</literal> is the default.  Only foreign
-      key constraints currently accept this clause.  All other
-      constraint types are not deferrable.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><literal>INITIALLY IMMEDIATE</literal> or <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" endterm="sql-set-constraints-title"> command.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
-
-
- </refsect1>    
-
-
- <refsect1 id="SQL-CREATETABLE-diagnostics">
-  <title>Diagnostics</title>
-
-  <msgset>
-   <msgentry>
-    <msg>
-     <msgmain>
-      <msgtext>
-       <simpara><computeroutput>CREATE TABLE</computeroutput></simpara>
-      </msgtext>
-     </msgmain>
-    </msg>
-
-    <msgexplan>
-     <para>
-      Message returned if table is successfully created.
-     </para>
-    </msgexplan>
-   </msgentry>
-
-
-   <msgentry>
-    <msg>
-     <msgmain>
-      <msgtext>
-       <simpara><computeroutput>ERROR</computeroutput></simpara>
-      </msgtext>
-     </msgmain>
-    </msg>
-
-    <msgexplan>
-     <para>
-      Message returned if table creation failed.  This is usually
-      accompanied by some descriptive text, such as:
-      <computeroutput>ERROR: Relation '<replaceable
-      class="parameter">table</replaceable>' already
-      exists</computeroutput>, which occurs at run time if the table
-      specified already exists in the database.
-     </para>
-    </msgexplan>
-   </msgentry>
-  </msgset>
- </refsect1>
-
-
- <refsect1 id="SQL-CREATETABLE-notes">
-  <title>Notes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     Whenever an application makes 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.  (It is likely that future <productname>PostgreSQL</>
-     releases will use a separate OID counter for each table, so that
-     it will be <emphasis>necessary</>, not optional, to include
-     <structfield>tableoid</> to have a unique identifier
-     database-wide.)
-    </para>
-
-    <tip>
-     <para>
-      The use of <literal>WITHOUT OIDS</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>
-   </listitem>
-
-   <listitem>
-    <para>
-     <productname>PostgreSQL</productname> automatically creates an
-     index for each unique constraint and primary key constraint to
-     enforce the uniqueness.  Thus, it is not necessary to create an
-     explicit index for primary key columns.  (See <xref
-     linkend="sql-createindex" endterm="sql-createindex-title"> for more information.)
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     The SQL92 standard says that <literal>CHECK</> column constraints
-     may only refer to the column they apply to; only
-     <literal>CHECK</> table constraints may refer to multiple
-     columns.  <productname>PostgreSQL</productname> does not enforce
-     this restriction; it treats column and table check constraints
-     alike.
-    </para>
-   </listitem>
-
-   <listitem>
-    <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>
-   </listitem>
-  </itemizedlist>
- </refsect1>
-
-
- <refsect1 id="SQL-CREATETABLE-examples">
-  <title>Examples</title>
-
-  <para>
-   Create table <structname>films</> and table
-   <structname>distributors</>:
-
-<programlisting>
-CREATE TABLE films (
-    code        CHARACTER(5) CONSTRAINT firstkey PRIMARY KEY,
-    title       CHARACTER VARYING(40) NOT NULL,
-    did         DECIMAL(3) NOT NULL,
-    date_prod   DATE,
-    kind        CHAR(10),
-    len         INTERVAL HOUR TO MINUTE
-);
-</programlisting>
-
-<programlisting>
-CREATE TABLE distributors (
-     did    DECIMAL(3) PRIMARY KEY DEFAULT NEXTVAL('serial'),
-     name   VARCHAR(40) NOT NULL CHECK (name &lt;&gt; '')
-);
-</programlisting>
-  </para>
-
-  <para>
-   Create a table with a 2-dimensional array:
-
-<programlisting>
-CREATE TABLE array (
-    vector  INT[][]
-);
-</programlisting>
-  </para>
-
-  <para>
-   Define a unique table constraint for the table films.  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         DECIMAL(3),
-    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     DECIMAL(3) CHECK (did > 100),
-    name    VARCHAR(40)
-);
-</programlisting>
-  </para>
-
-  <para>
-   Define a check table constraint:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     DECIMAL(3),
-    name    VARCHAR(40)
-    CONSTRAINT con1 CHECK (did > 100 AND name &lt;&gt; '')
-);
-</programlisting>
-  </para>
- 
-  <para>
-   Define a primary key table constraint for the table
-   <structname>films</>.  Primary key table constraints can be defined
-   on one or more columns of the table.
-
-<programlisting>
-CREATE TABLE films (
-    code        CHAR(5),
-    title       VARCHAR(40),
-    did         DECIMAL(3),
-    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 notation.
-
-<programlisting>
-CREATE TABLE distributors (
-    did     DECIMAL(3),
-    name    CHAR VARYING(40),
-    PRIMARY KEY(did)
-); 
-</programlisting>
-
-<programlisting>
-CREATE TABLE distributors (
-    did     DECIMAL(3) PRIMARY KEY,
-    name    VARCHAR(40)
-);
-</programlisting>
-  </para>
-
-  <para>
-   This assigns a literal constant default value for the column
-   <literal>name</literal>, and arranges for the default value of
-   column <literal>did</literal> to be generated by selecting the next
-   value of a sequence object.  The default value of
-   <literal>modtime</literal> will 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>
-
-  <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     DECIMAL(3) 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     DECIMAL(3),
-    name    VARCHAR(40) UNIQUE
-);
-</programlisting>
-
-     The above is equivalent to the following specified as a table constraint:
-
-<programlisting>
-CREATE TABLE distributors (
-    did     DECIMAL(3),
-    name    VARCHAR(40),
-    UNIQUE(name)
-);
-</programlisting>
-  </para>
-
- </refsect1>
- 
- <refsect1 id="SQL-CREATETABLE-compatibility">
-  <title id="SQL-CREATETABLE-compatibility-title">Compatibility</title>
-
-  <para>
-   The <command>CREATE TABLE</command> conforms to SQL92 Intermediate
-   and to a subset of SQL99, with exceptions listed below and in the
-   descriptions above.
-  </para>
-
-  <refsect2>
-   <title>Temporary Tables</title>
-
-   <para>
-    In addition to the local temporary table, SQL92 also defines a
-    <literal>CREATE GLOBAL TEMPORARY TABLE</literal> statement.
-    Global temporary tables are also visible to other sessions.
-   </para>
-
-   <para>
-    For temporary tables, there is an optional <literal>ON COMMIT</literal> clause:
-<synopsis>
-CREATE { GLOBAL | LOCAL } TEMPORARY TABLE <replaceable class="parameter">table</replaceable> ( <replaceable class="parameter">...</replaceable> ) [ ON COMMIT { DELETE | PRESERVE } ROWS ] 
-</synopsis>
-
-    The <literal>ON COMMIT</literal> clause specifies whether or not
-    the temporary table should be emptied of rows whenever
-    <command>COMMIT</command> is executed. If the <literal>ON
-    COMMIT</> clause is omitted, SQL92 specifies that the default is
-    <literal>ON COMMIT DELETE ROWS</>.  However, the behavior of
-    <productname>PostgreSQL</productname> is always like <literal>ON
-    COMMIT PRESERVE ROWS</literal>.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title><literal>NULL</literal> <quote>Constraint</quote></title>
-
-   <para>
-    The <literal>NULL</> <quote>constraint</quote> (actually a
-    non-constraint) is a <productname>PostgreSQL</productname>
-    extension to SQL92 that is included for compatibility with some
-    other RDBMS (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>Assertions</title>
-
-   <para>
-    An assertion is a special type of integrity constraint and shares
-    the same namespace as other constraints. However, an assertion is
-    not necessarily dependent on one particular table as constraints
-    are, so SQL92 provides the <command>CREATE ASSERTION</command>
-    statement as an alternate method for defining a constraint:
-
-<synopsis>
-CREATE ASSERTION <replaceable>name</replaceable> CHECK ( <replaceable>condition</replaceable> )
-</synopsis>
-   </para>
-
-   <para>
-    <productname>PostgreSQL</> does not implement assertions at present.
-   </para>
-  </refsect2>
-
-<!--    
-    <para>
-     Domain constraints are defined by CREATE DOMAIN or ALTER DOMAIN
-     statements:
-    </para>
-    <para>
-     Domain constraint: 
-
-     <synopsis>
-[ CONSTRAINT <replaceable>constraint_name</replaceable> ] CHECK <replaceable>constraint</replaceable> 
-    [ {INITIALLY DEFERRED | INITIALLY IMMEDIATE} ]
-    [ [ NOT ] DEFERRABLE ]
-     </synopsis>
-    </para>
--->
-   
-  <refsect2>
-   <title>Inheritance</title>
-
-   <para>
-    Multiple inheritance via the <literal>INHERITS</literal> clause is
-    a <productname>PostgreSQL</productname> language extension.  SQL99
-    (but not SQL92) defines single inheritance using a different
-    syntax and different semantics.  SQL99-style inheritance is not
-    yet supported by <productname>PostgreSQL</productname>.
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Object IDs</title>
-
-   <para>
-    The <productname>PostgreSQL</productname> concept of OIDs is not
-    standard.
-   </para>
-  </refsect2>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-altertable"></member>
-   <member><xref linkend="sql-droptable"></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_table_as.sgml b/doc/src/sgml/ref/create_table_as.sgml
deleted file mode 100644
index d027ff506f2..00000000000
--- a/doc/src/sgml/ref/create_table_as.sgml
+++ /dev/null
@@ -1,170 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.10 2002/04/23 02:07:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETABLEAS">
- <refmeta>
-  <refentrytitle>CREATE TABLE AS</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE TABLE AS</refname>
-  <refpurpose>create a new table from the results of a query</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE [ [ LOCAL ] { TEMPORARY | TEMP } ] TABLE <replaceable>table_name</replaceable> [ (<replaceable>column_name</replaceable> [, ...] ) ]
-    AS <replaceable>query</replaceable>
-  </synopsis>
- </refsynopsisdiv>
-  
- <refsect1>
-  <refsect1info>
-   <date>2001-03-20</date>
-  </refsect1info>
-  <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>[LOCAL] TEMPORARY</> or <literal>[LOCAL] 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><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. Multiple column names can
-      be specified using a comma-delimited list of column names.  If
-      column names are not provided, they are taken from the output
-      column names of the query.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term><replaceable>query</replaceable></term>
-    <listitem>
-     <para>
-      A query statement (that is, a <command>SELECT</command>
-      command).  Refer to
-      <xref linkend="sql-select">
-      for a description of the allowed syntax.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   Refer to <xref linkend="sql-createtable"> and
-   <xref linkend="sql-select">
-   for a summary of possible output messages.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   This command is functionally equivalent 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</command> syntax.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   This command is modeled after an <productname>Oracle</productname>
-   feature.  There is no command with equivalent functionality in
-   SQL92 or SQL99.  However, a combination of <literal>CREATE
-   TABLE</literal> and <literal>INSERT ... SELECT</literal> can
-   accomplish the same thing with little more effort.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>History</title>
-
-  <para>
-   The <command>CREATE TABLE AS</command> command has been available
-   since <productname>PostgreSQL</productname> 6.3.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtable"></member>
-   <member><xref linkend="sql-createview"></member>
-   <member><xref linkend="sql-select"></member>
-   <member><xref linkend="sql-selectinto"></member>
-  </simplelist>
- </refsect1>
- 
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
deleted file mode 100644
index e9f66d95b48..00000000000
--- a/doc/src/sgml/ref/create_trigger.sgml
+++ /dev/null
@@ -1,319 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v 1.26 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETRIGGER">
- <refmeta>
-  <refentrytitle id="SQL-CREATETRIGGER-TITLE">CREATE TRIGGER</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE TRIGGER
-  </refname>
-  <refpurpose>
-   define a new trigger
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-03-25</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE TRIGGER <replaceable class="PARAMETER">name</replaceable> { BEFORE | AFTER } { <replaceable class="PARAMETER">event</replaceable> [OR ...] }
-    ON <replaceable class="PARAMETER">table</replaceable> FOR EACH { ROW | STATEMENT }
-    EXECUTE PROCEDURE <replaceable class="PARAMETER">func</replaceable> ( <replaceable class="PARAMETER">arguments</replaceable> )
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-CREATETRIGGER-1">
-   <refsect2info>
-    <date>1998-09-21</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <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.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">event</replaceable></term>
-      <listitem>
-       <para>
-	One of INSERT, DELETE or UPDATE.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">table</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of the table the trigger is for.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">func</replaceable></term>
-      <listitem>
-       <para>
-	A user-supplied function that is declared as taking no arguments
-	and returning type <literal>opaque</>.
-       </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, along with the standard trigger
-	data such as old and new tuple contents.  The arguments are literal
-	string constants.  Simple names and numeric constants may be written
-	here too, but they will all be converted to strings.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATETRIGGER-2">
-   <refsect2info>
-    <date>1998-09-21</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE TRIGGER
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message is returned if the trigger is successfully created.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-SQL-CREATETRIGGER-1">
-  <refsect1info>
-   <date>1998-09-21</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>CREATE TRIGGER</command> will enter a new trigger into the current
-   data base.  The trigger will be associated with the relation
-   <replaceable class="parameter">table</replaceable> and will execute
-   the specified function <replaceable class="parameter">func</replaceable>.
-  </para>
-
-  <para>
-   The trigger can be specified to fire either before BEFORE the
-   operation is attempted on a tuple (before constraints are checked and
-   the <command>INSERT</command>, <command>UPDATE</command> or
-   <command>DELETE</command> is attempted) or AFTER the operation has
-   been attempted (e.g., after constraints are checked and the
-   <command>INSERT</command>, <command>UPDATE</command> or
-   <command>DELETE</command> has completed). If the trigger fires before
-   the event, the trigger may skip the operation for the current tuple,
-   or change the tuple being inserted (for <command>INSERT</command> and
-   <command>UPDATE</command> operations only). If the trigger fires
-   after the event, all changes, including the last insertion, update,
-   or deletion, are <quote>visible</quote> to the trigger.
-  </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>
-  <command>SELECT</command> does not modify any rows so you can not
-  create <command>SELECT</command> triggers. Rules and views are more
-  appropriate in such cases.
-  </para>
-
-  <para>
-   Refer to the chapters on SPI and Triggers in the
-   <citetitle>PostgreSQL Programmer's Guide</citetitle>  for  more
-   information.
-  </para>
- </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>
-   As of the current release, <literal>STATEMENT</literal> triggers are not implemented.
-  </para>
-
-  <para>
-   Refer to the <xref linkend="sql-droptrigger"> command for
-   information on how to remove triggers.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATETRIGGER-2">
-  <title>Examples</title>
-
-  <para>
-   Check if the specified distributor code exists in the distributors
-   table before appending or updating a row in the table films:
-
-<programlisting>
-CREATE TRIGGER if_dist_exists
-    BEFORE INSERT OR UPDATE ON films FOR EACH ROW
-    EXECUTE PROCEDURE check_primary_key ('did', 'distributors', 'did');
-</programlisting>
-  </para>
-
-  <para>
-   Before cancelling a distributor or updating its code, remove every
-   reference to the table films:
-<programlisting>
-CREATE TRIGGER if_film_exists 
-    BEFORE DELETE OR UPDATE ON distributors FOR EACH ROW
-    EXECUTE PROCEDURE check_foreign_key (1, 'CASCADE', 'did', 'films', 'did');
-</programlisting>
-  </para>
-
-  <para>
-   The second example can also be done by using a foreign key,
-   constraint as in:
-
-<programlisting>
-CREATE TABLE distributors (
-    did      DECIMAL(3),
-    name     VARCHAR(40),
-    CONSTRAINT if_film_exists
-    FOREIGN KEY(did) REFERENCES films
-    ON UPDATE CASCADE ON DELETE CASCADE  
-);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATETRIGGER-compatibility">
-  <title>Compatibility</title>
-  
-  <variablelist>
-   <varlistentry>
-    <term>SQL92</term>
-    <listitem>
-     <para>
-      There is no <command>CREATE TRIGGER</command> statement in <acronym>SQL92</acronym>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SQL99</term>
-    <listitem>
-     <para>
-      The <command>CREATE TRIGGER</command> statement in
-      <productname>PostgreSQL</productname> implements a subset of the
-      SQL99 standard.  The following functionality is missing:
-      <itemizedlist>
-       <listitem>
-        <para>
-         SQL99 allows triggers to fire on updates to specific columns
-         (e.g., <literal>AFTER UPDATE OF col1, col2</literal>).
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         SQL99 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 has row-level
-         triggers, no statement-level triggers.
-        </para>
-       </listitem>
-
-       <listitem>
-        <para>
-         <productname>PostgreSQL</productname> only allows the
-         execution of a stored procedure for the triggered action.
-         SQL99 allows the execution of a number of other SQL commands,
-         such as <command>CREATE TABLE</command> as triggered action.
-         This limitation is not hard to work around by creating a
-         stored procedure that executes these commands.
-        </para>
-       </listitem>
-      </itemizedlist>
-     </para>
-
-     <para>
-      SQL99 specifies that multiple triggers should be fired in
-      time-of-creation order.  <productname>PostgreSQL</productname>
-      uses name order, which was judged more convenient to work with.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </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><citetitle>PostgreSQL Programmer's Guide</citetitle></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_type.sgml b/doc/src/sgml/ref/create_type.sgml
deleted file mode 100644
index 042a8fd51d6..00000000000
--- a/doc/src/sgml/ref/create_type.sgml
+++ /dev/null
@@ -1,467 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_type.sgml,v 1.29 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATETYPE">
- <refmeta>
-  <refentrytitle id="sql-createtype-title">CREATE TYPE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE TYPE
-  </refname>
-  <refpurpose>
-   define a new data type
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE TYPE <replaceable class="parameter">typename</replaceable> ( INPUT = <replaceable class="parameter">input_function</replaceable>, OUTPUT = <replaceable class="parameter">output_function</replaceable>
-      , INTERNALLENGTH = { <replaceable
-      class="parameter">internallength</replaceable> | VARIABLE }
-    [ , EXTERNALLENGTH = { <replaceable class="parameter">externallength</replaceable> | VARIABLE } ]
-    [ , DEFAULT = <replaceable class="parameter">default</replaceable> ]
-    [ , ELEMENT = <replaceable class="parameter">element</replaceable> ] [ , DELIMITER = <replaceable class="parameter">delimiter</replaceable> ]
-    [ , SEND = <replaceable class="parameter">send_function</replaceable> ] [ , RECEIVE = <replaceable class="parameter">receive_function</replaceable> ]
-    [ , PASSEDBYVALUE ]
-    [ , ALIGNMENT = <replaceable class="parameter">alignment</replaceable> ]
-    [ , STORAGE = <replaceable class="parameter">storage</replaceable> ]
-)
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-CREATETYPE-1">
-   <refsect2info>
-    <date>1998-09-21</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">typename</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of a type to be created.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">internallength</replaceable></term>
-      <listitem>
-       <para>
-	A literal value, which specifies the internal length of
-	the new type.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">externallength</replaceable></term>
-      <listitem>
-       <para>
-	A literal value, which specifies the external (displayed) length of
-	the new type.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">input_function</replaceable></term>
-      <listitem>
-       <para>
-	The name of a function, created by
-	<command>CREATE FUNCTION</command>, which
-	converts data from its external form to the type's
-	internal form.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">output_function</replaceable></term>
-      <listitem>
-       <para>
-	The name of a function, created by
-	<command>CREATE FUNCTION</command>, which
-	converts data from its internal form to a form suitable
-	for display.
-       </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">default</replaceable></term>
-      <listitem>
-       <para>
-	The default value for the data type.  Usually this is omitted,
-	so that the default is NULL.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">send_function</replaceable></term>
-      <listitem>
-       <para>
-	The name of a function, created by <command>CREATE FUNCTION</command>, which
-	converts data of this type into a form suitable for
-	transmission to another machine.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">receive_function</replaceable></term>
-      <listitem>
-       <para>
-	The name of a function, created by <command>CREATE FUNCTION</command>, which
-	converts data of this type from a form suitable for
-	transmission from another machine to internal form.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">alignment</replaceable></term>
-      <listitem>
-       <para>
-        Storage alignment requirement of the data type.  If specified, 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>
-        Storage technique 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>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATETYPE-2">
-   <refsect2info>
-    <date>1998-09-21</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE TYPE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the type is successfully created.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATETYPE-1">
-  <refsect1info>
-   <date>1998-09-21</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>CREATE TYPE</command>  allows  the user to register a new data
-   type with <productname>PostgreSQL</> for use in the current data base.
-   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 one
-   at the front of the search path; see <literal>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 datatypes,
-   type names also must not conflict with table names in the same schema.)
-  </para>
-
-  <para>
-   <command>CREATE TYPE</command>  requires  the  registration of two functions
-   (using CREATE FUNCTION) before defining the type.   The
-   representation  of  a  new  base  type  is  determined  by
-   <replaceable class="parameter">input_function</replaceable>, which
-   converts the type's external  representation  to  an  internal
-   representation  usable by the
-   operators and functions defined for the type.   Naturally,
-   <replaceable class="parameter">output_function</replaceable>
-   performs the reverse transformation.  The input function may be
-   declared as taking one argument of type <type>opaque</type>,
-   or as taking three arguments of types
-   <type>opaque</type>, <type>OID</type>, <type>int4</type>.
-   (The first argument is the input text as a C string, the second
-   argument is the element type in case this is an array type,
-   and the third is the typmod of the destination column, if known.)
-   The output function may be
-   declared as taking one argument of type <type>opaque</type>,
-   or as taking two arguments of types
-   <type>opaque</type>, <type>OID</type>.
-   (The first argument is actually of the data type itself, but since the
-   output function must be declared first, it's easier to declare it as
-   accepting type <type>opaque</type>.  The second argument is again
-   the array element type for array types.)
-  </para>
-
-  <para>
-   New  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 <option>VARIABLE</option>.  (Internally, this is represented
-   by setting typlen to -1.)  The internal representation of all
-   variable-length types must start with an integer giving the total
-   length of this value of the type.
-  </para>
-
-  <para>
-   The external representation length is  similarly specified using the
-   <replaceable class="parameter">externallength</replaceable>
-   keyword.  (This value is not presently used, and is typically omitted,
-   letting it default to <option>VARIABLE</option>.)
-  </para>
-
-  <para>
-   To indicate that a type is an array,
-   specify the type  of  the  array
-   elements using the <option>ELEMENT</> keyword.  For example, to define
-   an array of 4-byte integers ("int4"), specify
-   <programlisting>ELEMENT = int4</programlisting>
-   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>
-   A default value may be specified, in case a user wants columns of the
-   data type to default to something other than NULL.
-   Specify the default with the <option>DEFAULT</option> keyword.
-   (Such a default may be overridden by an explicit <option>DEFAULT</option>
-   clause attached to a particular column.)
-  </para>
-
-  <para>
-   The optional arguments
-   <replaceable class="parameter">send_function</replaceable> and
-   <replaceable class="parameter">receive_function</replaceable>
-   are not currently used, and are usually omitted (allowing them
-   to default to the 
-   <replaceable class="parameter">output_function</replaceable> and
-   <replaceable class="parameter">input_function</replaceable>
-   respectively).  These functions may someday be resurrected for use
-   in specifying machine-independent binary representations.
-  </para>
-
-  <para>
-   The  optional flag,  <option>PASSEDBYVALUE</option>, indicates that
-   values of this data type are passed
-   by  value  rather  than by reference.  Note that you
-   may not pass by value types whose internal representation is 
-   longer than the width of the <type>Datum</> type (four bytes on
-   most machines, eight bytes on a few).
-  </para>
-
-  <para>
-   The <replaceable class="parameter">alignment</replaceable> keyword
-   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> keyword
-   allows selection of storage strategies for variable-length data types
-   (only <literal>plain</literal> is allowed for fixed-length types).
-   <literal>plain</literal> disables TOAST for the data type: it will always
-   be stored in-line and not compressed.
-   <literal>extended</literal> gives full TOAST capability: 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 method may
-   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>
-
-  <refsect2>
-   <title>Array Types</title>
-
-   <para>
-    Whenever a user-defined data type is created, 
-    <productname>PostgreSQL</productname> automatically creates an
-    associated array type, whose name consists of the base type's
-    name prepended with an underscore.  The parser understands this
-    naming convention, and translates requests for columns of type
-    <literal>foo[]</> into requests for type <literal>_foo</>.
-    The implicitly-created array type is variable length and uses the
-    built-in input and output functions <literal>array_in</> and
-    <literal>array_out</>.
-   </para>
-
-   <para>
-    You might reasonably ask <quote>why is there an <option>ELEMENT</>
-    option, if the system makes the correct array type automatically?</quote>
-    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 N
-    identical things, and you want to allow the N 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>name</>
-    allows its constituent <type>char</>s to be accessed this way.
-    A 2-D <type>point</> type could allow its two component floats to be
-    accessed like <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 N 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 id="SQL-CREATETYPE-notes">
-  <title>Notes</title>
-
-   <para>
-    User-defined type names cannot begin with the underscore character
-    (<quote><literal>_</literal></quote>) and can only be 30
-    characters long (or in general <literal>NAMEDATALEN-2</>, rather than
-    the <literal>NAMEDATALEN-1</> characters allowed for other names).
-    Type names beginning with underscore are
-    reserved for internally-created array type names.
-   </para>
- </refsect1>
- 
- <refsect1>
-  <title>Examples</title>
-  <para>
-   This example creates the <type>box</type> data type and then uses the
-   type in a table definition:
-<programlisting>
-CREATE TYPE box (INTERNALLENGTH = 16,
-    INPUT = my_procedure_1, OUTPUT = my_procedure_2);
-CREATE TABLE myboxes (id INT4, description box);
-</programlisting>
-  </para>
-
-  <para>
-   If <type>box</type>'s internal structure were an array of four
-   <type>float4</>s, we might instead say
-<programlisting>
-CREATE TYPE box (INTERNALLENGTH = 16,
-    INPUT = my_procedure_1, OUTPUT = my_procedure_2,
-    ELEMENT = float4);
-</programlisting>
-   which would allow a box value's component floats 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 int4, obj bigobj);
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATETYPE-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   This <command>CREATE TYPE</command> command is a
-   <productname>PostgreSQL</productname> extension.  There is a
-   <command>CREATE TYPE</command> statement in SQL99 that is rather
-   different in detail.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-CREATETYPE-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createfunction"></member>
-   <member><xref linkend="sql-droptype"></member>
-   <member><citetitle>PostgreSQL Programmer's Guide</citetitle></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_user.sgml b/doc/src/sgml/ref/create_user.sgml
deleted file mode 100644
index 04a596ef745..00000000000
--- a/doc/src/sgml/ref/create_user.sgml
+++ /dev/null
@@ -1,274 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_user.sgml,v 1.23 2002/02/27 21:14:53 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEUSER">
- <refmeta>
-  <refentrytitle id="sql-createuser-title">CREATE USER</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>CREATE USER</refname>
-  <refpurpose>define a new database user account</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-CREATE USER <replaceable class="PARAMETER">username</replaceable> [ [ WITH ] <replaceable class="PARAMETER">option</replaceable> [ ... ] ]
-
-where <replaceable class="PARAMETER">option</replaceable> can be:
-    
-      SYSID <replaceable class="PARAMETER">uid</replaceable> 
-    | [ ENCRYPTED | UNENCRYPTED ] PASSWORD '<replaceable class="PARAMETER">password</replaceable>'
-    | CREATEDB | NOCREATEDB
-    | CREATEUSER | NOCREATEUSER
-    | IN GROUP <replaceable class="PARAMETER">groupname</replaceable> [, ...]
-    | VALID UNTIL '<replaceable class="PARAMETER">abstime</replaceable>' 
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>CREATE USER</command> will add a new user to an instance
-   of <productname>PostgreSQL</productname>. Refer to the
-   <citetitle>Administrator's Guide</citetitle> for information about
-   managing users and authentication.  You must be a database
-   superuser to use this command.
-  </para>
-
-  <refsect2>
-   <title>Parameters</title>
-
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-	The name of the user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">uid</replaceable></term>
-      <listitem>
-       <para>
-        The <literal>SYSID</literal> clause can be used to choose the
-        <productname>PostgreSQL</productname> user ID of the user that
-        is being created. It is not at all necessary that those match
-        the Unix user IDs, but some people choose to keep the numbers
-        the same.
-       </para>
-       <para>
-        If this is not specified, the highest assigned user ID plus one
-	(with a minimum of 100) will be used as default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">password</replaceable></term>
-      <listitem>
-       <para>
-        Sets the user's password. If you do not plan to use password
-        authentication you can omit this option, but the user
-        won't be able to connect to a password-authenticated server.
-	The password can be set or changed later, using
-	<xref linkend="SQL-ALTERUSER" endterm="SQL-ALTERUSER-title">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>ENCRYPTED</></term>
-      <term><literal>UNENCRYPTED</></term>
-      <listitem>
-       <para>
-	These keywords control whether the password is stored
-	encrypted in <literal>pg_shadow</>.  (If neither is specified,
-	the default behavior is determined by the
-	<varname>PASSWORD_ENCRYPTION</varname> server parameter.)  If
-	the presented string is already in MD5-encrypted format, then
-	it is stored as-is, regardless of whether
-	<literal>ENCRYPTED</> or <literal>UNENCRYPTED</> is specified.
-	This allows reloading of encrypted passwords during
-	dump/restore.
-       </para>
-
-       <para>
-        See the chapter on client authentication in the
-        <citetitle>Administrator's Guide</citetitle> for details on
-        how to set up authentication mechanisms.  Note that older
-        clients may lack support for the MD5 authentication mechanism
-        that is needed to work with passwords that are stored
-        encrypted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CREATEDB</></term>
-      <term><literal>NOCREATEDB</></term>
-      <listitem>
-       <para>
-	These clauses define a user's ability to create databases.  If
-	<literal>CREATEDB</literal> is specified, the user being
-	defined will be allowed to create his own databases. Using
-	<literal>NOCREATEDB</literal> will deny a user the ability to
-	create databases. If this clause is omitted,
-	<literal>NOCREATEDB</literal> is used by default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>CREATEUSER</literal></term>
-      <term><literal>NOCREATEUSER</literal></term>
-      <listitem>
-       <para>
-	These clauses determine whether a user will be permitted to
-	create new users himself. This option will also make the user
-	a superuser who can override all access restrictions.
-	Omitting this clause will set the user's value of this
-	attribute to be <literal>NOCREATEUSER</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">groupname</replaceable></term>
-      <listitem>
-       <para>
-	A name of a group into which to insert the user as a new member.
-	Multiple group names may be listed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">abstime</replaceable></term>
-      <listitem>
-       <para>
-	The <literal>VALID UNTIL</literal> clause sets an absolute
-	time after which the user's password is no longer valid.  If
-	this clause is omitted the login will be valid for all time.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
- </refsect1> 
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><computeroutput>CREATE USER</computeroutput></term>
-     <listitem>
-      <para>
-       Message returned if the command completes successfully.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-ALTERUSER" endterm="SQL-ALTERUSER-title"> to
-   change the attributes of a user, and <xref linkend="SQL-DROPUSER"
-   endterm="SQL-DROPUSER-title"> to remove a user.  Use <xref
-   linkend="SQL-ALTERGROUP" endterm="SQL-ALTERGROUP-title"> to add the
-   user to groups or remove the user from groups.
-   <productname>PostgreSQL</productname> includes a program <xref
-   linkend="APP-CREATEUSER" endterm="APP-CREATEUSER-title"> 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>
-   Create a user with no password:
-<programlisting>
-CREATE USER jonathan;
-</programlisting>
-  </para>
-
-  <para>
-   Create a user with a password:
-<programlisting>
-CREATE USER davide WITH PASSWORD 'jw8s0F4';
-</programlisting>
-  </para>
-
-  <para>
-   Create a user with a password, whose account is valid until the end of 2001.
-   Note that after one second has ticked in 2002, the account is not
-   valid:
-
-<programlisting>
-CREATE USER miriam WITH PASSWORD 'jw8s0F4' VALID UNTIL 'Jan 1 2002';
-</programlisting>
-  </para>
-
-  <para> 
-   Create an account where the user can create databases:
-<programlisting>
-CREATE USER manuel WITH PASSWORD 'jw8s0F4' CREATEDB;
-</programlisting>
-  </para>
- </refsect1>
- 
- <refsect1>
-  <title>Compatibility</title>
-  
-  <para>
-   The <command>CREATE USER</command> statement is a
-   <productname>PostgreSQL</productname> extension.  The SQL standard
-   leaves the definition of users to the implementation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-alteruser" endterm="sql-alteruser-title"></member>
-   <member><xref linkend="sql-dropuser" endterm="sql-dropuser-title"></member>
-   <member><xref linkend="app-createuser"></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/create_view.sgml b/doc/src/sgml/ref/create_view.sgml
deleted file mode 100644
index aa7c869285f..00000000000
--- a/doc/src/sgml/ref/create_view.sgml
+++ /dev/null
@@ -1,275 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_view.sgml,v 1.18 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-CREATEVIEW">
- <refmeta>
-  <refentrytitle id="SQL-CREATEVIEW-TITLE">CREATE VIEW</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   CREATE VIEW
-  </refname>
-  <refpurpose>
-   define a new view
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-03-25</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-CREATE VIEW <replaceable class="PARAMETER">view</replaceable> [ ( <replaceable
-class="PARAMETER">column name list</replaceable> ) ] AS SELECT <replaceable class="PARAMETER">query</replaceable>
-  </synopsis>
-
-  <refsect2 id="R2-SQL-CREATEVIEW-1">
-   <refsect2info> 
-    <date>2000-03-25</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">view</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 list</replaceable></term>
-      <listitem>
-       <para>
-        An optional list of names to be used for columns of the view.
-	If given, these names override the column names that would be
-	deduced from the SQL query.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">query</replaceable></term>
-      <listitem>
-       <para>
-	An SQL query (that is, a <command>SELECT</> statement)
-	which will provide the columns and rows of the view.
-       </para>
-       <para>
-	Refer to <xref linkend="sql-select"> for more information
-	about valid arguments.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-CREATEVIEW-2">
-   <refsect2info>
-    <date>2000-03-25</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-CREATE VIEW
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the view is successfully created.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  Relation '<replaceable class="parameter">view</replaceable>' already exists
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This error occurs if the view specified already exists in the database.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  Attribute '<replaceable class="parameter">column</replaceable>' has an unknown type
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The view will be created having a column with an unknown type
-	if you do not specify it. For example, the following command gives
-	a warning:
-	<programlisting>
-CREATE VIEW vista AS SELECT 'Hello World'
-	</programlisting>
-
-	whereas this command does not:
-
-	<programlisting>
-CREATE VIEW vista AS SELECT text 'Hello World'
-	</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-CREATEVIEW-1">
-  <refsect1info>
-   <date>2000-03-25</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>CREATE VIEW</command> will define a view of a query.
-   The view is not physically materialized. Instead, a query
-   rewrite rule (an <literal>ON SELECT</> rule) is automatically generated to
-   support SELECT operations on views.
-  </para>
-
-  <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 one
-   at the front of the search path; see <literal>CURRENT_SCHEMA()</>).
-   The view name must be distinct from the name of any other view, table,
-   sequence, or index in the same schema.
-  </para>
-
-  <refsect2 id="R2-SQL-CREATEVIEW-3">
-   <refsect2info>
-    <date>2000-03-25</date>
-   </refsect2info>
-   <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 <command>DROP VIEW</command> statement to drop views.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-CREATEVIEW-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Create a view consisting of all Comedy films:
-
-   <programlisting>
-CREATE VIEW kinds AS
-    SELECT *
-    FROM films
-    WHERE kind = 'Comedy';
-
-SELECT * FROM kinds;
-
- code  |           title           | did | date_prod  |  kind  | len
--------+---------------------------+-----+------------+--------+-------
- UA502 | Bananas                   | 105 | 1971-07-13 | Comedy | 01:22
- C_701 | There's a Girl in my Soup | 107 | 1970-06-11 | Comedy | 01:36
-(2 rows)
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-CREATEVIEW-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-CREATEVIEW-5">
-   <refsect2info>
-    <date>2000-03-25</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    SQL92 specifies some additional capabilities for the
-    <command>CREATE VIEW</command> statement:
-   </para>
-   <synopsis>
-CREATE VIEW <replaceable class="parameter">view</replaceable> [ <replaceable class="parameter">column</replaceable> [, ...] ]
-    AS SELECT <replaceable class="parameter">expression</replaceable> [ AS <replaceable class="parameter">colname</replaceable> ] [, ...]
-    FROM <replaceable class="parameter">table</replaceable> [ WHERE <replaceable class="parameter">condition</replaceable> ]
-    [ WITH [ CASCADE | LOCAL ] CHECK OPTION ]
-   </synopsis>
-
-   <para>
-    The optional clauses for the full SQL92 command are:
-
-   <variablelist>
-     <varlistentry>
-      <term>CHECK OPTION</term>
-      <listitem>
-       <para>
-	This option is to do with updatable views.
-	All INSERTs and UPDATEs on the view will be
-	checked to ensure data satisfy the view-defining
-	condition. If they do not, the update will be rejected.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>LOCAL</term>
-      <listitem>
-       <para>
-	Check for integrity on this view.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>CASCADE</term>
-      <listitem>
-       <para>
-	Check for integrity on this view and on any dependent
-	view. CASCADE is assumed if neither CASCADE nor LOCAL is specified.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/createdb.sgml b/doc/src/sgml/ref/createdb.sgml
deleted file mode 100644
index 8c3723ca0e9..00000000000
--- a/doc/src/sgml/ref/createdb.sgml
+++ /dev/null
@@ -1,282 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/createdb.sgml,v 1.26 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-CREATEDB">
- <refmeta>
-  <refentrytitle id="APP-CREATEDB-TITLE"><application>createdb</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>createdb</refname>
-  <refpurpose>create a new <productname>PostgreSQL</productname> database</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>createdb</command>
-   <arg rep="repeat"><replaceable>options</replaceable></arg>
-   <arg><replaceable>dbname</replaceable></arg>
-   <arg><replaceable>description</replaceable></arg>
-  </cmdsynopsis>
-
-  <refsect2 id="R2-APP-CREATEDB-1">
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>-h, --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>-p, --port <replaceable class="parameter">port</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the Internet TCP/IP port or the local Unix domain socket file 
-	extension on which the server is listening for connections.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-U, --username <replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-        User name to connect as
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-W, --password</term>
-      <listitem>
-       <para>
-        Force password prompt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-e, --echo</term>
-      <listitem>
-       <para>
-        Echo the queries that <application>createdb</application> generates
-	and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-q, --quiet</term>
-      <listitem>
-       <para>
-        Do not display a response.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-O, --owner <replaceable class="parameter">owner</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the database user who will own the new database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-D, --location <replaceable class="parameter">datadir</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the alternative location for the database.  See also <xref
-	linkend="app-initlocation">.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-T, --template <replaceable class="parameter">template</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the template database from which to build this database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-E, --encoding <replaceable class="parameter">encoding</replaceable></term>
-      <listitem>
-       <para>
-        Specifies the character encoding scheme to be used in this database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">dbname</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the name of the database to be created.  The name must be
-	unique among all <productname>PostgreSQL</productname> databases in this installation.
-        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>
-        This optionally specifies a comment to be associated with the newly created
-	database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-    The options <option>-h</option>, <option>-p</option>, <option>-U</option>,
-    <option>-W</option>, and <option>-e</option> are passed on literally to
-    <xref linkend="app-psql">.
-
-    The options <option>-O</option>, <option>-D</option>,
-    <option>-T</option>, and
-    <option>-E</option> are converted into options for the underlying
-    SQL command <xref linkend="SQL-CREATEDATABASE"
-    endterm="SQL-CREATEDATABASE-title">; see there for more information
-    about them.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-CREATEDB-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>CREATE DATABASE</computeroutput></term>
-      <listitem>
-       <para>The database was successfully created.</para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>createdb: Database creation failed.</computeroutput></term>
-      <listitem>
-       <para>(Says it all.)</para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>createdb: Comment creation failed. (Database was created.)</computeroutput></term>
-      <listitem>
-       <para>
-       The comment/description for the database could not be created.
-       The database itself will have been created already. You can use the
-       <acronym>SQL</acronym> command <command>COMMENT ON DATABASE</command> to
-       create the comment later on.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    If there is an error condition, the backend error message will be displayed.
-    See <xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-TITLE">
-    and <xref linkend="APP-PSQL"> for possibilities.
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-CREATEDB-1">
-  <title>
-   Description
-  </title>
-  <para>
-   <application>createdb</application> creates a new <productname>PostgreSQL</productname>
-   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 shell script wrapper around the
-   <acronym>SQL</acronym> command
-   <xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-title"> via
-   the <productname>PostgreSQL</productname> interactive terminal
-   <xref linkend="APP-PSQL">. Thus, there is nothing
-   special about creating databases via this or other methods. This means
-   that the <application>psql</application> program must be found by the script and that
-   a database server must be running at the targeted port. Also, any default
-   settings and environment variables available to <application>psql</application>
-   and the <application>libpq</application> front-end library will apply.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-APP-CREATEDB-2">
-  <title>Usage</title>
-
-  <informalexample>
-   <para>
-    To create the database <literal>demo</literal> using the default
-    database server:
-<screen>
-<prompt>$ </prompt><userinput>createdb demo</userinput>
-<computeroutput>CREATE DATABASE</computeroutput>
-</screen>
-    The response is the same as you would have gotten from running the
-    <command>CREATE DATABASE</command> <acronym>SQL</acronym> command.
-   </para>
-  </informalexample>
-
-  <informalexample>
-   <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 query:
-<screen>
-<prompt>$ </prompt><userinput>createdb -p 5000 -h eden -E LATIN1 -e demo</userinput>
-<computeroutput>CREATE DATABASE "demo" WITH ENCODING = 'LATIN1'</computeroutput>
-<computeroutput>CREATE DATABASE</computeroutput>
-</screen>
-   </para>
-  </informalexample>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/createlang.sgml b/doc/src/sgml/ref/createlang.sgml
deleted file mode 100644
index 279f967412f..00000000000
--- a/doc/src/sgml/ref/createlang.sgml
+++ /dev/null
@@ -1,225 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/createlang.sgml,v 1.24 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-CREATELANG">
- <refmeta>
-  <refentrytitle id="APP-CREATELANG-TITLE"><application>createlang</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname id="createlang">createlang</refname>
-  <refpurpose>define a new <productname>PostgreSQL</productname> procedural language</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>createlang</command>
-   <arg rep="repeat"><replaceable>connection-options</replaceable></arg>
-   <arg choice="plain"><replaceable>langname</replaceable></arg>
-   <arg><replaceable>dbname</replaceable></arg>
-   <sbr>
-   <command>createlang</command>
-   <arg rep="repeat"><replaceable>connection-options</replaceable></arg>
-   <group choice="plain"><arg>--list</arg><arg>-l</arg></group>
-   <arg choice="plain"><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <refsect2 id="R2-APP-CREATELANG-1">
-   <title>
-    Inputs
-   </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 programming language to be
-	defined.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-d, --dbname <replaceable class="parameter">dbname</replaceable></term>
-      <listitem>
-       <para>
-	Specifies to which database 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>-e, --echo</term>
-      <listitem>
-       <para>
-        Displays SQL commands as they are executed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-l, --list</term>
-      <listitem>
-       <para>
-        Shows a list of already installed languages in the target database
-        (which must be specified).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>--L <replaceable class="parameter">directory</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the directory in which the language interpreter is
-        to be found.  The directory is normally found automatically; this
-        option is primarily for debugging purposes.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <application>createlang</application> also accepts 
-    the following command line arguments for connection parameters:
-    
-    <variablelist>
-     <varlistentry>
-      <term>-h, --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>-p, --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>-U, --username <replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-        User name to connect as
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-W, --password</term>
-      <listitem>
-       <para>
-        Force password prompt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-CREATELANG-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-    Most error messages are self-explanatory. If not, run
-    <application>createlang</application> with the <option>--echo</option>
-    option and see under the respective <acronym>SQL</acronym> command
-    for details. Check also under <xref linkend="APP-PSQL">
-    for more possibilities.
-   </para>
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-APP-CREATELANG-1">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <application>createlang</application> is a utility for adding a new 
-   programming language to a <productname>PostgreSQL</productname> database.
-   <application>createlang</application> can handle all the languages
-   supplied in the default <productname>PostgreSQL</> distribution, but
-   not languages provided by other parties.
-  </para>
-  <para>
-   Although backend programming languages can be added directly using
-   several <acronym>SQL</acronym> commands, it is recommended to use
-   <application>createlang</application> because it performs a number
-   of checks and is much easier to use. See
-   <xref linkend="sql-createlanguage" endterm="sql-createlanguage-title">
-   for more.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-APP-CREATELANG-2">
-  <title>
-   Notes
-  </title>
-  <para>
-   Use <xref linkend="app-droplang"> to remove a language.
-  </para>
-
-  <para>
-   <application>createlang</application> is a shell script that invokes
-   <application>psql</application> several times.  If you have things
-   arranged so that a password prompt is required to connect, you will be
-   prompted for a password several times.
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-APP-CREATELANG-3">
-  <title>Usage</title>
-
-  <informalexample>
-   <para>
-    To install <literal>pltcl</literal> into the database
-    <literal>template1</literal>:
-<screen>
-<prompt>$ </prompt><userinput>createlang pltcl template1</userinput>
-</screen>
-   </para>
-  </informalexample>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/createuser.sgml b/doc/src/sgml/ref/createuser.sgml
deleted file mode 100644
index ed92bb2d86e..00000000000
--- a/doc/src/sgml/ref/createuser.sgml
+++ /dev/null
@@ -1,294 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/createuser.sgml,v 1.25 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-CREATEUSER">
- <refmeta>
-  <refentrytitle id="APP-CREATEUSER-TITLE"><application>createuser</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>createuser</refname>
-  <refpurpose>define a new <productname>PostgreSQL</productname> user account</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>createuser</command>
-   <arg rep="repeat"><replaceable>options</replaceable></arg>
-   <arg><replaceable>username</replaceable></arg>
-  </cmdsynopsis>
-
-  <refsect2 id="R2-APP-CREATEUSER-1">
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>-h, --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>-p, --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>-e, --echo</term>
-      <listitem>
-       <para>
-        Echo the queries that <application>createuser</application> generates
-	and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-q, --quiet</term>
-      <listitem>
-       <para>
-        Do not display a response.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-d, --createdb</term>
-      <listitem>
-       <para>
-	The new user is allowed to create databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-D, --no-createdb</term>
-      <listitem>
-       <para>
-	The new user is not allowed to create databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-a, --adduser</term>
-      <listitem>
-       <para>
-	The new user is allowed to create other users.
-	(Note: actually, this makes the new user a <firstterm>superuser</>.
-	The option is poorly named.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-A, --no-adduser</term>
-      <listitem>
-       <para>
-	The new user is not allowed to create other users (i.e.,
-	the new user is a regular user not a superuser).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-P, --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>-i, --sysid <replaceable class="parameter">uid</replaceable></term>
-      <listitem>
-       <para>
-       Allows you to pick a non-default user id for the new user. This is not
-       necessary, but some people like it.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-E, --encrypted</term>
-      <listitem>
-       <para>
-	Encrypts the user's password stored in the database. If not
-	specified, the default is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-N, --unencrypted</term>
-      <listitem>
-       <para>
-	Does not encrypt the user's password stored in the database. If
-	not specified, the default is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the name of the <productname>PostgreSQL</productname> user to be created. 
-	This name must be unique among all <productname>PostgreSQL</productname> users.
-       </para>
-      </listitem>
-     </varlistentry>  
-    </variablelist>
-
-    You will be prompted for a name and other missing information if it is not
-    specified on the command line.
-    </para>
-
-    <para>
-    The options <literal>-h</literal>, <literal>-p</literal>, and <literal>-e</literal>,
-    are passed on literally to <xref linkend="APP-PSQL">. The
-    <application>psql</application> options <literal>-U</literal> and <literal>-W</literal>
-    are available as well, but their use can be confusing in this context.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-CREATEUSER-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>CREATE USER</computeroutput></term>
-      <listitem>
-       <para>
-        All is well.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>createuser: creation of user "<replaceable class="parameter">username</replaceable>" failed</computeroutput></term>
-      <listitem>
-       <para>
-        Something went wrong. The user was not created.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-    If there is an error condition, the backend error message will be displayed.
-    See <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title">
-    and <xref linkend="APP-PSQL"> for possibilities.
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-  
- <refsect1 id="R1-APP-CREATEUSER-1">
-  <title>
-   Description
-  </title>
-  <para>
-   <application>createuser</application> creates a 
-   new <productname>PostgreSQL</productname> user.  
-   Only superusers (users with <literal>usesuper</literal> set in
-   the <literal>pg_shadow</literal> table) can create 
-   new <productname>PostgreSQL</productname> users,
-   so <application>createuser</application> must be
-   invoked by someone who is a <productname>PostgreSQL</productname>
-   superuser.
-  </para>
-
-  <para>
-   Being a superuser also implies the ability to bypass access permission
-   checks within the database, so superuser-dom should not be granted lightly.
-  </para>
-
-  <para>
-   <application>createuser</application> is a shell script wrapper around the
-   <acronym>SQL</acronym> command
-   <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title"> via
-   the <productname>PostgreSQL</productname> interactive terminal
-   <xref linkend="APP-PSQL">. Thus, there is nothing
-   special about creating users via this or other methods. This means
-   that the <application>psql</application> application must be found by the
-   script and that 
-   a database server must be running at the targeted host. Also, any default
-   settings and environment variables used by <application>psql</application>
-   and the <application>libpq</application> front-end library will apply.
-  </para>
-
- </refsect1>
-
-
- <refsect1 id="R1-APP-CREATEUSER-2">
-  <title>Usage</title>
-
-  <informalexample>
-   <para>
-    To create a user <literal>joe</literal> on the default database
-    server:
-<screen>
-<prompt>$ </prompt><userinput>createuser joe</userinput>
-<computeroutput>Is the new user allowed to create databases? (y/n) </computeroutput><userinput>n</userinput>
-<computeroutput>Shall the new user be allowed to create more new users? (y/n) </computeroutput><userinput>n</userinput>
-<computeroutput>CREATE USER</computeroutput>
-</screen>
-   </para>
-  </informalexample>
-
-  <informalexample>
-   <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 query:
-<screen>
-<prompt>$ </prompt><userinput>createuser -p 5000 -h eden -D -A -e joe</userinput>
-<computeroutput>CREATE USER "joe" NOCREATEDB NOCREATEUSER</computeroutput>
-<computeroutput>CREATE USER</computeroutput>
-</screen>
-   </para>
-  </informalexample>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/current_date.sgml b/doc/src/sgml/ref/current_date.sgml
deleted file mode 100644
index 5e06c4dd70d..00000000000
--- a/doc/src/sgml/ref/current_date.sgml
+++ /dev/null
@@ -1,148 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_date.sgml,v 1.5 2002/04/21 19:02:39 thomas Exp $
-Postgres documentation
--->
-
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_date.sgml,v 1.5 2002/04/21 19:02:39 thomas Exp $
-Postgres documentation
--->
-
-<REFENTRY ID="SQL-CURRENT-DATE">
- <REFMETA>
-  <REFENTRYTITLE>CURRENT_DATE</REFENTRYTITLE>
-  <REFMISCINFO>SQL - Functions</REFMISCINFO>
- </REFMETA>
- <REFNAMEDIV>
-  <REFNAME>
-   CURRENT_DATE
-  </REFNAME>
-  <REFPURPOSE>
-Returns the current date
-  </REFPURPOSE>
- <REFSYNOPSISDIV>
-  <REFSYNOPSISDIVINFO>
-   <DATE>1998-04-15</DATE>
-  </REFSYNOPSISDIVINFO>
-  <SYNOPSIS>
-   CURRENT_DATE
-  </SYNOPSIS>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-DATE-1">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Inputs
-   </TITLE>
-   <PARA>
-None.
-  </REFSECT2>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-DATE-2">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Outputs
-   </TITLE>
-   <PARA>
-       <VARIABLELIST>
-	<VARLISTENTRY>
-	 <TERM>
-<replaceable>date</replaceable>
-
-	 </TERM>
-	 <LISTITEM>
-	  <PARA>
-	  Returns "<replaceable class="parameter">today</replaceable>".
-   </VARIABLELIST>
-  </REFSECT2>
- </REFSYNOPSISDIV>
- 
- <REFSECT1 ID="R1-SQL-CURRENT-DATE-1">
-  <REFSECT1INFO>
-   <DATE>1998-04-15</DATE>
-  </REFSECT1INFO>
-  <TITLE>
-   Description
-  </TITLE>
-  <PARA>
-   The niladic CURRENT_DATE function has a data type of
-   DATE and returns the date at the time that it is run.
-  </PARA>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-DATE-3">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Notes
-   </TITLE>
-   <PARA>
-    Refer to SET DATESTYLE for further information about date format.
-   </PARA>
-  </REFSECT2>
-  
- <REFSECT1 ID="R1-SQL-CURRENT-DATE-2">
-  <TITLE>
-   Usage
-  </TITLE>
-  <PARA>
-   Insert the date of insertion into a row:
-  </PARA>
-  <ProgramListing>
-   INSERT INTO films
-         VALUES ('TM999','Ben Hur',105,CURRENT_DATE,'Action',NULL);
-  </ProgramListing>
-  
-  <PARA>
-   Display CURRENT-DATE:
-  </PARA>
-  <ProgramListing>
-   SELECT CURRENT_DATE AS today;
-
-   today
-   ------------
-   1998-03-31
-
-  </ProgramListing>
- </REFSECT1>
- 
- <REFSECT1 ID="R1-SQL-CURRENT-DATE-3">
-  <TITLE>
-   Compatibility
-  </TITLE>
-  <PARA>
-  </PARA>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-DATE-4">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    SQL92
-   </TITLE>
-   <PARA>
-    Full compatibility.
-   </PARA>
-  </refsect2>
- </refsect1>
-</REFENTRY>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/current_time.sgml b/doc/src/sgml/ref/current_time.sgml
deleted file mode 100644
index 85cd7e7da6f..00000000000
--- a/doc/src/sgml/ref/current_time.sgml
+++ /dev/null
@@ -1,158 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_time.sgml,v 1.6 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<REFENTRY ID="SQL-CURRENT-TIME">
- <REFMETA>
-  <REFENTRYTITLE>CURRENT_TIME</REFENTRYTITLE>
-  <REFMISCINFO>SQL - Functions</REFMISCINFO>
- </REFMETA>
- <REFNAMEDIV>
-  <REFNAME>
-   CURRENT_TIME
-  </REFNAME>
-  <REFPURPOSE>
-Returns the current local time
-  </REFPURPOSE>
- <REFSYNOPSISDIV>
-  <REFSYNOPSISDIVINFO>
-   <DATE>1998-04-15</DATE>
-  </REFSYNOPSISDIVINFO>
-  <SYNOPSIS>
-   CURRENT_TIME 
-  </SYNOPSIS>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-TIME-1">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Inputs
-   </TITLE>
-   <PARA>
-None.
-   
-  </REFSECT2>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-TIME-2">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Outputs
-   </TITLE>
-   <PARA>
-       <VARIABLELIST>
-	<VARLISTENTRY>
-	 <TERM>
-	  <replaceable>time</replaceable>
-
-	 <LISTITEM>
-	  <PARA>
-	  <ReturnValue>Returns "<replaceable class="parameter">now</replaceable>"</ReturnValue>
-
-   </VARIABLELIST>
-  </REFSECT2>
- </REFSYNOPSISDIV>
- 
- <REFSECT1 ID="R1-SQL-CURRENT-TIME-1">
-  <REFSECT1INFO>
-   <DATE>1998-04-15</DATE>
-  </REFSECT1INFO>
-  <TITLE>
-   Description
-  </TITLE>
-  <PARA>
-   The niladic CURRENT_TIME function has a data type of
-   TIME and returns the local time when it is run.
-  </PARA>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-TIME-3">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Notes
-   </TITLE>
-   <PARA> Refer to the SET TIME ZONE statement for a further description
-    of local time.
-   </PARA>
-  </REFSECT2>
-  
- <REFSECT1 ID="R1-SQL-CURRENT-TIME-2">
-  <TITLE>
-   Usage
-  </TITLE>
-  <PARA>Display CURRENT_TIME:
-  </PARA>
-  <ProgramListing>
-   SELECT CURRENT_TIME AS now;
-
-   now
-   -----------
-   17:41:31+02
-
-  </ProgramListing>
- </REFSECT1>
- 
- <REFSECT1 ID="R1-SQL-CURRENT-TIME-3">
-  <TITLE>
-   Compatibility
-  </TITLE>
-  <PARA>
-  </PARA>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-TIME-4">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    SQL92
-   </TITLE>
-   <PARA>
-    SQL92 specifies some additional capabilities for CURRENT_TIME:
-   </PARA>
-   <VARIABLELIST>
-    <VARLISTENTRY>
-     <TERM>
-     </TERM>
-     <LISTITEM>
-      <PARA>
-       <VARIABLELIST>
-	<VARLISTENTRY>
-	 <TERM>
-	  <ReturnValue>
-	   CURRENT_TIME [ (<replaceable class="parameter">scale</replaceable>) ]</ReturnValue>
-	 </TERM>
-	 <LISTITEM>
-	  <PARA>
-	   The optional scale for CURRENT_TIME, if specified, is an
-	   unsigned integer representing the number of digits in the
-	   optional seconds fraction of the time value represented
-	   by the function.
-	  </PARA>
-	 </LISTITEM>
-	</VARLISTENTRY>
-       </VARIABLELIST>
-     </LISTITEM>
-    </VARLISTENTRY>
-   </VARIABLELIST>
-</REFENTRY>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/current_timestamp.sgml b/doc/src/sgml/ref/current_timestamp.sgml
deleted file mode 100644
index 75782dbc72f..00000000000
--- a/doc/src/sgml/ref/current_timestamp.sgml
+++ /dev/null
@@ -1,166 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_timestamp.sgml,v 1.6 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<REFENTRY ID="SQL-CURRENT-TIMESTAMP">
- <REFMETA>
-  <REFENTRYTITLE>CURRENT_TIMESTAMP</REFENTRYTITLE>
-  <REFMISCINFO>SQL - Functions</REFMISCINFO>
- </REFMETA>
- <REFNAMEDIV>
-  <REFNAME>
-   CURRENT_TIMESTAMP
-  </REFNAME>
-  <REFPURPOSE>
-   Returns the current date and time
-  </REFPURPOSE>
-  
-  
- <REFSYNOPSISDIV>
-  <REFSYNOPSISDIVINFO>
-   <DATE>1998-04-15</DATE>
-  </REFSYNOPSISDIVINFO>
-  <synopsis>
-  CURRENT_TIMESTAMP 
- </SYNOPSIS>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-TIMESTAMP-1">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Inputs
-   </TITLE>
-   <PARA>
-None.
-
-  </REFSECT2>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-TIMESTAMP-2">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Outputs
-   </TITLE>
-   <PARA>
-       <VARIABLELIST>
-	<VARLISTENTRY>
-	 <TERM>
-<replaceable>timestamp</replaceable>
-
-	 <LISTITEM>
-	  <PARA>
-	  Returns "<replaceable class="parameter">today</replaceable>" and "<replaceable class="parameter">now</replaceable>".
-
-   </VARIABLELIST>
-  </REFSECT2>
- </REFSYNOPSISDIV>
- 
- <REFSECT1 ID="R1-SQL-CURRENT-TIMESTAMP-1">
-  <REFSECT1INFO>
-   <DATE>1998-04-15</DATE>
-  </REFSECT1INFO>
-  <TITLE>
-   Description
-  </TITLE>
-  <PARA>
-   The niladic CURRENT_TIMESTAMP function has a data type of
-   TIMESTAMP and returns the date and local time at which it is run.
-  </PARA>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-TIMESTAMP-3">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Notes
-   </TITLE>
-   <PARA>
-    Refer to the SET TIME ZONE statement for a further description
-    of local time.
-   </PARA>
-   
-   
-  </REFSECT2>
-  
- <REFSECT1 ID="R1-SQL-CURRENT-TIMESTAMP-2">
-  <TITLE>
-   Usage
-  </TITLE>
-  <PARA>
-   Display CURRENT_TIMESTAMP:
-  </PARA>
-  <ProgramListing>
-   SELECT CURRENT_TIMESTAMP AS date_and_time;
-
-   date_and_time
-   ----------------------
-   1998-03-31 07:41:21-08
-  </ProgramListing>
- </REFSECT1>
- 
- <REFSECT1 ID="R1-SQL-CURRENT-TIMESTAMP-3">
-  <TITLE>
-   Compatibility
-  </TITLE>
-  <PARA>
-  </PARA>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-TIMESTAMP-4">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    SQL92
-   </TITLE>
-   <PARA>
-   SQL92 specifies some additional capabilities for CURRENT_TIMESTAMP:
-   </PARA>
-   
-   <VARIABLELIST>
-    <VARLISTENTRY>
-     <TERM>
-     </TERM>
-     <LISTITEM>
-      <PARA>
-       <VARIABLELIST>
-	<VARLISTENTRY>
-	 <TERM>
-	  <ReturnValue>CURRENT_TIMESTAMP [ (<replaceable class="parameter">scale</replaceable>) ]</ReturnValue>
-	 </TERM>
-	 <LISTITEM>
-	  <PARA>
-	   The optional scale for CURRENT_TIMESTAMP, if specified, is an
-	   unsigned integer representing the number of digits in the
-	   optional seconds fraction of the time value represented
-	   by the function.
-	  </PARA>
-	 </LISTITEM>
-	</VARLISTENTRY>
-       </VARIABLELIST>
-      </para>
-     </LISTITEM>
-    </VARLISTENTRY>
-   </VARIABLELIST>
-  </refsect2>
- </refsect1>
-</REFENTRY>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/current_user.sgml b/doc/src/sgml/ref/current_user.sgml
deleted file mode 100644
index d358dd8c43d..00000000000
--- a/doc/src/sgml/ref/current_user.sgml
+++ /dev/null
@@ -1,167 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/current_user.sgml,v 1.6 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<REFENTRY ID="SQL-CURRENT-USER">
- <REFMETA>
-  <REFENTRYTITLE>CURRENT_USER</REFENTRYTITLE>
-  <REFMISCINFO>SQL - Functions</REFMISCINFO>
- </REFMETA>
- <REFNAMEDIV>
-  <REFNAME>
-   CURRENT_USER
-  </REFNAME>
-  <REFPURPOSE>
-   Returns the current user name
-  </REFPURPOSE>
- <REFSYNOPSISDIV>
-  <REFSYNOPSISDIVINFO>
-   <DATE>1998-04-15</DATE>
-  </REFSYNOPSISDIVINFO>
-  <SYNOPSIS>
-   CURRENT_USER 
-  </SYNOPSIS>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-USER-1">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Inputs
-   </TITLE>
-   <PARA>
-
-None.
-  </REFSECT2>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-USER-2">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Outputs
-   </TITLE>
-   <PARA>
-
-       <VARIABLELIST>
-	<VARLISTENTRY>
-	 <TERM>
-	  <replaceable>username</replaceable>
-	 </TERM>
-	 <LISTITEM>
-	  <PARA>
-The name of the current user.
-
-   </VARIABLELIST>
-  </REFSECT2>
- </REFSYNOPSISDIV>
- 
- <REFSECT1 ID="R1-SQL-CURRENT-USER-1">
-  <REFSECT1INFO>
-   <DATE>1998-04-15</DATE>
-  </REFSECT1INFO>
-  <TITLE>
-   Description
-  </TITLE>
-  <PARA>
-   The niladic CURRENT_USER function returns a string of type "name"
-   whose value represents a user name identification.
-  </PARA>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-USER-3">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    Notes
-   </TITLE>
-   <PARA>
-    Data type "name" is a non-standard 31-character type for storing
-    system identifiers.
-   </PARA>
-  </REFSECT2>
-  
- <REFSECT1 ID="R1-SQL-CURRENT-USER-2">
-  <TITLE>
-   Usage
-  </TITLE>
-  <PARA>
-   Display CURRENT_USER
-  </PARA>
-  <ProgramListing>
-   SELECT CURRENT_USER AS who_am_i;
-
-   who_am_i
-   ------------
-   jose
-  </ProgramListing>
- </REFSECT1>
- 
- <REFSECT1 ID="R1-SQL-CURRENT-USER-3">
-  <TITLE>
-   Compatibility
-  </TITLE>
-  <PARA>
-  </PARA>
-  
-  <REFSECT2 ID="R2-SQL-CURRENT-USER-4">
-   <REFSECT2INFO>
-    <DATE>1998-04-15</DATE>
-   </REFSECT2INFO>
-   <TITLE>
-    SQL92
-   </TITLE>
-   <PARA>
-   SQL92 specifies some additional niladic USER functions:
-   </PARA>
-   <variablelist>
-    <varlistentry>
-     <term>CURRENT_USER / USER</term>
-     <listitem>
-      <para>  
-       USER is a synonym for CURRENT_USER. 
-      </para>
-     </listitem>
-    </varlistentry>
-    <varlistentry>
-     <term>SESSION_USER</term>
-     <listitem>
-      <para>
-       The SESSION_USER function returns the SQL-session user name.
-      </para>
-     </listitem>
-    </varlistentry>
-    <varlistentry>
-     <term>SYSTEM_USER</term>
-     <listitem>
-      <para>
-       The SYSTEM_USER function returns the database's initial default user.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-   <para>
-    A niladic USER function returns a SQL_TEXT character string whose
-    value represents a user name.
-   </para>
-  </refsect2>
- </refsect1>
-</REFENTRY>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml
deleted file mode 100644
index 77c45d90b09..00000000000
--- a/doc/src/sgml/ref/declare.sgml
+++ /dev/null
@@ -1,329 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.18 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DECLARE">
- <refmeta>
-  <refentrytitle id="SQL-DECLARE-TITLE">DECLARE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DECLARE
-  </refname>
-  <refpurpose>
-   define a cursor
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INSENSITIVE ] [ SCROLL ]
-    CURSOR FOR <replaceable class="parameter">query</replaceable>
-    [ FOR { READ ONLY | UPDATE [ OF <replaceable class="parameter">column</replaceable> [, ...] ] ]
-  </synopsis>
-  <refsect2 id="R2-SQL-DECLARE-1">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">cursorname</replaceable></term>
-      <listitem>
-       <para>
-	The name of the cursor to be used in subsequent FETCH operations.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>BINARY</term>
-      <listitem>
-       <para>
-	Causes the cursor to fetch data in binary
-	rather than in text format.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>INSENSITIVE</term>
-      <listitem>
-       <para>
-	<acronym>SQL92</acronym> keyword indicating that data retrieved
-	from the cursor should be unaffected by updates from other processes or cursors.
-	Since cursor operations occur within transactions
-	in <productname>PostgreSQL</productname> this is always the case.
-	This keyword has no effect.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>SCROLL</term>
-      <listitem>
-       <para>
-	<acronym>SQL92</acronym> keyword indicating that data may be retrieved
-	in multiple rows per FETCH operation. Since this is allowed at all times
-	by <productname>PostgreSQL</productname> this keyword has no effect.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">query</replaceable></term>
-      <listitem>
-       <para>
-	An SQL query which will provide the rows to be governed by the
-	cursor.
-	Refer to the SELECT statement for further information about
-	valid arguments.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>READ ONLY</term>
-      <listitem>
-       <para>
-	<acronym>SQL92</acronym> keyword indicating that the cursor will be used
-	in a read only mode. Since this is the only cursor access mode
-	available in <productname>PostgreSQL</productname> this keyword has no effect.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>UPDATE</term>
-      <listitem>
-       <para>
-	<acronym>SQL92</acronym> keyword indicating that the cursor will be used
-	to update tables. Since cursor updates are not currently
-	supported in <productname>PostgreSQL</productname> this keyword
-	provokes an informational error message.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">column</replaceable></term>
-      <listitem>
-       <para>
-	Column(s) to be updated.
-	Since cursor updates are not currently
-	supported in <productname>PostgreSQL</productname> the UPDATE clause
-	provokes an informational error message.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DECLARE-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DECLARE CURSOR
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the SELECT is run successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  Closing pre-existing portal "<replaceable class="parameter">cursorname</replaceable>"
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message is reported if the same cursor name was already declared
-	in the current transaction block.  The previous definition is
-	discarded.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  DECLARE CURSOR may only be used in begin/end transaction blocks
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This error occurs if the cursor is not declared within a transaction block.
-       </para>
-      </listitem>
-     </varlistentry>     
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DECLARE-1">
-  <refsect1info>
-   <date>1998-09-04</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <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. Cursors can
-   return data either in text or in binary format using
-   <xref linkend="sql-fetch" endterm="sql-fetch-title">.
-  </para>
-
-  <para>
-   Normal cursors return data in text format, either ASCII or another
-   encoding scheme depending on how the <productname>PostgreSQL</productname>
-   backend was built. Since
-   data is stored natively in binary format, the system must
-   do a conversion to produce the text format. In addition,
-   text formats are often larger in size than the corresponding binary format.
-   Once the information comes back in text form,  the client
-   application may need to convert it to a binary format to
-   manipulate it.
-   BINARY cursors give you back the data in the native binary
-   representation.
-  </para>
-
-  <para>
-   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 value equal to control-A (<literal>^A</literal>).
-  </para>
-
-  <para>
-   BINARY cursors should be used carefully. User applications such
-   as <application>psql</application> are not aware of binary cursors
-   and expect data to come back in a text format.
-  </para>
-
-  <para>
-   String representation is architecture-neutral whereas binary
-   representation can differ between different machine architectures.
-   <emphasis><productname>PostgreSQL</productname> does not resolve
-    byte ordering or representation issues for binary cursors</emphasis>.
-   Therefore, if your client machine and server machine use different
-   representations (e.g., <quote>big-endian</quote> versus <quote>little-endian</quote>),
-   you will probably not want your data returned in
-   binary format.
-   However, binary cursors may be a
-   little more efficient since there is less conversion overhead in
-   the server to client data transfer.
-
-   <tip>
-    <para>
-     If you intend to display the data in
-     ASCII,  getting it back in ASCII will save you some
-     effort on the client side.
-    </para>
-   </tip>
-  </para>
-
-  <refsect2 id="R2-SQL-DECLARE-3">
-   <refsect2info>
-    <date>1998-09-04</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    Cursors are only available in transactions. Use to
-    <xref linkend="sql-begin" endterm="sql-begin-title">,
-    <xref linkend="sql-commit" endterm="sql-commit-title">
-    and
-    <xref linkend="sql-rollback" endterm="sql-rollback-title">
-    to define a transaction block.
-   </para>
-
-   <para>
-    In <acronym>SQL92</acronym> cursors are only available in
-    embedded <acronym>SQL</acronym> (<acronym>ESQL</acronym>) applications. 
-    The <productname>PostgreSQL</productname> backend
-    does not implement an explicit <command>OPEN cursor</command>
-    statement; 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 <acronym>SQL92</acronym> cursor conventions, including those
-    involving DECLARE and OPEN statements.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-DECLARESTATEMENT-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To declare a cursor:
-
-   <programlisting>
-DECLARE liahona CURSOR
-    FOR SELECT * FROM films;
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-DECLARESTATEMENT-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-DECLARESTATEMENT-4">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <acronym>SQL92</acronym> allows cursors only in embedded <acronym>SQL</acronym>
-    and in modules. <productname>PostgreSQL</productname> permits cursors to be used
-    interactively.
-    <acronym>SQL92</acronym> allows embedded or modular cursors to
-    update database information.
-    All <productname>PostgreSQL</productname> cursors are read only.
-    The BINARY keyword is a <productname>PostgreSQL</productname> extension.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/delete.sgml b/doc/src/sgml/ref/delete.sgml
deleted file mode 100644
index e821d5e3cb1..00000000000
--- a/doc/src/sgml/ref/delete.sgml
+++ /dev/null
@@ -1,211 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/delete.sgml,v 1.16 2002/04/23 02:07:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DELETE">
- <refmeta>
-  <refentrytitle id="SQL-DELETE-TITLE">DELETE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DELETE
-  </refname>
-  <refpurpose>
-   delete rows of a table
-  </refpurpose>
-
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DELETE FROM [ ONLY ] <replaceable class="PARAMETER">table</replaceable> [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-DELETE-1">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <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">condition</replaceable></term>
-      <listitem>
-       <para>
-	This is an SQL selection query which returns the rows which
-	are to be deleted.
-       </para>
-       <para>
-	Refer to the SELECT statement for further description
-	of the WHERE clause.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DELETE-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DELETE <replaceable class="parameter">count</replaceable>
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if items are successfully deleted. The
-	<replaceable class="parameter">count</replaceable> is the number
-	of rows deleted.
-       </para>
-       <para>
-	If <replaceable class="parameter">count</replaceable> is 0,
-	no rows were deleted.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DELETE-1">
-  <refsect1info>
-   <date>1998-04-15</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>DELETE</command> removes rows which satisfy the WHERE
-   clause from the specified table.
-  </para>
-
-  <para>
-   If the <firstterm>condition</firstterm> (WHERE clause) is absent,
-   the effect is to delete all rows in the table.
-   The result is a valid, but empty table.
-
-   <tip>
-    <para>
-     <xref linkend="sql-truncate" endterm="sql-truncate-title"> is a
-     <productname>PostgreSQL</productname> extension which provides a
-     faster mechanism to remove all rows from a table.
-    </para>
-   </tip>
-  </para>
-
-  <para>
-  By default DELETE will delete tuples in the table specified 
-  and all its sub-tables. If you wish to only update the
-  specific table mentioned, you should use the ONLY clause.
-  </para>
-
-  <para>
-   You must have write access to the table in order to modify
-   it, as well as read access to any table whose values are
-   read in the <replaceable class="parameter">condition</replaceable>.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-DELETE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Remove all films but musicals:
-<programlisting>
-DELETE FROM films WHERE kind &lt;&gt; 'Musical';
-SELECT * FROM films;
-
-<computeroutput>
- code  |           title           | did | date_prod  |  kind   | len
--------+---------------------------+-----+------------+---------+-------
- UA501 | West Side Story           | 105 | 1961-01-03 | Musical | 02:32
- TC901 | The King and I            | 109 | 1956-08-11 | Musical | 02:13
- WD101 | Bed Knobs and Broomsticks | 111 |            | Musical | 01:57
-(3 rows)
-</computeroutput>
-</programlisting>
-  </para>
-
-  <para>
-   Clear the table <literal>films</literal>:
-<programlisting>
-DELETE FROM films;
-SELECT * FROM films;
-
-<computeroutput>
- code | title | did | date_prod | kind | len
-------+-------+-----+-----------+------+-----
-(0 rows)
-</computeroutput>
-</programlisting>      
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-DELETE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-DELETE-4">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <acronym>SQL92</acronym> allows a positioned DELETE statement:
-   
-    <synopsis>
-DELETE FROM <replaceable class="parameter">table</replaceable> WHERE
-    CURRENT OF <replaceable class="parameter">cursor</replaceable>
-    </synopsis>
-
-    where <replaceable class="parameter">cursor</replaceable>
-    identifies an open cursor.
-    Interactive cursors in <productname>PostgreSQL</productname> are read-only.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_aggregate.sgml b/doc/src/sgml/ref/drop_aggregate.sgml
deleted file mode 100644
index 857a7f10f48..00000000000
--- a/doc/src/sgml/ref/drop_aggregate.sgml
+++ /dev/null
@@ -1,176 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_aggregate.sgml,v 1.18 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPAGGREGATE">
- <refmeta>
-  <refentrytitle id="SQL-DROPAGGREGATE-TITLE">DROP AGGREGATE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP AGGREGATE
-  </refname>
-  <refpurpose>
-   remove a user-defined aggregate function
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP AGGREGATE <replaceable class="PARAMETER">name</replaceable> ( <replaceable class="PARAMETER">type</replaceable> )
-  </synopsis>
-
-  <refsect2 id="R2-SQL-DROPAGGREGATE-1">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <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>
-	The input data type of the aggregate function,
-	or <literal>*</literal> if the function accepts any input type.
-	(Refer to the <citetitle>PostgreSQL User's Guide</citetitle> for
-	further information about data types.)
-	<comment>This should become a cross-reference rather than a
-	 hard-coded chapter number</comment>
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPAGGREGATE-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP AGGREGATE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the command is successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: RemoveAggregate: aggregate '<replaceable class="parameter">name</replaceable>' for type <replaceable class="parameter">type</replaceable> does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the aggregate function specified does not
-	exist in the database.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPAGGREGATE-1">
-  <refsect1info>
-   <date>1998-04-15</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP AGGREGATE</command> will delete an existing
-   aggregate definition. To execute this command the current
-   user must be the owner of the aggregate.
-  </para>
-
-  <refsect2 id="R2-SQL-DROPAGGREGATE-3">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    Use
-    <xref linkend="sql-createaggregate" endterm="sql-createaggregate-title">
-    to create aggregate functions.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPAGGREGATE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To remove the <literal>myavg</literal> aggregate for type
-   <literal>int4</literal>:
-  </para>
-  <programlisting>
-DROP AGGREGATE myavg(int4);
-  </programlisting>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPAGGREGATE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-DROPAGGREGATE-4">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    There is no <command>DROP AGGREGATE</command> statement
-    in <acronym>SQL92</acronym>; the statement is a
-    <productname>PostgreSQL</productname>
-    language extension.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_database.sgml b/doc/src/sgml/ref/drop_database.sgml
deleted file mode 100644
index 4f5095892fc..00000000000
--- a/doc/src/sgml/ref/drop_database.sgml
+++ /dev/null
@@ -1,171 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_database.sgml,v 1.15 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPDATABASE">
- <refmeta>
-  <refentrytitle id="SQL-DROPDATABASE-TITLE">DROP DATABASE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP DATABASE
-  </refname>
-  <refpurpose>
-   remove a database
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-12-11</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP DATABASE <replaceable class="PARAMETER">name</replaceable>
-  </synopsis>
-
-  <refsect2 id="R2-SQL-DROPDATABASE-1">
-   <refsect2info>
-    <date>1999-12-11</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of an existing database to remove.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPDATABASE-2">
-   <refsect2info>
-    <date>1999-12-11</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-
-     <varlistentry>
-      <term><computeroutput>DROP DATABASE</computeroutput></term>
-      <listitem>
-       <para>
-	This message is returned if the command is successful.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>DROP DATABASE: cannot be executed on the currently open database</computeroutput></term>
-      <listitem>
-       <para>
-        You cannot be connected to the database you are about to remove.
-        Instead, connect to <literal>template1</literal> or any other
-        database and run this command again.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>DROP DATABASE: may not be called in a transaction block</computeroutput></term>
-      <listitem>
-       <para>
-        You must finish the transaction in progress before you can call this command.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-SQL-DROPDATABASE-1">
-  <refsect1info>
-   <date>1999-12-11</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP DATABASE</command> removes the catalog entries for an existing
-   database and deletes the directory containing the data.
-   It can only be executed by the database owner (usually the user that created
-   it).
-  </para>
-
-  <para>
-   <command>DROP DATABASE</command> cannot be undone.  Use it with care!
-  </para>
-
-  <refsect2 id="R2-SQL-DROPDATABASE-3">
-   <refsect2info>
-    <date>1999-12-11</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    This command cannot be executed while connected to the target
-    database. Thus, it might be more convenient to use the shell
-    script <xref linkend="app-dropdb" endterm="app-dropdb-title">,
-    which is a wrapper around this command, instead.
-   </para>
-
-   <para>
-    Refer to
-    <xref linkend="sql-createdatabase" endterm="sql-createdatabase-title">
-    for information on how to create a database.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPDATABASE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-DROPDATABASE-4">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    <command>DROP DATABASE</command> statement is a
-    <productname>PostgreSQL</productname> language extension;
-    there is no such command in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_domain.sgml b/doc/src/sgml/ref/drop_domain.sgml
deleted file mode 100644
index 5bc73a065fa..00000000000
--- a/doc/src/sgml/ref/drop_domain.sgml
+++ /dev/null
@@ -1,185 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_domain.sgml,v 1.6 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPDOMAIN">
- <refmeta>
-  <refentrytitle id="SQL-DROPDOMAIN-TITLE">
-   DROP DOMAIN
-  </refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP DOMAIN
-  </refname>
-  <refpurpose>
-   remove a user-defined domain
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP DOMAIN <replaceable class="PARAMETER">domainname</replaceable> [, ...]  [ CASCADE | RESTRICT ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-DROPDOMAIN-1">
-   <refsect2info>
-    <date>2002-02-24</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">domainname</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.  This
-	behavior is not currently supported.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><literal>RESTRICT</></term>
-      <listitem>
-       <para>
-        Do not drop dependent objects.  This is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPDOMAIN-2">
-   <refsect2info>
-    <date>2002-02-24</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP DOMAIN
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the command is successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  RemoveDomain: type '<replaceable class="parameter">domainname</replaceable>' does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the specified domain (or type) is not found.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPDOMAIN-1">
-  <refsect1info>
-   <date>2002-02-24</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP DOMAIN</command> will remove a user domain from the
-   system catalogs.
-  </para>
-  <para>
-   Only the owner of a domain can remove it.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPDOMAIN-notes">
-  <title>Notes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     It is the user's responsibility to remove any operators,
-     functions, aggregates, access methods, and tables that
-     use a deleted domain.
-    </para>
-   </listitem>
-  </itemizedlist>
- </refsect1>
-
- <refsect1 id="SQL-DROPDOMAIN-examples">
-  <title>Examples</title>
-  <para>
-   To remove the <type>box</type> domain:
-
-<programlisting>
-DROP DOMAIN box;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPDOMAIN-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   A <command>DROP DOMAIN</command> statement exists in SQL99.  As with
-   most other <quote>drop</quote> commands, <command>DROP
-   DOMAIN</command> in SQL99 requires a <quote>drop behavior</quote>
-   clause to select between dropping all dependent objects or refusing
-   to drop if dependent objects exist:
-<synopsis>
-DROP DOMAIN <replaceable>name</replaceable> { CASCADE | RESTRICT }
-</synopsis>
-   <productname>PostgreSQL</productname> accepts only the RESTRICT
-   option, and currently does not check for existence of dependent objects.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPDOMAIN-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createdomain"></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_function.sgml b/doc/src/sgml/ref/drop_function.sgml
deleted file mode 100644
index 268d8c66e8c..00000000000
--- a/doc/src/sgml/ref/drop_function.sgml
+++ /dev/null
@@ -1,175 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.20 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPFUNCTION">
- <refmeta>
-  <refentrytitle id="SQL-DROPFUNCTION-TITLE">DROP FUNCTION</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP FUNCTION
-  </refname>
-  <refpurpose>
-   remove a user-defined function
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP FUNCTION <replaceable class="parameter">name</replaceable> ( [ <replaceable class="parameter">type</replaceable> [, ...] ] )
-  </synopsis>
-
-  <refsect2 id="R2-SQL-DROPFUNCTION-1">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <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">type</replaceable></term>
-      <listitem>
-       <para>
-	The type of a parameter of the function.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPFUNCTION-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP FUNCTION
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the command completes successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  RemoveFunction: Function "<replaceable class="parameter">name</replaceable>" ("<replaceable class="parameter">types</replaceable>") does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message is given if the function specified does not
-	exist in the current database.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPFUNCTION-1">
-  <refsect1info>
-   <date>1998-04-15</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   DROP FUNCTION will remove the definition of an existing
-   function. To execute this command the user must be the
-   owner of the function. The input argument types to the
-   function must be specified, since several different functions
-   may exist with the same name and different argument lists.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPFUNCTION-notes">
-  <title>Notes</title>
-
-   <para>
-    Refer to
-    <xref linkend="sql-createfunction">
-    for information on creating functions.
-   </para>
-
-   <para>
-    No checks are made to ensure that types, operators, access
-    methods, or triggers that rely on the function have been removed first.
-   </para>
- </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 SQL99.  One of its syntax forms is:
-
-<synopsis>
-DROP FUNCTION <replaceable class="parameter">name</replaceable> (<replaceable>arg</>, ...) { RESTRICT | CASCADE }
-</synopsis>
-
-   where <literal>CASCADE</> specifies dropping all objects that
-   depend on the function and <literal>RESTRICT</literal> refuses to
-   drop the function if dependent objects exist.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createfunction"></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_group.sgml b/doc/src/sgml/ref/drop_group.sgml
deleted file mode 100644
index bb1d7224bb9..00000000000
--- a/doc/src/sgml/ref/drop_group.sgml
+++ /dev/null
@@ -1,136 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_group.sgml,v 1.4 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPGROUP">
- <refmeta>
-  <refentrytitle id="SQL-DROPGROUP-TITLE">DROP GROUP</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP GROUP
-  </refname>
-  <refpurpose>
-   remove a user group
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-01-14</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP GROUP <replaceable class="PARAMETER">name</replaceable>
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-DROPGROUP-1">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of an existing group.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-DROPGROUP-2">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>DROP GROUP</computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the group is successfully deleted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPGROUP-1">
-  <refsect1info>
-   <date>2000-01-14</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP GROUP</command> removes the specified group from the database.
-   The users in the group are not deleted.
-  </para>
-  <para>
-   Use <xref linkend="SQL-CREATEGROUP" endterm="SQL-CREATEGROUP-title">
-   to add new groups, and <xref linkend="SQL-ALTERGROUP"
-   endterm="SQL-ALTERGROUP-title"> to change a group's membership.
-  </para>  
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPGROUP-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To drop a group:
-<programlisting>
-DROP GROUP staff;
-</programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-DROPGROUP-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-DROPGROUP-4">
-   <refsect2info>
-    <date>2000-01-14</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>DROP GROUP</command> in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_index.sgml b/doc/src/sgml/ref/drop_index.sgml
deleted file mode 100644
index 0db2c609461..00000000000
--- a/doc/src/sgml/ref/drop_index.sgml
+++ /dev/null
@@ -1,167 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_index.sgml,v 1.15 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPINDEX">
- <refmeta>
-  <refentrytitle id="SQL-DROPINDEX-TITLE">DROP INDEX</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP INDEX
-  </refname>
-  <refpurpose>
-   remove an index
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP INDEX <replaceable class="PARAMETER">index_name</replaceable> [, ...]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-DROPINDEX-1">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">index_name</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of an index to remove.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPINDEX-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP INDEX
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the command completes successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: index "<replaceable class="PARAMETER">index_name</replaceable>" does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if <replaceable class="PARAMETER">index_name</replaceable>
-	is not an index in the database.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPINDEX-1">
-  <refsect1info>
-   <date>1998-04-15</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <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>
-
-  <refsect2 id="R2-SQL-DROPINDEX-3">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    <command>DROP INDEX</command> is a <productname>PostgreSQL</productname>
-    language extension.
-   </para>
-   <para>
-    Refer to 
-    <xref linkend="sql-createindex" endterm="sql-createindex-title">
-    for information on how to create indexes.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPINDEX-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   This command will remove the <literal>title_idx</literal> index:
-
-   <programlisting>
-    DROP INDEX title_idx;
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPINDEX-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-DROPINDEX-4">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <acronym>SQL92</acronym> defines commands by which to access
-    a generic relational database.
-    Indexes are an implementation-dependent feature and hence
-    there are no index-specific commands or definitions in the
-    <acronym>SQL92</acronym> language.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_language.sgml b/doc/src/sgml/ref/drop_language.sgml
deleted file mode 100644
index 08badab8083..00000000000
--- a/doc/src/sgml/ref/drop_language.sgml
+++ /dev/null
@@ -1,174 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_language.sgml,v 1.14 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPLANGUAGE">
- <refmeta>
-  <refentrytitle id="SQL-DROPLANGUAGE-TITLE">DROP LANGUAGE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP LANGUAGE
-  </refname>
-  <refpurpose>
-   remove a user-defined procedural language
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP [ PROCEDURAL ] LANGUAGE <replaceable class="PARAMETER">name</replaceable>
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-DROPLANGUAGE-1">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of an existing procedural language.  For backward
-        compatibility, the name may be enclosed by single quotes.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-DROPLANGUAGE-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP LANGUAGE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message is returned if the language is successfully dropped.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: Language "<replaceable class="parameter">name</replaceable>" doesn't exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if a language called
-	<replaceable class="parameter">name</replaceable> is
-	not found in the database.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-SQL-DROPLANGUAGE-1">
-  <refsect1info>
-   <date>1998-04-15</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP PROCEDURAL LANGUAGE</command> will remove the definition
-   of the previously registered procedural language called
-   <replaceable class="parameter">name</replaceable>.
-  </para>
-  
-  <refsect2 id="R2-SQL-DROPLANGUAGE-3">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    The <command>DROP PROCEDURAL LANGUAGE</command> statement is
-    a <productname>PostgreSQL</productname> language extension.
-   </para>
-   <para>
-    Refer to
-    <xref linkend="sql-createlanguage" endterm="sql-createlanguage-title">
-    for information on how to create procedural languages.
-   </para>
-
-   <para>
-    No checks are made if functions or trigger procedures registered
-    in this language still exist. To re-enable them without having
-    to drop and recreate all the functions, the pg_proc's prolang
-    attribute of the functions must be adjusted to the new object
-    ID of the recreated pg_language entry for the PL.
-   </para>
-  </refsect2>
- </refsect1>
- 
- <refsect1 id="R1-SQL-DROPLANGUAGE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   This command removes the PL/Sample language:
-
-   <programlisting>
-DROP LANGUAGE plsample;
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-DROPLANGUAGE-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-DROPLANGUAGE-5">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>DROP PROCEDURAL LANGUAGE</command> in 
-    <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_operator.sgml b/doc/src/sgml/ref/drop_operator.sgml
deleted file mode 100644
index bc4657038fd..00000000000
--- a/doc/src/sgml/ref/drop_operator.sgml
+++ /dev/null
@@ -1,225 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_operator.sgml,v 1.16 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPOPERATOR">
- <refmeta>
-  <refentrytitle id="SQL-DROPOPERATOR-TITLE">DROP OPERATOR</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP OPERATOR
-  </refname>
-  <refpurpose>
-   remove a user-defined operator
-  </refpurpose>
- </refnamediv>
-  
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP OPERATOR <replaceable class="PARAMETER">id</replaceable> ( <replaceable class="PARAMETER">lefttype</replaceable> | NONE , <replaceable class="PARAMETER">righttype</replaceable> | NONE )
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-DROPOPERATOR-1">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">id</replaceable></term>
-      <listitem>
-       <para>
-	The identifier (optionally schema-qualified) of an existing operator.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">lefttype</replaceable></term>
-      <listitem>
-       <para>
-	The type of the operator's left argument; write <literal>NONE</literal> if the
-	operator has no left argument.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">righttype</replaceable></term>
-      <listitem>
-       <para>
-	The type of the operator's right argument; write <literal>NONE</literal> if the
-	operator has no right argument.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPOPERATOR-2">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP OPERATOR
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the command is successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  RemoveOperator: binary operator '<replaceable class="PARAMETER">oper</replaceable>' taking '<replaceable class="PARAMETER">lefttype</replaceable>' and '<replaceable class="PARAMETER">righttype</replaceable>' does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the specified binary operator does not exist.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: RemoveOperator: left unary operator '<replaceable class="PARAMETER">oper</replaceable>' taking '<replaceable class="PARAMETER">lefttype</replaceable>' does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the left unary operator
-	specified does not exist.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: RemoveOperator: right unary operator '<replaceable class="PARAMETER">oper</replaceable>' taking '<replaceable class="PARAMETER">righttype</replaceable>' does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the right unary operator
-	specified does not exist.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPOPERATOR-1">
-  <refsect1info>
-   <date>1998-09-22</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP OPERATOR</command> drops an existing operator from the
-   database.
-   To execute this command you must be the owner of the operator.
-  </para>
-  <para>
-   The left or right type of a left or right unary
-   operator, respectively, must be specified as <literal>NONE</literal>.
-  </para>
-
-  <refsect2 id="R2-SQL-DROPOPERATOR-3">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    The <command>DROP OPERATOR</command> statement is a 
-    <productname>PostgreSQL</productname>
-    language extension.
-   </para>
-   <para>
-    Refer to
-    <xref linkend="sql-createoperator" endterm="sql-createoperator-title">
-    for information on how to create operators.
-   </para>
-   <para>
-    It is the user's responsibility to remove any access method
-    operator classes that rely on the deleted operator.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPOPERATOR-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Remove power operator <literal>a^n</literal> for <literal>int4</literal>:
-
-   <programlisting>
-DROP OPERATOR ^ (int4, int4);
-   </programlisting>
-  </para>
-  <para>
-   Remove left unary negation operator (<literal>! b</literal>) for <type>boolean</type>:
-   <programlisting>
-DROP OPERATOR ! (none, bool);
-   </programlisting>
-  </para>
-  <para>
-   Remove right unary factorial operator (<literal>i !</literal>) for
-   <literal>int4</literal>:
-   <programlisting>
-DROP OPERATOR ! (int4, none);
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-DROPOPERATOR-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-DROPOPERATOR-4">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>DROP OPERATOR</command> in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_rule.sgml b/doc/src/sgml/ref/drop_rule.sgml
deleted file mode 100644
index 4f8ea97f88d..00000000000
--- a/doc/src/sgml/ref/drop_rule.sgml
+++ /dev/null
@@ -1,173 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_rule.sgml,v 1.15 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPRULE">
- <refmeta>
-  <refentrytitle id="SQL-DROPRULE-TITLE">DROP RULE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP RULE
-  </refname>
-  <refpurpose>
-   remove a rewrite rule
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1998-09-22</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP RULE <replaceable class="PARAMETER">name</replaceable> ON <replaceable class="PARAMETER">relation</replaceable>
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-DROPRULE-1">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of an existing rule to drop.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="parameter">relation</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of the relation the rule
-	applies to.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPRULE-2">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP RULE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  Rule "<replaceable class="parameter">name</replaceable>" not found
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the specified rule does not exist.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPRULE-1">
-  <refsect1info>
-   <date>1998-09-22</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP RULE</command> drops a rule from the specified
-   <productname>PostgreSQL</productname> rule
-   system. <productname>PostgreSQL</productname>
-   will immediately cease enforcing it and
-   will purge its definition from the system catalogs.
-  </para>
-
-  <refsect2 id="R2-SQL-DROPRULE-3">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    The <command>DROP RULE</command> statement is a
-    <productname>PostgreSQL</productname>
-    language extension.
-   </para>
-
-   <para>
-    Refer to <command>CREATE RULE</command> for
-    information on how to create rules.
-   </para>
-  </refsect2>
- </refsect1>
-  
- <refsect1 id="R1-SQL-DROPRULE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To drop the rewrite rule <literal>newrule</literal>:
-
-   <programlisting>
-DROP RULE newrule ON mytable;
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-DROPRULE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-DROPRULE-5">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>DROP RULE</command> in SQL92.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_sequence.sgml b/doc/src/sgml/ref/drop_sequence.sgml
deleted file mode 100644
index 4c371164e1e..00000000000
--- a/doc/src/sgml/ref/drop_sequence.sgml
+++ /dev/null
@@ -1,163 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_sequence.sgml,v 1.14 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPSEQUENCE">
- <refmeta>
-  <refentrytitle id="SQL-DROPSEQUENCE-TITLE">DROP SEQUENCE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP SEQUENCE
-  </refname>
-  <refpurpose>
-   remove a sequence
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP SEQUENCE <replaceable class="PARAMETER">name</replaceable> [, ...]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-DROPSEQUENCE-1">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of a sequence.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPSEQUENCE-2">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP SEQUENCE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the sequence is successfully dropped.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: sequence "<replaceable class="parameter">name</replaceable>" does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the specified sequence does not exist.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPSEQUENCE-1">
-  <refsect1info>
-   <date>1998-09-22</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP SEQUENCE</command> removes sequence number generators from the
-   data base. With the current implementation of sequences as
-   special tables it works just like the <command>DROP TABLE</command>
-   statement.
-  </para>
-
-  <refsect2 id="R2-SQL-DROPSEQUENCE-3">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    The <command>DROP SEQUENCE</command> statement is a
-    <productname>PostgreSQL</productname>
-    language extension.
-   </para>
-   <para>
-    Refer to the <command>CREATE SEQUENCE</command> statement for
-    information on how to create a sequence.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPSEQUENCE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To remove sequence <literal>serial</literal> from database:
-
-   <programlisting>
-DROP SEQUENCE serial;
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-DROPSEQUENCE-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-DROPSEQUENCE-4">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>DROP SEQUENCE</command> in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_table.sgml b/doc/src/sgml/ref/drop_table.sgml
deleted file mode 100644
index cae3275067d..00000000000
--- a/doc/src/sgml/ref/drop_table.sgml
+++ /dev/null
@@ -1,196 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_table.sgml,v 1.15 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTABLE">
- <refmeta>
-  <refentrytitle id="SQL-DROPTABLE-TITLE">DROP TABLE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP TABLE
-  </refname>
-  <refpurpose>
-   remove a table
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP TABLE <replaceable class="PARAMETER">name</replaceable> [, ...]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-DROPTABLE-1">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of an existing table to drop.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPTABLE-2">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP TABLE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the command completes successfully.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: table "<replaceable class="parameter">name</replaceable>" does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If the specified table does not exist in the database.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-SQL-DROPTABLE-1">
-  <refsect1info>
-   <date>1998-09-22</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP TABLE</command> removes tables from the database.
-   Only its owner may destroy a table. A table may be emptied of rows, but not
-   destroyed, by using <command>DELETE</command>.
-  </para>
-  <para>
-   If a table being destroyed has secondary indexes on it,
-   they will be removed first. The removal of just a
-   secondary index will not affect the contents of the underlying table.
-  </para>
-  <para>
-   <command>DROP TABLE</command> will also remove any rules or triggers
-   that exist for the target table.
-  </para>
-
-  <refsect2 id="R2-SQL-DROPTABLE-3">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    Refer to <command>CREATE TABLE</command> and
-    <command>ALTER TABLE</command> for information on
-    how to create or modify tables.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPTABLE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To destroy two tables, <literal>films</literal> and 
-   <literal>distributors</literal>:
-
-   <programlisting>
-DROP TABLE films, distributors;
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-DROPTABLE-3">
-   <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-DROPTABLE-4">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    SQL92 specifies some additional capabilities for DROP TABLE:
-   </para>
-   <synopsis>
-DROP TABLE <replaceable class="parameter">table</replaceable> { RESTRICT | CASCADE }
-   </synopsis>
-   <variablelist>
-    <varlistentry>
-     <term>RESTRICT</term>
-     <listitem>
-      <para>
-       Ensures that only a table with no dependent views or
-       integrity constraints can be destroyed.
-      </para>
-     </listitem>
-    </varlistentry>
-    <varlistentry>
-     <term>CASCADE</term>
-     <listitem>
-      <para>
-       Any referencing views or integrity constraints
-       will also be dropped.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-    <tip>
-    <para>
-     At present, to remove a referencing view you must drop
-     it explicitly.
-    </para>
-   </tip>
-   </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_trigger.sgml b/doc/src/sgml/ref/drop_trigger.sgml
deleted file mode 100644
index e4f157b1d7c..00000000000
--- a/doc/src/sgml/ref/drop_trigger.sgml
+++ /dev/null
@@ -1,172 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_trigger.sgml,v 1.12 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTRIGGER">
- <refmeta>
-  <refentrytitle id="SQL-DROPTRIGGER-TITLE">DROP TRIGGER</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP TRIGGER
-  </refname>
-  <refpurpose>
-   remove a trigger
-  </refpurpose> 
- </refnamediv>            
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1998-09-22</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP TRIGGER <replaceable class="PARAMETER">name</replaceable> ON <replaceable class="PARAMETER">table</replaceable>
-  </synopsis>
-
-  <refsect2 id="R2-SQL-DROPTRIGGER-1">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of an existing trigger.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">table</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of a table.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPTRIGGER-2">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP TRIGGER
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the trigger is successfully dropped.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: DropTrigger: there is no trigger <replaceable class="PARAMETER">name</replaceable> on relation "<replaceable class="parameter">table</replaceable>"
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the trigger specified does not exist.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPTRIGGER-1">
-  <refsect1info>
-   <date>1998-09-22</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP TRIGGER</command> will remove 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 id="SQL-DROPTRIGGER-examples">
-  <title>Examples</title>
-
-  <para>
-   Destroy the <literal>if_dist_exists</literal> trigger
-   on table <literal>films</literal>:
-
-<programlisting>
-DROP TRIGGER if_dist_exists ON films;
-</programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="SQL-DROPTRIGGER-compatibility">
-  <title>Compatibility</title>
-  
-  <variablelist>
-   <varlistentry>
-    <term>SQL92</term>
-    <listitem>
-     <para>
-      There is no <command>DROP TRIGGER</command> statement in
-      <acronym>SQL92</acronym>.
-     </para>
-    </listitem>
-   </varlistentry>
-
-   <varlistentry>
-    <term>SQL99</term>
-    <listitem>
-     <para>
-      The <command>DROP TRIGGER</command> statement in
-      <productname>PostgreSQL</productname> is incompatible with
-      SQL99.  In SQL99, trigger names are not local to tables, so the
-      command is simply <literal>DROP TRIGGER
-      <replaceable>name</replaceable></literal>.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtrigger"></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_type.sgml b/doc/src/sgml/ref/drop_type.sgml
deleted file mode 100644
index 3ac0f17ae9f..00000000000
--- a/doc/src/sgml/ref/drop_type.sgml
+++ /dev/null
@@ -1,179 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.17 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPTYPE">
- <refmeta>
-  <refentrytitle id="SQL-DROPTYPE-TITLE">DROP TYPE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP TYPE
-  </refname>
-  <refpurpose>
-   remove a user-defined data type
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP TYPE <replaceable class="PARAMETER">typename</replaceable> [, ...]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-DROPTYPE-1">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">typename</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of an existing type.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPTYPE-2">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP TYPE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the command is successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  RemoveType: type '<replaceable class="parameter">typename</replaceable>' does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the specified type is not found.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPTYPE-1">
-  <refsect1info>
-   <date>1998-09-22</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP TYPE</command> will remove a user type from the
-   system catalogs.
-  </para>
-  <para>
-   Only the owner of a type can remove it.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPTYPE-notes">
-  <title>Notes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     It is the user's responsibility to remove any operators,
-     functions, aggregates, access methods, subtypes, and tables that
-     use a deleted type.  However, the associated array data type
-     (which was automatically created by <command>CREATE TYPE</command>)
-     will be removed automatically.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     If a built-in type is removed, the behavior of the server is
-     unpredictable.
-    </para>
-   </listitem>
-  </itemizedlist>
- </refsect1>
-  
- <refsect1 id="SQL-DROPTYPE-examples">
-  <title>Examples</title>
-  <para>
-   To remove the <type>box</type> type:
-
-<programlisting>
-DROP TYPE box;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPTYPE-compatibility">
-  <title>Compatibility</title>
-
-  <para>
-   A <command>DROP TYPE</command> statement exists in SQL99.  As with
-   most other <quote>drop</quote> commands, <command>DROP
-   TYPE</command> in SQL99 requires a <quote>drop behavior</quote>
-   clause to select between dropping all dependent objects or refusing
-   to drop if dependent objects exist:
-<synopsis>
-DROP TYPE <replaceable>name</replaceable> { CASCADE | RESTRICT }
-</synopsis>
-   <productname>PostgreSQL</productname> currently ignores
-   dependencies altogether.
-  </para>
-
-  <para>
-   Note that the <command>CREATE TYPE</command> command and the data
-   type extension mechanisms in <productname>PostgreSQL</productname>
-   differ from SQL99.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-DROPTYPE-see-also">
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createtype"></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_user.sgml b/doc/src/sgml/ref/drop_user.sgml
deleted file mode 100644
index d7f3af80b82..00000000000
--- a/doc/src/sgml/ref/drop_user.sgml
+++ /dev/null
@@ -1,148 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_user.sgml,v 1.15 2002/02/27 21:14:54 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPUSER">
- <refmeta>
-  <refentrytitle id="SQL-DROPUSER-TITLE">DROP USER</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>DROP USER</refname>
-  <refpurpose>remove a database user account</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-DROP USER <replaceable class="PARAMETER">name</replaceable>
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>DROP USER</command> removes the specified user from the database.
-   It does not remove tables, views, or other objects owned by the user. If the
-   user owns any database, an error is raised.
-  </para>
-
-  <refsect2>
-   <title>Parameters</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of an existing user.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
- </refsect1>
-
- <refsect1>
-  <title>Diagnostics</title>
-
-  <para>
-   <variablelist>
-    <varlistentry>
-     <term><computeroutput>DROP USER</computeroutput></term>
-     <listitem>
-      <para>
-       The message returned if the user is successfully deleted.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><computeroutput>ERROR:  DROP USER: user "<replaceable class="parameter">name</replaceable>" does not exist</computeroutput></term>
-     <listitem>
-      <para>
-       This message occurs if the user name is not found.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><computeroutput>DROP USER: user "<replaceable class="parameter">name</replaceable>" owns database "<replaceable class="parameter">name</replaceable>", cannot be removed</computeroutput></term>
-     <listitem>
-      <para>
-       You must drop the database first or change its ownership.
-      </para>
-     </listitem>
-    </varlistentry>
-
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="SQL-CREATEUSER" endterm="SQL-CREATEUSER-title">
-   to add new users, and <xref linkend="SQL-ALTERUSER"
-   endterm="SQL-ALTERUSER-title"> to change a user's attributes.
-   <productname>PostgreSQL</productname> includes a program <xref
-   linkend="APP-DROPUSER" endterm="APP-DROPUSER-title"> 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 user account:
-<programlisting>
-DROP USER jonathan;
-</programlisting>
-  </para>
- </refsect1>
- 
- <refsect1>
-  <title>Compatibility</title>
-  
-  <para>
-   The <command>DROP USER</command> statement is a
-   <productname>PostgreSQL</productname> extension.  The SQL standard
-   leaves the definition of users to the implementation.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="sql-createuser" endterm="sql-createuser-title"></member>
-   <member><xref linkend="sql-alteruser" endterm="sql-alteruser-title"></member>
-   <member><xref linkend="app-dropuser"></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/drop_view.sgml b/doc/src/sgml/ref/drop_view.sgml
deleted file mode 100644
index a789e38c4ce..00000000000
--- a/doc/src/sgml/ref/drop_view.sgml
+++ /dev/null
@@ -1,208 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_view.sgml,v 1.14 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-DROPVIEW">
- <refmeta>
-  <refentrytitle id="SQL-DROPVIEW-TITLE">DROP VIEW</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   DROP VIEW
-  </refname>
-  <refpurpose>
-   remove a view
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-DROP VIEW <replaceable class="PARAMETER">name</replaceable> [, ...]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-DROPVIEW-1">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of an existing view.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-DROPVIEW-2">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-DROP VIEW
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The message returned if the command is successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-ERROR: view <replaceable class="parameter">name</replaceable> does not exist
-       </computeroutput></term>
-      <listitem>
-       <para>
-	This message occurs if the specified view does not exist in
-	the database.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-DROPVIEW-1">
-  <refsect1info>
-   <date>1998-09-22</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>DROP VIEW</command> drops an existing view from the database.
-   To execute this command you must be the owner of the
-   view.
-  </para>
-
-  <refsect2 id="R2-SQL-DROPVIEW-3">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    Refer to <xref linkend="sql-createview">
-    for information on how to create views.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-DROPVIEW-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   This command will remove the view called <literal>kinds</literal>:
-  </para>
-  <programlisting>
-DROP VIEW kinds;
-  </programlisting>
- </refsect1>
- 
- <refsect1 id="R1-SQL-DROPVIEW-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-DROPVIEW-4">
-   <refsect2info>
-    <date>1998-09-22</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <acronym>SQL92</acronym> specifies some additional capabilities for
-    <command>DROP VIEW</command>:
-   
-    <synopsis>
-DROP VIEW <replaceable class="parameter">view</replaceable> { RESTRICT | CASCADE }
-    </synopsis>
-   </para>
-
-   <refsect3 id="R3-SQL-DROPVIEW-1">
-    <refsect3info>
-     <date>1998-09-22</date>
-    </refsect3info>
-    <title>
-     Inputs
-    </title>
-    <para>
-     <variablelist>
-      <varlistentry>
-       <term>RESTRICT</term>
-       <listitem>
-	<para>
-	 Ensures that only a view with no dependent views or
-	 integrity constraints can be destroyed.
-	</para>
-       </listitem>
-      </varlistentry>
-      <varlistentry>
-       <term>CASCADE</term>
-       <listitem>
-	<para>
-	 Any referencing views and integrity constraints
-	 will be dropped as well.
-	</para>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-   </refsect3>
-
-  <refsect3 id="R3-SQL-DROPVIEW-2">
-   <refsect3info>
-    <date>1998-09-22</date>
-   </refsect3info>
-   <title>
-    Notes
-    </title>
-    <para>
-     At present, to remove a referencing view from a
-     <productname>PostgreSQL</productname> database, 
-     you must drop it explicitly.
-    </para>
-   </refsect3>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/dropdb.sgml b/doc/src/sgml/ref/dropdb.sgml
deleted file mode 100644
index ecbfef2b82e..00000000000
--- a/doc/src/sgml/ref/dropdb.sgml
+++ /dev/null
@@ -1,221 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropdb.sgml,v 1.15 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-DROPDB">
- <refmeta>
-  <refentrytitle id="APP-DROPDB-TITLE"><application>dropdb</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>dropdb</refname>
-  <refpurpose>remove a <productname>PostgreSQL</productname> database</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>dropdb</command>
-   <arg rep="repeat"><replaceable>options</replaceable></arg>
-   <arg choice="plain"><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <refsect2 id="R2-APP-DROPDB-1">
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>-h, --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>-p, --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>-U, --username <replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-        User name to connect as
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-W, --password</term>
-      <listitem>
-       <para>
-        Force password prompt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-e, --echo</term>
-      <listitem>
-       <para>
-        Echo the queries that <application>dropdb</application> generates
-	and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-q, --quiet</term>
-      <listitem>
-       <para>
-        Do not display a response.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-i, --interactive</term>
-      <listitem>
-       <para>
-       Issues a verification prompt before doing anything destructive.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">dbname</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the name of the database to be removed.  The database
-	must be one of the existing <productname>PostgreSQL</productname> databases
-	in this installation.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    The options <literal>-h</literal>, <literal>-p</literal>, <literal>-U</literal>,
-    <literal>-W</literal>, and <literal>-e</literal> are passed on literally to
-    <xref linkend="APP-PSQL">.
-   </para>
-  </refsect2>
-
-
-  <refsect2 id="R2-APP-DROPDB-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>DROP DATABASE</computeroutput></term>
-      <listitem>
-       <para>The database was successfully removed.</para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>dropdb: Database removal failed.</computeroutput></term>
-      <listitem>
-       <para>Something didn't work out.</para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    If there is an error condition, the backend error message will be displayed.
-    See <xref linkend="SQL-DROPDATABASE" endterm="SQL-DROPDATABASE-title">
-    and <xref linkend="APP-PSQL"> for possibilities.
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
-
- <refsect1 id="R1-APP-DROPDB-1">
-  <title>
-   Description
-  </title>
-  <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 shell script wrapper around the
-   <acronym>SQL</acronym> command
-   <xref linkend="SQL-DROPDATABASE" endterm="SQL-DROPDATABASE-title"> via
-   the <productname>PostgreSQL</productname> interactive terminal
-   <xref linkend="APP-PSQL">. Thus, there is nothing
-   special about dropping databases via this or other methods. This means
-   that the <application>psql</application> must be found by the script and that
-   a database server is running at the targeted host. Also, any default
-   settings and environment variables available to <application>psql</application>
-   and the <application>libpq</application> front-end library do apply.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-APP-DROPDB-2">
-  <title>Usage</title>
-
-  <informalexample>
-   <para>
-    To destroy the database <literal>demo</literal> on the default
-    database server:
-<screen>
-<prompt>$ </prompt><userinput>dropdb demo</userinput>
-<computeroutput>DROP DATABASE</computeroutput>
-</screen>
-   </para>
-  </informalexample>
-
-  <informalexample>
-   <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 query:
-<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"
-DROP DATABASE</computeroutput>
-</screen>
-   </para>
-  </informalexample>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/droplang.sgml b/doc/src/sgml/ref/droplang.sgml
deleted file mode 100644
index c6eadb401f8..00000000000
--- a/doc/src/sgml/ref/droplang.sgml
+++ /dev/null
@@ -1,206 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/droplang.sgml,v 1.18 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-DROPLANG">
- <refmeta>
-  <refentrytitle id="APP-DROPLANG-TITLE"><application>droplang</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname id="droplang">droplang</refname>
-  <refpurpose>remove a <productname>PostgreSQL</productname> procedural language</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>droplang</command>
-   <arg rep="repeat"><replaceable>connection-options</replaceable></arg>
-   <arg choice="plain"><replaceable>langname</replaceable></arg>
-   <arg><replaceable>dbname</replaceable></arg>
-   <sbr>
-   <command>droplang</command>
-   <arg rep="repeat"><replaceable>connection-options</replaceable></arg>
-   <group choice="plain"><arg>--list</arg><arg>-l</arg></group>
-   <arg choice="plain"><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <refsect2 id="R2-APP-DROPLANG-1">
-   <title>
-    Inputs
-   </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 backend programming language to be removed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>[-d, --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>-e, --echo</term>
-      <listitem>
-       <para>
-        Displays SQL commands as they are executed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-l, --list</term>
-      <listitem>
-       <para>
-        Shows a list of already installed languages in the target database
-        (which must be specified).
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <application>droplang</application> also accepts 
-    the following command line arguments for connection parameters:
-    
-    <variablelist>
-     <varlistentry>
-      <term>-h, --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>-p, --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>-U, --username <replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-        User name to connect as
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-W, --password</term>
-      <listitem>
-       <para>
-        Force password prompt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-DROPLANG-2">
-   <title>
-    Outputs
-   </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. Check also under <xref linkend="APP-PSQL">
-    for more possibilities.
-   </para>
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-APP-DROPLANG-1">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <application>droplang</application> is a utility for removing an 
-   existing programming language from a
-   <productname>PostgreSQL</productname> database.
-   <application>droplang</application> can drop any procedural language,
-   even those not supplied by the <productname>PostgreSQL</> distribution.
-  </para>
-  <para>
-   Although backend programming languages can be removed directly using
-   several <acronym>SQL</acronym> commands, it is recommended to use
-   <application>droplang</application> because it performs a number
-   of checks and is much easier to use. See
-   <xref linkend="sql-droplanguage" endterm="sql-droplanguage-title">
-   for more.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-APP-DROPLANG-2">
-  <title>
-   Notes
-  </title>
-
-  <para>
-   Use <xref linkend="app-createlang"> to add a language.
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-APP-DROPLANG-3">
-  <title>Usage</title>
-
-  <informalexample>
-   <para>
-    To remove <literal>pltcl</literal>:
-<screen>
-<prompt>$ </prompt><userinput>droplang pltcl dbname</userinput>
-</screen>
-   </para>
-  </informalexample>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/dropuser.sgml b/doc/src/sgml/ref/dropuser.sgml
deleted file mode 100644
index 9741d10707a..00000000000
--- a/doc/src/sgml/ref/dropuser.sgml
+++ /dev/null
@@ -1,213 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/dropuser.sgml,v 1.18 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-DROPUSER">
- <refmeta>
-  <refentrytitle id="APP-DROPUSER-TITLE"><application>dropuser</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>dropuser</refname>
-  <refpurpose>remove a <productname>PostgreSQL</productname> user account</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>dropuser</command>
-   <arg rep="repeat"><replaceable>options</replaceable></arg>
-   <arg><replaceable>username</replaceable></arg>
-  </cmdsynopsis>
-
-  <refsect2 id="R2-APP-DROPUSER-1">
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>-h, --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>-p, --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>-e, --echo</term>
-      <listitem>
-       <para>
-        Echo the queries that <application>dropuser</application> generates
-	and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-q, --quiet</term>
-      <listitem>
-       <para>
-        Do not display a response.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-i, --interactive</term>
-      <listitem>
-       <para>
-        Prompt for confirmation before actually removing the user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the name of the <productname>PostgreSQL</productname> user to be removed. 
-	This name must exist in the <productname>PostgreSQL</productname> installation.
-	You will be prompted for a name if none is specified on the command line.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-    </para>
-
-    <para>
-    The options <literal>-h</literal>, <literal>-p</literal>, and <literal>-e</literal>,
-    are passed on literally to <xref linkend="APP-PSQL">. The
-    <application>psql</application> options <literal>-U</literal> and <literal>-W</literal>
-    are available as well, but they can be confusing in this context.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-DROPUSER-2">
-   <title>
-    Outputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>DROP USER</computeroutput></term>
-      <listitem>
-       <para>
-        All is well.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>dropuser: deletion of user "<replaceable class="parameter">username</replaceable>" failed</computeroutput></term>
-      <listitem>
-       <para>
-        Something went wrong. The user was not removed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-
-    If there is an error condition, the backend error message will be displayed.
-    See <xref linkend="SQL-DROPUSER" endterm="SQL-DROPUSER-title">
-    and <xref linkend="APP-PSQL"> for possibilities.
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-DROPUSER-1">
-  <title>
-   Description
-  </title>
-  <para>
-   <application>dropuser</application> removes an existing
-   <productname>PostgreSQL</productname> user
-   <emphasis>and</emphasis> the databases which that user owned.
-   Only users with <literal>usesuper</literal> set in
-   the <literal>pg_shadow</literal> table can destroy 
-   <productname>PostgreSQL</productname> users.
-  </para>
-
-  <para>
-   <application>dropuser</application> is a shell script wrapper around the
-   <acronym>SQL</acronym> command
-   <xref linkend="SQL-DROPUSER" endterm="SQL-DROPUSER-title"> via
-   the <productname>PostgreSQL</productname> interactive terminal
-   <xref linkend="APP-PSQL">. Thus, there is nothing
-   special about removing users via this or other methods. This means
-   that the <application>psql</application> must be found by the script and that
-   a database server is running at the targeted host. Also, any default
-   settings and environment variables available to <application>psql</application>
-   and the <application>libpq</application> front-end library do apply.
-  </para>
-
- </refsect1>
-
- <refsect1 id="R1-APP-DROPUSER-2">
-  <title>Usage</title>
-
-  <informalexample>
-   <para>
-    To remove user <literal>joe</literal> from the default database
-    server:
-<screen>
-<prompt>$ </prompt><userinput>dropuser joe</userinput>
-<computeroutput>DROP USER</computeroutput>
-</screen>
-   </para>
-  </informalexample>
-
-  <informalexample>
-   <para>
-    To remove user <literal>joe</literal> using the postmaster on host
-    <literal>eden</literal>, port 5000, with verification and a peek at the underlying
-    query:
-<screen>
-<prompt>$ </prompt><userinput>dropuser -p 5000 -h eden -i -e joe</userinput>
-<computeroutput>User "joe" and any owned databases will be permanently deleted.
-Are you sure? (y/n) </computeroutput><userinput>y</userinput>
-<computeroutput>DROP USER "joe"
-DROP USER</computeroutput>
-</screen>
-   </para>
-  </informalexample>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/ecpg-ref.sgml b/doc/src/sgml/ref/ecpg-ref.sgml
deleted file mode 100644
index e7e5a4a8a35..00000000000
--- a/doc/src/sgml/ref/ecpg-ref.sgml
+++ /dev/null
@@ -1,426 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.19 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-ECPG">
- <refmeta>
-  <refentrytitle id="app-ecpg-title"><application>ecpg</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   <application>ecpg</application>
-  </refname>
-  <refpurpose>
-   embedded SQL C preprocessor
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <cmdsynopsis>
-   <command>ecpg</command>
-   <arg choice="opt">-v</arg>
-   <arg choice="opt">-t</arg>
-   <arg choice="opt">-I <replaceable>include-path</replaceable></arg>
-   <arg choice="opt">-o <replaceable>outfile</replaceable></arg>
-   <arg choice="plain" rep="repeat"><replaceable>file</replaceable></arg>
-  </cmdsynopsis>
-
-  <refsect2 id="R2-APP-ECPG-1">
-   <refsect2info>
-    <date>1999-07-20</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    <application>ecpg</application> accepts the following command
-    line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term>-v</term>
-      <listitem>
-       <para>
-	Print version information. 
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-t</term>
-      <listitem>
-       <para>
-	Turn on auto-commit of transactions. In this mode, each query is
-	automatically committed unless it is inside an explicit
-	transaction block. In the default mode, queries are committed
-	only when <command>exec sql commit</command> is issued.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-I <replaceable class="parameter">include-path</replaceable></term>
-      <listitem>
-       <para>
-	Specify an additional include path.
-	Defaults are <filename>.</filename> (current directory),
-	<filename>/usr/local/include</filename>, the
-	<productname>PostgreSQL</productname> include path which is
-	defined at compile time (default:
-	<filename>/usr/local/pgsql/include</filename>), and
-	<filename>/usr/include</filename>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-o <replaceable>outfile</replaceable></term>
-      <listitem>
-       <para>
-	Specifies that <application>ecpg</application> should write all its output to <replaceable>outfile</replaceable>.
-	If no such option is given the output is written to
-	<filename><replaceable>name</replaceable>.c</filename>,
-	assuming the input file was 
-	named <filename><replaceable>name</replaceable>.pgc</filename>.
-	If the input file does have the expected
-	<literal>.pgc</literal> suffix, then the output file will have 
-	<literal>.pgc</literal> appended to the input file name.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="parameter">file</replaceable></term>
-      <listitem>
-       <para>
-	The files to be processed.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-ECPG-2">
-   <refsect2info>
-    <date>1998-11-05</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <application>ecpg</application> will create a file or
-    write to <filename>stdout</filename>.
-
-    <variablelist>
-     <varlistentry>
-      <term>Return value</term>
-      <listitem>
-       <para>
-	<application>ecpg</application> returns 0 to the shell on successful completion, non-zero
-	for errors.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-ECPG-description">
-  <title>Description</title>
-  <para>
-   <application>ecpg</application>
-   is an embedded SQL preprocessor for the C language and the
-   <productname>PostgreSQL</productname>. It
-   enables development of C programs with embedded SQL code.
-  </para>
-
-  <para>
-   Linus Tolke (<email>linus@epact.se</email>) was the
-   original author of <application>ecpg</application> (up to version 0.2).
-   Michael Meskes (<email>meskes@debian.org</email>)
-   is the current author and maintainer of <application>ecpg</application>.
-   Thomas Good (<email>tomg@q8.nrnet.org</email>)
-   is the author of the last revision of the <application>ecpg</application> man page, on which
-   this document is based.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-APP-ECPG-2">
-  <title>Usage</title>
-
-  <refsect2 id="R2-APP-ECPG-preprocessing">
-   <title>Preprocessing for Compilation</title>
-
-   <para>
-    An embedded SQL source file must be preprocessed before
-    compilation: 
-<synopsis>
-ecpg [ -d ] [ -o <replaceable>file</replaceable> ] <replaceable>file</replaceable>.pgc
-</synopsis>
-
-    where the optional <option>-d</option> flag turns on debugging.
-    The <literal>.pgc</literal> extension is an 
-    arbitrary means of denoting <application>ecpg</application> source.
-   </para>
-
-   <para>
-    You may want to redirect the preprocessor output to a log file.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-ECPG-compiling">
-   <title>Compiling and Linking</title>
-
-   <para>
-    Assuming the <productname>PostgreSQL</productname> binaries are in
-    <filename>/usr/local/pgsql</filename>, you will need to compile
-    and link your preprocessed source file:
-
-<synopsis>
-gcc -g -I /usr/local/pgsql/include [ -o <replaceable>file</replaceable> ] <replaceable>file</replaceable>.c -L /usr/local/pgsql/lib -lecpg -lpq
-</synopsis>
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-APP-ECPG-grammar">
-  <title>Grammar</title>
-
-  <refsect2 id="R2-APP-ECPG-library">
-   <title>Libraries</title>
-
-   <para>
-    The preprocessor will prepend two directives to the source:
-
-<programlisting>
-#include &lt;ecpgtype.h&gt;
-#include &lt;ecpglib.h&gt;
-</programlisting>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-declaration">
-   <title>Variable Declaration</title>
-
-   <para>
-    Variables declared within <application>ecpg</application> source code must be prepended with:
-
-<programlisting>
-EXEC SQL BEGIN DECLARE SECTION;
-</programlisting>
-   </para>
-
-   <para>
-    Similarly, variable declaration sections must terminate with:
-
-<programlisting>
-EXEC SQL END DECLARE SECTION;
-</programlisting>
-
-    <note>
-     <para>
-      Prior to version 2.1.0, each variable had to be declared 
-      on a separate line.  As of version 2.1.0 multiple variables may
-      be declared on a single line:
-<programlisting>
-char  foo[16], bar[16];
-</programlisting>
-     </para>
-    </note>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-ECPG-errors">
-   <title>Error Handling</title>
-
-   <para>
-    The SQL communication area is defined with:
-
-<programlisting>
-EXEC SQL INCLUDE sqlca;
-</programlisting>
-   </para>
-
-    <note>
-     <para>
-      The <literal>sqlca</literal> is in lowercase.
-      While SQL convention may be 
-      followed, i.e., using uppercase to separate embedded SQL 
-      from C statements, <literal>sqlca</literal> (which includes the <filename>sqlca.h</>
-      header file) <emphasis>must</> be lowercase.  This is because the
-      EXEC SQL prefix indicates that this inclusion will be parsed by
-      <application>ecpg</application>.
-      <application>ecpg</application> observes case sensitivity
-      (<filename>SQLCA.h</> will not be found).
-      <command>EXEC SQL INCLUDE</command>
-      can be used to include other header files
-      as long as case sensitivity is observed.
-     </para>
-    </note>
-
-   <para>
-    The <literal>sqlprint</literal> command is used with the <literal>EXEC SQL WHENEVER</literal>
-    statement to turn on error handling throughout the 
-    program:
-
-<programlisting>
-EXEC SQL WHENEVER sqlerror sqlprint;
-</programlisting>
-
-    and
-
-<programlisting>
-EXEC SQL WHENEVER not found sqlprint;
-</programlisting>
-   </para>
-
-    <note>
-     <para>
-      This is <emphasis>not</emphasis> an exhaustive example of usage for
-      the <command>EXEC SQL WHENEVER</command> statement.
-      Further examples of usage may
-      be found in SQL manuals (e.g., <citetitle>The LAN TIMES Guide to SQL</> by
-      Groff and Weinberg).
-     </para>
-    </note>
-  </refsect2>
-
-  <refsect2 id="R2-APP-ECPG-connecting">
-   <title>Connecting to the Database Server</title>
-
-   <para>
-    One connects to a database using the following:
-
-<programlisting>
-EXEC SQL CONNECT TO <replaceable>dbname</replaceable>;
-</programlisting>
-
-    where the database name is not quoted. Prior to version 2.1.0, the 
-    database name was required to be inside single quotes.
-   </para>
-
-   <para>
-    Specifying a server and port name in the connect statement is also 
-    possible. The syntax is:
-
-<synopsis>
-<replaceable>dbname</replaceable>[@<replaceable>server</replaceable>][:<replaceable>port</replaceable>]
-</synopsis>
-
-    or
-
-<synopsis>
-&lt;tcp|unix&gt;:postgresql://<replaceable>server</replaceable>[:<replaceable>port</replaceable>][/<replaceable>dbname</replaceable>][?<replaceable>options</replaceable>]
-</synopsis>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-ECPG-queries">
-   <title>Queries</title>
-
-   <para>
-    In general, SQL queries acceptable to other applications such as
-    <application>psql</application> can be embedded into your C
-    code. Here are some examples of how to do that.
-   </para>
-
-   <para>
-    Create Table:
-
-<programlisting>
-EXEC SQL CREATE TABLE foo (number int4, ascii char(16));
-EXEC SQL CREATE UNIQUE index num1 on foo(number);
-EXEC SQL COMMIT;
-</programlisting>
-   </para>
-
-   <para>
-    Insert:
-
-<programlisting>
-EXEC SQL INSERT INTO foo (number, ascii) VALUES (9999, 'doodad');
-EXEC SQL COMMIT;
-</programlisting>
-   </para>
-
-   <para>
-    Delete:
-
-<programlisting>
-EXEC SQL DELETE FROM foo WHERE number = 9999;
-EXEC SQL COMMIT;
-</programlisting>
-   </para>
-
-   <para>
-    Singleton Select:
-
-<programlisting>
-EXEC SQL SELECT foo INTO :FooBar FROM table1 WHERE ascii = 'doodad';
-</programlisting>
-   </para>
-
-   <para>
-    Select using Cursors:
-
-<programlisting>
-EXEC SQL DECLARE foo_bar CURSOR FOR
-    SELECT number, ascii FROM foo
-    ORDER BY ascii;
-EXEC SQL FETCH foo_bar INTO :FooBar, DooDad;
-...
-EXEC SQL CLOSE foo_bar;
-EXEC SQL COMMIT;
-</programlisting>
-   </para>
-
-   <para>
-    Updates:
-<programlisting>
-EXEC SQL UPDATE foo
-    SET ascii = 'foobar'
-    WHERE number = 9999;
-EXEC SQL COMMIT;
-</programlisting>
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-APP-ECPG-notes">
-  <title>Notes</title>
-  <para>
-   The complete structure definition MUST be listed
-   inside the declare section.
-  </para>
-
-  <para>
-   See the <filename>TODO</filename> file in the source for some more
-   missing features.
-  </para>
-
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/end.sgml b/doc/src/sgml/ref/end.sgml
deleted file mode 100644
index 3852f742863..00000000000
--- a/doc/src/sgml/ref/end.sgml
+++ /dev/null
@@ -1,168 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.8 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-END">
- <refmeta>
-  <refentrytitle id="SQL-END-TITLE">END</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   END
-  </refname>
-  <refpurpose>
-   commit the current transaction
-  </refpurpose>
- </refnamediv>  
-  
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-END [ WORK | TRANSACTION ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-END-1">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>WORK</term>
-      <term>TRANSACTION</term>
-      <listitem>
-       <para>
-	Optional keywords. They have no effect.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-   
-  <refsect2 id="R2-SQL-END-2">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-COMMIT
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the transaction is successfully committed.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  COMMIT: no transaction in progress
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If there is no transaction in progress.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-  
- <refsect1 id="R1-SQL-END-1">
-  <refsect1info>
-   <date>1998-09-08</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>END</command> is a <productname>PostgreSQL</productname>
-   extension, and is a synonym for the SQL92-compatible
-   <xref linkend="sql-commit" endterm="sql-commit-title">.
-  </para>
-  
-  <refsect2 id="R2-SQL-END-3">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    The keywords WORK and TRANSACTION are noise and can be omitted.
-   </para>
-
-   <para>
-    Use <xref linkend="SQL-ROLLBACK" endterm="SQL-ROLLBACK-TITLE">
-    to abort a transaction.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-END-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To make all changes permanent:
-
-   <programlisting>
-END WORK;
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-END-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-END-4">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    <command>END</command> is a <productname>PostgreSQL</productname>
-    extension which provides functionality equivalent to
-    <xref linkend="sql-commit" endterm="sql-commit-title">.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml
deleted file mode 100644
index 6a5d1c037cf..00000000000
--- a/doc/src/sgml/ref/explain.sgml
+++ /dev/null
@@ -1,274 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/explain.sgml,v 1.20 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-EXPLAIN">
- <refmeta>
-  <refentrytitle id="SQL-EXPLAIN-TITLE">EXPLAIN</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   EXPLAIN
-  </refname>
-  <refpurpose>
-   show the execution plan of a statement
-  </refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-EXPLAIN [ ANALYZE ] [ VERBOSE ] <replaceable class="PARAMETER">query</replaceable>        
-  </synopsis>
-
-  <refsect2 id="R2-SQL-EXPLAIN-1">
-   <refsect2info>
-    <date>1998-09-01</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>ANALYZE</term>
-      <listitem>
-       <para>
-	Flag to carry out the query and show actual run times.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>VERBOSE</term>
-      <listitem>
-       <para>
-	Flag to show detailed query plan dump.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">query</replaceable></term>
-      <listitem>
-       <para>
-	Any <replaceable class="PARAMETER">query</replaceable>.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-EXPLAIN-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>Query plan</term>
-      <listitem>
-       <para>
-	Explicit query plan from the <productname>PostgreSQL</productname>
-	planner.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <note>
-    <para>
-     Prior to <application>PostgreSQL</application> 7.3, the query plan
-     was emitted in the form of a NOTICE message.  Now it appears as a
-     query result (formatted like a table with a single text column).
-    </para>
-   </note>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-EXPLAIN-1">
-  <refsect1info>
-   <date>1998-04-15</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   This command displays the execution plan that the
-   <application>PostgreSQL</application> planner
-   generates for the supplied query.  The execution plan shows how
-   the table(s) referenced by the query will be scanned---by plain
-   sequential scan, index scan, etc.---and if multiple tables are
-   referenced, what join algorithms will be used to bring together
-   the required tuples from each input table.
-  </para>
-
-  <para>
-   The most critical part of the display is the estimated query execution
-   cost, which is the planner's guess at how long it will take to run the
-   query (measured in units of disk page fetches).  Actually two numbers
-   are shown: the start-up time before the first tuple can be returned, and
-   the total time to return all the tuples.  For most queries the total time
-   is what matters, but in contexts such as an EXISTS sub-query the planner
-   will choose the smallest start-up time instead of the smallest total time
-   (since the executor will stop after getting one tuple, anyway).
-   Also, if you limit the number of tuples to return with a LIMIT clause,
-   the planner makes an appropriate interpolation between the endpoint
-   costs to estimate which plan is really the cheapest.
-  </para>
-
-  <para>
-   The ANALYZE option causes the query 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>
-
-  <caution>
-   <para>
-    Keep in mind that the query is actually executed when ANALYZE is used.
-    Although <command>EXPLAIN</command> will discard any output that a SELECT
-    would return,
-    other side-effects of the query will happen as usual.
-    If you wish to use <command>EXPLAIN ANALYZE</command> on an INSERT,
-    UPDATE, or DELETE query without letting the query affect your data,
-    use this approach:
-      <programlisting>
-BEGIN;
-EXPLAIN ANALYZE ...;
-ROLLBACK;
-      </programlisting>
-   </para>
-  </caution>
-
-  <para>
-   The VERBOSE option emits the full internal representation of the plan tree,
-   rather than just a summary.
-   Usually this option is only useful for debugging
-   <application>PostgreSQL</application>.   The VERBOSE dump is either
-   pretty-printed or not, depending on the setting of the
-   <option>EXPLAIN_PRETTY_PRINT</option> configuration parameter.
-  </para>
-
-  <refsect2 id="R2-SQL-EXPLAIN-3">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    There is only sparse documentation on the optimizer's use of cost
-    information in <productname>PostgreSQL</productname>.
-    Refer to the <citetitle>User's Guide</citetitle> and
-    <citetitle>Programmer's Guide</citetitle> for more information.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-EXPLAIN-2">
-  <title>
-   Usage
-  </title>
-
-  <para>
-   To show a query plan for a simple query on a table with a single
-   <type>int4</type> column and 10000 rows:
-
-   <programlisting>
-EXPLAIN SELECT * FROM foo;
-    <computeroutput>
-                       QUERY PLAN
----------------------------------------------------------
- Seq Scan on foo  (cost=0.00..155.00 rows=10000 width=4)
-(1 row)
-    </computeroutput>
-   </programlisting>
-  </para>
-
-  <para>
-   If there is an index and we use a query with an indexable WHERE condition,
-   <command>EXPLAIN</command> will show a different plan:
-
-   <programlisting>
-EXPLAIN SELECT * FROM foo WHERE i = 4;
-    <computeroutput>
-                         QUERY PLAN
---------------------------------------------------------------
- Index Scan using fi on foo  (cost=0.00..5.98 rows=1 width=4)
-   Index Cond: (i = 4)
-(2 rows)
-    </computeroutput>
-   </programlisting>
-  </para>
-
-  <para>
-   And 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;
-    <computeroutput>
-                             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)
-    </computeroutput>
-   </programlisting>
-  </para>
-
-  <para>
-   Note that the specific numbers shown, and even the selected query
-   strategy, may vary between <application>PostgreSQL</application>
-   releases due to planner improvements.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-EXPLAIN-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-EXPLAIN-4">
-   <refsect2info>
-    <date>1998-09-01</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>EXPLAIN</command> statement defined in SQL92.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/fetch.sgml b/doc/src/sgml/ref/fetch.sgml
deleted file mode 100644
index fae7ab5ba24..00000000000
--- a/doc/src/sgml/ref/fetch.sgml
+++ /dev/null
@@ -1,405 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/fetch.sgml,v 1.21 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-FETCH">
- <refmeta>
-  <refentrytitle id="SQL-FETCH-TITLE">FETCH</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   FETCH
-  </refname>
-  <refpurpose>
-   retrieve rows from a table using a cursor
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-FETCH [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable class="PARAMETER">count</replaceable> ] { IN | FROM } <replaceable class="PARAMETER">cursor</replaceable>
-FETCH [ FORWARD | BACKWARD | RELATIVE ] [ <replaceable class="PARAMETER">#</replaceable> | ALL | NEXT | PRIOR ]
-    { IN | FROM } <replaceable class="PARAMETER">cursor</replaceable>
-  </synopsis>
-
-  <refsect2 id="R2-SQL-FETCH-1">
-   <refsect2info>
-    <date>1998-09-01</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">direction</replaceable></term>
-      <listitem>
-       <para>
-	<replaceable class="PARAMETER">selector</replaceable>
-	defines the fetch direction. It can be one of
-	the following:
-
-	<variablelist>
-	 <varlistentry>
-	  <term>FORWARD</term>
-	  <listitem>
-	   <para>
-	    fetch next row(s). This is the default
-	    if <replaceable class="PARAMETER">selector</replaceable> is omitted.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-	 <varlistentry>
-	  <term>BACKWARD</term>
-	  <listitem>
-	   <para>
-	    fetch previous row(s).
-	   </para>
-	  </listitem>
-	 </varlistentry>
-	 <varlistentry>
-	  <term>RELATIVE</term>
-	  <listitem>
-	   <para>
-	    Noise word for SQL92 compatibility.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-	</variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">count</replaceable></term>
-      <listitem>
-       <para>
-	<replaceable class="PARAMETER">count</replaceable>
-	determines how many rows to fetch. It can be one of the following:
-
-	<variablelist>
-	 <varlistentry>
-	  <term><replaceable class="PARAMETER">#</replaceable></term>
-	  <listitem>
-	   <para>
-	    A signed integer that specifies how many rows to fetch.
-	    Note that a negative integer is equivalent to changing the sense of
-	    FORWARD and BACKWARD.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>
-	   ALL
-	  </term>
-	  <listitem>
-	   <para>
-	    Retrieve all remaining rows.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>
-	   NEXT
-	  </term>
-	  <listitem>
-	   <para>
-	    Equivalent to specifying a count of <command>1</command>.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>
-	   PRIOR
-	  </term>
-	  <listitem>
-	   <para>
-	    Equivalent to specifying a count of <command>-1</command>.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-	</variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">cursor</replaceable></term>
-      <listitem>
-       <para>
-	An open cursor's name.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-FETCH-2">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    <command>FETCH</command> returns the results of the query defined by the specified cursor.
-    The following messages will be returned if the query fails:
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  PerformPortalFetch: portal "<replaceable class="PARAMETER">cursor</replaceable>" not found
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If <replaceable class="PARAMETER">cursor</replaceable>
-	is not previously declared.
-	The cursor must be declared within a transaction block.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  FETCH/ABSOLUTE not supported, using RELATIVE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	<productname>PostgreSQL</productname> does not support absolute
-	positioning of cursors.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-ERROR:  FETCH/RELATIVE at current position is not supported
-       </computeroutput></term>
-      <listitem>
-       <para>
-	<acronym>SQL92</acronym> allows one to repetitively retrieve the cursor
-	at its <quote>current position</quote> using the syntax
-	<synopsis>
-FETCH RELATIVE 0 FROM <replaceable class="PARAMETER">cursor</replaceable>.
-	</synopsis>
-       </para>
-
-       <para>
-	<productname>PostgreSQL</productname> does not currently support
-	this notion; in fact the value zero is reserved to indicate that
-	all rows should be retrieved and is equivalent to specifying the ALL keyword.
-	If the RELATIVE keyword has been used, <productname>PostgreSQL</productname> 
-	assumes that the user intended <acronym>SQL92</acronym> behavior
-	and returns this error message.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-FETCH-1">
-  <refsect1info>
-   <date>1998-04-15</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>FETCH</command> allows a user to retrieve rows using a cursor.
-   The number of rows retrieved is specified by
-   <replaceable class="PARAMETER">#</replaceable>.
-   If the number of rows remaining in the cursor is less
-   than <replaceable class="PARAMETER">#</replaceable>,
-   then only those available are fetched.
-   Substituting the keyword ALL in place of a number will
-   cause all remaining rows in the cursor to be retrieved.
-   Instances may be fetched in both FORWARD and BACKWARD
-   directions. The default direction is FORWARD.
-
-   <tip>
-    <para>
-     Negative numbers are allowed to be specified for the
-     row count. A negative number is equivalent to reversing
-     the sense of the FORWARD and BACKWARD keywords. For example,
-     <command>FORWARD -1</command> is the same as <command>BACKWARD 1</command>.
-    </para>
-   </tip>
-  </para>
-
-  <refsect2 id="R2-SQL-FETCH-3">
-   <refsect2info>
-    <date>1998-04-15</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    Note that the FORWARD and BACKWARD keywords are
-    <productname>PostgreSQL</productname> extensions.
-    The <acronym>SQL92</acronym> syntax is also supported, specified
-    in the second form of the command. See below for details
-    on compatibility issues.
-   </para>
-
-   <para>
-    Updating data in a cursor is not supported by 
-    <productname>PostgreSQL</productname>,
-    because mapping cursor updates back to base tables is
-    not generally possible, as is also the case with VIEW updates.
-    Consequently,
-    users must issue explicit UPDATE commands to replace data.
-   </para>
-
-   <para>
-    Cursors may only be used inside of transactions because
-    the data that they store spans multiple user queries.
-   </para>
-
-   <para>
-    Use
-    <xref linkend="sql-move" endterm="sql-move-title">
-    to change cursor position.
-    <xref linkend="sql-declare" endterm="sql-declare-title">
-    will define a cursor.
-    Refer to
-    <xref linkend="sql-begin" endterm="sql-begin-title">,
-    <xref linkend="sql-commit" endterm="sql-commit-title">,
-    and
-    <xref linkend="sql-rollback" endterm="sql-rollback-title">
-    for further information about transactions.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-FETCH-2">
-  <title>
-   Usage
-  </title>
-
-  <para>
-   The following examples traverses a table using a cursor.
-
-<programlisting>
--- Set up and use a cursor:
-
-BEGIN WORK;
-DECLARE liahona CURSOR FOR SELECT * FROM films;
-
--- Fetch first 5 rows in the cursor liahona:
-FETCH FORWARD 5 IN liahona;
-
-<computeroutput>
- 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
-</computeroutput>
-
--- Fetch previous row:
-FETCH BACKWARD 1 IN liahona;
-
-<computeroutput>
- code  | title   | did | date_prod  | kind   | len
--------+---------+-----+------------+--------+-------
- P_301 | Vertigo | 103 | 1958-11-14 | Action | 02:08
-</computeroutput>
-
--- close the cursor and commit work:
-
-CLOSE liahona;
-COMMIT WORK;
-</programlisting>
-  </para>        
- </refsect1>
-
- <refsect1 id="R1-SQL-FETCH-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-FETCH-4">
-   <refsect2info>
-    <date>1998-09-01</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    <note>
-     <para>
-      The non-embedded use of cursors is a <productname>PostgreSQL</productname>
-      extension. The syntax and usage of cursors is being compared
-      against the embedded form of cursors defined in <acronym>SQL92</acronym>.
-     </para>
-    </note>
-   </para>
-
-   <para>
-    <acronym>SQL92</acronym> allows absolute positioning of the cursor for
-    FETCH, and allows placing the results into explicit variables:
-
-    <synopsis>
-FETCH ABSOLUTE <replaceable class="PARAMETER">#</replaceable>
-    FROM <replaceable class="PARAMETER">cursor</replaceable>
-    INTO :<replaceable class="PARAMETER">variable</replaceable> [, ...]
-    </synopsis>
-
-    <variablelist>
-     <varlistentry>
-      <term>ABSOLUTE</term>
-      <listitem>
-       <para>
-	The cursor should be positioned to the specified absolute
-	row number. All row numbers in <productname>PostgreSQL</productname>
-	are relative numbers so this capability is not supported.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>:<replaceable class="PARAMETER">variable</replaceable></term>
-      <listitem>
-       <para>
-	Target host variable(s).
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml
deleted file mode 100644
index a1384409cf3..00000000000
--- a/doc/src/sgml/ref/grant.sgml
+++ /dev/null
@@ -1,384 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.26 2002/05/14 18:47:58 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-GRANT">
- <refmeta>
-  <refentrytitle id="sql-grant-title">GRANT</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>GRANT</refname>
-  <refpurpose>define access privileges</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-GRANT { { SELECT | INSERT | UPDATE | DELETE | RULE | REFERENCES | TRIGGER }
-    [,...] | ALL [ PRIVILEGES ] }
-    ON [ TABLE ] <replaceable class="PARAMETER">tablename</replaceable> [, ...]
-    TO { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-
-GRANT { { CREATE | TEMPORARY | TEMP } [,...] | ALL [ PRIVILEGES ] }
-    ON DATABASE <replaceable>dbname</replaceable> [, ...]
-    TO { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-
-GRANT { EXECUTE | ALL [ PRIVILEGES ] }
-    ON FUNCTION <replaceable>funcname</replaceable> ([<replaceable>type</replaceable>, ...]) [, ...]
-    TO { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-
-GRANT { USAGE | ALL [ PRIVILEGES ] }
-    ON LANGUAGE <replaceable>langname</replaceable> [, ...]
-    TO { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-
-GRANT { { CREATE | USAGE } [,...] | ALL [ PRIVILEGES ] }
-    ON SCHEMA <replaceable>schemaname</replaceable> [, ...]
-    TO { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-grant-description">
-  <title>Description</title>
-
-  <para>
-   The <command>GRANT</command> command gives specific permissions on
-   an object (table, view, sequence, database, function, procedural language,
-   or schema) to
-   one or more users or groups of users.  These permissions are added
-   to those already granted, if any.
-  </para>
-
-  <para>
-   The key word <literal>PUBLIC</literal> indicates that the
-   privileges are to be granted to all users, including those that may
-   be created later.  <literal>PUBLIC</literal> may be thought of as an
-   implicitly defined group that always includes all users.
-   Note that any particular user will have the sum
-   of privileges granted directly to him, privileges granted to any group he
-   is presently a member of, and privileges granted to
-   <literal>PUBLIC</literal>.
-  </para>
-
-  <para>
-   Users other than the creator of an object do not have any access privileges
-   to the object unless the creator grants permissions.
-   There is no need to grant privileges to the creator of an object,
-   as the creator automatically holds all privileges.
-   (The creator could, however, choose to revoke
-   some of his own privileges for safety.  Note that the ability to
-   grant and revoke privileges is inherent in the creator and cannot
-   be lost.  The right to drop the object is likewise inherent in the
-   creator, and cannot be granted or revoked.)
-  </para>
-
-  <para>
-   The possible privileges are:
-
-   <variablelist>
-    <varlistentry>
-     <term>SELECT</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-select" endterm="sql-select-title"> from any column of the
-       specified table, view, or sequence.  Also allows the use of
-       <xref linkend="sql-copy" endterm="sql-copy-title"> TO.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>INSERT</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-insert" endterm="sql-insert-title"> of a new row into the
-       specified table.  Also allows <xref linkend="sql-copy" endterm="sql-copy-title"> FROM.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>UPDATE</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-update" endterm="sql-update-title"> of any column of the
-       specified table.  <literal>SELECT ... FOR UPDATE</literal>
-       also requires this privilege (besides the
-       <literal>SELECT</literal> privilege).  For sequences, this
-       privilege allows the use of <function>nextval</function>,
-       <function>currval</function> and <function>setval</function>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>DELETE</term>
-     <listitem>
-      <para>
-       Allows <xref linkend="sql-delete" endterm="sql-delete-title"> of a row from the
-       specified table.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>RULE</term>
-     <listitem>
-      <para>
-       Allows the creation of a rule on the table/view.  (See <xref
-       linkend="sql-createrule" endterm="sql-createrule-title"> statement.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>REFERENCES</term>
-     <listitem>
-      <para>
-       To create a table with a foreign key constraint, it is
-       necessary to have this privilege on the table with the referenced
-       key.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>TRIGGER</term>
-     <listitem>
-      <para>
-       Allows the creation of a trigger on the specified table.  (See
-       <xref linkend="sql-createtrigger" endterm="sql-createtrigger-title"> 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>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>TEMPORARY</term>
-     <term>TEMP</term>
-     <listitem>
-      <para>
-       Allows temporary tables to be created while using the 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.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>ALL PRIVILEGES</term>
-     <listitem>
-      <para>
-       Grant all of the privileges applicable to the object at once.
-       The <literal>PRIVILEGES</literal> key word is optional in
-       <productname>PostgreSQL</productname>, though it is required by
-       strict SQL.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   The privileges required by other commands are listed on the
-   reference page of the respective command.
-  </para>
- </refsect1>
-
-
- <refsect1 id="SQL-GRANT-notes">
-  <title>Notes</title>
-
-   <para>
-    The <xref linkend="sql-revoke" endterm="sql-revoke-title"> command is used
-    to revoke access privileges.
-   </para>
-
-   <para>
-    It should be noted that database <firstterm>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>
-    Currently, to grant privileges in <productname>PostgreSQL</productname>
-    to only a few columns, you must
-    create a view having the desired columns and then grant privileges
-    to that view.
-   </para>
-
-   <para>
-    Use <xref linkend="app-psql">'s <command>\z</command> command
-    to obtain information about existing privileges, for example:
-<programlisting>
-lusitania=> \z mytable
-    Access privileges for database "lusitania"
-  Table  |           Access privileges
----------+---------------------------------------
- mytable | {=r,miriam=arwdRxt,"group todos=arw"}
-</programlisting>
-    The entries shown by <command>\z</command> are interpreted thus:
-<programlisting>
-              =xxxx -- privileges granted to PUBLIC
-         uname=xxxx -- privileges granted to a user
-   group gname=xxxx -- privileges granted to a group
-
-                  r -- SELECT ("read")
-                  w -- UPDATE ("write")
-                  a -- INSERT ("append")
-                  d -- DELETE
-                  R -- RULE
-                  x -- REFERENCES
-                  t -- TRIGGER
-                  X -- EXECUTE
-                  U -- USAGE
-                  C -- CREATE
-                  T -- TEMPORARY
-            arwdRxt -- ALL PRIVILEGES (for tables)
-</programlisting>
-
-    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 GROUP todos;
-</programlisting>
-   </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 field
-is NULL).  Currently, default privileges are interpreted the same way
-for all object types: all privileges for the owner and no privileges for
-anyone else.  The first <command>GRANT</> on an object will instantiate
-this default (producing, for example, <literal>{=,miriam=arwdRxt}</>)
-and then modify it per the specified request.
-   </para>
- </refsect1>
-
- <refsect1 id="sql-grant-examples">
-  <title>Examples</title>
-
-  <para>
-   Grant insert privilege to all users on table films:
-
-<programlisting>
-GRANT INSERT ON films TO PUBLIC;
-</programlisting>
-  </para>
-
-  <para>
-   Grant all privileges to user <literal>manuel</literal> on view <literal>kinds</literal>:
-
-<programlisting>
-GRANT ALL PRIVILEGES ON kinds TO manuel;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="sql-grant-compatibility">
-  <title>Compatibility</title>
-    
-  <refsect2>
-   <title>SQL92</title>
-
-   <para>
-    The <literal>PRIVILEGES</literal> key word in <literal>ALL
-    PRIVILEGES</literal> is required.  <acronym>SQL</acronym> does not
-    support setting the privileges on more than one table per command.
-   </para>
-
-   <para>
-    The <acronym>SQL92</acronym> syntax for GRANT allows setting
-    privileges for individual columns within a table, and allows
-    setting a privilege to grant the same privileges to others:
-
-<synopsis>
-GRANT <replaceable class="PARAMETER">privilege</replaceable> [, ...]
-    ON <replaceable class="PARAMETER">object</replaceable> [ ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) ] [, ...]
-    TO { PUBLIC | <replaceable class="PARAMETER">username</replaceable> [, ...] } [ WITH GRANT OPTION ]
-</synopsis>
-   </para>
-
-   <para>
-    <acronym>SQL</acronym> allows to grant the USAGE privilege on
-    other kinds of objects:  CHARACTER SET, COLLATION, TRANSLATION, DOMAIN.
-   </para>
-
-   <para>
-    The TRIGGER privilege was introduced in SQL99.  The RULE privilege
-    is a PostgreSQL extension.
-   </para>
-  </refsect2>
-
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <simpara>
-   <xref linkend="sql-revoke">
-  </simpara>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/initdb.sgml b/doc/src/sgml/ref/initdb.sgml
deleted file mode 100644
index 657fee3d381..00000000000
--- a/doc/src/sgml/ref/initdb.sgml
+++ /dev/null
@@ -1,298 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/initdb.sgml,v 1.21 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-INITDB">
- <refmeta>
-  <refentrytitle id="APP-INITDB-TITLE">initdb</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>initdb</refname>
-  <refpurpose>create a new <productname>PostgreSQL</productname> database cluster</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>initdb</command>
-    <group choice="plain">
-     <arg>--pgdata </arg>
-     <arg>-D </arg>
-     <replaceable>directory</replaceable>
-    </group>
-    <group>
-     <arg>--username </arg>
-     <arg>-U </arg>
-     <replaceable>username</replaceable>
-    </group>
-    <group><arg>--pwprompt</arg><arg>-W</arg></group>
-    <group>
-     <arg>--encoding </arg>
-     <arg>-E </arg>
-     <replaceable>encoding</replaceable>
-    </group>
-    <arg>--locale <replaceable>locale</replaceable></arg>
-    <arg>--lc-collate <replaceable>locale</replaceable></arg>
-    <arg>--lc-ctype <replaceable>locale</replaceable></arg>
-    <arg>--lc-messages <replaceable>locale</replaceable></arg>
-    <arg>--lc-monetary <replaceable>locale</replaceable></arg>
-    <arg>--lc-numeric <replaceable>locale</replaceable></arg>
-    <arg>--lc-time <replaceable>locale</replaceable></arg>
-    <arg>-L <replaceable>directory</replaceable></arg>
-    <group><arg>--noclean</arg><arg>-n</arg></group>
-    <group><arg>--debug</arg><arg>-d</arg></group>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-INITDB-1">
-  <title>
-   Description
-  </title>
-  <para>
-   <command>initdb</command> creates a new
-   <productname>PostgreSQL</productname> database cluster (or database
-   system).  A database cluster is a collection of databases that are
-   managed by a single server instance.
-  </para>
-
-  <para>
-   Creating a database system 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>
-   database.  When you create a new database, everything in the
-   <literal>template1</literal> database is copied.
-   It contains catalog tables filled in for things like the
-   built-in types.
-  </para>
-
-  <para>
-   <command>initdb</command> initializes the database cluster's
-   default locale and character set encoding.  Some locale categories
-   are fixed for the lifetime of the cluster, so it is important to
-   make the right choice when running <command>initdb</command>.
-   Other locale categories can be changed later when the server is
-   started.  <command>initdb</command> will write those locale
-   settings into the <filename>postgresql.conf</filename>
-   configuration file so they are the default, but they can be changed
-   by editing that file.  To set the locale that
-   <command>initdb</command> uses, see the description of the
-   <option>--locale</option> option.  The character set encoding can
-   be set separately for each database as it is created.
-   <command>initdb</command> determines the encoding for the
-   <literal>template1</literal> database, which will serve as the
-   default for all other databases.  To alter the default encoding use
-   the <option>--encoding</option> option.
-  </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 may not be run as root, you must not run
-   <command>initdb</command> as root either.  (It will in fact refuse
-   to do so.)
-  </para>
-
-  <para>
-   Although <command>initdb</command> will attempt to create the
-   specified data directory, often it won't have permission to do so,
-   since the parent of the desired data directory is often a root-owned
-   directory.  To set up an arrangement like this, create an empty data
-   directory as root, then use <command>chown</command> to hand over
-   ownership of that directory to the database user account, then
-   <command>su</command> to become the database user, and
-   finally run <command>initdb</command> as the database user.
-  </para>
-
-  <refsect2>
-   <title>Options</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term>--pgdata=<replaceable class="parameter">directory</replaceable></term>
-      <term>-D <replaceable class="parameter">directory</replaceable></term>
-      <listitem>
-       <para>
-        This option specifies the directory where the database system
-        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>postmaster</command>) can find the database
-        directory later by the same variable.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>--username=<replaceable class="parameter">username</replaceable></term>
-      <term>-U <replaceable class="parameter">username</replaceable></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 <quote>postgres</quote>, even if the operating
-        system user's name is different.
-       </para>
-      </listitem>
-     </varlistentry>
- 
-     <varlistentry>
-      <term>--pwprompt</term>
-      <term>-W</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>--encoding=<replaceable class="parameter">encoding</replaceable></term>
-      <term>-E <replaceable class="parameter">encoding</replaceable></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. To use the encoding feature, you must
-        have enabled it at build time, at which time you also select the default
-        for this option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>--locale=<replaceable>locale</replaceable></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.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>--lc-collate=<replaceable>locale</replaceable></term>
-      <term>--lc-ctype=<replaceable>locale</replaceable></term>
-      <term>--lc-messages=<replaceable>locale</replaceable></term>
-      <term>--lc-monetary=<replaceable>locale</replaceable></term>
-      <term>--lc-numeric=<replaceable>locale</replaceable></term>
-      <term>--lc-time=<replaceable>locale</replaceable></term>
-
-      <listitem>
-       <para>
-        Like <option>--locale</option>, but only sets the locale in
-        the specified category.
-       </para>
-      </listitem>
-     </varlistentry>
-   </variablelist>
-   </para>
-
-   <para>
-    Other, less commonly used, parameters are also available:
-
-    <variablelist>
-     <varlistentry>
-      <term>-L <replaceable class="parameter">directory</replaceable></term>
-      <listitem>
-       <para>
-        Specifies where <command>initdb</command> should find
-        its input files to initialize the database system.  This is
-        normally not necessary.  You will be told if you need to
-        specify their location explicitly.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>--noclean</term>
-      <term>-n</term>
-      <listitem>
-       <para>
-	By default, when <command>initdb</command>
-	determines that an error prevented it from completely creating the database
-	system, it removes any files it may have created before discovering
-	that it can't finish the job. This option inhibits tidying-up and is
-	thus useful for debugging.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>--debug</term>
-      <term>-d</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>
-
-    </variablelist>
-   </para>
-
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Environment</title>
-
-  <variablelist>
-   <varlistentry>
-    <term><envar>PGDATA</envar></term>
-
-    <listitem>
-     <para>
-      Specifies the directory where the database system is to be
-      stored; may be overridden using the <option>-D</option> option.
-     </para>
-    </listitem>
-   </varlistentry>
-  </variablelist>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-postgres"></member>
-   <member><xref linkend="app-postmaster"></member>
-   <member><citetitle>PostgreSQL Administrator's Guide</citetitle></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/initlocation.sgml b/doc/src/sgml/ref/initlocation.sgml
deleted file mode 100644
index 917deadbbeb..00000000000
--- a/doc/src/sgml/ref/initlocation.sgml
+++ /dev/null
@@ -1,88 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/initlocation.sgml,v 1.15 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-INITLOCATION">
- <refmeta>
-  <refentrytitle id="APP-INITLOCATION-TITLE"><application>initlocation</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>initlocation</refname>
-  <refpurpose>create a secondary <productname>PostgreSQL</productname> database storage area</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>initlocation</command>
-   <arg choice="plain"><replaceable>directory</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-INITLOCATION-1">
-  <title>Description</title>
-  <para>
-   <application>initlocation</application> 
-   creates a new <productname>PostgreSQL</productname> secondary database storage area.
-   See the discussion under <xref linkend="SQL-CREATEDATABASE" endterm="SQL-CREATEDATABASE-title">
-   about how to manage and use secondary storage areas. If the argument does not contain
-   a slash and is not valid as a path, it is assumed to be an environment variable,
-   which is referenced. See the examples at the end.
-  </para>
-  <para>
-   In order to use this command you must be logged in (using <command>su</command>, for example)
-   as the database superuser.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-APP-INITLOCATION-2">
-  <title>Usage</title>
-
-  <informalexample>
-   <para>
-    To create a database in an alternate location, using an
-    environment variable:
-<screen>
-<prompt>$ </prompt><userinput>export PGDATA2=/opt/postgres/data</userinput>
-</screen>
-    Stop and start postmaster so it sees the <envar>PGDATA2</envar>
-    environment variable.  The system must be configured so the
-    postmaster sees <envar>PGDATA2</envar> every time it starts.  Finally:
-<screen>
-<prompt>$</prompt> <userinput>initlocation PGDATA2</userinput>
-<prompt>$</prompt> <userinput>createdb -D PGDATA2 testdb</userinput>
-</screen>
-   </para>
-  </informalexample>
-
-  <informalexample>
-   <para>
-    Alternatively, if you allow absolute paths you could write:
-<screen>
-<prompt>$</prompt> <userinput>initlocation /opt/postgres/data</userinput>
-<prompt>$</prompt> <userinput>createdb -D /opt/postgres/data/testdb testdb</userinput>
-</screen>
-   </para>
-  </informalexample>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml
deleted file mode 100644
index d3bb16c191a..00000000000
--- a/doc/src/sgml/ref/insert.sgml
+++ /dev/null
@@ -1,271 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/insert.sgml,v 1.18 2002/04/24 02:31:30 momjian Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-INSERT">
- <refmeta>
-  <refentrytitle id="SQL-INSERT-TITLE">INSERT</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   INSERT
-  </refname>
-  <refpurpose>
-   create new rows in a table
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-08-08</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-INSERT INTO <replaceable class="PARAMETER">table</replaceable> [ ( <replaceable class="PARAMETER">column</replaceable> [, ...] ) ]
-    { DEFAULT VALUES | VALUES ( { <replaceable class="PARAMETER">expression</replaceable> | DEFAULT } [, ...] ) | SELECT <replaceable class="PARAMETER">query</replaceable> }
-  </synopsis>
-
-  <refsect2 id="R2-SQL-INSERT-1">
-   <title>
-    Inputs
-   </title>
-
-   <para>
-
-    <variablelist>
-     <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>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>DEFAULT VALUES</term>
-      <listitem>
-       <para>
-	All columns will be filled by NULLs or by values specified
-	when the table was created using DEFAULT clauses.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">expression</replaceable></term>
-      <listitem>
-       <para>
-	A valid expression or value to assign to <replaceable
-	 class="PARAMETER">column</replaceable>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">DEFAULT</replaceable></term>
-      <listitem>
-       <para>
-	This column will be filled in by the column DEFAULT clause, or NULL if
-	a default is not available.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">query</replaceable></term>
-      <listitem>
-       <para>
-	A valid query. Refer to the SELECT statement for a further description
-	of valid arguments.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-INSERT-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-INSERT <replaceable>oid</replaceable> 1
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if only one row was inserted.
-	<returnvalue><replaceable>oid</replaceable></returnvalue>
-	is the numeric <acronym>OID</acronym> of the inserted row.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-INSERT 0 <replaceable>#</replaceable>
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if more than one rows were inserted.
-	<returnvalue><replaceable>#</replaceable></returnvalue>
-	is the number of rows inserted.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-INSERT-1">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>INSERT</command> allows one to insert new rows into a
-   table. One can insert
-   a single row at a time or several rows as a result of a query.
-   The columns in the target list may be listed in any order.
-  </para>
-
-  <para>
-   Each column not present in the target list will be inserted
-   using a default value, either a declared DEFAULT value
-   or NULL. <productname>PostgreSQL</productname> will reject the new
-   column if a NULL is inserted into a column declared NOT NULL.
-  </para>
-
-  <para>
-   If the expression for each column
-   is not of the correct data type, automatic type coercion will be
-   attempted.
-  </para>
-
-  <para>
-   You must have insert privilege to a table in order to append
-   to it, as well as select privilege on any table specified
-   in a WHERE clause.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-INSERT-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Insert a single row into table <literal>films</literal>:
-
-   <programlisting>
-INSERT INTO films VALUES
-    ('UA502','Bananas',105,'1971-07-13','Comedy',INTERVAL '82 minute');
-   </programlisting>
-  </para>
-
-  <para>
-   In this second example the last column <literal>len</literal> is
-   omitted and therefore it will have the default value of NULL:
-
-   <programlisting>
-INSERT INTO films (code, title, did, date_prod, kind)
-    VALUES ('T_601', 'Yojimbo', 106, DATE '1961-06-16', 'Drama');
-   </programlisting>
-  </para>
-
-  <para>
-   In the third example, we use the DEFAULT values for the date columns
-   rather than specifying an entry.
-
-   <programlisting>
-INSERT INTO films VALUES
-    ('UA502','Bananas',105,DEFAULT,'Comedy',INTERVAL '82 minute');
-INSERT INTO films (code, title, did, date_prod, kind)
-    VALUES ('T_601', 'Yojimbo', 106, DEFAULT, 'Drama');
-   </programlisting>
-  </para>
-
-  <para>
-   Insert a single row into table distributors; note that
-   only column <literal>name</literal> is specified, so the omitted
-   column <literal>did</literal> will be assigned its default value:
-
-   <programlisting>
-INSERT INTO distributors (name) VALUES ('British Lion');
-   </programlisting>
-  </para>
-
-  <para>
-   Insert several rows into table films from table <literal>tmp</literal>:
-
-   <programlisting>
-INSERT INTO films SELECT * FROM tmp;
-   </programlisting>
-  </para>
-
-  <para>
-   Insert into arrays (refer to the
-   <citetitle>PostgreSQL User's Guide</citetitle> for further
-   information about arrays):
-
-   <programlisting>
--- Create an empty 3x3 gameboard for noughts-and-crosses
--- (all of these queries create the same board attribute)
-INSERT INTO tictactoe (game, board[1:3][1:3])
-    VALUES (1,'{{"","",""},{},{"",""}}');
-INSERT INTO tictactoe (game, board[3][3])
-    VALUES (2,'{}');
-INSERT INTO tictactoe (game, board)
-    VALUES (3,'{{,,},{,,},{,,}}');
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-INSERT-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-INSERT-4">
-   <title>
-    SQL92
-   </title>
-   <para>
-    <command>INSERT</command> is fully compatible with <acronym>SQL92</acronym>.
-    Possible limitations in features of the
-    <replaceable class="PARAMETER">query</replaceable>
-    clause are documented for
-    <xref linkend="sql-select" endterm="sql-select-title">.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/ipcclean.sgml b/doc/src/sgml/ref/ipcclean.sgml
deleted file mode 100644
index 76eee6f1077..00000000000
--- a/doc/src/sgml/ref/ipcclean.sgml
+++ /dev/null
@@ -1,84 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/ipcclean.sgml,v 1.7 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-IPCCLEAN">
- <refmeta>
-  <refentrytitle id="APP-IPCCLEAN-TITLE"><application>ipcclean</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>ipcclean</refname>
-  <refpurpose>remove shared memory and semaphores from an aborted <productname>PostgreSQL</productname> server</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>ipcclean</command>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-IPCCLEAN-1">
-  <title>Description</title>
-  <para>
-   <command>ipcclean</command> removes all shared memory segments and
-   semaphore sets owned by the current user.  It is intended to be
-   used for cleaning up after a crashed
-   <productname>PostgreSQL</productname> server (<xref
-   linkend="app-postmaster">).  Note that immediately restarting the
-   server will also clean up shared memory and semaphores, so this
-   command is of little real utility.
-  </para>
-
-  <para>
-   Only the database administrator should execute this program as it
-   can cause bizarre behavior (i.e., crashes) if run during multiuser
-   execution.  If this command is executed while a
-   <application>postmaster</application> is running, the shared memory
-   and semaphores allocated by the
-   <application>postmaster</application> will be deleted.  This will
-   result in a general failure of the backend servers started by that
-   <application>postmaster</application>.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   This script is a hack, but in the many years since it was written,
-   no one has come up with an equally effective and portable solution.
-   Since the <application>postmaster</application> can now clean up by
-   itself, it is unlikely that <command>ipcclean</command> will be
-   improved upon in the future.
-  </para>
-
-  <para>
-   The script makes assumption about the format of output of the
-   <application>ipcs</application>
-   utility which may not be true across different operating systems.
-   Therefore, it may not work on your particular OS.
-  </para>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/listen.sgml b/doc/src/sgml/ref/listen.sgml
deleted file mode 100644
index 405e6fb0e21..00000000000
--- a/doc/src/sgml/ref/listen.sgml
+++ /dev/null
@@ -1,210 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/listen.sgml,v 1.13 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-LISTEN">
- <refmeta>
-  <refentrytitle id="SQL-LISTEN-TITLE">LISTEN</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   LISTEN
-  </refname>
-  <refpurpose>
-   listen for a notification
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-LISTEN <replaceable class="PARAMETER">name</replaceable>
-  </synopsis>
-
-  <refsect2 id="R2-SQL-LISTEN-1">
-   <refsect2info>
-    <date>1998-10-07</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	Name of notify condition.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-LISTEN-2">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-LISTEN
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned upon successful completion of registration.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  Async_Listen: We are already listening on <replaceable class="PARAMETER">name</replaceable>
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If this backend is already registered for that notify condition.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>		
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-LISTEN-1">
-  <refsect1info>
-   <date>1998-10-07</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>LISTEN</command> registers the current 
-   <productname>PostgreSQL</productname> backend as a
-   listener on the notify condition
-   <replaceable class="PARAMETER">name</replaceable>.
-  </para>
-
-  <para>
-   Whenever the command 
-   <command>NOTIFY <replaceable class="PARAMETER">name</replaceable></command>
-   is invoked, either by this backend or another one connected to
-   the same database, all the backends currently listening on that notify
-   condition are notified, and each will in turn notify its connected
-   frontend application.  See the discussion of <command>NOTIFY</command>
-   for more information.
-  </para>
-
-  <para>
-   A backend can be unregistered for a given notify condition with the
-   <command>UNLISTEN</command> command.  Also, a backend's listen registrations
-   are automatically cleared when the backend process exits.
-  </para>
-
-  <para>
-   The method a frontend application must use to detect notify events depends on
-   which <productname>PostgreSQL</productname> application programming interface it
-   uses.  With the basic libpq library, the application issues
-   <command>LISTEN</command> as an ordinary SQL command, and then must
-   periodically call the routine <function>PQnotifies</function> to find out
-   whether any notify events have been received.  Other interfaces such as
-   libpgtcl provide higher-level methods for handling notify events; indeed,
-   with libpgtcl the application programmer should not even issue
-   <command>LISTEN</command> or <command>UNLISTEN</command> directly.  See the
-   documentation for the library you are using for more details.
-  </para>
-
-  <para>
-   <xref linkend="sql-notify" endterm="sql-notify-title">
-   contains a more extensive
-   discussion of the use of <command>LISTEN</command> and
-   <command>NOTIFY</command>.
-  </para>
-
-  <refsect2 id="R2-SQL-LISTEN-3">
-   <refsect2info>
-    <date>1998-10-07</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    <replaceable class="PARAMETER">name</replaceable>
-    can be any string valid as a name;
-    it need not correspond to the name of any actual table.  If
-    <replaceable class="PARAMETER">notifyname</replaceable>
-    is enclosed in double-quotes, it need not even be a syntactically
-    valid name, but can be any string up to 31 characters long.
-   </para>
-   <para>
-    In some previous releases of
-    <productname>PostgreSQL</productname>,
-    <replaceable class="PARAMETER">name</replaceable>
-    had to be enclosed in double-quotes when it did not correspond to any existing
-    table name, even if syntactically valid as a name.  That is no longer required.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-LISTEN-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Configure and execute a listen/notify sequence from <application>psql</application>:
-<programlisting>
-LISTEN virtual;
-NOTIFY virtual;
-
-Asynchronous NOTIFY 'virtual' from backend with pid '8448' received.
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-LISTEN-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-LISTEN-4">
-   <refsect2info>
-    <date>1998-09-01</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>LISTEN</command> in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/load.sgml b/doc/src/sgml/ref/load.sgml
deleted file mode 100644
index 38fad94aaaf..00000000000
--- a/doc/src/sgml/ref/load.sgml
+++ /dev/null
@@ -1,79 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/load.sgml,v 1.12 2002/01/20 22:19:57 petere Exp $
--->
-
-<refentry id="SQL-LOAD">
- <refmeta>
-  <refentrytitle id="SQL-LOAD-TITLE">LOAD</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>LOAD</refname>
-  <refpurpose>load or reload a shared library file</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-LOAD '<replaceable class="PARAMETER">filename</replaceable>'
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="sql-load-description">
-  <title>Description</title>
-
-  <para>
-   Loads a shared library file into the PostgreSQL backend's address
-   space.  If the file had been loaded previously, it is first
-   unloaded.  This command is primarily useful to unload and reload a
-   shared library file that has been changed since the backend first
-   loaded it.  To make use of the
-   shared library, function(s) in it need to be declared using the <xref
-   linkend="sql-createfunction" endterm="sql-createfunction-title"> command.
-  </para>
-
-  <para>
-   The file name is specified in the same way as for shared library
-   names in <xref linkend="sql-createfunction" endterm="sql-createfunction-title">; in particular, one
-   may rely on a search path and automatic addition of the system's standard
-   shared library file name extension.  See the
-   <citetitle>Programmer's Guide</citetitle> for more detail.
-  </para>
- </refsect1>
-
- <refsect1 id="sql-load-compat">
-  <title>Compatibility</title>
-
-  <para>
-   <command>LOAD</command> is a <application>PostgreSQL</application>
-   extension.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <xref linkend="sql-createfunction">,
-   <citetitle>PostgreSQL Programmer's Guide</citetitle>
-  </para>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml
deleted file mode 100644
index e28efe8fad6..00000000000
--- a/doc/src/sgml/ref/lock.sgml
+++ /dev/null
@@ -1,523 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.33 2002/05/30 20:45:18 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-LOCK">
- <refmeta>
-  <refentrytitle id="sql-lock-title">LOCK</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   LOCK
-  </refname>
-  <refpurpose>
-   explicitly lock a table
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2001-07-09</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> [, ...]
-LOCK [ TABLE ] <replaceable class="PARAMETER">name</replaceable> [, ...] IN <replaceable class="PARAMETER">lockmode</replaceable> MODE
-
-where <replaceable class="PARAMETER">lockmode</replaceable> is one of:
-
-	ACCESS SHARE | ROW SHARE | ROW EXCLUSIVE | SHARE UPDATE EXCLUSIVE |
-	SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE | ACCESS EXCLUSIVE
-  </synopsis>
-
-  <refsect2 id="R2-SQL-LOCK-1">
-   <refsect2info>
-    <date>1999-06-09</date>
-   </refsect2info>
-
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of an existing table to lock.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ACCESS SHARE MODE</term>
-      <listitem>
-       <para>
-	This is the least restrictive lock mode.  It conflicts only with
-	ACCESS EXCLUSIVE mode. It is used to protect a table from being
-	modified by concurrent <command>ALTER TABLE</command>, 
-	<command>DROP TABLE</command> and <command>VACUUM FULL</command>
-	commands.
-       </para>
-
-       <note>
-	<para>
-	 The <command>SELECT</command> command acquires a
-	 lock of this mode on referenced tables.  In general, any query
-	 that only reads a table and does not modify it will acquire
-	 this lock mode.
-	</para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ROW SHARE MODE</term>
-      <listitem>
-       <para>
-	Conflicts with EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
-       </para>
-
-       <note>
-       <para>
-	 The <command>SELECT FOR UPDATE</command> command acquires 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</option>).
-	</para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ROW EXCLUSIVE MODE</term>
-      <listitem>
-       <para>
-	 Conflicts with SHARE, SHARE ROW EXCLUSIVE, EXCLUSIVE and
-	 ACCESS EXCLUSIVE modes.
-       </para>
-
-       <note>
-	<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
-	 query that modifies the data in a table.
-        </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>SHARE UPDATE EXCLUSIVE MODE</term>
-      <listitem>
-       <para>
-	Conflicts with SHARE UPDATE EXCLUSIVE, SHARE, SHARE ROW EXCLUSIVE,
-	EXCLUSIVE and
-	ACCESS EXCLUSIVE modes. This mode protects a table against
-	concurrent schema changes and VACUUMs.
-       </para>
-
-       <note>
-       <para>
-	 Acquired by <command>VACUUM</command> (without
-	 <option>FULL</option>).
-       </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>SHARE MODE</term>
-      <listitem>
-       <para>
-	Conflicts with ROW EXCLUSIVE, SHARE UPDATE EXCLUSIVE,
-	SHARE ROW EXCLUSIVE, EXCLUSIVE and
-	ACCESS EXCLUSIVE modes. This mode protects a table against
-	concurrent data changes.
-       </para>
-
-       <note>
-       <para>
-	 Acquired by <command>CREATE INDEX</command>.
-       </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>SHARE ROW EXCLUSIVE MODE</term>
-      <listitem>
-       <para>
-        Conflicts with ROW EXCLUSIVE, SHARE UPDATE EXCLUSIVE, SHARE,
-	SHARE ROW EXCLUSIVE, EXCLUSIVE and ACCESS EXCLUSIVE modes.
-       </para>
-
-       <note>
-       <para>
-         This lock mode is not automatically acquired by any
-         <productname>PostgreSQL</productname> command.
-       </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>EXCLUSIVE MODE</term>
-      <listitem>
-       <para>
-	Conflicts with ROW SHARE, ROW EXCLUSIVE, SHARE UPDATE EXCLUSIVE,
-	SHARE, SHARE ROW EXCLUSIVE,
-	EXCLUSIVE and ACCESS EXCLUSIVE modes.
-	This mode allows only concurrent ACCESS SHARE, i.e., only reads
-	from the table can proceed in parallel with a transaction holding
-	this lock mode.
-       </para>
-
-       <note>
-       <para>
-        This lock mode is not automatically acquired by any
-        <productname>PostgreSQL</productname> command.
-       </para>
-       </note>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ACCESS EXCLUSIVE MODE</term>
-      <listitem>
-       <para>
-	Conflicts with all lock modes.  This mode guarantees that the
-	holder is the only transaction accessing the table in any way.
-       </para>
-
-       <note>
-	<para>
-	 Acquired by <command>ALTER TABLE</command>,
-	 <command>DROP TABLE</command>, and <command>VACUUM FULL</command>
-	 statements.
-	 This is also the default lock mode for <command>LOCK TABLE</command>
-         statements that do not specify a mode explicitly.
-	</para>
-       </note>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-LOCK-2">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-    
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-LOCK TABLE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The lock was successfully acquired.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-ERROR <replaceable class="PARAMETER">name</replaceable>: Table does not exist.
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if <replaceable class="PARAMETER">name</replaceable>
-	does not exist.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-LOCK-1">
-  <refsect1info>
-   <date>1998-09-24</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>LOCK TABLE</command> obtains a table-level lock, waiting if
-   necessary for any conflicting locks to be released.  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.
-  </para>
-
-  <para>
-   For example, suppose an application runs a transaction at 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 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 SHARE lock mode conflicts with the 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 ROW EXCLUSIVE mode
-   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.
-
-   <note>
-    <para>
-     To achieve a similar effect when running a transaction
-     at the SERIALIZABLE isolation level, you have to execute the
-     <command>LOCK TABLE</>
-     statement before executing any DML statement.  A serializable
-     transaction's view of data will be frozen when its first DML statement
-     begins.  A later <command>LOCK</> will still prevent concurrent writes
-     --- but it
-     won't ensure that what the transaction reads corresponds to the latest
-     committed values.
-    </para>
-   </note>
-  </para>
-  
-  <para>
-   If a transaction of this sort is going to
-   change the data in the table, then it should use SHARE ROW EXCLUSIVE lock
-   mode instead of 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 SHARE mode, and then be unable to also
-   acquire ROW EXCLUSIVE mode to actually perform their updates.  (Note that
-   a transaction's own locks never conflict, so a transaction can acquire
-   ROW EXCLUSIVE mode when it holds SHARE mode --- but not if anyone else
-   holds SHARE mode.)
-  </para>
-  
-  <para>
-   Two general rules may be followed to prevent deadlock conditions:
-  </para>
-
-  <itemizedlist>  
-   <listitem>
-    <para>
-     Transactions have to acquire locks on the same objects in the same order.
-    </para>
-   
-    <para>
-     For example, if one application updates row R1 and than updates 
-     row R2 (in the same transaction) then the second application shouldn't 
-     update row R2 if it's going to update row R1 later (in a single transaction). 
-     Instead, it should update rows R1 and R2 in the same order as the first 
-     application.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     If multiple lock modes are involved for a single object,
-     then transactions should always acquire the  most restrictive mode first.
-    </para>
-   
-    <para>
-     An example for this rule was given previously when discussing the 
-     use of SHARE ROW EXCLUSIVE mode rather than SHARE mode.
-    </para>
-
-   </listitem>
-  </itemizedlist>
-
-  <para>
-   <productname>PostgreSQL</productname> does detect deadlocks and will
-   rollback at least one waiting transaction to resolve the deadlock.
-   If it is not practical to code an application to follow the above rules
-   strictly, an alternative solution is to be prepared to retry transactions
-   when they are aborted by deadlocks.
-  </para>
-
-  <para>
-   When locking multiple tables, the command <literal>LOCK a, b;</> is
-   equivalent to <literal>LOCK a; LOCK b;</>. The tables are locked one-by-one
-   in the order specified in the
-   <command>LOCK</command> command.
-  </para>
-
-  <refsect2 id="R2-SQL-LOCK-3">
-   <refsect2info>
-    <date>1999-06-08</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    <literal>LOCK ... IN ACCESS SHARE MODE</> requires <literal>SELECT</>
-    privileges on the target table.  All other forms of <command>LOCK</>
-    require <literal>UPDATE</> and/or <literal>DELETE</> privileges.
-   </para>
-
-   <para>
-    <command>LOCK</command> is useful only inside a transaction block
-    (<command>BEGIN</>...<command>COMMIT</>), since the lock is dropped
-    as soon as the transaction ends.  A <command>LOCK</> command appearing
-    outside any transaction block forms a self-contained transaction, so the
-    lock will be dropped as soon as it is obtained.
-   </para>
-
-  <para>
-   <acronym>RDBMS</acronym> locking uses the following standard terminology:
-
-   <variablelist>
-    <varlistentry>
-     <term>EXCLUSIVE</term>
-     <listitem>
-      <para>
-       An exclusive lock prevents other locks of the same type from being
-       granted.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>SHARE</term>
-     <listitem>
-      <para>
-      A shared lock allows others to also hold the same type of lock,
-      but prevents the corresponding EXCLUSIVE lock from being granted.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>ACCESS</term>
-     <listitem>
-      <para>
-       Locks table schema.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>ROW</term>
-     <listitem>
-      <para>
-       Locks individual rows.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname> does not follow this terminology
-   exactly.  <command>LOCK TABLE</> only deals with table-level locks, and
-   so the mode names involving 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,
-   ROW EXCLUSIVE mode does not follow this naming convention accurately,
-   since it 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.
-  </para>
-
-  </refsect2>
- </refsect1>
-  
- <refsect1 id="R1-SQL-LOCK-2">
-  <title>
-   Usage
-  </title>
-
-  <para>
-   Obtain a 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 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 < 5);
-DELETE FROM films WHERE rating < 5;
-COMMIT WORK;
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-LOCK-3">
-  <title>
-   Compatibility
-  </title>
-	  
-  <refsect2 id="R2-SQL-LOCK-4">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>LOCK TABLE</command> in <acronym>SQL92</acronym>,
-    which instead uses <command>SET TRANSACTION</command> to specify
-    concurrency levels on transactions.  We support that too; see
-    <xref linkend="SQL-SET-TRANSACTION" endterm="SQL-SET-TRANSACTION-TITLE"> for details.
-   </para>
-
-   <para>
-    Except for ACCESS SHARE, ACCESS EXCLUSIVE, and 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>(TM).
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/move.sgml b/doc/src/sgml/ref/move.sgml
deleted file mode 100644
index 0d0d662ada2..00000000000
--- a/doc/src/sgml/ref/move.sgml
+++ /dev/null
@@ -1,148 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/move.sgml,v 1.13 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-MOVE">
- <refmeta>
-  <refentrytitle id="SQL-MOVE-TITLE">MOVE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   MOVE
-  </refname>
-  <refpurpose>
-   position a cursor on a specified row of a table
-  </refpurpose>
- </refnamediv>                
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-MOVE [ <replaceable class="PARAMETER">direction</replaceable> ] [ <replaceable class="PARAMETER">count</replaceable> ] 
-    { IN | FROM } <replaceable class="PARAMETER">cursor</replaceable>
-  </synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-MOVE-1">
-  <refsect1info>
-   <date>1998-09-24</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>MOVE</command> allows a user to move cursor position a specified
-   number of rows.
-   <command>MOVE</command> works like the <command>FETCH</command> command,
-   but only positions the cursor and does
-   not return rows.
-  </para>
-  <para>
-   Refer to 
-   <xref linkend="sql-fetch" endterm="sql-fetch-title">
-   for details on syntax and usage.
-  </para>
-
-  <refsect2 id="R2-SQL-MOVE-3">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    <command>MOVE</command> is a <productname>PostgreSQL</productname>
-    language extension.
-   </para>
-
-   <para>
-    Refer to
-    <xref linkend="sql-fetch" endterm="sql-fetch-title">
-    for a description of valid arguments.
-    Refer to 
-    <xref linkend="sql-declare" endterm="sql-declare-title">
-    to define a cursor.
-    Refer to 
-    <xref linkend="sql-begin" endterm="sql-begin-title">, 
-    <xref linkend="sql-commit" endterm="sql-commit-title">,
-    and
-    <xref linkend="sql-rollback" endterm="sql-rollback-title">
-    for further information about transactions.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-MOVE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Set up and use a cursor:
-
-<programlisting>
-BEGIN WORK;
-DECLARE liahona CURSOR  FOR SELECT * FROM films;
--- Skip first 5 rows:
-MOVE FORWARD 5 IN liahona;
-<computeroutput>
-MOVE
-</computeroutput>
--- Fetch 6th row in the cursor liahona:
-FETCH 1 IN liahona;
-<computeroutput>
-FETCH
-
- code  | title  | did | date_prod | kind   | len
--------+--------+-----+-----------+--------+-------
- P_303 | 48 Hrs | 103 | 1982-10-22| Action | 01:37
-(1 row)
-</computeroutput>
--- close the cursor liahona and commit work:
-CLOSE liahona;
-COMMIT WORK;
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-MOVE-3">
-  <title>
-   Compatibility
-  </title>
-	
-  <refsect2 id="R2-SQL-MOVE-4">
-   <refsect2info>
-    <date>1998-09-01</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <acronym>SQL92</acronym> <command>MOVE</command> statement. 
-    Instead, <acronym>SQL92</acronym> allows
-    one to <command>FETCH</command> rows from an absolute cursor position,
-    implicitly moving the cursor to the correct position.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/notify.sgml b/doc/src/sgml/ref/notify.sgml
deleted file mode 100644
index e21121dabd8..00000000000
--- a/doc/src/sgml/ref/notify.sgml
+++ /dev/null
@@ -1,252 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/notify.sgml,v 1.17 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-NOTIFY">
- <refmeta>
-  <refentrytitle id="sql-notify-title">NOTIFY</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   NOTIFY
-  </refname>
-  <refpurpose>
-   generate a notification
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-NOTIFY <replaceable class="PARAMETER">name</replaceable>        
-  </synopsis>
-
-  <refsect2 id="R2-SQL-NOTIFY-1">
-   <refsect2info>
-    <date>1998-10-07</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">notifyname</replaceable></term>
-      <listitem>
-       <para>
-	Notify condition to be signaled.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-NOTIFY-2">
-   <refsect2info>
-    <date>1998-10-07</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-NOTIFY
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Acknowledgement that notify command has executed.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable>Notify events</replaceable></term>
-      <listitem>
-       <para>
-	Events are delivered to listening frontends; whether and how each frontend
-	application reacts depends on its programming.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-NOTIFY-1">
-  <refsect1info>
-   <date>1998-10-07</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   The <command>NOTIFY</command> command sends a notify event to each
-   frontend application that has previously executed
-   <command>LISTEN <replaceable class="parameter">notifyname</replaceable></command>
-   for the specified notify condition in the current database.
-  </para>
-  <para>
-   The information passed to the frontend for a notify event includes the notify
-   condition name and the notifying backend process's PID.  It is up to the
-   database designer to define the condition names that will be used in a given
-   database and what each one means.
-  </para>
-  <para>
-   Commonly, the notify condition 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 condition names
-   to signal different sorts of changes to a single table.
-  </para>
-  <para>
-   <command>NOTIFY</command> provides a simple form of signal or
-   IPC (interprocess communication) mechanism for a collection of processes
-   accessing the same <productname>PostgreSQL</productname> database.
-   Higher-level mechanisms can be built by using tables in the database to
-   pass additional data (beyond a mere condition name) from notifier to
-   listener(s).
-  </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 can't 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 we would like all the commands within it to have had no
-   effect, including <command>NOTIFY</command>.  But it can be disconcerting if one
-   is expecting the notify events to be delivered immediately.  Secondly, if
-   a listening backend receives a notify signal while it is within a transaction,
-   the notify event will not be delivered to its connected frontend until just
-   after the transaction is completed (either committed or aborted).  Again, the
-   reasoning is that if a notify were delivered within a transaction that was
-   later aborted, one would want the notification to be undone somehow---but
-   the backend cannot <quote>take back</quote> a notify once it has sent it to the frontend.
-   So notify 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>
-   <command>NOTIFY</command> behaves like Unix signals in one important
-   respect: if the same condition name is signaled multiple times in quick
-   succession, recipients may get only one notify event for several executions
-   of <command>NOTIFY</command>.  So it is a bad idea to depend on the number
-   of notifies received.  Instead, use <command>NOTIFY</command> to wake up
-   applications that need to pay attention to something, and use a database
-   object (such as a sequence) to keep track of what happened or how many times
-   it happened.
-  </para>
-  <para>
-   It is common for a frontend that sends <command>NOTIFY</command> to be
-   listening on the same notify name itself.  In that case it will get back a
-   notify event, just like all the other listening frontends.  Depending on the
-   application logic, this could result in useless work---for example,
-   re-reading a database table to find the same updates that that frontend just
-   wrote out.  In <productname>PostgreSQL</productname> 6.4 and later, it is
-   possible to avoid such extra work by noticing whether the notifying backend
-   process's PID (supplied in the notify event message) is the same as one's own
-   backend's PID (available from libpq).  When they are the same, the notify
-   event is one's own work bouncing back, and can be ignored.  (Despite what was
-   said in the preceding paragraph, this is a safe technique.
-   <productname>PostgreSQL</productname> keeps self-notifies separate from notifies
-   arriving from other backends, so you cannot miss an outside notify by ignoring
-   your own notifies.)
-  </para>
-
-  <refsect2 id="R2-SQL-NOTIFY-3">
-   <refsect2info>
-    <date>1998-10-07</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    <replaceable class="PARAMETER">name</replaceable>
-    can be any string valid as a name;
-    it need not correspond to the name of any actual table.  If
-    <replaceable class="PARAMETER">name</replaceable>
-    is enclosed in double-quotes, it need not even be a syntactically
-    valid name, but can be any string up to 31 characters long.
-   </para>
-   <para>
-    In some previous releases of
-    <productname>PostgreSQL</productname>,
-    <replaceable class="PARAMETER">name</replaceable>
-    had to be enclosed in double-quotes when it did not correspond to any existing
-    table name, even if syntactically valid as a name.  That is no longer required.
-   </para>
-   <para>
-    In <productname>PostgreSQL</productname> releases prior to 6.4, the backend
-    PID delivered in a notify message was always the PID of the frontend's own
-    backend.  So it was not possible to distinguish one's own notifies from other
-    clients' notifies in those earlier releases.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-NOTIFY-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Configure and execute a listen/notify sequence from
-   <application>psql</application>:
-
-<programlisting>
-LISTEN virtual;
-NOTIFY virtual;
-Asynchronous NOTIFY 'virtual' from backend with pid '8448' received. 
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-NOTIFY-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-NOTIFY-4">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>NOTIFY</command> statement in
-    <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/pg_config-ref.sgml b/doc/src/sgml/ref/pg_config-ref.sgml
deleted file mode 100644
index b7f1a42014a..00000000000
--- a/doc/src/sgml/ref/pg_config-ref.sgml
+++ /dev/null
@@ -1,165 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.10 2002/04/21 19:02:39 thomas Exp $ -->
-
-<refentry id="app-pgconfig">
- <refmeta>
-  <refentrytitle id="app-pgconfig-title">pg_config</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_config</refname>
-  <refpurpose>retrieve information about the installed version of <productname>PostgreSQL</></refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_config</command>
-   <group choice="req" rep="repeat">
-    <arg>--bindir</arg>
-    <arg>--includedir</arg>
-    <arg>--includedir-server</arg>
-    <arg>--libdir</arg>
-    <arg>--pkglibdir</arg>
-    <arg>--configure</arg>
-    <arg>--version</arg>
-   </group>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</>
-  <para>
-   The <application>pg_config</> utility prints configuration parameters
-   of the currently installed version of <productname>PostgreSQL</>. It is
-   intended, for example, to be used by software packages that want to interface
-   to <productname>PostgreSQL</> to facilitate finding the required header files
-   and libraries.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Options</title>
-
-  <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 <application>psql</> program. This is normally also the location
-       where the <filename>pg_config</> program resides.       
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--includedir</option></>
-     <listitem>
-      <para>
-       Print the location of C and C++ header files of the client interfaces.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--includedir-server</option></>
-     <listitem>
-      <para>
-       Print the location of C and 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 may also be installed in this
-       directory.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--configure</option></>
-     <listitem>
-      <para>
-       Print the options that were given to the <filename>configure</>
-       script when <productname>PostgreSQL</> was configured for building.
-       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.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><option>--version</option></>
-     <listitem>
-      <para>
-       Print the version of <productname>PostgreSQL</> and exit.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-
-   If more than one option (except for <option>--version</>) is given, the
-   information is printed in that order, one item per line.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The option <option>--includedir-server</option> is new in
-   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>--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>
-   In releases prior to PostgreSQL 7.1, before the
-   <command>pg_config</command> came to be, a method for finding the
-   equivalent configuration information did not exist.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>History</title>
-
-  <para>
-   The <command>pg_config</command> utility first appeared in PostgreSQL 7.1.
-  </para>
- </refsect1>
-
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <citetitle>PostgreSQL Programmer's Guide</citetitle>
-  </para>
- </refsect1>
-</refentry>
diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml
deleted file mode 100644
index da545ab6fe2..00000000000
--- a/doc/src/sgml/ref/pg_ctl-ref.sgml
+++ /dev/null
@@ -1,368 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_ctl-ref.sgml,v 1.14 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="app-pg-ctl">
- <refmeta>
-  <refentrytitle id="app-pg-ctl-title"><application>pg_ctl</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_ctl</refname>
-  <refpurpose>start, stop, or restart a <productname>PostgreSQL</productname> server</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_ctl</command>
-   <arg choice="plain">start</arg>
-   <arg>-w</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>
-   <sbr>
-   <command>pg_ctl</command>
-   <arg choice="plain">stop</arg>
-   <arg>-W</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>
-   <sbr>
-   <command>pg_ctl</command>
-   <arg choice="plain">restart</arg>
-   <arg>-w</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>
-   <arg>-o <replaceable>options</replaceable></arg>
-   <sbr>
-   <command>pg_ctl</command>
-   <arg choice="plain">reload</arg>
-   <arg>-s</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <sbr>
-   <command>pg_ctl</command>
-   <arg choice="plain">status</arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="app-pg-ctl-description">
-  <title>Description</title>
-  <para>
-   <application>pg_ctl</application> is a utility for starting,
-   stopping, or restarting <xref linkend="app-postmaster">, the
-   <productname>PostgreSQL</productname> backend server, or displaying
-   the status of a running postmaster.  Although the postmaster can be
-   started manually, <application>pg_ctl</application> encapsulates
-   tasks such as redirecting log output, properly detaching from the
-   terminal and process group, and it provides convenient options for
-   controlled shutdown.
-  </para>
-
-  <para>
-   In <option>start</option> mode, a new postmaster is launched.  The
-   server is started in the background, the standard input attached to
-   <filename>/dev/null</filename>.  The standard output and standard
-   error are either appended to a log file, if the <option>-l</option>
-   option is used, or are redirected to
-   <application>pg_ctl</application>'s standard output (not standard
-   error).  If no log file is chosen, the standard output of
-   <application>pg_ctl</application> should be redirected to a file or
-   piped to another process, for example a log rotating program,
-   otherwise the postmaster will write its output the the controlling
-   terminal (from the background) and will not leave the shell's
-   process group.
-  </para>
-
-  <para>
-   In <option>stop</option> mode, the postmaster 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 all the clients to
-   disconnect.  This is the default.  <quote>Fast</quote> mode does
-   not wait for clients to disconnect.  All active transactions are
-   rolled back and clients are forcibly disconnected, then the
-   database is shut down.  <quote>Immediate</quote> mode will abort
-   all server processes without 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 the changing of postmaster command line
-   options.
-  </para>
-
-  <para>
-   <option>reload</option> mode simply sends the postmaster 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 postmaster is running
-   and if so displays the <acronym>PID</acronym> and the command line
-   options that were used to invoke it.
-  </para>
-
-  <refsect2 id="app-pg-ctl-options">
-   <title>Options</title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>-D <replaceable class="parameter">datadir</replaceable></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>-l <replaceable class="parameter">filename</replaceable></term>
-      <listitem>
-       <para>
-        Append the server log output to
-        <replaceable>filename</replaceable>.  If the file does not
-        exist, it is created.  The umask is set to 077, so access to
-        the log file from other users is disallowed by default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-m <replaceable class="parameter">mode</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the shutdown mode.  <replaceable>mode</replaceable>
-	may 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>-o <replaceable class="parameter">options</replaceable></term>
-      <listitem>
-       <para>
-        Specifies options to be passed directly to
-	<application>postmaster</application>.
-       </para>
-       <para>
-	The parameters are usually surrounded by single or double
-	quotes to ensure that they are passed through as a group.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-p <replaceable class="parameter">path</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the location of the <filename>postmaster</filename>
-	executable.  By default the postmaster is taken from the same
-	directory as <command>pg_ctl</>, 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 postmaster was not found.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-s</term>
-      <listitem>
-       <para>
-        Only print errors, no informational messages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-w</term>
-      <listitem>
-       <para>
-	Wait for the start or shutdown to complete.  Times out after
-	60 seconds.  This is the default for shutdowns.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-W</term>
-      <listitem>
-       <para>
-        Do not wait for start or shutdown to complete.  This is the
-        default for starts and restarts.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2>
-   <title>Files</title>
-
-   <para>
-    If the file <filename>postmaster.opts.default</filename> exists in
-    the data directory, the contents of the file will be passed as
-    options to the <application>postmaster</application>, unless
-    overridden by the <option>-o</option> option.
-   </para>
-  </refsect2>
-
- </refsect1>
-
-
- <refsect1 id="R1-APP-PGCTL-2">
-  <title>Examples</title>
-
-  <refsect2 id="R2-APP-PGCTL-3">
-   <title>Starting the postmaster</title>
-
-   <para>
-    To start up a <application>postmaster</application>:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl start</userinput>
-</screen>
-   </para>
-
-   <para>
-    An example of starting the <application>postmaster</application>,
-    blocking until the postmaster comes up is:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl -w start</userinput>
-</screen>
-   </para>
-
-   <para>
-    For a <application>postmaster</application> 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 postmaster</title>
-   <para>
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl stop</userinput>
-</screen>
-    stops the postmaster. 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 postmaster</title>
-
-   <para>
-    This is almost equivalent to stopping the
-    <application>postmaster</application> 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 <application>postmaster</application> in the simplest form:
-<screen>
-<prompt>$</prompt> <userinput>pg_ctl restart</userinput>
-</screen>
-   </para>
-
-   <para>
-    To restart <application>postmaster</application>,
-    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 postmaster 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: postmaster is running (pid: 13718)
-Command line was:
-/usr/local/pgsql/bin/postmaster '-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>Bugs</title>
-
-  <para>
-   Waiting for complete start is not a well-defined operation and may
-   fail if access control is set up so that a local client cannot
-   connect without manual interaction.  It should be avoided.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <xref linkend="app-postmaster">, <citetitle>PostgreSQL Administrator's Guide</citetitle>
-  </para>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
deleted file mode 100644
index d2ab719fe34..00000000000
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ /dev/null
@@ -1,745 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.45 2002/05/10 22:36:26 tgl Exp $
-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>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_dump</command>
-   <group> <arg>-a</arg> <arg>-s</arg> </group>
-   <arg>-b</arg>
-   <arg>-c</arg>
-   <arg>-C</arg>
-   <group> <arg>-d</arg> <arg>-D</arg> </group>
-   <arg>-f <replaceable>file</replaceable></arg> 
-   <arg>-F <replaceable>format</replaceable></arg>
-   <arg>-i</arg>
-   <group> <arg>-n</arg> <arg>-N</arg> </group>
-   <arg>-o</arg>
-   <arg>-O</arg>
-   <arg>-R</arg>
-   <arg>-S</arg>
-   <arg>-t <replaceable>table</replaceable></arg>
-   <arg>-v</arg>
-   <arg>-x</arg>
-   <arg>-X <replaceable>keyword</replaceable></arg>
-   <arg>-Z <replaceable>0...9</replaceable></arg>
-   <arg>-h <replaceable>host</replaceable></arg>
-   <arg>-p <replaceable>port</replaceable></arg>
-   <arg>-U <replaceable>username</replaceable></arg>
-   <arg>-W</arg>
-   <arg choice="plain"><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="pg-dump-description">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>pg_dump</command> is a utility for saving a
-   <productname>PostgreSQL</productname> database into a script or an
-   archive file.  The script files are in plain-text format and
-   contain the SQL commands required to reconstruct the database to
-   the state it was in at the time it was saved.  They can be used to
-   reconstruct the database even on other machines and other
-   architectures, with some modifications even on other RDBMS
-   products.  Furthermore, there are alternative archive file formats that
-   are meant to be
-   used with <xref linkend="app-pgrestore"> to rebuild the database,
-   and they also allow <command>pg_restore</command> to be selective
-   about what is restored, or even to reorder the items prior to being
-   restored. The archive files are also designed to be portable across
-   architectures.
-  </para>
-
-  <para>
-   <command>pg_dump</command> will save the information necessary to
-   re-generate all user-defined types, functions, tables, indexes,
-   aggregates, and operators.  In addition, all the data is copied out
-   in text format so that it can be readily copied in again, as well
-   as imported into tools for editing.
-  </para>
-
-  <para>
-   <command>pg_dump</command> 
-   is useful for dumping out the contents of a database to move from one
-   <productname>PostgreSQL</productname> installation to another.
-  </para>
-
-  <para>
-   When used with one of the archive file formats and combined with
-   <xref linkend="app-pgrestore">, <command>pg_dump</command> provides a
-   flexible archival and 
-   transfer mechanism. <command>pg_dump</command> can be used to
-   backup an entire database, then <command>pg_restore</command> 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. The
-   <filename>tar</filename> format (<option>-Ft</option>) is not
-   compressed and it is not possible to reorder data when loading, but
-   it is otherwise quite flexible; moreover, it can be manipulated with
-   other tools such as <filename>tar</filename>.
-  </para>
-
-  <para>
-   While running <command>pg_dump</command>, one should examine the
-   output for any warnings (printed on standard error), especially in
-   light of the limitations listed below.
-  </para>
-
-  <para>
-   <command>pg_dump</command> makes consistent backups even if the
-   database is being used concurrently.  <command>pg_dump</command>
-   does not block other users accessing the database (readers or
-   writers).
-  </para>
-
-  <refsect2 id="pg-dump-options">
-   <title>Options</title>
-
-   <para>
-    <command>pg_dump</command> accepts the following command
-    line arguments.  (Long option forms are only available on some platforms.)
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">dbname</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the name of the database to be dumped.
-       </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 other formats, you may 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 dump.
-       </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 (the commands for) creating them.
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the other formats, you may 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 other formats, you may specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-d</option></term>
-      <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, but it makes the archives more portable to other RDBMS
-	packages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-D</option></term>
-      <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,
-	but it is necessary if you desire to rearrange column ordering.
-       </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.  If this is omitted, the
-	standard output is used.
-       </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>p</term>
-         <listitem>
-          <para>
-           Output a plain-text <acronym>SQL</acronym> script file (default)
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term>t</term>
-         <listitem>
-          <para>
-         Output a <filename>tar</filename> archive suitable for input into 
-         <command>pg_restore</command>. Using this archive format 
-         allows reordering and/or exclusion of schema elements 
-         at the time the database is restored. It is also possible to limit 
-         which data is reloaded at restore time.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term>c</term>
-         <listitem>
-          <para>
-         Output a custom archive suitable for input into 
-         <command>pg_restore</command>. This is the most flexible 
-         format in that it allows reordering of data load as well 
-         as schema elements. This format is also compressed by default.
-          </para>
-         </listitem>
-        </varlistentry>
-
-       </variablelist>
-       </para>
-
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</></term>
-      <term><option>--ignore-version</></term>
-      <listitem>
-       <para>
-        Ignore version mismatch between <command>pg_dump</command>
-	and the database server.  Since <command>pg_dump</command>
-	knows a great deal about system catalogs, any given version of
-	<command>pg_dump</command> is only intended to work with
-	the corresponding release of the database server.  Use this option
-	if you need to override the version check (and if
-	<command>pg_dump</command> then fails, don't
-	say you weren't warned).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-n</></term>
-      <term><option>--no-quotes</></term>
-      <listitem>
-       <para>
-	Suppress double quotes around identifiers unless absolutely necessary.
-	This may cause trouble loading this dumped data if there are reserved words
-	used for identifiers. 
-	This was the default behavior for
-	<command>pg_dump</command> prior to version 6.4.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-N</></term>
-      <term><option>--quotes</></term>
-      <listitem>
-       <para>
-	Include double quotes around identifiers.
-	This is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o</></term>
-      <term><option>--oids</></term>
-      <listitem>
-       <para>
-	Dump object identifiers (<acronym>OID</acronym>s) for every
-	table.  Use this option if your application references the 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 the
-	object ownership to match the original database.  Typically,
-	<command>pg_dump</command> issues
-	(<command>psql</command>-specific) <command>\connect</command>
-	statements to set ownership of schema elements.  See also
-	under <option>-R</option> and <option>-X
-	use-set-session-authorization</option>.  Note that
-	<option>-O</option> does not prevent all reconnections to the
-	database, only the ones that are exclusively used for
-	ownership adjustments.
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the other formats, you may 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>
-	Prohibit <command>pg_dump</command>
-        from outputting a script that would require reconnections to
-        the database while being restored.  An average restoration
-        script usually has to reconnect several times as different
-        users to set the original ownerships of the objects.  This
-        option is a rather blunt instrument because it makes
-        <command>pg_dump</command> lose this ownership information,
-        <emphasis>unless</emphasis> you use the <option>-X
-        use-set-session-authorization</option> option.
-       </para>
-
-       <para>
-        One possible reason why reconnections during restore might not
-        be desired is if the access to the database requires manual
-        interaction (e.g., passwords).
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the other formats, you may specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <term><option>--schema-only</option></term>
-      <listitem>
-       <para>
-	Dump only the schema (data definitions), no 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 specify
-	<option>--use-set-session-authorization</>, and then 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 data for <replaceable class="parameter">table</replaceable> only.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-v</></term>
-      <term><option>--verbose</></term>
-      <listitem>
-       <para>
-	Specifies verbose mode.
-       </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>-X use-set-session-authorization</></term>
-      <term><option>--use-set-session-authorization</></term>
-      <listitem>
-       <para>
-        Normally, if a (plain-text mode) script generated by
-        <command>pg_dump</command> must alter the current database
-        user (e.g., to set correct object ownerships), it uses the
-        <xref linkend="app-psql"> <command>\connect</command> command.
-        This command actually opens a new connection, which might
-        require manual interaction (e.g., passwords).  If you use the
-        <option>-X use-set-session-authorization</option> option, then
-        <command>pg_dump</command> will instead output <xref
-        linkend="sql-set-session-authorization" endterm="sql-set-session-authorization-title"> commands.  This has
-        the same effect, but it requires that the user restoring the
-        database from the generated script be a database superuser.
-        This option effectively overrides the <option>-R</option>
-        option.
-       </para>
-
-       <para>
-        Since <xref linkend="sql-set-session-authorization" endterm="sql-set-session-authorization-title"> is a
-        standard SQL command, whereas <command>\connect</command> only
-        works in <xref linkend="app-psql">, this option also enhances
-        the theoretical portability of the output script.
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the other formats, you may specify the option when you
-        call <command>pg_restore</command>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-X disable-triggers</></term>
-      <term><option>--disable-triggers</></term>
-      <listitem>
-       <para>
-        This option is only relevant when creating a data-only dump.
-	It instructs <command>pg_dump</command> 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 specify
-	<option>--use-set-session-authorization</> and then be careful to
-	start the resulting script as a superuser.  If you give neither
-	option, the entire script must be run as superuser.
-       </para>
-
-       <para>
-        This option is only meaningful for the plain-text format.  For
-        the other formats, you may specify the option when you
-        call <command>pg_restore</command>.
-       </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 in archive formats that support 
-      compression (currently only the custom archive format supports compression).
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-    </variablelist>
-   </para>
-   <para>
-    <command>pg_dump</command> 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 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></option></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></option></term>
-      <listitem>
-       <para>
-	Specifies the Internet TCP/IP port or local Unix domain socket file 
-	extension on which the server
-	is listening for connections.  The port number defaults to 5432,
-	or the value of the <envar>PGPORT</envar>
-	environment variable (if set).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable>username</replaceable></option></term>
-      <listitem>
-       <para>
-        Connect as the given user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <listitem>
-       <para>
-        Force a password prompt.  This should happen automatically if
-        the server requires password authentication.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
- </refsect1>
-
- <refsect1 id="app-pgdump-diagnostics">
-  <title>Diagnostics</title>
-
-  <msgset>
-   <msgentry>
-    <msg>
-     <msgmain>
-      <msgtext>
-<screen><computeroutput>
-Connection to database 'template1' failed.
-connectDBStart() -- connect() failed: No such file or directory
-        Is the postmaster running locally
-        and accepting connections on Unix socket '/tmp/.s.PGSQL.5432'?
-</computeroutput></screen>
-      </msgtext>
-     </msgmain> 
-    </msg>
-
-    <msgexplan>
-       <para>
-	<command>pg_dump</command> could not attach to the 
-	<command>postmaster</command> 
-	process on the specified host and port.  If you see this message,
-	ensure that the <command>postmaster</command> 
-	is running on the proper host and that you have specified the proper
-	port.
-       </para>
-    </msgexplan>
-   </msgentry>
-
-  </msgset>
-
-   <note>
-    <para>
-     <command>pg_dump</command> internally executes
-     <command>SELECT</command> statements. If you have problems running
-     <command>pg_dump</command>,
-     make sure you are able to select information from the database using, for
-     example, <xref linkend="app-psql">.
-    </para>
-   </note>
- </refsect1>
-
-
- <refsect1 id="pg-dump-notes">
-  <title>Notes</title>
-
-  <para>
-   If your installation has any local additions to the template1 database,
-   be careful to restore the output of <command>pg_dump</command> 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 template0 not template1,
-   for example:
-<programlisting>
-CREATE DATABASE foo WITH TEMPLATE = template0;
-</programlisting>
-  </para>
-
-  <para>
-   <command>pg_dump</command> has a few limitations:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      When dumping a single table or as plain text, <command>pg_dump</command> 
-      does not handle large objects. Large objects must be dumped in their
-      entirety using one of the binary archive formats.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      When doing a data only dump, <command>pg_dump</command> emits queries
-      to disable triggers on user tables before inserting the data and queries to
-      re-enable them after the data has been inserted.  If the restore is stopped
-      in the middle, the system catalogs may be left in the wrong state.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </para>
- </refsect1>
-
- <refsect1 id="pg-dump-examples">
-  <title>Examples</title>
-
-  <para>
-   To dump a database:
-<screen>
-<prompt>$</prompt> <userinput>pg_dump mydb &gt; db.out</userinput>
-</screen>
-  </para>
-
-  <para>
-   To reload this database:
-<screen>
-<prompt>$</prompt> <userinput>psql -d database -f db.out</userinput>
-</screen>
-  </para>
-
-  <para>
-   To dump a database called <literal>mydb</> that contains
-   large objects to a <filename>tar</filename> file:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -Ft -b mydb &gt; db.tar</userinput>
-</screen>
-  </para>
-
-  <para>
-   To reload this database (with large objects) to an
-   existing database called <literal>newdb</>:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_restore -d newdb db.tar</userinput>
-</screen>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>History</title>
-
-  <para>
-   The <command>pg_dump</command> utility first appeared in
-   <application>Postgres95</application> release <literal>0.02</literal>.  The
-   non-plain-text output formats were introduced in
-   <application>PostgreSQL</application> release <literal>7.1</literal>.
-  </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>
-   <member><citetitle>PostgreSQL Administrator's Guide</citetitle></member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/pg_dumpall.sgml b/doc/src/sgml/ref/pg_dumpall.sgml
deleted file mode 100644
index 44e38f28bc6..00000000000
--- a/doc/src/sgml/ref/pg_dumpall.sgml
+++ /dev/null
@@ -1,203 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.28 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-PG-DUMPALL">
- <refmeta>
-  <refentrytitle id="APP-PG-DUMPALL-TITLE"><application>pg_dumpall</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pg_dumpall</refname>
-  <refpurpose>extract all <productname>PostgreSQL</productname> databases into a script file</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_dumpall</command>
-   <group><arg>-c</arg><arg>--clean</arg></group>
-   <group><arg>-g</arg><arg>--globals-only</arg></group>
-   <arg>-h <replaceable>host</replaceable></arg>
-   <arg>-p <replaceable>port</replaceable></arg>
-   <arg>-U <replaceable>username</replaceable></arg>
-   <arg>-W</arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="app-pg-dumpall-description">
-  <title>Description</title>
-
-  <para>
-   <application>pg_dumpall</application> is a utility for writing out
-   (<quote>dumping</quote>) all PostgreSQL databases of a cluster into
-   one script file.  The script file contains SQL 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 the information about database users and
-   groups.
-  </para>
-
-  <para>
-   Thus, <application>pg_dumpall</application> is an integrated
-   solution for backing up your databases.  But note a limitation:
-   it cannot dump <quote>large objects</quote>, since
-   <application>pg_dump</application> cannot dump such objects into
-   text files.  If you have databases containing large objects,
-   they should be dumped using one of <application>pg_dump</application>'s
-   non-text output modes.
-  </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.  Shell
-   operators should be used to redirect it into a file.
-  </para>
-
-  <refsect2>
-   <title>Options</title>
-
-   <para>
-    <application>pg_dumpall</application> accepts the following
-    command line arguments:
-
-    <variablelist>
-     <varlistentry>
-      <term>-c, --clean</term>
-      <listitem>
-       <para>
-	Include SQL commands to clean (drop) database objects before
-	recreating them.  (This option is fairly useless, since the
-	output script expects to create the databases themselves;
-	they would always be empty upon creation.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-g, --globals-only</term>
-      <listitem>
-       <para>
-	Only dump global objects (users and groups), no databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-h <replaceable>host</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the host name of the machine on which the database
-	server is running.  If host 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>-p <replaceable>port</replaceable></term>
-      <listitem>
-       <para>
-        The port number on which the server is listening.  Defaults to
-        the <envar>PGPORT</envar> environment variable, if set, or a
-        compiled-in default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-U <replaceable>username</replaceable></term>
-      <listitem>
-       <para>
-        Connect as the given user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-W</term>
-      <listitem>
-       <para>
-        Force a password prompt.  This should happen automatically if
-        the server requires password authentication.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    Any other command line parameters are passed to the underlying
-    <xref linkend="app-pgdump">
-    calls.  This is useful to control some aspects of the output
-    format, but some options such as <option>-f</option>,
-    <option>-t</option>, and <replaceable
-    class="parameter">dbname</replaceable> should be avoided.
-   </para>
-  </refsect2>
- </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 this database use, for example:
-<screen>
-<prompt>$</prompt> <userinput>psql -f db.out template1</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>
-    <xref linkend="app-pgdump">, <xref linkend="app-psql">.  Check
-    there for details on possible error conditions.
-  </para>
- </refsect1>   
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml
deleted file mode 100644
index aa87e2e6f44..00000000000
--- a/doc/src/sgml/ref/pg_restore.sgml
+++ /dev/null
@@ -1,706 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.25 2002/05/10 22:36:26 tgl Exp $ -->
-
-<refentry id="APP-PGRESTORE">
- <docinfo>
-  <date>2001-03-06</date>
- </docinfo>
-
- <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 pg_dump
-  </refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pg_restore</command>
-   <arg> -a </arg>
-   <arg> -c </arg>
-   <arg> -C </arg>
-   <arg> -d <replaceable class="parameter">dbname</replaceable> </arg>
-   <arg> -f <replaceable class="parameter">output-file</replaceable> </arg>
-   <arg> -F <replaceable class="parameter">format</replaceable> </arg>
-   <arg> -i  <replaceable class="parameter">index</replaceable> </arg>
-   <arg> -l </arg>
-   <arg> -L <replaceable class="parameter">contents-file</replaceable> </arg>
-   <group> <arg> -N </arg> <arg> -o </arg> <arg> -r </arg> </group>
-   <arg> -O </arg>
-   <arg> -P <replaceable class="parameter">function-name</replaceable> </arg>
-   <arg> -R </arg>
-   <arg> -s </arg>
-   <arg> -S </arg>
-   <arg> -t  <replaceable class="parameter">table</replaceable> </arg>
-   <arg> -T  <replaceable class="parameter">trigger</replaceable> </arg>
-   <arg> -v </arg>
-   <arg> -x </arg>
-   <arg> -X <replaceable>keyword</replaceable></arg>
-   <arg> -h  <replaceable class="parameter">host</replaceable> </arg>
-   <arg> -p  <replaceable class="parameter">port</replaceable> </arg>
-   <arg> -U <replaceable>username</replaceable> </arg>
-   <arg> -W </arg>
-   <arg> <replaceable class="parameter">archive-file</replaceable> </arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
-
- <refsect1 id="app-pgrestore-description">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>pg_restore</command> 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 re-generate all user-defined
-   types, functions, tables, indexes, aggregates, and operators, as
-   well as the data in the tables.
-  </para>
-
-  <para>
-   The archive files contain information for
-   <command>pg_restore</command> to rebuild the database, but also
-   allow <command>pg_restore</command> 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>
-   <command>pg_restore</command> can operate in two modes:  If a
-   database name is specified, the archive is restored 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), similar to the ones created by the
-   <command>pg_dump</command> plain text format.  Some of the options
-   controlling the script output are therefore analogous to
-   <command>pg_dump</command> options.
-  </para>
-
-  <para>
-   Obviously, <command>pg_restore</command> 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>s</quote> option,
-   <command>pg_restore</command> will not be able to load the data
-   using <command>COPY</command> statements.
-  </para>
-
-  <refsect2 id="app-pgrestore-options">
-   <title>
-    Options
-   </title>
-
-   <para>
-    <command>pg_restore</command> accepts the following command
-    line arguments.  (Long option forms are only available on some platforms.)
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">archive-name</replaceable></term>
-      <listitem>
-       <para>
-       Specifies the location of the archive file 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, no schema (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 switch appears, the database named with <option>-d</option>
-	is used only 
-	to issue the initial 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. Large objects can only be restored by using a direct database connection.
-       </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 <COMMAND>pg_restore</COMMAND> will
-        determine the format automatically. If specified, it can be one of the following:
-       </para>
-
-       <variablelist>
-
-        <varlistentry>
-         <term>t</term>
-         <listitem>
-          <para>
-           Archive is a <filename>tar</filename> archive. Using this archive format allows reordering and/or
-           exclusion of schema elements at the time the database is restored. It is also possible to limit which
-           data is reloaded at restore time.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term>c</term>
-         <listitem>
-          <para>
-           Archive is in the custom format of <command>pg_dump</command>. This is the most flexible format
-           in that it allows reordering of data load as well as schema elements.
-           This format is also compressed by default.
-          </para>
-         </listitem>
-        </varlistentry>
-
-       </variablelist>
-
-      </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 for named <replaceable class="parameter">index</replaceable> only.
-       </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 command can be used with the <option>-L</option> option
-        to restrict and reorder the items that are restored.
-       </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 elements in <REPLACEABLE CLASS="PARAMETER">list-file</REPLACEABLE> only, and in the
-        order they appear in the file. Lines can be moved and may also be commented out by placing a <literal>;</literal> at the
-        start of the line.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-N</option></term>
-      <term><option>--orig-order</option></term>
-      <listitem>
-       <para>
-        Restore items in the original dump order. By default <command>pg_dump</command> will dump items in an order convenient
-        to <command>pg_dump</command>, then save the archive in a modified OID order. This option overrides the OID ordering.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o</option></term>
-      <term><option>--oid-order</option></term>
-      <listitem>
-       <para>
-        Restore items in the OID order. By default <command>pg_dump</command> will dump items in an order convenient
-        to <command>pg_dump</command>, then save the archive in a modified OID order. This option enforces strict OID ordering.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-O</option></term>
-      <term><option>--no-owner</option></term>
-      <listitem>
-       <para>
-        Prevent any attempt to restore original object ownership. Objects will be owned by the user name used
-        to attach to the database.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-P <replaceable class="parameter">function-name</replaceable></option></term>
-      <term><option>--function=<replaceable class="parameter">function-name</replaceable></option></term>
-      <listitem>
-       <para>
-        Specify a procedure or function to be restored.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-r</option></term>
-      <term><option>--rearrange</option></term>
-      <listitem>
-       <para>
-        Restore items in modified OID order. By default <command>pg_dump</command> will dump items in an order convenient
-        to <command>pg_dump</command>, then save the archive in a modified OID order. Most objects
-        will be restored in OID order, but some things (e.g., rules and indexes) will be restored at the end of
-        the process irrespective of their OIDs. This option is the default.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-R</option></term>
-      <term><option>--no-reconnect</option></term>
-      <listitem>
-       <para>
-        While restoring an archive, <command>pg_restore</command>
-        typically has to reconnect to the database several times with
-        different user names to set the correct ownership of the
-        created objects.  If this is undesirable (e.g., because manual
-        interaction (passwords) would be necessary for each
-        reconnection), this option prevents
-        <command>pg_restore</command> from issuing any reconnection
-        requests.  (A connection request while in plain text mode, not
-        connected to a database, is made by putting out a <xref
-        linkend="app-psql"> <command>\connect</command> command.)
-        However, this option is a rather blunt instrument because it
-        makes <command>pg_restore</command> lose all object ownership
-        information, <emphasis>unless</emphasis> you use the
-        <option>-X use-set-session-authorization</option> option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <term><option>--schema-only</option></term>
-      <listitem>
-       <para>
-	Restore the schema (definitions), no data. Sequence values will be reset.
-       </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 schema/data for <REPLACEABLE CLASS="PARAMETER">table</REPLACEABLE> only.
-       </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 definition of <REPLACEABLE CLASS="PARAMETER">trigger</REPLACEABLE> 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>-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>-X use-set-session-authorization</option></term>
-      <term><option>--use-set-session-authorization</option></term>
-      <listitem>
-       <para>
-        Normally, if restoring an archive requires altering the
-        current database user (e.g., to set correct object
-        ownerships), a new connection to the database must be opened,
-        which might require manual interaction (e.g., passwords).  If
-        you use the <option>-X use-set-session-authorization</option> option,
-        then <command>pg_restore</command> will instead use the <xref
-        linkend="sql-set-session-authorization"> command.  This has
-        the same effect, but it requires that the user restoring the
-        archive is a database superuser.  This option effectively
-        overrides the <option>-R</option> option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-X disable-triggers</></term>
-      <term><option>--disable-triggers</></term>
-      <listitem>
-       <para>
-        This option is only relevant when performing a data-only restore.
-	It instructs <command>pg_restore</command> 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 specify
-	<option>--use-set-session-authorization</> and run
-	<command>pg_restore</command> as a superuser.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <command>pg_restore</command> 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 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></option></term>
-      <term><option>--port=<replaceable class="parameter">port</replaceable></option></term>
-      <listitem>
-       <para>
-	Specifies the Internet TCP/IP port or local Unix domain socket file
-	extension on which the server
-	is listening for connections.  The port number defaults to 5432,
-	or the value of the <envar>PGPORT</envar>
-	environment variable (if set).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-U <replaceable>username</replaceable></option></term>
-      <listitem>
-       <para>
-        Connect as the given user.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option></term>
-      <listitem>
-       <para>
-        Force a password prompt.  This should happen automatically if
-        the server requires password authentication.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
- </refsect1>
-
-
- <refsect1 id="app-pgrestore-diagnostics">
-  <title>Diagnostics</title>
-
-  <msgset>
-   <msgentry>
-    <msg>
-     <msgmain>
-      <msgtext>
-<screen><computeroutput>
-Connection to database 'template1' failed.
-connectDBStart() -- connect() failed: No such file or directory
-        Is the postmaster running locally
-        and accepting connections on Unix socket '/tmp/.s.PGSQL.5432'?
-</computeroutput></screen>
-      </msgtext>
-     </msgmain>
-    </msg>
-
-    <msgexplan>
-       <para>
-	<command>pg_restore</command> could not attach to the
-	<command>postmaster</command>
-	process on the specified host and port.  If you see this message,
-	ensure that the server
-	is running on the proper host and that you have specified the proper
-	port.  If your site uses an authentication system, ensure that you
-	have obtained the required authentication credentials.
-       </para>
-    </msgexplan>
-   </msgentry>
-  </msgset>  
-
-   <note>
-    <para>
-     When a direct database connection is specified using the -d option, <command>pg_restore</command>
-     internally executes  <command>SQL</command> statements. If you  have problems running
-     <command>pg_restore</command>,
-     make sure you are able to select information from the database using, for
-     example, <command>psql</command>.
-    </para>
-   </note>
- </refsect1>
-
-
- <refsect1 id="app-pgrestore-notes">
-  <title>
-   Notes
-  </title>
-
-  <para>
-   If your installation has any local additions to the template1 database,
-   be careful to load the output of <command>pg_restore</command> 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 template0 not template1,
-   for example:
-<programlisting>
-CREATE DATABASE foo WITH TEMPLATE = template0;
-</programlisting>
-  </para>
-
-  <para>
-   The limitations of <command>pg_restore</command> are detailed below.
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      When restoring data to a pre-existing table, <command>pg_restore</command> emits queries
-      to disable triggers on user tables before inserting the data then emits queries to
-      re-enable them after the data has been inserted.  If the restore is stopped in the
-      middle, the system catalogs may be left in the wrong state.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      <command>pg_restore</command> will not restore large objects for a single table. If
-      an archive contains large objects, then all large objects will be restored.
-     </para>
-    </listitem>
-
-   </itemizedlist>
-  </para>
-
-  <para>
-   See the <xref linkend="app-pgdump"> documentation for details on
-   limitations of <command>pg_dump</command>.
-  </para>
- </refsect1>
-
-
- <refsect1 id="app-pgrestore-examples">
-  <title>
-   Examples
-  </title>
-
-  <para>
-   To dump a database:
-<screen>
-<prompt>$</prompt> <userinput>pg_dump mydb &gt; db.out</userinput>
-</screen>
-  </para>
-
-  <para>
-   To reload this database:
-<screen>
-<prompt>$</prompt> <userinput>psql -d database -f db.out</userinput>
-</screen>
-  </para>
-
-  <para>
-   To dump a database called <literal>mydb</> that contains
-   large objects to a <filename>tar</filename> file:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_dump -Ft -b mydb &gt; db.tar</userinput>
-</screen>
-  </para>
-
-  <para>
-   To reload this database (with large objects) to an
-   existing database called <literal>newdb</>:
-
-<screen>
-<prompt>$</prompt> <userinput>pg_restore -d newdb db.tar</userinput>
-</screen>
-  </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 archive.file &gt; archive.list</userinput>
-</screen>
-   The listing file consists of a header and one line for each item, e.g.,
-<programlisting>
-;
-; Archive created at Fri Jul 28 22:28:36 2000
-;     dbname: birds
-;     TOC Entries: 74
-;     Compression: 0
-;     Dump Version: 1.4-0
-;     Format: CUSTOM
-;
-;
-; Selected TOC Entries:
-;
-2; 145344 TABLE species postgres
-3; 145344 ACL species
-4; 145359 TABLE nt_header postgres
-5; 145359 ACL nt_header
-6; 145402 TABLE species_records postgres
-7; 145402 ACL species_records
-8; 145416 TABLE ss_old postgres
-9; 145416 ACL ss_old
-10; 145433 TABLE map_resolutions postgres
-11; 145433 ACL map_resolutions
-12; 145443 TABLE hs_old postgres
-13; 145443 ACL hs_old
-</programlisting>
-   Semi-colons are comment delimiters, 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 <command>pg_restore</command> and would only restore
-   items 10 and 6, in that order.
-<screen>
-<prompt>$</prompt> <userinput>pg_restore -L archive.list archive.file</userinput>
-</screen>
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>History</title>
-
-  <para>
-   The <command>pg_restore</command> utility first appeared in
-   PostgreSQL 7.1.
-  </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>
-   <member><citetitle>PostgreSQL Administrator's Guide</citetitle></member>
-  </simplelist>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/pgaccess-ref.sgml b/doc/src/sgml/ref/pgaccess-ref.sgml
deleted file mode 100644
index ff69bbf86d8..00000000000
--- a/doc/src/sgml/ref/pgaccess-ref.sgml
+++ /dev/null
@@ -1,405 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgaccess-ref.sgml,v 1.14 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-PGACCESS">
- <refmeta>
-  <refentrytitle id="app-pgaccess-title"><application>pgaccess</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pgaccess</refname>
-  <refpurpose>a graphical <productname>PostgreSQL</productname> client application</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pgaccess</command>
-   <arg><replaceable>dbname</replaceable></arg>
-  </cmdsynopsis>
-
-  <refsect2 id="app-pgaccess-options">
-   <title>Options</title>
-
-   <variablelist>
-    <varlistentry>
-     <term><replaceable>dbname</replaceable></term>
-     <listitem>
-      <para>
-	The name of an existing database to access.
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </refsect2>
-
- </refsynopsisdiv>
-
- <refsect1 id="R1-APP-PGACCESS-1">
-  <title>
-   Description
-  </title>
-  <para>
-   <application>PgAccess</application> provides a graphical interface
-   for <productname>PostgreSQL</productname>
-   wherein you
-   can manage your tables, edit them, define queries, sequences and
-   functions.
-  </para>
-
-  <para>
-   <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Open any database on a specified host at the specified port,
-      user name, and password.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Execute <xref linkend="sql-vacuum" endterm="sql-vacuum-title">.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Save preferences in the <filename>~/.pgaccessrc</filename> file.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For tables, <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Open multiple tables for viewing, with a configurable number of rows shown.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Resize columns by dragging the vertical grid lines.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Wrap text in cells.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Dynamically adjust row height when editing.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Save table layout for every table.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Import/export to external files (<acronym>SDF</acronym>, <acronym>CSV</acronym>).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use filter capabilities; enter filters like <literal>price &gt; 3.14</literal>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Specify sort order; enter manually the sort field(s).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Edit in place; double click the text you want to change.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Delete records; point to the record, press the <keycap>Delete</keycap> key.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Add new records; save new row with right-button click.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Create tables with an assistant.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Rename and delete (drop) tables.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Retrieve information on tables, including owner, field information, indexes.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For queries, <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Define, edit and store user-defined queries.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Save view layouts.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Store queries as views.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Execute with optional user input parameters, e.g.,
-<programlisting>
-select * from invoices where year=[parameter "Year of selection"]
-</programlisting>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      View any select query result.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Run action queries (insert, update, delete).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Construct queries using a visual query builder
-      with drag &amp; drop support, table aliasing.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For sequences, <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Define new instances.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Inspect existing instances.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Delete.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For views, <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Define them by saving queries as views.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      View them, with filtering and sorting capabilities.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Design new views.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Delete (drop) existing views.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For functions, <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Define.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Inspect.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Delete.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For reports, <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Generate simple reports from a table (beta stage).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Change font, size, and style of fields and labels.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Load and save reports from the database.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Preview tables, sample <productname>Postscript</productname> print.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For forms, <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Open user-defined forms.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Use a form design module.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Access record sets using a query widget.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   For scripts, <application>PgAccess</application> can:
-
-   <itemizedlist mark="bullet" spacing="compact">
-    <listitem>
-     <para>
-      Define.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Modify.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Call user defined scripts.
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   <application>PgAccess</application> is written in Tcl/Tk.  Your
-   <productname>PostgreSQL</productname> installation needs to be
-   built with Tcl support for <application>PgAccess</application> to
-   be available.
-  </para>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/pgtclsh.sgml b/doc/src/sgml/ref/pgtclsh.sgml
deleted file mode 100644
index 4b8546fbc10..00000000000
--- a/doc/src/sgml/ref/pgtclsh.sgml
+++ /dev/null
@@ -1,83 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtclsh.sgml,v 1.5 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-PGTCLSH">
- <refmeta>
-  <refentrytitle>pgtclsh</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pgtclsh</refname>
-  <refpurpose>
-   <productname>PostgreSQL</productname> <application>Tcl</application> shell client
-  </refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pgtclsh</command>
-   <arg><replaceable>filename</replaceable> <arg rep="repeat"><replaceable>arguments</replaceable></arg></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="app-pgtclsh-description">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>pgtclsh</command> is a <application>Tcl</application>
-   shell interface extended with
-   <productname>PostgreSQL</productname> database access functions.
-   (Essentially, it is <command>tclsh</command> with
-   <filename>libpgtcl</filename> loaded.)  Like with the regular
-   <application>Tcl</application> shell, the first command line
-   argument is a script file, any remaining arguments are passed to
-   the script.  If no script file is named, the shell is
-   interactive.
-  </para>
-
-  <para>
-   A <application>Tcl</application> shell with
-   <application>Tk</application> and
-   <productname>PostgreSQL</productname> functions is available as <xref
-   linkend="app-pgtksh">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-pgtksh"></member>
-   <member>
-    <citetitle>PostgreSQL Programmer's Guide</citetitle> (description of <filename>libpgtcl</filename>)
-   </member>
-   <member>
-    <citerefentry><refentrytitle>tclsh</refentrytitle> <manvolnum>1</manvolnum></citerefentry>
-   </member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/pgtksh.sgml b/doc/src/sgml/ref/pgtksh.sgml
deleted file mode 100644
index af8f483cb43..00000000000
--- a/doc/src/sgml/ref/pgtksh.sgml
+++ /dev/null
@@ -1,86 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/Attic/pgtksh.sgml,v 1.5 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-PGTKSH">
- <refmeta>
-  <refentrytitle>pgtksh</refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>pgtksh</refname>
-  <refpurpose>
-   <productname>PostgreSQL</productname> <application>Tcl/Tk</application> shell client
-  </refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>pgtksh</command>
-   <arg><replaceable>filename</replaceable> <arg rep="repeat"><replaceable>arguments</replaceable></arg></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1 id="app-pgtksh-description">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>pgtksh</command> is a <application>Tcl/Tk</application>
-   shell interface extended with <productname>PostgreSQL</productname>
-   database access functions.  (Essentially, it is
-   <command>wish</command> with <filename>libpgtcl</filename> loaded.)
-   Like with <command>wish</command>, the regular
-   <application>Tcl/Tk</application> shell, the first command line
-   argument is a script file, any remaining arguments are passed to
-   the script.  Special options may be processed by the
-   <application>X Window System</application> libraries instead.
-   If no script file is named, the shell is interactive.
-  </para>
-
-  <para>
-   A plain <application>Tcl</application> shell with
-   <productname>PostgreSQL</productname> functions is available as <xref
-   linkend="app-pgtclsh">.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simplelist type="inline">
-   <member><xref linkend="app-pgtclsh"></member>
-   <member>
-    <citetitle>PostgreSQL Programmer's Guide</citetitle> (description of <filename>libpgtcl</filename>)
-   </member>
-   <member>
-    <citerefentry><refentrytitle>tclsh</refentrytitle> <manvolnum>1</manvolnum></citerefentry>
-   </member>
-   <member>
-    <citerefentry><refentrytitle>wish</refentrytitle> <manvolnum>1</manvolnum></citerefentry>
-   </member>
-  </simplelist>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml
deleted file mode 100644
index f78c0533201..00000000000
--- a/doc/src/sgml/ref/postgres-ref.sgml
+++ /dev/null
@@ -1,422 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.26 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-POSTGRES">
- <refmeta>
-  <refentrytitle id="APP-POSTGRES-TITLE"><application>postgres</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>postgres</refname>
-  <refpurpose>run a <productname>PostgreSQL</productname> server in single-user mode</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <!-- standalone call -->
-   <command>postgres</command>
-   <arg>-A <group choice="plain"><arg>0</arg><arg>1</arg></group></arg>
-   <arg>-B <replaceable>nbuffers</replaceable></arg>
-   <arg>-c <replaceable>name</replaceable>=<replaceable>value</replaceable></arg>
-   <arg>-d <replaceable>debug-level</replaceable></arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-e</arg>
-   <arg>-E</arg>
-   <arg>-f<group choice="plain"><arg>s</arg><arg>i</arg><arg>t</arg><arg>n</arg><arg>m</arg><arg>h</arg></group></arg>
-   <arg>-F</arg>
-   <arg>-i</arg>
-   <arg>-N</arg>
-   <arg>-o <replaceable>filename</replaceable></arg>
-   <arg>-O</arg>
-   <arg>-P</arg>
-   <group>
-    <arg>-s</arg>
-    <arg>-t<group choice="plain"><arg>pa</arg><arg>pl</arg><arg>ex</arg></group></arg>
-   </group>
-   <arg>-S <replaceable>sort-mem</replaceable></arg>
-   <arg>-W <replaceable>seconds</replaceable></arg>
-   <arg>--<replaceable>name</replaceable>=<replaceable>value</replaceable></arg>
-   <arg choice="plain"><replaceable>database</replaceable></arg>
-   <sbr>
-   <!-- postmaster fork -->
-   <command>postgres</command>
-   <arg>-A <group choice="plain"><arg>0</arg><arg>1</arg></group></arg>
-   <arg>-B <replaceable>nbuffers</replaceable></arg>
-   <arg>-c <replaceable>name</replaceable>=<replaceable>value</replaceable></arg>
-   <arg>-d <replaceable>debug-level</replaceable></arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-e</arg>
-   <arg>-f<group choice="plain"><arg>s</arg><arg>i</arg><arg>t</arg><arg>n</arg><arg>m</arg><arg>h</arg></group></arg>
-   <arg>-F</arg>
-   <arg>-i</arg>
-   <arg>-o <replaceable>filename</replaceable></arg>
-   <arg>-O</arg>
-   <arg>-p <replaceable>database</replaceable></arg>
-   <arg>-P</arg>
-   <group>
-    <arg>-s</arg>
-    <arg>-t<group choice="plain"><arg>pa</arg><arg>pl</arg><arg>ex</arg></group></arg>
-   </group>
-   <arg>-S <replaceable>sort-mem</replaceable></arg>
-   <arg>-v <replaceable>protocol-version</replaceable></arg>
-   <arg>-W <replaceable>seconds</replaceable></arg>
-   <arg>--<replaceable>name</replaceable>=<replaceable>value</replaceable></arg>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   The <filename>postgres</filename> executable is the actual
-   <productname>PostgreSQL</productname> server process that processes
-   queries.  It is normally not called directly; instead a <xref
-   linkend="app-postmaster"> multiuser server is started.
-  </para>
-
-  <para>
-   The second form above is how
-   <application>postgres</application> is invoked by the <xref
-   linkend="app-postmaster"> (only
-   conceptually, since both <filename>postmaster</filename> and
-   <filename>postgres</filename> are in fact the same program); it
-   should not be invoked directly this way.  The first form invokes
-   the server directly in interactive 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.
-  </para>
-
-  <para>
-   When invoked in interactive 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.  But note
-   that running a single-user backend is not truly suitable for
-   debugging the server since no realistic interprocess communication
-   and locking will happen.
-  </para>
-
-  <para>
-   When running a stand-alone backend, the session user will be set to
-   the user with id 1.  This user does not actually have to exist, so
-   a stand-alone backend can be used to manually recover from certain
-   kinds of accidental damage to the system catalogs.  Implicit
-   superuser powers are granted to the user with id 1 in stand-alone
-   mode.
-  </para>
-
-  <refsect2>
-   <title>Options</title>
-
-   <para>
-    When <application>postgres</application> is started by a <xref
-    linkend="app-postmaster"> then it
-    inherits all options set by the latter.  Additionally,
-    <application>postgres</application>-specific options can be passed
-    from the <application>postmaster</application> with the
-    <option>-o</option> switch.
-   </para>
-
-   <para>
-    You can avoid having to type these options by setting up a
-    configuration file.  See the <citetitle>Administrator's
-    Guide</citetitle> for details.  Some (safe) options can also be
-    set from the connecting client in an application-dependent way.
-    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
-    <application>postgres</application> command-line options.
-   </para>
-
-   <refsect3>
-    <title>General Purpose</title>
-
-    <para>
-     The options <option>-A</option>, <option>-B</option>,
-     <option>-c</option>, <option>-d</option>, <option>-D</option>,
-     <option>-F</option>, and <option>--name</> have the same meanings
-     as the <xref linkend="app-postmaster"> except that
-     <option>-d</option> <literal>0</> prevents the debugging level of
-     the postmaster from being propagated to the backend.
-    </para>
-
-    <variablelist>
-     <varlistentry>
-      <term><option>-e</option></term>
-      <listitem>
-       <para>
-        Sets the default date style to <quote>European</quote>, which
-	means that the <quote>day before month</quote> (rather than
-	month before day) rule is used to interpret ambiguous date
-	input, and that the day is printed before the month in certain
-	date output formats.  See the <citetitle>PostgreSQL User's
-	Guide</citetitle> for more information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-o</option> <replaceable class="parameter">filename</replaceable></term>
-      <listitem>
-       <para>
-	Sends all debugging and error output to 
-	<replaceable class="parameter">filename</replaceable>.
-	If the backend is running under the
-	<application>postmaster</application>, this option is ignored,
-	and the <systemitem>stderr</> inherited from the
-	<application>postmaster</application> is used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-P</option></term>
-      <listitem>
-       <para>
-	Ignore system indexes while scanning/updating system tuples. The
-	<command>REINDEX</command> command for system tables/indexes
-	requires this option to be used.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-s</option></term>
-      <listitem>
-       <para>
-	Print time information and other statistics at the end of each query.
-	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">sort-mem</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the amount of memory to be used by internal sorts and hashes
-	before resorting to temporary disk files.  The value is specified in
-	kilobytes, and defaults to 512 kilobytes.  Note that for a complex query,
-	several sorts and/or hashes might be running in parallel, and each one
-	will be allowed to use as much as
-	<replaceable class="parameter">sort-mem</replaceable> kilobytes
-	before it starts to put data into temporary files.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </refsect3>
-
-   <refsect3>
-    <title>Options for stand-alone mode</title>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="parameter">database</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the name of the database to be accessed.  If it is
-	omitted it defaults to the user name.	
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-E</option></term>
-      <listitem>
-       <para>
-	Echo all queries.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-N</option></term>
-      <listitem>
-       <para>
-	Disables use of newline as a query delimiter.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </refsect3>
-
-   <refsect3>
-    <title>Semi-internal Options</title>
-
-    <para>
-     There are several other options that may be specified, used
-     mainly for debugging purposes.  These are listed here only for
-     the use by <productname>PostgreSQL</productname> system
-     developers.  <emphasis>Use of any of these options is highly
-     discouraged.</emphasis>  Furthermore, any of these options may
-     disappear or change 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.
-	
-	<note>
-	 <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>
-	</note>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-i</option></term>
-      <listitem>
-       <para>
-	Prevents query execution, but shows the plan tree.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-O</option></term>
-      <listitem>
-       <para>
-	Allows the structure of system tables to be modified.  This is
-	used by <application>initdb</application>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-p</option> <replaceable class="parameter">database</replaceable></term>
-      <listitem>
-       <para>
-	Indicates that this server has been started by a
-	<application>postmaster</application> and makes different
-	assumptions about buffer pool management, file descriptors,
-	etc.
-       </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>-v</option> <replaceable class="parameter">protocol</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the version number of the frontend/backend protocol
-	to be used for this particular session.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>-W</option> <replaceable class="parameter">seconds</replaceable></term>
-      <listitem>
-       <para>
-	As soon as this option is encountered, the process sleeps for
-	the specified amount of seconds.  This gives developers time
-	to attach a debugger to the backend process.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </refsect3>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Usage</title>
-
-   <para>
-    Start a stand-alone backend with a command like
-<screen>
-<userinput>postgres -D $PGDATA <replaceable>other-options</> my_database</userinput>
-</screen>
-    Provide the correct path to the database area 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 stand-alone backend 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>-N</> command line switch, then newline does
-    not terminate command entry.  The backend will read the standard input
-    until the end-of-file (<acronym>EOF</>) marker, then
-    process the input as a single query 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>-N</>, two consecutive <acronym>EOF</>s are needed to exit.
-   </para>
-
-   <para>
-    Note that the stand-alone backend does not provide sophisticated
-    line-editing features (no command history, for example).
-   </para>
-
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <para>
-   <xref linkend="app-initdb">,
-   <xref linkend="app-ipcclean">,
-   <xref linkend="app-postmaster">
-  </para>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml
deleted file mode 100644
index 0d2a7e93dd2..00000000000
--- a/doc/src/sgml/ref/postmaster.sgml
+++ /dev/null
@@ -1,528 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/postmaster.sgml,v 1.30 2002/06/15 19:52:56 momjian Exp $
-PostgreSQL documentation
--->
-
-<refentry id="app-postmaster">
- <refmeta>
-  <refentrytitle id="APP-POSTMASTER-TITLE"><application>postmaster</application></refentrytitle>
-  <manvolnum>1</manvolnum>
-  <refmiscinfo>Application</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname id="postmaster-ref">postmaster</refname>
-  <refpurpose><productname>PostgreSQL</productname> multiuser database server</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>postmaster</command>
-   <arg>-A <group choice="plain"><arg>0</arg><arg>1</arg></group></arg>
-   <arg>-B <replaceable>nbuffers</replaceable></arg>
-   <arg>-c <replaceable>name</replaceable>=<replaceable>value</replaceable></arg>
-   <arg>-d <replaceable>debug-level</replaceable></arg>
-   <arg>-D <replaceable>datadir</replaceable></arg>
-   <arg>-F</arg>
-   <arg>-h <replaceable>hostname</replaceable></arg>
-   <arg>-i</arg>
-   <arg>-k <replaceable>directory</replaceable></arg>
-   <arg>-l</arg>
-   <arg>-N <replaceable>max-connections</replaceable></arg>
-   <arg>-o <replaceable>extra-options</replaceable></arg>
-   <arg>-p <replaceable>port</replaceable></arg>
-   <arg>-S</arg>
-   <arg>--<replaceable>name</replaceable>=<replaceable>value</replaceable></arg>
-   <group><arg>-n</arg><arg>-s</arg></group>
-  </cmdsynopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <application>postmaster</application> is the
-   <productname>PostgreSQL</productname> multiuser database server.
-   In order for a client application to access a database it connects
-   (over a network or locally) to a running
-   <application>postmaster</application>.  The
-   <application>postmaster</application> then starts a separate server
-   process (<quote><xref linkend="app-postgres"></quote>) to handle
-   the connection.  The <application>postmaster</application> also
-   manages the communication among server processes.
-  </para>
-
-  <para>
-   By default the <application>postmaster</application> starts in the
-   foreground and prints log messages to the standard output.  In
-   practical applications the <application>postmaster</application>
-   should be started as a background process, perhaps at boot time.
-  </para>
-
-  <para>
-   One <application>postmaster</application> always manages the data
-   from exactly one database cluster.  A database cluster is a
-   collection of databases that is stored at a common file system
-   location.  When the postmaster starts it needs to know the location
-   of the database cluster files (<quote>data area</quote>).  This is
-   done with the <option>-D</option> invocation option or the
-   <envar>PGDATA</envar> environment variable; there is no default.
-   More than one postmaster process can run on a system at one time,
-   as long as they use different data areas and different
-   communication ports (see below).  A data area is created with <xref
-   linkend="app-initdb">.
-  </para>
-
-  <refsect2 id="app-postmaster-options">
-   <title>Options</title>
-   <para>
-    <application>postmaster</application> accepts the following
-    command line arguments.  For a detailed discussion of the options
-    consult the <citetitle>Administrator's Guide</citetitle>.  You can
-    also save typing most of these options by setting up a
-    configuration file.
-    
-    <variablelist>
-     <varlistentry>
-      <term>-A 0|1</term>
-      <listitem>
-       <para>
-        Enables run-time assert checks, which is a debugging aid to
-        detect programming mistakes.  This is only available if it was
-        enabled during compilation.  If so, the default is on.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-B <replaceable class="parameter">nbuffers</replaceable></term>
-      <listitem>
-       <para>
-	Sets the number of shared buffers for use by the server
-	processes.  This value defaults to 64 buffers, where each
-	buffer is 8 kB.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-c <replaceable>name</replaceable>=<replaceable>value</replaceable></term>
-      <listitem>
-       <para>
-        Sets a named run-time parameter. Consult the
-        <citetitle>Administrator's Guide</citetitle> for a list and
-        descriptions.  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>-d <replaceable>debug-level</replaceable></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.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-D <replaceable class="parameter">datadir</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the file system location of the data directory.  See
-	discussion above.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-F</term>
-      <listitem>
-       <para>
-        Disables <function>fsync</function> calls for performance
-        improvement, at the risk of data corruption in event of a
-        system crash.  This parameter corresponds to setting
-        fsync=false in postgresql.conf. Read the detailed
-        documentation before using this!
-       </para>
-       <para>
-        <option>--fsync=true</option> has the opposite effect
-        of this option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-h <replaceable class="parameter">hostname</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the TCP/IP host name or address on which the
-	<application>postmaster</application> is to listen for
-	connections from client applications.  Defaults to
-	listening on all configured addresses (including
-        <systemitem class="systemname">localhost</systemitem>).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-i</term>
-      <listitem>
-       <para>
-        Allows clients to connect via TCP/IP (Internet domain)
-	connections.  Without this option, only local Unix domain
-        socket connections are accepted. This option corresponds
-        to setting tcpip_socket=true in postgresql.conf.
-       </para>
-       <para>
-        <option>--tcpip_socket=false</option> has the opposite
-        effect of this option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-k <replaceable class="parameter">directory</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the directory of the Unix-domain socket on which the
-	<application>postmaster</application> 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>-l</term>
-      <listitem>
-       <para>
-	Enables secure connections using SSL.  The <option>-i</option>
-	option is also required.  You must have compiled with SSL
-	enabled to use this option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-N <replaceable class="parameter">max-connections</replaceable></term>
-      <listitem>
-       <para>
-	Sets the maximum number of client connections that this
-	<application>postmaster</application> will accept.  By
-	default, this value is 32, but it can be set as high as your
-	system will support.  (Note that
-	<option>-B</option> is required to be at least twice
-	<option>-N</option>.  See the <citetitle>Administrator's
-	Guide</citetitle> for a discussion of system resource requirements
-	for large numbers of client connections.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-o <replaceable class="parameter">extra-options</replaceable></term>
-      <listitem>
-       <para>
-	The command line-style options specified in <replaceable
-	class="parameter">extra-options</replaceable> are passed to
-	all backend server processes started by this
-	<application>postmaster</application>.  See <xref
-	linkend="app-postgres"> for possibilities.  If the option
-	string contains any spaces, the entire string must be quoted.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-p <replaceable class="parameter">port</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the TCP/IP port or local Unix domain socket file
-	extension on which the <application>postmaster</application>
-	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>-S</term>
-      <listitem>
-       <para>
-	Specifies that the <application>postmaster</application>
-	process should start up in silent mode.  That is, it will
-	disassociate from the user's (controlling) terminal, start its
-	own process group, and redirect its standard output and
-	standard error to <filename>/dev/null</filename>.
-       </para>
-       <para>
-        Using this switch discards all logging output, which is
-	probably not what you want, since it makes it very difficult
-	to troubleshoot problems.  See below for a better way to start
-	the <application>postmaster</application> in the background.
-       </para>
-       <para>
-        <option>--silent_mode=false</option> has the opposite effect
-        of this option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>--<replaceable>name</replaceable>=<replaceable>value</replaceable></term>
-      <listitem>
-       <para>
-        Sets a named run-time parameter; a shorter form of
-        <option>-c</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    Two additional command line options are available for debugging
-    problems that cause a backend to die abnormally.  These options
-    control the behavior of the <application>postmaster</application>
-    in this situation, and <emphasis>neither option is intended for
-    use in ordinary operation</emphasis>.
-   </para>
-
-   <para>
-    The ordinary strategy for this situation is to notify all other
-    backends that they must terminate and then reinitialize the shared
-    memory and semaphores.  This is because an errant backend could
-    have corrupted some shared state before terminating.
-   </para>
-
-   <para>
-    These special-case options are:
-
-    <variablelist>
-     <varlistentry>
-      <term>-n</term>
-      <listitem>
-       <para>
-	<application>postmaster</application>
-	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>-s</term>
-      <listitem>
-       <para>
-	<application>postmaster</application>
-	will stop all other backend 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 backend processes by hand.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-POSTMASTER-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-semget: No space left on device
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If you see this message, you should run the
-	<application>ipcclean</application>
-	command.  After doing so, try starting
-	<application>postmaster</application>
-	again.  If this still doesn't work, you probably need to configure
-	your kernel for shared memory and semaphores as described in the
-	installation notes.  If you run multiple instances of
-	<application>postmaster</application>
-	on a single host, or have a kernel with particularly small shared memory
-	and/or semaphore limits, you may have to reconfigure your kernel to increase
-	its shared memory or semaphore parameters.
-
-	<tip>
-	 <para>
-	  You may be able to postpone
-	  reconfiguring your kernel by decreasing <option>-B</option> to reduce
-	  the shared memory consumption of <productname>PostgreSQL</>,
-	  and/or by reducing <option>-N</option> to reduce the semaphore
-	  consumption.
-	 </para>
-	</tip>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-StreamServerPort: cannot bind to port
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If you see this message, you should make certain that there is no
-	other <application>postmaster</application>
-	process already running on the same port number.  The easiest way to
-	determine this is by using the command
-<screen>
-<prompt>$</prompt> <userinput>ps ax | grep postmaster</userinput>
-</screen>
-        or
-<screen>
-<prompt>$</prompt> <userinput>ps -e | grep postmaster</userinput>
-</screen>
-	depending on your system.
-       </para>
-
-       <para>
-	If you 
-	are sure that no other
-	<application>postmaster</application>
-	processes are running and you still get this error, try specifying a
-	different port using the
-	<literal>-p</literal>
-	option.  You may also get this error if you terminate the
-	<application>postmaster</application>
-	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 may 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 <firstterm>trusted</firstterm>
-	and only permit the Unix superuser to access them.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-  
-  <para>
-   If at all possible, <emphasis>do not</emphasis> use
-   <literal>SIGKILL</literal> to kill the
-   <application>postmaster</application>.  This will prevent
-   <application>postmaster</application> from freeing the system
-   resources (e.g., shared memory and semaphores) that it holds before
-   terminating.
-  </para>
-
-  <para>
-   To terminate the <application>postmaster</application> 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 utility command <xref linkend="app-pg-ctl"> can be used to
-   start and shut down the <application>postmaster</application>
-   safely and comfortably.
-  </para>
-
-  <para>
-   The <option>--</> options will not work on FreeBSD or 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>
-
- <refsect1 id="app-postmaster-usage">
-  <title>Usage</title>
-  <para>
-   To start <application>postmaster</application> in the background
-   using default values, type:
-
-<screen>
-<prompt>$</prompt> <userinput>nohup postmaster &gt;logfile 2&gt;&amp;1 &lt;/dev/null &amp;</userinput>
-</screen>
-  </para>
-
-  <para>
-   To start <application>postmaster</application> with a specific
-   port:
-<screen>
-<prompt>$</prompt> <userinput>postmaster -p 1234</userinput>
-</screen>
-   This command will start up <application>postmaster</application>
-   communicating through the port 1234. In order to connect to this
-   <application>postmaster</application> using psql, you would need to
-   run it as
-<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:
-<screen>
-<prompt>$</prompt> <userinput>postmaster -c sort_mem=1234</userinput>
-<prompt>$</prompt> <userinput>postmaster --sort-mem=1234</userinput>
-</screen>
-   Either form overrides whatever setting might exist for <literal>sort_mem</>
-   in <filename>postgresql.conf</>.  Notice that underscores in parameter
-   names can be written as either underscore or dash on the command line.
-  </para>
-
-  <tip>
-  <para>
-   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>
-  </tip>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml
deleted file mode 100644
index 85bc6852be4..00000000000
--- a/doc/src/sgml/ref/psql-ref.sgml
+++ /dev/null
@@ -1,2553 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.67 2002/06/20 16:00:43 momjian Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-PSQL">
- <docinfo>
-  <date>2000-12-25</date>
- </docinfo>
-
-  <refmeta>
-    <refentrytitle id="app-psql-title"><application>psql</application></refentrytitle>
-    <manvolnum>1</manvolnum>
-    <refmiscinfo>Application</refmiscinfo>
-  </refmeta>
-
-  <refnamediv>
-    <refname><application>psql</application></refname>
-    <refpurpose>
-      <productname>PostgreSQL</productname> interactive terminal
-    </refpurpose>
-  </refnamediv>
-
-  <refsynopsisdiv>
-    <refsynopsisdivinfo>
-      <date>1999-10-26</date>
-    </refsynopsisdivinfo>
-
-    <synopsis>psql [ <replaceable class="parameter">options</replaceable> ] [ <replaceable class="parameter">dbname</replaceable> [ <replaceable class="parameter">user</replaceable> ] ]</synopsis>
-
-  <refsect2 id="R2-APP-PSQL-1">
-    <refsect2info>
-      <date>1998-09-26</date>
-    </refsect2info>
-
-    <title>Summary</title>
-
-    <para>
-     <application>psql</application> is a terminal-based front-end to
-     <productname>PostgreSQL</productname>. It enables you to type in
-     queries interactively, issue them to
-     <productname>PostgreSQL</productname>, and see the query results.
-     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>
-
-  </refsect2>
-
-</refsynopsisdiv>
-
-<refsect1 id="R1-APP-PSQL-1">
-  <refsect1info>
-    <date>1998-10-26</date>
-  </refsect1info>
-
-  <title>Description</title>
-
-  <refsect2 id="R2-APP-PSQL-connecting">
-    <refsect2info>
-      <date>2000-01-14</date>
-    </refsect2info>
-   
-    <title>Connecting To A Database</title>
-
-    <para>
-    <application>psql</application> is a regular
-    <productname>PostgreSQL</productname> client application. In order
-    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 also given). Not all
-    these options are required, defaults do apply. If you omit the host
-    name psql will connect via a Unix domain socket to a server on the
-    local host. The default port number is compile-time determined.
-    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 can't
-    just connect to any database under any user name. Your database
-    administrator should have informed you about your access rights. To
-    save you some typing you can also set the environment variables
-    <envar>PGDATABASE</envar>, <envar>PGHOST</envar>,
-    <envar>PGPORT</envar> and <envar>PGUSER</envar> to appropriate
-    values.
-    </para>
-
-    <para>
-    If the connection could not be made for any reason (e.g., insufficient
-    privileges, postmaster is not running on the server, etc.),
-    <application>psql</application> will return an error and terminate.
-    </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-PSQL-4">
-    <refsect2info>
-      <date>1998-09-26</date>
-    </refsect2info>
-
-    <title>Entering Queries</title>
-
-    <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>
-Welcome to psql, the PostgreSQL interactive terminal.
-
-Type:  \copyright for distribution terms
-       \h for help with SQL commands
-       \? for help on internal slash commands
-       \g or terminate with semicolon to execute query
-       \q to quit
-
-testdb=>
-</programlisting>
-    </para>
-
-    <para>
-    At the prompt, the user may type in <acronym>SQL</acronym> queries.
-    Ordinarily, input lines are sent to the backend when a
-    query-terminating semicolon is reached. An end of line does not
-    terminate a query! Thus queries can be spread over several lines for
-    clarity. If the query was sent and without error, the query results
-    are displayed on the screen.
-    </para>
-
-    <para>
-    Whenever a query is executed, <application>psql</application> also polls
-    for asynchronous notification events generated by
-    <xref linkend="SQL-LISTEN" endterm="SQL-LISTEN-title"> and
-    <xref linkend="SQL-NOTIFY" endterm="SQL-NOTIFY-title">.
-    </para>
-  </refsect2>
-</refsect1>
-
-<refsect1 id="R1-APP-PSQL-2">
-    <refsect1info>
-      <date>1998-09-26</date>
-    </refsect1info>
-
-    <title><application>psql</application> Meta-Commands</title>
-
-    <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 are what makes
-    <application>psql</application> interesting for administration or
-    scripting. Meta-commands are more commonly 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 must quote it with a
-    single quote. To include a single quote into such an argument,
-    precede it by a backslash. 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>,
-    <literal>\0</literal><replaceable>digits</replaceable>, and
-    <literal>\0x</literal><replaceable>digits</replaceable> (the
-    character with the given decimal, octal, or hexadecimal code).
-    </para>
-
-    <para>
-    If an unquoted argument begins with a colon (<literal>:</literal>),
-    it is taken as a variable and the value of the variable is taken as
-    the argument instead.
-    </para>
-
-    <para>
-    Arguments that are quoted in <quote>backticks</quote>
-    (<literal>`</literal>) are taken as a command line that is passed to
-    the shell. The output of the command (with a trailing newline
-    removed) is taken as the argument value. The above escape sequences
-    also apply in backticks.
-    </para>
-
-    <para>
-    Some commands take the name of an <acronym>SQL</acronym> identifier
-    (such as a table name) as argument. These arguments follow the
-    syntax rules of <acronym>SQL</acronym> regarding double quotes: an
-    identifier without double quotes is coerced to lower-case. For all
-    other commands double quotes are not special and will become part of
-    the argument.
-    </para>
-
-    <para>
-    Parsing for arguments stops when another unquoted backslash occurs.
-    This 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> queries, 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, switch to aligned.
-	If it is not unaligned, set it to unaligned. This command is
-	kept for backwards compatibility. See <command>\pset</command> for a
-	general solution.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><literal>\cd</literal> <optional><replaceable>directory</replaceable></optional></term>
-       <listitem>
-        <para>
-	 Change the current working directory to
-	 <replaceable>directory</replaceable>. Without argument, change
-	 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>\C</literal> [ <replaceable class="parameter">title</replaceable> ]</term>
-        <listitem>
-        <para>
-        Set 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>\connect</literal> (or <literal>\c</literal>) [ <replaceable class="parameter">dbname</replaceable> [ <replaceable class="parameter">username</replaceable> ] ]</term>
-        <listitem>
-        <para>
-	Establishes a connection to a new database and/or under a user
-	name. The previous connection is closed. If <replaceable
-	class="parameter">dbname</replaceable> is <literal>-</literal>
-	the current database name is assumed.
-	</para>
-
-	<para>
-	If <replaceable class="parameter">username</replaceable> is
-	omitted the current user name is assumed. </para>
-
-	<para>
-	As a special rule, <command>\connect</command> without any
-	arguments will connect to the default database as the default
-	user (as you would have gotten by starting
-	<application>psql</application> without any arguments).
-	</para>
-
-	<para>
-	If the connection attempt failed (wrong user name, access
-	denied, etc.), the previous connection will be kept if and only
-	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>\copy</literal> <replaceable class="parameter">table</replaceable>
-        { <literal>from</literal> | <literal>to</literal> }
-	<replaceable class="parameter">filename</replaceable> | stdin | stdout
-        [ <literal>with</literal> ] 
-            [ <literal>oids</literal> ] 
-            [ <literal>delimiter [as] </literal> '<replaceable class="parameter">character</replaceable>' ]
-            [ <literal>null [as] </literal> '<replaceable class="parameter">string</replaceable>' ]
-        </term>
-
-        <listitem>
-        <para>
-        Performs a frontend (client) copy. This is an operation that
-        runs an <acronym>SQL</acronym> <xref linkend="SQL-COPY"
-        endterm="SQL-COPY-title"> command, but instead of the backend's
-        reading or writing the specified file, and consequently
-        requiring backend access and special user privilege, as well as
-        being bound to the file system accessible by the backend,
-        <application>psql</application> reads or writes the file and
-        routes the data between the backend and the local file system.
-	</para>
-
-	<para>
-	The syntax of the command is similar to that of the
-	<acronym>SQL</acronym> <command>COPY</command> command (see its
-	description for the details). 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>
-
-        <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 IP or socket connection. For large
-	amounts of data the other technique may be preferable.
-        </para>
-        </tip>
-
-        <note>
-        <para>
-        Note the difference in interpretation of
-        <literal>stdin</literal> and <literal>stdout</literal> between
-        frontend and backend copies: in a frontend copy these always
-        refer to <application>psql</application>'s input and output
-        stream. On a backend copy <literal>stdin</literal> comes from
-        wherever the <command>COPY</command> itself came from (for
-        example, a script run with the <option>-f</option> option), and
-        <literal>stdout</literal> refers to the query output stream (see
-        <command>\o</command> meta-command below).
-        </para>
-        </note>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\copyright</literal></term>
-        <listitem>
-        <para>
-        Shows the copyright and distribution terms of
-        <application>PostgreSQL</application>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\d</literal> <replaceable class="parameter">relation</replaceable> </term>
-
-        <listitem>
-        <para>
-	Shows all columns of <replaceable
-	class="parameter">relation</replaceable> (which could be a
-	table, view, index, or sequence), their types, and any special
-	attributes such as <literal>NOT NULL</literal> or defaults, if
-	any. If the relation is, in fact, a table, any defined indices,
-	primary keys, unique constraints and check constraints are also
-	listed. If the relation is a view, the view definition is also
-	shown.
-	</para>
-
-	<para>
-	The command form <literal>\d+</literal> is identical, but any
-	comments associated with the table columns are shown as well.
-	</para>
-
-	<note>
-	<para>
-	If <command>\d</command> is called without any arguments, it is
-	equivalent to <command>\dtvs</command> which will show a list of
-	all tables, views, and sequences. This is purely a convenience
-	measure.
-	</para>
-	</note>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\da</literal> [ <replaceable class="parameter">pattern</replaceable> ]</term>
-
-        <listitem>
-        <para>
-        Lists all available aggregate functions, together with the data
-        type they operate on. If <replaceable
-        class="parameter">pattern</replaceable> (a regular expression)
-        is specified, only matching aggregates are shown.
-        </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\dd</literal> [ <replaceable class="parameter">object</replaceable> ]</term>
-        <listitem>
-        <para>
-        Shows the descriptions of <replaceable
-        class="parameter">object</replaceable> (which can be a regular
-        expression), or of all objects if no argument is given.
-        (<quote>Object</quote> covers aggregates, functions, operators,
-        types, relations (tables, views, indexes, sequences, large
-        objects), rules, and triggers.) For example:
-<programlisting>
-=> <userinput>\dd version</userinput>
-              Object descriptions
-  Name   |   What   |        Description
----------+----------+---------------------------
- version | function | PostgreSQL version string
-(1 row)
-</programlisting>
-        </para>
-
-        <para>
-        Descriptions for objects can be generated with the
-        <command>COMMENT ON</command> <acronym>SQL</acronym> command.
-	</para>
-
-        <note>
-        <para>
-        <productname>PostgreSQL</productname> stores the object
-        descriptions in the pg_description system table.
-        </para>
-        </note>
-
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dD</literal> [ <replaceable class="parameter">pattern</replaceable> ]</term>
-        <listitem>
-        <para>
-        Lists all available domains (derived types). If <replaceable
-        class="parameter">pattern</replaceable> (a regular expression)
-        is specified, only matching domains are shown.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\df [ <replaceable class="parameter">pattern</replaceable> ]</literal></term>
-
-        <listitem>
-        <para>
-        Lists available functions, together with their argument and
-        return types. If <replaceable
-        class="parameter">pattern</replaceable> (a regular expression)
-        is specified, only matching functions are shown. If the form
-        <literal>\df+</literal> is used, additional information about
-        each function, including language and description, is shown.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\distvS [ <replaceable class="parameter">pattern</replaceable> ]</literal></term>
-
-	<listitem>
-	<para>
-	This is not the actual command name: The letters i, s, t, v, S
-	stand for index, sequence, table, view, and system table,
-	respectively. You can specify any or all of them in any order to
-	obtain a listing of them, together with who the owner is.
-	</para>
-
-	<para>
-	If <replaceable class="parameter">pattern</replaceable> is
-	specified, it is a regular expression that restricts the listing
-	to those objects whose name matches. If one appends a
-	<quote>+</quote> to the command name, each object is listed with
-	its associated description, if any.
-	</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>\do [ <replaceable class="parameter">name</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-        Lists available operators with their operand and return types.
-        If <replaceable class="parameter">name</replaceable> is
-        specified, only operators with that name will be shown.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dp</literal> [ <replaceable class="parameter">pattern</replaceable> ]</term>
-	<listitem>
-	<para>
-	This is an alias for <command>\z</command> which was included
-	for its greater mnemonic value (<quote>display
-	permissions</quote>).
-	</para>
-	</listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\dT [ <replaceable class="parameter">pattern</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-        Lists all data types or only those that match <replaceable
-        class="parameter">pattern</replaceable>. The command form
-        <literal>\dT+</literal> shows extra information.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\du [ <replaceable class="parameter">pattern</replaceable> ]</literal></term>
-        <listitem>
-        <para>
-        Lists all configured users or only those that match <replaceable
-        class="parameter">pattern</replaceable>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\edit</literal> (or <literal>\e</literal>) [ <replaceable class="parameter">filename</replaceable> ]</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 argument 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 also that
-        if the query ends with (or rather contains) a semicolon, it is
-        immediately executed. In other cases it will merely wait in the
-        query buffer.
-        </para>
-
-        <tip>
-        <para>
-        <application>psql</application> searches 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>/bin/vi</filename> is run.
-        </para>
-        </tip>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\echo</literal> <replaceable class="parameter">text</replaceable> [ ... ]</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>
-=> <userinput>\echo `date`</userinput>
-Tue Oct 26 21:40:57 CEST 1999
-</programlisting>
-        If the first argument is an unquoted <literal>-n</literal> the the trailing
-        newline is not written.
-	</para>
-
-	<tip>
-	<para>
-	If you use the <command>\o</command> command to redirect your
-	query output you may wish to use <command>\qecho</command>
-	instead of this command.
-	</para>
-	</tip>
-	</listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\encoding</literal> [ <replaceable class="parameter">encoding</replaceable> ]</term>
-
-        <listitem>
-        <para>
-        Sets the client encoding, if you are using multibyte encodings.
-        Without an argument, this command shows the current encoding.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\f</literal> [ <replaceable class="parameter">string</replaceable> ]</term>
-
-        <listitem>
-        <para>
-        Sets the field separator for unaligned query output. The default
-        is pipe (<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 backend and
-        optionally saves the output in <replaceable
-        class="parameter">filename</replaceable> or pipes the output
-        into a separate Unix shell to execute <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>\help</literal> (or <literal>\h</literal>) [ <replaceable class="parameter">command</replaceable> ]</term>
-        <listitem>
-        <para>
-        Give 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 (<quote>*</quote>), 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</literal> <replaceable class="parameter">filename</replaceable></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 <envar>ECHO</envar> to
-	<literal>all</literal>.
-	</para>
-	</note>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\l</literal> (or <literal>\list</literal>)</term>
-        <listitem>
-        <para>
-        List all the databases in the server as well as their owners.
-        Append a <quote>+</quote> to the command name to see any
-        descriptions for the databases as well. If your
-        <productname>PostgreSQL</productname> installation was compiled
-        with multibyte encoding support, the encoding scheme of each
-        database is shown as well.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\lo_export</literal> <replaceable class="parameter">loid</replaceable> <replaceable class="parameter">filename</replaceable></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>
-	<note>
-	<para>
-	See the description of the <envar>LO_TRANSACTION</envar>
-	variable for important information concerning all large object
-	operations.
-	</para>
-	</note>
-	</listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\lo_import</literal> <replaceable class="parameter">filename</replaceable> [ <replaceable class="parameter">comment</replaceable> ]</term>
-
-	<listitem>
-	<para>
-	Stores the file into a <productname>PostgreSQL</productname>
-	<quote>large object</quote>. Optionally, it associates the given
-	comment with the object. Example:
-<programlisting>
-foo=> <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 one ought to remember if one wants to access the
-	object ever again. For that reason it is recommended to always
-	associate a human-readable comment with every object. Those can
-	then be seen 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>
-
-	<note>
-	<para>
-	See the description of the <envar>LO_TRANSACTION</envar>
-	variable for important information concerning all large object
-	operations.
-	</para>
-	</note>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\lo_list</literal></term>
-	<listitem>
-	<para>
-	Shows a list of all <productname>PostgreSQL</productname>
-	<quote>large objects</quote> currently stored in the database,
-	along with any comments provided for them.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>\lo_unlink</literal> <replaceable class="parameter">loid</replaceable></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>
-	<note>
-	<para>
-	See the description of the <envar>LO_TRANSACTION</envar>
-	variable for important information concerning all large object
-	operations.
-	</para>
-	</note>
-	</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
-        <filename>stdout</filename>.
-        </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>\pset</literal> <replaceable class="parameter">parameter</replaceable> [ <replaceable class="parameter">value</replaceable> ]</term>
-
-	<listitem>
-	<para>
-	This command sets options affecting the output of query result
-	tables. <replaceable class="parameter">parameter</replaceable>
-	describes which option is to be set. The semantics of
-	<replaceable class="parameter">value</replaceable> depend
-	thereon.
-	</para>
-
-	<para>
-	Adjustable printing options are:
-	<variablelist>
-	  <varlistentry>
-	  <term><literal>format</literal></term>
-	  <listitem>
-	  <para>
-	  Sets the output format to one of <literal>unaligned</literal>,
-	  <literal>aligned</literal>, <literal>html</literal>, or
-	  <literal>latex</literal>. Unique abbreviations are allowed.
-	  (That would mean one letter is enough.)
-	  </para>
-
-	  <para>
-	  <quote>Unaligned</quote> writes all fields of a tuple on a
-	  line, separated by the currently active field separator. This
-	  is intended to create output that might be intended to be read
-	  in by other programs (tab-separated, comma-separated).
-	  <quote>Aligned</quote> mode is the standard, human-readable,
-	  nicely formatted text output that is default. The
-	  <quote><acronym>HTML</acronym></quote> and
-	  <quote>LaTeX</quote> modes 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>border</literal></term>
-	  <listitem>
-	  <para>
-	  The second argument 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> mode, this will translate directly
-	  into the <literal>border=...</literal> attribute, in the
-	  others only values 0 (no border), 1 (internal dividing lines),
-	  and 2 (table frame) make sense.
-	  </para>
-	  </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-	  <term><literal>expanded</literal> (or <literal>x</literal>)</term>
-	  <listitem>
-	  <para>
-	  Toggles between regular and expanded format. When expanded
-	  format is enabled, all output has two columns with the field
-	  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>
-
-	  <para>
-	  Expanded mode is supported by all four output modes.
-	  </para>
-	  </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-	  <term><literal>null</literal></term>
-	  <listitem>
-	  <para>
-	  The second argument is a string that should be printed
-	  whenever a field is null. The default is not to print
-	  anything, which can easily be mistaken for, say, an empty
-	  string. Thus, one might choose to write <literal>\pset null
-	  '(null)'</literal>.
-	  </para>
-	  </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-	  <term><literal>fieldsep</literal></term>
-	  <listitem>
-	  <para>
-	  Specifies the field separator to be used in unaligned output
-	  mode. 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 <quote>pipe</quote> symbol).
-	  </para>
-	  </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-	  <term><literal>footer</literal></term>
-	  <listitem>
-	  <para>
-	  Toggles the display of the default footer <literal>(x
-	  rows)</literal>.
-	  </para>
-	  </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-	  <term><literal>recordsep</literal></term>
-	  <listitem>
-	  <para>
-          Specifies the record (line) separator to use in unaligned
-          output mode. The default is a newline character.
-	  </para>
-	  </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-	  <term><literal>tuples_only</literal> (or <literal>t</literal>)</term>
-	  <listitem>
-	  <para>
-	  Toggles between tuples only and full display. Full display may
-	  show extra information such as column headers, titles, and
-	  various footers. In tuples only mode, only actual table data
-	  is shown.
-	  </para>
-	  </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-	  <term><literal>title</literal> [ <replaceable class="parameter">text</replaceable> ]</term>
-	  <listitem>
-	  <para>
-	  Sets the table title for any subsequently printed tables. This
-	  can be used to give your output descriptive tags. If no
-	  argument is given, the title is unset.
-	  </para>
-
-	  <note>
-	  <para>
-	  This formerly only affected <acronym>HTML</acronym> mode. You
-	  can now set titles in any output format.
-	  </para>
-	  </note>
-	  </listitem>
-	  </varlistentry>
-
-	  <varlistentry>
-	  <term><literal>tableattr</literal> (or <literal>T</literal>) [ <replaceable class="parameter">text</replaceable> ]</term>
-	  <listitem>
-	  <para>
-	  Allows you to specify any attributes to be placed inside the
-	  <acronym>HTML</acronym> <sgmltag>table</sgmltag> tag. 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>.
-	  </para>
-	  </listitem>
-	  </varlistentry>
-
-
-	  <varlistentry>
-	  <term><literal>pager</literal></term>
-	  <listitem>
-	  <para>
-	  Toggles the list of a pager to do table output. If the
-	  environment variable <envar>PAGER</envar> is set, the output
-	  is piped to the specified program. Otherwise
-	  <filename>more</filename> is used.
-	  </para>
-
-	  <para>
-	  In any case, <application>psql</application> only uses the
-	  pager if it seems appropriate. That means among other things
-	  that the output is to a terminal and that the table would
-	  normally not fit on the screen. Because of the modular nature
-	  of the printing routines it is not always possible to predict
-	  the number of lines that will actually be printed. For that
-	  reason <application>psql</application> might not appear very
-	  discriminating about when to use the pager and when not to.
-	  </para>
-	  </listitem>
-	  </varlistentry>
-	</variablelist>
-	Illustrations on 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
-	arguments. In the future this call might show the current status
-	of all printing options.
-	</para>
-	</note>
-
-	</listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\q</literal></term>
-        <listitem>
-        <para>
-        Quit the <application>psql</application> program.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\qecho</literal> <replaceable class="parameter">text</replaceable> [ ... ] </term>
-        <listitem>
-        <para>
-	This command is identical to <command>\echo</command> except
-	that all 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</literal> [ <replaceable class="parameter">filename</replaceable> ]</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> history library.
-        </para>
-
-	<note>
-	<para>
-	In the current version, it is no longer necessary to save the
-	command history, since that will be done automatically on
-	program termination. The history is also loaded automatically
-	every time <application>psql</application> starts up.
-	</para>
-	</note>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\set</literal> [ <replaceable class="parameter">name</replaceable> [ <replaceable class="parameter">value</replaceable> [ ... ]]]</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 about
-	<application>psql</application> variables for details.
-	</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" endterm="SQL-SET-title">.
-	</para>
-	</note>
-	</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</literal> <replaceable class="parameter">table_options</replaceable></term>
-        <listitem>
-        <para>
-        Allows you to specify options to be placed within the
-        <sgmltag>table</sgmltag> tag in <acronym>HTML</acronym> tabular
-        output mode. This command is equivalent to <literal>\pset
-        tableattr <replaceable
-        class="parameter">table_options</replaceable></literal>.
-        </para>
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-       <term><literal>\timing</literal></term>
-        <listitem>
-        <para>
-         Toggles a display of how long each query takes in seconds.
-        </para>
-       </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\w</literal> {<replaceable class="parameter">filename</replaceable> | <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 extended row format mode. As such it is equivalent to
-	<literal>\pset expanded</literal>.
-       </para>
-       </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\z</literal> [ <replaceable class="parameter">pattern</replaceable> ]</term>
-        <listitem>
-        <para>
-        Produces a list of all tables in the database with their
-        appropriate access permissions listed. If an argument is given
-        it is taken as a regular expression which limits the listing to
-        those tables which match it.
-        </para>
-
-	<para>
-<programlisting>
-test=&gt; <userinput>\z</userinput>
-Access permissions for database "test"
- Relation |           Access permissions
-----------+-------------------------------------
- my_table | {"=r","joe=arwR", "group staff=ar"}
-(1 row )
-</programlisting>
-        Read this as follows:
-
-	<itemizedlist>
-          <listitem>
-          <para>
-          <literal>"=r"</literal>: <literal>PUBLIC</literal> has read
-          (<command>SELECT</command>) permission on the table.
-	  </para>
-	  </listitem>
-
-	  <listitem>
-	  <para>
-	  <literal>"joe=arwR"</literal>: User <literal>joe</literal> has
-	  read, write (<command>UPDATE</command>,
-	  <command>DELETE</command>), <quote>append</quote>
-	  (<command>INSERT</command>) permissions, and permission to
-	  create rules on the table.
-	  </para>
-	  </listitem>
-
-	  <listitem>
-	  <para>
-	  <literal>"group staff=ar"</literal>: Group
-	  <literal>staff</literal> has <command>SELECT</command> and
-	  <command>INSERT</command> permission.
-	  </para>
-	  </listitem>
-	</itemizedlist>
-	</para>
-
-	<para>
-	The commands <xref linkend="SQL-GRANT"> and
-	<xref linkend="SQL-REVOKE">
-	are used to set access permissions.
-	</para>
-
-        </listitem>
-      </varlistentry>
-
-
-      <varlistentry>
-        <term><literal>\!</literal> [ <replaceable class="parameter">command</replaceable> ]</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>
-        Get help information about the backslash (<quote>\</quote>)
-        commands.
-        </para>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-  </para>
-</refsect1>
-
-
-
-<refsect1 id="R1-APP-PSQL-3">
-  <refsect1info>
-    <date>1998-09-26</date>
-  </refsect1info>
-
-  <title>Command-line Options</title>
-
-  <para>
-  If so configured, <application>psql</application> understands both
-  standard Unix short options, and <acronym>GNU</acronym>-style long
-  options. The latter are not available on all systems.
-  </para>
-
-  <para>
-  <variablelist>
-    <varlistentry>
-      <term>-a, --echo-all</term>
-      <listitem>
-      <para>
-      Print all the lines to the screen as they are read. This is more
-      useful for script processing rather than interactive mode. This is
-      equivalent to setting the variable <envar>ECHO</envar> to
-      <literal>all</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-A, --no-align</term>
-      <listitem>
-      <para>
-      Switches to unaligned output mode. (The default output mode is
-      otherwise aligned.)
-      </para>
-      </listitem>
-    </varlistentry>
-
-	
-    <varlistentry>
-      <term>-c, --command <replaceable class="parameter">query</replaceable></term>
-      <listitem>
-      <para>
-      Specifies that <application>psql</application> is to execute one
-      query string, <replaceable class="parameter">query</replaceable>,
-      and then exit. This is useful in shell scripts.
-      </para>
-      <para>
-      <replaceable class="parameter">query</replaceable> must be either
-      a query string that is completely parseable by the backend (i.e.,
-      it contains no <application>psql</application> specific features),
-      or it is a single backslash command. Thus you cannot mix
-      <acronym>SQL</acronym> and <application>psql</application>
-      meta-commands. To achieve that, you could pipe the string into
-      <application>psql</application>, like this: <literal>echo "\x \\
-      select * from foo;" | psql</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-d, --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>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-e, --echo-queries</term>
-      <listitem>
-      <para>
-      Show all queries that are sent to the backend. This is equivalent
-      to setting the variable <envar>ECHO</envar> to
-      <literal>queries</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-E, --echo-hidden</term>
-      <listitem>
-      <para>
-      Echoes the actual queries generated by \d and other backslash
-      commands. You can use this if you wish to include similar
-      functionality into your own programs. This is equivalent to
-      setting the variable <envar>ECHO_HIDDEN</envar> from within
-      <application>psql</application>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-f, --file <replaceable class="parameter">filename</replaceable></term>
-      <listitem>
-      <para>
-      Use the file <replaceable class="parameter">filename</replaceable>
-      as the source of queries instead of reading queries 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 that you would have gotten had you entered
-      everything by hand.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-F, --field-separator <replaceable class="parameter">separator</replaceable></term>
-      <listitem>
-      <para>
-      Use <replaceable class="parameter">separator</replaceable> as the
-      field separator. This is equivalent to <command>\pset
-      fieldsep</command> or <command>\f</command>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-h, --host <replaceable class="parameter">hostname</replaceable></term>
-      <listitem>
-      <para>
-      Specifies the host name of the machine on which the
-      <application>postmaster</application> is running. If host begins
-      with a slash, it is used as the directory for the unix domain
-      socket.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-H, --html</term>
-      <listitem>
-      <para>
-      Turns 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>-l, --list</term>
-      <listitem>
-      <para>
-      Lists all available databases, then exits. Other non-connection
-      options are ignored. This is similar to the internal command
-      <command>\list</command>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-o, --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>-p, --port <replaceable class="parameter">port</replaceable></term>
-      <listitem>
-      <para>
-      Specifies the TCP/IP port or, by omission, the local Unix domain
-      socket file extension on which the
-      <application>postmaster</application> 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>-P, --pset <replaceable class="parameter">assignment</replaceable></term>
-      <listitem>
-      <para>
-      Allows you to specify printing options in the style of
-      <command>\pset</command> on the command line. Note that here you
-      have to separate name and value with an equal sign instead of a
-      space. Thus to set the output format to LaTeX, you could write
-      <literal>-P format=latex</literal>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-q</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
-      <envar>QUIET</envar> variable to achieve the same effect.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-R, --record-separator <replaceable class="parameter">separator</replaceable></term>
-      <listitem>
-      <para>
-      Use <replaceable class="parameter">separator</replaceable> as the
-      record separator. This is equivalent to the <command>\pset
-      recordsep</command> command.
-      </para>
-      </listitem>
-    </varlistentry>
-
- 
-    <varlistentry>
-      <term>-s, --single-step</term>
-      <listitem>
-      <para>
-      Run in single-step mode. That means the user is prompted before
-      each query is sent to the backend, with the option to cancel
-      execution as well. Use this to debug scripts.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-S, --single-line</term>
-      <listitem>
-      <para>
-      Runs in single-line mode where a newline terminates a query, 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>-t, --tuples-only</term>
-      <listitem>
-      <para>
-      Turn off printing of column names and result row count footers,
-      etc. It is completely equivalent to the <command>\t</command>
-      meta-command.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-T, --table-attr <replaceable class="parameter">table_options</replaceable></term>
-      <listitem>
-      <para>
-      Allows you to specify options to be placed within the
-      <acronym>HTML</acronym> <sgmltag>table</sgmltag> tag. See
-      <command>\pset</command> for details.
-      </para>
-      </listitem>
-    </varlistentry>
-
- 
-    <varlistentry>
-      <term>-u</term>
-      <listitem>
-      <para>
-      Makes <application>psql</application> prompt for the user name and
-      password before connecting to the database.
-      </para>
-
-      <para>
-      This option is deprecated, as it is conceptually flawed.
-      (Prompting for a non-default user name and prompting for a
-      password because the backend requires it are really two different
-      things.) You are encouraged to look at the <option>-U</option> and
-      <option>-W</option> options instead.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-U, --username <replaceable class="parameter">username</replaceable></term>
-      <listitem>
-      <para>
-      Connects 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>-v, --variable, --set <replaceable class="parameter">assignment</replaceable></term>
-      <listitem>
-      <para>
-      Performs 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>-V, --version</term>
-      <listitem>
-      <para>
-      Shows the <application>psql</application> version.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-W, --password</term>
-      <listitem>
-      <para>
-      Requests that <application>psql</application> should prompt for a
-      password before connecting to a database. This will remain set for
-      the entire session, even if you change the database connection
-      with the meta-command <command>\connect</command>.
-      </para>
-
-      <para>
-      In the current version, <application>psql</application>
-      automatically issues a password prompt whenever the backend
-      requests password authentication. Because this is currently based
-      on a hack, the automatic recognition might mysteriously fail,
-      hence this option to force a prompt. If no password prompt is
-      issued and the backend requires password authentication the
-      connection attempt will fail.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-x, --expanded</term>
-      <listitem>
-      <para>
-      Turns on extended row format mode. This is equivalent to the
-      command <command>\x</command>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-X, --no-psqlrc</term>
-      <listitem>
-      <para>
-      Do not read the start-up file <filename>~/.psqlrc</filename>.
-      </para>
-      </listitem>
-    </varlistentry>
-
-
-    <varlistentry>
-      <term>-?, --help</term>
-      <listitem>
-      <para>
-      Shows help about <application>psql</application> command line
-      arguments.
-      </para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
-  </para>
-
-</refsect1>
-
-
-<refsect1 id="R1-APP-PSQL-4">
-    <refsect1info>
-      <date>1998-09-27</date>
-    </refsect1info>
-
-    <title>Advanced features</title>
-
-  <refsect2 id="APP-PSQL-variables">
-    <title id="APP-PSQL-variables-title">Variables</title>
-
-    <para>
-    <application>psql</application> provides variable substitution
-    features similar to common Unix command shells. This feature is new
-    and not very sophisticated, yet, but there are plans to expand it in
-    the future. 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=> <userinput>\set foo bar</userinput>
-</programlisting>
-    sets the variable <quote>foo</quote> to the value
-    <quote>bar</quote>. 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=> <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 simply set, but has no 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 regular 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 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
-    such variables. A list of all specially treated variables follows.
-    <variablelist>
-      <varlistentry>
-        <term><envar>DBNAME</envar></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><envar>ECHO</envar></term>
-	<listitem>
-	<para>
-	If set to <quote><literal>all</literal></quote>, all lines
-	entered or from a script are written to the standard output
-	before they are parsed or executed. To specify this on program
-	start-up, use the switch <option>-a</option>. If set to
-	<quote><literal>queries</literal></quote>,
-	<application>psql</application> merely prints all queries as
-	they are sent to the backend. The option for this is
-	<option>-e</option>.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><envar>ECHO_HIDDEN</envar></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
-	<productname>PostgreSQL</productname> internals and provide
-	similar functionality in your own programs. If you set the
-	variable to the value <quote>noexec</quote>, the queries are
-	just shown but are not actually sent to the backend and
-	executed.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><envar>ENCODING</envar></term>
-	<listitem>
-	<para>
-        The current client multibyte encoding. If you are not set up to
-        use multibyte characters, this variable will always contain
-        <quote>SQL_ASCII</quote>.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><envar>HISTCONTROL</envar></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><envar>HISTSIZE</envar></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><envar>HOST</envar></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><envar>IGNOREEOF</envar></term>
-	<listitem>
-	<para>
-         If unset, sending an EOF character (usually Control-D) to an
-         interactive session of <application>psql</application> will
-         terminate the application. If set to a numeric value, that many
-         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><envar>LASTOID</envar></term>
-	<listitem>
-	<para>
-        The value of the last affected oid, as returned from an
-        <command>INSERT</command> or <command>lo_insert</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>
-        <term><envar>LO_TRANSACTION</envar></term>
-	<listitem>
-	<para>
-	If you use the <productname>PostgreSQL</productname> large
-	object interface to specially store data that does not fit into
-	one tuple, all the operations must be contained in a transaction
-	block. (See the documentation of the large object interface for
-	more information.) Since <application>psql</application> has no
-	way to tell if you already have a transaction in progress when
-	you call one of its internal commands
-	(<command>\lo_export</command>, <command>\lo_import</command>,
-	<command>\lo_unlink</command>) it must take some arbitrary
-	action. This action could either be to roll back any transaction
-	that might already be in progress, or to commit any such
-	transaction, or to do nothing at all. In the last case you must
-	provide your own <command>BEGIN
-	TRANSACTION</command>/<command>COMMIT</command> block or the
-	results will be unpredictable (usually resulting in the desired
-	action's not being performed in any case).
-	</para>
-
-	<para>
-	To choose what you want to do you set this variable to one of
-	<quote>rollback</quote>, <quote>commit</quote>, or
-	<quote>nothing</quote>. The default is to roll back the
-	transaction. If you just want to load one or a few objects this
-	is fine. However, if you intend to transfer many large objects,
-	it might be advisable to provide one explicit transaction block
-	around all commands.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><envar>ON_ERROR_STOP</envar></term>
-	<listitem>
-	<para>
-	By default, if non-interactive scripts encounter an error, such
-	as a malformed <acronym>SQL</acronym> query 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><envar>PORT</envar></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><envar>PROMPT1</envar>, <envar>PROMPT2</envar>, <envar>PROMPT3</envar></term>
-	<listitem>
-	<para>
-	These specify what the prompt <application>psql</application>
-	issues is supposed to look like. See <quote><xref
-	linkend="APP-PSQL-prompting"
-	endterm="APP-PSQL-prompting-title"></quote> below.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><envar>QUIET</envar></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><envar>SINGLELINE</envar></term>
-	<listitem>
-	<para>
-	This variable is set by the command line option
-	<option>-S</option>. You can unset or reset it at run time.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><envar>SINGLESTEP</envar></term>
-	<listitem>
-	<para>
-	This variable is equivalent to the command line option
-	<option>-s</option>.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><envar>USER</envar></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>
-
-    </variablelist>
-
-    </para>
-
-  </refsect2>
-
-
-  <refsect2 id="APP-PSQL-sql-interpol">
-    <title id="APP-PSQL-sql-interpol-title"><acronym>SQL</acronym> Interpolation</title>
-
-    <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. The syntax for
-    this is again to prepend the variable name with a colon
-    (<literal>:</literal>).
-<programlisting>
-testdb=> <userinput>\set foo 'my_table'</userinput>
-testdb=> <userinput>SELECT * FROM :foo;</userinput>
-</programlisting>
-    would then query the table <literal>my_table</literal>. 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. Variable interpolation will not be performed into
-    quoted <acronym>SQL</acronym> entities.
-    </para>
-
-    <para>
-    A popular application of this facility is to refer to the last
-    inserted <acronym>OID</acronym> in subsequent statements to build a
-    foreign key scenario. Another possible use of this mechanism is to
-    copy the contents of a file into a field. First load the file into a
-    variable and then proceed as above.
-<programlisting>
-testdb=> <userinput>\set content '\'' `cat my_file.txt` '\''</userinput>
-testdb=> <userinput>INSERT INTO my_table VALUES (:content);</userinput>
-</programlisting>
-    One possible problem with this approach is that <filename>my_file.txt</filename>
-    might contain single quotes. These need to be escaped so that
-    they don't cause a syntax error when the third line is processed. This
-    could be done with the program <application>sed</application>:
-<programlisting>
-testdb=> <userinput>\set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\''</userinput>
-</programlisting>
-    Observe the correct number of backslashes (6)! You can resolve it
-    this way: After <application>psql</application> has parsed this
-    line, it passes <literal>sed -e "s/'/\\\'/g" < my_file.txt</literal>
-    to the shell. The shell will do its own thing inside the double
-    quotes and execute <filename>sed</filename> with the arguments
-    <literal>-e</literal> and <literal>s/'/\\'/g</literal>. When
-    <application>sed</application> parses this it will replace the two
-    backslashes with a single one and then do the substitution. Perhaps
-    at one point you thought it was great that all Unix commands use the
-    same escape character. And this is ignoring the fact that you might
-    have to escape all backslashes as well because
-    <acronym>SQL</acronym> text constants are also subject to certain
-    interpretations. In that case you might be better off preparing the
-    file externally.
-    </para>
-
-    <para>
-    Since colons may legally appear in queries, the following rule
-    applies: If the variable is not set, the character sequence
-    <quote>colon+name</quote> is not changed. In any case you can escape
-    a colon with a backslash to protect it from interpretation. (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
-    <productname>PostgreSQL</productname> extensions, hence the
-    conflict.)
-    </para>
-
-  </refsect2>
-
-
-  <refsect2 id="APP-PSQL-prompting">
-    <title id="APP-PSQL-prompting-title">Prompting</title>
-
-    <para>
-    The prompts <application>psql</application> issues can be customized
-    to your preference. The three variables <envar>PROMPT1</envar>,
-    <envar>PROMPT2</envar>, and <envar>PROMPT3</envar> 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 query. Prompt 2 is
-    issued when more input is expected during query input because the
-    query 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
-    tuples on the terminal.
-    </para>
-
-    <para>
-    The value of the respective prompt variable is printed literally,
-    except where a percent sign (<quote>%</quote>) 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 after 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 user name you are connected as (not your local system
-         user name).</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 <quote>~</quote>
-         (tilde) if the database is your default database.</para></listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%#</literal></term>
-	<listitem><para>If the current user is a database superuser, then a
-         <quote>#</quote>, otherwise a <quote>&gt;</quote>.</para></listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%R</literal></term>
-	<listitem>
-	<para>
-	In prompt 1 normally <quote>=</quote>, but <quote>^</quote> if
-	in single-line mode, and <quote>!</quote> if the session is
-	disconnected from the database (which can happen if
-	<command>\connect</command> fails). In prompt 2 the sequence is
-	replaced by <quote>-</quote>, <quote>*</quote>, a single quote,
-	or a double quote, depending on whether
-	<application>psql</application> expects more input because the
-	query wasn't terminated yet, because you are inside a
-	<literal>/* ... */</literal> comment, or because you are inside
-	a quote. In prompt 3 the sequence doesn't resolve to anything.
-	</para>
-	</listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term><literal>%</literal><replaceable class="parameter">digits</replaceable></term>
-	<listitem>
-	<para>
-	If <replaceable class="parameter">digits</replaceable> starts
-	with <literal>0x</literal> the rest of the characters are
-	interpreted as a hexadecimal digit and the character with the
-	corresponding code is substituted. If the first digit is
-	<literal>0</literal> the characters are interpreted as on octal
-	number and the corresponding character is substituted. Otherwise
-	a decimal number is assumed.
-	</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 <quote><xref linkend="APP-PSQL-variables"
-	endterm="APP-PSQL-variables-title"></quote> 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>
-
-    </variablelist>
-
-    To insert a percent sign into your prompt, write
-    <literal>%%</literal>. The default prompts are equivalent to
-    <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>
-
-   </refsect2>
-
-  <refsect2 id="APP-PSQL-MISC">
-    <title id="APP-PSQL-MISC-title">Miscellaneous</title>
-
-    <para>
-    <application>psql</application> returns 0 to the shell if it
-    finished normally, 1 if a fatal error of its own (out of memory,
-    file not found) occurs, 2 if the connection to the backend went bad
-    and the session is not interactive, and 3 if an error occurred in a
-    script and the variable <envar>ON_ERROR_STOP</envar> was set.
-    </para>
-
-    <para>
-    Before starting up, <application>psql</application> attempts to read
-    and execute commands from the file
-    <filename>$HOME/.psqlrc</filename>. 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>
-
-  </refsect2>
-
-  <refsect2>
-    <title><acronym>GNU</acronym> readline</title>
-
-    <para>
-    <application>psql</application> supports the readline and history
-    libraries for convenient line editing and retrieval. The command
-    history is stored in a file named <filename>.psql_history</filename>
-    in your home directory 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. When available,
-    <application>psql</application> is automatically built to use these
-    features. If for some reason you do not like the tab completion, you
-    can turn if 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>
-
-    <para>
-    If you have the readline library installed but
-    <application>psql</application> does not seem to use it, you must
-    make sure that <productname>PostgreSQL</productname>'s top-level
-    <filename>configure</filename> script finds it.
-    <filename>configure</filename> needs to find both the library
-    <filename>libreadline.a</filename> (or a shared library equivalent)
-    <emphasis>and</emphasis> the header files
-    <filename>readline.h</filename> and <filename>history.h</filename>
-    (or <filename>readline/readline.h</filename> and
-    <filename>readline/history.h</filename>) in appropriate directories.
-    If you have the library and header files installed in an obscure
-    place you must tell <filename>configure</filename> about them, for
-    example:
-<programlisting>
-$ ./configure --with-includes=/opt/gnu/include --with-libs=/opt/gnu/lib  ...
-</programlisting>
-    Then you have to recompile <application>psql</application> (not
-    necessarily the entire code tree).
-    </para>
-
-    <para>
-    The <acronym>GNU</acronym> readline library can be obtained from the
-    <acronym>GNU</acronym> project's <acronym>FTP</acronym> server at
-    <ulink URL="ftp://ftp.gnu.org">ftp://ftp.gnu.org</ulink>.
-    </para>
-  </refsect2>
-
-
-
-</refsect1>
-
-
-<refsect1 id="APP-PSQL-examples">
-  <title id="APP-PSQL-examples-title">Examples</title>
-
-  <note>
-  <para>
-  This section only shows a few examples specific to
-  <application>psql</application>. If you want to learn
-  <acronym>SQL</acronym> or get familiar with
-  <productname>PostgreSQL</productname>, you might wish to read the
-  Tutorial that is included in the distribution.
-  </para>
-  </note>
-
-  <para>
-  The first example shows how to spread a query over several lines of
-  input. Notice the changing prompt:
-<programlisting>
-testdb=> <userinput>CREATE TABLE my_table (</userinput>
-testdb(> <userinput> first integer not null default 0,</userinput>
-testdb(> <userinput> second text</userinput>
-testdb-> <userinput>);</userinput>
-CREATE
-</programlisting>
-  Now look at the table definition again:
-<programlisting>
-testdb=> <userinput>\d my_table</userinput>
-             Table "my_table"
- Attribute |  Type   |      Modifier
------------+---------+--------------------
- first     | integer | not null default 0
- second    | text    |
-
-</programlisting>
-  At this point you decide to change the prompt to something more
-  interesting:
-<programlisting>
-testdb=> <userinput>\set PROMPT1 '%n@%m %~%R%# '</userinput>
-peter@localhost testdb=>
-</programlisting>
-  Let's assume you have filled the table with data and want to take a
-  look at it:
-<programlisting>
-peter@localhost testdb=> SELECT * FROM my_table;
- first | second
--------+--------
-     1 | one
-     2 | two
-     3 | three
-     4 | four
-(4 rows)
-
-</programlisting>
-  You can make this table look differently by using the
-  <command>\pset</command> command:
-<programlisting>
-peter@localhost testdb=> <userinput>\pset border 2</userinput>
-Border style is 2.
-peter@localhost testdb=> <userinput>SELECT * FROM my_table;</userinput>
-+-------+--------+
-| first | second |
-+-------+--------+
-|     1 | one    |
-|     2 | two    |
-|     3 | three  |
-|     4 | four   |
-+-------+--------+
-(4 rows)
-
-peter@localhost testdb=> <userinput>\pset border 0</userinput>
-Border style is 0.
-peter@localhost testdb=> <userinput>SELECT * FROM my_table;</userinput>
-first second
------ ------
-    1 one
-    2 two
-    3 three
-    4 four
-(4 rows)
-
-peter@localhost testdb=> <userinput>\pset border 1</userinput>
-Border style is 1.
-peter@localhost testdb=> <userinput>\pset format unaligned</userinput>
-Output format is unaligned.
-peter@localhost testdb=> <userinput>\pset fieldsep ","</userinput>
-Field separator is ",".
-peter@localhost testdb=> <userinput>\pset tuples_only</userinput>
-Showing only tuples.
-peter@localhost testdb=> <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=> <userinput>\a \t \x</userinput>
-Output format is aligned.
-Tuples only is off.
-Expanded display is on.
-peter@localhost testdb=> <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>
-
-
-<refsect1>
-  <refsect1info>
-    <date>1999-10-27</date>
-  </refsect1info>
-
-  <title>Appendix</title>
-
-  <refsect2>
-    <title>Bugs and Issues</title>
-
-    <itemizedlist>
-      <listitem>
-      <para>
-      In some earlier life <application>psql</application> allowed the
-      first argument to start directly after the (single-letter)
-      command. For compatibility this is still supported to some extent
-      but I am not going to explain the details here as this use is
-      discouraged. But if you get strange messages, keep this in mind.
-      For example
-<programlisting>
-testdb=> <userinput>\foo</userinput>
-Field separator is "oo",
-</programlisting>
-      which is perhaps not what one would expect.
-      </para>
-      </listitem>
-
-      <listitem>
-      <para>
-      <application>psql</application> only works 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.
-      </para>
-      </listitem>
-
-      <listitem>
-      <para>
-      Pressing Control-C during a <quote>copy in</quote> (data sent to
-      the server) doesn't show the most ideal of behaviors. If you get a
-      message such as <quote>COPY state must be terminated
-      first</quote>, simply reset the connection by entering <literal>\c
-      - -</literal>.
-      </para>
-      </listitem>
-
-    </itemizedlist>
-
-  </refsect2>
-
-</refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml
deleted file mode 100644
index 95830ebd420..00000000000
--- a/doc/src/sgml/ref/reindex.sgml
+++ /dev/null
@@ -1,270 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.11 2002/04/23 02:07:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-REINDEX">
- <refmeta>
-  <refentrytitle id="SQL-REINDEX-TITLE">REINDEX</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   REINDEX
-  </refname>
-  <refpurpose>
-   rebuild corrupted indexes
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-03-30</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-REINDEX { TABLE | DATABASE | INDEX } <replaceable class="PARAMETER">name</replaceable> [ FORCE ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-REINDEX-1">
-   <refsect2info>
-    <date>2000-03-30</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>TABLE</term>
-      <listitem>
-       <para>
-	Recreate all indexes of a specified table.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>DATABASE</term>
-      <listitem>
-       <para>
-	Recreate all system indexes of a specified database.
-	(User-table indexes are not included.)
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>INDEX</term>
-      <listitem>
-       <para>
-	Recreate a specified index.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name of the specific table/database/index to be reindexed.
-	Table and index names may be schema-qualified.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>FORCE</term>
-      <listitem>
-       <para>
-	Force rebuild of system indexes.  Without this keyword
-	<command>REINDEX</> skips system indexes that are not marked invalid.
-	FORCE is irrelevant for <command>REINDEX INDEX</>, or when reindexing
-	user indexes.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-REINDEX-2">
-   <refsect2info>
-    <date>2000-03-30</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-REINDEX
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the table is successfully reindexed.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-REINDEX-1">
-  <refsect1info>
-   <date>2000-03-30</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>REINDEX</command> is used to rebuild corrupted indexes.
-   Although in theory this should never be necessary, in practice
-   indexes may become corrupted due to software bugs or hardware
-   failures.  <command>REINDEX</command> provides a recovery method.
-  </para>
-
-  <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>
-
-  <note>
-   <para>
-    Another approach to dealing with a corrupted user-table index is
-    just to drop and recreate it.  This may in fact be preferable if
-    you would like to maintain some semblance of normal operation on
-    the table meanwhile.  <command>REINDEX</> acquires exclusive lock
-    on the table, while <command>CREATE INDEX</> only locks out writes
-    not reads of the table.
-   </para>
-  </note>
-
-  <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 backend
-   doing the recovery to not have used any of the suspect indexes itself.
-   (Indeed, in this sort of scenario you may find that backends are
-   crashing immediately at start-up, due to reliance on the corrupted
-   indexes.)  To recover safely, the postmaster must be shut down and a
-   stand-alone <productname>PostgreSQL</productname> backend must be
-   started instead, giving it
-   the command-line options -O and -P (these options allow system table
-   modifications and prevent use of system indexes, respectively).  Then
-   issue <command>REINDEX INDEX</>, <command>REINDEX TABLE</>, or
-   <command>REINDEX DATABASE</> depending on how much you want to reconstruct.
-   If in doubt, use <command>REINDEX DATABASE FORCE</> to force reconstruction
-   of all system indexes in the database.  Then quit the standalone backend
-   and restart the postmaster.
-  </para>
-
-  <para>
-   Since this is likely the only situation when most people will ever use
-   a standalone backend, some usage notes might be in order:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      Start the backend with a command like
-<screen>
-<userinput>postgres -D $PGDATA -O -P my_database</userinput>
-</screen>
-      Provide the correct path to the database area 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>
-    </listitem>
-
-    <listitem>
-     <para>
-      You can issue any SQL command, not only <command>REINDEX</>.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      Be aware that the standalone backend 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.
-      Also, you won't have any of the conveniences of readline processing
-      (no command history, for example).
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      To quit the backend, type EOF (control-D, usually).
-     </para>
-    </listitem>
-
-   </itemizedlist>
-
-   See the <xref linkend="app-postgres"> reference page for more information.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-REINDEX-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Recreate the indexes on the table <literal>mytable</literal>:
-
-   <programlisting>
-     REINDEX TABLE mytable;
-   </programlisting>
-  </para>
-
-  <para>
-   Rebuild a single index:
-
-   <programlisting>
-    REINDEX INDEX my_index;
-   </programlisting>
-  </para>
-
-  <para>
-   Rebuild all system indexes (this will only work in a standalone backend):
-
-   <programlisting>
-    REINDEX DATABASE my_database FORCE;
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-REINDEX-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-REINDEX-4">
-   <refsect2info>
-    <date>2000-03-30</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>REINDEX</command> in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/reset.sgml b/doc/src/sgml/ref/reset.sgml
deleted file mode 100644
index 9f78d9df6c1..00000000000
--- a/doc/src/sgml/ref/reset.sgml
+++ /dev/null
@@ -1,122 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/reset.sgml,v 1.14 2002/05/17 01:19:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-RESET">
- <refmeta>
-  <refentrytitle id="SQL-RESET-TITLE">RESET</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>RESET</refname>
-  <refpurpose>restore the value of a run-time parameter to a default value</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <synopsis>
-RESET <replaceable class="PARAMETER">variable</replaceable>
-  </synopsis>
-  <synopsis>
-RESET ALL
-  </synopsis>
-
-  <refsect2 id="R2-SQL-RESET-1">
-   <title>Inputs</title>
-   <para>		
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">variable</replaceable></term>
-      <listitem>
-       <para>
-	The name of a run-time parameter. See <xref
-	linkend="sql-set" endterm="sql-set-title"> for a list.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>ALL</term>
-      <listitem>
-       <para>
-        Resets all settable run-time parameters to default values.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
- </refsynopsisdiv>
-  
- <refsect1>
-  <title>Description</title>
-  <para>
-   <command>RESET</command> restores run-time parameters to their
-   default values. Refer to
-   <xref linkend="sql-set" endterm="sql-set-title">
-   for details. <command>RESET</command> is an alternate spelling for
-
-   <synopsis>
-SET <replaceable class="parameter">variable</replaceable> TO DEFAULT
-   </synopsis>
-
-   The default value is defined as the value that the variable would
-   have had, had no <command>SET</> ever been issued for it in the
-   current session.  The actual source of this value might be a
-   compiled-in default, the postmaster's configuration file or command-line
-   switches, or per-database or per-user default settings.  See the
-   <citetitle>Administrator's Guide</citetitle> for details.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Diagnostics</title>
-  <para>
-   See under the <xref linkend="sql-set"
-   endterm="sql-set-title"> command.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-  <para>
-   Set DateStyle to its default value:
-
-<screen>
-RESET DateStyle;
-</screen>
-  </para>
-
-  <para>
-   Set Geqo to its default value:
-
-<screen>   
-RESET GEQO;
-</screen>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <para>
-   <command>RESET</command> is a <productname>PostgreSQL</productname> extension.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/revoke.sgml b/doc/src/sgml/ref/revoke.sgml
deleted file mode 100644
index 3bc30cfd49a..00000000000
--- a/doc/src/sgml/ref/revoke.sgml
+++ /dev/null
@@ -1,154 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/revoke.sgml,v 1.22 2002/04/21 00:26:42 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-REVOKE">
- <refmeta>
-  <refentrytitle id="sql-revoke-title">REVOKE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>REVOKE</refname>
-  <refpurpose>remove access privileges</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-<synopsis>
-REVOKE { { SELECT | INSERT | UPDATE | DELETE | RULE | REFERENCES | TRIGGER }
-    [,...] | ALL [ PRIVILEGES ] }
-    ON [ TABLE ] <replaceable class="PARAMETER">tablename</replaceable> [, ...]
-    FROM { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-
-REVOKE { { CREATE | TEMPORARY | TEMP } [,...] | ALL [ PRIVILEGES ] }
-    ON DATABASE <replaceable>dbname</replaceable> [, ...]
-    FROM { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-
-REVOKE { EXECUTE | ALL [ PRIVILEGES ] }
-    ON FUNCTION <replaceable>funcname</replaceable> ([<replaceable>type</replaceable>, ...]) [, ...]
-    FROM { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-
-REVOKE { USAGE | ALL [ PRIVILEGES ] }
-    ON LANGUAGE <replaceable>langname</replaceable> [, ...]
-    FROM { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-
-REVOKE { { CREATE | USAGE } [,...] | ALL [ PRIVILEGES ] }
-    ON SCHEMA <replaceable>schemaname</replaceable> [, ...]
-    FROM { <replaceable class="PARAMETER">username</replaceable> | GROUP <replaceable class="PARAMETER">groupname</replaceable> | PUBLIC } [, ...]
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1 id="SQL-REVOKE-description">
-  <title>Description</title>
-
-  <para>
-   <command>REVOKE</command> allows the creator of an object to revoke
-   previously granted permissions from one or more users or groups of users.
-   The key word <literal>PUBLIC</literal> refers to the implicitly defined
-   group of all users.
-  </para>
-
-  <para>
-   Note that any particular user will have the sum
-   of privileges granted directly to him, privileges granted to any group he
-   is presently a member of, and privileges granted to
-   <literal>PUBLIC</literal>.  Thus, for example, revoking SELECT privilege
-   from <literal>PUBLIC</literal> does not necessarily mean that all users
-   have lost SELECT privilege on the object: those who have it granted
-   directly or via a group will still have it.
-  </para>
-
-  <para>
-   See the description of the <xref linkend="sql-grant" endterm="sql-grant-title"> command for
-   the meaning of the privilege types.
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-REVOKE-notes">
-  <title>Notes</title>
-
-  <para>
-   Use <xref linkend="app-psql">'s <command>\z</command> command to
-   display the privileges granted on existing objects.  See also <xref
-   linkend="sql-grant"> for information about the format.
-  </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>
-  </para>
- </refsect1>
-
- <refsect1 id="SQL-REVOKE-compatibility">
-  <title>Compatibility</title>
-
-  <refsect2>
-   <title>SQL92</title>
-
-   <para>
-    The compatibility notes of the <xref linkend="sql-grant" endterm="sql-grant-title"> command
-    apply analogously to <command>REVOKE</command>.  The syntax summary is:
-
-<synopsis>
-REVOKE [ GRANT OPTION FOR ] { SELECT | INSERT | UPDATE | DELETE | REFERENCES }
-    ON <replaceable class="parameter">object</replaceable> [ ( <replaceable class="parameter">column</replaceable> [, ...] ) ]
-    FROM { PUBLIC | <replaceable class="parameter">username</replaceable> [, ...] }
-    { RESTRICT | CASCADE }
-</synopsis>
-   </para>
-
-   <para> 
-    If user1 gives a privilege WITH GRANT OPTION to user2,
-    and user2 gives it to user3 then user1 can revoke
-    this privilege in cascade using the CASCADE keyword.
-    If user1 gives a privilege WITH GRANT OPTION to user2,
-    and user2 gives it to user3, then if user1 tries to revoke
-    this privilege it fails if he specifies the RESTRICT
-    keyword.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1>
-  <title>See Also</title>
-
-  <simpara>
-   <xref linkend="sql-grant">
-  </simpara>
- </refsect1>
-
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/rollback.sgml b/doc/src/sgml/ref/rollback.sgml
deleted file mode 100644
index 2f14ead6843..00000000000
--- a/doc/src/sgml/ref/rollback.sgml
+++ /dev/null
@@ -1,152 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/rollback.sgml,v 1.13 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-ROLLBACK">
- <refmeta>
-  <refentrytitle id="SQL-ROLLBACK-TITLE">ROLLBACK</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   ROLLBACK
-  </refname>
-  <refpurpose>
-   abort the current transaction
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-ROLLBACK [ WORK | TRANSACTION ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-ROLLBACK-1">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-    None.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-ROLLBACK-2">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-	
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-ROLLBACK
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if successful.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><computeroutput>
-WARNING:  ROLLBACK: no transaction in progress
-       </computeroutput></term>
-      <listitem>
-       <para>
-	If there is not any transaction currently in progress.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-ROLLBACK-1">
-  <refsect1info>
-   <date>1998-09-24</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>ROLLBACK</command> rolls back the current transaction and causes
-   all the updates made by the transaction to be discarded.
-  </para>
-
-  <refsect2 id="R2-SQL-ROLLBACK-3">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    Use <xref linkend="SQL-COMMIT" endterm="SQL-COMMIT-TITLE">
-    to successfully terminate a transaction.
-    <xref linkend="SQL-ABORT" endterm="SQL-ABORT-TITLE"> is a
-    synonym for <command>ROLLBACK</command>.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-ROLLBACK-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   To abort all changes:
-
-   <programlisting>
-ROLLBACK WORK;
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-ROLLBACK-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-ROLLBACK-4">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <acronym>SQL92</acronym> only specifies the two forms <literal>ROLLBACK</literal>
-    and <literal>ROLLBACK WORK</literal>. Otherwise full compatibility.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
deleted file mode 100644
index 9c203f5e57f..00000000000
--- a/doc/src/sgml/ref/select.sgml
+++ /dev/null
@@ -1,1077 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.54 2002/04/23 02:07:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SELECT">
- <refmeta>
-  <refentrytitle id="sql-select-title">SELECT</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   SELECT
-  </refname>
-  <refpurpose>
-   retrieve rows from a table or view
-  </refpurpose></refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-12-11</date>
-  </refsynopsisdivinfo>
-  <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> ] [, ...] ]
-    [ FOR UPDATE [ OF <replaceable class="PARAMETER">tablename</replaceable> [, ...] ] ]
-    [ LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-
-where <replaceable class="PARAMETER">from_item</replaceable> can be:
-
-[ ONLY ] <replaceable class="PARAMETER">table_name</replaceable> [ * ]
-    [ [ AS ] <replaceable class="PARAMETER">alias</replaceable> [ ( <replaceable class="PARAMETER">column_alias_list</replaceable> ) ] ]
-|
-( <replaceable class="PARAMETER">select</replaceable> )
-    [ AS ] <replaceable class="PARAMETER">alias</replaceable> [ ( <replaceable class="PARAMETER">column_alias_list</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_list</replaceable> ) ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-SELECT-1">
-   <refsect2info>
-    <date>2000-12-11</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">expression</replaceable></term>
-      <listitem>
-       <para>
-	The name of a table's column or an expression.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><replaceable class="PARAMETER">output_name</replaceable></term>
-      <listitem>
-       <para>
-	Specifies another name for an output column using
-	the AS clause.  This name is primarily used to label the column
-	for display.  It can also be used to refer to the column's value in
-	ORDER BY and GROUP BY clauses.  But the
-	<replaceable class="PARAMETER">output_name</replaceable>
-	cannot be used in the WHERE or HAVING clauses; write out the
-	expression instead.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><replaceable class="PARAMETER">from_item</replaceable></term>
-      <listitem>
-       <para>
-        A table reference, sub-SELECT, or JOIN clause.  See below for details.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><replaceable class="PARAMETER">condition</replaceable></term>
-      <listitem>
-       <para>
-	A Boolean expression giving a result of true or false.
-	See the WHERE and HAVING clause descriptions below.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><replaceable class="PARAMETER">select</replaceable></term>
-      <listitem>
-       <para>
-	A select statement with all features except the ORDER BY, FOR UPDATE,
-	and LIMIT clauses (even those can be used when the select is
-	parenthesized).
-       </para>
-      </listitem>
-     </varlistentry>
-     
-    </variablelist>
-   </para>
-
-   <para>
-    FROM items can contain:
-    <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 all its descendant
-	tables (if any) are scanned.  <literal>*</> can be appended to the
-	table name to indicate that descendant tables are to be scanned, but
-	in the current version, this is the default behavior.  (In releases
-	before 7.1, <literal>ONLY</> was the default behavior.)
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><replaceable class="PARAMETER">alias</replaceable></term>
-      <listitem>
-       <para>
-	A substitute name for the preceding
-	<replaceable class="PARAMETER">table_name</replaceable>.
-	An alias is used for brevity or to eliminate ambiguity for self-joins
-	(where the same table is scanned multiple times).  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-SELECT can appear in the FROM clause.  This acts as though
-	its output were created as a temporary table for the duration of
-	this single SELECT command.  Note that the sub-SELECT must be
-	surrounded by parentheses, and an alias <emphasis>must</emphasis>
-	be provided for it.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><replaceable class="PARAMETER">join_type</replaceable></term>
-      <listitem>
-       <para>
-       One of
-       <command>[ INNER ] JOIN</command>,
-       <command>LEFT [ OUTER ] JOIN</command>,
-       <command>RIGHT [ OUTER ] JOIN</command>,
-       <command>FULL [ OUTER ] JOIN</command>, or
-       <command>CROSS JOIN</command>.
-       For INNER and OUTER join types, exactly one of NATURAL,
-       ON <replaceable class="PARAMETER">join_condition</replaceable>, or
-       USING ( <replaceable class="PARAMETER">join_column_list</replaceable> )
-       must appear.  For CROSS JOIN, none of these items may appear.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><replaceable class="PARAMETER">join_condition</replaceable></term>
-      <listitem>
-       <para>
-       A qualification condition.  This is similar to the WHERE condition
-       except that it only applies to the two from_items being joined in
-       this JOIN clause.
-       </para>
-      </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><replaceable class="PARAMETER">join_column_list</replaceable></term>
-      <listitem>
-       <para>
-       A USING column list ( a, b, ... ) is shorthand for the ON condition
-       left_table.a = right_table.a AND left_table.b = right_table.b ...
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-SELECT-2">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term>Rows</term>
-      <listitem>
-       <para>
-	The complete set of rows resulting from the query specification.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>
-       <returnvalue><replaceable>count</replaceable></returnvalue>
-      </term>
-      <listitem>
-       <para>
-	The count of rows returned by the query.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-SELECT-1">
-  <refsect1info>
-   <date>2000-12-11</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>SELECT</command> will return rows from one or more tables.
-   Candidates for selection are rows which satisfy the WHERE condition;
-   if WHERE is omitted, all rows are candidates.
-   (See <xref linkend="sql-where" endterm="sql-where-title">.)
-  </para>
-
-  <para>
-   Actually, the returned rows are not directly the rows produced by the
-   FROM/WHERE/GROUP BY/HAVING clauses; rather, the output rows are formed
-   by computing the SELECT output expressions for each selected row.
-   <command>*</command> can be written in the output list as a shorthand
-   for all the columns of the selected rows.  Also, one can write
-   <replaceable class="PARAMETER">table_name</replaceable><command>.*</command>
-   as a shorthand for the columns coming from just that table.
-  </para>
-
-  <para>
-   <command>DISTINCT</command> will eliminate duplicate rows from the
-   result.
-   <command>ALL</command> (the default) will return all candidate rows,
-   including duplicates.
-  </para>
-
-  <para>
-   <command>DISTINCT ON</command> eliminates rows that match on all the
-   specified expressions, keeping only the first row of each set of
-   duplicates.  The DISTINCT ON expressions are interpreted using the
-   same rules as for ORDER BY items; see below.
-   Note that the <quote>first row</quote> of each set is unpredictable
-   unless <command>ORDER BY</command> is used to ensure that the desired
-   row appears first.  For example,
-   <programlisting>
-        SELECT DISTINCT ON (location) location, time, report
-        FROM weatherReports
-        ORDER BY location, time DESC;
-   </programlisting>
-   retrieves the most recent weather report for each location.  But if
-   we had not used ORDER BY to force descending order of time values
-   for each location, we'd have gotten a report of unpredictable age
-   for each location.
-  </para>
-
-  <para>
-   The GROUP BY clause allows a user to divide a table
-   into groups of rows that match on one or more values.
-   (See <xref linkend="sql-groupby" endterm="sql-groupby-title">.)
-  </para>
-
-  <para>
-   The HAVING clause allows selection of only those groups of rows
-   meeting the specified condition.
-   (See <xref linkend="sql-having" endterm="sql-having-title">.)
-  </para>
-   
-  <para>
-   The ORDER BY clause causes the returned rows to be sorted in a specified
-   order.  If ORDER BY is not given, the rows are returned in whatever order
-   the system finds cheapest to produce.
-   (See <xref linkend="sql-orderby" endterm="sql-orderby-title">.)
-  </para>
-   
-  <para>
-   SELECT queries can be combined using UNION, INTERSECT, and EXCEPT
-   operators.  Use parentheses if necessary to determine the ordering
-   of these operators.
-  </para>
-   
-  <para>
-   The UNION operator computes the collection of rows
-   returned by the queries involved.
-   Duplicate rows are eliminated unless ALL is specified.
-   (See <xref linkend="sql-union" endterm="sql-union-title">.)
-  </para>
-   
-  <para>
-   The INTERSECT operator computes the rows that are common to both queries.
-   Duplicate rows are eliminated unless ALL is specified.
-   (See <xref linkend="sql-intersect" endterm="sql-intersect-title">.)
-  </para>
-   
-  <para>
-   The EXCEPT operator computes the rows returned by the first query but
-   not the second query.
-   Duplicate rows are eliminated unless ALL is specified.
-   (See <xref linkend="sql-except" endterm="sql-except-title">.)
-  </para>
-   
-  <para>
-   The FOR UPDATE clause allows the SELECT statement to perform 
-   exclusive locking of selected rows.
-  </para>
-   
-  <para>
-   The LIMIT clause allows a subset of the rows produced by the query
-   to be returned to the user.
-   (See <xref linkend="sql-limit" endterm="sql-limit-title">.)
-  </para>
-
-  <para>
-   You must have SELECT privilege to a table to read its values
-   (See the <command>GRANT</command>/<command>REVOKE</command> statements).
-  </para>
-   
-  <refsect2 id="SQL-FROM">
-   <refsect2info>
-    <date>2000-12-11</date>
-   </refsect2info>
-   <title id="sql-from-title">
-    FROM Clause
-   </title>
-
-   <para>
-    The FROM clause specifies one or more source tables for the SELECT.
-    If multiple sources are specified, the result is conceptually the
-    Cartesian product of all the rows in all the sources --- but usually
-    qualification conditions are added to restrict the returned rows to
-    a small subset of the Cartesian product.
-   </para>
-
-   <para>
-    When a FROM item is a simple table name, it implicitly includes rows
-    from sub-tables (inheritance children) of the table.
-    <command>ONLY</command> will
-    suppress rows from sub-tables of the table.  Before
-    <Productname>PostgreSQL</Productname> 7.1,
-    this was the default result, and adding sub-tables was done
-    by appending <command>*</command> to the table name.
-    This old behavior is available via the command 
-    <command>SET SQL_Inheritance TO OFF;</command>
-   </para>
-
-   <para>
-    A FROM item can also be a parenthesized sub-SELECT (note that an
-    alias clause is required for a sub-SELECT!).  This is an extremely
-    handy feature since it's the only way to get multiple levels of
-    grouping, aggregation, or sorting in a single query.
-   </para>
-
-   <para>
-    Finally, a FROM item can be a JOIN clause, which combines two simpler
-    FROM items.  (Use parentheses if necessary to determine the order
-    of nesting.)
-   </para>
-
-   <para>
-    A CROSS JOIN or INNER JOIN is a simple Cartesian product,
-    the same as you get from listing the two items at the top level of FROM.
-    CROSS JOIN is equivalent to 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 FROM and
-    WHERE.
-   </para>
-
-   <para>
-    LEFT OUTER JOIN returns all rows in the qualified Cartesian product
-    (i.e., all combined rows that pass its ON condition), plus one copy of each
-    row in the left-hand table for which there was no right-hand row that
-    passed the ON condition.  This left-hand row is extended to the full
-    width of the joined table by inserting NULLs for the right-hand columns.
-    Note that only the JOIN's own ON or USING condition is considered while
-    deciding which rows have matches.  Outer ON or WHERE conditions are
-    applied afterwards.
-   </para>
-
-   <para>
-    Conversely, 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 LEFT OUTER JOIN by switching
-    the left and right inputs.
-   </para>
-
-   <para>
-    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>
-
-   <para>
-    For all the JOIN types except CROSS JOIN, you must write exactly one of
-    ON <replaceable class="PARAMETER">join_condition</replaceable>,
-    USING ( <replaceable class="PARAMETER">join_column_list</replaceable> ),
-    or NATURAL.  ON is the most general case: you can write any qualification
-    expression involving the two tables to be joined.
-    A USING column list ( a, b, ... ) is shorthand for the ON condition
-    left_table.a = right_table.a AND left_table.b = right_table.b ...
-    Also, USING implies that only one of each pair of equivalent columns will
-    be included in the JOIN output, not both.  NATURAL is shorthand for
-    a USING list that mentions all similarly-named columns in the tables.
-   </para>
-  </refsect2>
-   
-  <refsect2 id="SQL-WHERE">
-   <refsect2info>
-    <date>2000-03-15</date>
-   </refsect2info>
-   <title id="sql-where-title">
-    WHERE Clause
-   </title>
-
-   <para>
-    The optional WHERE condition has the general form:
-    
-    <synopsis>
-WHERE <replaceable class="PARAMETER">boolean_expr</replaceable>
-    </synopsis>
-    
-    <replaceable class="PARAMETER">boolean_expr</replaceable>
-    can consist of any expression which evaluates to a Boolean value.
-    In many cases, this expression will be:
-
-    <synopsis>
-     <replaceable class="PARAMETER">expr</replaceable> <replaceable class="PARAMETER">cond_op</replaceable> <replaceable class="PARAMETER">expr</replaceable>
-    </synopsis>
-
-    or
-
-    <synopsis>
-     <replaceable class="PARAMETER">log_op</replaceable> <replaceable class="PARAMETER">expr</replaceable>
-    </synopsis>
-
-    where <replaceable class="PARAMETER">cond_op</replaceable>
-    can be one of: =, &lt;, &lt;=, &gt;, &gt;= or &lt;&gt;,
-    a conditional operator like ALL, ANY, IN, LIKE, or a
-    locally defined operator, 
-    and <replaceable class="PARAMETER">log_op</replaceable> can be one 
-    of: AND, OR, NOT.
-    SELECT will ignore all rows for which the WHERE condition does not return
-    TRUE.
-   </para>
-  </refsect2>
-  
-  <refsect2 id="SQL-GROUPBY">
-   <refsect2info>
-    <date>2000-03-15</date>
-   </refsect2info>
-   <title id="sql-groupby-title">
-    GROUP BY Clause
-   </title>
-   <para>
-    GROUP BY specifies a grouped table derived by the application
-    of this clause:
-    <synopsis>
-GROUP BY <replaceable class="PARAMETER">expression</replaceable> [, ...]
-    </synopsis>
-   </para>
-
-   <para>
-    GROUP BY will condense into a single row all selected rows that share the
-    same values for the grouped columns.  Aggregate functions, if any,
-    are computed across all rows making up each group, producing a
-    separate value for each group (whereas without GROUP BY, an
-    aggregate produces a single value computed across all the selected
-    rows).  When GROUP BY is present, it is not valid for the SELECT
-    output expression(s) to refer to
-    ungrouped columns except within aggregate functions, since there
-    would be more than one possible value to return for an ungrouped column.
-   </para>
-
-   <para>
-    A GROUP BY item can be an input column name, or the name or ordinal
-    number of an output column (SELECT expression), or it can be an arbitrary
-    expression formed from input-column values.  In case of ambiguity, a GROUP
-    BY name will 
-    be interpreted as an input-column name rather than an output column name.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-HAVING">
-   <refsect2info>
-    <date>2000-03-15</date>
-   </refsect2info>
-   <title id="sql-having-title">
-    HAVING Clause
-   </title>
-   <para>
-    The optional HAVING condition has the general form:
-    
-    <synopsis>
-HAVING <replaceable class="PARAMETER">boolean_expr</replaceable>
-    </synopsis>
-    
-    where <replaceable class="PARAMETER">boolean_expr</replaceable> is the same
-    as specified for the WHERE clause.
-   </para>
-    
-   <para>
-    HAVING specifies a grouped table derived by the elimination
-    of group rows that do not satisfy the
-    <replaceable class="PARAMETER">boolean_expr</replaceable>.
-    HAVING is different from WHERE:
-    WHERE filters individual rows before application of GROUP BY,
-    while HAVING filters group rows created by GROUP BY.
-   </para>
-
-   <para>
-    Each column referenced in 
-    <replaceable class="PARAMETER">boolean_expr</replaceable> shall unambiguously
-    reference a grouping column, unless the reference appears within an
-    aggregate function.
-   </para>
-  </refsect2>
-  
-  <refsect2 id="SQL-ORDERBY">
-   <refsect2info>
-    <date>2000-03-15</date>
-   </refsect2info>
-   <title id="sql-orderby-title">
-    ORDER BY Clause
-   </title>
-   <para>
-    <synopsis>
-ORDER BY <replaceable class="PARAMETER">expression</replaceable> [ ASC | DESC | USING <replaceable class="PARAMETER">operator</replaceable> ] [, ...]
-    </synopsis></para>
-    
-   <para>
-    An ORDER BY item can be the name or ordinal
-    number of an output column (SELECT expression), or it can be an arbitrary
-    expression formed from input-column values.  In case of ambiguity, an
-    ORDER BY name will be interpreted as an output-column name.
-   </para>
-   <para>
-    The ordinal number refers to the ordinal (left-to-right) position
-    of the result column. This feature makes it possible to define an ordering
-    on the basis of a column that does not have a proper name.
-    This is never absolutely necessary because it is always possible
-    to assign a name to a result column using the AS clause, e.g.:
-    <programlisting>
-SELECT title, date_prod + 1 AS newlen FROM films ORDER BY newlen;
-    </programlisting></para>
-    
-   <para>
-    It is also possible to ORDER BY
-    arbitrary expressions (an extension to SQL92),
-    including fields that do not appear in the
-    SELECT result list.
-    Thus the following statement is legal:
-    <programlisting>
-SELECT name FROM distributors ORDER BY code;
-    </programlisting>
-    A limitation of this feature is that an ORDER BY clause applying to the
-    result of a UNION, INTERSECT, or EXCEPT query may only specify an output
-    column name or number, not an expression.
-   </para>
-    
-   <para>
-    Note that if an ORDER BY item is a simple name that matches both
-    a result column name and an input column name, ORDER BY will interpret
-    it as the result column name.  This is the opposite of the choice that
-    GROUP BY will make in the same situation.  This inconsistency is
-    mandated by the SQL92 standard.
-   </para>
-    
-   <para>
-    Optionally one may add the keyword DESC (descending)
-    or ASC (ascending) after each column name in the ORDER BY clause.
-    If not specified, ASC is assumed by default.  Alternatively, a
-    specific ordering operator name may be specified.  ASC is equivalent
-    to USING &lt; and DESC is equivalent to USING &gt;.
-   </para>
-
-   <para>
-   The null value sorts higher than any other value in a domain. In other
-   words, with ascending sort order nulls sort at the end and with
-   descending sort order nulls sort at the beginning.
-   </para>
-
-  </refsect2>
-  
-  <refsect2 id="SQL-UNION">
-   <refsect2info>
-    <date>2000-12-11</date>
-   </refsect2info>
-   <title id="sql-union-title">
-    UNION Clause
-   </title>
-   <para>
-    <synopsis>
-<replaceable class="PARAMETER">table_query</replaceable> UNION [ ALL ] <replaceable class="PARAMETER">table_query</replaceable>
-    [ ORDER BY <replaceable class="PARAMETER">expression</replaceable> [ ASC | DESC | USING <replaceable class="PARAMETER">operator</replaceable> ] [, ...] ]
-    [ LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-    </synopsis>
-
-    where
-    <replaceable class="PARAMETER">table_query</replaceable>
-    specifies any select expression without an ORDER BY, FOR UPDATE,
-    or LIMIT clause.  (ORDER BY and LIMIT can be attached to a sub-expression
-    if it is enclosed in parentheses.  Without parentheses, these clauses
-    will be taken to apply to the result of the UNION, not to its right-hand
-    input expression.)
-   </para>
-    
-   <para>
-    The UNION operator computes the collection (set union) of the rows
-    returned by the queries involved.
-    The two SELECTs that represent the direct operands of the UNION must
-    produce the same number of columns, and corresponding columns must be
-    of compatible data types.
-   </para>
-    
-   <para>
-    The result of UNION does not contain any duplicate rows
-    unless the ALL option is specified.  ALL prevents elimination of
-    duplicates.
-   </para>
-    
-   <para>
-    Multiple UNION operators in the same SELECT statement are
-    evaluated left to right, unless otherwise indicated by parentheses.
-   </para>
-    
-   <para>
-    Currently, FOR UPDATE may not be specified either for a UNION result
-    or for the inputs of a UNION.
-   </para>
-
-  </refsect2>
-
-  <refsect2 id="SQL-INTERSECT">
-   <refsect2info>
-    <date>2000-12-11</date>
-   </refsect2info>
-   <title id="sql-intersect-title">
-    INTERSECT Clause
-   </title>
-   <para>
-    <synopsis>
-<replaceable class="PARAMETER">table_query</replaceable> INTERSECT [ ALL ] <replaceable class="PARAMETER">table_query</replaceable>
-    [ ORDER BY <replaceable class="PARAMETER">expression</replaceable> [ ASC | DESC | USING <replaceable class="PARAMETER">operator</replaceable> ] [, ...] ]
-    [ LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-    </synopsis>
-    
-    where
-    <replaceable class="PARAMETER">table_query</replaceable>
-    specifies any select expression without an ORDER BY, FOR UPDATE,
-    or LIMIT clause.
-   </para>
-
-   <para>
-    INTERSECT is similar to UNION, except that it produces only rows that
-    appear in both query outputs, rather than rows that appear in either.
-   </para>
-    
-   <para>
-    The result of INTERSECT does not contain any duplicate rows
-    unless the ALL option is specified.  With ALL, a row that has
-    m duplicates in L and n duplicates in R will appear min(m,n) times.
-   </para>
-    
-   <para>
-    Multiple INTERSECT operators in the same SELECT statement are
-    evaluated left to right, unless parentheses dictate otherwise.
-    INTERSECT binds more tightly than UNION --- that is,
-    A UNION B INTERSECT C will be read as 
-    A UNION (B INTERSECT C) unless otherwise specified by parentheses.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-EXCEPT">
-   <refsect2info>
-    <date>2000-12-11</date>
-   </refsect2info>
-   <title id="sql-except-title">
-    EXCEPT Clause
-   </title>
-   <para>
-    <synopsis>
-<replaceable class="PARAMETER">table_query</replaceable> EXCEPT [ ALL ] <replaceable class="PARAMETER">table_query</replaceable>
-    [ ORDER BY <replaceable class="PARAMETER">expression</replaceable> [ ASC | DESC | USING <replaceable class="PARAMETER">operator</replaceable> ] [, ...] ]
-    [ LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-    </synopsis>
-    
-    where
-    <replaceable class="PARAMETER">table_query</replaceable>
-    specifies any select expression without an ORDER BY, FOR UPDATE,
-    or LIMIT clause.
-   </para>
-
-   <para>
-    EXCEPT is similar to UNION, except that it produces only rows that
-    appear in the left query's output but not in the right query's output.
-   </para>
-    
-   <para>
-    The result of EXCEPT does not contain any duplicate rows
-    unless the ALL option is specified.  With ALL, a row that has
-    m duplicates in L and n duplicates in R will appear max(m-n,0) times.
-   </para>
-    
-   <para>
-    Multiple EXCEPT operators in the same SELECT statement are
-    evaluated left to right, unless parentheses dictate otherwise.
-    EXCEPT binds at the same level as UNION.
-   </para>
-  </refsect2>
-
-  <refsect2 id="SQL-LIMIT">
-   <refsect2info>
-    <date>2000-02-20</date>
-   </refsect2info>
-   <title id="sql-limit-title">
-    LIMIT Clause
-   </title>
-   <para>
-    <synopsis>
-    LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL }
-    OFFSET <replaceable class="PARAMETER">start</replaceable>
-    </synopsis>
-    
-    where
-    <replaceable class="PARAMETER">count</replaceable> specifies the
-    maximum number of rows to return, and
-    <replaceable class="PARAMETER">start</replaceable> specifies the
-    number of rows to skip before starting to return rows.
-   </para>
-
-   <para>
-    LIMIT allows you to retrieve just a portion of the rows that are generated
-    by the rest of the query.  If a limit count is given, no more than that
-    many rows will be returned.  If an offset is given, that many rows will
-    be skipped before starting to return rows.
-   </para>
-
-   <para>
-    When using LIMIT, it is a good idea to use an 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 may be asking for
-    the tenth through twentieth rows, but tenth through twentieth in what
-    ordering?  You don't know what ordering unless you specify ORDER BY.
-   </para>
-
-   <para>
-    As of <productname>PostgreSQL</productname> 7.0, the
-    query optimizer takes 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 LIMIT and OFFSET.  Thus, using
-    different LIMIT/OFFSET values to select different subsets of a query
-    result <emphasis>will give inconsistent results</emphasis> unless
-    you enforce a predictable result ordering with 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 ORDER BY is used to constrain the order.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-SELECT-2">
-  <title>
-   Usage
-  </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
- Une Femme est une Femme   | 102 | Jean Luc Godard  | 1961-03-12 | Romantic
- Vertigo                   | 103 | Paramount        | 1958-11-14 | Action
- Becket                    | 103 | Paramount        | 1964-02-03 | Drama
- 48 Hrs                    | 103 | Paramount        | 1982-10-22 | Action
- War and Peace             | 104 | Mosfilm          | 1967-02-12 | Drama
- West Side Story           | 105 | United Artists   | 1961-01-03 | Musical
- Bananas                   | 105 | United Artists   | 1971-07-13 | Comedy
- Yojimbo                   | 106 | Toho             | 1961-06-16 | Drama
- There's a Girl in my Soup | 107 | Columbia         | 1970-06-11 | Comedy
- Taxi Driver               | 107 | Columbia         | 1975-05-15 | Action
- Absence of Malice         | 107 | Columbia         | 1981-11-15 | Action
- Storia di una donna       | 108 | Westward         | 1970-08-15 | Romantic
- The King and I            | 109 | 20th Century Fox | 1956-08-11 | Musical
- Das Boot                  | 110 | Bavaria Atelier  | 1981-11-11 | Drama
- Bed Knobs and Broomsticks | 111 | Walt Disney      |            | Musical
-(17 rows)
-</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
-(5 rows)
-</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) < INTERVAL '5 hour';
-
- kind     | total
-----------+-------
- Comedy   | 02:58
- Romantic | 04:38
-(2 rows)
-</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
-(13 rows)
-</programlisting>
-  </para>
-
-  <para>
-   This 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 letter W in each table.  Only distinct rows are wanted, so the
-   ALL keyword 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>
- </refsect1>
- 
- <refsect1 id="R1-SQL-SELECT-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-SELECT-4">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>Extensions</title>
-
-   <para>
-<productname>PostgreSQL</productname> allows one to omit 
-the <command>FROM</command> clause from a query. This feature
-was retained from the original PostQuel query language.  It has
-a straightforward use to compute the results of simple constant
-expressions:
-
-  <programlisting>
-SELECT 2+2;
-
- ?column?
-----------
-        4
-  </programlisting>
-
-Some other DBMSes cannot do this except by introducing a dummy one-row
-table to do the select from.  A less obvious use is to abbreviate a
-normal select from one or more tables:
-
-  <programlisting>
-SELECT distributors.* WHERE distributors.name = 'Westward';
-
- did | name
------+----------
- 108 | Westward
-  </programlisting>
-
-This works because an implicit FROM item is added for each table that is
-referenced in the query but not mentioned in FROM.  While this is a convenient
-shorthand, it's easy to misuse.  For example, the query
-  <programlisting>
-SELECT distributors.* FROM distributors d;
-  </programlisting>
-is probably a mistake; most likely the user meant
-  <programlisting>
-SELECT d.* FROM distributors d;
-  </programlisting>
-rather than the unconstrained join
-  <programlisting>
-SELECT distributors.* FROM distributors d, distributors distributors;
-  </programlisting>
-that he will actually get.  To help detect this sort of mistake,
-<Productname>PostgreSQL</Productname> 7.1
-and later will warn if the implicit-FROM feature is used in a query that also
-contains an explicit FROM clause.
-
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-SELECT-5">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    <acronym>SQL92</acronym>
-   </title>
-   <para>
-   </para>
-   
-   <refsect3 id="R3-SQL-SELECT-1">
-    <refsect3info>
-     <date>1998-04-15</date>
-    </refsect3info>
-    <title>
-     SELECT Clause
-    </title>
-    <para>
-     In the <acronym>SQL92</acronym> standard, the optional keyword <literal>AS</>
-     is just noise and can be 
-     omitted without affecting the meaning.
-     The <productname>PostgreSQL</productname> parser requires this keyword when
-     renaming output columns because the type extensibility features lead to
-     parsing ambiguities
-     in this context.  <literal>AS</literal> is optional in FROM items, however.</para>
-     
-    <para>
-     The DISTINCT ON phrase is not part of <acronym>SQL92</acronym>.
-     Nor are LIMIT and OFFSET.
-    </para>
-     
-    <para>
-     In <acronym>SQL92</acronym>, an ORDER BY clause may only use result
-     column names or numbers, while a GROUP BY clause may only use 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 result-column names.
-    </para>
-   </refsect3>
-
-   <refsect3 id="R3-SQL-UNION-1">
-    <refsect3info>
-     <date>1998-09-24</date>
-    </refsect3info>
-    <title>
-     UNION/INTERSECT/EXCEPT Clause
-    </title>
-    <para>
-     The <acronym>SQL92</acronym> syntax for UNION/INTERSECT/EXCEPT allows an
-     additional CORRESPONDING BY option:
-     <synopsis> 
-<replaceable class="PARAMETER">table_query</replaceable> UNION [ALL]
-    [CORRESPONDING [BY (<replaceable class="PARAMETER">column</replaceable> [,...])]]
-    <replaceable class="PARAMETER">table_query</replaceable>
-     </synopsis></para>
-
-    <para>
-     The CORRESPONDING BY clause is not supported by
-     <productname>PostgreSQL</productname>.
-    </para>
-   </refsect3>
-   
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/select_into.sgml b/doc/src/sgml/ref/select_into.sgml
deleted file mode 100644
index 13a80622683..00000000000
--- a/doc/src/sgml/ref/select_into.sgml
+++ /dev/null
@@ -1,165 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/select_into.sgml,v 1.18 2002/04/23 02:07:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SELECTINTO">
- <refmeta>
-  <refentrytitle id="SQL-SELECTINTO-TITLE">SELECT INTO</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   SELECT INTO
-  </refname>
-  <refpurpose>
-   create a new table from the results of a query
-  </refpurpose></refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-12-11</date>
-  </refsynopsisdivinfo>
-  <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> ] [, ...] ]
-    [ FOR UPDATE [ OF <replaceable class="PARAMETER">tablename</replaceable> [, ...] ] ]
-    [ LIMIT [ <replaceable class="PARAMETER">start</replaceable> , ] { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-
-where <replaceable class="PARAMETER">from_item</replaceable> can be:
-
-[ ONLY ] <replaceable class="PARAMETER">table_name</replaceable> [ * ]
-    [ [ AS ] <replaceable class="PARAMETER">alias</replaceable> [ ( <replaceable class="PARAMETER">column_alias_list</replaceable> ) ] ]
-|
-( <replaceable class="PARAMETER">select</replaceable> )
-    [ AS ] <replaceable class="PARAMETER">alias</replaceable> [ ( <replaceable class="PARAMETER">column_alias_list</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_list</replaceable> ) ]
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-SELECTINTO-1">
-   <refsect2info>
-    <date>2001-03-20</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-
-   <para>
-    <variablelist>
-    <varlistentry>
-     <term>TEMPORARY</term>
-     <term>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><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>
-
-   <para>
-    All other inputs are described in detail for
-    <xref linkend="sql-select">.
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-SELECTINTO-2">
-   <refsect2info>
-    <date>2001-03-20</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-
-   <para>
-    Refer to
-    <xref linkend="sql-createtable">
-    and
-    <xref linkend="sql-select">
-    for a summary of possible output messages.
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-SELECTINTO-1">
-  <refsect1info>
-   <date>2001-03-20</date>
-  </refsect1info>
-  <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>.
-
-   <note>
-    <para>
-     <xref linkend="sql-createtableas">
-     is functionally equivalent to <command>SELECT INTO</command>.
-     <command>CREATE TABLE AS</command> is the recommended syntax, since
-     <command>SELECT INTO</command> is not standard.  In fact, this form of
-     <command>SELECT INTO</command> is not available in <application>PL/pgSQL</application> or <xref linkend="app-ecpg">,
-     because they interpret the INTO clause differently.
-    </para>
-   </note>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-SELECTINTO-2">
-  <title>
-   Compatibility
-  </title>
-
-   <para>
-    SQL92 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>PL/pgSQL</application> and <xref linkend="app-ecpg">.
-    The <productname>PostgreSQL</productname> usage of <command>SELECT
-    INTO</command> to represent table creation is historical.  It's best
-    to use <command>CREATE TABLE AS</command> for this purpose in new code.
-    (<command>CREATE TABLE AS</command> isn't standard either, but it's
-    less likely to cause confusion.)
-    </para>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/set.sgml b/doc/src/sgml/ref/set.sgml
deleted file mode 100644
index 5ccb3a7a0df..00000000000
--- a/doc/src/sgml/ref/set.sgml
+++ /dev/null
@@ -1,515 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.62 2002/06/11 15:41:30 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SET">
- <refmeta>
-  <refentrytitle id="SQL-SET-TITLE">SET</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>SET</refname>
-  <refpurpose>change a run-time parameter</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <synopsis>
-SET [ SESSION | LOCAL ] <replaceable class="PARAMETER">variable</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>
-
-  <refsect2 id="R2-SQL-SET-1">
-   <title>Inputs</title>
-   <para>
-    <variablelist>
-
-     <varlistentry>
-      <term><option>SESSION</></term>
-      <listitem>
-       <para>
-        Specifies that the command takes effect for the current session.
-        (This is the default if neither <option>SESSION</> nor
-        <option>LOCAL</> appears.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><option>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's
-        executed outside a <command>BEGIN</> block, since the transaction
-        will end immediately.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">variable</replaceable></term>
-      <listitem>
-       <para>
-        A settable run-time parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable class="PARAMETER">value</replaceable></term>
-      <listitem>
-       <para>
-        New value of parameter.  <option>DEFAULT</option> can be
-        used to specify resetting the parameter to its default
-        value. Lists of strings are allowed, but more complex
-        constructs may need to be single or double quoted.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
- </refsynopsisdiv>
- 
- <refsect1 id="R1-SQL-SET-1">
-  <title>Description</title>
-
-  <para>
-   The <command>SET</command> command changes run-time configuration
-   parameters.  Many of the run-time parameters listed in the
-   <citetitle>Administrator's Guide</citetitle> 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.)
-   Note that <command>SET</command> only affects the value used by the
-   current session.
-  </para>
-
-  <para>
-   If <command>SET</command> or <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.  (This behavior represents a change from
-   <productname>PostgreSQL</productname> versions prior to 7.3, where
-   the effects of <command>SET</command> would not roll back after a later
-   error.)  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>
-   Here are additional details about a few of the parameters that can be set:
-
-   <variablelist>
-    <varlistentry>
-     <term>DATESTYLE</term>
-     <listitem>
-      <para>
-       Choose the date/time representation style. Two separate
-       settings are involved: the default date/time output and the
-       interpretation of ambiguous input.
-      </para>
-
-      <para>
-       The following are date/time output styles:
-
-       <variablelist>
-        <varlistentry>
-         <term>ISO</term>
-         <listitem>
-          <para>
-           Use ISO 8601-style dates and times (<literal>YYYY-MM-DD
-            HH:MM:SS</literal>). This is the default.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term>SQL</term>
-         <listitem>
-          <para>
-           Use Oracle/Ingres-style dates and times. Note that this
-           style has nothing to do with SQL (which mandates ISO 8601
-           style), the naming of this option is a historical accident.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term>PostgreSQL</term>
-         <listitem>
-          <para>
-           Use traditional <productname>PostgreSQL</productname> format.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term>German</term>
-         <listitem>
-          <para>
-           Use <literal>dd.mm.yyyy</literal> for numeric date representations.
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-      </para>
-
-      <para>
-       The following two options determine both a substyle of the
-       <quote>SQL</quote> and <quote>PostgreSQL</quote> output formats
-       and the preferred interpretation of ambiguous date input.
-
-       <variablelist>
-        <varlistentry>
-         <term>European</term>
-         <listitem>
-          <para>
-           Use <literal>dd/mm/yyyy</literal> for numeric date representations.
-          </para>
-         </listitem>
-        </varlistentry>
-
-        <varlistentry>
-         <term>NonEuropean</term>
-         <term>US</term>
-         <listitem>
-          <para>
-           Use <literal>mm/dd/yyyy</literal> for numeric date representations.
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-      </para>
-
-      <para>
-       A value for <command>SET DATESTYLE</command> can be one from
-       the first list (output styles), or one from the second list
-       (substyles), or one from each separated by a comma.
-      </para>
-
-      <para>
-       <command>SET DATESTYLE</command> affects interpretation of
-       input and provides several standard output formats. For
-       applications needing different variations or tighter control
-       over input or output, consider using
-       the <function>to_char</function> family of
-       functions.
-      </para>
-
-      <para>
-       There are several now-deprecated means for setting the datestyle
-       in addition to the normal methods of setting it via <command>SET</> or
-       a configuration-file entry:
-       <simplelist>
-        <member>
-         Setting the postmaster's <envar>PGDATESTYLE</envar> environment
-         variable.  (This will be overridden by any of the other methods.)
-        </member>
-        <member>
-         Running postmaster using the option <option>-o -e</option> to
-         set dates to the <literal>European</literal> convention.
-         (This overrides environment variables and configuration-file
-         entries.)
-        </member>
-        <member>
-         Setting the client's <envar>PGDATESTYLE</envar> environment variable.
-         If PGDATESTYLE is set in the frontend environment of a client
-         based on libpq, libpq will automatically set DATESTYLE to the
-         value of PGDATESTYLE during connection start-up.  This is
-         equivalent to a manually issued <command>SET DATESTYLE</>.
-        </member>
-       </simplelist>
-      </para>
-
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>NAMES</term>
-     <listitem>
-      <para>
-       <command>SET NAMES</> is an alias for <command>SET CLIENT_ENCODING</>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-     <varlistentry>
-      <term>SEED</term>
-      <listitem>
-       <para>
-       Sets the internal seed for the random number generator.
-	
-       <variablelist>
-        <varlistentry>
-         <term><replaceable class="parameter">value</replaceable></term>
-         <listitem>
-          <para>
-           The value for the seed to be used by the
-           <function>random</function> function. Allowed
-           values are floating-point numbers between 0 and 1, which
-           are then multiplied by 2<superscript>31</>-1.
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-      </para>
-
-      <para>
-       The seed can also be set by invoking the
-       <function>setseed</function> SQL function:
-
-       <programlisting>
-SELECT setseed(<replaceable>value</replaceable>);
-       </programlisting>
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>SERVER_ENCODING</term>
-     <listitem>
-      <para>
-       Shows the server-side multibyte encoding.  (At present, this
-       parameter can be shown but not set, because the encoding is
-       determined at initdb time.)
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>TIME ZONE</term>
-     <term>TIMEZONE</term>
-     <listitem>
-      <para>
-       Sets the default time zone for your session. Arguments can be
-       an SQL time interval constant, an integer or double precision
-       constant, or a string representing a time zone name recognized
-       by the host operating system.
-      </para>
-
-      <para>
-       Here are some typical values for time zone settings:
-
-       <variablelist>
-        <varlistentry>
-         <term>'PST8PDT'</term>
-         <listitem>
-          <para>
-           Set the time zone for Berkeley, California.
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term>'Portugal'</term>
-         <listitem>
-          <para>
-           Set the time zone for Portugal.
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term>'Europe/Rome'</term>
-         <listitem>
-          <para>
-           Set the time zone for Italy.
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term>7</term>
-         <listitem>
-          <para>
-           Set the time zone to 7 hours offset west from GMT (equivalent
-           to PDT).
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term>INTERVAL '08:00' HOUR TO MINUTE</term>
-         <listitem>
-          <para>
-           Set the time zone to 8 hours offset west from GMT (equivalent
-           to PST).
-          </para>
-         </listitem>
-        </varlistentry>
-        <varlistentry>
-         <term>LOCAL</term>
-         <term>DEFAULT</term>
-         <listitem>
-          <para>
-           Set the time zone to your local time zone (the one that
-           your operating system defaults to).
-          </para>
-         </listitem>
-        </varlistentry>
-       </variablelist>
-      </para>
-
-      <para>
-       The available time zone names depend on your operating
-       system. For example, on Linux
-       <filename>/usr/share/zoneinfo</filename> contains the database
-       of time zones; the names of the files in that directory can be
-       used as parameters to this command.
-      </para>
-
-      <para>
-       If an invalid time zone is specified, the time zone
-       becomes GMT (on most systems anyway).
-      </para>
-
-      <para>
-       If the <envar>PGTZ</envar> environment variable is set in the frontend
-       environment of a client based on libpq, libpq will automatically
-       <command>SET TIMEZONE</command> to the value of
-       <envar>PGTZ</envar> during connection start-up. 
-      </para>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
-
-  <para>
-   Use <xref linkend="SQL-SHOW" endterm="SQL-SHOW-title"> to show the
-   current setting of a parameter.
-  </para>
-  
- </refsect1>
-
- <refsect1>
-  <title>Diagnostics</title>
-  <para>
-    
-   <variablelist>
-    <varlistentry>
-     <term><computeroutput>SET</computeroutput></term>
-     <listitem>
-      <para>
-       Message returned if successful.
-      </para>
-     </listitem>
-    </varlistentry>
-     
-    <varlistentry>
-     <term><computeroutput>ERROR:  not a valid option name: <replaceable>name</replaceable></computeroutput></term>
-     <listitem>
-      <para>
-       The parameter you tried to set does not exist.
-      </para>
-     </listitem>
-    </varlistentry>
-     
-    <varlistentry>
-     <term><computeroutput>ERROR:  permission denied</computeroutput></term>
-     <listitem>
-      <para>
-       You must be a superuser to alter certain settings.
-      </para>
-     </listitem>
-    </varlistentry>
-     
-    <varlistentry>
-     <term><computeroutput>ERROR:  <replaceable>name</replaceable> can only be set at start-up</computeroutput></term>
-     <listitem>
-      <para>
-       Some parameters are fixed once the server is started.
-      </para>
-     </listitem>
-    </varlistentry>
-     
-   </variablelist>
-  </para>
- </refsect1>
-
- 
- <refsect1>
-  <title>Examples</title>
-  <para>
-   Set the style of date to traditional
-   <productname>PostgreSQL</productname> with European conventions:
-   <screen>
-SET DATESTYLE TO PostgreSQL,European;
-   </screen>
-  </para>
-
-  <para>
-   Set the time zone for Berkeley, California, using quotes to
-   preserve the uppercase spelling of the time zone name (note
-   that the date style is <literal>PostgreSQL</literal> for this
-   example): 
-
-   <screen>
-SET TIME ZONE 'PST8PDT';
-SELECT CURRENT_TIMESTAMP AS today;
-               today                
-------------------------------------
- Tue Feb 26 07:32:21.42834 2002 PST
-   </screen>
-  </para>
-
-  <para>
-   Set the time zone for Italy (note the required single quotes to handle 
-   the special characters):
-
-   <screen>
-SET TIME ZONE 'Europe/Rome';
-SELECT CURRENT_TIMESTAMP AS today;
-   
-         today
-------------------------
- 1998-03-31 17:41:31+02
-   </screen>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-SET-3">
-  <title>Compatibility</title>
-
-  <refsect2 id="R2-SQL-SET-4">
-   <title>
-    SQL92
-   </title>
-
-   <para>
-    <literal>SET TIME ZONE</literal>
-    extends syntax defined in
-    <acronym>SQL9x</acronym>. <acronym>SQL9x</acronym> allows
-    only numeric time zone offsets while
-    <productname>PostgreSQL</productname> allows full time zone
-    specifier strings as well. All other <literal>SET</literal>
-    features are
-    <productname>PostgreSQL</productname> extensions.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/set_constraints.sgml b/doc/src/sgml/ref/set_constraints.sgml
deleted file mode 100644
index ed15b09a24c..00000000000
--- a/doc/src/sgml/ref/set_constraints.sgml
+++ /dev/null
@@ -1,76 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_constraints.sgml,v 1.4 2002/06/03 01:10:38 momjian Exp $ -->
-<refentry id="SQL-SET-CONSTRAINTS">
- <refmeta>
-  <refentrytitle id="SQL-SET-CONSTRAINTS-title">SET CONSTRAINTS</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>SET CONSTRAINTS</refname>
-  <refpurpose>set the constraint mode of the current transaction</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2000-06-01</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-SET CONSTRAINTS { ALL | <replaceable class="parameter">constraint</replaceable> [, ...] } { DEFERRED | IMMEDIATE }
-  </synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   <command>SET CONSTRAINTS</command> sets the behavior of constraint
-   evaluation in the current transaction. In
-   <option>IMMEDIATE</option> mode, constraints are checked at the end
-   of each statement. In <option>DEFERRED</option> mode, constraints
-   are not checked until transaction commit.
-  </para>
-
-  <para>
-   Upon creation, a constraint is always give one of three
-   characteristics: <option>INITIALLY DEFERRED</option>,
-   <option>INITIALLY IMMEDIATE DEFERRABLE</option>, or
-   <option>INITIALLY IMMEDIATE NOT DEFERRABLE</option>. The third
-   class is not affected by the <command>SET CONSTRAINTS</command>
-   command.
-  </para>
-
-  <para>
-   Currently, only foreign key constraints are affected by this
-   setting. Check and unique constraints are always effectively
-   initially immediate not deferrable.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-SET-CONSTRAINT-3">
-  <title>Compatibility</title>
-
-  <refsect2 id="R2-SQL-SET-CONSTRAINT-4">
-   <title>SQL92, SQL99</title>
-
-   <para>
-    <command>SET CONSTRAINTS</command> is defined in
-    <acronym>SQL92</acronym> and <acronym>SQL99</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/set_session_auth.sgml b/doc/src/sgml/ref/set_session_auth.sgml
deleted file mode 100644
index dfb20357005..00000000000
--- a/doc/src/sgml/ref/set_session_auth.sgml
+++ /dev/null
@@ -1,120 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_session_auth.sgml,v 1.6 2002/05/17 01:19:16 tgl Exp $ -->
-<refentry id="SQL-SET-SESSION-AUTHORIZATION">
- <docinfo>
-  <date>2001-04-21</date>
- </docinfo>
-
- <refmeta>
-  <refentrytitle id="sql-set-session-authorization-title">SET SESSION AUTHORIZATION</refentrytitle>
-  <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>
-
- <refsynopsisdiv>
-<synopsis>
-SET [ SESSION | LOCAL ] SESSION AUTHORIZATION <parameter>username</parameter>
-SET [ SESSION | LOCAL ] SESSION AUTHORIZATION DEFAULT
-RESET SESSION AUTHORIZATION
-</synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   This command sets the session user identifier and the current user
-   identifier of the current SQL-session context to be
-   <parameter>username</parameter>.  The user name may be written as
-   either an identifier or a string literal.
-   The session user identifier is valid for the duration of a
-   connection; for example, it is possible to temporarily become an
-   unprivileged user and later switch back to become 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
-   may change temporarily in the context of <quote>setuid</quote>
-   functions and similar mechanisms.  The current user identifier is
-   relevant for permission checking.
-  </para>
-
-  <para>
-   The session user identifier may 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 username.
-  </para>
-
-  <para>
-   The <option>SESSION</> and <option>LOCAL</> modifiers act the same
-   as for the regular <xref linkend="SQL-SET" endterm="SQL-SET-title">
-   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 are always accepted.
-  </para>
-
- </refsect1>
-
- <refsect1>
-  <title>Examples</title>
-
-<screen>
-<userinput>SELECT SESSION_USER, CURRENT_USER;</userinput>
- current_user | session_user
---------------+--------------
- peter        | peter
-
-<userinput>SET SESSION AUTHORIZATION 'paul';</userinput>
-
-<userinput>SELECT SESSION_USER, CURRENT_USER;</userinput>
- current_user | session_user
---------------+--------------
- paul         | paul
-</screen>
- </refsect1>
-
- <refsect1>
-  <title>Compatibility</title>
-
-  <simpara>SQL99</simpara>
-
-  <para>
-   SQL99 allows some other expressions to appear in place of the
-   literal <parameter>username</parameter> which are not important in
-   practice.  <application>PostgreSQL</application> allows identifier
-   syntax (<literal>"username"</literal>), which SQL does not.  SQL
-   does not allow this command during a transaction;
-   <application>PostgreSQL</application> does not make
-   this restriction because there is no reason to.  The
-   privileges necessary to execute this command are left
-   implementation-defined by the standard.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/set_transaction.sgml b/doc/src/sgml/ref/set_transaction.sgml
deleted file mode 100644
index 5a253d85806..00000000000
--- a/doc/src/sgml/ref/set_transaction.sgml
+++ /dev/null
@@ -1,135 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_transaction.sgml,v 1.8 2002/01/20 22:19:57 petere Exp $ -->
-<refentry id="SQL-SET-TRANSACTION">
- <docinfo>
-  <date>2000-11-24</date>
- </docinfo>
-
- <refmeta>
-  <refentrytitle id="SQL-SET-TRANSACTION-TITLE">SET TRANSACTION</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
-
- <refnamediv>
-  <refname>SET TRANSACTION</refname>
-  <refpurpose>set the characteristics of the current transaction</refpurpose>
- </refnamediv>
-
- <refsynopsisdiv>
-  <synopsis>
-SET TRANSACTION ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE }
-SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL
-    { READ COMMITTED | SERIALIZABLE }
-  </synopsis>
- </refsynopsisdiv>
-
- <refsect1>
-  <title>Description</title>
-
-  <para>
-   This command sets the transaction isolation level.  The
-   <command>SET TRANSACTION</command> command sets the characteristics
-   for the current SQL-transaction. It has no effect on any subsequent
-   transactions.  This command cannot be used after the first query or data-modification
-   statement (<command>SELECT</command>, <command>INSERT</command>,
-   <command>DELETE</command>, <command>UPDATE</command>,
-   <command>FETCH</command>, <command>COPY</command>) of a transaction
-   has been executed.  <command>SET SESSION CHARACTERISTICS</command>
-   sets the default transaction isolation level for each transaction
-   for a session.  <command>SET TRANSACTION</command> can override it
-   for an individual transaction.
-  </para>
-
-  <para>
-   The isolation level of a transaction determines what data the
-   transaction can see when other transactions are running concurrently.
-
-   <variablelist>
-    <varlistentry>
-     <term>READ COMMITTED</term>
-     <listitem>
-      <para>
-       A statement can only see rows committed before it began. This
-       is the default.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term>SERIALIZABLE</term>
-     <listitem>
-      <para>
-       The current transaction can only see rows committed before
-       first query or data-modification statement was executed in this transaction.
-      </para>
-      <tip>
-       <para>
-        Intuitively, serializable means that two concurrent
-        transactions will leave the database in the same state as if
-        the two has been executed strictly after one another in either
-        order.
-       </para>
-      </tip>
-     </listitem>
-    </varlistentry>
-   </variablelist>
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Notes</title>
-
-  <para>
-   The session default transaction isolation level can also be set
-   with the command
-<programlisting>
-SET default_transaction_isolation = '<replaceable>value</replaceable>'
-</programlisting>
-   and in the
-   configuration file.  Consult the <citetitle>Administrator's
-   Guide</citetitle> for more information.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-SET-TRANSACTION-3">
-  <title>Compatibility</title>
-
-  <refsect2 id="R2-SQL-SET-TRANSACTION-4">
-   <title>SQL92, SQL99</title>
-
-   <para>
-    SERIALIZABLE is the default level in <acronym>SQL</acronym>.
-    <productname>PostgreSQL</productname> does not provide the
-    isolation levels <option>READ UNCOMMITTED</option> 
-    and <option>REPEATABLE READ</option>. Because
-    of multiversion concurrency control, the serializable level is not
-    truly serializable. See the <citetitle>User's Guide</citetitle> for
-    details.
-   </para>
-
-   <para>
-    In <acronym>SQL</acronym> there are two other transaction
-    characteristics that can be set with these commands: whether the
-    transaction is read-only and the size of the diagnostics area.
-    Neither of these concepts are supported in
-    <productname>PostgreSQL</productname>. 
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/show.sgml b/doc/src/sgml/ref/show.sgml
deleted file mode 100644
index b752f86ee61..00000000000
--- a/doc/src/sgml/ref/show.sgml
+++ /dev/null
@@ -1,124 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/show.sgml,v 1.17 2002/05/17 01:19:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-SHOW">
- <refmeta>
-  <refentrytitle id="SQL-SHOW-TITLE">SHOW</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>SHOW</refname>
-  <refpurpose>show the value of a run-time parameter</refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <synopsis>
-SHOW <replaceable class="PARAMETER">name</replaceable>
-  </synopsis>
-  <synopsis>
-SHOW ALL
-  </synopsis>
-
-  <refsect2 id="R2-SQL-SHOW-1">
-   <title>Inputs</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-        The name of a run-time parameter. See
-	<xref linkend="sql-set" endterm="sql-set-title">
-        for a list.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>ALL</term>
-      <listitem>
-       <para>
-        Show all current session parameters.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-SHOW-1">
-  <title>Description</title>
-  <para>
-   <command>SHOW</command> will display the current setting of a
-   run-time parameter. These variables can be set using the
-   <command>SET</command> statement or are determined at session start.
-  </para>
- </refsect1>
-
- <refsect1>
-  <title>Diagnostics</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>ERROR:  not a valid option name: <replaceable>name</replaceable></computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if <replaceable>variable</replaceable> does
-	not stand for an existing parameter.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-SHOW-2">
-  <title>Examples</title>
-  <para>
-   Show the current <literal>DateStyle</literal> setting:
-
-<screen>
-SHOW DateStyle;
-INFO:  DateStyle is ISO with US (NonEuropean) conventions
-</screen>
-  </para>
-
-  <para>
-   Show the current genetic optimizer (<literal>geqo</literal>) setting:
-<screen>
-SHOW GEQO;
-INFO:  geqo is on
-</screen>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-SHOW-3">
-  <title>Compatibility</title>
-
-  <para>
-   The <command>SHOW</command> command is a
-   <productname>PostgreSQL</productname> extension.
-  </para>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
deleted file mode 100644
index 723079ab3bc..00000000000
--- a/doc/src/sgml/ref/truncate.sgml
+++ /dev/null
@@ -1,142 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.8 2002/05/18 15:44:47 petere Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-TRUNCATE">
- <refmeta>
-  <refentrytitle id="SQL-TRUNCATE-TITLE">TRUNCATE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   TRUNCATE
-  </refname>
-  <refpurpose>
-   empty a table
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-TRUNCATE [ TABLE ] <replaceable class="PARAMETER">name</replaceable>
-  </synopsis>
-  
-  <refsect2 id="R2-SQL-TRUNCATE-1">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">name</replaceable></term>
-      <listitem>
-       <para>
-	The name (optionally schema-qualified) of the table to be truncated.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-  
-  <refsect2 id="R2-SQL-TRUNCATE-2">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-TRUNCATE TABLE
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if the table is successfully truncated.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-TRUNCATE-1">
-  <refsect1info>
-   <date>1998-09-08</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>TRUNCATE</command> quickly removes all rows from a
-   table. It has the same effect as an unqualified
-   <command>DELETE</command> but since it does not actually scan the
-   table it is faster. This is most useful on large tables.
-  </para>
-
-  <para>
-   <command>TRUNCATE</command> cannot be executed inside a transaction
-   block (<command>BEGIN</>/<command>COMMIT</> pair), because there is
-   no way to roll it back.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-TRUNCATE-2">
-  <title>
-   Usage
-  </title>
-  <para>
-   Truncate the table <literal>bigtable</literal>:
-
-   <programlisting>
-TRUNCATE TABLE bigtable;
-   </programlisting>
-  </para>
- </refsect1>
- 
- <refsect1 id="R1-SQL-TRUNCATE-3">
-  <title>
-   Compatibility
-  </title>
-  
-  <refsect2 id="R2-SQL-TRUNCATE-4">
-   <refsect2info>
-    <date>1998-09-08</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>TRUNCATE</command> in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/unlisten.sgml b/doc/src/sgml/ref/unlisten.sgml
deleted file mode 100644
index 07d3db1ec9e..00000000000
--- a/doc/src/sgml/ref/unlisten.sgml
+++ /dev/null
@@ -1,193 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/unlisten.sgml,v 1.18 2002/04/21 19:02:39 thomas Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-UNLISTEN">
- <refmeta>
-  <refentrytitle>UNLISTEN</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   UNLISTEN
-  </refname>
-  <refpurpose>
-   stop listening for a notification
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1998-10-19</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-UNLISTEN { <replaceable class="PARAMETER">notifyname</replaceable> | * }
-  </synopsis>
-
-  <refsect2 id="R2-SQL-UNLISTEN-1">
-   <refsect2info>
-    <date>1998-10-19</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">notifyname</replaceable></term>
-      <listitem>
-       <para>
-	Name of previously registered notify condition.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><literal>*</literal></term>
-      <listitem>
-       <para>
-	All current listen registrations for this backend are cleared.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-UNLISTEN-2">
-   <refsect2info>
-    <date>1998-10-19</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-<returnvalue>UNLISTEN</returnvalue>
-       </computeroutput></term>
-      <listitem>
-       <para>
-	Acknowledgment that statement has executed.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-UNLISTEN-1">
-  <refsect1info>
-   <date>1998-10-19</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-
-  <para>
-   <command>UNLISTEN</command>
-   is used to remove an existing <command>NOTIFY</command> registration.
-   UNLISTEN cancels any existing registration of the current
-   <productname>PostgreSQL</productname> session as a listener on the notify
-   condition <replaceable class="PARAMETER">notifyname</replaceable>.
-   The special condition wildcard <literal>*</literal> cancels all listener registrations
-   for the current session.
-  </para>
-
-  <para>
-   <xref endterm="sql-notify-title" linkend="sql-notify">
-   contains a more extensive
-   discussion of the use of <command>LISTEN</command> and
-   <command>NOTIFY</command>.
-  </para>
-
-  <refsect2 id="R2-SQL-UNLISTEN-3">
-   <refsect2info>
-    <date>1998-10-19</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-   <para>
-    <replaceable class="PARAMETER">notifyname</replaceable>
-    need not be a valid class name but can be any string valid
-    as a name up to 32 characters long.
-   </para>
-   <para>
-    The backend does not complain if you UNLISTEN something you were not
-    listening for.
-    Each backend will automatically execute <command>UNLISTEN *</command> when
-    exiting.
-   </para>
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-UNLISTEN-2">
-  <title>
-   Usage
-  </title>
-
-  <para>
-   To subscribe to an existing registration:
-
-<programlisting>
-LISTEN virtual;
-LISTEN
-NOTIFY virtual;
-NOTIFY
-Asynchronous NOTIFY 'virtual' from backend with pid '8448' received
-</programlisting>
-  </para>
-
-  <para>
-   Once UNLISTEN has been executed, further NOTIFY commands will be
-   ignored:
-
-<programlisting>
-UNLISTEN virtual;
-UNLISTEN
-NOTIFY virtual;
-NOTIFY
--- notice no NOTIFY event is received
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-UNLISTEN-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-UNLISTEN-4">
-   <refsect2info>
-    <date>1998-10-19</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>UNLISTEN</command> in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/update.sgml b/doc/src/sgml/ref/update.sgml
deleted file mode 100644
index 439e11be4bb..00000000000
--- a/doc/src/sgml/ref/update.sgml
+++ /dev/null
@@ -1,219 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.19 2002/04/23 02:07:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-UPDATE">
- <refmeta>
-  <refentrytitle id="SQL-UPDATE-TITLE">UPDATE</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   UPDATE
-  </refname>
-  <refpurpose>
-   update rows of a table
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>1999-07-20</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-UPDATE [ ONLY ] <replaceable class="PARAMETER">table</replaceable> SET <replaceable class="PARAMETER">col</replaceable> = <replaceable class="PARAMETER">expression</replaceable> [, ...]
-    [ FROM <replaceable class="PARAMETER">fromlist</replaceable> ]
-    [ WHERE <replaceable class="PARAMETER">condition</replaceable> ]
-  </synopsis>
-
-  <refsect2 id="R2-SQL-UPDATE-1">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-   <para>
-
-    <variablelist>
-     <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>.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">expression</replaceable></term>
-      <listitem>
-       <para>
-	A valid expression or value to assign to column.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">fromlist</replaceable></term>
-      <listitem>
-       <para>
-	A <productname>PostgreSQL</productname>
-	non-standard extension to allow columns
-	from other tables to appear in the WHERE condition.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term><replaceable class="PARAMETER">condition</replaceable></term>
-      <listitem>
-       <para>
-	Refer to the SELECT statement for a further description
-	of the WHERE clause.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-UPDATE-2">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-UPDATE <replaceable class="parameter">#</replaceable>
-      </computeroutput></term>
-      <listitem>
-       <para>
-	Message returned if successful.
-	The <replaceable class="parameter">#</replaceable>
-	means the number of rows updated.
-	If <replaceable class="parameter">#</replaceable>
-	is 0 no rows are updated.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-UPDATE-1">
-  <refsect1info>
-   <date>1998-09-24</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>UPDATE</command> changes the values of the columns specified for
-   all rows which satisfy condition. Only the columns 
-   to be modified need appear as columns in the statement.
-  </para>
-
-  <para>
-   Array references use the same syntax found in
-   <xref linkend="sql-select" endterm="sql-select-title">.
-   That is, either single array elements, a range of array
-   elements or the entire array may be replaced with a single
-   query.
-  </para>
-
-  <para>
-   You must have write access to the table in order to modify
-   it, as well as read access to any table whose values are
-   mentioned in the WHERE condition.
-  </para>
-
-  <para>
-  By default UPDATE will update tuples in the table specified 
-  and all its sub-tables. If you wish to only update the
-  specific table mentioned, you should use the ONLY clause.
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-UPDATE-2">
-  <title>
-   Usage
-  </title>
-
-  <para>
-   Change word <literal>Drama</> with <literal>Dramatic</> on column <structfield>kind</>:
-
-<programlisting>
-UPDATE films 
-SET kind = 'Dramatic' 
-WHERE kind = 'Drama';
-SELECT * 
-FROM films 
-WHERE kind = 'Dramatic' OR kind = 'Drama';
-
- code  |     title     | did | date_prod  |   kind   | len
--------+---------------+-----+------------+----------+-------
- BL101 | The Third Man | 101 | 1949-12-23 | Dramatic | 01:44
- P_302 | Becket        | 103 | 1964-02-03 | Dramatic | 02:28
- M_401 | War and Peace | 104 | 1967-02-12 | Dramatic | 05:57
- T_601 | Yojimbo       | 106 | 1961-06-16 | Dramatic | 01:50
- DA101 | Das Boot      | 110 | 1981-11-11 | Dramatic | 02:29
-</programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-UPDATE-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-UPDATE-4">
-   <refsect2info>
-    <date>1998-09-24</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    <acronym>SQL92</acronym> defines a different syntax for
-    the positioned UPDATE statement:
-
-    <synopsis>
-UPDATE <replaceable>table</replaceable> SET <replaceable>column</replaceable> = <replaceable>expression</replaceable> [, ...]
-    WHERE CURRENT OF <replaceable class="parameter">cursor</replaceable>
-    </synopsis>
-
-    where <replaceable class="parameter">cursor</replaceable>
-    identifies an open cursor.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
deleted file mode 100644
index 310dd4004f7..00000000000
--- a/doc/src/sgml/ref/vacuum.sgml
+++ /dev/null
@@ -1,305 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.25 2002/04/23 02:07:16 tgl Exp $
-PostgreSQL documentation
--->
-
-<refentry id="SQL-VACUUM">
- <refmeta>
-  <refentrytitle id="sql-vacuum-title">VACUUM</refentrytitle>
-  <refmiscinfo>SQL - Language Statements</refmiscinfo>
- </refmeta>
- <refnamediv>
-  <refname>
-   VACUUM
-  </refname>
-  <refpurpose>
-   garbage-collect and optionally analyze a database
-  </refpurpose>
- </refnamediv>
- <refsynopsisdiv>
-  <refsynopsisdivinfo>
-   <date>2001-08-26</date>
-  </refsynopsisdivinfo>
-  <synopsis>
-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>
-
-  <refsect2 id="R2-SQL-VACUUM-1">
-   <refsect2info>
-    <date>2001-07-10</date>
-   </refsect2info>
-   <title>
-    Inputs
-   </title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term>FULL</term>
-      <listitem>
-       <para>
-        Selects <quote>full</quote> vacuum, which may reclaim more space,
-	but takes much longer and exclusively locks the table.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>FREEZE</term>
-      <listitem>
-       <para>
-        Selects aggressive <quote>freezing</quote> of tuples.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>VERBOSE</term>
-      <listitem>
-       <para>
-	Prints a detailed vacuum activity report for each table.
-       </para>
-      </listitem>
-     </varlistentry>
-     <varlistentry>
-      <term>ANALYZE</term>
-      <listitem>
-       <para>
-	Updates statistics used by the optimizer 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.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-SQL-VACUUM-2">
-   <refsect2info>
-    <date>1998-10-04</date>
-   </refsect2info>
-   <title>
-    Outputs
-   </title>
-   <para>
-
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>
-<returnvalue>VACUUM</returnvalue>
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The command is complete.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-INFO:  --Relation <replaceable class="PARAMETER">table</replaceable>--
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The report header for <replaceable class="PARAMETER">table</replaceable>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-INFO:  Pages 98: Changed 25, Reapped 74, Empty 0, New 0;
-         Tup 1000: Vac 3000, Crash 0, UnUsed 0, MinLen 188, MaxLen 188;
-         Re-using: Free/Avail. Space 586952/586952; EndEmpty/Avail. Pages 0/74.
-         Elapsed 0/0 sec.
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The analysis for <replaceable class="PARAMETER">table</replaceable> itself.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>
-INFO:  Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
-         Tuples 1000: Deleted 3000. Elapsed 0/0 sec.
-       </computeroutput></term>
-      <listitem>
-       <para>
-	The analysis for an index on the target table.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
- </refsynopsisdiv>
-
- <refsect1 id="R1-SQL-VACUUM-1">
-  <refsect1info>
-   <date>2001-07-10</date>
-  </refsect1info>
-  <title>
-   Description
-  </title>
-  <para>
-   <command>VACUUM</command> reclaims storage occupied by deleted tuples.
-   In normal <productname>PostgreSQL</productname> operation, tuples that
-   are DELETEd or obsoleted by 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.  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" endterm="sql-analyze-title">
-   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.  <command>VACUUM
-   FULL</command> does more extensive processing, including moving of tuples
-   across blocks to try to compact the table to the minimum number of disk
-   blocks.  This form is much slower and requires an exclusive lock on each
-   table while it is being processed.
-  </para>
-
-  <para>
-   <command>FREEZE</command> is a special-purpose option that
-   causes tuples to be marked <quote>frozen</quote> as soon as possible,
-   rather than waiting until they are quite old.  If this is done when there
-   are no other open transactions in the same database, then it is guaranteed
-   that all tuples in the database are <quote>frozen</> and will not be
-   subject to transaction ID wraparound problems, no matter how long the
-   database is left un-vacuumed.
-   <command>FREEZE</command> is not recommended for routine use.  Its only
-   intended usage is in connection with preparation of user-defined template
-   databases, or other databases that are completely read-only and will not
-   receive routine maintenance <command>VACUUM</> operations.
-   See the <citetitle>Administrator's Guide</> for details.
-  </para>
-
-  <refsect2 id="R2-SQL-VACUUM-3">
-   <refsect2info>
-    <date>2001-07-10</date>
-   </refsect2info>
-   <title>
-    Notes
-   </title>
-
-   <para>
-    We recommend that active production databases be
-    <command>VACUUM</command>-ed frequently (at least nightly), in order to
-    remove expired rows. After adding or deleting a large number
-    of records, it may 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
-    <productname>PostgreSQL</productname> query optimizer to make better
-    choices in planning user queries.
-   </para>
-
-   <para>
-    The <option>FULL</option> option is not recommended for routine use,
-    but may be useful in special cases.  An example is when you have deleted
-    most of the rows in a table and would like the table to physically shrink
-    to occupy less disk space.  <command>VACUUM FULL</command> will usually
-    shrink the table more than a plain <command>VACUUM</command> would.
-   </para>
-
-  </refsect2>
- </refsect1>
-
- <refsect1 id="R1-SQL-VACUUM-2">
-  <title>
-   Usage
-  </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:  --Relation onek--
-INFO:  Index onek_unique1: Pages 14; Tuples 1000: Deleted 3000.
-        CPU 0.00s/0.11u sec elapsed 0.12 sec.
-INFO:  Index onek_unique2: Pages 16; Tuples 1000: Deleted 3000.
-        CPU 0.00s/0.10u sec elapsed 0.10 sec.
-INFO:  Index onek_hundred: Pages 13; Tuples 1000: Deleted 3000.
-        CPU 0.00s/0.10u sec elapsed 0.10 sec.
-INFO:  Index onek_stringu1: Pages 31; Tuples 1000: Deleted 3000.
-        CPU 0.01s/0.09u sec elapsed 0.10 sec.
-INFO:  Removed 3000 tuples in 70 pages.
-        CPU 0.02s/0.04u sec elapsed 0.07 sec.
-INFO:  Pages 94: Changed 0, Empty 0; Tup 1000: Vac 3000, Keep 0, UnUsed 0.
-        Total CPU 0.05s/0.45u sec elapsed 0.59 sec.
-INFO:  Analyzing onek
-VACUUM
-   </programlisting>
-  </para>
- </refsect1>
-
- <refsect1 id="R1-SQL-VACUUM-3">
-  <title>
-   Compatibility
-  </title>
-
-  <refsect2 id="R2-SQL-VACUUM-4">
-   <refsect2info>
-    <date>1998-10-04</date>
-   </refsect2info>
-   <title>
-    SQL92
-   </title>
-   <para>
-    There is no <command>VACUUM</command> statement in <acronym>SQL92</acronym>.
-   </para>
-  </refsect2>
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/ref/vacuumdb.sgml b/doc/src/sgml/ref/vacuumdb.sgml
deleted file mode 100644
index b1c3cab01a8..00000000000
--- a/doc/src/sgml/ref/vacuumdb.sgml
+++ /dev/null
@@ -1,310 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuumdb.sgml,v 1.21 2002/02/18 05:48:43 momjian Exp $
-PostgreSQL documentation
--->
-
-<refentry id="APP-VACUUMDB">
- <docinfo>
-  <date>2000-11-11</date>
- </docinfo>
-
- <refmeta>
-  <refentrytitle id="APP-VACUUMDB-TITLE"><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>
-
- <refsynopsisdiv>
-  <cmdsynopsis>
-   <command>vacuumdb</command>
-   <arg rep="repeat"><replaceable>connection-options</replaceable></arg>
-   <group><arg>--full</arg><arg>-f</arg></group>
-   <group><arg>--verbose</arg><arg>-v</arg></group>
-   <group><arg>--analyze</arg><arg>-z</arg></group>
-   <arg>--table | -t '<replaceable>table</replaceable>
-    <arg>( <replaceable class="parameter">column</replaceable> [,...] )</arg>'
-   </arg>
-   <arg><replaceable>dbname</replaceable></arg>
-   <sbr>
-   <command>vacuumdb</command>
-   <arg rep="repeat"><replaceable>connection-options</replaceable></arg>
-   <group><arg>--all</arg><arg>-a</arg></group>
-   <group><arg>--full</arg><arg>-f</arg></group>
-   <group><arg>--verbose</arg><arg>-v</arg></group>
-   <group><arg>--analyze</arg><arg>-z</arg></group>
-  </cmdsynopsis>
-
-  <refsect2 id="R2-APP-VACUUMDB-1">
-   <title>
-    Inputs
-   </title>
-   <para>
-    <application>vacuumdb</application> accepts the following command line arguments:
-    
-    <variablelist>
-     <varlistentry>
-      <term>-d <replaceable class="parameter">dbname</replaceable></term>
-      <term>--dbname <replaceable class="parameter">dbname</replaceable></term>
-      <listitem>
-       <para>
-	Specifies the name of the database to be cleaned or analyzed.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-a</term>
-      <term>--all</term>
-      <listitem>
-       <para>
-	Vacuum all databases.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-f</term>
-      <term>--full</term>
-      <listitem>
-       <para>
-        Perform <quote>full</quote> vacuuming.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-v</term>
-      <term>--verbose</term>
-      <listitem>
-       <para>
-	Print detailed information during processing.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-z</term>
-      <term>--analyze</term>
-      <listitem>
-       <para>
-	Calculate statistics for use by the optimizer.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-t <replaceable class="parameter">table</replaceable> [ (<replaceable class="parameter">column</replaceable> [,...]) ]</term>
-      <term>--table <replaceable class="parameter">table</replaceable> [ (<replaceable class="parameter">column</replaceable> [,...]) ]</term>
-      <listitem>
-       <para>
-	Clean or analyze <replaceable class="parameter">table</replaceable> only.
-	Column names may be specified only in conjunction with
-	the <option>--analyze</option> option.
-       </para>
-       <tip>
-        <para>
-         If you specify columns to vacuum, you probably have to escape the parentheses
-         from the shell.
-        </para>
-       </tip>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-    <application>vacuumdb</application> also accepts 
-    the following command line arguments for connection parameters:
-    
-    <variablelist>
-     <varlistentry>
-      <term>-h <replaceable class="parameter">host</replaceable></term>
-      <term>--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>-p <replaceable class="parameter">port</replaceable></term>
-      <term>--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>-U <replaceable class="parameter">username</replaceable></term>
-      <term>--username <replaceable class="parameter">username</replaceable></term>
-      <listitem>
-       <para>
-        User name to connect as
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-W</term>
-      <term>--password</term>
-      <listitem>
-       <para>
-        Force password prompt.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-e</term>
-      <term>--echo</term>
-      <listitem>
-       <para>
-        Echo the commands that <application>vacuumdb</application> generates
-	and sends to the server.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>-q</term>
-      <term>--quiet</term>
-      <listitem>
-       <para>
-        Do not display a response.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </refsect2>
-
-  <refsect2 id="R2-APP-VACUUMDB-2">
-   <title>
-    Outputs
-   </title>
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><computeroutput>VACUUM</computeroutput></term>
-      <listitem>
-       <para>
-        Everything went well.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><computeroutput>vacuumdb: Vacuum failed.</computeroutput></term>
-      <listitem>
-       <para>
-        Something went wrong. <application>vacuumdb</application> is only a wrapper
-        script. See <xref linkend="SQL-VACUUM" endterm="SQL-VACUUM-title">
-        and <xref linkend="APP-PSQL"> for a detailed
-        discussion of error messages and potential problems.
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-
-   <para>
-   </para>
-
-  </refsect2>
- </refsynopsisdiv>
- 
- <refsect1 id="R1-APP-VACUUMDB-1">
-  <title>
-   Description
-  </title>
-
-  <para>
-   <application>vacuumdb</application> is a utility for cleaning a
-   <productname>PostgreSQL</productname> database.
-   <application>vacuumdb</application> will also generate internal statistics
-   used by the <productname>PostgreSQL</productname> query optimizer.
-  </para>
-
-  <para>
-   <application>vacuumdb</application> is a shell script wrapper around the
-   backend command
-   <xref linkend="SQL-VACUUM" endterm="SQL-VACUUM-title"> via
-   the <productname>PostgreSQL</productname> interactive terminal
-   <xref linkend="APP-PSQL">. There is no effective
-   difference between vacuuming databases via this or other methods.
-   <application>psql</application> must be found by the script and
-   a database server must be running at the targeted host. Also, any default
-   settings and environment variables available to <application>psql</application>
-   and the <application>libpq</application> front-end library do apply.
-  </para>
-
- </refsect1>
-
- <refsect1 id="R1-APP-VACUUMDB-3">
-  <title>Usage</title>
-
-  <informalexample>
-   <para>
-    To clean the database <literal>test</literal>:
-<screen>
-<prompt>$ </prompt><userinput>vacuumdb test</userinput>
-</screen>
-   </para>
-  </informalexample>
-
-  <informalexample>
-   <para>
-    To clean and analyze for the optimizer a database named
-    <literal>bigdb</literal>:
-<screen>
-<prompt>$ </prompt><userinput>vacuumdb --analyze bigdb</userinput>
-</screen>
-   </para>
-  </informalexample>
-
-  <informalexample>
-   <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>
-  </informalexample>
-
- </refsect1>
-</refentry>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode: sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"../reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:"/usr/lib/sgml/catalog"
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/refentry.sgml b/doc/src/sgml/refentry.sgml
deleted file mode 100644
index 64d102c1308..00000000000
--- a/doc/src/sgml/refentry.sgml
+++ /dev/null
@@ -1 +0,0 @@
-<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V3.1//EN">
diff --git a/doc/src/sgml/reference.ced b/doc/src/sgml/reference.ced
deleted file mode 100644
index fb8789f928c..00000000000
--- a/doc/src/sgml/reference.ced
+++ /dev/null
@@ -1,1597 +0,0 @@
-;;; This file was created by psgml on Tue Nov 13 18:57:01 2001
-(sgml-saved-dtd-version 7)
-("/usr/share/sgml/docbook/sgml-dtd-3.1/dbgenent.mod" "/usr/share/sgml/docbook/sgml-dtd-3.1/dbhier.mod" "/usr/share/sgml/docbook/sgml-dtd-3.1/cals-tbl.dtd" "/usr/share/sgml/docbook/sgml-dtd-3.1/dbpool.mod" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOtech.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOpub.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOnum.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOlat2.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOlat1.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOgrk4.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOgrk3.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOgrk2.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOgrk1.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOdia.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOcyr2.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOcyr1.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISObox.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOamsr.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOamso.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOamsn.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOamsc.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOamsb.ent" "/usr/share/sgml/sgml-iso-entities-8879.1986/ISOamsa.ent" "/usr/share/sgml/docbook/sgml-dtd-3.1/dbcent.mod" "/usr/share/sgml/docbook/sgml-dtd-3.1/dbnotn.mod" "/usr/share/sgml/docbook/sgml-dtd-3.1/docbook.dtd")
-(nil ("dbnotn" text ("-//OASIS//ENTITIES DocBook Notations V3.1//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("local.notation.class" text "" nil) ("notation.class" text "BMP| CGM-CHAR | CGM-BINARY | CGM-CLEAR | DITROFF | DVI
-		| EPS | EQN | FAX | GIF | GIF87a | GIF89a 
-		| JPG | JPEG | IGES | PCX
-		| PIC | PS | SGML | TBL | TEX | TIFF | WMF | WPG
-		| linespecific
-		" nil) ("dbcent" text ("-//OASIS//ENTITIES DocBook Character Entities V3.1//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOamsa.module" text "INCLUDE" nil) ("ISOamsa" text ("ISO 8879:1986//ENTITIES Added Math Symbols: Arrow Relations//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOamsb.module" text "INCLUDE" nil) ("ISOamsb" text ("ISO 8879:1986//ENTITIES Added Math Symbols: Binary Operators//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOamsc.module" text "INCLUDE" nil) ("ISOamsc" text ("ISO 8879:1986//ENTITIES Added Math Symbols: Delimiters//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOamsn.module" text "INCLUDE" nil) ("ISOamsn" text ("ISO 8879:1986//ENTITIES Added Math Symbols: Negated Relations//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOamso.module" text "INCLUDE" nil) ("ISOamso" text ("ISO 8879:1986//ENTITIES Added Math Symbols: Ordinary//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOamsr.module" text "INCLUDE" nil) ("ISOamsr" text ("ISO 8879:1986//ENTITIES Added Math Symbols: Relations//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISObox.module" text "INCLUDE" nil) ("ISObox" text ("ISO 8879:1986//ENTITIES Box and Line Drawing//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOcyr1.module" text "INCLUDE" nil) ("ISOcyr1" text ("ISO 8879:1986//ENTITIES Russian Cyrillic//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOcyr2.module" text "INCLUDE" nil) ("ISOcyr2" text ("ISO 8879:1986//ENTITIES Non-Russian Cyrillic//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOdia.module" text "INCLUDE" nil) ("ISOdia" text ("ISO 8879:1986//ENTITIES Diacritical Marks//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOgrk1.module" text "INCLUDE" nil) ("ISOgrk1" text ("ISO 8879:1986//ENTITIES Greek Letters//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOgrk2.module" text "INCLUDE" nil) ("ISOgrk2" text ("ISO 8879:1986//ENTITIES Monotoniko Greek//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOgrk3.module" text "INCLUDE" nil) ("ISOgrk3" text ("ISO 8879:1986//ENTITIES Greek Symbols//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOgrk4.module" text "INCLUDE" nil) ("ISOgrk4" text ("ISO 8879:1986//ENTITIES Alternative Greek Symbols//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOlat1.module" text "INCLUDE" nil) ("ISOlat1" text ("ISO 8879:1986//ENTITIES Added Latin 1//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOlat2.module" text "INCLUDE" nil) ("ISOlat2" text ("ISO 8879:1986//ENTITIES Added Latin 2//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOnum.module" text "INCLUDE" nil) ("ISOnum" text ("ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOpub.module" text "INCLUDE" nil) ("ISOpub" text ("ISO 8879:1986//ENTITIES Publishing//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("ISOtech.module" text "INCLUDE" nil) ("ISOtech" text ("ISO 8879:1986//ENTITIES General Technical//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("dbpool" text ("-//OASIS//ELEMENTS DocBook Information Pool V3.1//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("yesorno.attvals" text "NUMBER" nil) ("no.attval" text "0" nil) ("dbpool.redecl.module" text "IGNORE" nil) ("local.list.class" text "" nil) ("list.class" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList " nil) ("local.admon.class" text "" nil) ("admon.class" text "Caution|Important|Note|Tip|Warning " nil) ("local.linespecific.class" text "" nil) ("linespecific.class" text "LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot " nil) ("local.synop.class" text "" nil) ("synop.class" text "Synopsis|CmdSynopsis|FuncSynopsis " nil) ("local.para.class" text "" nil) ("para.class" text "FormalPara|Para|SimPara " nil) ("local.informal.class" text "" nil) ("informal.class" text "Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable " nil) ("local.formal.class" text "" nil) ("formal.class" text "Equation|Example|Figure|Table " nil) ("local.compound.class" text "" nil) ("compound.class" text "MsgSet|Procedure|Sidebar|QandASet " nil) ("local.genobj.class" text "" nil) ("genobj.class" text "Anchor|BridgeHead|Comment|Highlights
-		" nil) ("local.descobj.class" text "" nil) ("descobj.class" text "Abstract|AuthorBlurb|Epigraph
-		" nil) ("local.ndxterm.class" text "" nil) ("ndxterm.class" text "IndexTerm " nil) ("local.xref.char.class" text "" nil) ("xref.char.class" text "FootnoteRef|XRef " nil) ("local.gen.char.class" text "" nil) ("gen.char.class" text "Abbrev|Acronym|Citation|CiteRefEntry|CiteTitle|Emphasis
-		|FirstTerm|ForeignPhrase|GlossTerm|Footnote|Phrase
-		|Quote|Trademark|WordAsWord " nil) ("local.link.char.class" text "" nil) ("link.char.class" text "Link|OLink|ULink " nil) ("local.tech.char.class" text "" nil) ("tech.char.class" text "Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		" nil) ("local.base.char.class" text "" nil) ("base.char.class" text "Anchor " nil) ("local.docinfo.char.class" text "" nil) ("docinfo.char.class" text "Author|AuthorInitials|CorpAuthor|ModeSpec|OtherCredit
-		|ProductName|ProductNumber|RevHistory
-		" nil) ("local.other.char.class" text "" nil) ("other.char.class" text "Comment|Subscript|Superscript " nil) ("local.inlineobj.char.class" text "" nil) ("inlineobj.char.class" text "InlineGraphic|InlineMediaObject|InlineEquation " nil) ("local.component.mix" text "" nil) ("component.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 		|MsgSet|Procedure|Sidebar|QandASet 
-		|Anchor|BridgeHead|Comment|Highlights
-				|Abstract|AuthorBlurb|Epigraph
-		
-		|IndexTerm 
-		" nil) ("local.sidebar.mix" text "" nil) ("sidebar.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 		|Procedure
-		|Anchor|BridgeHead|Comment|Highlights
-		
-		|IndexTerm 
-		" nil) ("local.qandaset.mix" text "" nil) ("qandaset.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 		|Procedure
-		|Anchor|BridgeHead|Comment|Highlights
-		
-		|IndexTerm 
-		" nil) ("local.footnote.mix" text "" nil) ("footnote.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		" nil) ("local.example.mix" text "" nil) ("example.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|IndexTerm 
-		" nil) ("local.highlights.mix" text "" nil) ("highlights.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|FormalPara|Para|SimPara 
-		|IndexTerm 
-		" nil) ("local.para.mix" text "" nil) ("para.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList            |Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 
-					|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 
-		" nil) ("local.admon.mix" text "" nil) ("admon.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 		|Procedure|Sidebar
-		|Anchor|BridgeHead|Comment
-		|IndexTerm 
-		" nil) ("local.figure.mix" text "" nil) ("figure.mix" text "LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-					|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|IndexTerm 
-		" nil) ("local.tabentry.mix" text "" nil) ("tabentry.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 
-		|FormalPara|Para|SimPara 		|Graphic|MediaObject
-		" nil) ("local.glossdef.mix" text "" nil) ("glossdef.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 
-		|Comment
-		|IndexTerm 
-		" nil) ("local.legalnotice.mix" text "" nil) ("legalnotice.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 
-		|FormalPara|Para|SimPara 		|BlockQuote
-		|IndexTerm 
-		" nil) ("local.textobject.mix" text "" nil) ("textobject.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 
-		|FormalPara|Para|SimPara 		|BlockQuote
-		" nil) ("local.mediaobject.mix" text "" nil) ("mediaobject.mix" text "VideoObject|AudioObject|ImageObject " nil) ("local.ubiq.mix" text "" nil) ("ubiq.mix" text "IndexTerm |BeginPage " nil) ("ubiq.exclusion" text "-(IndexTerm |BeginPage )" nil) ("ubiq.inclusion" text "+(IndexTerm |BeginPage )" nil) ("footnote.exclusion" text "-(Footnote|Equation|Example|Figure|Table )" nil) ("highlights.exclusion" text "-(IndexTerm |BeginPage |Equation|Example|Figure|Table )" nil) ("admon.exclusion" text "-(Caution|Important|Note|Tip|Warning )" nil) ("formal.exclusion" text "-(Equation|Example|Figure|Table )" nil) ("acronym.exclusion" text "-(Acronym)" nil) ("beginpage.exclusion" text "-(BeginPage)" nil) ("ndxterm.exclusion" text "-(IndexTerm )" nil) ("local.para.char.mix" text "" nil) ("para.char.mix" text "#PCDATA
-		|FootnoteRef|XRef 	|Abbrev|Acronym|Citation|CiteRefEntry|CiteTitle|Emphasis
-		|FirstTerm|ForeignPhrase|GlossTerm|Footnote|Phrase
-		|Quote|Trademark|WordAsWord 
-		|Link|OLink|ULink 	|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		|Anchor 	|Author|AuthorInitials|CorpAuthor|ModeSpec|OtherCredit
-		|ProductName|ProductNumber|RevHistory
-		
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject|InlineEquation 
-		|Synopsis|CmdSynopsis|FuncSynopsis 
-		|IndexTerm 
-		" nil) ("local.title.char.mix" text "" nil) ("title.char.mix" text "#PCDATA
-		|FootnoteRef|XRef 	|Abbrev|Acronym|Citation|CiteRefEntry|CiteTitle|Emphasis
-		|FirstTerm|ForeignPhrase|GlossTerm|Footnote|Phrase
-		|Quote|Trademark|WordAsWord 
-		|Link|OLink|ULink 	|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		|Anchor 	|Author|AuthorInitials|CorpAuthor|ModeSpec|OtherCredit
-		|ProductName|ProductNumber|RevHistory
-		
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject|InlineEquation 
-		|IndexTerm 
-		" nil) ("local.ndxterm.char.mix" text "" nil) ("ndxterm.char.mix" text "#PCDATA
-		|FootnoteRef|XRef 	|Abbrev|Acronym|Citation|CiteRefEntry|CiteTitle|Emphasis
-		|FirstTerm|ForeignPhrase|GlossTerm|Footnote|Phrase
-		|Quote|Trademark|WordAsWord 
-		|Link|OLink|ULink 	|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		|Anchor 	|Author|AuthorInitials|CorpAuthor|ModeSpec|OtherCredit
-		|ProductName|ProductNumber|RevHistory
-		
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject
-		" nil) ("local.cptr.char.mix" text "" nil) ("cptr.char.mix" text "#PCDATA
-		|Link|OLink|ULink 	|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		|Anchor 
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject
-		|IndexTerm 
-		" nil) ("local.smallcptr.char.mix" text "" nil) ("smallcptr.char.mix" text "#PCDATA
-					|Replaceable
-					|InlineGraphic|InlineMediaObject
-		|IndexTerm 
-		" nil) ("local.word.char.mix" text "" nil) ("word.char.mix" text "#PCDATA
-					|Acronym|Emphasis|Trademark
-		|Link|OLink|ULink 
-		|Anchor 
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject
-		|IndexTerm 
-		" nil) ("local.docinfo.char.mix" text "" nil) ("docinfo.char.mix" text "#PCDATA
-		|Link|OLink|ULink 
-					|Emphasis|Trademark
-					|Replaceable
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject
-		|IndexTerm 
-		" nil) ("formalobject.title.content" text "Title, TitleAbbrev?" nil) ("equation.content" text "(Graphic+|MediaObject+)" nil) ("inlineequation.content" text "(Graphic+|InlineMediaObject+)" nil) ("programlisting.content" text "CO | LineAnnotation | #PCDATA
-		|FootnoteRef|XRef 	|Abbrev|Acronym|Citation|CiteRefEntry|CiteTitle|Emphasis
-		|FirstTerm|ForeignPhrase|GlossTerm|Footnote|Phrase
-		|Quote|Trademark|WordAsWord 
-		|Link|OLink|ULink 	|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		|Anchor 	|Author|AuthorInitials|CorpAuthor|ModeSpec|OtherCredit
-		|ProductName|ProductNumber|RevHistory
-		
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject|InlineEquation 
-		|Synopsis|CmdSynopsis|FuncSynopsis 
-		|IndexTerm 
-		" nil) ("screen.content" text "CO | LineAnnotation | #PCDATA
-		|FootnoteRef|XRef 	|Abbrev|Acronym|Citation|CiteRefEntry|CiteTitle|Emphasis
-		|FirstTerm|ForeignPhrase|GlossTerm|Footnote|Phrase
-		|Quote|Trademark|WordAsWord 
-		|Link|OLink|ULink 	|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		|Anchor 	|Author|AuthorInitials|CorpAuthor|ModeSpec|OtherCredit
-		|ProductName|ProductNumber|RevHistory
-		
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject|InlineEquation 
-		|Synopsis|CmdSynopsis|FuncSynopsis 
-		|IndexTerm 
-		" nil) ("arch.attrib" text "Arch		CDATA		#IMPLIED" nil) ("conformance.attrib" text "Conformance	NMTOKENS	#IMPLIED" nil) ("os.attrib" text "OS		CDATA		#IMPLIED" nil) ("revision.attrib" text "Revision	CDATA		#IMPLIED" nil) ("userlevel.attrib" text "UserLevel	CDATA		#IMPLIED" nil) ("vendor.attrib" text "Vendor		CDATA		#IMPLIED" nil) ("local.effectivity.attrib" text "" nil) ("effectivity.attrib" text "Arch		CDATA		#IMPLIED
-	Conformance	NMTOKENS	#IMPLIED
-	OS		CDATA		#IMPLIED
-	Revision	CDATA		#IMPLIED
-	UserLevel	CDATA		#IMPLIED
-	Vendor		CDATA		#IMPLIED
-	" nil) ("id.attrib" text "Id		ID		#IMPLIED" nil) ("idreq.attrib" text "Id		ID		#REQUIRED" nil) ("lang.attrib" text "Lang		CDATA		#IMPLIED" nil) ("remap.attrib" text "Remap		CDATA		#IMPLIED" nil) ("role.attrib" text "Role		CDATA		#IMPLIED" nil) ("xreflabel.attrib" text "XRefLabel	CDATA		#IMPLIED" nil) ("revisionflag.attrib" text "RevisionFlag	(Changed
-			|Added
-			|Deleted
-			|Off)		#IMPLIED" nil) ("local.common.attrib" text "" nil) ("common.attrib" text "Id		ID		#IMPLIED
-	Lang		CDATA		#IMPLIED
-	Remap		CDATA		#IMPLIED
-	--Role is included explicitly on each element--
-	XRefLabel	CDATA		#IMPLIED
-	RevisionFlag	(Changed
-			|Added
-			|Deleted
-			|Off)		#IMPLIED
-	Arch		CDATA		#IMPLIED
-	Conformance	NMTOKENS	#IMPLIED
-	OS		CDATA		#IMPLIED
-	Revision	CDATA		#IMPLIED
-	UserLevel	CDATA		#IMPLIED
-	Vendor		CDATA		#IMPLIED
-	
-	" nil) ("idreq.common.attrib" text "Id		ID		#REQUIRED
-	Lang		CDATA		#IMPLIED
-	Remap		CDATA		#IMPLIED
-	--Role is included explicitly on each element--
-	XRefLabel	CDATA		#IMPLIED
-	RevisionFlag	(Changed
-			|Added
-			|Deleted
-			|Off)		#IMPLIED
-	Arch		CDATA		#IMPLIED
-	Conformance	NMTOKENS	#IMPLIED
-	OS		CDATA		#IMPLIED
-	Revision	CDATA		#IMPLIED
-	UserLevel	CDATA		#IMPLIED
-	Vendor		CDATA		#IMPLIED
-	
-	" nil) ("local.graphics.attrib" text "" nil) ("graphics.attrib" text "
-	--EntityRef: Name of an external entity containing the content
-	of the graphic--
-	EntityRef	ENTITY		#IMPLIED
-
-	--FileRef: Filename, qualified by a pathname if desired, 
-	designating the file containing the content of the graphic--
-	FileRef 	CDATA		#IMPLIED
-
-	--Format: Notation of the element content, if any--
-	Format		NOTATION
-			(BMP| CGM-CHAR | CGM-BINARY | CGM-CLEAR | DITROFF | DVI
-		| EPS | EQN | FAX | GIF | GIF87a | GIF89a 
-		| JPG | JPEG | IGES | PCX
-		| PIC | PS | SGML | TBL | TEX | TIFF | WMF | WPG
-		| linespecific
-		)
-					#IMPLIED
-
-	--SrcCredit: Information about the source of the Graphic--
-	SrcCredit	CDATA		#IMPLIED
-
-	--Width: Same as CALS reprowid (desired width)--
-	Width		NUTOKEN		#IMPLIED
-
-	--Depth: Same as CALS reprodep (desired depth)--
-	Depth		NUTOKEN		#IMPLIED
-
-	--Align: Same as CALS hplace with 'none' removed; #IMPLIED means 
-	application-specific--
-	Align		(Left
-			|Right 
-			|Center)	#IMPLIED
-
-	--Scale: Conflation of CALS hscale and vscale--
-	Scale		NUMBER		#IMPLIED
-
-	--Scalefit: Same as CALS scalefit--
-	Scalefit	NUMBER
-					#IMPLIED
-	" nil) ("local.keyaction.attrib" text "" nil) ("keyaction.attrib" text "
-	--Action: Key combination type; default is unspecified if one 
-	child element, Simul if there is more than one; if value is 
-	Other, the OtherAction attribute must have a nonempty value--
-	Action		(Click
-			|Double-Click
-			|Press
-			|Seq
-			|Simul
-			|Other)		#IMPLIED
-
-	--OtherAction: User-defined key combination type--
-	OtherAction	CDATA		#IMPLIED
-	" nil) ("label.attrib" text "Label		CDATA		#IMPLIED" nil) ("linespecific.attrib" text "Format		NOTATION
-			(linespecific)	linespecific" nil) ("linkend.attrib" text "Linkend	IDREF		#IMPLIED" nil) ("linkendreq.attrib" text "Linkend	IDREF		#REQUIRED" nil) ("linkends.attrib" text "Linkends	IDREFS		#IMPLIED" nil) ("local.mark.attrib" text "" nil) ("mark.attrib" text "Mark		CDATA		#IMPLIED
-	" nil) ("moreinfo.attrib" text "MoreInfo	(RefEntry|None)	None" nil) ("pagenum.attrib" text "Pagenum	CDATA		#IMPLIED" nil) ("local.status.attrib" text "" nil) ("status.attrib" text "Status		CDATA		#IMPLIED
-	" nil) ("width.attrib" text "Width		NUMBER		#IMPLIED" nil) ("title.module" text "INCLUDE" nil) ("local.title.attrib" text "" nil) ("title.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("title.element" text "INCLUDE" nil) ("title.attlist" text "INCLUDE" nil) ("titleabbrev.module" text "INCLUDE" nil) ("local.titleabbrev.attrib" text "" nil) ("titleabbrev.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("titleabbrev.element" text "INCLUDE" nil) ("titleabbrev.attlist" text "INCLUDE" nil) ("subtitle.module" text "INCLUDE" nil) ("local.subtitle.attrib" text "" nil) ("subtitle.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("subtitle.element" text "INCLUDE" nil) ("subtitle.attlist" text "INCLUDE" nil) ("local.person.ident.mix" text "" nil) ("person.ident.mix" text "Honorific|FirstName|Surname|Lineage|OtherName|Affiliation
-		|AuthorBlurb|Contrib " nil) ("local.bibliocomponent.mix" text "" nil) ("bibliocomponent.mix" text "Abbrev|Abstract|Address|ArtPageNums|Author
-		|AuthorGroup|AuthorInitials|BiblioMisc|BiblioSet
-		|Collab|ConfGroup|ContractNum|ContractSponsor
-		|Copyright|CorpAuthor|CorpName|Date|Edition
-		|Editor|InvPartNumber|ISBN|ISSN|IssueNum|OrgName
-		|OtherCredit|PageNums|PrintHistory|ProductName
-		|ProductNumber|PubDate|Publisher|PublisherName
-		|PubsNumber|ReleaseInfo|RevHistory|SeriesVolNums
-		|Subtitle|Title|TitleAbbrev|VolumeNum|CiteTitle
-		|Honorific|FirstName|Surname|Lineage|OtherName|Affiliation
-		|AuthorBlurb|Contrib 
-		|IndexTerm 
-		" nil) ("biblioentry.module" text "INCLUDE" nil) ("local.biblioentry.attrib" text "" nil) ("biblioentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("biblioentry.element" text "INCLUDE" nil) ("biblioentry.attlist" text "INCLUDE" nil) ("bibliomixed.module" text "INCLUDE" nil) ("local.bibliomixed.attrib" text "" nil) ("bibliomixed.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("bibliomixed.element" text "INCLUDE" nil) ("bibliomixed.attlist" text "INCLUDE" nil) ("bookbiblio.module" text "INCLUDE" nil) ("local.bookbiblio.attrib" text "" nil) ("bookbiblio.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("bookbiblio.element" text "INCLUDE" nil) ("bookbiblio.attlist" text "INCLUDE" nil) ("seriesinfo.module" text "INCLUDE" nil) ("local.seriesinfo.attrib" text "" nil) ("seriesinfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("seriesinfo.element" text "INCLUDE" nil) ("seriesinfo.attlist" text "INCLUDE" nil) ("artheader.module" text "INCLUDE" nil) ("local.artheader.attrib" text "" nil) ("artheader.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("artheader.element" text "INCLUDE" nil) ("artheader.attlist" text "INCLUDE" nil) ("biblioset.module" text "INCLUDE" nil) ("local.biblioset.attrib" text "" nil) ("biblioset.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("biblioset.element" text "INCLUDE" nil) ("biblioset.attlist" text "INCLUDE" nil) ("bibliomset.module" text "INCLUDE" nil) ("bibliomset.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("local.bibliomset.attrib" text "" nil) ("bibliomset.element" text "INCLUDE" nil) ("bibliomset.attlist" text "INCLUDE" nil) ("bibliomisc.module" text "INCLUDE" nil) ("local.bibliomisc.attrib" text "" nil) ("bibliomisc.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("bibliomisc.element" text "INCLUDE" nil) ("bibliomisc.attlist" text "INCLUDE" nil) ("subjectset.content.module" text "INCLUDE" nil) ("subjectset.module" text "INCLUDE" nil) ("local.subjectset.attrib" text "" nil) ("subjectset.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("subjectset.element" text "INCLUDE" nil) ("subjectset.attlist" text "INCLUDE" nil) ("subject.module" text "INCLUDE" nil) ("local.subject.attrib" text "" nil) ("subject.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("subject.element" text "INCLUDE" nil) ("subject.attlist" text "INCLUDE" nil) ("subjectterm.module" text "INCLUDE" nil) ("local.subjectterm.attrib" text "" nil) ("subjectterm.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("subjectterm.element" text "INCLUDE" nil) ("subjectterm.attlist" text "INCLUDE" nil) ("keywordset.content.module" text "INCLUDE" nil) ("local.keywordset.attrib" text "" nil) ("keywordset.module" text "INCLUDE" nil) ("keywordset.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("keywordset.element" text "INCLUDE" nil) ("keywordset.attlist" text "INCLUDE" nil) ("keyword.module" text "INCLUDE" nil) ("local.keyword.attrib" text "" nil) ("keyword.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("keyword.element" text "INCLUDE" nil) ("keyword.attlist" text "INCLUDE" nil) ("itermset.module" text "INCLUDE" nil) ("local.itermset.attrib" text "" nil) ("itermset.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("itermset.element" text "INCLUDE" nil) ("itermset.attlist" text "INCLUDE" nil) ("msgset.content.module" text "INCLUDE" nil) ("msgset.module" text "INCLUDE" nil) ("local.msgset.attrib" text "" nil) ("msgset.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgset.element" text "INCLUDE" nil) ("msgset.attlist" text "INCLUDE" nil) ("msgentry.module" text "INCLUDE" nil) ("local.msgentry.attrib" text "" nil) ("msgentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgentry.element" text "INCLUDE" nil) ("msgentry.attlist" text "INCLUDE" nil) ("msg.module" text "INCLUDE" nil) ("local.msg.attrib" text "" nil) ("msg.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msg.element" text "INCLUDE" nil) ("msg.attlist" text "INCLUDE" nil) ("msgmain.module" text "INCLUDE" nil) ("local.msgmain.attrib" text "" nil) ("msgmain.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgmain.element" text "INCLUDE" nil) ("msgmain.attlist" text "INCLUDE" nil) ("msgsub.module" text "INCLUDE" nil) ("local.msgsub.attrib" text "" nil) ("msgsub.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgsub.element" text "INCLUDE" nil) ("msgsub.attlist" text "INCLUDE" nil) ("msgrel.module" text "INCLUDE" nil) ("local.msgrel.attrib" text "" nil) ("msgrel.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgrel.element" text "INCLUDE" nil) ("msgrel.attlist" text "INCLUDE" nil) ("msginfo.module" text "INCLUDE" nil) ("local.msginfo.attrib" text "" nil) ("msginfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msginfo.element" text "INCLUDE" nil) ("msginfo.attlist" text "INCLUDE" nil) ("msglevel.module" text "INCLUDE" nil) ("local.msglevel.attrib" text "" nil) ("msglevel.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msglevel.element" text "INCLUDE" nil) ("msglevel.attlist" text "INCLUDE" nil) ("msgorig.module" text "INCLUDE" nil) ("local.msgorig.attrib" text "" nil) ("msgorig.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgorig.element" text "INCLUDE" nil) ("msgorig.attlist" text "INCLUDE" nil) ("msgaud.module" text "INCLUDE" nil) ("local.msgaud.attrib" text "" nil) ("msgaud.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgaud.element" text "INCLUDE" nil) ("msgaud.attlist" text "INCLUDE" nil) ("msgexplan.module" text "INCLUDE" nil) ("local.msgexplan.attrib" text "" nil) ("msgexplan.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgexplan.element" text "INCLUDE" nil) ("msgexplan.attlist" text "INCLUDE" nil) ("qandset.content.module" text "INCLUDE" nil) ("qandset.module" text "INCLUDE" nil) ("local.qandset.attrib" text "" nil) ("qandset.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("qandset.element" text "INCLUDE" nil) ("qandset.attlist" text "INCLUDE" nil) ("qandadiv.module" text "INCLUDE" nil) ("local.qandadiv.attrib" text "" nil) ("qandadiv.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("qandadiv.element" text "INCLUDE" nil) ("qandadiv.attlist" text "INCLUDE" nil) ("qandaentry.module" text "INCLUDE" nil) ("local.qandaentry.attrib" text "" nil) ("qandaentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("qandaentry.element" text "INCLUDE" nil) ("qandaentry.attlist" text "INCLUDE" nil) ("question.module" text "INCLUDE" nil) ("local.question.attrib" text "" nil) ("question.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("question.element" text "INCLUDE" nil) ("question.attlist" text "INCLUDE" nil) ("answer.module" text "INCLUDE" nil) ("local.answer.attrib" text "" nil) ("answer.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("answer.element" text "INCLUDE" nil) ("answer.attlist" text "INCLUDE" nil) ("label.module" text "INCLUDE" nil) ("local.label.attrib" text "" nil) ("label.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("label.element" text "INCLUDE" nil) ("label.attlist" text "INCLUDE" nil) ("procedure.content.module" text "INCLUDE" nil) ("procedure.module" text "INCLUDE" nil) ("local.procedure.attrib" text "" nil) ("procedure.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("procedure.element" text "INCLUDE" nil) ("procedure.attlist" text "INCLUDE" nil) ("step.module" text "INCLUDE" nil) ("local.step.attrib" text "" nil) ("step.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("step.element" text "INCLUDE" nil) ("step.attlist" text "INCLUDE" nil) ("substeps.module" text "INCLUDE" nil) ("local.substeps.attrib" text "" nil) ("substeps.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("substeps.element" text "INCLUDE" nil) ("substeps.attlist" text "INCLUDE" nil) ("sidebar.module" text "INCLUDE" nil) ("local.sidebar.attrib" text "" nil) ("sidebar.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("sidebar.element" text "INCLUDE" nil) ("sidebar.attlist" text "INCLUDE" nil) ("abstract.module" text "INCLUDE" nil) ("local.abstract.attrib" text "" nil) ("abstract.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("abstract.element" text "INCLUDE" nil) ("abstract.attlist" text "INCLUDE" nil) ("authorblurb.module" text "INCLUDE" nil) ("local.authorblurb.attrib" text "" nil) ("authorblurb.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("authorblurb.element" text "INCLUDE" nil) ("authorblurb.attlist" text "INCLUDE" nil) ("blockquote.module" text "INCLUDE" nil) ("local.blockquote.attrib" text "" nil) ("blockquote.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("blockquote.element" text "INCLUDE" nil) ("blockquote.attlist" text "INCLUDE" nil) ("attribution.module" text "INCLUDE" nil) ("local.attribution.attrib" text "" nil) ("attribution.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("attribution.element" text "INCLUDE" nil) ("attribution.attlist" text "INCLUDE" nil) ("bridgehead.module" text "INCLUDE" nil) ("local.bridgehead.attrib" text "" nil) ("bridgehead.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("bridgehead.element" text "INCLUDE" nil) ("bridgehead.attlist" text "INCLUDE" nil) ("comment.module" text "INCLUDE" nil) ("local.comment.attrib" text "" nil) ("comment.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("comment.element" text "INCLUDE" nil) ("comment.attlist" text "INCLUDE" nil) ("epigraph.module" text "INCLUDE" nil) ("local.epigraph.attrib" text "" nil) ("epigraph.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("epigraph.element" text "INCLUDE" nil) ("epigraph.attlist" text "INCLUDE" nil) ("footnote.module" text "INCLUDE" nil) ("local.footnote.attrib" text "" nil) ("footnote.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("footnote.element" text "INCLUDE" nil) ("footnote.attlist" text "INCLUDE" nil) ("highlights.module" text "INCLUDE" nil) ("local.highlights.attrib" text "" nil) ("highlights.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("highlights.element" text "INCLUDE" nil) ("highlights.attlist" text "INCLUDE" nil) ("formalpara.module" text "INCLUDE" nil) ("local.formalpara.attrib" text "" nil) ("formalpara.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("formalpara.element" text "INCLUDE" nil) ("formalpara.attlist" text "INCLUDE" nil) ("para.module" text "INCLUDE" nil) ("local.para.attrib" text "" nil) ("para.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("para.element" text "INCLUDE" nil) ("para.attlist" text "INCLUDE" nil) ("simpara.module" text "INCLUDE" nil) ("local.simpara.attrib" text "" nil) ("simpara.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("simpara.element" text "INCLUDE" nil) ("simpara.attlist" text "INCLUDE" nil) ("admon.module" text "INCLUDE" nil) ("local.admon.attrib" text "" nil) ("admon.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("admon.elements" text "INCLUDE" nil) ("admon.attlists" text "INCLUDE" nil) ("glosslist.module" text "INCLUDE" nil) ("local.glosslist.attrib" text "" nil) ("glosslist.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("glosslist.element" text "INCLUDE" nil) ("glosslist.attlist" text "INCLUDE" nil) ("glossentry.content.module" text "INCLUDE" nil) ("glossentry.module" text "INCLUDE" nil) ("local.glossentry.attrib" text "" nil) ("glossentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("glossentry.element" text "INCLUDE" nil) ("glossentry.attlist" text "INCLUDE" nil) ("glossdef.module" text "INCLUDE" nil) ("local.glossdef.attrib" text "" nil) ("glossdef.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("glossdef.element" text "INCLUDE" nil) ("glossdef.attlist" text "INCLUDE" nil) ("glosssee.module" text "INCLUDE" nil) ("local.glosssee.attrib" text "" nil) ("glosssee.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("glosssee.element" text "INCLUDE" nil) ("glosssee.attlist" text "INCLUDE" nil) ("glossseealso.module" text "INCLUDE" nil) ("local.glossseealso.attrib" text "" nil) ("glossseealso.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("glossseealso.element" text "INCLUDE" nil) ("glossseealso.attlist" text "INCLUDE" nil) ("itemizedlist.module" text "INCLUDE" nil) ("local.itemizedlist.attrib" text "" nil) ("itemizedlist.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("itemizedlist.element" text "INCLUDE" nil) ("itemizedlist.attlist" text "INCLUDE" nil) ("orderedlist.module" text "INCLUDE" nil) ("local.orderedlist.attrib" text "" nil) ("orderedlist.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("orderedlist.element" text "INCLUDE" nil) ("orderedlist.attlist" text "INCLUDE" nil) ("listitem.module" text "INCLUDE" nil) ("local.listitem.attrib" text "" nil) ("listitem.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("listitem.element" text "INCLUDE" nil) ("listitem.attlist" text "INCLUDE" nil) ("segmentedlist.content.module" text "INCLUDE" nil) ("segmentedlist.module" text "INCLUDE" nil) ("local.segmentedlist.attrib" text "" nil) ("segmentedlist.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("segmentedlist.element" text "INCLUDE" nil) ("segmentedlist.attlist" text "INCLUDE" nil) ("segtitle.module" text "INCLUDE" nil) ("local.segtitle.attrib" text "" nil) ("segtitle.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("segtitle.element" text "INCLUDE" nil) ("segtitle.attlist" text "INCLUDE" nil) ("seglistitem.module" text "INCLUDE" nil) ("local.seglistitem.attrib" text "" nil) ("seglistitem.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("seglistitem.element" text "INCLUDE" nil) ("seglistitem.attlist" text "INCLUDE" nil) ("seg.module" text "INCLUDE" nil) ("local.seg.attrib" text "" nil) ("seg.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("seg.element" text "INCLUDE" nil) ("seg.attlist" text "INCLUDE" nil) ("simplelist.content.module" text "INCLUDE" nil) ("simplelist.module" text "INCLUDE" nil) ("local.simplelist.attrib" text "" nil) ("simplelist.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("simplelist.element" text "INCLUDE" nil) ("simplelist.attlist" text "INCLUDE" nil) ("member.module" text "INCLUDE" nil) ("local.member.attrib" text "" nil) ("member.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("member.element" text "INCLUDE" nil) ("member.attlist" text "INCLUDE" nil) ("variablelist.content.module" text "INCLUDE" nil) ("variablelist.module" text "INCLUDE" nil) ("local.variablelist.attrib" text "" nil) ("variablelist.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("variablelist.element" text "INCLUDE" nil) ("variablelist.attlist" text "INCLUDE" nil) ("varlistentry.module" text "INCLUDE" nil) ("local.varlistentry.attrib" text "" nil) ("varlistentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("varlistentry.element" text "INCLUDE" nil) ("varlistentry.attlist" text "INCLUDE" nil) ("term.module" text "INCLUDE" nil) ("local.term.attrib" text "" nil) ("term.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("term.element" text "INCLUDE" nil) ("term.attlist" text "INCLUDE" nil) ("calloutlist.content.module" text "INCLUDE" nil) ("calloutlist.module" text "INCLUDE" nil) ("local.calloutlist.attrib" text "" nil) ("calloutlist.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("calloutlist.element" text "INCLUDE" nil) ("calloutlist.attlist" text "INCLUDE" nil) ("callout.module" text "INCLUDE" nil) ("local.callout.attrib" text "" nil) ("callout.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("callout.element" text "INCLUDE" nil) ("callout.attlist" text "INCLUDE" nil) ("example.module" text "INCLUDE" nil) ("local.example.attrib" text "" nil) ("example.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("example.element" text "INCLUDE" nil) ("example.attlist" text "INCLUDE" nil) ("informalexample.module" text "INCLUDE" nil) ("local.informalexample.attrib" text "" nil) ("informalexample.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("informalexample.element" text "INCLUDE" nil) ("informalexample.attlist" text "INCLUDE" nil) ("programlistingco.module" text "INCLUDE" nil) ("local.programlistingco.attrib" text "" nil) ("programlistingco.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("programlistingco.element" text "INCLUDE" nil) ("programlistingco.attlist" text "INCLUDE" nil) ("areaspec.content.module" text "INCLUDE" nil) ("areaspec.module" text "INCLUDE" nil) ("local.areaspec.attrib" text "" nil) ("areaspec.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("areaspec.element" text "INCLUDE" nil) ("areaspec.attlist" text "INCLUDE" nil) ("area.module" text "INCLUDE" nil) ("local.area.attrib" text "" nil) ("area.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("area.element" text "INCLUDE" nil) ("area.attlist" text "INCLUDE" nil) ("areaset.module" text "INCLUDE" nil) ("local.areaset.attrib" text "" nil) ("areaset.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("areaset.element" text "INCLUDE" nil) ("areaset.attlist" text "INCLUDE" nil) ("programlisting.module" text "INCLUDE" nil) ("local.programlisting.attrib" text "" nil) ("programlisting.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("programlisting.element" text "INCLUDE" nil) ("programlisting.attlist" text "INCLUDE" nil) ("literallayout.module" text "INCLUDE" nil) ("local.literallayout.attrib" text "" nil) ("literallayout.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("literallayout.element" text "INCLUDE" nil) ("literallayout.attlist" text "INCLUDE" nil) ("screenco.module" text "INCLUDE" nil) ("local.screenco.attrib" text "" nil) ("screenco.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("screenco.element" text "INCLUDE" nil) ("screenco.attlist" text "INCLUDE" nil) ("screen.module" text "INCLUDE" nil) ("local.screen.attrib" text "" nil) ("screen.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("screen.element" text "INCLUDE" nil) ("screen.attlist" text "INCLUDE" nil) ("screenshot.content.module" text "INCLUDE" nil) ("screenshot.module" text "INCLUDE" nil) ("local.screenshot.attrib" text "" nil) ("screenshot.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("screenshot.element" text "INCLUDE" nil) ("screenshot.attlist" text "INCLUDE" nil) ("screeninfo.module" text "INCLUDE" nil) ("local.screeninfo.attrib" text "" nil) ("screeninfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("screeninfo.element" text "INCLUDE" nil) ("screeninfo.attlist" text "INCLUDE" nil) ("figure.module" text "INCLUDE" nil) ("local.figure.attrib" text "" nil) ("figure.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("figure.element" text "INCLUDE" nil) ("figure.attlist" text "INCLUDE" nil) ("informalfigure.module" text "INCLUDE" nil) ("local.informalfigure.attrib" text "" nil) ("informalfigure.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("informalfigure.element" text "INCLUDE" nil) ("informalfigure.attlist" text "INCLUDE" nil) ("graphicco.module" text "INCLUDE" nil) ("local.graphicco.attrib" text "" nil) ("graphicco.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("graphicco.element" text "INCLUDE" nil) ("graphicco.attlist" text "INCLUDE" nil) ("graphic.module" text "INCLUDE" nil) ("local.graphic.attrib" text "" nil) ("graphic.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("graphic.element" text "INCLUDE" nil) ("graphic.attlist" text "INCLUDE" nil) ("inlinegraphic.module" text "INCLUDE" nil) ("local.inlinegraphic.attrib" text "" nil) ("inlinegraphic.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("inlinegraphic.element" text "INCLUDE" nil) ("inlinegraphic.attlist" text "INCLUDE" nil) ("mediaobject.content.module" text "INCLUDE" nil) ("mediaobject.module" text "INCLUDE" nil) ("local.mediaobject.attrib" text "" nil) ("mediaobject.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("mediaobject.element" text "INCLUDE" nil) ("mediaobject.attlist" text "INCLUDE" nil) ("inlinemediaobject.module" text "INCLUDE" nil) ("local.inlinemediaobject.attrib" text "" nil) ("inlinemediaobject.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("inlinemediaobject.element" text "INCLUDE" nil) ("inlinemediaobject.attlist" text "INCLUDE" nil) ("videoobject.module" text "INCLUDE" nil) ("local.videoobject.attrib" text "" nil) ("videoobject.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("videoobject.element" text "INCLUDE" nil) ("videoobject.attlist" text "INCLUDE" nil) ("audioobject.module" text "INCLUDE" nil) ("local.audioobject.attrib" text "" nil) ("audioobject.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("audioobject.element" text "INCLUDE" nil) ("audioobject.attlist" text "INCLUDE" nil) ("imageobject.module" text "INCLUDE" nil) ("local.imageobject.attrib" text "" nil) ("imageobject.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("imageobject.element" text "INCLUDE" nil) ("imageobject.attlist" text "INCLUDE" nil) ("textobject.module" text "INCLUDE" nil) ("local.textobject.attrib" text "" nil) ("textobject.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("textobject.element" text "INCLUDE" nil) ("textobject.attlist" text "INCLUDE" nil) ("objectinfo.module" text "INCLUDE" nil) ("local.objectinfo.attrib" text "" nil) ("objectinfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("objectinfo.element" text "INCLUDE" nil) ("objectinfo.attlist" text "INCLUDE" nil) ("local.objectdata.attrib" text "" nil) ("objectdata.attrib" text "
-	--EntityRef: Name of an external entity containing the content
-	of the object data--
-	EntityRef	ENTITY		#IMPLIED
-
-	--FileRef: Filename, qualified by a pathname if desired, 
-	designating the file containing the content of the object data--
-	FileRef 	CDATA		#IMPLIED
-
-	--Format: Notation of the element content, if any--
-	Format		(BMP| CGM-CHAR | CGM-BINARY | CGM-CLEAR | DITROFF | DVI
-		| EPS | EQN | FAX | GIF | GIF87a | GIF89a 
-		| JPG | JPEG | IGES | PCX
-		| PIC | PS | SGML | TBL | TEX | TIFF | WMF | WPG
-		| linespecific
-		)
-					#IMPLIED
-
-	--SrcCredit: Information about the source of the image--
-	SrcCredit	CDATA		#IMPLIED
-
-	" nil) ("videodata.module" text "INCLUDE" nil) ("local.videodata.attrib" text "" nil) ("videodata.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("videodata.element" text "INCLUDE" nil) ("videodata.attlist" text "INCLUDE" nil) ("audiodata.module" text "INCLUDE" nil) ("local.audiodata.attrib" text "" nil) ("audiodata.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("audiodata.element" text "INCLUDE" nil) ("audiodata.attlist" text "INCLUDE" nil) ("imagedata.module" text "INCLUDE" nil) ("local.imagedata.attrib" text "" nil) ("imagedata.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("imagedata.element" text "INCLUDE" nil) ("imagedata.attlist" text "INCLUDE" nil) ("caption.module" text "INCLUDE" nil) ("local.caption.attrib" text "" nil) ("caption.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("caption.element" text "INCLUDE" nil) ("caption.attlist" text "INCLUDE" nil) ("mediaobjectco.module" text "INCLUDE" nil) ("local.mediaobjectco.attrib" text "" nil) ("mediaobjectco.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("mediaobjectco.element" text "INCLUDE" nil) ("mediaobjectco.attlist" text "INCLUDE" nil) ("imageobjectco.module" text "INCLUDE" nil) ("local.imageobjectco.attrib" text "" nil) ("imageobjectco.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("imageobjectco.element" text "INCLUDE" nil) ("imageobjectco.attlist" text "INCLUDE" nil) ("equation.module" text "INCLUDE" nil) ("local.equation.attrib" text "" nil) ("equation.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("equation.element" text "INCLUDE" nil) ("equation.attlist" text "INCLUDE" nil) ("informalequation.module" text "INCLUDE" nil) ("local.informalequation.attrib" text "" nil) ("informalequation.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("informalequation.element" text "INCLUDE" nil) ("informalequation.attlist" text "INCLUDE" nil) ("inlineequation.module" text "INCLUDE" nil) ("local.inlineequation.attrib" text "" nil) ("inlineequation.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("inlineequation.element" text "INCLUDE" nil) ("inlineequation.attlist" text "INCLUDE" nil) ("alt.module" text "INCLUDE" nil) ("local.alt.attrib" text "" nil) ("alt.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("alt.element" text "INCLUDE" nil) ("alt.attlist" text "INCLUDE" nil) ("table.module" text "INCLUDE" nil) ("tables.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("bodyatt" text "Label		CDATA		#IMPLIED" nil) ("secur" text "Id		ID		#IMPLIED
-	Lang		CDATA		#IMPLIED
-	Remap		CDATA		#IMPLIED
-	--Role is included explicitly on each element--
-	XRefLabel	CDATA		#IMPLIED
-	RevisionFlag	(Changed
-			|Added
-			|Deleted
-			|Off)		#IMPLIED
-	Arch		CDATA		#IMPLIED
-	Conformance	NMTOKENS	#IMPLIED
-	OS		CDATA		#IMPLIED
-	Revision	CDATA		#IMPLIED
-	UserLevel	CDATA		#IMPLIED
-	Vendor		CDATA		#IMPLIED
-	
-	
-	Role		CDATA		#IMPLIED" nil) ("tbl.table.name" text "Table" nil) ("tbl.table.mdl" text "((Title, TitleAbbrev?),
-          (IndexTerm )*,
-          (Graphic+|MediaObject+|TGroup+))" nil) ("tbl.table.excep" text "-(InformalTable|Equation|Example|Figure|Table )" nil) ("tbl.row.excep" text "" nil) ("tbl.entry.mdl" text "((CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 
-		|FormalPara|Para|SimPara 		|Graphic|MediaObject
-		)+ | (#PCDATA
-		|FootnoteRef|XRef 	|Abbrev|Acronym|Citation|CiteRefEntry|CiteTitle|Emphasis
-		|FirstTerm|ForeignPhrase|GlossTerm|Footnote|Phrase
-		|Quote|Trademark|WordAsWord 
-		|Link|OLink|ULink 	|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		|Anchor 	|Author|AuthorInitials|CorpAuthor|ModeSpec|OtherCredit
-		|ProductName|ProductNumber|RevHistory
-		
-		|Comment|Subscript|Superscript 	|InlineGraphic|InlineMediaObject|InlineEquation 
-		|Synopsis|CmdSynopsis|FuncSynopsis 
-		|IndexTerm 
-		)+)" nil) ("tbl.entry.excep" text "" nil) ("tbl.entrytbl.excep" text "-(EntryTbl)" nil) ("calstbls" text ("-//USA-DOD//DTD Table Model 951010//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("yesorno" text "NUMBER" nil) ("titles" text "title?" nil) ("paracon" text "#PCDATA" nil) ("tbl.table-titles.mdl" text "title?," nil) ("tbl.table-main.mdl" text "(tgroup+|graphic+)" nil) ("tbl.table.att" text "
-    tabstyle    NMTOKEN         #IMPLIED
-    tocentry    NUMBER       #IMPLIED
-    shortentry  NUMBER       #IMPLIED
-    orient      (port|land)     #IMPLIED
-    pgwide      NUMBER       #IMPLIED " nil) ("tbl.tgroup.mdl" text "colspec*,spanspec*,thead?,tfoot?,tbody" nil) ("tbl.tgroup.att" text "
-    tgroupstyle NMTOKEN         #IMPLIED " nil) ("tbl.hdft.name" text "(thead|tfoot)" nil) ("tbl.hdft.mdl" text "colspec*,row+" nil) ("tbl.hdft.excep" text "-(entrytbl)" nil) ("tbl.row.mdl" text "(entry|entrytbl)+" nil) ("tbl.entrytbl.mdl" text "colspec*,spanspec*,thead?,tbody" nil) ("informaltable.module" text "INCLUDE" nil) ("local.informaltable.attrib" text "" nil) ("informaltable.element" text "INCLUDE" nil) ("informaltable.attlist" text "INCLUDE" nil) ("synopsis.module" text "INCLUDE" nil) ("local.synopsis.attrib" text "" nil) ("synopsis.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("synopsis.element" text "INCLUDE" nil) ("synopsis.attlist" text "INCLUDE" nil) ("cmdsynopsis.content.module" text "INCLUDE" nil) ("cmdsynopsis.module" text "INCLUDE" nil) ("local.cmdsynopsis.attrib" text "" nil) ("cmdsynopsis.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("cmdsynopsis.element" text "INCLUDE" nil) ("cmdsynopsis.attlist" text "INCLUDE" nil) ("arg.module" text "INCLUDE" nil) ("local.arg.attrib" text "" nil) ("arg.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("arg.element" text "INCLUDE" nil) ("arg.attlist" text "INCLUDE" nil) ("group.module" text "INCLUDE" nil) ("local.group.attrib" text "" nil) ("group.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("group.element" text "INCLUDE" nil) ("group.attlist" text "INCLUDE" nil) ("sbr.module" text "INCLUDE" nil) ("local.sbr.attrib" text "" nil) ("sbr.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("sbr.element" text "INCLUDE" nil) ("sbr.attlist" text "INCLUDE" nil) ("synopfragmentref.module" text "INCLUDE" nil) ("local.synopfragmentref.attrib" text "" nil) ("synopfragmentref.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("synopfragmentref.element" text "INCLUDE" nil) ("synopfragmentref.attlist" text "INCLUDE" nil) ("synopfragment.module" text "INCLUDE" nil) ("local.synopfragment.attrib" text "" nil) ("synopfragment.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("synopfragment.element" text "INCLUDE" nil) ("synopfragment.attlist" text "INCLUDE" nil) ("funcsynopsis.content.module" text "INCLUDE" nil) ("funcsynopsis.module" text "INCLUDE" nil) ("local.funcsynopsis.attrib" text "" nil) ("funcsynopsis.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("funcsynopsis.element" text "INCLUDE" nil) ("funcsynopsis.attlist" text "INCLUDE" nil) ("funcsynopsisinfo.module" text "INCLUDE" nil) ("local.funcsynopsisinfo.attrib" text "" nil) ("funcsynopsisinfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("funcsynopsisinfo.element" text "INCLUDE" nil) ("funcsynopsisinfo.attlist" text "INCLUDE" nil) ("funcprototype.module" text "INCLUDE" nil) ("local.funcprototype.attrib" text "" nil) ("funcprototype.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("funcprototype.element" text "INCLUDE" nil) ("funcprototype.attlist" text "INCLUDE" nil) ("funcdef.module" text "INCLUDE" nil) ("local.funcdef.attrib" text "" nil) ("funcdef.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("funcdef.element" text "INCLUDE" nil) ("funcdef.attlist" text "INCLUDE" nil) ("void.module" text "INCLUDE" nil) ("local.void.attrib" text "" nil) ("void.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("void.element" text "INCLUDE" nil) ("void.attlist" text "INCLUDE" nil) ("varargs.module" text "INCLUDE" nil) ("local.varargs.attrib" text "" nil) ("varargs.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("varargs.element" text "INCLUDE" nil) ("varargs.attlist" text "INCLUDE" nil) ("paramdef.module" text "INCLUDE" nil) ("local.paramdef.attrib" text "" nil) ("paramdef.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("paramdef.element" text "INCLUDE" nil) ("paramdef.attlist" text "INCLUDE" nil) ("funcparams.module" text "INCLUDE" nil) ("local.funcparams.attrib" text "" nil) ("funcparams.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("funcparams.element" text "INCLUDE" nil) ("funcparams.attlist" text "INCLUDE" nil) ("docinfo.content.module" text "INCLUDE" nil) ("ackno.module" text "INCLUDE" nil) ("local.ackno.attrib" text "" nil) ("ackno.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("ackno.element" text "INCLUDE" nil) ("ackno.attlist" text "INCLUDE" nil) ("address.content.module" text "INCLUDE" nil) ("address.module" text "INCLUDE" nil) ("local.address.attrib" text "" nil) ("address.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("address.element" text "INCLUDE" nil) ("address.attlist" text "INCLUDE" nil) ("street.module" text "INCLUDE" nil) ("local.street.attrib" text "" nil) ("street.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("street.element" text "INCLUDE" nil) ("street.attlist" text "INCLUDE" nil) ("pob.module" text "INCLUDE" nil) ("local.pob.attrib" text "" nil) ("pob.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("pob.element" text "INCLUDE" nil) ("pob.attlist" text "INCLUDE" nil) ("postcode.module" text "INCLUDE" nil) ("local.postcode.attrib" text "" nil) ("postcode.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("postcode.element" text "INCLUDE" nil) ("postcode.attlist" text "INCLUDE" nil) ("city.module" text "INCLUDE" nil) ("local.city.attrib" text "" nil) ("city.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("city.element" text "INCLUDE" nil) ("city.attlist" text "INCLUDE" nil) ("state.module" text "INCLUDE" nil) ("local.state.attrib" text "" nil) ("state.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("state.element" text "INCLUDE" nil) ("state.attlist" text "INCLUDE" nil) ("country.module" text "INCLUDE" nil) ("local.country.attrib" text "" nil) ("country.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("country.element" text "INCLUDE" nil) ("country.attlist" text "INCLUDE" nil) ("phone.module" text "INCLUDE" nil) ("local.phone.attrib" text "" nil) ("phone.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("phone.element" text "INCLUDE" nil) ("phone.attlist" text "INCLUDE" nil) ("fax.module" text "INCLUDE" nil) ("local.fax.attrib" text "" nil) ("fax.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("fax.element" text "INCLUDE" nil) ("fax.attlist" text "INCLUDE" nil) ("otheraddr.module" text "INCLUDE" nil) ("local.otheraddr.attrib" text "" nil) ("otheraddr.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("otheraddr.element" text "INCLUDE" nil) ("otheraddr.attlist" text "INCLUDE" nil) ("affiliation.content.module" text "INCLUDE" nil) ("affiliation.module" text "INCLUDE" nil) ("local.affiliation.attrib" text "" nil) ("affiliation.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("affiliation.element" text "INCLUDE" nil) ("affiliation.attlist" text "INCLUDE" nil) ("shortaffil.module" text "INCLUDE" nil) ("local.shortaffil.attrib" text "" nil) ("shortaffil.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("shortaffil.element" text "INCLUDE" nil) ("shortaffil.attlist" text "INCLUDE" nil) ("jobtitle.module" text "INCLUDE" nil) ("local.jobtitle.attrib" text "" nil) ("jobtitle.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("jobtitle.element" text "INCLUDE" nil) ("jobtitle.attlist" text "INCLUDE" nil) ("orgdiv.module" text "INCLUDE" nil) ("local.orgdiv.attrib" text "" nil) ("orgdiv.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("orgdiv.element" text "INCLUDE" nil) ("orgdiv.attlist" text "INCLUDE" nil) ("artpagenums.module" text "INCLUDE" nil) ("local.artpagenums.attrib" text "" nil) ("argpagenums.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("artpagenums.element" text "INCLUDE" nil) ("artpagenums.attlist" text "INCLUDE" nil) ("author.module" text "INCLUDE" nil) ("local.author.attrib" text "" nil) ("author.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("author.element" text "INCLUDE" nil) ("author.attlist" text "INCLUDE" nil) ("authorgroup.content.module" text "INCLUDE" nil) ("authorgroup.module" text "INCLUDE" nil) ("local.authorgroup.attrib" text "" nil) ("authorgroup.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("authorgroup.element" text "INCLUDE" nil) ("authorgroup.attlist" text "INCLUDE" nil) ("collab.content.module" text "INCLUDE" nil) ("collab.module" text "INCLUDE" nil) ("local.collab.attrib" text "" nil) ("collab.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("collab.element" text "INCLUDE" nil) ("collab.attlist" text "INCLUDE" nil) ("collabname.module" text "INCLUDE" nil) ("local.collabname.attrib" text "" nil) ("collabname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("collabname.element" text "INCLUDE" nil) ("collabname.attlist" text "INCLUDE" nil) ("authorinitials.module" text "INCLUDE" nil) ("local.authorinitials.attrib" text "" nil) ("authorinitials.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("authorinitials.element" text "INCLUDE" nil) ("authorinitials.attlist" text "INCLUDE" nil) ("confgroup.content.module" text "INCLUDE" nil) ("confgroup.module" text "INCLUDE" nil) ("local.confgroup.attrib" text "" nil) ("confgroup.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("confgroup.element" text "INCLUDE" nil) ("confgroup.attlist" text "INCLUDE" nil) ("confdates.module" text "INCLUDE" nil) ("local.confdates.attrib" text "" nil) ("confdates.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("confdates.element" text "INCLUDE" nil) ("confdates.attlist" text "INCLUDE" nil) ("conftitle.module" text "INCLUDE" nil) ("local.conftitle.attrib" text "" nil) ("conftitle.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("conftitle.element" text "INCLUDE" nil) ("conftitle.attlist" text "INCLUDE" nil) ("confnum.module" text "INCLUDE" nil) ("local.confnum.attrib" text "" nil) ("confnum.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("confnum.element" text "INCLUDE" nil) ("confnum.attlist" text "INCLUDE" nil) ("confsponsor.module" text "INCLUDE" nil) ("local.confsponsor.attrib" text "" nil) ("confsponsor.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("confsponsor.element" text "INCLUDE" nil) ("confsponsor.attlist" text "INCLUDE" nil) ("contractnum.module" text "INCLUDE" nil) ("local.contractnum.attrib" text "" nil) ("contractnum.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("contractnum.element" text "INCLUDE" nil) ("contractnum.attlist" text "INCLUDE" nil) ("contractsponsor.module" text "INCLUDE" nil) ("local.contractsponsor.attrib" text "" nil) ("contractsponsor.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("contractsponsor.element" text "INCLUDE" nil) ("contractsponsor.attlist" text "INCLUDE" nil) ("copyright.content.module" text "INCLUDE" nil) ("copyright.module" text "INCLUDE" nil) ("local.copyright.attrib" text "" nil) ("copyright.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("copyright.element" text "INCLUDE" nil) ("copyright.attlist" text "INCLUDE" nil) ("year.module" text "INCLUDE" nil) ("local.year.attrib" text "" nil) ("year.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("year.element" text "INCLUDE" nil) ("year.attlist" text "INCLUDE" nil) ("holder.module" text "INCLUDE" nil) ("local.holder.attrib" text "" nil) ("holder.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("holder.element" text "INCLUDE" nil) ("holder.attlist" text "INCLUDE" nil) ("corpauthor.module" text "INCLUDE" nil) ("local.corpauthor.attrib" text "" nil) ("corpauthor.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("corpauthor.element" text "INCLUDE" nil) ("corpauthor.attlist" text "INCLUDE" nil) ("corpname.module" text "INCLUDE" nil) ("local.corpname.attrib" text "" nil) ("corpname.element" text "INCLUDE" nil) ("corpname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("corpname.attlist" text "INCLUDE" nil) ("date.module" text "INCLUDE" nil) ("local.date.attrib" text "" nil) ("date.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("date.element" text "INCLUDE" nil) ("date.attlist" text "INCLUDE" nil) ("edition.module" text "INCLUDE" nil) ("local.edition.attrib" text "" nil) ("edition.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("edition.element" text "INCLUDE" nil) ("edition.attlist" text "INCLUDE" nil) ("editor.module" text "INCLUDE" nil) ("local.editor.attrib" text "" nil) ("editor.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("editor.element" text "INCLUDE" nil) ("editor.attlist" text "INCLUDE" nil) ("isbn.module" text "INCLUDE" nil) ("local.isbn.attrib" text "" nil) ("isbn.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("isbn.element" text "INCLUDE" nil) ("isbn.attlist" text "INCLUDE" nil) ("issn.module" text "INCLUDE" nil) ("local.issn.attrib" text "" nil) ("issn.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("issn.element" text "INCLUDE" nil) ("issn.attlist" text "INCLUDE" nil) ("invpartnumber.module" text "INCLUDE" nil) ("local.invpartnumber.attrib" text "" nil) ("invpartnumber.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("invpartnumber.element" text "INCLUDE" nil) ("invpartnumber.attlist" text "INCLUDE" nil) ("issuenum.module" text "INCLUDE" nil) ("local.issuenum.attrib" text "" nil) ("issuenum.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("issuenum.element" text "INCLUDE" nil) ("issuenum.attlist" text "INCLUDE" nil) ("legalnotice.module" text "INCLUDE" nil) ("local.legalnotice.attrib" text "" nil) ("legalnotice.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("legalnotice.element" text "INCLUDE" nil) ("legalnotice.attlist" text "INCLUDE" nil) ("modespec.module" text "INCLUDE" nil) ("local.modespec.attrib" text "" nil) ("modespec.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("modespec.element" text "INCLUDE" nil) ("modespec.attlist" text "INCLUDE" nil) ("orgname.module" text "INCLUDE" nil) ("local.orgname.attrib" text "" nil) ("orgname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("orgname.element" text "INCLUDE" nil) ("orgname.attlist" text "INCLUDE" nil) ("othercredit.module" text "INCLUDE" nil) ("local.othercredit.attrib" text "" nil) ("othercredit.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("othercredit.element" text "INCLUDE" nil) ("othercredit.attlist" text "INCLUDE" nil) ("pagenums.module" text "INCLUDE" nil) ("local.pagenums.attrib" text "" nil) ("pagenums.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("pagenums.element" text "INCLUDE" nil) ("pagenums.attlist" text "INCLUDE" nil) ("person.ident.module" text "INCLUDE" nil) ("contrib.module" text "INCLUDE" nil) ("local.contrib.attrib" text "" nil) ("contrib.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("contrib.element" text "INCLUDE" nil) ("contrib.attlist" text "INCLUDE" nil) ("firstname.module" text "INCLUDE" nil) ("local.firstname.attrib" text "" nil) ("firstname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("firstname.element" text "INCLUDE" nil) ("firstname.attlist" text "INCLUDE" nil) ("honorific.module" text "INCLUDE" nil) ("local.honorific.attrib" text "" nil) ("honorific.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("honorific.element" text "INCLUDE" nil) ("honorific.attlist" text "INCLUDE" nil) ("lineage.module" text "INCLUDE" nil) ("local.lineage.attrib" text "" nil) ("lineage.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("lineage.element" text "INCLUDE" nil) ("lineage.attlist" text "INCLUDE" nil) ("othername.module" text "INCLUDE" nil) ("local.othername.attrib" text "" nil) ("othername.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("othername.element" text "INCLUDE" nil) ("othername.attlist" text "INCLUDE" nil) ("surname.module" text "INCLUDE" nil) ("local.surname.attrib" text "" nil) ("surname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("surname.element" text "INCLUDE" nil) ("surname.attlist" text "INCLUDE" nil) ("printhistory.module" text "INCLUDE" nil) ("local.printhistory.attrib" text "" nil) ("printhistory.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("printhistory.element" text "INCLUDE" nil) ("printhistory.attlist" text "INCLUDE" nil) ("productname.module" text "INCLUDE" nil) ("local.productname.attrib" text "" nil) ("productname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("productname.element" text "INCLUDE" nil) ("productname.attlist" text "INCLUDE" nil) ("productnumber.module" text "INCLUDE" nil) ("local.productnumber.attrib" text "" nil) ("productnumber.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("productnumber.element" text "INCLUDE" nil) ("productnumber.attlist" text "INCLUDE" nil) ("pubdate.module" text "INCLUDE" nil) ("local.pubdate.attrib" text "" nil) ("pubdate.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("pubdate.element" text "INCLUDE" nil) ("pubdate.attlist" text "INCLUDE" nil) ("publisher.content.module" text "INCLUDE" nil) ("publisher.module" text "INCLUDE" nil) ("local.publisher.attrib" text "" nil) ("publisher.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("publisher.element" text "INCLUDE" nil) ("publisher.attlist" text "INCLUDE" nil) ("publishername.module" text "INCLUDE" nil) ("local.publishername.attrib" text "" nil) ("publishername.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("publishername.element" text "INCLUDE" nil) ("publishername.attlist" text "INCLUDE" nil) ("pubsnumber.module" text "INCLUDE" nil) ("local.pubsnumber.attrib" text "" nil) ("pubsnumber.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("pubsnumber.element" text "INCLUDE" nil) ("pubsnumber.attlist" text "INCLUDE" nil) ("releaseinfo.module" text "INCLUDE" nil) ("local.releaseinfo.attrib" text "" nil) ("releaseinfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("releaseinfo.element" text "INCLUDE" nil) ("releaseinfo.attlist" text "INCLUDE" nil) ("revhistory.content.module" text "INCLUDE" nil) ("revhistory.module" text "INCLUDE" nil) ("local.revhistory.attrib" text "" nil) ("revhistory.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("revhistory.element" text "INCLUDE" nil) ("revhistory.attlist" text "INCLUDE" nil) ("revision.module" text "INCLUDE" nil) ("local.revision.attrib" text "" nil) ("revision.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("revision.element" text "INCLUDE" nil) ("revision.attlist" text "INCLUDE" nil) ("revnumber.module" text "INCLUDE" nil) ("local.revnumber.attrib" text "" nil) ("revnumber.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("revnumber.element" text "INCLUDE" nil) ("revnumber.attlist" text "INCLUDE" nil) ("revremark.module" text "INCLUDE" nil) ("local.revremark.attrib" text "" nil) ("revremark.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("revremark.element" text "INCLUDE" nil) ("revremark.attlist" text "INCLUDE" nil) ("seriesvolnums.module" text "INCLUDE" nil) ("local.seriesvolnums.attrib" text "" nil) ("seriesvolnums.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("seriesvolnums.element" text "INCLUDE" nil) ("seriesvolnums.attlist" text "INCLUDE" nil) ("volumenum.module" text "INCLUDE" nil) ("local.volumenum.attrib" text "" nil) ("volumenum.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("volumenum.element" text "INCLUDE" nil) ("volumenum.attlist" text "INCLUDE" nil) ("accel.module" text "INCLUDE" nil) ("local.accel.attrib" text "" nil) ("accel.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("accel.element" text "INCLUDE" nil) ("accel.attlist" text "INCLUDE" nil) ("action.module" text "INCLUDE" nil) ("local.action.attrib" text "" nil) ("action.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("action.element" text "INCLUDE" nil) ("action.attlist" text "INCLUDE" nil) ("application.module" text "INCLUDE" nil) ("local.application.attrib" text "" nil) ("application.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("application.element" text "INCLUDE" nil) ("application.attlist" text "INCLUDE" nil) ("classname.module" text "INCLUDE" nil) ("local.classname.attrib" text "" nil) ("classname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("classname.element" text "INCLUDE" nil) ("classname.attlist" text "INCLUDE" nil) ("co.module" text "INCLUDE" nil) ("local.co.attrib" text "" nil) ("co.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("co.element" text "INCLUDE" nil) ("co.attlist" text "INCLUDE" nil) ("command.module" text "INCLUDE" nil) ("local.command.attrib" text "" nil) ("command.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("command.element" text "INCLUDE" nil) ("command.attlist" text "INCLUDE" nil) ("computeroutput.module" text "INCLUDE" nil) ("local.computeroutput.attrib" text "" nil) ("computeroutput.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("computeroutput.element" text "INCLUDE" nil) ("computeroutput.attlist" text "INCLUDE" nil) ("database.module" text "INCLUDE" nil) ("local.database.attrib" text "" nil) ("database.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("database.element" text "INCLUDE" nil) ("database.attlist" text "INCLUDE" nil) ("email.module" text "INCLUDE" nil) ("local.email.attrib" text "" nil) ("email.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("email.element" text "INCLUDE" nil) ("email.attlist" text "INCLUDE" nil) ("envar.module" text "INCLUDE" nil) ("local.envar.attrib" text "" nil) ("envar.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("envar.element" text "INCLUDE" nil) ("envar.attlist" text "INCLUDE" nil) ("errorcode.module" text "INCLUDE" nil) ("local.errorcode.attrib" text "" nil) ("errorcode.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("errorcode.element" text "INCLUDE" nil) ("errorcode.attlist" text "INCLUDE" nil) ("errorname.module" text "INCLUDE" nil) ("local.errorname.attrib" text "" nil) ("errorname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("errorname.element" text "INCLUDE" nil) ("errorname.attlist" text "INCLUDE" nil) ("errortype.module" text "INCLUDE" nil) ("local.errortype.attrib" text "" nil) ("errortype.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("errortype.element" text "INCLUDE" nil) ("errortype.attlist" text "INCLUDE" nil) ("filename.module" text "INCLUDE" nil) ("local.filename.attrib" text "" nil) ("filename.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("filename.element" text "INCLUDE" nil) ("filename.attlist" text "INCLUDE" nil) ("function.module" text "INCLUDE" nil) ("local.function.attrib" text "" nil) ("function.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("function.element" text "INCLUDE" nil) ("function.attlist" text "INCLUDE" nil) ("guibutton.module" text "INCLUDE" nil) ("local.guibutton.attrib" text "" nil) ("guibutton.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("guibutton.element" text "INCLUDE" nil) ("guibutton.attlist" text "INCLUDE" nil) ("guiicon.module" text "INCLUDE" nil) ("local.guiicon.attrib" text "" nil) ("guiicon.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("guiicon.element" text "INCLUDE" nil) ("guiicon.attlist" text "INCLUDE" nil) ("guilabel.module" text "INCLUDE" nil) ("local.guilabel.attrib" text "" nil) ("guilabel.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("guilabel.element" text "INCLUDE" nil) ("guilabel.attlist" text "INCLUDE" nil) ("guimenu.module" text "INCLUDE" nil) ("local.guimenu.attrib" text "" nil) ("guimenu.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("guimenu.element" text "INCLUDE" nil) ("guimenu.attlist" text "INCLUDE" nil) ("guimenuitem.module" text "INCLUDE" nil) ("local.guimenuitem.attrib" text "" nil) ("guimenuitem.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("guimenuitem.element" text "INCLUDE" nil) ("guimenuitem.attlist" text "INCLUDE" nil) ("guisubmenu.module" text "INCLUDE" nil) ("local.guisubmenu.attrib" text "" nil) ("guisubmenu.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("guisubmenu.element" text "INCLUDE" nil) ("guisubmenu.attlist" text "INCLUDE" nil) ("hardware.module" text "INCLUDE" nil) ("local.hardware.attrib" text "" nil) ("hardware.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("hardware.element" text "INCLUDE" nil) ("hardware.attlist" text "INCLUDE" nil) ("interface.module" text "INCLUDE" nil) ("local.interface.attrib" text "" nil) ("interface.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("interface.element" text "INCLUDE" nil) ("interface.attlist" text "INCLUDE" nil) ("interfacedefinition.module" text "INCLUDE" nil) ("local.interfacedefinition.attrib" text "" nil) ("interfacedefinition.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("interfacedefinition.element" text "INCLUDE" nil) ("interfacedefinition.attlist" text "INCLUDE" nil) ("keycap.module" text "INCLUDE" nil) ("local.keycap.attrib" text "" nil) ("keycap.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("keycap.element" text "INCLUDE" nil) ("keycap.attlist" text "INCLUDE" nil) ("keycode.module" text "INCLUDE" nil) ("local.keycode.attrib" text "" nil) ("keycode.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("keycode.element" text "INCLUDE" nil) ("keycode.attlist" text "INCLUDE" nil) ("keycombo.module" text "INCLUDE" nil) ("local.keycombo.attrib" text "" nil) ("keycombo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("keycombo.element" text "INCLUDE" nil) ("keycombo.attlist" text "INCLUDE" nil) ("keysym.module" text "INCLUDE" nil) ("local.keysym.attrib" text "" nil) ("keysysm.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("keysym.element" text "INCLUDE" nil) ("keysym.attlist" text "INCLUDE" nil) ("lineannotation.module" text "INCLUDE" nil) ("local.lineannotation.attrib" text "" nil) ("lineannotation.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("lineannotation.element" text "INCLUDE" nil) ("lineannotation.attlist" text "INCLUDE" nil) ("literal.module" text "INCLUDE" nil) ("local.literal.attrib" text "" nil) ("literal.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("literal.element" text "INCLUDE" nil) ("literal.attlist" text "INCLUDE" nil) ("constant.module" text "INCLUDE" nil) ("local.constant.attrib" text "" nil) ("constant.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("constant.element" text "INCLUDE" nil) ("constant.attlist" text "INCLUDE" nil) ("varname.module" text "INCLUDE" nil) ("local.varname.attrib" text "" nil) ("varname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("varname.element" text "INCLUDE" nil) ("varname.attlist" text "INCLUDE" nil) ("markup.module" text "INCLUDE" nil) ("local.markup.attrib" text "" nil) ("markup.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("markup.element" text "INCLUDE" nil) ("markup.attlist" text "INCLUDE" nil) ("medialabel.module" text "INCLUDE" nil) ("local.medialabel.attrib" text "" nil) ("medialabel.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("medialabel.element" text "INCLUDE" nil) ("medialabel.attlist" text "INCLUDE" nil) ("menuchoice.content.module" text "INCLUDE" nil) ("menuchoice.module" text "INCLUDE" nil) ("local.menuchoice.attrib" text "" nil) ("menuchoice.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("menuchoice.element" text "INCLUDE" nil) ("menuchoice.attlist" text "INCLUDE" nil) ("shortcut.module" text "INCLUDE" nil) ("local.shortcut.attrib" text "" nil) ("shortcut.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("shortcut.element" text "INCLUDE" nil) ("shortcut.attlist" text "INCLUDE" nil) ("mousebutton.module" text "INCLUDE" nil) ("local.mousebutton.attrib" text "" nil) ("mousebutton.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("mousebutton.element" text "INCLUDE" nil) ("mousebutton.attlist" text "INCLUDE" nil) ("msgtext.module" text "INCLUDE" nil) ("local.msgtext.attrib" text "" nil) ("msgtext.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("msgtext.element" text "INCLUDE" nil) ("msgtext.attlist" text "INCLUDE" nil) ("option.module" text "INCLUDE" nil) ("local.option.attrib" text "" nil) ("option.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("option.element" text "INCLUDE" nil) ("option.attlist" text "INCLUDE" nil) ("optional.module" text "INCLUDE" nil) ("local.optional.attrib" text "" nil) ("optional.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("optional.element" text "INCLUDE" nil) ("optional.attlist" text "INCLUDE" nil) ("parameter.module" text "INCLUDE" nil) ("local.parameter.attrib" text "" nil) ("parameter.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("parameter.element" text "INCLUDE" nil) ("parameter.attlist" text "INCLUDE" nil) ("prompt.module" text "INCLUDE" nil) ("local.prompt.attrib" text "" nil) ("prompt.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("prompt.element" text "INCLUDE" nil) ("prompt.attlist" text "INCLUDE" nil) ("property.module" text "INCLUDE" nil) ("local.property.attrib" text "" nil) ("property.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("property.element" text "INCLUDE" nil) ("property.attlist" text "INCLUDE" nil) ("replaceable.module" text "INCLUDE" nil) ("local.replaceable.attrib" text "" nil) ("replaceable.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("replaceable.element" text "INCLUDE" nil) ("replaceable.attlist" text "INCLUDE" nil) ("returnvalue.module" text "INCLUDE" nil) ("local.returnvalue.attrib" text "" nil) ("returnvalue.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("returnvalue.element" text "INCLUDE" nil) ("returnvalue.attlist" text "INCLUDE" nil) ("sgmltag.module" text "INCLUDE" nil) ("local.sgmltag.attrib" text "" nil) ("sgmltag.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("sgmltag.element" text "INCLUDE" nil) ("sgmltag.attlist" text "INCLUDE" nil) ("structfield.module" text "INCLUDE" nil) ("local.structfield.attrib" text "" nil) ("structfield.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("structfield.element" text "INCLUDE" nil) ("structfield.attlist" text "INCLUDE" nil) ("structname.module" text "INCLUDE" nil) ("local.structname.attrib" text "" nil) ("structname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("structname.element" text "INCLUDE" nil) ("structname.attlist" text "INCLUDE" nil) ("symbol.module" text "INCLUDE" nil) ("local.symbol.attrib" text "" nil) ("symbol.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("symbol.element" text "INCLUDE" nil) ("symbol.attlist" text "INCLUDE" nil) ("systemitem.module" text "INCLUDE" nil) ("local.systemitem.attrib" text "" nil) ("systemitem.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("systemitem.element" text "INCLUDE" nil) ("systemitem.attlist" text "INCLUDE" nil) ("token.module" text "INCLUDE" nil) ("local.token.attrib" text "" nil) ("token.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("token.element" text "INCLUDE" nil) ("token.attlist" text "INCLUDE" nil) ("type.module" text "INCLUDE" nil) ("local.type.attrib" text "" nil) ("type.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("type.element" text "INCLUDE" nil) ("type.attlist" text "INCLUDE" nil) ("userinput.module" text "INCLUDE" nil) ("local.userinput.attrib" text "" nil) ("userinput.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("userinput.element" text "INCLUDE" nil) ("userinput.attlist" text "INCLUDE" nil) ("abbrev.module" text "INCLUDE" nil) ("local.abbrev.attrib" text "" nil) ("abbrev.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("abbrev.element" text "INCLUDE" nil) ("abbrev.attlist" text "INCLUDE" nil) ("acronym.module" text "INCLUDE" nil) ("local.acronym.attrib" text "" nil) ("acronym.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("acronym.element" text "INCLUDE" nil) ("acronym.attlist" text "INCLUDE" nil) ("citation.module" text "INCLUDE" nil) ("local.citation.attrib" text "" nil) ("citation.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("citation.element" text "INCLUDE" nil) ("citation.attlist" text "INCLUDE" nil) ("citerefentry.module" text "INCLUDE" nil) ("local.citerefentry.attrib" text "" nil) ("citerefentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("citerefentry.element" text "INCLUDE" nil) ("citerefentry.attlist" text "INCLUDE" nil) ("refentrytitle.module" text "INCLUDE" nil) ("local.refentrytitle.attrib" text "" nil) ("refentrytitle.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refentrytitle.element" text "INCLUDE" nil) ("refentrytitle.attlist" text "INCLUDE" nil) ("manvolnum.module" text "INCLUDE" nil) ("local.manvolnum.attrib" text "" nil) ("namvolnum.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("manvolnum.element" text "INCLUDE" nil) ("manvolnum.attlist" text "INCLUDE" nil) ("citetitle.module" text "INCLUDE" nil) ("local.citetitle.attrib" text "" nil) ("citetitle.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("citetitle.element" text "INCLUDE" nil) ("citetitle.attlist" text "INCLUDE" nil) ("emphasis.module" text "INCLUDE" nil) ("local.emphasis.attrib" text "" nil) ("emphasis.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("emphasis.element" text "INCLUDE" nil) ("emphasis.attlist" text "INCLUDE" nil) ("firstterm.module" text "INCLUDE" nil) ("local.firstterm.attrib" text "" nil) ("firstterm.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("firstterm.element" text "INCLUDE" nil) ("firstterm.attlist" text "INCLUDE" nil) ("foreignphrase.module" text "INCLUDE" nil) ("local.foreignphrase.attrib" text "" nil) ("foreignphrase.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("foreignphrase.element" text "INCLUDE" nil) ("foreignphrase.attlist" text "INCLUDE" nil) ("glossterm.module" text "INCLUDE" nil) ("local.glossterm.attrib" text "" nil) ("glossterm.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("glossterm.element" text "INCLUDE" nil) ("glossterm.attlist" text "INCLUDE" nil) ("phrase.module" text "INCLUDE" nil) ("local.phrase.attrib" text "" nil) ("phrase.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("phrase.element" text "INCLUDE" nil) ("phrase.attlist" text "INCLUDE" nil) ("quote.module" text "INCLUDE" nil) ("local.quote.attrib" text "" nil) ("quote.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("quote.element" text "INCLUDE" nil) ("quote.attlist" text "INCLUDE" nil) ("ssscript.module" text "INCLUDE" nil) ("local.ssscript.attrib" text "" nil) ("ssscript.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("ssscript.elements" text "INCLUDE" nil) ("ssscript.attlists" text "INCLUDE" nil) ("trademark.module" text "INCLUDE" nil) ("local.trademark.attrib" text "" nil) ("trademark.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("trademark.element" text "INCLUDE" nil) ("trademark.attlist" text "INCLUDE" nil) ("wordasword.module" text "INCLUDE" nil) ("local.wordasword.attrib" text "" nil) ("wordasword.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("wordasword.element" text "INCLUDE" nil) ("wordasword.attlist" text "INCLUDE" nil) ("link.module" text "INCLUDE" nil) ("local.link.attrib" text "" nil) ("link.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("link.element" text "INCLUDE" nil) ("link.attlist" text "INCLUDE" nil) ("olink.module" text "INCLUDE" nil) ("local.olink.attrib" text "" nil) ("olink.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("olink.element" text "INCLUDE" nil) ("olink.attlist" text "INCLUDE" nil) ("ulink.module" text "INCLUDE" nil) ("local.ulink.attrib" text "" nil) ("ulink.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("ulink.element" text "INCLUDE" nil) ("ulink.attlist" text "INCLUDE" nil) ("footnoteref.module" text "INCLUDE" nil) ("local.footnoteref.attrib" text "" nil) ("footnoteref.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("footnoteref.element" text "INCLUDE" nil) ("footnoteref.attlist" text "INCLUDE" nil) ("xref.module" text "INCLUDE" nil) ("local.xref.attrib" text "" nil) ("xref.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("xref.element" text "INCLUDE" nil) ("xref.attlist" text "INCLUDE" nil) ("anchor.module" text "INCLUDE" nil) ("local.anchor.attrib" text "" nil) ("anchor.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("anchor.element" text "INCLUDE" nil) ("anchor.attlist" text "INCLUDE" nil) ("beginpage.module" text "INCLUDE" nil) ("local.beginpage.attrib" text "" nil) ("beginpage.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("beginpage.element" text "INCLUDE" nil) ("beginpage.attlist" text "INCLUDE" nil) ("indexterm.content.module" text "INCLUDE" nil) ("indexterm.module" text "INCLUDE" nil) ("local.indexterm.attrib" text "" nil) ("indexterm.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("indexterm.element" text "INCLUDE" nil) ("indexterm.attlist" text "INCLUDE" nil) ("primsecter.module" text "INCLUDE" nil) ("local.primsecter.attrib" text "" nil) ("primsecter.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("primsecter.elements" text "INCLUDE" nil) ("primsecter.attlists" text "INCLUDE" nil) ("containing.attlist" text "INCLUDE" nil) ("seeseealso.module" text "INCLUDE" nil) ("local.seeseealso.attrib" text "" nil) ("seeseealso.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("seeseealso.elements" text "INCLUDE" nil) ("seeseealso.attlists" text "INCLUDE" nil) ("intermod.redecl.module" text "IGNORE" nil) ("dbhier" text ("-//OASIS//ELEMENTS DocBook Document Hierarchy V3.1//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil) ("dbhier.redecl.module" text "IGNORE" nil) ("dbhier.redecl2.module" text "IGNORE" nil) ("local.appendix.class" text "" nil) ("appendix.class" text "Appendix " nil) ("local.article.class" text "" nil) ("article.class" text "Article " nil) ("local.book.class" text "" nil) ("book.class" text "Book " nil) ("local.chapter.class" text "" nil) ("chapter.class" text "Chapter " nil) ("local.index.class" text "" nil) ("index.class" text "Index|SetIndex " nil) ("local.otherinfo.class" text "" nil) ("otherinfo.class" text "DocInfo|Sect1Info|Sect2Info|Sect3Info
-				|Sect4Info|Sect5Info|RefSect1Info
-				|RefSect2Info|RefSect3Info|RefSynopsisDivInfo
-				" nil) ("local.refentry.class" text "" nil) ("refentry.class" text "RefEntry " nil) ("local.nav.class" text "" nil) ("nav.class" text "ToC|LoT|Index|Glossary|Bibliography 
-				" nil) ("local.divcomponent.mix" text "" nil) ("divcomponent.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 		|MsgSet|Procedure|Sidebar|QandASet 
-		|Anchor|BridgeHead|Comment|Highlights
-				|Abstract|AuthorBlurb|Epigraph
-		
-		|IndexTerm 
-		" nil) ("local.refcomponent.mix" text "" nil) ("refcomponent.mix" text "CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 		|MsgSet|Procedure|Sidebar|QandASet 
-		|Anchor|BridgeHead|Comment|Highlights
-				|Abstract|AuthorBlurb|Epigraph
-		
-		|IndexTerm 
-		" nil) ("local.indexdivcomponent.mix" text "" nil) ("indexdivcomponent.mix" text "ItemizedList|OrderedList|VariableList|SimpleList
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Anchor|Comment
-		|Link|OLink|ULink 
-		" nil) ("local.refname.char.mix" text "" nil) ("refname.char.mix" text "#PCDATA
-		|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		" nil) ("local.partcontent.mix" text "" nil) ("partcontent.mix" text "Appendix |Chapter |ToC|LoT|Index|Glossary|Bibliography 
-				|Article 
-		|Preface|RefEntry |Reference " nil) ("local.refinline.char.mix" text "" nil) ("refinline.char.mix" text "#PCDATA
-		|FootnoteRef|XRef 	|Abbrev|Acronym|Citation|CiteRefEntry|CiteTitle|Emphasis
-		|FirstTerm|ForeignPhrase|GlossTerm|Footnote|Phrase
-		|Quote|Trademark|WordAsWord 
-		|Link|OLink|ULink 	|Action|Application|ClassName|Command|ComputerOutput
-		|Database|Email|EnVar|ErrorCode|ErrorName|ErrorType|Filename
-		|Function|GUIButton|GUIIcon|GUILabel|GUIMenu|GUIMenuItem
-		|GUISubmenu|Hardware|Interface|InterfaceDefinition|KeyCap
-		|KeyCode|KeyCombo|KeySym|Literal|Constant|Markup|MediaLabel
-		|MenuChoice|MouseButton|MsgText|Option|Optional|Parameter
-		|Prompt|Property|Replaceable|ReturnValue|SGMLTag|StructField
-		|StructName|Symbol|SystemItem|Token|Type|UserInput|VarName
-		
-		|Anchor 	|Author|AuthorInitials|CorpAuthor|ModeSpec|OtherCredit
-		|ProductName|ProductNumber|RevHistory
-		
-		|Comment|Subscript|Superscript 
-		|IndexTerm 
-		" nil) ("local.refclass.char.mix" text "" nil) ("refclass.char.mix" text "#PCDATA
-		|Application
-		" nil) ("div.title.content" text "Title, Subtitle?, TitleAbbrev?" nil) ("bookcomponent.title.content" text "DocInfo?, Title, Subtitle?, TitleAbbrev?" nil) ("sect.title.content" text "Title, Subtitle?, TitleAbbrev?" nil) ("refsect.title.content" text "Title, Subtitle?, TitleAbbrev?" nil) ("bookcomponent.content" text "((CalloutList|GlossList|ItemizedList|OrderedList|SegmentedList
-		|SimpleList|VariableList 		|Caution|Important|Note|Tip|Warning 
-		|LiteralLayout|ProgramListing|ProgramListingCO|Screen
-		|ScreenCO|ScreenShot 	|Synopsis|CmdSynopsis|FuncSynopsis 
-		|FormalPara|Para|SimPara 		|Address|BlockQuote
-		|Graphic|GraphicCO|MediaObject|MediaObjectCO
-		|InformalEquation
-		|InformalExample
-		|InformalFigure
-		|InformalTable 
-		|Equation|Example|Figure|Table 		|MsgSet|Procedure|Sidebar|QandASet 
-		|Anchor|BridgeHead|Comment|Highlights
-				|Abstract|AuthorBlurb|Epigraph
-		
-		|IndexTerm 
-		)+, 
-	(Sect1*|(RefEntry )*|SimpleSect*|Section*))
-	| (Sect1+|(RefEntry )+|SimpleSect+|Section+)" nil) ("set.content.module" text "INCLUDE" nil) ("set.module" text "INCLUDE" nil) ("local.set.attrib" text "" nil) ("set.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("set.element" text "INCLUDE" nil) ("set.attlist" text "INCLUDE" nil) ("setinfo.module" text "INCLUDE" nil) ("local.setinfo.attrib" text "" nil) ("setinfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("setinfo.element" text "INCLUDE" nil) ("setinfo.attlist" text "INCLUDE" nil) ("book.content.module" text "INCLUDE" nil) ("book.module" text "INCLUDE" nil) ("local.book.attrib" text "" nil) ("book.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("book.element" text "INCLUDE" nil) ("book.attlist" text "INCLUDE" nil) ("bookinfo.module" text "INCLUDE" nil) ("local.bookinfo.attrib" text "" nil) ("bookinfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("bookinfo.element" text "INCLUDE" nil) ("bookinfo.attlist" text "INCLUDE" nil) ("dedication.module" text "INCLUDE" nil) ("local.dedication.attrib" text "" nil) ("dedication.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("dedication.element" text "INCLUDE" nil) ("dedication.attlist" text "INCLUDE" nil) ("colophon.module" text "INCLUDE" nil) ("local.colophon.attrib" text "" nil) ("colophon.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("colophon.element" text "INCLUDE" nil) ("colophon.attlist" text "INCLUDE" nil) ("toc.content.module" text "INCLUDE" nil) ("toc.module" text "INCLUDE" nil) ("local.toc.attrib" text "" nil) ("toc.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("toc.element" text "INCLUDE" nil) ("toc.attlist" text "INCLUDE" nil) ("tocfront.module" text "INCLUDE" nil) ("local.tocfront.attrib" text "" nil) ("tocfront.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("tocfront.element" text "INCLUDE" nil) ("tocfront.attlist" text "INCLUDE" nil) ("tocentry.module" text "INCLUDE" nil) ("local.tocentry.attrib" text "" nil) ("tocentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("tocentry.element" text "INCLUDE" nil) ("tocentry.attlist" text "INCLUDE" nil) ("tocpart.module" text "INCLUDE" nil) ("local.tocpart.attrib" text "" nil) ("tocpart.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("tocpart.element" text "INCLUDE" nil) ("tocpart.attlist" text "INCLUDE" nil) ("tocchap.module" text "INCLUDE" nil) ("local.tocchap.attrib" text "" nil) ("tocchap.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("tocchap.element" text "INCLUDE" nil) ("tocchap.attlist" text "INCLUDE" nil) ("toclevel1.module" text "INCLUDE" nil) ("local.toclevel1.attrib" text "" nil) ("toclevel1.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("toclevel1.element" text "INCLUDE" nil) ("toclevel1.attlist" text "INCLUDE" nil) ("toclevel2.module" text "INCLUDE" nil) ("local.toclevel2.attrib" text "" nil) ("toclevel2.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("toclevel2.element" text "INCLUDE" nil) ("toclevel2.attlist" text "INCLUDE" nil) ("toclevel3.module" text "INCLUDE" nil) ("local.toclevel3.attrib" text "" nil) ("toclevel3.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("toclevel3.element" text "INCLUDE" nil) ("toclevel3.attlist" text "INCLUDE" nil) ("toclevel4.module" text "INCLUDE" nil) ("local.toclevel4.attrib" text "" nil) ("toclevel4.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("toclevel4.element" text "INCLUDE" nil) ("toclevel4.attlist" text "INCLUDE" nil) ("toclevel5.module" text "INCLUDE" nil) ("local.toclevel5.attrib" text "" nil) ("toclevel5.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("toclevel5.element" text "INCLUDE" nil) ("toclevel5.attlist" text "INCLUDE" nil) ("tocback.module" text "INCLUDE" nil) ("local.tocback.attrib" text "" nil) ("tocback.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("tocback.element" text "INCLUDE" nil) ("tocback.attlist" text "INCLUDE" nil) ("lot.content.module" text "INCLUDE" nil) ("lot.module" text "INCLUDE" nil) ("local.lot.attrib" text "" nil) ("lot.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("lot.element" text "INCLUDE" nil) ("lot.attlist" text "INCLUDE" nil) ("lotentry.module" text "INCLUDE" nil) ("local.lotentry.attrib" text "" nil) ("lotentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("lotentry.element" text "INCLUDE" nil) ("lotentry.attlist" text "INCLUDE" nil) ("appendix.module" text "INCLUDE" nil) ("local.appendix.attrib" text "" nil) ("appendix.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("appendix.element" text "INCLUDE" nil) ("appendix.attlist" text "INCLUDE" nil) ("chapter.module" text "INCLUDE" nil) ("local.chapter.attrib" text "" nil) ("chapter.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("chapter.element" text "INCLUDE" nil) ("chapter.attlist" text "INCLUDE" nil) ("part.module" text "INCLUDE" nil) ("local.part.attrib" text "" nil) ("part.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("part.element" text "INCLUDE" nil) ("part.attlist" text "INCLUDE" nil) ("preface.module" text "INCLUDE" nil) ("local.preface.attrib" text "" nil) ("preface.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("preface.element" text "INCLUDE" nil) ("preface.attlist" text "INCLUDE" nil) ("reference.module" text "INCLUDE" nil) ("local.reference.attrib" text "" nil) ("reference.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("reference.element" text "INCLUDE" nil) ("reference.attlist" text "INCLUDE" nil) ("partintro.module" text "INCLUDE" nil) ("local.partintro.attrib" text "" nil) ("partintro.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("partintro.element" text "INCLUDE" nil) ("partintro.attlist" text "INCLUDE" nil) ("otherinfo.module" text "INCLUDE" nil) ("local.otherinfo.attrib" text "" nil) ("otherinfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("otherinfo.elements" text "INCLUDE" nil) ("otherinfo.attlists" text "INCLUDE" nil) ("section.content.module" text "INCLUDE" nil) ("section.module" text "INCLUDE" nil) ("local.section.attrib" text "" nil) ("section.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("section.element" text "INCLUDE" nil) ("section.attlist" text "INCLUDE" nil) ("sectioninfo.module" text "INCLUDE" nil) ("sectioninfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("local.sectioninfo.attrib" text "" nil) ("sectioninfo.element" text "INCLUDE" nil) ("sectioninfo.attlist" text "INCLUDE" nil) ("sect1.module" text "INCLUDE" nil) ("local.sect1.attrib" text "" nil) ("sect1.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("sect1.element" text "INCLUDE" nil) ("sect1.attlist" text "INCLUDE" nil) ("sect2.module" text "INCLUDE" nil) ("local.sect2.attrib" text "" nil) ("sect2.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("sect2.element" text "INCLUDE" nil) ("sect2.attlist" text "INCLUDE" nil) ("sect3.module" text "INCLUDE" nil) ("local.sect3.attrib" text "" nil) ("sect3.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("sect3.element" text "INCLUDE" nil) ("sect3.attlist" text "INCLUDE" nil) ("sect4.module" text "INCLUDE" nil) ("local.sect4.attrib" text "" nil) ("sect4.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("sect4.element" text "INCLUDE" nil) ("sect4.attlist" text "INCLUDE" nil) ("sect5.module" text "INCLUDE" nil) ("local.sect5.attrib" text "" nil) ("sect5.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("sect5.element" text "INCLUDE" nil) ("sect5.attlist" text "INCLUDE" nil) ("simplesect.module" text "INCLUDE" nil) ("local.simplesect.attrib" text "" nil) ("simplesect.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("simplesect.element" text "INCLUDE" nil) ("simplesect.attlist" text "INCLUDE" nil) ("bibliography.content.module" text "INCLUDE" nil) ("bibliography.module" text "INCLUDE" nil) ("local.bibliography.attrib" text "" nil) ("bibliography.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("bibliography.element" text "INCLUDE" nil) ("bibliography.attlist" text "INCLUDE" nil) ("bibliodiv.module" text "INCLUDE" nil) ("local.bibliodiv.attrib" text "" nil) ("bibliodiv.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("bibliodiv.element" text "INCLUDE" nil) ("bibliodiv.attlist" text "INCLUDE" nil) ("glossary.content.module" text "INCLUDE" nil) ("glossary.module" text "INCLUDE" nil) ("local.glossary.attrib" text "" nil) ("glossary.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("glossary.element" text "INCLUDE" nil) ("glossary.attlist" text "INCLUDE" nil) ("glossdiv.module" text "INCLUDE" nil) ("local.glossdiv.attrib" text "" nil) ("glossdiv.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("glossdiv.element" text "INCLUDE" nil) ("glossdiv.attlist" text "INCLUDE" nil) ("index.content.module" text "INCLUDE" nil) ("indexes.module" text "INCLUDE" nil) ("local.indexes.attrib" text "" nil) ("indexes.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("indexes.elements" text "INCLUDE" nil) ("indexes.attlists" text "INCLUDE" nil) ("indexdiv.module" text "INCLUDE" nil) ("local.indexdiv.attrib" text "" nil) ("indexdiv.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("indexdiv.element" text "INCLUDE" nil) ("indexdiv.attlist" text "INCLUDE" nil) ("indexentry.module" text "INCLUDE" nil) ("local.indexentry.attrib" text "" nil) ("indexentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("indexentry.element" text "INCLUDE" nil) ("indexentry.attlist" text "INCLUDE" nil) ("primsecterie.module" text "INCLUDE" nil) ("local.primsecterie.attrib" text "" nil) ("primsecterie.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("primsecterie.elements" text "INCLUDE" nil) ("primsecterie.attlists" text "INCLUDE" nil) ("seeie.module" text "INCLUDE" nil) ("local.seeie.attrib" text "" nil) ("seeie.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("seeie.element" text "INCLUDE" nil) ("seeie.attlist" text "INCLUDE" nil) ("seealsoie.module" text "INCLUDE" nil) ("local.seealsoie.attrib" text "" nil) ("seealsoie.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("seealsoie.element" text "INCLUDE" nil) ("seealsoie.attlist" text "INCLUDE" nil) ("refentry.content.module" text "INCLUDE" nil) ("refentry.module" text "INCLUDE" nil) ("local.refentry.attrib" text "" nil) ("refentry.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refentry.element" text "INCLUDE" nil) ("refentry.attlist" text "INCLUDE" nil) ("refmeta.module" text "INCLUDE" nil) ("local.refmeta.attrib" text "" nil) ("refmeta.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refmeta.element" text "INCLUDE" nil) ("refmeta.attlist" text "INCLUDE" nil) ("refmiscinfo.module" text "INCLUDE" nil) ("local.refmiscinfo.attrib" text "" nil) ("refmiscinfo.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refmiscinfo.element" text "INCLUDE" nil) ("refmiscinfo.attlist" text "INCLUDE" nil) ("refnamediv.module" text "INCLUDE" nil) ("local.refnamediv.attrib" text "" nil) ("refnamediv.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refnamediv.element" text "INCLUDE" nil) ("refnamediv.attlist" text "INCLUDE" nil) ("refdescriptor.module" text "INCLUDE" nil) ("local.refdescriptor.attrib" text "" nil) ("refdescriptor.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refdescriptor.element" text "INCLUDE" nil) ("refdescriptor.attlist" text "INCLUDE" nil) ("refname.module" text "INCLUDE" nil) ("local.refname.attrib" text "" nil) ("refname.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refname.element" text "INCLUDE" nil) ("refname.attlist" text "INCLUDE" nil) ("refpurpose.module" text "INCLUDE" nil) ("local.refpurpose.attrib" text "" nil) ("refpurpose.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refpurpose.element" text "INCLUDE" nil) ("refpurpose.attlist" text "INCLUDE" nil) ("refclass.module" text "INCLUDE" nil) ("local.refclass.attrib" text "" nil) ("refclass.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refclass.element" text "INCLUDE" nil) ("refclass.attlist" text "INCLUDE" nil) ("refsynopsisdiv.module" text "INCLUDE" nil) ("local.refsynopsisdiv.attrib" text "" nil) ("refsynopsisdiv.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refsynopsisdiv.element" text "INCLUDE" nil) ("refsynopsisdiv.attlist" text "INCLUDE" nil) ("refsect1.module" text "INCLUDE" nil) ("local.refsect1.attrib" text "" nil) ("refsect1.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refsect1.element" text "INCLUDE" nil) ("refsect1.attlist" text "INCLUDE" nil) ("refsect2.module" text "INCLUDE" nil) ("local.refsect2.attrib" text "" nil) ("refsect2.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refsect2.element" text "INCLUDE" nil) ("refsect2.attlist" text "INCLUDE" nil) ("refsect3.module" text "INCLUDE" nil) ("local.refsect3.attrib" text "" nil) ("refsect3.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("refsect3.element" text "INCLUDE" nil) ("refsect3.attlist" text "INCLUDE" nil) ("article.module" text "INCLUDE" nil) ("local.article.attrib" text "" nil) ("article.role.attrib" text "Role		CDATA		#IMPLIED" nil) ("article.element" text "INCLUDE" nil) ("article.attlist" text "INCLUDE" nil) ("dbgenent" text ("-//OASIS//ENTITIES DocBook Additional General Entities V3.1//EN" nil . "/usr/share/sgml/docbook/sgml-dtd-3.1/") nil))
-"BOOK"
-ûe"SECTIONINFO"
-"LOT"
-"SUBJECTSET"
-"BIBLIOENTRY"
-"SIMPLESECT"
-"PRIMARY"
-"CITY"
-"SCREENCO"
-"INVPARTNUMBER"
-"OLINK"
-"REFMISCINFO"
-"REFNAMEDIV"
-"VIDEODATA"
-"ITERMSET"
-"PUBSNUMBER"
-"FIRSTTERM"
-"TEXTOBJECT"
-"NOTE"
-"SYNOPSIS"
-"OTHERCREDIT"
-"CITETITLE"
-"FAX"
-"CAPTION"
-"AFFILIATION"
-"LINEAGE"
-"MSGTEXT"
-"IMPORTANT"
-"BEGINPAGE"
-"INDEXTERM"
-"MARKUP"
-"MSGENTRY"
-"CMDSYNOPSIS"
-"GRAPHIC"
-"INLINEMEDIAOBJECT"
-"ERRORNAME"
-"TERTIARY"
-"ARG"
-"OBJECTINFO"
-"LINEANNOTATION"
-"STEP"
-"GRAPHICCO"
-"ARTPAGENUMS"
-"FOOTNOTEREF"
-"MSGSET"
-"USERINPUT"
-"GLOSSTERM"
-"REVNUMBER"
-"TGROUP"
-"EPIGRAPH"
-"VARIABLELIST"
-"MSGEXPLAN"
-"HONORIFIC"
-"VOLUMENUM"
-"REVHISTORY"
-"SYMBOL"
-"TOCENTRY"
-"TOCCHAP"
-"PART"
-"VARLISTENTRY"
-"PUBLISHER"
-"AUTHORGROUP"
-"MEDIALABEL"
-"DATABASE"
-"TOC"
-"POSTCODE"
-"IMAGEOBJECT"
-"SEGTITLE"
-"GLOSSDEF"
-"MEDIAOBJECTCO"
-"INDEXENTRY"
-"BIBLIODIV"
-"JOBTITLE"
-"FORMALPARA"
-"PAGENUMS"
-"SUBSCRIPT"
-"TYPE"
-"TERTIARYIE"
-"SECT1INFO"
-"COLSPEC"
-"INFORMALEXAMPLE"
-"SIMPLELIST"
-"BOOKBIBLIO"
-"SECT5INFO"
-"POB"
-"CO"
-"SEGLISTITEM"
-"ANSWER"
-"MSGMAIN"
-"CORPAUTHOR"
-"RETURNVALUE"
-"SETINFO"
-"COLLABNAME"
-"ALT"
-"SUBJECTTERM"
-"DATE"
-"CORPNAME"
-"PARAMDEF"
-"AUTHOR"
-"OPTIONAL"
-"QUOTE"
-"REFENTRY"
-"CONTRACTNUM"
-"PARAMETER"
-"SUBSTEPS"
-"AREASET"
-"AREA"
-"CAUTION"
-"SEGMENTEDLIST"
-"FUNCTION"
-"PHRASE"
-"TBODY"
-"CONFSPONSOR"
-"TIP"
-"SBR"
-"INFORMALFIGURE"
-"PROGRAMLISTINGCO"
-"STRUCTFIELD"
-"REFSECT3INFO"
-"EXAMPLE"
-"MENUCHOICE"
-"GUILABEL"
-"COLOPHON"
-"PREFACE"
-"ACTION"
-"REFSYNOPSISDIV"
-"BOOK"
-"SHORTAFFIL"
-"FIGURE"
-"CALLOUTLIST"
-"REFSECT3"
-"PRIMARYIE"
-"TOCLEVEL5"
-"BOOKINFO"
-"AUTHORBLURB"
-"ISBN"
-"ANCHOR"
-"REFSECT2"
-"TOCLEVEL4"
-"SIDEBAR"
-"KEYCODE"
-"REFSECT1"
-"PARTINTRO"
-"TOCLEVEL3"
-"PARA"
-"EDITION"
-"VARNAME"
-"INDEXDIV"
-"TOCLEVEL2"
-"QANDAENTRY"
-"SIMPARA"
-"SGMLTAG"
-"WORDASWORD"
-"TOCLEVEL1"
-"EQUATION"
-"SUPERSCRIPT"
-"AUTHORINITIALS"
-"GUISUBMENU"
-"COMPUTEROUTPUT"
-"ORGDIV"
-"ARTHEADER"
-"PROMPT"
-"REFSYNOPSISDIVINFO"
-"SECT4INFO"
-"SETINDEX"
-"MEDIAOBJECT"
-"CONTRIB"
-"OTHERNAME"
-"REFENTRYTITLE"
-"HOLDER"
-"ACKNO"
-"MSGORIG"
-"COMMENT"
-"ERRORCODE"
-"CONFNUM"
-"CONFDATES"
-"VIDEOOBJECT"
-"ORDEREDLIST"
-"CONFGROUP"
-"SUBTITLE"
-"TITLEABBREV"
-"ENVAR"
-"ULINK"
-"FOOTNOTE"
-"REVISION"
-"AUDIODATA"
-"AREASPEC"
-"CALLOUT"
-"CONSTANT"
-"KEYSYM"
-"REFPURPOSE"
-"FUNCPARAMS"
-"TFOOT"
-"TABLE"
-"PROGRAMLISTING"
-"MSGINFO"
-"TITLE"
-"REFERENCE"
-"FUNCDEF"
-"GLOSSLIST"
-"REPLACEABLE"
-"LINK"
-"ACCEL"
-"REVREMARK"
-"COUNTRY"
-"RELEASEINFO"
-"ISSUENUM"
-"MODESPEC"
-"INTERFACEDEFINITION"
-"INFORMALEQUATION"
-"ITEMIZEDLIST"
-"ABSTRACT"
-"QANDASET"
-"ERRORTYPE"
-"EMAIL"
-"REFSECT2INFO"
-"VOID"
-"SCREENINFO"
-"APPLICATION"
-"MANVOLNUM"
-"ENTRYTBL"
-"SPANSPEC"
-"CITEREFENTRY"
-"ABBREV"
-"PUBLISHERNAME"
-"SYNOPFRAGMENT"
-"HIGHLIGHTS"
-"BIBLIOMIXED"
-"SERIESVOLNUMS"
-"INDEX"
-"SET"
-"MEMBER"
-"BIBLIOMSET"
-"GUIMENU"
-"SECONDARYIE"
-"LOTENTRY"
-"VARARGS"
-"THEAD"
-"ISSN"
-"CONTRACTSPONSOR"
-"EMPHASIS"
-"TRADEMARK"
-"REFDESCRIPTOR"
-"APPENDIX"
-"ENTRY"
-"KEYCOMBO"
-"GUIMENUITEM"
-"XREF"
-"SECT3INFO"
-"AUDIOOBJECT"
-"GLOSSENTRY"
-"HARDWARE"
-"SHORTCUT"
-"MSGREL"
-"COMMAND"
-"REFNAME"
-"PHONE"
-"GROUP"
-"GLOSSSEE"
-"CITATION"
-"TOCFRONT"
-"GLOSSARY"
-"SYNOPFRAGMENTREF"
-"PUBDATE"
-"PROPERTY"
-"SEEALSOIE"
-"SEEALSO"
-"MOUSEBUTTON"
-"TERM"
-"INTERFACE"
-"FOREIGNPHRASE"
-"ACRONYM"
-"SECT5"
-"QUESTION"
-"BRIDGEHEAD"
-"LITERALLAYOUT"
-"WARNING"
-"MSG"
-"COPYRIGHT"
-"COLLAB"
-"OPTION"
-"SECT4"
-"OTHERADDR"
-"BLOCKQUOTE"
-"SCREEN"
-"PRODUCTNAME"
-"SECT3"
-"SEG"
-"KEYWORDSET"
-"SYSTEMITEM"
-"GLOSSDIV"
-"SECT2"
-"DOCINFO"
-"SERIESINFO"
-"PRODUCTNUMBER"
-"TOKEN"
-"KEYCAP"
-"REFSECT1INFO"
-"SECTION"
-"SECT1"
-"DEDICATION"
-"SEE"
-"CONFTITLE"
-"MSGSUB"
-"BIBLIOGRAPHY"
-"SECONDARY"
-"ATTRIBUTION"
-"LEGALNOTICE"
-"INLINEGRAPHIC"
-"STRUCTNAME"
-"TOCBACK"
-"CLASSNAME"
-"REFCLASS"
-"ARTICLE"
-"YEAR"
-"LITERAL"
-"REFMETA"
-"IMAGEOBJECTCO"
-"KEYWORD"
-"FIRSTNAME"
-"ORGNAME"
-"STREET"
-"ROW"
-"MSGLEVEL"
-"FUNCSYNOPSIS"
-"INLINEEQUATION"
-"TOCPART"
-"FUNCSYNOPSISINFO"
-"BIBLIOMISC"
-"STATE"
-"IMAGEDATA"
-"INFORMALTABLE"
-"MSGAUD"
-"SURNAME"
-"PRINTHISTORY"
-"FILENAME"
-"SECT2INFO"
-"QANDADIV"
-"SUBJECT"
-"EDITOR"
-"SEEIE"
-"CHAPTER"
-"LISTITEM"
-"GLOSSSEEALSO"
-"SCREENSHOT"
-"GUIICON"
-"FUNCPROTOTYPE"
-"LABEL"
-"PROCEDURE"
-"BIBLIOSET"
-"ADDRESS"
-"GUIBUTTON"
-ûe(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-ۑ
û*Ä
ë

Äë
´³
ëë
´(attlist (("SCHEME" NAME IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ûX

ûX
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€5ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦

û+
R
 
5 
R
û+

¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
´³2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†12�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
´2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†12�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1(attlist (("SORTAS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
º

û"
�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("TARGETDOCENT" ENTITY IMPLIED) ("LINKMODE" IDREF IMPLIED) ("LOCALINFO" CDATA IMPLIED) ("TYPE" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("CLASS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ò

û
û
û
¾¬É
-¶û>¶
-ɬ(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ENTITYREF" ENTITY IMPLIED) ("FILEREF" CDATA IMPLIED) ("FORMAT" (name-token-group ("BMP" "CGM-CHAR" "CGM-BINARY" "CGM-CLEAR" "DITROFF" "DVI" "EPS" "EQN" "FAX" "GIF" "GIF87A" "GIF89A" "JPG" "JPEG" "IGES" "PCX" "PIC" "PS" "SGML" "TBL" "TEX" "TIFF" "WMF" "WPG" "LINESPECIFIC")) IMPLIED) ("SRCCREDIT" CDATA IMPLIED) ("WIDTH" NUTOKEN IMPLIED) ("DEPTH" NUTOKEN IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER")) IMPLIED) ("SCALE" NUMBER IMPLIED) ("SCALEFIT" NUMBER IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€



(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("LINKEND" IDREF IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:›K¬ˆ¶
-Éñðû(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
&
nû!–�Iû^û"tÂûûqk2Ql±ÒÇ��ÇÒ±lQ2kqûûÂtû"û^I�–û!n�ÇÒ±lQ2kqûûÂtû"û^I�–û!(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬'¬ûˆ‹ûbÁ€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂû2Ql±ÒÇ�'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬kqû(attlist (("LABEL" CDATA IMPLIED) ("FORMAT" (NOTATION ("LINESPECIFIC")) (nil "linespecific")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
[¥!ûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+'(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€¦
†

§

ûS
ûE
4
4
ûE
ûS

§

†
¦
(attlist (("PUBWORK" (name-token-group ("ARTICLE" "BOOK" "CHAPTER" "PART" "REFENTRY" "SECTION" "JOURNAL" "SERIES" "SET" "MANUSCRIPT")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û!–�Iû^û"tÂûûqk2Ql±ÒÇ�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€ûd
ŸûFH
ûd
ûd
Ÿûd
Ÿûd
ŸûFH(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€2
1
†
Ó
â
¬
û
ˆ
Ô
‹
ûb
,
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
û
q


k
2
Q
l
±
Ò
Ç
�
2�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬'¬ûˆ‹ûbÁ€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂû2Ql±ÒÇ�'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬kqû(attlist (("PAGENUM" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("PAGENUM" CDATA IMPLIED) ("SCOPE" (name-token-group ("ALL" "GLOBAL" "LOCAL")) IMPLIED) ("SIGNIFICANCE" (name-token-group ("PREFERRED" "NORMAL")) (nil "Normal")) ("CLASS" (name-token-group ("SINGULAR" "STARTOFRANGE" "ENDOFRANGE")) IMPLIED) ("STARTREF" IDREF CONREF) ("ZONE" IDREFS IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
-

ûû3û7
ûûû3$
ûûû3	
û(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û
3Ãû

3
3(attlist (("LABEL" CDATA IMPLIED) ("SEPCHAR" CDATA (nil " ")) ("CMDLENGTH" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€r
û
%
û
áû
%
û
r

á(attlist (("ENTITYREF" ENTITY IMPLIED) ("FILEREF" CDATA IMPLIED) ("FORMAT" (NOTATION ("BMP" "CGM-CHAR" "CGM-BINARY" "CGM-CLEAR" "DITROFF" "DVI" "EPS" "EQN" "FAX" "GIF" "GIF87A" "GIF89A" "JPG" "JPEG" "IGES" "PCX" "PIC" "PS" "SGML" "TBL" "TEX" "TIFF" "WMF" "WPG" "LINESPECIFIC")) IMPLIED) ("SRCCREDIT" CDATA IMPLIED) ("WIDTH" NUTOKEN IMPLIED) ("DEPTH" NUTOKEN IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER")) IMPLIED) ("SCALE" NUMBER IMPLIED) ("SCALEFIT" NUMBER IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
&
°ùBBù°°ùB(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("SORTAS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("CHOICE" (name-token-group ("OPT" "REQ" "PLAIN")) (nil "Opt")) ("REP" (name-token-group ("NOREPEAT" "REPEAT")) (nil "Norepeat")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
rÈûûû%(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("PERFORMANCE" (name-token-group ("OPTIONAL" "REQUIRED")) (nil "Required")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1h3h1†Óâ¬ûˆÔ‹ûb,Á€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂûûqk2Ql±ÒÇ�3h�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†121†Óâ¬ûˆÔ‹ûb,Á€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂûûqk2Ql±ÒÇ�21†Óâ¬ûˆÔ‹ûb,Á€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂûûqk2Ql±ÒÇ�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
º

!
�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("LINKEND" IDREF REQUIRED) ("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä


´


(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("LINKEND" IDREF IMPLIED) ("BASEFORM" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("COLS" NUMBER REQUIRED) ("TGROUPSTYLE" NMTOKEN IMPLIED) ("COLSEP" NUMBER IMPLIED) ("ROWSEP" NUMBER IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER" "JUSTIFY" "CHAR")) IMPLIED) ("CHAR" CDATA IMPLIED) ("CHAROFF" NUTOKEN IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€À
íÝO
o
o
À

oÀ
íÝ
o(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û8
I�––�II�–(attlist (("TERMLENGTH" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä

;
´
;
;
;(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†121†Óâ¬ûˆÔ‹ûb,Á€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂûûqk2Ql±ÒÇ�2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
¸

¸
(attlist (("CLASS" (name-token-group ("LIMIT")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("LINKEND" IDREF IMPLIED) ("PAGENUM" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
8
™8

™(attlist (("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û*

Ä
ÄŽ´³óû[@åûû6û?{eÅóû[@åûû6û?{eÅ
Žóû[@åûû6û?{eÅŽ´óû[@åûû6û?{eÅóû[@åûû6û?{eÅ(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û

û

û\(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
à

ûd
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Y
û
ûY
b
b
ûY
û
Y

(attlist (("CLASS" (name-token-group ("CARTRIDGE" "CDROM" "DISK" "TAPE")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("CLASS" (name-token-group ("NAME" "TABLE" "FIELD" "KEY1" "KEY2" "RECORD")) IMPLIED) ("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("PAGENUM" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€û<
ûL9û
-û*Ä
û<
û<
9ûLû<
ûL9û
-
Äû<
ûL9û
-´³û<
ûL9û
-û<
ûL9û
-´(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
&

ûP
ûP(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
UûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("SUBJECT" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€#
¬
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
2
Q
l
±
Ò
Ç
�
$û]�
Ç
Ò
±
l
Q
2
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
¬


û](attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
&

ûC
ûCûC(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ƒ
êû
ûZ
êMûûZ(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€3�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

Äã2
1
†
Ó
â
¬
û
ˆ
Ô
‹
ûb
,
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
û
q


k
2
Q
l
±
Ò
Ç
�
ã4�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

´³ãã2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1ã3�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

´ã(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä



�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

›K¬ˆ"û:7Èð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("LINKENDS" IDREFS IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("COLNUM" NUMBER IMPLIED) ("COLNAME" NMTOKEN IMPLIED) ("COLWIDTH" CDATA IMPLIED) ("COLSEP" NUMBER IMPLIED) ("ROWSEP" NUMBER IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER" "JUSTIFY" "CHAR")) IMPLIED) ("CHAR" CDATA IMPLIED) ("CHAROFF" NUTOKEN IMPLIED)))
-(attlist (("WIDTH" NUMBER IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
2
Q
l
±
Ò
Ç
�
�
Ç
Ò
±
l
Q
2
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ

(attlist (("COLUMNS" NUMBER IMPLIED) ("TYPE" (name-token-group ("INLINE" "VERT" "HORIZ")) (nil "Vert")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ç

ç
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€3û+

¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß
3ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦

û+
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("LABEL" CDATA IMPLIED) ("LINKENDS" IDREFS IMPLIED) ("ID" ID REQUIRED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û%

û%
û%(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€)•
�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬âûa
•
(•
â¬ûˆûbÁ€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂû2Ql±ÒÇ�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("CONTENTS" IDREFS IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
¿gÈ(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€¦
†

§

ûS
ûE
4
4
ûE
ûS

§

†
¦
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€¬
É

-
¶
ûBû*
¶

-
É
¬

ƒ
-¶
¬
É

-
¶
ûB

}
�
�
�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("CLASS" (name-token-group ("COMMAND" "FUNCTION" "OPTION")) IMPLIED) ("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("PERFORMANCE" (name-token-group ("OPTIONAL" "REQUIRED")) (nil "Required")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
(

(
(attlist (("LABEL" CDATA IMPLIED) ("UNITS" (name-token-group ("CALSPAIR" "LINECOLUMN" "LINERANGE" "LINECOLUMNPAIR" "OTHER")) IMPLIED) ("OTHERUNITS" NAME IMPLIED) ("COORDS" CDATA REQUIRED) ("ID" ID REQUIRED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
j

j
(attlist (("LABEL" CDATA IMPLIED) ("LINKENDS" IDREFS IMPLIED) ("UNITS" (name-token-group ("CALSPAIR" "LINECOLUMN" "LINERANGE" "LINECOLUMNPAIR" "OTHER")) IMPLIED) ("OTHERUNITS" NAME IMPLIED) ("COORDS" CDATA REQUIRED) ("ID" ID REQUIRED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬'¬ûˆ‹ûbÁ€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂû2Ql±ÒÇ�'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬kqû(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€C
Ä
V
C

VC
´
V
V
C
V(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("VALIGN" (name-token-group ("TOP" "MIDDLE" "BOTTOM")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ûH

ûH
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬'¬ûˆ‹ûbÁ€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂû2Ql±ÒÇ�'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬kqû(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("FLOAT" NUMBER (nil "0")) ("PGWIDE" NUMBER IMPLIED) ("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-ۦ

-
É

ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
ûJ
 

û^

û"
t
Â
û
û
Â
t
û"

û^

 
ûJ
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ

É

-
¶
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
º

Â
�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("LABEL" CDATA IMPLIED) ("WIDTH" NUMBER IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä

´�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQ�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQ�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û
ûeû_yéö�ûû�öéyû_ûeûeû_yéö�û(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ê"û:È(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
�ÇÒ±lQ2kqûûÂtû"û^I�–û!´³�ÇÒ±lQ2kqûûÂtû"û^I�–û!�ÇÒ±lQ2kqûûÂtû"û^I�–û!�ÇÒ±lQ2kqûûÂtû"û^I�–û!
´�ÇÒ±lQ2kqûûÂtû"û^I�–û!(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û*

Ä
Ä´³6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	
´6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	6û1
-eû0
�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
û0

e
û1	û0
eû1
-
e

û0
(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-ۀ
¢3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‰´³3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‰
Ä
3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‰3‰�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
‰3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‰
´3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‰
‰(attlist (("FPI" CDATA IMPLIED) ("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€û2
@

û
û6
{
û[
Å
:
û?
ó
å
¤
z
…Äz
¤
å
ó
û?
:
Å
û[
{
û6
û

@
û2
û2@ûû6{û[Å:û?óå¤zû2
@

û
û6
{
û[
Å
:
û?
ó
å
¤
z
…´³û2
@

û
û6
{
û[
Å
:
û?
ó
å
¤
z
…û2
@

û
û6
{
û[
Å
:
û?
ó
å
¤
z
…´(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("FLOAT" NUMBER (nil "0")) ("PGWIDE" NUMBER IMPLIED) ("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä

´ûÂtû"û^ ûJûdû!!)¥EÑPsûQÉ
-¶ûÂtû"û^ ûJûdû!!)¥EÑPsûQÉ
-¶ûÂtû"û^ ûJûdû!!)¥EÑPsûQÉ
-¶(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä

»
´
»
»
»(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
v

Ä
Ä´³2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†12�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
´2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†12�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1(attlist (("LINKENDS" IDREFS IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
8

8
(attlist (("CONTENTS" IDREFS IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€:R

¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
:!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦

R

(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
I�––�II�–(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID REQUIRED) ("PAGENUM" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
×

Ä
Ä´³3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‚3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‚
´3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‚3‚�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
‚
‚(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
8
„8

„(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
,�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬â
´,�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬â,�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬â,�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬â(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û/

Ä
Ä´³3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‰3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‰
´3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1‰3‰�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
‰
‰(attlist (("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

Ä
6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1´³6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû16û1	e
-û0�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
û0

e
û16�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1
´6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1û0e
-û1	
e
-

û0(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
8
Š8

Š(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
xÁ€wšûQsPÑE¥)!û!ûdû^û"tÂûûqk2Ql±ÒÇ�ûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€ Ò
±
2
Q
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
ˆ
¬
É

-
¶
ÄlF¶

-
É
¬
ˆ
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
Q
2
±
Ò
Fl!Ò
±
2
Q
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
ˆ
¬
É

-
¶
´³lF
FÒ±2QûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQˆ¬É
-¶lF Ò
±
2
Q
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
ˆ
¬
É

-
¶
´lF(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
8
�8

�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û

W
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("CLASS" (name-token-group ("ATTRIBUTE" "ATTVALUE" "ELEMENT" "ENDTAG" "GENENTITY" "NUMCHARREF" "PARAMENTITY" "PI" "STARTTAG" "SGMLCOMMENT")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:›K¬ˆ¶
-Éñðû(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
8
”8

”(attlist (("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€]
ÄÑ!¥¥!]
´Ñ!¥
!
¥
]
Ñ!¥(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

›K¬ˆ"û:7Èð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ê"û:È(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€:R

¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
:!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦

R

(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€6“
F�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û*ÄF“

F4“
F1†Óâ¬ûˆÔ‹ûb,Á€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂûûqk2Ql±ÒÇ�
Ä6“
F�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1´³4“
F�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†15“
F�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1´
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
&
°ùBBù°°ùB(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
&




(attlist (("NUMERATION" (name-token-group ("ARABIC" "UPPERALPHA" "LOWERALPHA" "UPPERROMAN" "LOWERROMAN")) IMPLIED) ("INHERITNUM" (name-token-group ("INHERIT" "IGNORE")) (nil "Ignore")) ("CONTINUATION" (name-token-group ("CONTINUES" "RESTARTS")) (nil "Restarts")) ("SPACING" (name-token-group ("NORMAL" "COMPACT")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û\

û\
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
pûd®û4¯(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
UûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
UûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("URL" CDATA REQUIRED) ("TYPE" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
2
Q
l
±
Ò
Ç
�
�
Ç
Ò
±
l
Q
2
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
·šw€Á(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
/

_˜(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ENTITYREF" ENTITY IMPLIED) ("FILEREF" CDATA IMPLIED) ("FORMAT" (name-token-group ("BMP" "CGM-CHAR" "CGM-BINARY" "CGM-CLEAR" "DITROFF" "DVI" "EPS" "EQN" "FAX" "GIF" "GIF87A" "GIF89A" "JPG" "JPEG" "IGES" "PCX" "PIC" "PS" "SGML" "TBL" "TEX" "TIFF" "WMF" "WPG" "LINESPECIFIC")) IMPLIED) ("SRCCREDIT" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("UNITS" (name-token-group ("CALSPAIR" "LINECOLUMN" "LINERANGE" "LINECOLUMNPAIR" "OTHER")) IMPLIED) ("OTHERUNITS" NAME IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€i
j
j
i
(attlist (("AREAREFS" IDREFS REQUIRED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€2
1
†
Ó
â
¬
û
ˆ
Ô
‹
ûb
,
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
û
q


k
2
Q
l
±
Ò
Ç
�
2�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED) ("CLASS" (name-token-group ("LIMIT")) IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
R›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("VALIGN" (name-token-group ("TOP" "MIDDLE" "BOTTOM")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
O
ûH

ûH

Ü(attlist (("FRAME" (name-token-group ("TOP" "BOTTOM" "TOPBOT" "ALL" "SIDES" "NONE")) IMPLIED) ("COLSEP" NUMBER IMPLIED) ("ROWSEP" NUMBER IMPLIED) ("TABSTYLE" NMTOKEN IMPLIED) ("TOCENTRY" NUMBER IMPLIED) ("SHORTENTRY" NUMBER IMPLIED) ("ORIENT" (name-token-group ("PORT" "LAND")) IMPLIED) ("PGWIDE" NUMBER IMPLIED) ("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
´!¥0
!¥0
!¥0
!
¥
0ûQšw€Á(attlist (("WIDTH" NUMBER IMPLIED) ("FORMAT" (NOTATION ("LINESPECIFIC")) (nil "linespecific")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ZûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+'U(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ûR«ûI(attlist (("PAGENUM" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
UûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û*

Ä
ÄŽ´³
e
e
Ž
eŽ´
e
e(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
mÈ(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ú

ú
(attlist (("CLASS" (name-token-group ("COMMAND" "FUNCTION" "OPTION" "PARAMETER")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:›K¬ˆc¶
-É(attlist (("ENDTERM" IDREF IMPLIED) ("LINKEND" IDREF REQUIRED) ("TYPE" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("APPLICATION" (NOTATION ("BMP" "CGM-CHAR" "CGM-BINARY" "CGM-CLEAR" "DITROFF" "DVI" "EPS" "EQN" "FAX" "GIF" "GIF87A" "GIF89A" "JPG" "JPEG" "IGES" "PCX" "PIC" "PS" "SGML" "TBL" "TEX" "TIFF" "WMF" "WPG" "LINESPECIFIC")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
]
!¥¥!
!
¥(attlist (("SPACING" (name-token-group ("NORMAL" "COMPACT")) IMPLIED) ("MARK" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û\

û\
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
I�––�II�–(attlist (("DEFAULTLABEL" (name-token-group ("QANDA" "NUMBER" "NONE")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€(�
Ç
Ò
±
l
Q
2
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
ûb
ˆ
û
¬
â

ÄûW•'
â
¬
û
ˆ
ûb
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
2
Q
l
±
Ò
Ç
�
ûW•(�
Ç
Ò
±
l
Q
2
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
ûb
ˆ
û
¬
â

´ûW•
ûW
•'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬âûW•(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("CLASS" (name-token-group ("HARDWARE" "SOFTWARE")) IMPLIED) ("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:›K¬ˆ¶
-Éñðû(attlist (("COLS" NUMBER REQUIRED) ("TGROUPSTYLE" NMTOKEN IMPLIED) ("COLNAME" NMTOKEN IMPLIED) ("SPANNAME" NMTOKEN IMPLIED) ("NAMEST" NMTOKEN IMPLIED) ("NAMEEND" NMTOKEN IMPLIED) ("COLSEP" NUMBER IMPLIED) ("ROWSEP" NUMBER IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER" "JUSTIFY" "CHAR")) IMPLIED) ("CHAR" CDATA IMPLIED) ("CHAROFF" NUTOKEN IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-ے
ÝO
o
oí
Ý
o
Ü(attlist (("NAMEST" NMTOKEN REQUIRED) ("NAMEEND" NMTOKEN REQUIRED) ("SPANNAME" NMTOKEN REQUIRED) ("COLSEP" NUMBER IMPLIED) ("ROWSEP" NUMBER IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER" "JUSTIFY" "CHAR")) IMPLIED) ("CHAR" CDATA IMPLIED) ("CHAROFF" NUTOKEN IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
¨

Û(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:›K¬ˆ¶
-Éñðû(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID REQUIRED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€û
%
%
û
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
–
�
I
û
q


k
2
Q
l
±
Ò
Ç
�
�
Ç
Ò
±
l
Q
2
k


q
û
I
�
–

šw€Á(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
4覆§ûSûE45´Ä³ä6Íà<û
û,û#ûTJûFÎî‡	ûY‘_`Yûïf²ûûcûNœ=b*ûdÓß(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€6“
F�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û*ÄF“

F4“
F1†Óâ¬ûˆÔ‹ûb,Á€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂûûqk2Ql±ÒÇ�
Ä6“
F�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1´³4“
F�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†15“
F�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1´
(attlist (("FPI" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€@
[Ä
~
~
@

~@
[´³
~¤~@
[
~@
[´
~(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("RELATION" CDATA IMPLIED) ("ROLE" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED)))
-€
4覆§ûSûE45´Ä³ä6Íà<û
û,û#ûTJûFÎî‡	ûY‘_`Yûïf²ûûcûNœ=b*ûdÓß(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ê"û:È(attlist (("LINKENDS" IDREFS IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("SRCCREDIT" CDATA IMPLIED) ("PAGENUM" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("LINKEND" IDREF IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("VALIGN" (name-token-group ("TOP" "MIDDLE" "BOTTOM")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
O
ûH

ûH

Ü(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("CLASS" (name-token-group ("SERVICE" "TRADE" "REGISTERED" "COPYRIGHT")) (nil "Trade")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<ð"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
2’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|(attlist (("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û*

Ä
Ä9´³6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0e	û1
-6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0e	û1
-
96�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0e	û1
-9´6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0e	û1
-6û1e
û0�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
û0

e	
û1
-û0
eû1
e


û0(attlist (("COLNAME" NMTOKEN IMPLIED) ("NAMEST" NMTOKEN IMPLIED) ("NAMEEND" NMTOKEN IMPLIED) ("SPANNAME" NMTOKEN IMPLIED) ("MOREROWS" NUMBER IMPLIED) ("COLSEP" NUMBER IMPLIED) ("ROWSEP" NUMBER IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER" "JUSTIFY" "CHAR")) IMPLIED) ("CHAR" CDATA IMPLIED) ("CHAROFF" NUTOKEN IMPLIED) ("ROTATE" NUMBER IMPLIED) ("VALIGN" (name-token-group ("TOP" "MIDDLE" "BOTTOM")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€o
+
÷
ß
û
û	
Þ

ð

û
.
·
n
d
ñ
˜
É

-
¶
|
Ú
û=
û
ž
?
Ö
µ
­
#
Õ
ûU
m
ûe
û_
y
é
ö
�
û

û
Ð
û.
Œ
õ
½
ûA
¼

>
x
û

û
c
g
¡
û
È
Z
—
u
û;
7
û'
û-
L
-
’
ˆ
b
œ
Y
Ï

û#
û,
6
¬
K
›
û:
"
ûK

 
ûJ

¥!–�Iû^û"tÂûûqk2Ql±ÒÇ�X
ûJ
 

ûK
"
û:
›
K
¬
6
û,
û#

Ï
Y
œ
b
ˆ
’
-
L
û-
û'
7
û;
u
—
Z
È
û
¡
g
c
û

û
x
>

¼
ûA
½
õ
Œ
û.
Ð
û
û

�
ö
é
y
û_
ûe
m
ûU
Õ
#
­
µ
Ö
?
ž
û
û=
Ú
|
¶

-
É
˜
ñ
d
n
·
.
û

ð

Þ
û	
û
ß
÷
+

�ÇÒ±lQ2kqûûÂtû"û^I�–!¥(attlist (("ACTION" (name-token-group ("CLICK" "DOUBLE-CLICK" "PRESS" "SEQ" "SIMUL" "OTHER")) IMPLIED) ("OTHERACTION" CDATA IMPLIED) ("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€û
½
õ
û.
û.
õ
½
û
(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ê"û:È(attlist (("ENDTERM" IDREF IMPLIED) ("LINKEND" IDREF REQUIRED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
&

¹
¹(attlist (("SORTAS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
.
6ßûûDûD6ûD6ûD6ßûD
D(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ACTION" (name-token-group ("CLICK" "DOUBLE-CLICK" "PRESS" "SEQ" "SIMUL" "OTHER")) IMPLIED) ("OTHERACTION" CDATA IMPLIED) ("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€û
½
õ
û.
û.
õ
½
û
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä


(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
2’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("CHOICE" (name-token-group ("OPT" "REQ" "PLAIN" "OPTMULT" "REQMULT")) (nil "Opt")) ("REP" (name-token-group ("NOREPEAT" "REPEAT")) (nil "Norepeat")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€r
È
û
û
û
%
%
û
û
û
È
r
(attlist (("OTHERTERM" IDREF CONREF) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("LABEL" CDATA IMPLIED) ("LINKEND" IDREF IMPLIED) ("PAGENUM" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€	4�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

û*Äû(ú2
1
†
Ó
â
¬
û
ˆ
Ô
‹
ûb
,
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
û
q


k
2
Q
l
±
Ò
Ç
�
û(ú
Ä4�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

´³û(úû6û(û6ú2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û(ú3�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

´û(ú(attlist (("LINKEND" IDREF REQUIRED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("LINKENDS" IDREFS IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("CLASS" (name-token-group ("BUTTON" "ICON" "MENU" "MENUITEM")) IMPLIED) ("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
=Ê"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:›K¬ˆ¶
-Éñðû
û(attlist (("RENDERAS" (name-token-group ("SECT1" "SECT2" "SECT3" "SECT4")) IMPLIED) ("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S

Ä
Ä@åûû6´³4�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû6ûå@4�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1e@åûû64�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1e@åûû6´4�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1e9@		å	û	û6	e
-�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1@		å	û	û6	e@		å	û	û6	û6	û	å		@	@		å	û	û6	e
-@		å	û	û6	(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ûa
'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬â'â¬ûˆûbÁ€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂû2Ql±ÒÇ�'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬â(attlist (("RENDERAS" (name-token-group ("OTHER" "SECT1" "SECT2" "SECT3" "SECT4" "SECT5")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
UûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("WIDTH" NUMBER IMPLIED) ("FORMAT" (NOTATION ("LINESPECIFIC")) (nil "linespecific")) ("CLASS" (name-token-group ("MONOSPACED" "NORMAL")) (nil "Normal")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
YûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+'(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬'¬ûˆ‹ûbÁ€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂû2Ql±ÒÇ�'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûb‹ˆû¬kqû(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä

X
Xû5û(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û@
©û@

©(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
\


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("RENDERAS" (name-token-group ("SECT1" "SECT2" "SECT3" "SECT5")) IMPLIED) ("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
£

Ä
Ä@åûû6´³5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû	û6ûå@5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû	@åûû65�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû	@åûû6´5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû	:@
-
-å
-û
-û6
-eû
�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1@
-
-å
-û
-û6
-e@
-
-å
-û
-û6
-û@
-
-å
-û
-û6
-	û6
-û
-å
-
-@
-@
-
-å
-û
-û6
-
ûe@
-
-å
-û
-û6
-û@
-
-å
-û
-û6
-
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€û8
Ä2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†12�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
û8
2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†12�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1(attlist (("WIDTH" NUMBER IMPLIED) ("FORMAT" (NOTATION ("LINESPECIFIC")) (nil "linespecific")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ZûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+'U(attlist (("CLASS" (name-token-group ("SERVICE" "TRADE" "REGISTERED" "COPYRIGHT")) (nil "Trade")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("RENDERAS" (name-token-group ("SECT1" "SECT2" "SECT4" "SECT5")) IMPLIED) ("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ø

Ä
Ä@åûû6´³5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû	û6ûå@5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû	@åûû65�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû	@åûû6´5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû	:@
-
-å
-û
-û6
-eû
�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1@
-
-å
-û
-û6
-e@
-
-å
-û
-û6
-û@
-
-å
-û
-û6
-	û6
-û
-å
-
-@
-@
-
-å
-û
-û6
-
ûe@
-
-å
-û
-û6
-û@
-
-å
-û
-û6
-
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ûD

ûD
(attlist (("CLASS" (name-token-group ("CONSTANT" "ENVIRONVAR" "MACRO" "OSNAME" "PROMPT" "RESOURCE" "SYSTEMNAME")) IMPLIED) ("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
=û"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
4�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1´³
ú21†Óâ¬ûˆÔ‹ûb,Á€wšûQsPÑE¥)!û!ûd–�IûJ û^û"tÂûûqk2Ql±ÒÇ�
ú2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
ú3�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1´
ú
ú(attlist (("RENDERAS" (name-token-group ("SECT1" "SECT3" "SECT4" "SECT5")) IMPLIED) ("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ûV

Ä
Ä@åûû6´³5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû$	û6ûå@5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû$	@åûû65�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû$	@åûû6´5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû$	:@
-
-å
-û
-û6
-eû$
�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1@
-
-å
-û
-û6
-e@
-
-å
-û
-û6
-û$@
-
-å
-û
-û6
-	û6
-û
-å
-
-@
-@
-
-å
-û
-û6
-
û$e@
-
-å
-û
-û6
-û$@
-
-å
-û
-û6
-
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€2
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß
2ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦

(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€



Ä
Ä@åûû6´³4�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû0û6ûå@4�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû0@åûû64�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû0@åûû6´4�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû09@		å	û	û6	e
-û0�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1@		å	û	û6	e@		å	û	û6	û0û6	û	å		@	@		å	û	û6	û0e
-@		å	û	û6	û0(attlist (("RENDERAS" (name-token-group ("SECT2" "SECT3" "SECT4" "SECT5")) IMPLIED) ("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
N

Ä
Ä@åûû6´³5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû)	û6ûå@5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû)	@åûû65�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû)	@åûû6´5�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1eû)	:@
-
-å
-û
-û6
-eû)
�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1@
-
-å
-û
-û6
-e@
-
-å
-û
-û6
-û)@
-
-å
-û
-û6
-	û6
-û
-å
-
-@
-@
-
-å
-û
-û6
-
û)e@
-
-å
-û
-û6
-û)@
-
-å
-û
-û6
-
(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
�ÇÒ±lQ2kqûûÂtû"û^I�–û!´³�ÇÒ±lQ2kqûûÂtû"û^I�–û!�ÇÒ±lQ2kqûûÂtû"û^I�–û!�ÇÒ±lQ2kqûûÂtû"û^I�–û!
´�ÇÒ±lQ2kqûûÂtû"û^I�–û!(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä


(attlist (("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€4�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

û*ÄGã2
1
†
Ó
â
¬
û
ˆ
Ô
‹
ûb
,
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
û
q


k
2
Q
l
±
Ò
Ç
�
Gã
Ä4�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

´³Gã
Gã2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1Gã3�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

´Gã(attlist (("SORTAS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ä
�ÇÒ±lQ2kqûûÂtû"û^I�–û!û!–�Iû^û"tÂûûqk2Ql±ÒÇ��ÇÒ±lQ2kqûûÂtû"û^I�–û!šw€Á(attlist (("ENTITYREF" ENTITY IMPLIED) ("FILEREF" CDATA IMPLIED) ("FORMAT" (NOTATION ("BMP" "CGM-CHAR" "CGM-BINARY" "CGM-CLEAR" "DITROFF" "DVI" "EPS" "EQN" "FAX" "GIF" "GIF87A" "GIF89A" "JPG" "JPEG" "IGES" "PCX" "PIC" "PS" "SGML" "TBL" "TEX" "TIFF" "WMF" "WPG" "LINESPECIFIC")) IMPLIED) ("SRCCREDIT" CDATA IMPLIED) ("WIDTH" NUTOKEN IMPLIED) ("DEPTH" NUTOKEN IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER")) IMPLIED) ("SCALE" NUMBER IMPLIED) ("SCALEFIT" NUMBER IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("LABEL" CDATA IMPLIED) ("LINKEND" IDREF IMPLIED) ("PAGENUM" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ú(attlist (("CLASS" (name-token-group ("JOURNALARTICLE" "PRODUCTSHEET" "WHITEPAPER" "TECHREPORT" "FAQ")) IMPLIED) ("PARENTBOOK" IDREF IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
9 Ä6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	

6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	
6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	
96�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	
9 ´
-³6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	=@åûû6óªû1
eû0�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1@åûû6óªû0@åûû6óª@åûû6óªe@åûû6óªû1	
9 6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	
9 ´
-6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0eû1	ªóû6ûå@@åûû6óªû0eû1
@åûû6óªe@åûû6óª@åûû6óªû0(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
¨
Û


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
º

B
�(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ROWSEP" NUMBER IMPLIED) ("VALIGN" (name-token-group ("TOP" "MIDDLE" "BOTTOM")) IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-ۆ
ô
ô
Ü
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:È(attlist (("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
ûM
û`ÆÆû`ûMû`aìØûMÆaûMÆ(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
]
!""!
!
"(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
8
98

9(attlist (("FORMAT" (NOTATION ("LINESPECIFIC")) (nil "linespecific")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
="û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É'(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ENTITYREF" ENTITY IMPLIED) ("FILEREF" CDATA IMPLIED) ("FORMAT" (name-token-group ("BMP" "CGM-CHAR" "CGM-BINARY" "CGM-CLEAR" "DITROFF" "DVI" "EPS" "EQN" "FAX" "GIF" "GIF87A" "GIF89A" "JPG" "JPEG" "IGES" "PCX" "PIC" "PS" "SGML" "TBL" "TEX" "TIFF" "WMF" "WPG" "LINESPECIFIC")) IMPLIED) ("SRCCREDIT" CDATA IMPLIED) ("WIDTH" NUTOKEN IMPLIED) ("DEPTH" NUTOKEN IMPLIED) ("ALIGN" (name-token-group ("LEFT" "RIGHT" "CENTER")) IMPLIED) ("SCALE" NUMBER IMPLIED) ("SCALEFIT" NUMBER IMPLIED) ("ROLE" CDATA IMPLIED)))
-(attlist (("FRAME" (name-token-group ("TOP" "BOTTOM" "TOPBOT" "ALL" "SIDES" "NONE")) IMPLIED) ("COLSEP" NUMBER IMPLIED) ("ROWSEP" NUMBER IMPLIED) ("TABSTYLE" NMTOKEN IMPLIED) ("TOCENTRY" NUMBER IMPLIED) ("SHORTENTRY" NUMBER IMPLIED) ("ORIENT" (name-token-group ("PORT" "LAND")) IMPLIED) ("PGWIDE" NUMBER IMPLIED) ("LABEL" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€0
¥!
0

¥
!ûQšw€Á(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€

"û:›K¬Èñð¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€–
�
I
I
�
–
(attlist (("CLASS" (name-token-group ("HEADERFILE" "SYMLINK" "DIRECTORY")) IMPLIED) ("PATH" CDATA IMPLIED) ("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
<"û:›K¬ˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-É(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€9
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß

û&

Ï
û9
¥
!
9!
¥
û9
Ï

û&

ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦


(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€(�
Ç
Ò
±
l
Q
2
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
ûb
ˆ
û
¬
â

ÄûW•'
â
¬
û
ˆ
ûb
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
2
Q
l
±
Ò
Ç
�
ûW•(�
Ç
Ò
±
l
Q
2
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
ûb
ˆ
û
¬
â

´ûW•
ûW
•'�ÇÒ±lQ2ûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Áûbˆû¬âûW•(attlist (("WEIGHT" NUMBER IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
^

^
(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€¦
†

§

ûS
ûE
4
4
ûE
ûS

§

†
¦
(attlist (("LINKEND" IDREF IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
S"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("LABEL" CDATA IMPLIED) ("STATUS" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û*

Ä
Ä9´³6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0e	û1
-6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0e	û1
-
96�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0e	û1
-9´6�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1û0e	û1
-9åûû6û1e
û0�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1åûû6û0åûû6åûû6e	åûû6û1
-û6ûååûû6û0e
û1åûû6e
åûû6åûû6û0(attlist (("OVERRIDE" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€2
1
†
Ó
â
¬
û
ˆ
Ô
‹
ûb
,
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
û
q


k
2
Q
l
±
Ò
Ç
�
2�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

(attlist (("OTHERTERM" IDREF CONREF) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
XûJ ûK"û:›K¬6û,û#ÏYœbˆ’-Lû-û'7û;u—ZÈû¡gcûûx>¼ûA½õŒû.Ðûû
�öéyû_ûemûUÕ#­µÖ?žûû=Ú|¶
-ɘñdn·.ûðÞû	ûß÷+(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ù
!)¥EE¥)!(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ê"û:È(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Æ
aìØ
a(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
"û:›K¬ˆ¶
-Éñðû(attlist (("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€3�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

Ä
(2
1
†
Ó
â
¬
û
ˆ
Ô
‹
ûb
,
Á
€
w
š
ûQ
s
P
Ñ
E
¥
)
!
û!
ûd
–
�
I
ûJ
 

û^

û"
t
Â
û
û
q


k
2
Q
l
±
Ò
Ç
�

(3�
Ç
Ò
±
l
Q
2
k


q
û
û
Â
t
û"

û^

 
ûJ
I
�
–
ûd
û!
!
)
¥
E
Ñ
P
s
ûQ
š
w
€
Á
,
ûb
‹
Ô
ˆ
û
¬
â
Ó
†
1

´
(
(2�ÇÒ±lQ2kqûûÂtû"û^ ûJI�–ûdû!!)¥EÑPsûQšw€Á,ûb‹Ôˆû¬âÓ†1
((attlist (("RELATION" CDATA IMPLIED) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€2
¦
†

§

ûS
ûE
4

5
´
Ä
³
ä
6
Í

à
<
û

û,
û#
ûT
J

ûF
Î
î
‡
	
ûY
‘
_
`
Y
û
ï
f
²
û
ûc
ûN
œ
=
b
*
ûd
Ó
ß
2ß
Ó
ûd
*
b
=
œ
ûN
ûc
û
²
f
ï
û
Y
`
_
‘
ûY
	
‡
î
Î
ûF

J
ûT
û#
û,
û

<
à

Í
6
ä
³
Ä
´
5

4
ûE
ûS

§

†
¦

(attlist (("FORMAT" (NOTATION ("LINESPECIFIC")) (nil "linespecific")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
û ÖûÌûOATûG¦†§ûSûE4(attlist (("MOREINFO" (name-token-group ("REFENTRY" "NONE")) (nil "None")) ("ID" ID IMPLIED) ("LANG" CDATA IMPLIED) ("REMAP" CDATA IMPLIED) ("XREFLABEL" CDATA IMPLIED) ("REVISIONFLAG" (name-token-group ("CHANGED" "ADDED" "DELETED" "OFF")) IMPLIED) ("ARCH" CDATA IMPLIED) ("CONFORMANCE" NMTOKENS IMPLIED) ("OS" CDATA IMPLIED) ("REVISION" CDATA IMPLIED) ("USERLEVEL" CDATA IMPLIED) ("VENDOR" CDATA IMPLIED) ("ROLE" CDATA IMPLIED)))
-€
Ê"û:È(nil ("biblio" text (nil "biblio.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("cvs" text (nil "cvs.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("glossary" text (nil "glossary.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("building" text (nil "building.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("configuration" text (nil "configuration.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("corba" text (nil "corba.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("framework" text (nil "framework.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("hardware" text (nil "hardware.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("projects" text (nil "projects.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("release" text (nil "release.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("servers" text (nil "servers.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("telemetry" text (nil "telemetry.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("ilu" text (nil "ilu.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("java" text (nil "java.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("mico" text (nil "mico.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("postgres" text (nil "postgres.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("tao" text (nil "tao.sgml" . "/home/lockhart/build/1.4/rtc/doc/sgml/") nil) ("cularr" SDATA "[cularr]" nil) ("curarr" SDATA "[curarr]" nil) ("dArr" SDATA "[dArr  ]" nil) ("darr2" SDATA "[darr2 ]" nil) ("dharl" SDATA "[dharl ]" nil) ("dharr" SDATA "[dharr ]" nil) ("lAarr" SDATA "[lAarr ]" nil) ("Larr" SDATA "[Larr  ]" nil) ("larr2" SDATA "[larr2 ]" nil) ("larrhk" SDATA "[larrhk]" nil) ("larrlp" SDATA "[larrlp]" nil) ("larrtl" SDATA "[larrtl]" nil) ("lhard" SDATA "[lhard ]" nil) ("lharu" SDATA "[lharu ]" nil) ("hArr" SDATA "[hArr  ]" nil) ("harr" SDATA "[harr  ]" nil) ("lrarr2" SDATA "[lrarr2]" nil) ("rlarr2" SDATA "[rlarr2]" nil) ("harrw" SDATA "[harrw ]" nil) ("rlhar2" SDATA "[rlhar2]" nil) ("lrhar2" SDATA "[lrhar2]" nil) ("lsh" SDATA "[lsh   ]" nil) ("map" SDATA "[map   ]" nil) ("mumap" SDATA "[mumap ]" nil) ("nearr" SDATA "[nearr ]" nil) ("nlArr" SDATA "[nlArr ]" nil) ("nlarr" SDATA "[nlarr ]" nil) ("nhArr" SDATA "[nhArr ]" nil) ("nharr" SDATA "[nharr ]" nil) ("nrarr" SDATA "[nrarr ]" nil) ("nrArr" SDATA "[nrArr ]" nil) ("nwarr" SDATA "[nwarr ]" nil) ("olarr" SDATA "[olarr ]" nil) ("orarr" SDATA "[orarr ]" nil) ("rAarr" SDATA "[rAarr ]" nil) ("Rarr" SDATA "[Rarr  ]" nil) ("rarr2" SDATA "[rarr2 ]" nil) ("rarrhk" SDATA "[rarrhk]" nil) ("rarrlp" SDATA "[rarrlp]" nil) ("rarrtl" SDATA "[rarrtl]" nil) ("rarrw" SDATA "[rarrw ]" nil) ("rhard" SDATA "[rhard ]" nil) ("rharu" SDATA "[rharu ]" nil) ("rsh" SDATA "[rsh   ]" nil) ("drarr" SDATA "[drarr ]" nil) ("dlarr" SDATA "[dlarr ]" nil) ("uArr" SDATA "[uArr  ]" nil) ("uarr2" SDATA "[uarr2 ]" nil) ("vArr" SDATA "[vArr  ]" nil) ("varr" SDATA "[varr  ]" nil) ("uharl" SDATA "[uharl ]" nil) ("uharr" SDATA "[uharr ]" nil) ("xlArr" SDATA "[xlArr ]" nil) ("xhArr" SDATA "[xhArr ]" nil) ("xharr" SDATA "[xharr ]" nil) ("xrArr" SDATA "[xrArr ]" nil) ("amalg" SDATA "[amalg ]" nil) ("Barwed" SDATA "[Barwed]" nil) ("barwed" SDATA "[barwed]" nil) ("Cap" SDATA "[Cap   ]" nil) ("Cup" SDATA "[Cup   ]" nil) ("cuvee" SDATA "[cuvee ]" nil) ("cuwed" SDATA "[cuwed ]" nil) ("diam" SDATA "[diam  ]" nil) ("divonx" SDATA "[divonx]" nil) ("intcal" SDATA "[intcal]" nil) ("lthree" SDATA "[lthree]" nil) ("ltimes" SDATA "[ltimes]" nil) ("minusb" SDATA "[minusb]" nil) ("oast" SDATA "[oast  ]" nil) ("ocir" SDATA "[ocir  ]" nil) ("odash" SDATA "[odash ]" nil) ("odot" SDATA "[odot  ]" nil) ("ominus" SDATA "[ominus]" nil) ("oplus" SDATA "[oplus ]" nil) ("osol" SDATA "[osol  ]" nil) ("otimes" SDATA "[otimes]" nil) ("plusb" SDATA "[plusb ]" nil) ("plusdo" SDATA "[plusdo]" nil) ("rthree" SDATA "[rthree]" nil) ("rtimes" SDATA "[rtimes]" nil) ("sdot" SDATA "[sdot  ]" nil) ("sdotb" SDATA "[sdotb ]" nil) ("setmn" SDATA "[setmn ]" nil) ("sqcap" SDATA "[sqcap ]" nil) ("sqcup" SDATA "[sqcup ]" nil) ("ssetmn" SDATA "[ssetmn]" nil) ("sstarf" SDATA "[sstarf]" nil) ("timesb" SDATA "[timesb]" nil) ("top" SDATA "[top   ]" nil) ("uplus" SDATA "[uplus ]" nil) ("wreath" SDATA "[wreath]" nil) ("xcirc" SDATA "[xcirc ]" nil) ("xdtri" SDATA "[xdtri ]" nil) ("xutri" SDATA "[xutri ]" nil) ("coprod" SDATA "[coprod]" nil) ("prod" SDATA "[prod  ]" nil) ("sum" SDATA "[sum   ]" nil) ("rceil" SDATA "[rceil ]" nil) ("rfloor" SDATA "[rfloor]" nil) ("rpargt" SDATA "[rpargt]" nil) ("urcorn" SDATA "[urcorn]" nil) ("drcorn" SDATA "[drcorn]" nil) ("lceil" SDATA "[lceil ]" nil) ("lfloor" SDATA "[lfloor]" nil) ("lpargt" SDATA "[lpargt]" nil) ("ulcorn" SDATA "[ulcorn]" nil) ("dlcorn" SDATA "[dlcorn]" nil) ("gnap" SDATA "[gnap  ]" nil) ("gne" SDATA "[gne   ]" nil) ("gnE" SDATA "[gnE   ]" nil) ("gnsim" SDATA "[gnsim ]" nil) ("gvnE" SDATA "[gvnE  ]" nil) ("lnap" SDATA "[lnap  ]" nil) ("lnE" SDATA "[lnE   ]" nil) ("lne" SDATA "[lne   ]" nil) ("lnsim" SDATA "[lnsim ]" nil) ("lvnE" SDATA "[lvnE  ]" nil) ("nap" SDATA "[nap   ]" nil) ("ncong" SDATA "[ncong ]" nil) ("nequiv" SDATA "[nequiv]" nil) ("ngE" SDATA "[ngE   ]" nil) ("nge" SDATA "[nge   ]" nil) ("nges" SDATA "[nges  ]" nil) ("ngt" SDATA "[ngt   ]" nil) ("nle" SDATA "[nle   ]" nil) ("nlE" SDATA "[nlE   ]" nil) ("nles" SDATA "[nles  ]" nil) ("nlt" SDATA "[nlt   ]" nil) ("nltri" SDATA "[nltri ]" nil) ("nltrie" SDATA "[nltrie]" nil) ("nmid" SDATA "[nmid  ]" nil) ("npar" SDATA "[npar  ]" nil) ("npr" SDATA "[npr   ]" nil) ("npre" SDATA "[npre  ]" nil) ("nrtri" SDATA "[nrtri ]" nil) ("nrtrie" SDATA "[nrtrie]" nil) ("nsc" SDATA "[nsc   ]" nil) ("nsce" SDATA "[nsce  ]" nil) ("nsim" SDATA "[nsim  ]" nil) ("nsime" SDATA "[nsime ]" nil) ("nsmid" SDATA "[nsmid ]" nil) ("nspar" SDATA "[nspar ]" nil) ("nsub" SDATA "[nsub  ]" nil) ("nsube" SDATA "[nsube ]" nil) ("nsubE" SDATA "[nsubE ]" nil) ("nsup" SDATA "[nsup  ]" nil) ("nsupE" SDATA "[nsupE ]" nil) ("nsupe" SDATA "[nsupe ]" nil) ("nvdash" SDATA "[nvdash]" nil) ("nvDash" SDATA "[nvDash]" nil) ("nVDash" SDATA "[nVDash]" nil) ("nVdash" SDATA "[nVdash]" nil) ("prnap" SDATA "[prnap ]" nil) ("prnE" SDATA "[prnE  ]" nil) ("prnsim" SDATA "[prnsim]" nil) ("scnap" SDATA "[scnap ]" nil) ("scnE" SDATA "[scnE  ]" nil) ("scnsim" SDATA "[scnsim]" nil) ("subne" SDATA "[subne ]" nil) ("subnE" SDATA "[subnE ]" nil) ("supne" SDATA "[supne ]" nil) ("supnE" SDATA "[supnE ]" nil) ("vsubnE" SDATA "[vsubnE]" nil) ("vsubne" SDATA "[vsubne]" nil) ("vsupne" SDATA "[vsupne]" nil) ("vsupnE" SDATA "[vsupnE]" nil) ("ang" SDATA "[ang   ]" nil) ("angmsd" SDATA "[angmsd]" nil) ("beth" SDATA "[beth  ]" nil) ("bprime" SDATA "[bprime]" nil) ("comp" SDATA "[comp  ]" nil) ("daleth" SDATA "[daleth]" nil) ("ell" SDATA "[ell   ]" nil) ("empty" SDATA "[empty ]" nil) ("gimel" SDATA "[gimel ]" nil) ("image" SDATA "[image ]" nil) ("inodot" SDATA "[inodot]" nil) ("jnodot" SDATA "[jnodot]" nil) ("nexist" SDATA "[nexist]" nil) ("oS" SDATA "[oS    ]" nil) ("planck" SDATA "[planck]" nil) ("real" SDATA "[real  ]" nil) ("sbsol" SDATA "[sbsol ]" nil) ("vprime" SDATA "[vprime]" nil) ("weierp" SDATA "[weierp]" nil) ("ape" SDATA "[ape   ]" nil) ("asymp" SDATA "[asymp ]" nil) ("bcong" SDATA "[bcong ]" nil) ("bepsi" SDATA "[bepsi ]" nil) ("bowtie" SDATA "[bowtie]" nil) ("bsim" SDATA "[bsim  ]" nil) ("bsime" SDATA "[bsime ]" nil) ("bump" SDATA "[bump  ]" nil) ("bumpe" SDATA "[bumpe ]" nil) ("cire" SDATA "[cire  ]" nil) ("colone" SDATA "[colone]" nil) ("cuepr" SDATA "[cuepr ]" nil) ("cuesc" SDATA "[cuesc ]" nil) ("cupre" SDATA "[cupre ]" nil) ("dashv" SDATA "[dashv ]" nil) ("ecir" SDATA "[ecir  ]" nil) ("ecolon" SDATA "[ecolon]" nil) ("eDot" SDATA "[eDot  ]" nil) ("esdot" SDATA "[esdot ]" nil) ("efDot" SDATA "[efDot ]" nil) ("egs" SDATA "[egs   ]" nil) ("els" SDATA "[els   ]" nil) ("erDot" SDATA "[erDot ]" nil) ("fork" SDATA "[fork  ]" nil) ("frown" SDATA "[frown ]" nil) ("gap" SDATA "[gap   ]" nil) ("gsdot" SDATA "[gsdot ]" nil) ("gE" SDATA "[gE    ]" nil) ("gel" SDATA "[gel   ]" nil) ("gEl" SDATA "[gEl   ]" nil) ("ges" SDATA "[ges   ]" nil) ("Gg" SDATA "[Gg    ]" nil) ("gl" SDATA "[gl    ]" nil) ("gsim" SDATA "[gsim  ]" nil) ("Gt" SDATA "[Gt    ]" nil) ("lap" SDATA "[lap   ]" nil) ("ldot" SDATA "[ldot  ]" nil) ("lE" SDATA "[lE    ]" nil) ("lEg" SDATA "[lEg   ]" nil) ("leg" SDATA "[leg   ]" nil) ("les" SDATA "[les   ]" nil) ("lg" SDATA "[lg    ]" nil) ("Ll" SDATA "[Ll    ]" nil) ("lsim" SDATA "[lsim  ]" nil) ("Lt" SDATA "[Lt    ]" nil) ("ltrie" SDATA "[ltrie ]" nil) ("mid" SDATA "[mid   ]" nil) ("models" SDATA "[models]" nil) ("pr" SDATA "[pr    ]" nil) ("prap" SDATA "[prap  ]" nil) ("pre" SDATA "[pre   ]" nil) ("prsim" SDATA "[prsim ]" nil) ("rtrie" SDATA "[rtrie ]" nil) ("samalg" SDATA "[samalg]" nil) ("sc" SDATA "[sc    ]" nil) ("scap" SDATA "[scap  ]" nil) ("sccue" SDATA "[sccue ]" nil) ("sce" SDATA "[sce   ]" nil) ("scsim" SDATA "[scsim ]" nil) ("sfrown" SDATA "[sfrown]" nil) ("smid" SDATA "[smid  ]" nil) ("smile" SDATA "[smile ]" nil) ("spar" SDATA "[spar  ]" nil) ("sqsub" SDATA "[sqsub ]" nil) ("sqsube" SDATA "[sqsube]" nil) ("sqsup" SDATA "[sqsup ]" nil) ("sqsupe" SDATA "[sqsupe]" nil) ("ssmile" SDATA "[ssmile]" nil) ("Sub" SDATA "[Sub   ]" nil) ("subE" SDATA "[subE  ]" nil) ("Sup" SDATA "[Sup   ]" nil) ("supE" SDATA "[supE  ]" nil) ("thkap" SDATA "[thkap ]" nil) ("thksim" SDATA "[thksim]" nil) ("trie" SDATA "[trie  ]" nil) ("twixt" SDATA "[twixt ]" nil) ("vdash" SDATA "[vdash ]" nil) ("Vdash" SDATA "[Vdash ]" nil) ("vDash" SDATA "[vDash ]" nil) ("veebar" SDATA "[veebar]" nil) ("vltri" SDATA "[vltri ]" nil) ("vprop" SDATA "[vprop ]" nil) ("vrtri" SDATA "[vrtri ]" nil) ("Vvdash" SDATA "[Vvdash]" nil) ("boxh" SDATA "[boxh  ]" nil) ("boxv" SDATA "[boxv  ]" nil) ("boxur" SDATA "[boxur ]" nil) ("boxul" SDATA "[boxul ]" nil) ("boxdl" SDATA "[boxdl ]" nil) ("boxdr" SDATA "[boxdr ]" nil) ("boxvr" SDATA "[boxvr ]" nil) ("boxhu" SDATA "[boxhu ]" nil) ("boxvl" SDATA "[boxvl ]" nil) ("boxhd" SDATA "[boxhd ]" nil) ("boxvh" SDATA "[boxvh ]" nil) ("boxvR" SDATA "[boxvR ]" nil) ("boxhU" SDATA "[boxhU ]" nil) ("boxvL" SDATA "[boxvL ]" nil) ("boxhD" SDATA "[boxhD ]" nil) ("boxvH" SDATA "[boxvH ]" nil) ("boxH" SDATA "[boxH  ]" nil) ("boxV" SDATA "[boxV  ]" nil) ("boxUR" SDATA "[boxUR ]" nil) ("boxUL" SDATA "[boxUL ]" nil) ("boxDL" SDATA "[boxDL ]" nil) ("boxDR" SDATA "[boxDR ]" nil) ("boxVR" SDATA "[boxVR ]" nil) ("boxHU" SDATA "[boxHU ]" nil) ("boxVL" SDATA "[boxVL ]" nil) ("boxHD" SDATA "[boxHD ]" nil) ("boxVH" SDATA "[boxVH ]" nil) ("boxVr" SDATA "[boxVr ]" nil) ("boxHu" SDATA "[boxHu ]" nil) ("boxVl" SDATA "[boxVl ]" nil) ("boxHd" SDATA "[boxHd ]" nil) ("boxVh" SDATA "[boxVh ]" nil) ("boxuR" SDATA "[boxuR ]" nil) ("boxUl" SDATA "[boxUl ]" nil) ("boxdL" SDATA "[boxdL ]" nil) ("boxDr" SDATA "[boxDr ]" nil) ("boxUr" SDATA "[boxUr ]" nil) ("boxuL" SDATA "[boxuL ]" nil) ("boxDl" SDATA "[boxDl ]" nil) ("boxdR" SDATA "[boxdR ]" nil) ("acy" SDATA "[acy   ]" nil) ("Acy" SDATA "[Acy   ]" nil) ("bcy" SDATA "[bcy   ]" nil) ("Bcy" SDATA "[Bcy   ]" nil) ("vcy" SDATA "[vcy   ]" nil) ("Vcy" SDATA "[Vcy   ]" nil) ("gcy" SDATA "[gcy   ]" nil) ("Gcy" SDATA "[Gcy   ]" nil) ("dcy" SDATA "[dcy   ]" nil) ("Dcy" SDATA "[Dcy   ]" nil) ("iecy" SDATA "[iecy  ]" nil) ("IEcy" SDATA "[IEcy  ]" nil) ("iocy" SDATA "[iocy  ]" nil) ("IOcy" SDATA "[IOcy  ]" nil) ("zhcy" SDATA "[zhcy  ]" nil) ("ZHcy" SDATA "[ZHcy  ]" nil) ("zcy" SDATA "[zcy   ]" nil) ("Zcy" SDATA "[Zcy   ]" nil) ("icy" SDATA "[icy   ]" nil) ("Icy" SDATA "[Icy   ]" nil) ("jcy" SDATA "[jcy   ]" nil) ("Jcy" SDATA "[Jcy   ]" nil) ("kcy" SDATA "[kcy   ]" nil) ("Kcy" SDATA "[Kcy   ]" nil) ("lcy" SDATA "[lcy   ]" nil) ("Lcy" SDATA "[Lcy   ]" nil) ("mcy" SDATA "[mcy   ]" nil) ("Mcy" SDATA "[Mcy   ]" nil) ("ncy" SDATA "[ncy   ]" nil) ("Ncy" SDATA "[Ncy   ]" nil) ("ocy" SDATA "[ocy   ]" nil) ("Ocy" SDATA "[Ocy   ]" nil) ("pcy" SDATA "[pcy   ]" nil) ("Pcy" SDATA "[Pcy   ]" nil) ("rcy" SDATA "[rcy   ]" nil) ("Rcy" SDATA "[Rcy   ]" nil) ("scy" SDATA "[scy   ]" nil) ("Scy" SDATA "[Scy   ]" nil) ("tcy" SDATA "[tcy   ]" nil) ("Tcy" SDATA "[Tcy   ]" nil) ("ucy" SDATA "[ucy   ]" nil) ("Ucy" SDATA "[Ucy   ]" nil) ("fcy" SDATA "[fcy   ]" nil) ("Fcy" SDATA "[Fcy   ]" nil) ("khcy" SDATA "[khcy  ]" nil) ("KHcy" SDATA "[KHcy  ]" nil) ("tscy" SDATA "[tscy  ]" nil) ("TScy" SDATA "[TScy  ]" nil) ("chcy" SDATA "[chcy  ]" nil) ("CHcy" SDATA "[CHcy  ]" nil) ("shcy" SDATA "[shcy  ]" nil) ("SHcy" SDATA "[SHcy  ]" nil) ("shchcy" SDATA "[shchcy]" nil) ("SHCHcy" SDATA "[SHCHcy]" nil) ("hardcy" SDATA "[hardcy]" nil) ("HARDcy" SDATA "[HARDcy]" nil) ("ycy" SDATA "[ycy   ]" nil) ("Ycy" SDATA "[Ycy   ]" nil) ("softcy" SDATA "[softcy]" nil) ("SOFTcy" SDATA "[SOFTcy]" nil) ("ecy" SDATA "[ecy   ]" nil) ("Ecy" SDATA "[Ecy   ]" nil) ("yucy" SDATA "[yucy  ]" nil) ("YUcy" SDATA "[YUcy  ]" nil) ("yacy" SDATA "[yacy  ]" nil) ("YAcy" SDATA "[YAcy  ]" nil) ("numero" SDATA "[numero]" nil) ("djcy" SDATA "[djcy  ]" nil) ("DJcy" SDATA "[DJcy  ]" nil) ("gjcy" SDATA "[gjcy  ]" nil) ("GJcy" SDATA "[GJcy  ]" nil) ("jukcy" SDATA "[jukcy ]" nil) ("Jukcy" SDATA "[Jukcy ]" nil) ("dscy" SDATA "[dscy  ]" nil) ("DScy" SDATA "[DScy  ]" nil) ("iukcy" SDATA "[iukcy ]" nil) ("Iukcy" SDATA "[Iukcy ]" nil) ("yicy" SDATA "[yicy  ]" nil) ("YIcy" SDATA "[YIcy  ]" nil) ("jsercy" SDATA "[jsercy]" nil) ("Jsercy" SDATA "[Jsercy]" nil) ("ljcy" SDATA "[ljcy  ]" nil) ("LJcy" SDATA "[LJcy  ]" nil) ("njcy" SDATA "[njcy  ]" nil) ("NJcy" SDATA "[NJcy  ]" nil) ("tshcy" SDATA "[tshcy ]" nil) ("TSHcy" SDATA "[TSHcy ]" nil) ("kjcy" SDATA "[kjcy  ]" nil) ("KJcy" SDATA "[KJcy  ]" nil) ("ubrcy" SDATA "[ubrcy ]" nil) ("Ubrcy" SDATA "[Ubrcy ]" nil) ("dzcy" SDATA "[dzcy  ]" nil) ("DZcy" SDATA "[DZcy  ]" nil) ("acute" SDATA "[acute ]" nil) ("breve" SDATA "[breve ]" nil) ("caron" SDATA "[caron ]" nil) ("cedil" SDATA "[cedil ]" nil) ("circ" SDATA "[circ  ]" nil) ("dblac" SDATA "[dblac ]" nil) ("die" SDATA "[die   ]" nil) ("dot" SDATA "[dot   ]" nil) ("grave" SDATA "[grave ]" nil) ("macr" SDATA "[macr  ]" nil) ("ogon" SDATA "[ogon  ]" nil) ("ring" SDATA "[ring  ]" nil) ("tilde" SDATA "[tilde ]" nil) ("uml" SDATA "[uml   ]" nil) ("agr" SDATA "[agr   ]" nil) ("Agr" SDATA "[Agr   ]" nil) ("bgr" SDATA "[bgr   ]" nil) ("Bgr" SDATA "[Bgr   ]" nil) ("ggr" SDATA "[ggr   ]" nil) ("Ggr" SDATA "[Ggr   ]" nil) ("dgr" SDATA "[dgr   ]" nil) ("Dgr" SDATA "[Dgr   ]" nil) ("egr" SDATA "[egr   ]" nil) ("Egr" SDATA "[Egr   ]" nil) ("zgr" SDATA "[zgr   ]" nil) ("Zgr" SDATA "[Zgr   ]" nil) ("eegr" SDATA "[eegr  ]" nil) ("EEgr" SDATA "[EEgr  ]" nil) ("thgr" SDATA "[thgr  ]" nil) ("THgr" SDATA "[THgr  ]" nil) ("igr" SDATA "[igr   ]" nil) ("Igr" SDATA "[Igr   ]" nil) ("kgr" SDATA "[kgr   ]" nil) ("Kgr" SDATA "[Kgr   ]" nil) ("lgr" SDATA "[lgr   ]" nil) ("Lgr" SDATA "[Lgr   ]" nil) ("mgr" SDATA "[mgr   ]" nil) ("Mgr" SDATA "[Mgr   ]" nil) ("ngr" SDATA "[ngr   ]" nil) ("Ngr" SDATA "[Ngr   ]" nil) ("xgr" SDATA "[xgr   ]" nil) ("Xgr" SDATA "[Xgr   ]" nil) ("ogr" SDATA "[ogr   ]" nil) ("Ogr" SDATA "[Ogr   ]" nil) ("pgr" SDATA "[pgr   ]" nil) ("Pgr" SDATA "[Pgr   ]" nil) ("rgr" SDATA "[rgr   ]" nil) ("Rgr" SDATA "[Rgr   ]" nil) ("sgr" SDATA "[sgr   ]" nil) ("Sgr" SDATA "[Sgr   ]" nil) ("sfgr" SDATA "[sfgr  ]" nil) ("tgr" SDATA "[tgr   ]" nil) ("Tgr" SDATA "[Tgr   ]" nil) ("ugr" SDATA "[ugr   ]" nil) ("Ugr" SDATA "[Ugr   ]" nil) ("phgr" SDATA "[phgr  ]" nil) ("PHgr" SDATA "[PHgr  ]" nil) ("khgr" SDATA "[khgr  ]" nil) ("KHgr" SDATA "[KHgr  ]" nil) ("psgr" SDATA "[psgr  ]" nil) ("PSgr" SDATA "[PSgr  ]" nil) ("ohgr" SDATA "[ohgr  ]" nil) ("OHgr" SDATA "[OHgr  ]" nil) ("aacgr" SDATA "[aacgr ]" nil) ("Aacgr" SDATA "[Aacgr ]" nil) ("eacgr" SDATA "[eacgr ]" nil) ("Eacgr" SDATA "[Eacgr ]" nil) ("eeacgr" SDATA "[eeacgr]" nil) ("EEacgr" SDATA "[EEacgr]" nil) ("idigr" SDATA "[idigr ]" nil) ("Idigr" SDATA "[Idigr ]" nil) ("iacgr" SDATA "[iacgr ]" nil) ("Iacgr" SDATA "[Iacgr ]" nil) ("idiagr" SDATA "[idiagr]" nil) ("oacgr" SDATA "[oacgr ]" nil) ("Oacgr" SDATA "[Oacgr ]" nil) ("udigr" SDATA "[udigr ]" nil) ("Udigr" SDATA "[Udigr ]" nil) ("uacgr" SDATA "[uacgr ]" nil) ("Uacgr" SDATA "[Uacgr ]" nil) ("udiagr" SDATA "[udiagr]" nil) ("ohacgr" SDATA "[ohacgr]" nil) ("OHacgr" SDATA "[OHacgr]" nil) ("alpha" SDATA "[alpha ]" nil) ("beta" SDATA "[beta  ]" nil) ("gamma" SDATA "[gamma ]" nil) ("Gamma" SDATA "[Gamma ]" nil) ("gammad" SDATA "[gammad]" nil) ("delta" SDATA "[delta ]" nil) ("Delta" SDATA "[Delta ]" nil) ("epsi" SDATA "[epsi  ]" nil) ("epsiv" SDATA "[epsiv ]" nil) ("epsis" SDATA "[epsis ]" nil) ("zeta" SDATA "[zeta  ]" nil) ("eta" SDATA "[eta   ]" nil) ("thetas" SDATA "[thetas]" nil) ("Theta" SDATA "[Theta ]" nil) ("thetav" SDATA "[thetav]" nil) ("iota" SDATA "[iota  ]" nil) ("kappa" SDATA "[kappa ]" nil) ("kappav" SDATA "[kappav]" nil) ("lambda" SDATA "[lambda]" nil) ("Lambda" SDATA "[Lambda]" nil) ("mu" SDATA "[mu    ]" nil) ("nu" SDATA "[nu    ]" nil) ("xi" SDATA "[xi    ]" nil) ("Xi" SDATA "[Xi    ]" nil) ("pi" SDATA "[pi    ]" nil) ("piv" SDATA "[piv   ]" nil) ("Pi" SDATA "[Pi    ]" nil) ("rho" SDATA "[rho   ]" nil) ("rhov" SDATA "[rhov  ]" nil) ("sigma" SDATA "[sigma ]" nil) ("Sigma" SDATA "[Sigma ]" nil) ("sigmav" SDATA "[sigmav]" nil) ("tau" SDATA "[tau   ]" nil) ("upsi" SDATA "[upsi  ]" nil) ("Upsi" SDATA "[Upsi  ]" nil) ("phis" SDATA "[phis  ]" nil) ("Phi" SDATA "[Phi   ]" nil) ("phiv" SDATA "[phiv  ]" nil) ("chi" SDATA "[chi   ]" nil) ("psi" SDATA "[psi   ]" nil) ("Psi" SDATA "[Psi   ]" nil) ("omega" SDATA "[omega ]" nil) ("Omega" SDATA "[Omega ]" nil) ("b.alpha" SDATA "[b.alpha ]" nil) ("b.beta" SDATA "[b.beta  ]" nil) ("b.gamma" SDATA "[b.gamma ]" nil) ("b.Gamma" SDATA "[b.Gamma ]" nil) ("b.gammad" SDATA "[b.gammad]" nil) ("b.delta" SDATA "[b.delta ]" nil) ("b.Delta" SDATA "[b.Delta ]" nil) ("b.epsi" SDATA "[b.epsi  ]" nil) ("b.epsiv" SDATA "[b.epsiv ]" nil) ("b.epsis" SDATA "[b.epsis ]" nil) ("b.zeta" SDATA "[b.zeta  ]" nil) ("b.eta" SDATA "[b.eta   ]" nil) ("b.thetas" SDATA "[b.thetas]" nil) ("b.Theta" SDATA "[b.Theta ]" nil) ("b.thetav" SDATA "[b.thetav]" nil) ("b.iota" SDATA "[b.iota  ]" nil) ("b.kappa" SDATA "[b.kappa ]" nil) ("b.kappav" SDATA "[b.kappav]" nil) ("b.lambda" SDATA "[b.lambda]" nil) ("b.Lambda" SDATA "[b.Lambda]" nil) ("b.mu" SDATA "[b.mu    ]" nil) ("b.nu" SDATA "[b.nu    ]" nil) ("b.xi" SDATA "[b.xi    ]" nil) ("b.Xi" SDATA "[b.Xi    ]" nil) ("b.pi" SDATA "[b.pi    ]" nil) ("b.Pi" SDATA "[b.Pi    ]" nil) ("b.piv" SDATA "[b.piv   ]" nil) ("b.rho" SDATA "[b.rho   ]" nil) ("b.rhov" SDATA "[b.rhov  ]" nil) ("b.sigma" SDATA "[b.sigma ]" nil) ("b.Sigma" SDATA "[b.Sigma ]" nil) ("b.sigmav" SDATA "[b.sigmav]" nil) ("b.tau" SDATA "[b.tau   ]" nil) ("b.upsi" SDATA "[b.upsi  ]" nil) ("b.Upsi" SDATA "[b.Upsi  ]" nil) ("b.phis" SDATA "[b.phis  ]" nil) ("b.Phi" SDATA "[b.Phi   ]" nil) ("b.phiv" SDATA "[b.phiv  ]" nil) ("b.chi" SDATA "[b.chi   ]" nil) ("b.psi" SDATA "[b.psi   ]" nil) ("b.Psi" SDATA "[b.Psi   ]" nil) ("b.omega" SDATA "[b.omega ]" nil) ("b.Omega" SDATA "[b.Omega ]" nil) ("aacute" SDATA "[aacute]" nil) ("Aacute" SDATA "[Aacute]" nil) ("acirc" SDATA "[acirc ]" nil) ("Acirc" SDATA "[Acirc ]" nil) ("agrave" SDATA "[agrave]" nil) ("Agrave" SDATA "[Agrave]" nil) ("aring" SDATA "[aring ]" nil) ("Aring" SDATA "[Aring ]" nil) ("atilde" SDATA "[atilde]" nil) ("Atilde" SDATA "[Atilde]" nil) ("auml" SDATA "[auml  ]" nil) ("Auml" SDATA "[Auml  ]" nil) ("aelig" SDATA "[aelig ]" nil) ("AElig" SDATA "[AElig ]" nil) ("ccedil" SDATA "[ccedil]" nil) ("Ccedil" SDATA "[Ccedil]" nil) ("eth" SDATA "[eth   ]" nil) ("ETH" SDATA "[ETH   ]" nil) ("eacute" SDATA "[eacute]" nil) ("Eacute" SDATA "[Eacute]" nil) ("ecirc" SDATA "[ecirc ]" nil) ("Ecirc" SDATA "[Ecirc ]" nil) ("egrave" SDATA "[egrave]" nil) ("Egrave" SDATA "[Egrave]" nil) ("euml" SDATA "[euml  ]" nil) ("Euml" SDATA "[Euml  ]" nil) ("iacute" SDATA "[iacute]" nil) ("Iacute" SDATA "[Iacute]" nil) ("icirc" SDATA "[icirc ]" nil) ("Icirc" SDATA "[Icirc ]" nil) ("igrave" SDATA "[igrave]" nil) ("Igrave" SDATA "[Igrave]" nil) ("iuml" SDATA "[iuml  ]" nil) ("Iuml" SDATA "[Iuml  ]" nil) ("ntilde" SDATA "[ntilde]" nil) ("Ntilde" SDATA "[Ntilde]" nil) ("oacute" SDATA "[oacute]" nil) ("Oacute" SDATA "[Oacute]" nil) ("ocirc" SDATA "[ocirc ]" nil) ("Ocirc" SDATA "[Ocirc ]" nil) ("ograve" SDATA "[ograve]" nil) ("Ograve" SDATA "[Ograve]" nil) ("oslash" SDATA "[oslash]" nil) ("Oslash" SDATA "[Oslash]" nil) ("otilde" SDATA "[otilde]" nil) ("Otilde" SDATA "[Otilde]" nil) ("ouml" SDATA "[ouml  ]" nil) ("Ouml" SDATA "[Ouml  ]" nil) ("szlig" SDATA "[szlig ]" nil) ("thorn" SDATA "[thorn ]" nil) ("THORN" SDATA "[THORN ]" nil) ("uacute" SDATA "[uacute]" nil) ("Uacute" SDATA "[Uacute]" nil) ("ucirc" SDATA "[ucirc ]" nil) ("Ucirc" SDATA "[Ucirc ]" nil) ("ugrave" SDATA "[ugrave]" nil) ("Ugrave" SDATA "[Ugrave]" nil) ("uuml" SDATA "[uuml  ]" nil) ("Uuml" SDATA "[Uuml  ]" nil) ("yacute" SDATA "[yacute]" nil) ("Yacute" SDATA "[Yacute]" nil) ("yuml" SDATA "[yuml  ]" nil) ("abreve" SDATA "[abreve]" nil) ("Abreve" SDATA "[Abreve]" nil) ("amacr" SDATA "[amacr ]" nil) ("Amacr" SDATA "[Amacr ]" nil) ("aogon" SDATA "[aogon ]" nil) ("Aogon" SDATA "[Aogon ]" nil) ("cacute" SDATA "[cacute]" nil) ("Cacute" SDATA "[Cacute]" nil) ("ccaron" SDATA "[ccaron]" nil) ("Ccaron" SDATA "[Ccaron]" nil) ("ccirc" SDATA "[ccirc ]" nil) ("Ccirc" SDATA "[Ccirc ]" nil) ("cdot" SDATA "[cdot  ]" nil) ("Cdot" SDATA "[Cdot  ]" nil) ("dcaron" SDATA "[dcaron]" nil) ("Dcaron" SDATA "[Dcaron]" nil) ("dstrok" SDATA "[dstrok]" nil) ("Dstrok" SDATA "[Dstrok]" nil) ("ecaron" SDATA "[ecaron]" nil) ("Ecaron" SDATA "[Ecaron]" nil) ("edot" SDATA "[edot  ]" nil) ("Edot" SDATA "[Edot  ]" nil) ("emacr" SDATA "[emacr ]" nil) ("Emacr" SDATA "[Emacr ]" nil) ("eogon" SDATA "[eogon ]" nil) ("Eogon" SDATA "[Eogon ]" nil) ("gacute" SDATA "[gacute]" nil) ("gbreve" SDATA "[gbreve]" nil) ("Gbreve" SDATA "[Gbreve]" nil) ("Gcedil" SDATA "[Gcedil]" nil) ("gcirc" SDATA "[gcirc ]" nil) ("Gcirc" SDATA "[Gcirc ]" nil) ("gdot" SDATA "[gdot  ]" nil) ("Gdot" SDATA "[Gdot  ]" nil) ("hcirc" SDATA "[hcirc ]" nil) ("Hcirc" SDATA "[Hcirc ]" nil) ("hstrok" SDATA "[hstrok]" nil) ("Hstrok" SDATA "[Hstrok]" nil) ("Idot" SDATA "[Idot  ]" nil) ("Imacr" SDATA "[Imacr ]" nil) ("imacr" SDATA "[imacr ]" nil) ("ijlig" SDATA "[ijlig ]" nil) ("IJlig" SDATA "[IJlig ]" nil) ("iogon" SDATA "[iogon ]" nil) ("Iogon" SDATA "[Iogon ]" nil) ("itilde" SDATA "[itilde]" nil) ("Itilde" SDATA "[Itilde]" nil) ("jcirc" SDATA "[jcirc ]" nil) ("Jcirc" SDATA "[Jcirc ]" nil) ("kcedil" SDATA "[kcedil]" nil) ("Kcedil" SDATA "[Kcedil]" nil) ("kgreen" SDATA "[kgreen]" nil) ("lacute" SDATA "[lacute]" nil) ("Lacute" SDATA "[Lacute]" nil) ("lcaron" SDATA "[lcaron]" nil) ("Lcaron" SDATA "[Lcaron]" nil) ("lcedil" SDATA "[lcedil]" nil) ("Lcedil" SDATA "[Lcedil]" nil) ("lmidot" SDATA "[lmidot]" nil) ("Lmidot" SDATA "[Lmidot]" nil) ("lstrok" SDATA "[lstrok]" nil) ("Lstrok" SDATA "[Lstrok]" nil) ("nacute" SDATA "[nacute]" nil) ("Nacute" SDATA "[Nacute]" nil) ("eng" SDATA "[eng   ]" nil) ("ENG" SDATA "[ENG   ]" nil) ("napos" SDATA "[napos ]" nil) ("ncaron" SDATA "[ncaron]" nil) ("Ncaron" SDATA "[Ncaron]" nil) ("ncedil" SDATA "[ncedil]" nil) ("Ncedil" SDATA "[Ncedil]" nil) ("odblac" SDATA "[odblac]" nil) ("Odblac" SDATA "[Odblac]" nil) ("Omacr" SDATA "[Omacr ]" nil) ("omacr" SDATA "[omacr ]" nil) ("oelig" SDATA "[oelig ]" nil) ("OElig" SDATA "[OElig ]" nil) ("racute" SDATA "[racute]" nil) ("Racute" SDATA "[Racute]" nil) ("rcaron" SDATA "[rcaron]" nil) ("Rcaron" SDATA "[Rcaron]" nil) ("rcedil" SDATA "[rcedil]" nil) ("Rcedil" SDATA "[Rcedil]" nil) ("sacute" SDATA "[sacute]" nil) ("Sacute" SDATA "[Sacute]" nil) ("scaron" SDATA "[scaron]" nil) ("Scaron" SDATA "[Scaron]" nil) ("scedil" SDATA "[scedil]" nil) ("Scedil" SDATA "[Scedil]" nil) ("scirc" SDATA "[scirc ]" nil) ("Scirc" SDATA "[Scirc ]" nil) ("tcaron" SDATA "[tcaron]" nil) ("Tcaron" SDATA "[Tcaron]" nil) ("tcedil" SDATA "[tcedil]" nil) ("Tcedil" SDATA "[Tcedil]" nil) ("tstrok" SDATA "[tstrok]" nil) ("Tstrok" SDATA "[Tstrok]" nil) ("ubreve" SDATA "[ubreve]" nil) ("Ubreve" SDATA "[Ubreve]" nil) ("udblac" SDATA "[udblac]" nil) ("Udblac" SDATA "[Udblac]" nil) ("umacr" SDATA "[umacr ]" nil) ("Umacr" SDATA "[Umacr ]" nil) ("uogon" SDATA "[uogon ]" nil) ("Uogon" SDATA "[Uogon ]" nil) ("uring" SDATA "[uring ]" nil) ("Uring" SDATA "[Uring ]" nil) ("utilde" SDATA "[utilde]" nil) ("Utilde" SDATA "[Utilde]" nil) ("wcirc" SDATA "[wcirc ]" nil) ("Wcirc" SDATA "[Wcirc ]" nil) ("ycirc" SDATA "[ycirc ]" nil) ("Ycirc" SDATA "[Ycirc ]" nil) ("Yuml" SDATA "[Yuml  ]" nil) ("zacute" SDATA "[zacute]" nil) ("Zacute" SDATA "[Zacute]" nil) ("zcaron" SDATA "[zcaron]" nil) ("Zcaron" SDATA "[Zcaron]" nil) ("zdot" SDATA "[zdot  ]" nil) ("Zdot" SDATA "[Zdot  ]" nil) ("half" SDATA "[half  ]" nil) ("frac12" SDATA "[frac12]" nil) ("frac14" SDATA "[frac14]" nil) ("frac34" SDATA "[frac34]" nil) ("frac18" SDATA "[frac18]" nil) ("frac38" SDATA "[frac38]" nil) ("frac58" SDATA "[frac58]" nil) ("frac78" SDATA "[frac78]" nil) ("sup1" SDATA "[sup1  ]" nil) ("sup2" SDATA "[sup2  ]" nil) ("sup3" SDATA "[sup3  ]" nil) ("plus" SDATA "[plus  ]" nil) ("plusmn" SDATA "[plusmn]" nil) ("lt" SDATA "[lt    ]" nil) ("equals" SDATA "[equals]" nil) ("gt" SDATA "[gt    ]" nil) ("divide" SDATA "[divide]" nil) ("times" SDATA "[times ]" nil) ("curren" SDATA "[curren]" nil) ("pound" SDATA "[pound ]" nil) ("dollar" SDATA "[dollar]" nil) ("cent" SDATA "[cent  ]" nil) ("yen" SDATA "[yen   ]" nil) ("num" SDATA "[num   ]" nil) ("percnt" SDATA "[percnt]" nil) ("amp" SDATA "[amp   ]" nil) ("ast" SDATA "[ast   ]" nil) ("commat" SDATA "[commat]" nil) ("lsqb" SDATA "[lsqb  ]" nil) ("bsol" SDATA "[bsol  ]" nil) ("rsqb" SDATA "[rsqb  ]" nil) ("lcub" SDATA "[lcub  ]" nil) ("horbar" SDATA "[horbar]" nil) ("verbar" SDATA "[verbar]" nil) ("rcub" SDATA "[rcub  ]" nil) ("micro" SDATA "[micro ]" nil) ("ohm" SDATA "[ohm   ]" nil) ("deg" SDATA "[deg   ]" nil) ("ordm" SDATA "[ordm  ]" nil) ("ordf" SDATA "[ordf  ]" nil) ("sect" SDATA "[sect  ]" nil) ("para" SDATA "[para  ]" nil) ("middot" SDATA "[middot]" nil) ("larr" SDATA "[larr  ]" nil) ("rarr" SDATA "[rarr  ]" nil) ("uarr" SDATA "[uarr  ]" nil) ("darr" SDATA "[darr  ]" nil) ("copy" SDATA "[copy  ]" nil) ("reg" SDATA "[reg   ]" nil) ("trade" SDATA "[trade ]" nil) ("brvbar" SDATA "[brvbar]" nil) ("not" SDATA "[not   ]" nil) ("sung" SDATA "[sung  ]" nil) ("excl" SDATA "[excl  ]" nil) ("iexcl" SDATA "[iexcl ]" nil) ("quot" SDATA "[quot  ]" nil) ("apos" SDATA "[apos  ]" nil) ("lpar" SDATA "[lpar  ]" nil) ("rpar" SDATA "[rpar  ]" nil) ("comma" SDATA "[comma ]" nil) ("lowbar" SDATA "[lowbar]" nil) ("hyphen" SDATA "[hyphen]" nil) ("period" SDATA "[period]" nil) ("sol" SDATA "[sol   ]" nil) ("colon" SDATA "[colon ]" nil) ("semi" SDATA "[semi  ]" nil) ("quest" SDATA "[quest ]" nil) ("iquest" SDATA "[iquest]" nil) ("laquo" SDATA "[laquo ]" nil) ("raquo" SDATA "[raquo ]" nil) ("lsquo" SDATA "[lsquo ]" nil) ("rsquo" SDATA "[rsquo ]" nil) ("ldquo" SDATA "[ldquo ]" nil) ("rdquo" SDATA "[rdquo ]" nil) ("nbsp" SDATA "[nbsp  ]" nil) ("shy" SDATA "[shy   ]" nil) ("emsp" SDATA "[emsp  ]" nil) ("ensp" SDATA "[ensp  ]" nil) ("emsp13" SDATA "[emsp3 ]" nil) ("emsp14" SDATA "[emsp4 ]" nil) ("numsp" SDATA "[numsp ]" nil) ("puncsp" SDATA "[puncsp]" nil) ("thinsp" SDATA "[thinsp]" nil) ("hairsp" SDATA "[hairsp]" nil) ("mdash" SDATA "[mdash ]" nil) ("ndash" SDATA "[ndash ]" nil) ("dash" SDATA "[dash  ]" nil) ("blank" SDATA "[blank ]" nil) ("hellip" SDATA "[hellip]" nil) ("nldr" SDATA "[nldr  ]" nil) ("frac13" SDATA "[frac13]" nil) ("frac23" SDATA "[frac23]" nil) ("frac15" SDATA "[frac15]" nil) ("frac25" SDATA "[frac25]" nil) ("frac35" SDATA "[frac35]" nil) ("frac45" SDATA "[frac45]" nil) ("frac16" SDATA "[frac16]" nil) ("frac56" SDATA "[frac56]" nil) ("incare" SDATA "[incare]" nil) ("block" SDATA "[block ]" nil) ("uhblk" SDATA "[uhblk ]" nil) ("lhblk" SDATA "[lhblk ]" nil) ("blk14" SDATA "[blk14 ]" nil) ("blk12" SDATA "[blk12 ]" nil) ("blk34" SDATA "[blk34 ]" nil) ("marker" SDATA "[marker]" nil) ("cir" SDATA "[cir   ]" nil) ("squ" SDATA "[squ   ]" nil) ("rect" SDATA "[rect  ]" nil) ("utri" SDATA "[utri  ]" nil) ("dtri" SDATA "[dtri  ]" nil) ("star" SDATA "[star  ]" nil) ("bull" SDATA "[bull  ]" nil) ("squf" SDATA "[squf  ]" nil) ("utrif" SDATA "[utrif ]" nil) ("dtrif" SDATA "[dtrif ]" nil) ("ltrif" SDATA "[ltrif ]" nil) ("rtrif" SDATA "[rtrif ]" nil) ("clubs" SDATA "[clubs ]" nil) ("diams" SDATA "[diams ]" nil) ("hearts" SDATA "[hearts]" nil) ("spades" SDATA "[spades]" nil) ("malt" SDATA "[malt  ]" nil) ("dagger" SDATA "[dagger]" nil) ("Dagger" SDATA "[Dagger]" nil) ("check" SDATA "[check ]" nil) ("cross" SDATA "[ballot]" nil) ("sharp" SDATA "[sharp ]" nil) ("flat" SDATA "[flat  ]" nil) ("male" SDATA "[male  ]" nil) ("female" SDATA "[female]" nil) ("phone" SDATA "[phone ]" nil) ("telrec" SDATA "[telrec]" nil) ("copysr" SDATA "[copysr]" nil) ("caret" SDATA "[caret ]" nil) ("lsquor" SDATA "[lsquor]" nil) ("ldquor" SDATA "[ldquor]" nil) ("fflig" SDATA "[fflig ]" nil) ("filig" SDATA "[filig ]" nil) ("fjlig" SDATA "[fjlig ]" nil) ("ffilig" SDATA "[ffilig]" nil) ("ffllig" SDATA "[ffllig]" nil) ("fllig" SDATA "[fllig ]" nil) ("mldr" SDATA "[mldr  ]" nil) ("rdquor" SDATA "[rdquor]" nil) ("rsquor" SDATA "[rsquor]" nil) ("vellip" SDATA "[vellip]" nil) ("hybull" SDATA "[hybull]" nil) ("loz" SDATA "[loz   ]" nil) ("lozf" SDATA "[lozf  ]" nil) ("ltri" SDATA "[ltri  ]" nil) ("rtri" SDATA "[rtri  ]" nil) ("starf" SDATA "[starf ]" nil) ("natur" SDATA "[natur ]" nil) ("rx" SDATA "[rx    ]" nil) ("sext" SDATA "[sext  ]" nil) ("target" SDATA "[target]" nil) ("dlcrop" SDATA "[dlcrop]" nil) ("drcrop" SDATA "[drcrop]" nil) ("ulcrop" SDATA "[ulcrop]" nil) ("urcrop" SDATA "[urcrop]" nil) ("aleph" SDATA "[aleph ]" nil) ("and" SDATA "[and   ]" nil) ("ang90" SDATA "[ang90 ]" nil) ("angsph" SDATA "[angsph]" nil) ("ap" SDATA "[ap    ]" nil) ("becaus" SDATA "[becaus]" nil) ("bottom" SDATA "[bottom]" nil) ("cap" SDATA "[cap   ]" nil) ("cong" SDATA "[cong  ]" nil) ("conint" SDATA "[conint]" nil) ("cup" SDATA "[cup   ]" nil) ("equiv" SDATA "[equiv ]" nil) ("exist" SDATA "[exist ]" nil) ("forall" SDATA "[forall]" nil) ("fnof" SDATA "[fnof  ]" nil) ("ge" SDATA "[ge    ]" nil) ("iff" SDATA "[iff   ]" nil) ("infin" SDATA "[infin ]" nil) ("int" SDATA "[int   ]" nil) ("isin" SDATA "[isin  ]" nil) ("lang" SDATA "[lang  ]" nil) ("lArr" SDATA "[lArr  ]" nil) ("le" SDATA "[le    ]" nil) ("minus" SDATA "[minus ]" nil) ("mnplus" SDATA "[mnplus]" nil) ("nabla" SDATA "[nabla ]" nil) ("ne" SDATA "[ne    ]" nil) ("ni" SDATA "[ni    ]" nil) ("or" SDATA "[or    ]" nil) ("par" SDATA "[par   ]" nil) ("part" SDATA "[part  ]" nil) ("permil" SDATA "[permil]" nil) ("perp" SDATA "[perp  ]" nil) ("prime" SDATA "[prime ]" nil) ("Prime" SDATA "[Prime ]" nil) ("prop" SDATA "[prop  ]" nil) ("radic" SDATA "[radic ]" nil) ("rang" SDATA "[rang  ]" nil) ("rArr" SDATA "[rArr  ]" nil) ("sim" SDATA "[sim   ]" nil) ("sime" SDATA "[sime  ]" nil) ("square" SDATA "[square]" nil) ("sub" SDATA "[sub   ]" nil) ("sube" SDATA "[sube  ]" nil) ("sup" SDATA "[sup   ]" nil) ("supe" SDATA "[supe  ]" nil) ("there4" SDATA "[there4]" nil) ("Verbar" SDATA "[Verbar]" nil) ("angst" SDATA "[angst ]" nil) ("bernou" SDATA "[bernou]" nil) ("compfn" SDATA "[compfn]" nil) ("Dot" SDATA "[Dot   ]" nil) ("DotDot" SDATA "[DotDot]" nil) ("hamilt" SDATA "[hamilt]" nil) ("lagran" SDATA "[lagran]" nil) ("lowast" SDATA "[lowast]" nil) ("notin" SDATA "[notin ]" nil) ("order" SDATA "[order ]" nil) ("phmmat" SDATA "[phmmat]" nil) ("tdot" SDATA "[tdot  ]" nil) ("tprime" SDATA "[tprime]" nil) ("wedgeq" SDATA "[wedgeq]" nil))
-(nil)
-nil
diff --git a/doc/src/sgml/reference.sgml b/doc/src/sgml/reference.sgml
deleted file mode 100644
index d1d40f3a72b..00000000000
--- a/doc/src/sgml/reference.sgml
+++ /dev/null
@@ -1,218 +0,0 @@
-<!-- reference.sgml
-$Header: /cvsroot/pgsql/doc/src/sgml/reference.sgml,v 1.28 2002/04/25 21:47:06 tgl Exp $
-
-PostgreSQL Reference Manual
--->
-
-<book id="reference">
-
- <title>PostgreSQL &version; Reference Manual</title>
- <bookinfo>
-  <corpauthor>The PostgreSQL Global Development Group</corpauthor>
-  &legal;
- </bookinfo>
-
- <preface id="reference-preface">
-  <title>Preface</title>
-
-  <para>
-   The entries in this <citetitle>Reference Manual</citetitle> are
-   meant to provide in reasonable length an authoritative, complete, and
-   formal summary about their respective subjects.  More information
-   about the use of <productname>PostgreSQL</productname>, in
-   narrative, tutorial, or example form, may be found in other parts
-   of the <productname>PostgreSQL</productname> documentation set.
-   See the cross-references listed on each reference page.
-  </para>
-
-  <para>
-   The <citetitle>Reference Manual</citetitle> entries are also
-   available as traditional <quote>man</quote> pages.
-  </para>
- </preface>
-
- <reference id="sql-commands">
-  <title>SQL Commands</title>
-
-  <partintro>
-   <para>
-    This part contains reference information for the
-    <acronym>SQL</acronym> commands supported by
-    <productname>PostgreSQL</productname>.  By <quote>SQL</quote> the
-    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;
-   &alterDatabase;
-   &alterGroup;
-   &alterTable;
-   &alterTrigger;
-   &alterUser;
-   &analyze;
-   &begin;
-   &checkpoint;
-   &close;
-   &cluster;
-   &commentOn;
-   &commit;
-   &copyTable;
-   &createAggregate;
-   &createConstraint;
-   &createDatabase;
-   &createDomain;
-   &createFunction;
-   &createGroup;
-   &createIndex;
-   &createLanguage;
-   &createOperator;
-   &createRule;
-   &createSchema;
-   &createSequence;
-   &createTable;
-   &createTableAs;
-   &createTrigger;
-   &createType;
-   &createUser;
-   &createView;
-   &declare;
-   &delete;
-   &dropAggregate;
-   &dropDatabase;
-   &dropDomain;
-   &dropFunction;
-   &dropGroup;
-   &dropIndex;
-   &dropLanguage;
-   &dropOperator;
-   &dropRule;
-   &dropSequence;
-   &dropTable;
-   &dropTrigger;
-   &dropType
-   &dropUser;
-   &dropView;
-   &end;
-   &explain;
-   &fetch;
-   &grant;
-   &insert;
-   &listen;
-   &load;
-   &lock;
-   &move;
-   &notify;
-   &reindex;
-   &reset;
-   &revoke;
-   &rollback;
-   &select;
-   &selectInto;
-   &set;
-   &setConstraints;
-   &setSessionAuth;
-   &setTransaction;
-   &show;
-   &truncate;
-   &unlisten;
-   &update;
-   &vacuum;
-
- </reference>
-
-<!--
-Disable this chapter until we have more functions documented.
-- thomas 1998-10-27
-
- <reference id="sql-functions">
-  <title>SQL Functions</title>
-
-  <partintro>
-   <para>
-    This part provides reference information for the
-    <acronym>SQL</acronym> functions supported by
-    <productname>PostgreSQL</productname>.
-   </para>
-
-   &currentDate;
-   &currentTime;
-   &currentTimestamp;
-   &currentUser;
- </reference>
--->
-
- <reference id="reference-client">
-  <title>PostgreSQL Client Applications</title>
-
-  <partintro>
-   <para>
-    This part contains reference information for
-    <productname>PostgreSQL</productname> client applications and
-    utilities.  Not all of these commands are of general utility, some
-    may 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>
-
-   &createdb;
-   &createlang;
-   &createuser;
-   &dropdb;
-   &droplang;
-   &dropuser;
-   &ecpgRef;
-   &pgAccess;
-   &pgConfig;
-   &pgDump;
-   &pgDumpall;
-   &pgRestore;
-   &psqlRef;
-   &pgTclSh;
-   &pgTkSh;
-   &vacuumdb;
-
- </reference>
-
- <reference id="reference-server">
-  <title>PostgreSQL Server Applications</title>
-
-  <partintro>
-   <para>
-    This part contains reference information for
-    <productname>PostgreSQL</productname> server applications and
-    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>
-
-   &initdb;
-   &initlocation;
-   &ipcclean;
-   &pgCtl;
-   &postgres;
-   &postmaster;
-
- </reference>
-
-</book>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml
deleted file mode 100644
index 64c5abdf8ce..00000000000
--- a/doc/src/sgml/regress.sgml
+++ /dev/null
@@ -1,437 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/regress.sgml,v 1.27 2002/05/14 13:05:42 petere Exp $ -->
-
- <chapter id="regress">
-  <title id="regress-title">Regression Tests</title>
-
-  <sect1 id="regress-intro">
-   <title>Introduction</title>
-
-  <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>.  The test suite was
-   originally developed by Jolly Chen and Andrew Yu, and was
-   extensively revised and repackaged by Marc Fournier and Thomas
-   Lockhart.  From <productname>PostgreSQL</productname> 6.1 onward
-   the regression tests are current for every official release.
-  </para>
-
-  </sect1>
-
-  <sect1 id="regress-run">
-   <title>Running the Tests</title>
-
-  <para>
-   The regression test 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 in turn, whereas 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.  For
-   historical reasons, the sequential test is usually run against an
-   existing installation and the parallel method against a temporary
-   installation, but there are no technical reasons for this.
-  </para>
-
-  <para>
-   To run the regression tests after building but before installation,
-   type
-<screen>
-<prompt>$ </prompt><userinput>gmake check</userinput>
-</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
-   platform-dependent <quote>expected</quote> files and some sample
-   user-defined trigger functions, and then run the test driver
-   script.  At the end you should see something like
-<screen>
-<computeroutput>
-======================
- All 77 tests passed.
-======================
-</computeroutput>
-</screen>
-   or otherwise a note about what tests failed.  See <xref
-   linkend="regress-evaluation"> below for more.
-  </para>
-
-  <note>
-   <para>
-    Because this test method runs a temporary server, it will not work
-    when you are the root user (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>chmod -R a+w contrib/spi</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>
-  </note>
-
-  <tip>
-   <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 sixty processes --- there's a backend, a psql,
-    and usually a shell parent process for the psql 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 seventy-five or so, else you may get
-    random-seeming failures in the parallel test.  If you are not in
-    a position to raise the limit, you can edit the file
-    <filename>src/test/regress/parallel_schedule</> to split the
-    larger concurrent test sets into more manageable groups.
-   </para>
-  </tip>
-
-  <tip>
-   <para>
-    On some systems, the default Bourne-compatible shell
-    (<filename>/bin/sh</filename>) gets confused when it has to manage
-    too many child processes in parallel.  This may cause the parallel
-    test run to lock up or fail.  In such cases, specify a different
-    Bourne-compatible shell on the command line, for example:
-    <informalexample>
-<screen>
-<prompt>$ </prompt><userinput>gmake SHELL=/bin/ksh check</userinput>
-</screen>
-    </informalexample>
-    If no non-broken shell is available, you can alter the parallel test
-    schedule as suggested above.
-   </para>
-  </tip>
-
-  <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>
-<prompt>$ </prompt><userinput>gmake installcheck</userinput>
-</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>
-  </sect1>
-
-  <sect1 id="regress-evaluation">
-   <title>Test Evaluation</title> 
-
-   <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 time zone support. The tests are currently evaluated using a simple
-    <application>diff</application> 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 may well 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 <application>diff</application> 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 <application>diff</application> yourself, if you prefer.)
-   </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 may
-     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 an already-installed server that was
-     initialized with a collation order locale different than C then
-     there may be differences due to sort order and follow-up
-     failures.  The regression test suite is set up to handle this
-     problem by providing alternative result files that together are
-     known to handle a large number of locales.  For example, for the
-     <quote>char</quote> test, the expected file
-     <filename>char.out</filename> handles the C and POSIX locales,
-     and the file <filename>char_1.out</filename> handles many other
-     locales.  The regression test driver will automatically pick the
-     best file to match against when checking for success and for
-     computing failure differences.  (This means that the regression
-     tests cannot detect whether the results are appropriate for the
-     configured locale.  The tests will simply pick the one result
-     file that works best.)
-    </para>
-
-    <para>
-     If for some reason the existing expected files do not cover some
-     locale, you can add a new file.  The naming scheme is
-     <literal><replaceable>testname</>_<replaceable>digit</>.out</>.
-     The actual digit is not significant.  Remember that the
-     regression test driver will consider all such files to be equally
-     valid test results.  If the test results are platform-dependent,
-     the technique described in <xref linkend="regress-platform">
-     should be used instead.
-    </para>
-   </sect2>
-    
-   <sect2>
-    <title>Date and time differences</title>
-
-    <para>
-     Some of the queries in the <filename>horology</filename> test will
-     fail if you run the test on the day of a daylight-saving time
-     changeover, or the day before or after one.  These queries assume
-     that the intervals between midnight yesterday, midnight today and
-     midnight tomorrow are exactly twenty-four hours -- which is wrong
-     if daylight-saving time went into or out of effect meanwhile.
-    </para>
-
-    <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.  However, your system must provide library
-     support for the <literal>PST8PDT</literal> time zone, or the time zone-dependent
-     tests will fail. To verify that your machine does have this
-     support, type the following:
-<screen>
-<prompt>$ </prompt><userinput>env TZ=PST8PDT date</userinput>
-</screen>
-     The command above should have returned the current system time in
-     the <literal>PST8PDT</literal> time zone. If the <literal>PST8PDT</literal> database is not available,
-     then your system may have returned the time in GMT. If the
-     <literal>PST8PDT</literal> time zone is not available, you can set the time zone
-     rules explicitly:
-<programlisting>
-PGTZ='PST8PDT7,M04.01.0,M10.05.03'; export PGTZ
-</programlisting>
-    </para>
-
-    <para>
-     There appear to be some systems that do not accept the
-     recommended syntax for explicitly setting the local time zone
-     rules; you may need to use a different <envar>PGTZ</envar>
-     setting on such machines.
-    </para>
-
-    <para>
-     Some systems using older time zone libraries fail to apply
-     daylight-saving corrections to dates before 1970, causing
-     pre-1970 <acronym>PDT</acronym> times to be displayed in <acronym>PST</acronym> instead.  This will
-     result in localized differences in the test results.
-    </para>
-   </sect2>
-    
-   <sect2>
-    <title>Floating-point differences</title>
-      
-    <para>
-     Some of the tests involve computing 64-bit (<type>double
-     precision</type>) numbers from table columns. Differences in
-     results involving mathematical functions of <type>double
-     precision</type> columns have been observed.  The float8 and
-     geometry tests are particularly prone to small differences across
-     platforms, or even with different compiler optimization options.
-     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 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>Polygon differences</title>
-      
-    <para>
-     Several of the tests involve operations on geographic data about
-     the Oakland/Berkeley, California street map. The map data is expressed as
-     polygons whose vertices are represented as pairs of <type>double
-     precision</type> numbers (decimal latitude and
-     longitude). Initially, some tables are created and loaded with
-     geographic data, then some views are created that join two
-     tables using the polygon intersection operator
-     (<literal>##</literal>), then a select is done on the view.
-    </para>
-
-    <para>
-     When comparing the results from different platforms, differences
-     occur in the 2nd or 3rd place to the right of the decimal
-     point. The SQL statements where these problems occur are the
-     following:
-<programlisting>
-SELECT * from street;
-SELECT * from iexit;
-</programlisting>
-    </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 ORDER BY for every single
-SELECT, and so their result row orderings are not well-defined
-according to the letter of 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, and
-so the lack of ORDER BY isn't a problem.  Some queries do exhibit
-cross-platform ordering differences, however.  (Ordering differences
-can also be triggered by non-C locale settings.)
-    </para>
-
-    <para>
-Therefore, if you see an ordering difference, it's not something to
-worry about, unless the query does have an ORDER BY that your result
-is violating.  But please report it anyway, so that we can add an
-ORDER BY to that particular query and thereby eliminate the bogus
-<quote>failure</quote> in future releases.
-    </para>
-
-    <para>
-You might wonder why we don't order all the regress 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>The <quote>random</quote> test</title>
-      
-    <para>
-     There is at least one case in the <quote>random</quote> test
-     script that is intended to produce random results. This causes
-     random to fail the regression test once in a while (perhaps once
-     in every five to ten trials).  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 always fails in repeated
-     attempts.  (On the other hand, if the random test is
-     <emphasis>never</emphasis> reported to fail even in many trials
-     of the regression tests, you probably <emphasis>should</emphasis>
-     worry.)
-    </para>
-   </sect2>
-  </sect1>
-
-<![%standalone-ignore;[
-<!-- We might want to move the following section into the developer's guide. -->
-  <sect1 id="regress-platform">
-   <title>Platform-specific comparison files</title>
-
-   <para>
-    Since some of the tests inherently produce platform-specific
-    results, we have provided a way to supply platform-specific result
-    comparison files.  Frequently, the same variation applies to
-    multiple platforms; rather than supplying a separate comparison
-    file for every platform, there is a mapping file that defines
-    which comparison file to use.  So, to eliminate bogus test
-    <quote>failures</quote> for a particular platform, you must choose
-    or make a variant result file, and then add a line to the mapping
-    file, which is <filename>resultmap</filename>.
-   </para>
-
-   <para>
-    Each line in the mapping file is of the form
-<synopsis>
-testname/platformpattern=comparisonfilename
-</synopsis>
-    The test name is just the name of the particular regression test
-    module.  The platform pattern is a pattern in the style of
-    <citerefentry><refentrytitle>expr</><manvolnum>1</></citerefentry> (that is, a regular expression with an implicit
-    <literal>^</literal> anchor
-    at the start).  It is matched against the platform name as printed
-    by <filename>config.guess</filename> followed by
-    <literal>:gcc</literal> or <literal>:cc</literal>, depending on
-    whether you use the GNU compiler or the system's native compiler
-    (on systems where there is a difference).  The comparison file
-    name is the name of the substitute result comparison file.
-   </para>
-
-   <para>
-    For example: some systems using older time zone libraries fail to apply
-    daylight-saving corrections to dates before 1970, causing
-    pre-1970 <acronym>PDT</acronym> times to be displayed in <acronym>PST</acronym> instead.  This causes a
-    few differences in the <filename>horology</> regression test.
-    Therefore, we provide a variant comparison file,
-    <filename>horology-no-DST-before-1970.out</filename>, which includes
-    the results to be expected on these systems.  To silence the bogus
-    <quote>failure</quote> message on <systemitem>HPPA</systemitem> platforms, <filename>resultmap</filename>
-    includes
-<programlisting>
-horology/hppa=horology-no-DST-before-1970
-</programlisting>
-    which will trigger on any machine for which the output of <command>config.guess</command>
-    begins with <quote><literal>hppa</literal></quote>.  Other lines
-    in <filename>resultmap</> select the variant comparison file for other
-    platforms where it's appropriate.
-   </para>
-    
-  </sect1>
-]]>
-  
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
deleted file mode 100644
index 9cd74fae205..00000000000
--- a/doc/src/sgml/release.sgml
+++ /dev/null
@@ -1,4444 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.139 2002/06/11 15:32:33 thomas Exp $
--->
-
-<appendix id="release">
- <title>Release Notes</title>
-
- <sect1 id="release-devel">
-  <title>&version; Development Branch</title>
-
-  <para>
-   Below is a subset of the changes that have gone into the
-   development branch of PostgreSQL since version 7.2.  For a complete
-   list of changes, consult the CVS logs.
-  </para>
-
-<!--
-Developers: When you add a feature, mention it here.  This avoids
-lossiness when digging out the information from the CVS logs, and
-furthermore it advertises your feature to external parties at the
-earliest possible moment.
- 
-CDATA means the content is "SGML-free", so you can write without
-worries about funny characters.
--->
-<literallayout><![CDATA[
-Recursive SQL functions can be defined
-User-defined procedural languages can register a validator function to check new functions as they are created
-Functions can be executed with the privileges of the owner
-Syntax of CREATE FUNCTION has been extended to resemble SQL99
-Effects of SET within a transaction block now roll back if transaction aborts
-New SET LOCAL syntax sets a parameter for the life of the current transaction
-Datestyle, timezone, client_encoding can be set in postgresql.conf
-The last vestiges of support for type names datetime and timespan are gone; use timestamp and interval instead
-Rule names are now per-relation, not global; DROP RULE and COMMENT ON RULE syntax changes accordingly
-Readline and Zlib are now required by default and must be turned off explicitly if their use is not desired
-Define a third class of function volatility to allow indexscans in more cases
-Locale support is now built by default; choice of locale is set by initdb and/or at run-time
-ALTER TABLE ALTER COLUMN SET/DROP NOT NULL
-EXPLAIN output comes out as a query result, not a NOTICE message
-DOMAINs (types that are constrained versions of base types)
-Access privileges on functions
-Access privileges on procedural languages
-CREATE DATABASE has OWNER option so superuser can create DB for someone else
-Kerberos 5 support now works with Heimdal
-Database and user-specific session defaults for run-time configuration variables (ALTER DATABASE ... SET and ALTER USER ... SET)
-String function OVERLAY() implemented per SQL99
-Regular expression operator SIMILAR TO implemented per SQL99
-Regular expression function SUBSTRING() implemented per SQL99
-]]></literallayout>
-
- </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 has a variety of fixes from 7.2.
-   </para>
-
-
-   <sect2>
-    <title>Migration to version 7.2.1</title>
-
-    <para>
-     A dump/restore is <emphasis>not</emphasis> required for those running
-     7.2.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Changes</title>
-
-    <para>
-<literallayout>
-Ensure that sequence counters do not go backwards after a crash (Tom)
-Fix pgaccess kanji-coversion key binding (Tatsuo)
-Optimizer improvements (Tom)
-cash I/O improvements (Tom)
-New Russian FAQ
-Compile fix for missing AuthBlockSig (Heiko)
-Additional time zones and time zone fixes (Thomas)
-Allow psql \connect to handle mixed case database and user names (Tom)
-Return proper OID on command completion even with ON INSERT rules (Tom)
-Allow COPY FROM to use 8-bit DELIMITERS (Tatsuo)
-Fix bug in extract/date_part for milliseconds/microseconds (Tatsuo)
-Improve handling of multiple UNIONs with different lengths (Tom)
-contrib/btree_gist improvements (Teodor Sigaev)
-contrib/tsearch dictionary improvements, see README.tsearch for
-  an additional installation step (Thomas T. Thai, Teodor Sigaev)
-Fix for array subscripts handling (Tom)
-Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/PgSQL (Tom)
-</literallayout>
-    </para>
-   </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:
-
-    <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>
-   </para>
-  </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:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       The semantics of the <command>VACUUM</command> command have
-       changed in this release.  You may 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>
-
-   <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>
-<literallayout>
-Create temporary files in a separate directory (Bruce)
-Delete orphaned temporary files on postmaster startup (Bruce)
-Added unique indexes to some system tables (Tom)
-System table operator reorganization (Oleg Bartunov, Teodor Sigaev, Tom)
-Renamed pg_log to pg_clog (Tom)
-Enable SIGTERM, SIGQUIT to kill backends (Jan)
-Removed compile-time limit on number of backends (Tom)
-Better cleanup for semaphore resource failure (Tatsuo, Tom)
-Allow safe transaction ID wraparound (Tom)
-Removed OIDs from some system tables (Tom)
-Removed "triggered data change violation" error check (Tom)
-SPI portal creation of prepared/saved plans (Jan)
-Allow SPI column functions to work for system columns (Tom)
-Long value compression improvement (Tom)
-Statistics collector for table, index access (Jan)
-Truncate extra-long sequence names to a reasonable value (Tom)
-Measure transaction times in milliseconds (Thomas)
-Fix TID sequential scans (Hiroshi)
-Superuser ID now fixed at 1 (Peter E)
-New pg_ctl "reload" option (Tom)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Performance</title>
-<literallayout>
-Optimizer improvements (Tom)
-New histogram column statistics for optimizer (Tom)
-Reuse write-ahead log files rather than discarding them (Tom)
-Cache improvements (Tom)
-IS NULL, IS NOT NULL optimizer improvement (Tom)
-Improve lock manager to reduce lock contention (Tom)
-Keep relcache entries for index access support functions (Tom)
-Allow better selectivity with NaN and infinities in NUMERIC (Tom)
-R-tree performance improvements (Kenneth Been)
-B-tree splits more efficient (Tom)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Privileges</title>
-<literallayout>
-Change UPDATE, DELETE permissions to be distinct (Peter E)
-New REFERENCES, TRIGGER privileges (Peter E)
-Allow GRANT/REVOKE to/from more than one user at a time (Peter E)
-New has_table_privilege() function (Joe Conway)
-Allow non-superuser to vacuum database (Tom)
-New SET SESSION AUTHORIZATION command (Peter E)
-Fix bug in privilege modifications on newly created tables (Tom)
-Disallow access to pg_statistic for non-superuser, add user-accessible views (Tom)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Client Authentication</title>
-<literallayout>
-Fork postmaster before doing authentication to prevent hangs (Peter E)
-Add ident authentication over Unix domain sockets on Linux, *BSD (Helge Bahmann, Oliver Elphick, Teodor Sigaev, Bruce)
-Add a password authentication method that uses MD5 encryption (Bruce)
-Allow encryption of stored passwords using MD5 (Bruce)
-PAM authentication (Dominic J. Eidson)
-Load pg_hba.conf and pg_ident.conf only on startup and SIGHUP (Bruce)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Server Configuration</title>
-<literallayout>
-Interpretation of some time zone abbreviations as Australian rather than North American now settable at run time (Bruce)
-New parameter to set default transaction isolation level (Peter E)
-New parameter to enable conversion of "expr = NULL" into "expr IS NULL", off by default (Peter E)
-New parameter to control memory usage by VACUUM (Tom)
-New parameter to set client authentication timeout (Tom)
-New parameter to set maximum number of open files (Tom)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Queries</title>
-<literallayout>
-Statements added by INSERT rules now execute after the INSERT (Jan)
-Prevent unadorned relation names in target list (Bruce)
-NULLs now sort after all normal values in ORDER BY (Tom)
-New IS UNKNOWN, IS NOT UNKNOWN Boolean tests (Tom)
-New SHARE UPDATE EXCLUSIVE lock mode (Tom)
-New EXPLAIN ANALYZE command that shows run times and row counts (Martijn van Oosterhout)
-Fix problem with LIMIT and subqueries (Tom)
-Fix for LIMIT, DISTINCT ON pushed into subqueries (Tom)
-Fix nested EXCEPT/INTERSECT (Tom)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Schema Manipulation</title>
-<literallayout>
-Fix SERIAL in temporary tables (Bruce)
-Allow temporary sequences (Bruce)
-Sequences now use int8 internally (Tom)
-New SERIAL8 creates int8 columns with sequences, default still SERIAL4 (Tom)
-Make OIDs optional using WITHOUT OIDS (Tom)
-Add %TYPE syntax to CREATE TYPE (Ian Lance Taylor)
-Add ALTER TABLE / DROP CONSTRAINT for CHECK constraints (Christopher Kings-Lynne)
-New CREATE OR REPLACE FUNCTION to alter existing function (preserving the function OID) (Gavin Sherry)
-Add ALTER TABLE / ADD [ UNIQUE | PRIMARY ] (Christopher Kings-Lynne)
-Allow column renaming in views
-Make ALTER TABLE / RENAME COLUMN update column names of indexes (Brent Verner)
-Fix for ALTER TABLE / ADD CONSTRAINT ... CHECK with inherited tables (Stephan Szabo)
-ALTER TABLE RENAME update foreign-key trigger arguments correctly (Brent Verner)
-DROP AGGREGATE and COMMENT ON AGGREGATE now accept an aggtype (Tom)
-Add automatic return type data casting for SQL functions (Tom)
-Allow GiST indexes to handle NULLs and multikey indexes (Oleg Bartunov, Teodor Sigaev, Tom)
-Enable partial indexes (Martijn van Oosterhout)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Utility Commands</title>
-<literallayout>
-Add RESET ALL, SHOW ALL (Marko Kreen)
-CREATE/ALTER USER/GROUP now allow options in any order (Vince)
-Add LOCK A, B, C functionality (Neil Padgett)
-New ENCRYPTED/UNENCRYPTED option to CREATE/ALTER USER (Bruce)
-New light-weight VACUUM does not lock table; old semantics are available as VACUUM FULL (Tom)
-Disable COPY TO/FROM on views (Bruce)
-COPY DELIMITERS string must be exactly one character (Tom)
-VACUUM warning about index tuples fewer than heap now only appears when appropriate (Martijn van Oosterhout)
-Fix permission checks for CREATE INDEX (Tom)
-Disallow inappropriate use of CREATE/DROP INDEX/TRIGGER/VIEW (Tom)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Data Types and Functions</title>
-<literallayout>
-SUM(), AVG(), COUNT() now uses int8 internally for speed (Tom)
-Add convert(), convert2() (Tatsuo)
-New function bit_length() (Peter E)
-Make the "n" in CHAR(n)/VARCHAR(n) represents letters, not bytes (Tatsuo)
-CHAR(), VARCHAR() now reject strings that are too long (Peter E)
-BIT VARYING now rejects bit strings that are too long (Peter E)
-BIT now rejects bit strings that do not match declared size (Peter E)
-INET, CIDR text conversion functions (Alex Pilosov)
-INET, CIDR operators << and <<= indexable (Alex Pilosov)
-Bytea \### now requires valid three digit octal number
-Bytea comparison improvements, now supports =, &lt;&gt;, >, >=, <, and <=
-Bytea now supports B-tree indexes
-Bytea now supports LIKE, LIKE...ESCAPE, NOT LIKE, NOT LIKE...ESCAPE
-Bytea now supports concatenation
-New bytea functions: position, substring, trim, btrim, and length
-New encode() function mode, "escaped", converts minimally escaped bytea to/from text
-Add pg_database_encoding_max_length() (Tatsuo)
-Add pg_client_encoding() function (Tatsuo)
-now() returns time with millisecond precision (Thomas)
-New TIMESTAMP WITHOUT TIMEZONE data type (Thomas)
-Add ISO date/time specification with "T", yyyy-mm-ddThh:mm:ss (Thomas)
-New xid/int comparison functions (Hiroshi)
-Add precision to TIME, TIMESTAMP, and INVERVAL data types (Thomas)
-Modify type coercion logic to attempt binary-compatible functions first (Tom)
-New encode() function installed by default (Marko Kreen)
-Improved to_*() conversion functions (Karel Zak)
-Optimize LIKE/ILIKE when using single-byte encodings (Tatsuo)
-New functions in contrib/pgcrypto: crypt(), hmac(), encrypt(), gen_salt() (Marko Kreen)
-Correct description of translate() function (Bruce)
-Add INTERVAL argument for SET TIME ZONE (Thomas)
-Add INTERVAL YEAR TO MONTH (etc.) syntax (Thomas)
-Optimize length functions when using single-byte encodings (Tatsuo)
-Fix path_inter, path_distance, path_length, dist_ppath to handle closed paths (Curtis Barrett, Tom)
-octet_length(text) now returns non-compressed length (Tatsuo, Bruce)
-Handle "July" full name in date/time literals (Greg Sabino Mullane)
-Some datatype() function calls now evaluated differently
-Add support for Julian and ISO time specifications (Thomas)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Internationalization</title>
-<literallayout>
-National language support in psql, pg_dump, libpq, and server (Peter E)
-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)
-Make trim, ltrim, rtrim, btrim, lpad, rpad, translate multibyte aware (Tatsuo)
-Add LATIN5,6,7,8,9,10 support (Tatsuo)
-Add ISO 8859-5,6,7,8 support (Tatsuo)
-Correct LATIN5 to mean ISO-8859-9, not ISO-8859-5 (Tatsuo)
-Make mic2ascii() non-ASCII aware (Tatsuo)
-Reject invalid multibyte character sequences (Tatsuo)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>PL/pgSQL</title>
-<literallayout>
-Now uses portals for SELECT loops, allowing huge result sets (Jan)
-CURSOR and REFCURSOR support (Jan)
-Can now return open cursors (Jan)
-Add ELSEIF (Klaus Reger)
-Improve PL/pgSQL error reporting, including location of error (Tom)
-Allow IS or FOR key words in cursor declaration, for compatibility (Bruce)
-Fix for SELECT ... FOR UPDATE (Tom)
-Fix for PERFORM returning multiple rows (Tom)
-Make PL/pgSQL use the server's type coercion code (Tom)
-Memory leak fix (Jan, Tom)
-Make trailing semicolon optional (Tom)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>PL/Perl</title>
-<literallayout>
-New untrusted PL/Perl (Alex Pilosov)
-PL/Perl is now built on some platforms even if libperl is not shared (Peter E)
-</literallayout>
-    </sect3>
-
-   <sect3>
-    <title>PL/Tcl</title>
-<literallayout>
-Now reports errorInfo (Vsevolod Lobko)
-Add spi_lastoid function (bob@redivi.com)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>PL/Python</title>
-<literallayout>
-...is new (Andrew Bosma)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Psql</title>
-<literallayout>
-\d displays indexes in unique, primary groupings (Christopher Kings-Lynne)
-Allow trailing semicolons in backslash commands (Greg Sabino Mullane)
-Read password from /dev/tty if possible
-Force new password prompt when changing user and database (Tatsuo, Tom)
-Format the correct number of columns for Unicode (Patrice)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Libpq</title>
-<literallayout>
-New function PQescapeString() to escape quotes in command strings (Florian Weimer)
-New function PQescapeBytea() escapes binary strings for use as SQL string literals
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>JDBC</title>
-<literallayout>
-Return OID of INSERT (Ken K)
-Handle more data types (Ken K)
-Handle single quotes and newlines in strings (Ken K)
-Handle NULL variables (Ken K)
-Fix for time zone handling (Barry Lind)
-Improved Druid support
-Allow eight-bit characters with non-multibyte server (Barry Lind)
-Support BIT, BINARY types (Ned Wolpert)
-Reduce memory usage (Michael Stephens, Dave Cramer)
-Update DatabaseMetaData (Peter E)
-Add DatabaseMetaData.getCatalogs() (Peter E)
-Encoding fixes (Anders Bengtsson)
-Get/setCatalog methods (Jason Davies)
-DatabaseMetaData.getColumns() now returns column defaults (Jason Davies)
-DatabaseMetaData.getColumns() performance improvement (Jeroen van Vianen)
-Some JDBC1 and JDBC2 merging (Anders Bengtsson)
-Transaction performance improvements (Barry Lind)
-Array fixes (Greg Zoller)
-Serialize addition 
-Fix batch processing (Rene Pijlman)
-ExecSQL method reorganization (Anders Bengtsson)
-GetColumn() fixes (Jeroen van Vianen)
-Fix isWriteable() function (Rene Pijlman)
-Improved passage of JDBC2 conformance tests (Rene Pijlman)
-Add bytea type capability (Barry Lind)
-Add isNullable() (Rene Pijlman)
-JDBC date/time test suite fixes (Liam Stewart)
-Fix for SELECT 'id' AS xxx FROM table (Dave Cramer)
-Fix DatabaseMetaData to show precision properly (Mark Lillywhite)
-New getImported/getExported keys (Jason Davies)
-MD5 password encryption support (Jeremy Wohl)
-Fix to actually use type cache (Ned Wolpert)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>ODBC</title>
-<literallayout>
-Remove query size limit (Hiroshi)
-Remove text field size limit (Hiroshi)
-Fix for SQLPrimaryKeys in multibyte mode (Hiroshi)
-Allow ODBC procedure calls (Hiroshi)
-Improve boolean handing (Aidan Mountford)
-Most configuration options on setable via DSN (Hiroshi)
-Multibyte, performance fixes (Hiroshi)
-Allow driver to be used with iODBC or unixODBC (Peter E)
-MD5 password encryption support (Bruce)
-Add more compatibility functions to odbc.sql (Peter E)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>ECPG</title>
-<literallayout>
-EXECUTE ... INTO implemented (Christof Petig)
-Multiple row descriptor support (e.g. CARDINALITY) (Christof Petig)
-Fix for GRANT parameters (Lee Kindness)
-Fix INITIALLY DEFERRED bug
-Various bug fixes (Michael, Christof Petig)
-Auto allocation for indicator variable arrays (int *ind_p=NULL)
-Auto allocation for string arrays (char **foo_pp=NULL)
-ECPGfree_auto_mem fixed
-All function names with external linkage are now prefixed by ECPG
-Fixes for arrays of structures (Michael)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Misc. Interfaces</title>
-<literallayout>
-Python fix fetchone() (Gerhard Haring)
-Use UTF, Unicode in Tcl where appropriate (Vsevolod Lobko, Reinhard Max)
-Add Tcl COPY TO/FROM (ljb)
-Prevent output of default index op class in pg_dump (Tom)
-Fix libpgeasy memory leak (Bruce)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Build and Install</title>
-<literallayout>
-Configure, dynamic loader, and shared library fixes (Peter E)
-Fixes in QNX 4 port (Bernd Tegge)
-Fixes in Cygwin and Win32 ports (Jason Tishler, Gerhard Haring, Dmitry Yurtaev, Darko Prenosil, Mikhail Terekhov)
-Fix for Win32 socket communication failures (Magnus, Mikhail Terekhov)
-Hurd compile fix (Oliver Elphick)
-BeOS fixes (Cyril Velter)
-Remove configure --enable-unicode-conversion, now enabled by multibyte (Tatsuo)
-AIX fixes (Tatsuo, Andreas)
-Fix parallel make (Peter E)
-Install SQL language manual pages into OS-specific directories (Peter E)
-Rename config.h to pg_config.h (Peter E)
-Reorganize installation layout of header files (Peter E)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Source Code</title>
-<literallayout>
-Remove SEP_CHAR (Bruce)
-New GUC hooks (Tom)
-Merge GUC and command line handling (Marko Kreen)
-Remove EXTEND INDEX (Martijn van Oosterhout, Tom)
-New pgjindent utility to indent java code (Bruce)
-Remove define of true/false when compiling under C++ (Leandro Fanzone, Tom)
-pgindent fixes (Bruce, Tom)
-Replace strcasecmp() with strcmp() where appropriate (Peter E)
-Dynahash portability improvements (Tom)
-Add 'volatile' usage in spinlock structures
-Improve signal handling logic (Tom)
-</literallayout>
-   </sect3>
-
-   <sect3>
-    <title>Contrib</title>
-<literallayout>
-New contrib/rtree_gist (Oleg Bartunov, Teodor Sigaev)
-New contrib/tsearch full-text indexing (Oleg, Teodor Sigaev)
-Add contrib/dblink for remote database access (Joe Conway)
-contrib/ora2pg Oracle conversion utility (Gilles Darold)
-contrib/xml XML conversion utility (John Gray)
-contrib/fulltextindex fixes (Christopher Kings-Lynne)
-New contrib/fuzzystrmatch with levenshtein and metaphone, soundex merged (Joe Conway)
-Add contrib/intarray boolean queries, binary search, fixes (Oleg Bartunov)
-New pg_upgrade utility (Bruce)
-Add new pg_resetxlog options (Bruce, Tom)
-</literallayout>
-   </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 segements 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 permission 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 tuples 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
-	PostgreSQL code for many years.
-   </para>
-
-   <para>
-    Major changes in this release:
-
-    <variablelist>
-     <varlistentry>
-      <term>
-	Write-ahead Log (WAL)
-      </term>
-      <listitem>
-       <para>
-To maintain database consistency in case
-of an operating system crash, previous releases of PostgreSQL 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 may 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 NULLs 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 may 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>
-   </para>
-
-   <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 sub-selects (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 keyword 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 keyword 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 aloocation 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 tuples when source and
-    destination of a tuple 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->timestamp and timespan->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 & 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:
-
-    <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 INNER JOINs 
-	for this release. JOIN, NATURAL JOIN, JOIN/USING, JOIN/ON are
-	available, as are column correlation names.
-       </para>
-      </listitem>
-     </varlistentry>
-
-<!--
-     <varlistentry>
-      <term>
-       Upcoming Features
-      </term>
-      <listitem>
-       <para>
-	In 7.1 or 7.2, we plan to have outer joins, storage for very long rows, and a
-	write-ahead logging system.
-       </para>
-      </listitem>
-     </varlistentry>
--->
-    </variablelist>
-   </para>
-
-   <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 may 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:
-
-     <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 may not 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 may go up. If you are dealing with large amounts
-	of data, you may 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>
-    </para>
-
-   </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 permissions 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 permission 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 > 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>jens@jens.de</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>mascarim@yahoo.com</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 permissions 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;zakkr@zf.jcu.cz&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 keyword, 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 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 > 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 WIN32 compilation of libpq
-Alpha spinlock fix from Uncle George <email>gatgul@voicenet.com</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 Win32 (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>lamj@stat.cmu.edu</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 Win32 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;yucao@falcon.kla-tencor.com&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 expresssion 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 tuple from being created(Bruce)
-plpgsql fixes
-Allow port numbers 32k - 64k(Bruce)
-Add ^ precidence(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 PostgreSQL
-	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 PostgreSQL, 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<->float8 and text<->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 username containing a dash GRANT permissions
-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 permissions(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 suppports 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 NT/Win32 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 keyword 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 existance 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 Win32 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 Iishi
-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 can't 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 win32(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 permissions on 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 win32 using win32.mak(Magnus)
-Lo_read no longer stores trailing NULL(Bruce)
-Identifiers are now truncated to 31 characters internally(Bruce)
-Createuser options now availble 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 keyword, that is no longer used(Thomas)
-pg_dump -n flag to supress 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 documention(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 keyword 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 may need to start <application>postmaster</application> with the
-       <option>-i</option> flag.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Better password authorization mechanisms. Default table permissions 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 can not 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 may
-    think.  Vadim has put us on the big SQL map with subselects, and fully
-    functional ones too.  The only thing you can't 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 may 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 permission to PUBLIC by
-    default.  This was done because the ANSI standard requires it.  You can
-    of course GRANT any permissions 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
-    permissions now, not based on the underlying tables, so permissions 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 MergeJion(Vadim)
-
-Enhancements
-------------
-Subselects with EXISTS, IN, ALL, ANY keywords (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 <= 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 permissions(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 permissions 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 permissions.
-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 & 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 spin lock 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 tuples changed/inserted by a commnd
-	visible to the command itself (so we had multiple update of 
-	updated tuples, 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 tuples 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 & Peter)
-pg_password utility
-Return number of tuples 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 & 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 "<===>" with "<->"(Thomas)
-Replace "above" operator "!^" with ">^" and "below" operator "!|" with "<^"(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 & 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 & 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 & 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 & 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 may 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 "random" results in the random test should cause the "random" test
-  to be "failed", since the regression tests are evaluated using a simple
-  diff. However, "random" does not seem to produce random results on my 
-  test machine (Linux/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 < or <= 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 tuples re-incarnation 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 WIN32-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 postgress 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 unitialized 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 permissions
-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 & 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 distrubution(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 easly 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, centeralized #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/uninialized 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-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 depreciated 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 (appologies to any missed)
- * Kurt J. Lidl <lidl@va.pubnix.com> 
-	(missed in first run, but no less important)
- * Erich Stamberger <eberger@gewi.kfunigraz.ac.at>
- * Jason Wright <jason@shiloh.vnet.net>
- * Cees de Groot <C.deGroot@inter.NL.net>
- * ernst.molitor@uni-bonn.de
- * michael.siebenborn@ae3.Hypo.DE (Michael Siebenborn (6929))
- * Brian E. Gallew <geek+@cmu.edu>
- * Vadim B. Mikheev <vadim@sable.krasnoyarsk.su>
- * Adam Sussman <myddryn@vidya.com>
- * Chris Dunlop <chris@onthe.net.au>
- * Marc G. Fournier <scrappy@ki.net>
- * Dan McGuirk <mcguirk@indirect.com>
- * Dr_George_D_Detlefsen <drgeorge@ilt.com>
- * Erich Stamberger <eberger@gewi.kfunigraz.ac.at>
- * Massimo Dal Zotto <dz@cs.unitn.it>
- * Randy Kunkee <kunkee@Starbase.NeoSoft.COM>
- * Rick Weldon <rick@wisetech.com>
- * Thomas van Reimersdahl <reimersd@dali.techinfo.rwth-aachen.de>
- * david bennett <dave@bensoft.com>
- * ernst.molitor@uni-bonn.de
- * Julian Assange <proff@suburbia.net>
- * Bruce Momjian <maillist@candle.pha.pa.us>
- * Paul "Shag" Walmsley <ccshag@cclabs.missouri.edu>
- * "Alistair G. Crooks" <azcb0@sde.uts.amdahl.com>
--->
-</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 keywords
- * 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 keyword
-
-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
-   permissions
- *  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 may 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 -> int2
-		integer, int -> int4
-		float, real  -> 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" keyword.
-	For example:
-		GRANT SELECT ON foobar TO GROUP my_group;
-	The keyword '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 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 tuple 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 tuple 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:
-
-     <programlisting>
-  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
-     </programlisting>
-    </para>
-
-    <para>
-     Timing with <function>fsync()</function> enabled:
-
-     <programlisting>
-  Time   System
-  04:21  Dual Pentium Pro 180, 224MB, UW-SCSI, Linux 2.0.36, gcc 2.7.2.3 -O2 -m486
-     </programlisting>
-
-     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>
-<programlisting>
-  Time   System
-  02:26  Dual Pentium Pro 180, 96MB, UW-SCSI, Linux 2.0.30, gcc 2.7.2.1 -O2 -m486
-</programlisting>
-</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>
-]]>
-</appendix>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml
deleted file mode 100644
index f26319c463a..00000000000
--- a/doc/src/sgml/rules.sgml
+++ /dev/null
@@ -1,2026 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/rules.sgml,v 1.23 2002/04/19 23:13:53 tgl Exp $ -->
-
-<Chapter Id="rules">
-<Title>The Rule System</Title>
-
- <indexterm zone="rules">
-  <primary>rules</primary>
- </indexterm>
-
-   <note>
-    <title>Author</title>
-    <para>
-     Written by Jan Wieck.  Updates for 7.1 by Tom Lane.
-    </para>
-   </note>
-
-   <sect1 id="rules-intro">
-    <title>Introduction</title>
-
-<Para>
-     Production rule systems are conceptually simple, but
-     there are many subtle points involved in actually using
-     them. Some of these points and
-     the theoretical foundations of the <ProductName>PostgreSQL</ProductName>
-     rule system can be found in
-<XRef LinkEnd="STON90b">.
-</Para>
-
-<Para>
-     Some other database systems define active database rules. These
-     are usually stored procedures and triggers and are implemented
-     in <ProductName>PostgreSQL</ProductName> as functions and triggers.
-</Para>
-
-<Para>
-     The query rewrite rule system (the <firstterm>rule system</> from now on) 
-     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
-     power  of  this  rule system is discussed in 
-<XRef LinkEnd="ONG90">
- as well as
-<XRef LinkEnd="STON90b">.
-</para>
-
-  </sect1>
-
-<Sect1 id="querytree">
-<Title>What is a Query Tree?</Title>
-
-<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 query parser and the planner.
-    It takes the output of the parser, one query tree, and the rewrite
-    rules from the <FileName>pg_rewrite</FileName> catalog, which are
-    query trees too with some extra information, and creates zero or many
-    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 built
-    it are stored separately. These query trees are visible when starting
-    the <ProductName>PostgreSQL</ProductName> backend with debug level 4
-    and typing queries into the interactive backend interface. The rule
-    actions in the <FileName>pg_rewrite</FileName> system catalog are
-    also stored as query trees. They are not formatted like the debug
-    output, but they contain exactly the same information.
-</Para>
-
-<Para>
-    Reading a query tree requires some experience and it was a hard
-    time when I started to work on the rule system. I can remember
-    that I was standing at the coffee machine and I saw the cup
-    in a target list, water and coffee powder in a range table and all
-    the buttons in a qualification expression. Since 
-    <Acronym>SQL</Acronym> representations of query trees are
-    sufficient to understand the rule system, this document will
-    not teach how to read them. It might help to learn
-    it and the naming conventions are required in the later following
-    descriptions.
-</Para>
-
-<Sect2>
-<Title>The Parts of a Query tree</Title>
-
-<Para>
-    When reading the <Acronym>SQL</Acronym> representations of the 
-    query trees in this document 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
-	(SELECT, INSERT, UPDATE, DELETE) produced the parse 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 SELECT statement these are the relations given after
-	the FROM keyword.
-    </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
-	index 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 document 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>
-	SELECT queries
-	normally don't have a result relation. The special case
-	of a SELECT INTO is mostly identical to a CREATE TABLE,
-	INSERT ... SELECT sequence and is not discussed separately
-	here.
-    </Para>
-
-    <Para>
-        On INSERT, UPDATE and DELETE queries the result relation
-	is the table (or view!) where the changes take effect.
-    </Para>
-    </ListItem>
-    </VarListEntry>
-
-    <VarListEntry>
-    <Term>
-        the target list
-    </Term>
-    <ListItem>
-    <Para>
-        The target list is a list of expressions that define the result
-	of the query. In the case of a SELECT, the expressions are what
-	builds the final output of the query. They are the expressions
-	between the SELECT and the FROM keywords.  (* is just an
-	abbreviation for all the attribute names of a relation.  It is
-	expanded by the parser into the individual attributes, so the
-	rule system never sees it.)
-    </Para>
-
-    <Para>
-        DELETE queries don't need a target list because they don't
-	produce any result. In fact the planner will add a special CTID
-	entry to the empty target list. But this is after the rule
-	system and will be discussed later. For the rule system the
-	target list is empty.
-    </Para>
-
-    <Para>
-        In INSERT queries the target list describes the new rows that
-	should go into the result relation. It is the expressions in the VALUES
-	clause or the ones from the SELECT clause in INSERT ... SELECT.
-	Missing columns of the result relation will be filled in by the
-	planner with a constant NULL expression.
-    </Para>
-
-    <Para>
-        In UPDATE queries, the target list describes the new rows that should
-	replace the old ones. In the rule system, it contains just the
-	expressions from the SET attribute = expression part of the query.
-	The planner will add missing columns by inserting expressions that
-	copy the values from the old row into the new one. And it will add
-	the special CTID entry just as for DELETE too.
-    </Para>
-
-    <Para>
-        Every entry in the target list contains an expression that can
-	be a constant value, a variable pointing to an attribute 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 if the operation
-	(INSERT, UPDATE, DELETE or SELECT) for the final result row should be
-	executed or not. It is the 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 FROM clause.
-	For a simple query like SELECT FROM a, b, c the join tree is just
-	a list of the FROM items, because we are allowed to join them in
-	any order.  But when JOIN expressions --- particularly outer joins
-	--- are used, we have to join in the order shown by the joins.
-	The join tree shows the structure of the JOIN expressions.  The
-	restrictions associated with particular JOIN clauses (from ON or
-	USING expressions) are stored as qualification expressions attached
-	to those join tree nodes.  It turns out to be convenient to store
-	the top-level WHERE expression as a qualification attached to the
-	top-level join tree item, too.  So really the join tree represents
-	both the FROM and WHERE clauses of a SELECT.
-    </Para>
-    </ListItem>
-    </VarListEntry>
-
-    <VarListEntry>
-    <Term>
-        the others
-    </Term>
-    <ListItem>
-    <Para>
-        The other parts of the query tree like the ORDER BY 
-	clause aren't of interest here. The rule system
-	substitutes 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>
-</Sect2>
-</Sect1>
-
-<Sect1 id="rules-views">
-<Title>Views and the Rule System</Title>
-<indexterm zone="rules-views"><primary>rules</><secondary>and views</></>
-
-<Sect2>
-<Title>Implementation of Views in <ProductName>PostgreSQL</ProductName></Title>
-
-<Para>
-    Views in <ProductName>PostgreSQL</ProductName> are implemented
-    using the rule system. In fact there is absolutely no difference
-    between a
-
-<ProgramListing>
-CREATE VIEW myview AS SELECT * FROM mytab;
-</ProgramListing>
-    
-    compared against the two commands
-
-<ProgramListing>
-CREATE TABLE myview (<Replaceable>same attribute list as for mytab</Replaceable>);
-CREATE RULE "_RETURN" AS ON SELECT TO myview DO INSTEAD
-    SELECT * FROM mytab;
-</ProgramListing>
-    
-    because this is exactly what the CREATE VIEW 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
-    query parser, there is absolutely no difference between
-    a table and a view. They are the same thing - relations. That is the
-    important one for now.
-</Para>
-</Sect2>
-
-<Sect2>
-<Title>How SELECT Rules Work</Title>
-
-<Para>
-    Rules ON SELECT are applied to all queries as the
-    last step, even if the command
-    given is an INSERT, UPDATE or DELETE. And they have different
-    semantics from the others in that they modify the parse tree in
-    place instead of creating a new one.
-    So SELECT rules are described first.
-</Para>
-
-<Para>
-    Currently, there can be only one action in an ON SELECT rule, and it must
-    be an unconditional SELECT action that is INSTEAD. This restriction was
-    required to make rules safe enough to open them for ordinary users and
-    it restricts rules ON SELECT to real view rules.
-</Para>
-
-<Para>
-    The examples for this document 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
-    INSERT, UPDATE and DELETE operations so that the final result will
-    be a view that behaves like a real table with some magic functionality.
-    It 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>
-    The database needed to play with the examples is named <literal>al_bundy</literal>.
-    You'll see soon why this is the database name. And it needs the
-    procedural language <application>PL/pgSQL</> installed, because
-    we need a little min() function returning the lower of 2
-    integer values. We create that as
-
-<ProgramListing>
-CREATE FUNCTION min(integer, integer) RETURNS integer AS '
-    BEGIN
-        IF $1 < $2 THEN
-            RETURN $1;
-        END IF;
-        RETURN $2;
-    END;
-' LANGUAGE plpgsql;
-</ProgramListing>
-</Para>
-
-<Para>
-    The real tables we need in the first two rule system descriptions
-    are these:
-
-<ProgramListing>
-CREATE TABLE shoe_data (
-    shoename   char(10),      -- primary key
-    sh_avail   integer,       -- available # of pairs
-    slcolor    char(10),      -- preferred shoelace color
-    slminlen   float,         -- miminum shoelace length
-    slmaxlen   float,         -- maximum shoelace length
-    slunit     char(8)        -- length unit
-);
-
-CREATE TABLE shoelace_data (
-    sl_name    char(10),      -- primary key
-    sl_avail   integer,       -- available # of pairs
-    sl_color   char(10),      -- shoelace color
-    sl_len     float,         -- shoelace length
-    sl_unit    char(8)        -- length unit
-);
-
-CREATE TABLE unit (
-    un_name    char(8),       -- the primary key
-    un_fact    float          -- factor to transform to cm
-);
-</ProgramListing>
-
-    I think most of us wear shoes and can realize that this is
-    really useful data. Well there are shoes out in the world
-    that don't require shoelaces, but this doesn't make Al's
-    life easier and so we ignore it.
-</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 >= rsh.slminlen_cm
-       AND rsl.sl_len_cm <= rsh.slmaxlen_cm;
-</ProgramListing>
-
-    The CREATE VIEW command for the <Filename>shoelace</Filename> 
-    view (which is the simplest one we have)
-    will create a relation shoelace and an entry 
-    in <FileName>pg_rewrite</FileName>
-    that tells that there is a rewrite rule that must be applied
-    whenever the relation shoelace is referenced in a query's range table.
-    The rule has no rule qualification (discussed later, with the
-    non SELECT rules, since SELECT rules currently cannot have them) and
-    it is INSTEAD. Note that rule qualifications are not the same as
-    query qualifications! The rule's action has a query qualification.
-</Para>
-
-<Para>
-    The rule's action is one query tree that is a copy of the
-    SELECT statement in the view creation command.
-    
-    <Note>
-    <Title>Note</Title>
-    <Para>
-    The two extra range
-    table entries for NEW and OLD (named *NEW* and *CURRENT* for
-    historical reasons in the printed query tree) you can see in
-    the <Filename>pg_rewrite</Filename> entry aren't of interest
-    for SELECT rules.
-    </Para>
-    </Note>
-
-    Now we populate <Filename>unit</Filename>, <Filename>shoe_data</Filename>
-    and <Filename>shoelace_data</Filename> and Al types the first 
-    SELECT in his life:
-
-<ProgramListing>
-al_bundy=> INSERT INTO unit VALUES ('cm', 1.0);
-al_bundy=> INSERT INTO unit VALUES ('m', 100.0);
-al_bundy=> INSERT INTO unit VALUES ('inch', 2.54);
-al_bundy=> 
-al_bundy=> INSERT INTO shoe_data VALUES 
-al_bundy->     ('sh1', 2, 'black', 70.0, 90.0, 'cm');
-al_bundy=> INSERT INTO shoe_data VALUES 
-al_bundy->     ('sh2', 0, 'black', 30.0, 40.0, 'inch');
-al_bundy=> INSERT INTO shoe_data VALUES 
-al_bundy->     ('sh3', 4, 'brown', 50.0, 65.0, 'cm');
-al_bundy=> INSERT INTO shoe_data VALUES 
-al_bundy->     ('sh4', 3, 'brown', 40.0, 50.0, 'inch');
-al_bundy=> 
-al_bundy=> INSERT INTO shoelace_data VALUES 
-al_bundy->     ('sl1', 5, 'black', 80.0, 'cm');
-al_bundy=> INSERT INTO shoelace_data VALUES 
-al_bundy->     ('sl2', 6, 'black', 100.0, 'cm');
-al_bundy=> INSERT INTO shoelace_data VALUES 
-al_bundy->     ('sl3', 0, 'black', 35.0 , 'inch');
-al_bundy=> INSERT INTO shoelace_data VALUES 
-al_bundy->     ('sl4', 8, 'black', 40.0 , 'inch');
-al_bundy=> INSERT INTO shoelace_data VALUES 
-al_bundy->     ('sl5', 4, 'brown', 1.0 , 'm');
-al_bundy=> INSERT INTO shoelace_data VALUES 
-al_bundy->     ('sl6', 0, 'brown', 0.9 , 'm');
-al_bundy=> INSERT INTO shoelace_data VALUES 
-al_bundy->     ('sl7', 7, 'brown', 60 , 'cm');
-al_bundy=> INSERT INTO shoelace_data VALUES 
-al_bundy->     ('sl8', 1, 'brown', 40 , 'inch');
-al_bundy=> 
-al_bundy=> 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>
-
-    It's the simplest SELECT Al can do on our views, so we take this
-    to explain the basics of view rules.
-    The <literal>SELECT * FROM shoelace</literal> was interpreted by the parser and
-    produced the parse 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 in <Filename>pg_rewrite</Filename>
-    for any relation. When processing the range table entry for
-    <Filename>shoelace</Filename> (the only one up to now) it finds the
-    <literal>_RETURN</literal> rule with the parse tree
-
-<ProgramListing>
-<emphasis>SELECT s.sl_name, s.sl_avail,
-       s.sl_color, s.sl_len, s.sl_unit,
-       float8mul(s.sl_len, u.un_fact) AS sl_len_cm
-  FROM shoelace *OLD*, shoelace *NEW*,
-       shoelace_data s, unit u
- WHERE bpchareq(s.sl_unit, u.un_name);</emphasis>
-</ProgramListing>
-
-    Note that the parser changed the calculation and qualification into
-    calls to the appropriate functions. But
-    in fact this changes nothing.
-</Para>
-
-<Para>
-    To expand the view, the rewriter simply creates a subselect range-table
-    entry containing the rule's action parse tree, and substitutes this
-    range table entry for the original one that referenced the view.  The 
-    resulting rewritten parse tree is almost the same as if Al 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 sub-query's range table has two
-     extra entries shoelace *OLD*, shoelace *NEW*.  These entries don't
-     participate directly in the query, since they aren't referenced by
-     the sub-query's join tree or target list.  The rewriter uses them
-     to store the access permission check info 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 permissions 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 sub-query to see if any of them reference views.  (But it
-    won't expand *OLD* or *NEW* --- otherwise we'd have infinite recursion!)
-    In this example, there are no rewrite rules for shoelace_data or unit,
-    so rewriting is complete and the above is the final result given to
-    the planner.
-</Para>
-
-<Para>
-    Now we face Al with the problem that the Blues Brothers appear
-    in his shop and
-    want to buy some new shoes, and as the Blues Brothers are,
-    they want to wear the same shoes. And they want to wear them
-    immediately, so they need shoelaces too.
-</Para>
-
-<Para>
-    Al needs to know for which shoes currently in the store
-    he has the matching shoelaces (color and size) and where the
-    total number of exactly matching pairs is greater or equal to two.
-    We teach him what to do and he asks his database:
-
-<ProgramListing>
-al_bundy=> SELECT * FROM shoe_ready WHERE total_avail >= 2;
-shoename  |sh_avail|sl_name   |sl_avail|total_avail
-----------+--------+----------+--------+-----------
-sh1       |       2|sl1       |       5|          2
-sh3       |       4|sl7       |       7|          4
-(2 rows)
-</ProgramListing>
-
-    Al is a shoe guru and so he knows that only shoes of type sh1
-    would fit (shoelace sl7 is brown and shoes that need brown shoelaces
-    aren't shoes the Blues Brothers would ever wear).
-</Para>
-
-<Para>
-    The output of the parser this time is the parse 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 int4ge(shoe_ready.total_avail, 2);
-</ProgramListing>
-
-    The first rule applied will be the one for the 
-    <Filename>shoe_ready</Filename> view and it results in the
-    parse 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 >= rsh.slminlen_cm
-           AND rsl.sl_len_cm <= rsh.slmaxlen_cm) shoe_ready
- WHERE int4ge(shoe_ready.total_avail, 2);
-</ProgramListing>
-
-    Similarly, the rules for <Filename>shoe</Filename> and
-    <Filename>shoelace</Filename> are substituted into the range table of
-    the sub-query, 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 >= rsh.slminlen_cm
-           AND rsl.sl_len_cm <= rsh.slmaxlen_cm) shoe_ready
- WHERE int4ge(shoe_ready.total_avail, 2);
-</ProgramListing>
-
-    It turns out that the planner will collapse this tree into a two-level
-    query tree: the bottommost selects will be <quote>pulled up</quote> into the middle
-    select since there's no need to process them separately.  But the
-    middle select will remain separate from the top, because it contains
-    aggregate functions.  If we pulled those up it would change the behavior
-    of the topmost select, which we don't want.  However, collapsing the
-    query tree is an optimization that the rewrite system doesn't
-    have to concern itself with.
-
-    <Note>
-    <Title>Note</Title>
-    <Para>
-    There is currently no recursion stopping mechanism for view
-    rules in the rule system (only for the other kinds of rules).
-    This doesn't hurt much, because the only way to push this
-    into an endless loop (blowing up the
-    backend until it reaches the memory limit)
-    is to create tables and then setup the
-    view rules by hand with CREATE RULE in such a way, that
-    one selects from the other that selects from the one.
-    This could never happen if CREATE VIEW is used because
-    for the first CREATE VIEW, the second relation does not exist
-    and thus the first view cannot select from the second.
-    </Para>
-    </Note>
-</Para>
-
-</Sect2>
-
-<Sect2>
-<Title>View Rules in Non-SELECT Statements</Title>
-
-<Para>
-    Two details of the parse tree aren't touched in the description of
-    view rules above. These are the command type and the result relation.
-    In fact, view rules don't need this information.
-</Para>
-
-<Para>
-    There are only a few differences between a parse tree for a SELECT
-    and one for any other command. Obviously they have another command type
-    and this time the result relation points to the range table entry where
-    the result should go. Everything else is absolutely the same. 
-    So having two tables t1 and t2 with attributes
-    a and b, the parse trees for the two statements
-
-<ProgramListing>
-SELECT t2.b FROM t1, t2 WHERE t1.a = t2.a;
-
-UPDATE t1 SET b = t2.b WHERE t1.a = t2.a;
-</ProgramListing>
-
-    are nearly identical.
-
-    <ItemizedList>
-        <ListItem>
-	<Para>
-	    The range tables contain entries for the tables t1 and t2.
-	</Para>
-        </ListItem>
-
-        <ListItem>
-	<Para>
-	    The target lists contain one variable that points to attribute
-	    b of the range table entry for table t2.
-	</Para>
-        </ListItem>
-
-        <ListItem>
-	<Para>
-	    The qualification expressions compare the attributes a of both
-	    ranges for equality.
-	</Para>
-        </ListItem>
-
-        <ListItem>
-	<Para>
-	    The join trees show a simple join between t1 and t2.
-	</Para>
-        </ListItem>
-    </ItemizedList>
-
-    The consequence is, that both parse trees result in similar execution
-    plans. They are both joins over the two tables. For the UPDATE
-    the missing columns from t1 are added to the target list by the planner 
-    and the final parse tree will read as
-
-<ProgramListing>
-UPDATE t1 SET a = t1.a, b = t2.b WHERE t1.a = t2.a;
-</ProgramListing>
-
-    and thus the executor run over the join will produce exactly the
-    same result set as a
-
-<ProgramListing>
-SELECT t1.a, t2.b FROM t1, t2 WHERE t1.a = t2.a;
-</ProgramListing>
-    
-    will do. But there is a little problem in UPDATE. The executor does
-    not care what the results from the join it is doing are meant
-    for. It just produces a result set of rows. The difference that one
-    is a SELECT command and the other is an UPDATE is handled in the
-    caller of the executor. The caller still knows (looking at the
-    parse tree) that this is an UPDATE, and he knows that this result
-    should go into table 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 UPDATE (and also in DELETE) statements: the current tuple ID (CTID).
-    This is a system attribute containing the file
-    block number and position in the block for the row. Knowing the table,
-    the CTID can be used to retrieve the original t1 row to be updated.
-    After adding the 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. At this moment, table rows aren't overwritten and this is why
-    ABORT TRANSACTION is fast. In an UPDATE, the new result row is inserted
-    into the table (after stripping CTID) and in the tuple header of the row 
-    that CTID pointed to the cmax and xmax entries are set to the current
-    command counter and current transaction ID. Thus the old row is hidden
-    and after the transaction committed the vacuum cleaner can really move
-    it out.
-</Para>
-
-<Para>
-    Knowing all that, we can simply apply view rules in absolutely
-    the same way to any command. There is no difference.
-</Para>
-</Sect2>
-
-<Sect2>
-<Title>The Power of Views in <ProductName>PostgreSQL</ProductName></Title>
-
-<Para>
-    The above demonstrates how the rule system incorporates
-    view definitions into the original parse tree. In the second example
-    a simple SELECT from one view created a final parse tree that is
-    a join of 4 tables (unit is used twice with different names).
-</Para>
-
-<Sect3>
-<Title>Benefits</Title>
-
-<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 parse tree. And this is still the situation
-    when the original query is already a join over views.
-    Now the planner has to decide which is
-    the best path to execute the query. 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 now.
-</Para>
-</Sect3>
-</Sect2>
-
-<Sect2 id="rules-views-update">
-<Title>What about updating a view?</Title>
-<indexterm zone="rules-views-update"><primary>views</><secondary>updating</></>
-
-<Para>
-    What happens if a view is named as the target relation for an INSERT,
-    UPDATE, or DELETE?  After doing the substitutions described above,
-    we will have a query tree in which the result relation points at a
-    subquery range table entry.  This will not work, so the rewriter throws
-    an error if it sees it has produced such a thing.
-</Para>
-
-<Para>
-    To change this we can define rules that modify the behavior
-    of non-SELECT queries. This is the topic of the next section.
-</Para>
-</Sect2>
-
-</Sect1>
-
-<Sect1 id="rules-insert">
-<Title>Rules on INSERT, UPDATE and DELETE</Title>
-
-<Sect2>
-<Title>Differences from View Rules</Title>
-
-<Para>
-    Rules that are defined ON INSERT, UPDATE and DELETE are
-    totally different from the view rules described
-    in the previous section. First, their CREATE RULE
-    command allows more:
-
-    <ItemizedList>
-        <ListItem>
-	<Para>
-	    They can have no action.
-	</Para>
-	</ListItem>
-
-        <ListItem>
-	<Para>
-	    They can have multiple actions.
-	</Para>
-	</ListItem>
-
-        <ListItem>
-	<Para>
-	    The keyword INSTEAD is optional.
-	</Para>
-	</ListItem>
-
-        <ListItem>
-	<Para>
-	    The pseudo relations NEW and OLD become useful.
-	</Para>
-	</ListItem>
-
-        <ListItem>
-	<Para>
-	    They can have rule qualifications.
-	</Para>
-	</ListItem>
-    </ItemizedList>
-
-    Second, they don't modify the parse tree in place. Instead they
-    create zero or many new parse trees and can throw away the
-    original one.
-</Para>
-</sect2>
-<Sect2>
-<Title>How These Rules Work</Title>
-
-<Para>
-    Keep the syntax
-
-<ProgramListing>
-CREATE RULE rule_name AS ON event
-    TO object [WHERE rule_qualification]
-    DO [INSTEAD] [action | (actions) | NOTHING];
-</ProgramListing>
-
-    in mind.
-    In the following, <firstterm>update rules</> means rules that are defined
-    ON INSERT, UPDATE or DELETE.
-</Para>
-
-<Para>
-    Update rules get applied by the rule system when the result
-    relation and the command type of a parse tree are equal to the
-    object and event given in the CREATE RULE command.
-    For update rules, the rule system creates a list of parse trees.
-    Initially the parse tree list is empty.
-    There can be zero (NOTHING keyword), one or multiple actions.
-    To simplify, we look at a rule with one action. This rule
-    can have a qualification or not and it can be INSTEAD or not.
-</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 NEW and/or OLD pseudo relations
-    which are basically the relation given as object (but with a
-    special meaning).
-</Para>
-
-<Para>
-    So we have four cases that produce the following parse trees for
-    a one-action rule.
-</Para>
-<Para>
-    <ItemizedList>
-    <ListItem>
-    <Para>
-        No qualification and not INSTEAD:
-        <ItemizedList>
-	    <ListItem>
-	    <Para>
-	        The parse tree from the rule action where the
-		original parse tree's qualification has been added.
-	    </Para>
-	    </ListItem>
-	</ItemizedList>
-    </Para>
-    </ListItem>
-
-    <ListItem>
-    <Para>
-        No qualification but INSTEAD:
-        <ItemizedList>
-	    <ListItem>
-	    <Para>
-	        The parse tree from the rule action where the
-		original parse tree's qualification has been added.
-	    </Para>
-	    </ListItem>
-	</ItemizedList>
-    </Para>
-    </ListItem>
-
-    <ListItem>
-    <Para>
-        Qualification given and not INSTEAD:
-        <ItemizedList>
-	    <ListItem>
-	    <Para>
-	        The parse tree from the rule action where the rule
-		qualification and the original parse tree's 
-		qualification have been added.
-	    </Para>
-	    </ListItem>
-	</ItemizedList>
-    </Para>
-    </ListItem>
-
-    <ListItem>
-    <Para>
-        Qualification given and INSTEAD:
-        <ItemizedList>
-	    <ListItem>
-	    <Para>
-	        The parse tree from the rule action where the rule
-		qualification and the original parse tree's 
-		qualification have been added.
-	    </Para>
-	    </ListItem>
-
-	    <ListItem>
-	    <Para>
-	        The original parse tree where the negated rule
-		qualification has been added.
-	    </Para>
-	    </ListItem>
-	</ItemizedList>
-    </Para>
-    </ListItem>
-    </ItemizedList>
-</para>
-<Para>
-    Finally, if the rule is not INSTEAD, the unchanged original parse tree is
-    added to the list. Since only qualified INSTEAD rules already add the
-    original parse tree, we end up with either one or two output parse trees
-    for a rule with one action.
-</Para>
-
-<Para>
-    For ON INSERT rules, the original query (if not suppressed by INSTEAD)
-    is done before any actions added by rules.  This allows the actions to
-    see the inserted row(s).  But for ON UPDATE and 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 parse trees generated from rule actions are thrown into the
-    rewrite system again and maybe more rules get applied resulting
-    in more or less parse trees.
-    So the parse trees in the rule actions must have either another command type
-    or another result relation. Otherwise this recursive process will end up in a loop.
-    There is a compiled in recursion limit of currently 10 iterations.
-    If after 10 iterations there are still update rules to apply the
-    rule system assumes a loop over multiple rule definitions and reports
-    an error.
-</Para>
-
-<Para>
-    The parse trees found in the actions of the <Filename>pg_rewrite</Filename>
-    system catalog are only templates. Since they can reference the
-    range-table entries for NEW and OLD, some substitutions have to be made
-    before they can be used. For any reference to NEW, the target list of
-    the original query is searched for a corresponding entry. If found,
-    that entry's expression replaces the reference. Otherwise
-    NEW means the same as OLD (for an UPDATE) or is replaced by NULL
-    (for an INSERT). Any reference to OLD is replaced by a
-    reference to the range-table entry which is the result relation.
-</Para>
-
-<Para>
-    After we are done applying update rules, we apply view rules to the
-    produced parse 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>
-
-<Para>
-    We want to trace changes to the sl_avail column in the
-    <Filename>shoelace_data</Filename> relation. So we setup a
-    log table and a rule that conditionally writes a log entry when
-    an UPDATE is performed on <Filename>shoelace_data</Filename>.
-
-<ProgramListing>
-CREATE TABLE shoelace_log (
-    sl_name    char(10),      -- 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 != OLD.sl_avail
-    DO INSERT INTO shoelace_log VALUES (
-                                    NEW.sl_name,
-                                    NEW.sl_avail,
-                                    current_user,
-                                    current_timestamp
-                                );
-</ProgramListing>
-</Para>
-
-<Para>
-    Now Al does
-
-<ProgramListing>
-al_bundy=> UPDATE shoelace_data SET sl_avail = 6                       
-al_bundy->     WHERE sl_name = 'sl7';
-</ProgramListing>
-
-    and we look at the log table.
-
-<ProgramListing>
-al_bundy=> 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>
-
-    That's what we expected. What happened in the background is the following.
-    The parser created the parse tree (this time the parts of the original
-    parse tree are highlighted because the base of operations is the
-    rule action for update rules).
-
-<ProgramListing>
-<emphasis>UPDATE shoelace_data SET sl_avail = 6
-  FROM shoelace_data shoelace_data
- WHERE bpchareq(shoelace_data.sl_name, 'sl7');</emphasis>
-</ProgramListing>
-
-    There is a rule <literal>log_shoelace</literal> that is ON UPDATE with the rule
-    qualification expression
-
-<ProgramListing>
-int4ne(NEW.sl_avail, OLD.sl_avail)
-</ProgramListing>
-
-    and one 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 is a little strange-looking since you can't normally write
-    INSERT ... VALUES ... FROM.  The FROM clause here is just to indicate
-    that there are range-table entries in the parse tree for *NEW* and *OLD*.
-    These are needed so that they can be referenced by variables in the
-    INSERT command's query tree.
-</Para>
-
-<Para>
-    The rule is a qualified non-INSTEAD rule, so the rule system
-    has to return two parse trees: the modified rule action and the original
-    parse tree. In the first step the range table of the original query is
-    incorporated into the rule's action parse 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 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 int4ne(*NEW*.sl_avail, *OLD*.sl_avail)</emphasis>;
-</ProgramListing>
-
-    This is even stranger-looking, since INSERT ... VALUES doesn't have
-    a WHERE clause either, but the planner and executor will have no
-    difficulty with it.  They need to support this same functionality
-    anyway for INSERT ... SELECT.
-
-    In step 3 the original parse tree's qualification is added,
-    restricting the result set further to only the rows touched
-    by the original parse tree.
-
-<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 int4ne(*NEW*.sl_avail, *OLD*.sl_avail)
-   <emphasis>AND bpchareq(shoelace_data.sl_name, 'sl7')</emphasis>;
-</ProgramListing>
-
-    Step 4 substitutes NEW references by the target list entries from the
-    original parse tree or with 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 int4ne(<emphasis>6</emphasis>, *OLD*.sl_avail)
-   AND bpchareq(shoelace_data.sl_name, 'sl7');
-</ProgramListing>
-
-    Step 5 changes 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 int4ne(6, <emphasis>shoelace_data.sl_avail</emphasis>)
-   AND bpchareq(shoelace_data.sl_name, 'sl7');
-</ProgramListing>
-
-    That's it.  Since the rule is not INSTEAD, we also output the
-    original parse tree.  In short, the output from the rule system
-    is a list of two parse trees that are the same as the statements:
-
-<ProgramListing>
-INSERT INTO shoelace_log VALUES(
-       shoelace_data.sl_name, 6,
-       current_user, current_timestamp
-  FROM shoelace_data
- WHERE 6 != 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 defines. The substitutions and the qualifications
-    added 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.  This
-    time the original parse tree does not contain a target list
-    entry for sl_avail, so NEW.sl_avail will get replaced by
-    shoelace_data.sl_avail resulting in the extra query
-
-<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> != shoelace_data.sl_avail
-   AND shoelace_data.sl_name = 'sl7';
-</ProgramListing>
-
-    and that qualification will never be true. It will also
-    work if the original query modifies multiple rows. So if Al
-    would issue the command
-
-<ProgramListing>
-UPDATE shoelace_data SET sl_avail = 0
- WHERE sl_color = 'black';
-</ProgramListing>
-
-    four rows in fact get updated (sl1, sl2, sl3 and sl4).
-    But sl3 already has sl_avail = 0. This time, the original
-    parse trees qualification is different and that results
-    in the extra parse tree
-
-<ProgramListing>
-INSERT INTO shoelace_log SELECT
-       shoelace_data.sl_name, 0,
-       current_user, current_timestamp
-  FROM shoelace_data
- WHERE 0 != shoelace_data.sl_avail
-   AND <emphasis>shoelace_data.sl_color = 'black'</emphasis>;
-</ProgramListing>
-
-    This parse 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 parse tree is
-    executed last.
-    If the UPDATE would have been executed first, all the rows
-    are already set to zero, so the logging INSERT
-    would not find any row where 0 != shoelace_data.sl_avail.
-</Para>
-</Sect3>
-
-</Sect2>
-
-<Sect2>
-<Title>Cooperation with Views</Title>
-
-<Para>
-    A simple way to protect view relations from the mentioned
-    possibility that someone can try to INSERT, UPDATE and DELETE
-    on them is to let those parse trees get
-    thrown away. We 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 Al now tries to do any of these operations on the view
-    relation <Filename>shoe</Filename>, the rule system will
-    apply the rules. Since the rules have
-    no actions and are INSTEAD, the resulting list of
-    parse 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.
-
-    <Note>
-    <Title>Note</Title>
-    <Para>
-    This way might irritate frontend applications because
-    absolutely nothing happened on the database and thus, the
-    backend will not return anything for the query. Not
-    even a <symbol>PGRES_EMPTY_QUERY</symbol> will be available in <application>libpq</>.
-    In <application>psql</application>, nothing happens. This might change in the future.
-    </Para>
-    </Note>
-
-</Para>
-
-<Para>
-    A more sophisticated way to use the rule system is to
-    create rules that rewrite the parse tree into one that
-    does the right operation on the real tables. To do that
-    on the <Filename>shoelace</Filename> 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>
-
-    Now there is a pack of shoelaces arriving in Al's shop and it has
-    a big part list. Al is not that good in calculating and so
-    we don't want him to manually update the shoelace view.
-    Instead we setup two little tables, one where he can
-    insert the items from the part list and one with a special
-    trick. The create commands for these are:
-
-<ProgramListing>
-CREATE TABLE shoelace_arrive (
-    arr_name    char(10),
-    arr_quant   integer
-);
-
-CREATE TABLE shoelace_ok (
-    ok_name     char(10),
-    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 Al can sit down and do whatever until
-
-<ProgramListing>
-al_bundy=> SELECT * FROM shoelace_arrive;
-arr_name  |arr_quant
-----------+---------
-sl3       |       10
-sl6       |       20
-sl8       |       20
-(3 rows)
-</ProgramListing>
-
-    is exactly what's on the part list. We take a quick look
-    at the current data,
-    
-<ProgramListing>
-al_bundy=> 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>
-
-    move the arrived shoelaces in
-
-<ProgramListing>
-al_bundy=> INSERT INTO shoelace_ok SELECT * FROM shoelace_arrive;
-</ProgramListing>
-
-    and check the results
-
-<ProgramListing>
-al_bundy=> 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)
-
-al_bundy=> 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>
-
-    It's a long way from the one INSERT ... SELECT to these
-    results. And its description will be the last in this
-    document (but not the last example :-). First there was 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 it
-    into
-
-<ProgramListing>
-UPDATE shoelace SET
-       sl_avail = int4pl(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 bpchareq(shoelace.sl_name, showlace_arrive.arr_name);
-</ProgramListing>
-
-    and throws away the original INSERT on <Filename>shoelace_ok</Filename>.
-    This rewritten query is passed to the rule system again and
-    the second applied rule <literal>shoelace_upd</literal> produced
-
-<ProgramListing>
-UPDATE shoelace_data SET
-       sl_name = shoelace.sl_name,
-       sl_avail = int4pl(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 showlace_data
- WHERE bpchareq(shoelace.sl_name, showlace_arrive.arr_name)
-   AND bpchareq(shoelace_data.sl_name, shoelace.sl_name);
-</ProgramListing>
-
-    Again it's an INSTEAD rule and the previous parse tree is trashed.
-    Note that this query still uses the view <Filename>shoelace</Filename>.
-    But the rule system isn't finished with this loop 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 = int4pl(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 showlace_data,
-       shoelace *OLD*, shoelace *NEW*,
-       shoelace_data s, unit u
- WHERE bpchareq(s.sl_name, showlace_arrive.arr_name)
-   AND bpchareq(shoelace_data.sl_name, s.sl_name);
-</ProgramListing>
-
-    Again an update rule has been applied and so the wheel
-    turns on and we are in rewrite round 3. This time rule
-    <literal>log_shoelace</literal> gets applied what produces the extra
-    parse tree
-
-<ProgramListing>
-INSERT INTO shoelace_log SELECT
-       s.sl_name,
-       int4pl(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 showlace_data,
-       shoelace *OLD*, shoelace *NEW*,
-       shoelace_data s, unit u,
-       shoelace_data *OLD*, shoelace_data *NEW*
-       shoelace_log shoelace_log
- WHERE bpchareq(s.sl_name,  showlace_arrive.arr_name)
-   AND bpchareq(shoelace_data.sl_name, s.sl_name);
-   AND int4ne(int4pl(s.sl_avail, shoelace_arrive.arr_quant), s.sl_avail);
-</ProgramListing>
-    
-    After that the rule system runs out of rules and returns the 
-    generated parse trees.
-    So we end up with two final parse trees that are equal 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 != 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 turns out, that the <Filename>shoelace_data</Filename>
-    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 INSERT will be
-
-<ProgramListing>
-Nested Loop
-  ->  Merge Join
-        ->  Seq Scan
-              ->  Sort
-                    ->  Seq Scan on s
-        ->  Seq Scan
-              ->  Sort
-                    ->  Seq Scan on shoelace_arrive
-  ->  Seq Scan on shoelace_data
-</ProgramListing>
-
-    while omitting the extra range table entry would result in a
-
-<ProgramListing>
-Merge Join
-  ->  Seq Scan
-        ->  Sort
-              ->  Seq Scan on s
-  ->  Seq Scan
-        ->  Sort
-              ->  Seq Scan on shoelace_arrive
-</ProgramListing>
-
-    that totally produces the same entries in the log relation.
-    Thus, the rule system caused one extra scan on the
-    <Filename>shoelace_data</Filename> relation that is
-    absolutely not necessary. And the same obsolete scan
-    is done once more in the UPDATE. But it was a really hard
-    job to make that all possible at all.
-</Para>
-
-<Para>
-    A final demonstration of the <ProductName>PostgreSQL</ProductName>
-    rule system and its power. There is a cute blonde that
-    sells shoelaces. And what Al could never realize, she's not
-    only cute, she's smart too - a little too smart. Thus, it
-    happens from time to time that Al orders shoelaces that
-    are absolutely not sellable. This time he ordered 1000 pairs
-    of magenta shoelaces and since another kind is currently not
-    available but he committed to buy some, he also prepared
-    his database for pink ones.
-
-<ProgramListing>
-al_bundy=> INSERT INTO shoelace VALUES 
-al_bundy->     ('sl9', 0, 'pink', 35.0, 'inch', 0.0);
-al_bundy=> INSERT INTO shoelace VALUES 
-al_bundy->     ('sl10', 1000, 'magenta', 40.0, 'inch', 0.0);
-</ProgramListing>
-
-    Since this happens often, we must lookup for shoelace entries,
-    that fit for absolutely no shoe sometimes. We could do that in
-    a complicated statement every time, or we can setup a view
-    for it. The view for this is
-
-<ProgramListing>
-CREATE VIEW shoelace_obsolete AS
-    SELECT * FROM shoelace WHERE NOT EXISTS
-        (SELECT shoename FROM shoe WHERE slcolor = sl_color);
-</ProgramListing>
-
-    Its output is
-
-<ProgramListing>
-al_bundy=> SELECT * FROM shoelace_obsolete;
-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>
-
-    For the 1000 magenta shoelaces we must debt Al before we can
-    throw 'em away, but that's another problem. The pink entry we delete.
-    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_candelete AS
-    SELECT * FROM shoelace_obsolete WHERE sl_avail = 0;
-</ProgramListing>
-
-    and do it this way:
-
-<ProgramListing>
-DELETE FROM shoelace WHERE EXISTS
-    (SELECT * FROM shoelace_candelete
-             WHERE sl_name = shoelace.sl_name);
-</ProgramListing>
-
-    <foreignphrase>Voilà</foreignphrase>:
-
-<ProgramListing>
-al_bundy=> 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>
-
-    A DELETE on a view, with a subselect qualification that
-    in total uses 4 nesting/joined views, where one of them
-    itself has a subselect qualification containing a view
-    and where calculated view columns are used,
-    gets rewritten into 
-    one single parse tree that deletes the requested data
-    from a real table.
-</Para>
-
-<Para>
-    I think there are only a few situations out in the real
-    world, where such a construct is necessary. But
-    it makes me feel comfortable that it works.
-</Para>
-
-    <formalpara>
-    <Title>The truth is:</Title>
-    <Para>
-    Doing this I found one more bug while writing this document.
-    But after fixing that I was a little amazed that it works at all.
-    </Para>
-    </formalpara>
-</Sect2>
-
-</Sect1>
-
-<Sect1 id="rules-permissions">
-<Title>Rules and Permissions</Title>
-
-<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. Using update rules, 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
-    permissions of the rule owner, not the user invoking the rule.
-    This means, that a user does only need the required permissions
-    for the tables/views he names 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 bool);
-CREATE VIEW phone_number AS
-    SELECT person, phone FROM phone_data WHERE NOT private;
-GRANT SELECT ON phone_number TO secretary;
-</ProgramListing>
-    
-    Nobody except him (and the database superusers) can access the
-    phone_data table. But due to the GRANT, the secretary can SELECT from the
-    phone_number view. The rule system will rewrite
-    the SELECT from phone_number into a SELECT from phone_data and add the qualification
-    that only entries where private is false are wanted. Since the
-    user is the owner of phone_number, the read access to phone_data
-    is now checked against his permissions and the query is considered
-    granted. The check for accessing 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 permissions 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 public. Then, anyone
-    can see the phone_number data through the secretaries view.
-    What the secretary cannot do is to create a view that directly
-    accesses phone_data (actually he can, but it will not work since
-    every access aborts the transaction during the permission checks).
-    And as soon as the user will notice, that the secretary opened
-    his phone_number view, he can REVOKE his access. Immediately any
-    access to the secretaries view will fail.
-</Para>
-
-<Para>
-    Someone might think that this rule by rule checking is a security
-    hole, but in fact it isn't. If this would not work, the secretary
-    could setup a table with the same columns as 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 GRANT means <quote>I trust you</quote>.
-    If someone you trust does the thing above, it's time to
-    think it over and then REVOKE.
-</Para>
-
-<Para>
-    This mechanism does also work for update rules. In the examples
-    of the previous section, the owner of the tables in Al's database
-    could GRANT SELECT, INSERT, UPDATE and DELETE on the shoelace view to al.
-    But only SELECT on shoelace_log. The rule action to write log entries
-    will still be executed successfully. And Al could see the log entries.
-    But he cannot create fake entries, nor could he manipulate or remove
-    existing ones.
-
-    <Note>
-    <Title>Warning</Title>
-    <Para>
-    GRANT ALL currently includes RULE permission. This means the granted
-    user could drop the rule, do the changes and reinstall it. I think
-    this should get changed quickly.
-    </Para>
-    </Note>
-</Para>
-</Sect1>
-
-<Sect1 id="rules-triggers">
-<Title>Rules versus Triggers</Title>
-
-<Para>
-    Many things that can be done using triggers can also be
-    implemented using the <ProductName>PostgreSQL</ProductName>
-    rule system. What currently cannot be implemented by
-    rules are some kinds of constraints. It is possible,
-    to place a qualified rule that rewrites a query to 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 for now.
-</Para>
-
-<Para>
-    On the other hand a trigger that is fired on INSERT 
-    on a view can do the same as a rule, put the data somewhere
-    else and suppress the insert in the view. But it cannot
-    do the same thing on UPDATE or DELETE, because there is
-    no real data in the view relation that could be scanned
-    and thus the trigger would never get called. Only a rule
-    will help.
-</Para>
-
-<Para>
-    For the things that can be implemented by both,
-    it depends on the usage of the database, which is the best.
-    A trigger is fired for any row affected once. A rule manipulates
-    the parse tree or generates an additional one. So if many
-    rows are affected in one statement, a rule issuing one extra
-    query would usually do a better job than a trigger that is
-    called for any single row and must execute his operations
-    this many times.
-</Para>
-
-<Para>
-    For example: 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 index on <structfield>hostname</> is unique.
-    The <structfield>hostname</> column contains the full qualified domain
-    name of the computer. The rule/trigger should constraint
-    delete rows from software that reference the deleted host.
-    Since the trigger is called for each individual row
-    deleted from computer, it can use the statement
-
-<ProgramListing>
-DELETE FROM software WHERE hostname = $1;
-</ProgramListing>
-
-    in a prepared and saved plan and pass the <structfield>hostname</> 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>
-
-    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 computer is scanned by index (fast) and the
-    query issued by the trigger would also be an index scan (fast too).
-    The extra query from the rule would be a
-
-<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
-
-<ProgramListing>
-Nestloop
-  ->  Index Scan using comp_hostidx on computer
-  ->  Index Scan using soft_hostidx on software
-</ProgramListing>
-
-    So there would be not that much difference in speed between
-    the trigger and the rule implementation. With the next delete
-    we want to get rid of all the 2000 computers where the <structfield>hostname</> starts
-    with 'old'. There are two possible queries to do that. One is
-
-<ProgramListing>
-DELETE FROM computer WHERE hostname >= 'old'
-                       AND hostname <  'ole'
-</ProgramListing>
-
-    Where the plan for the rule query will be a 
-
-<ProgramListing>
-Hash Join
-  ->  Seq Scan on software
-  ->  Hash
-    ->  Index Scan using comp_hostidx on computer
-</ProgramListing>
-
-    The other possible query is a
-
-<ProgramListing>
-DELETE FROM computer WHERE hostname ~ '^old';
-</ProgramListing>
-
-    with the execution plan
-
-<ProgramListing>
-Nestloop
-  ->  Index Scan using comp_hostidx on computer
-  ->  Index Scan using soft_hostidx on software
-</ProgramListing>
-
-    This shows, that the planner does not realize that the
-    qualification for the <structfield>hostname</> on computer could also be
-    used for an index scan on software when there are
-    multiple qualification expressions combined with AND, what
-    he does in the regexp version of the query. The trigger will
-    get invoked once for any of the 2000 old computers that
-    have to be deleted and that will result in one index scan
-    over computer and 2000 index scans for the software. The
-    rule implementation will do it with two queries over indexes.
-    And it depends on the overall size of the software table if
-    the rule will still be faster in the sequential scan situation. 2000
-    query executions over the SPI manager take some time, even
-    if all the index blocks to look them up will soon appear in
-    the cache.
-</Para>
-
-<Para>
-    The last query we look at is a
-
-<ProgramListing>
-DELETE FROM computer WHERE manufacurer = 'bim';
-</ProgramListing>
-
-    Again this could result in many rows to be deleted from
-    computer. So the trigger will again fire many queries into
-    the executor. But the rule plan will again be the nested loop over
-    two index scans. Only using another index on computer:
-
-<ProgramListing>
-Nestloop
-  ->  Index Scan using comp_manufidx on computer
-  ->  Index Scan using soft_hostidx on software
-</ProgramListing>
-
-    resulting from the rules query
-
-<ProgramListing>
-DELETE FROM software WHERE computer.manufacurer = 'bim'
-                       AND software.hostname = computer.hostname;
-</ProgramListing>
-
-    In any of these cases, the extra queries from the rule system will be
-    more or less independent from the number of affected rows
-    in a query. 
-</Para>
-
-<Para>
-    Another situation is cases on UPDATE where it depends on the
-    change of an attribute if an action should be performed or
-    not. In <ProductName>PostgreSQL</ProductName> version 6.4, the
-    attribute specification for rule events is disabled (it will have
-    its comeback latest in 6.5, maybe earlier 
-    - stay tuned). So for now 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>
-    Rules will only be significantly slower than triggers if
-    their actions result in large and bad qualified joins, a situation
-    where the planner fails. They are a big hammer.
-    Using a big hammer without caution can cause big damage. But
-    used with the right touch, they can hit any nail on the head.
-</Para>
-</Sect1>
-
-</Chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
deleted file mode 100644
index 1a26e9d7942..00000000000
--- a/doc/src/sgml/runtime.sgml
+++ /dev/null
@@ -1,2736 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.119 2002/06/16 00:09:11 momjian Exp $
--->
-
-<Chapter Id="runtime">
- <Title>Server Run-time Environment</Title>
-
- <Para>
-  This chapter discusses how to set up and run the database server
-  and the interactions with the operating system.
- </para>
-
- <sect1 id="postgres-user">
-  <title>The <productname>PostgreSQL</productname> user account</title>
-
-  <indexterm>
-   <primary>postgres user</primary>
-  </indexterm>
-
-  <para>
-   As with any other server daemon that is connected to outside world,
-   it is advisable to run <productname>PostgreSQL</productname> under a
-   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 <quote>nobody</quote> 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 but is by no
-   means required.
-  </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>
-
-  <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 instead.) A
-   database cluster is a collection of databases is accessible by a
-   single instance of a running database server. After initialization, a
-   database cluster will contain a database named
-   <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.
-  </para>
-
-  <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 <command>initdb</command>, which is
-   installed with <productname>PostgreSQL</productname>. The desired
-   file system location of your database system is indicated by the
-   <option>-D</option> option, for example
-<screen>
-<prompt>$</> <userinput>initdb -D /usr/local/pgsql/data</userinput>
-</screen>
-   Note that you must execute this command while logged into the
-   <productname>PostgreSQL</productname> user account, which is
-   described in the previous section.
-  </para>
-
-  <tip>
-   <para>
-    <indexterm>
-     <primary><envar>PGDATA</envar></primary>
-    </indexterm>
-    As an alternative to the <option>-D</option> option, you can set
-    the environment variable <envar>PGDATA</envar>.
-   </para>
-  </tip>
-
-  <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
-   <productname>PostgreSQL</productname> user. Here is how this might
-   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</userinput>
-</screen>
-  </para>
-
-  <para>
-   <command>initdb</command> will refuse to run if the data directory
-   looks like it 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
-   <productname>PostgreSQL</productname> user.
-  </para>
-
-  <para>
-   However, while the directory contents are secure, the default
-   <filename>pg_hba.conf</filename> authentication method of
-   <literal>trust</literal> allows any local user to connect to the
-   database and even become the database superuser. If you don't trust
-   other local users, we recommend you use <command>initdb</command>'s
-   <option>-W</option> or <option>--pwprompt</option> option to assign a
-   password to the database superuser. After <command>initdb</command>,
-   modify <filename>pg_hba.conf</filename> to use <literal>md5</> or
-   <literal>password</> instead of <literal>trust</> authentication
-   <emphasis>before</> you start the server for the first time. (Other,
-   approaches include using <literal>ident</literal> authentication or
-   file system permissions to restrict connections. See <xref
-   linkend="client-authentication"> for more information.
-  </para>
-
-  <para>
-   <indexterm><primary>locale</></>
-   <indexterm><primary>LC_COLLATE</></>
-   <command>initdb</command> also initializes the default 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">.  One surprise you might encounter while running
-   <command>initdb</command> is a notice similar to this:
-<screen>
-The database cluster will be initialized with locale de_DE.
-This locale setting will prevent the use of indexes for pattern matching
-operations.  If that is a concern, rerun initdb with the collation order
-set to "C".  For more information see the Administrator's Guide.
-</screen>
-   This is intended to warn you that the currently selected locale
-   will cause indexes to be sorted in an order that prevents them from
-   being used for LIKE and regular-expression searches. If you need
-   good performance in such searches, you should set your current
-   locale to <literal>C</> and re-run <command>initdb</command>, e.g.,
-   by running <literal>initdb --lc-collate=C</literal>. The sort
-   order used within a particular database cluster is set by
-   <command>initdb</command> and cannot be changed later, short of
-   dumping all data, rerunning <command>initdb</command>, and
-   reloading the data. So it's important to make this choice correctly
-   the first time.
-  </para>
- </sect1>
-
- <sect1 id="postmaster-start">
-  <title>Starting the database server</title>
-
-  <para>
-   <indexterm>
-    <primary>postmaster</primary>
-   </indexterm>
-   Before anyone can access the database, you must start the database
-   server. The database server is called
-   <firstterm>postmaster</firstterm>. The postmaster 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>postmaster -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 in the environment variable <envar>PGDATA</envar>.
-   If neither of these succeed, it will fail.
-  </para>
-
-  <para>
-   To start the <application>postmaster</application> in the
-   background, use the usual shell syntax:
-<screen>
-$ <userinput>postmaster -D /usr/local/pgsql/data &gt; logfile 2&gt;&amp;1 &amp;</userinput>
-</screen>
-   It is an 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>
-   <indexterm>
-    <primary>TCP/IP</primary>
-   </indexterm>
-   The postmaster also takes a number of other command line options. For
-   more information, see the reference page and <xref
-   linkend="runtime-config"> below. In particular, in order for the
-   server to accept TCP/IP connections (rather than just Unix domain
-   socket ones), you must specify the <option>-i</option> option.
-  </para>
-
-  <para>
-   <indexterm>
-    <primary>pg_ctl</primary>
-   </indexterm>
-   This shell syntax can get tedious quickly.  Therefore the shell
-   script wrapper <application>pg_ctl</application> 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 in the postmaster. <application>pg_ctl</application> is also
-   capable of stopping the server.
-  </para>
-
-  <para>
-   Normally, you will want to start the database server when the
-   computer boots. Auto-start scripts are operating-system specific.
-   There are a few distributed with
-   <productname>PostgreSQL</productname> in the
-   <filename>/contrib/start-scripts</> directory. This may 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. (Always
-   replace these with the proper installation directory and the user
-   name.)
-
-   <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</></>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On <productname>OpenBSD</productname>, add the following lines
-      to the file <filename>/etc/rc.local</filename>:
-      <indexterm><primary>OpenBSD</></>
-<programlisting>
-if [ -x /usr/local/pgsql/bin/pg_ctl -a -x /usr/local/pgsql/bin/postmaster ]; 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</></>
-<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</></>
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      On <productname>Solaris</productname>, create a file called
-      <filename>/etc/init.d/postgresql</filename> which should contain
-      the following line:
-      <indexterm><primary>Solaris</></>
-<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
-      <literal>S99postgresql</>.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-  </para>
-
-   <para>
-    While the <application>postmaster</application> is running, its
-    <acronym>PID</acronym> is in the file
-    <filename>postmaster.pid</filename> in the data directory. This is
-    used to prevent multiple postmasters running in the same data
-    directory, and can also be used for shutting down the postmaster.
-   </para>
-
-   <sect2 id="postmaster-start-failures">
-    <title>Server Start-up Failures</title>
-
-    <para>
-     There are several common reasons the postmaster might fail to
-     start. Check the postmaster's log file, or start it by hand
-     (without redirecting standard output or standard error) and see
-     what error messages appear. Some of the error messages are
-     self-explanatory, but some are not, as shown below:
-    </para>
-
-    <para>
-<screen>
-FATAL: StreamServerPort: bind() failed: Address already in use
-        Is another postmaster already running on that port?
-</screen>
-     This usually means just what it suggests: you tried to start
-     another postmaster 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 may
-     be a different problem. For example, trying to start a postmaster
-     on a reserved port number may draw something like:
-<screen>
-$ <userinput>postmaster -i -p 666</userinput>
-FATAL: StreamServerPort: bind() failed: Permission denied
-        Is another postmaster already running on that port?
-</screen>
-    </para>
-
-    <para>
-     A message like:
-<screen>
-IpcMemoryCreate: shmget(key=5440001, size=83918612, 01600) failed: Invalid argument
-FATAL 1:  ShmemCreate: cannot create region
-</screen>
-     probably means your kernel's limit on the size of shared memory is
-     smaller than the buffer area <productname>PostgreSQL</productname>
-     is trying to create (83918612 bytes in this example). Or it could
-     mean that you don't have System-V-style shared memory support
-     configured into your kernel at all. As a temporary workaround, you
-     can try starting the postmaster with a smaller-than-normal number
-     of buffers (<option>-B</option> switch). You will eventually want
-     to reconfigure your kernel to increase the allowed shared memory
-     size. You may see this message when trying to start multiple
-     postmasters on the same machine if their total space requested
-     exceeds the kernel limit.
-    </para>
-
-    <para>
-     An error like:
-<screen>
-IpcSemaphoreCreate: semget(key=5440026, num=16, 01600) failed: No space left on device
-</screen>
-     does <emphasis>not</emphasis> mean you've run out of disk space. It
-     means your kernel's limit on the number of System V semaphores is
-     smaller than the number <productname>PostgreSQL</productname> wants
-     to create. As above, you may be able to work around the problem by
-     starting the postmaster with a reduced number of backend processes
-     (<option>-N</option> switch), but you'll eventually want to
-     increase the kernel limit.
-    </para>
-
-    <para>
-     If you get an <quote>illegal system call</> error, it is likely
-     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>
-
-    <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 up. 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 the
-     <option>-i</option> option to allow the postmaster to accept TCP/IP
-     connections.
-    </para>
-
-    <para>
-     Alternatively, you'll get this when attempting Unix-socket
-     communication to a local postmaster:
-<screen>
-psql: could not connect to server: Connection refused
-        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 postmaster
-     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 postmaster 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> may
-     indicate more fundamental problems, like lack of network
-     connectivity.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="runtime-config">
-   <Title>Run-time configuration</Title>
-
-   <indexterm>
-    <primary>configuration</primary>
-    <secondary>server</secondary>
-   </indexterm>
-
-   <para>
-    There are a lot of configuration parameters that affect the behavior
-    of the database system. Here we describe how to set them and the
-    following subsections will discuss each in detail.
-   </para>
-
-   <para>
-    All parameter names are case-insensitive. Every parameter takes a
-    value of one of the four types: Boolean, integer, floating point,
-    and string. Boolean values are <literal>ON</literal>,
-    <literal>OFF</literal>, <literal>TRUE</literal>,
-    <literal>FALSE</literal>, <literal>YES</literal>,
-    <literal>NO</literal>, <literal>1</literal>, <literal>0</literal>
-    (case-insensitive) or any non-ambiguous prefix of these.
-   </para>
-
-   <para>
-    One way to set these options is to edit the file
-    <filename>postgresql.conf</filename> in the data directory. (A
-    default file is installed there.) An example of what this file might
-    look like is:
-<programlisting>
-# This is a comment
-log_connections = yes
-syslog = 2
-search_path = '$user, public'
-</programlisting>
-    As you see, options are one per line. The equal sign between name
-    and value is optional. Whitespace is insignificant and blank lines
-    are ignored. Hash marks (<quote>#</quote>) introduce comments
-    anywhere.  Parameter values that are not simple identifiers or
-    numbers should be single-quoted.
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>SIGHUP</primary>
-    </indexterm>
-    The configuration file is reread whenever the postmaster receives a
-    <systemitem>SIGHUP</> signal (which is most easily sent by means of
-    <literal>pg_ctl reload</>). The postmaster also propagates this
-    signal to all currently running backend processes so that existing
-    sessions also get the new value. Alternatively, you can send the
-    signal to a single backend process directly.
-   </para>
-
-   <para>
-    A second way to set these configuration parameters is to give them
-    as a command line option to the postmaster, such as:
-<programlisting>
-postmaster -c log_connections=yes -c syslog=2
-</programlisting>
-    which would have the same effect as the previous example.
-    Command-line options override any conflicting settings in
-    <filename>postgresql.conf</filename>.
-   </para>
-
-   <para>
-    Occasionally it is also useful to give a command line option to
-    one particular backend 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 libpq-based client application, not just
-    <application>psql</application>.) Note that this won't work for
-    options that are fixed when the server is started, such as the port
-    number.
-   </para>
-
-   <para>
-    Some options can be changed in individual SQL sessions with the
-    <command>SET</command> command, for example:
-<screen>
-=&gt; <userinput>SET ENABLE_SEQSCAN TO OFF;</userinput>
-</screen>
-    See the SQL command language reference for details on the syntax.
-   </para>
-
-   <para>
-    Furthermore, it is possible to assign a set of option 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 <literal>ALTER DATABASE</literal> and <literal>ALTER
-    USER</literal>, respectively, are used to configure these settings.
-    Such per-database settings override anything received from the postmaster
-    or the configuration file, and in turn are overridden by per-user
-    settings.
-   </para>
-
-   <sect2 id="runtime-config-optimizer">
-    <title>Planner and Optimizer Tuning</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><varname>CPU_INDEX_TUPLE_COST</varname> (<type>floating point</type>)</term>
-      <listitem>
-       <para>
-        Sets the query optimizer's estimate of the cost of processing
-	each index tuple during an index scan. This is measured as a
-	fraction of the cost of a sequential page fetch.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><varname>CPU_OPERATOR_COST</varname> (<type>floating point</type>)</term>
-      <listitem>
-       <para>
-        Sets the optimizer's estimate of the cost of processing each
-	operator in a WHERE clause. This is measured as a fraction of
-	the cost of a sequential page fetch.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><varname>CPU_TUPLE_COST</varname> (<type>floating point</type>)</term>
-      <listitem>
-       <para>
-        Sets the query optimizer's estimate of the cost of processing
-	each tuple during a query. This is measured as a fraction of
-	the cost of a sequential page fetch.
-       </para>
-      </listitem>
-     </varlistentry>
-    
-     <varlistentry>
-      <term><varname>EFFECTIVE_CACHE_SIZE</varname> (<type>floating point</type>)</term>
-      <listitem>
-       <para>
-        Sets the optimizer's assumption about the effective size of the
-        disk cache (that is, the portion of the kernel's disk cache that
-        will be used for <productname>PostgreSQL</productname> data
-        files). This is measured in disk pages, which are normally 8 kB
-        each.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>ENABLE_HASHJOIN</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of hash-join plan
-        types. The default is on. This is used for debugging the
-        query planner.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>index scan</primary>
-      </indexterm>
-
-      <term><varname>ENABLE_INDEXSCAN</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of index-scan plan
-        types. The default is on. This is used to debugging the
-        query planner.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>ENABLE_MERGEJOIN</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of merge-join plan
-        types. The default is on. This is used for debugging the
-        query planner.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>ENABLE_NESTLOOP</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of nested-loop join
-        plans. It's not possible 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
-        on. This is used for debugging the query planner.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>sequential scan</primary>
-      </indexterm>
-
-      <term><varname>ENABLE_SEQSCAN</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of sequential scan
-        plan types. It's not possible 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 on. This is used for debugging the query planner.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>ENABLE_SORT</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of explicit sort
-	steps. It's not possible 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 on. This is used for debugging the query planner.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>ENABLE_TIDSCAN</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables the query planner's use of <acronym>TID</> scan plan
-        types. The default is on. This is used for debugging the
-        query planner.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>genetic query optimization</primary>
-      </indexterm>
-      <indexterm>
-       <primary>GEQO</primary>
-       <see>genetic query optimization</see>
-      </indexterm>
-
-      <term><varname>GEQO</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables or disables genetic query optimization, which is an
-        algorithm that attempts to do query planning without exhaustive
-        searching. This is on by default. See also the various other
-        <varname>GEQO_</varname> settings.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>GEQO_EFFORT</varname> (<type>integer</type>)</term>
-      <term><varname>GEQO_GENERATIONS</varname> (<type>integer</type>)</term>
-      <term><varname>GEQO_POOL_SIZE</varname> (<type>integer</type>)</term>
-      <term><varname>GEQO_RANDOM_SEED</varname> (<type>integer</type>)</term>
-      <term><varname>GEQO_SELECTION_BIAS</varname> (<type>floating point</type>)</term>
-      <listitem>
-       <para>
-        Various tuning parameters for the genetic query optimization
-        algorithm: The pool size is the number of individuals in one
-        population. Valid values are between 128 and 1024. If it is set
-        to 0 (the default) a pool size of 2^(QS+1), where QS is the
-        number of FROM items in the query, is taken. The effort is used
-        to calculate a default for generations. Valid values are between
-        1 and 80, 40 being the default. Generations specifies the number
-        of iterations in the algorithm. The number must be a positive
-        integer. If 0 is specified then <literal>Effort *
-        Log2(PoolSize)</literal> is used. The run time of the algorithm
-        is roughly proportional to the sum of pool size and generations.
-        The selection bias is the selective pressure within the
-        population. Values can be from 1.50 to 2.00; the latter is the
-        default. The random seed can be set to get reproducible results
-        from the algorithm. If it is set to -1 then the algorithm
-        behaves non-deterministically.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>GEQO_THRESHOLD</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Use genetic query optimization to plan queries with at least
-        this many <literal>FROM</> items involved. (Note that a
-        <literal>JOIN</> construct counts as only one <literal>FROM</>
-        item.) The default is 11. For simpler queries it is usually best
-        to use the deterministic, exhaustive planner. This parameter
-        also controls how hard the optimizer will try to merge subquery
-        <literal>FROM</literal> clauses into the upper query.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>RANDOM_PAGE_COST</varname> (<type>floating point</type>)</term>
-      <listitem>
-       <para>
-        Sets the query optimizer's estimate of the cost of a
-        nonsequentially fetched disk page. This is measured as a
-        multiple of the cost of a sequential page fetch.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <note>
-    <para>
-     Unfortunately, there is no well-defined method for determining
-     ideal values for the family of <quote>COST</quote> variables that
-     were just described. You are encouraged to experiment and share
-     your findings.
-    </para>
-   </note>
-
-   </sect2>
-
-   <sect2 id="logging">
-    <title>Logging and Debugging</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><varname>SERVER_MIN_MESSAGES</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        This controls how much detail is written to the server logs. The
-        default is <literal>NOTICE</>. 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</>. Later values send less 
-	detail to the logs. <literal>LOG</> has a different precedence 
-	here than in <literal>CLIENT_MIN_MESSAGES</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>CLIENT_MIN_MESSAGES</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        This controls how much detail is written to the client. The
-        default is <literal>NOTICE</>. Valid values are
-        <literal>DEBUG5</>, <literal>DEBUG4</>, <literal>DEBUG3</>,
-        <literal>DEBUG2</>, <literal>DEBUG1</>, <literal>LOG</>,
-        <literal>NOTICE</>, <literal>WARNING</>, and <literal>ERROR</>. 
-	Later values send less information to the user. <literal>LOG</> 
-	has a different precedence here than in 
-	<literal>SERVER_MIN_MESSAGES</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>DEBUG_ASSERTIONS</varname> (<type>boolean</type>)</term>
-      <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 option, the macro <literal>USE_ASSERT_CHECKING</literal>
-        must be defined when <productname>PostgreSQL</productname> is
-        built (see the configure option
-        <literal>--enable-cassert</literal>). Note that
-        <literal>DEBUG_ASSERTIONS</literal> defaults to on if
-        <productname>PostgreSQL</productname> has been built this way.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>DEBUG_PRINT_QUERY</varname> (<type>boolean</type>)</term>
-      <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>
-      <term><varname>DEBUG_PRETTY_PRINT</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        These flags enable various debugging output to be sent to the
-	server log.  For each executed query, prints either the query text,
-	the resulting parse tree, the query rewriter output, or the execution
-	plan. <option>DEBUG_PRETTY_PRINT</option> indents these displays
-	to produce a more readable but much longer output format.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>EXPLAIN_PRETTY_PRINT</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Determines whether <command>EXPLAIN VERBOSE</> uses the indented
-	or non-indented format for displaying detailed querytree dumps.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>HOSTNAME_LOOKUP</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        By default, connection logs only show the IP address of the
-        connecting host. If you want it to show the host name you can
-        turn this on, but depending on your host name resolution setup
-        it might impose a non-negligible performance penalty. This
-        option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>LOG_CONNECTIONS</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        This outputs a line to the server logs detailing each successful
-        connection. This is off by default, although it is probably very
-        useful. This option can only be set at server start or in the
-        <filename>postgresql.conf</filename> configuration file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>LOG_PID</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Prefixes each server message in the logfile with the process ID of
-        the backend process. This is useful to sort out which messages
-        pertain to which connection. The default is off.  This parameter
-        does not affect messages logged via syslog(), which always contain
-        the process ID.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>LOG_TIMESTAMP</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Prefixes each server log message with a time stamp. The default
-        is off.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SHOW_QUERY_STATS</varname> (<type>boolean</type>)</term>
-      <term><varname>SHOW_PARSER_STATS</varname> (<type>boolean</type>)</term>
-      <term><varname>SHOW_PLANNER_STATS</varname> (<type>boolean</type>)</term>
-      <term><varname>SHOW_EXECUTOR_STATS</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        For each query, write performance statistics of the respective
-        module to the server log. This is a crude profiling
-        instrument.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SHOW_SOURCE_PORT</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Shows the outgoing port number of the connecting host in the
-        connection log messages. You could trace back the port number
-        to find out what user initiated the connection. Other than
-        that, it's pretty useless and therefore off by default. This
-        option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>STATS_COMMAND_STRING</varname> (<type>boolean</type>)</term>
-      <term><varname>STATS_BLOCK_LEVEL</varname> (<type>boolean</type>)</term>
-      <term><varname>STATS_ROW_LEVEL</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        These flags determine what information backends send to the statistics
-	collector process: current commands, block-level activity statistics,
-	or row-level activity statistics.  All default to off.  Enabling
-	statistics collection costs a small amount of time per query, but
-	is invaluable for debugging and performance tuning.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>STATS_RESET_ON_SERVER_START</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        If on, collected statistics are zeroed out whenever the server
-        is restarted. If off, statistics are accumulated across server
-        restarts. The default is on. This option can only be set at
-        server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>STATS_START_COLLECTOR</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Controls whether the server should start the statistics-collection
-	subprocess.  This is on by default, but may be turned off if you
-	know you have no interest in collecting statistics.  This option
-	can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SYSLOG</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        <productname>PostgreSQL</productname> allows the use of
-        <systemitem>syslog</systemitem> for logging. If this option is
-        set to 1, messages go both to <systemitem>syslog</> and the
-        standard output. A setting of 2 sends output only to
-        <systemitem>syslog</>. (Some messages will still go to the
-        standard output/error.) The default is 0, which means
-        <systemitem>syslog</> is off. This option must be set at server
-        start.
-       </para>
-       <para>
-        To use <systemitem>syslog</>, the build of
-        <productname>PostgreSQL</productname> must be configured with
-        the <option>--enable-syslog</option> option.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SYSLOG_FACILITY</varname> (<type>string</type>)</term>
-       <listitem>
-        <para>
-          This option determines the <application>syslog</application>
-          <quote>facility</quote> to be used when
-          <application>syslog</application> is enabled. You may choose
-          from LOCAL0, LOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6,
-          LOCAL7; the default is LOCAL0. See also the documentation of
-          your system's <application>syslog</application>.
-        </para>
-       </listitem>
-     </varlistentry>
-     
-     <varlistentry>
-      <term><varname>SYSLOG_IDENT</varname> (<type>string</type>)</term>
-       <listitem>
-        <para>
-         If logging to <application>syslog</> is enabled, this option
-         determines the program name used to identify
-         <productname>PostgreSQL</productname> messages in
-         <application>syslog</application> log messages. The default is
-         <literal>postgres</literal>.
-        </para>
-       </listitem>
-      </varlistentry>
-
-     <varlistentry>
-      <term><varname>TRACE_NOTIFY</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Generates a great amount of debugging output for the
-        <command>LISTEN</command> and <command>NOTIFY</command>
-        commands.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-   </sect2>
-
-   <sect2 id="runtime-config-general">
-    <title>General operation</title>
-
-   <para>
-    <variablelist>
-     <varlistentry>
-      <term><varname>AUSTRALIAN_TIMEZONES</varname> (<type>bool</type>)</term>
-      <indexterm><primary>Australian time zones</></>
-      <listitem>
-       <para>
-        If set to true, <literal>CST</literal>, <literal>EST</literal>,
-        and <literal>SAT</literal> are interpreted as Australian
-        time zones rather than as North American Central/Eastern
-        time zones and Saturday. The default is false.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>AUTHENTICATION_TIMEOUT</varname> (<type>integer</type>)</term>
-      <indexterm><primary>timeout</><secondary>authentication</></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 breaks the connection. This prevents
-        hung clients from occupying a connection indefinitely. This
-        option can only be set at server start or in the
-        <filename>postgresql.conf</filename> file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>CLIENT_ENCODING</varname> (<type>string</type>)</term>
-      <indexterm><primary>character set encoding</></>
-      <listitem>
-       <para>
-        Sets the client-side encoding for multibyte character sets.
-	The default is to use the database encoding.
-       </para>
-       <para>
-        This option is only available if
-        <productname>PostgreSQL</productname> was built with multibyte
-        support.
-      </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>DATESTYLE</varname> (<type>string</type>)</term>
-      <indexterm><primary>date style</></>
-      <listitem>
-       <para>
-        Sets the display format for dates, as well as the rules for
-	interpreting ambiguous input dates.
-        The default is <literal>ISO, US</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>deadlock</primary>
-       <secondary>timeout</secondary>
-      </indexterm>
-      <indexterm>
-       <primary>timeout</primary>
-       <secondary>deadlock</secondary>
-      </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 slow, 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 starting check 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 1000 (i.e., one second),
-        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 the lock will be released before
-        the waiter decides to check for deadlock. This option can only
-        be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>transaction isolation level</primary>
-      </indexterm>
-
-      <term><varname>DEFAULT_TRANSACTION_ISOLATION</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        Each SQL transaction has an isolation level, which can be either
-        <quote>read committed</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 the <citetitle>PostgreSQL User's Guide</citetitle> and
-        the command <command>SET TRANSACTION</command> for more
-        information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>DYNAMIC_LIBRARY_PATH</varname> (<type>string</type>)</term>
-      <indexterm><primary>dynamic_library_path</></>
-      <indexterm><primary>dynamic loading</></>
-      <listitem>
-       <para>
-        If a dynamically loadable module needs to be opened and the
-        specified name does not have a directory component (i.e. the
-        name does not contain a slash), the system will search this
-        path for the specified file.  (The name that is used is the
-        name specified in the <command>CREATE FUNCTION</command> or
-        <command>LOAD</command> command.)
-       </para>
-
-       <para>
-        The value for dynamic_library_path has to be a colon-separated
-        list of absolute directory names. If a directory name starts
-        with the special value <literal>$libdir</literal>, the
-        compiled-in <productname>PostgreSQL</productname> package
-        library directory is substituted. This where the modules
-        provided by the <productname>PostgreSQL</productname>
-        distribution are installed. (Use <literal>pg_config
-        --pkglibdir</literal> to print the name of this directory.) For
-        example:
-        <informalexample>
-<programlisting>
-dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
-</programlisting>
-        </informalexample>
-       </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>
-      <term><varname>SEARCH_PATH</varname> (<type>string</type>)</term>
-      <indexterm><primary>search_path</></>
-      <indexterm><primary>namespaces</></>
-      <listitem>
-       <para>
-        This variable specifies the order in which namespaces are searched
-	when an object (table, datatype, function, etc) is referenced by a
-	simple name with no schema component.  When there are objects of
-	identical names in different namespaces, the one found first
-	in the search path is used.  An object that is not in any of the
-	namespaces in the search path can only be referenced by specifying
-	its containing namespace with a qualified (dotted) name.
-       </para>
-
-       <para>
-        The value for search_path has to be a comma-separated
-        list of namespace (schema) names.  If one of the list items is
-        the special value <literal>$user</literal>, then the namespace
-	having the same name as the SESSION_USER is substituted, if there
-	is such a namespace.  (If not, <literal>$user</literal> is ignored.)
-       </para>
-
-       <para>
-        The system catalog namespace, <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.
-	It should also be noted that the temporary-table namespace,
-	<literal>pg_temp_nnn</>, is implicitly searched before any of
-	these.
-       </para>
-
-       <para>
-        When objects are created without specifying a particular target
-	namespace, they will be placed in the first namespace 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 namespace named <literal>public</>).
-	This supports shared use of a database (where no users
-	have private namespaces, and all share use of <literal>public</>),
-	private per-user namespaces, and combinations of these.  Other
-	effects can be obtained by altering the default search path
-	setting, either globally or per-user.
-       </para>
-
-       <para>
-        By default, a newly created database will contain a world-writable
-	namespace named <literal>public</>, but no private namespaces.
-	The administrator may choose to restrict permissions on
-	<literal>public</> or even remove it, if that suits his purposes.
-       </para>
-
-       <para>
-        The current effective value of the search path can be examined
-	via the SQL 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 requests appearing in <varname>search_path</varname>
-	were resolved.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>fsync</primary>
-      </indexterm>
-
-      <term><varname>FSYNC</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        If this option is on, the <productname>PostgreSQL</> backend
-        will use the <function>fsync()</> system call in several places
-        to make sure that updates are physically written to disk. This
-        insures that a database installation will recover to a
-        consistent state after an operating system or hardware crash.
-        (Crashes of the database server itself are <emphasis>not</>
-        related to this.)
-       </para>
-
-       <para>
-        However, this operation does slow down
-        <productname>PostgreSQL</> because at transaction commit it has
-        wait for the operating system to flush the write-ahead log.
-        Without <function>fsync</>, the operating system is allowed to
-        do its best in buffering, sorting, and delaying writes, which
-        can considerably increase performance. However, if the system
-        crashes, the results of the last few committed transactions may
-        be lost in part or whole. In the worst case, unrecoverable data
-        corruption may occur.
-       </para>
-
-       <para>
-        For the above reasons, some administrators always leave it off,
-        some turn it off only for bulk loads, where there is a clear
-        restart point if something goes wrong, and some leave it on just
-        to be on the safe side. Because it is always safe, the default
-        is on. If you trust your operating system, your hardware, and
-        your utility company (or better your UPS), you might want to
-        disable <varname>fsync</varname>.
-       </para>
-
-       <para>
-        It should be noted that the performance penalty of doing
-        <function>fsync</>s is considerably less in
-        <productname>PostgreSQL</> version 7.1 and later. If you
-        previously suppressed <function>fsync</>s for performance
-        reasons, you may wish to reconsider your choice.
-       </para>
-
-       <para>
-	This option can only be set at server start or in the
-	<filename>postgresql.conf</filename> file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>KRB_SERVER_KEYFILE</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        Sets the location of the Kerberos server key file. See
-        <xref linkend="kerberos-auth"> for details.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>LC_MESSAGES</varname> (<type>string</type>)</term>
-      <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>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>LC_MONETARY</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        Sets the locale to use for formatting monetary amounts.
-        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>
-      <term><varname>LC_NUMERIC</varname> (<type>string</type>)</term>
-      <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>
-      <term><varname>LC_TIME</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        Sets the locale to use for formatting date and time values,
-        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>
-      <term><varname>MAX_CONNECTIONS</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Determines the maximum number of concurrent connections to the
-        database server. The default is 32 (unless altered while
-        building the server). This parameter can only be set at server
-        start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>MAX_EXPR_DEPTH</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Sets the maximum expression nesting depth of the parser. The
-        default value is high enough for any normal query, but you can
-        raise it if needed. (But if you raise it too high, you run
-        the risk of backend crashes due to stack overflow.)
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>MAX_FILES_PER_PROCESS</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Sets the maximum number of simultaneously open files in each
-        server subprocess. The default is 1000. The limit actually used
-        by the code is the smaller of this setting and the result of
-        <literal>sysconf(_SC_OPEN_MAX)</literal>. Therefore, on systems
-        where <function>sysconf</> returns a reasonable limit, you don't
-        need to worry about this setting. But on some platforms
-        (notably, most BSD systems), <function>sysconf</> returns a
-        value that is much larger than the system can really support
-        when a large number of processes all try to open that many
-        files. If you find yourself seeing <quote>Too many open files</>
-        failures, try reducing this setting. This option can only be set
-        at server start or in the <filename>postgresql.conf</filename>
-        configuration file; if changed in the configuration file, it
-        only affects subsequently-started server subprocesses.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>MAX_FSM_RELATIONS</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Sets the maximum number of relations (tables) for which free
-        space will be tracked in the shared free-space map. The default
-        is 100. This option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>MAX_FSM_PAGES</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Sets the maximum number of disk pages for which free space will
-        be tracked in the shared free-space map. The default is 10000.
-        This option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>MAX_LOCKS_PER_TRANSACTION</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        The shared lock table is sized on the assumption that at most
-        <varname>max_locks_per_transaction</> *
-        <varname>max_connections</varname> distinct objects will need to
-        be locked at any one time. The default, 64, which 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 option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>PASSWORD_ENCRYPTION</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        When a password is specified in <command>CREATE USER</> or
-        <command>ALTER USER</> without writing either ENCRYPTED or
-        UNENCRYPTED, this flag determines whether the password is to be
-        encrypted. The default is on (encrypt the password).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>PORT</varname> (<type>integer</type>)</term>
-      <indexterm><primary>port</></>
-      <listitem>
-       <para>
-        The TCP port the server listens on; 5432 by default. This
-        option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SHARED_BUFFERS</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Sets the number of shared memory buffers used by the database
-        server. The default is 64. Each buffer is typically 8192 bytes.
-        This option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SILENT_MODE</varname> (<type>bool</type>)</term>
-      <listitem>
-       <para>
-        Runs postmaster silently. If this option is set, the postmaster
-        will automatically run in background and any controlling ttys
-        are disassociated, thus no messages are written to standard
-        output or standard error (same effect as postmaster's -S
-        option). Unless some logging system such as
-        <application>syslog</> is enabled, using this option is
-        discouraged since it makes it impossible to see error messages.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SORT_MEM</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-	Specifies the amount of memory to be used by internal sorts and
-	hashes before switching to temporary disk files. The value is
-	specified in kilobytes, and defaults to 512 kilobytes. Note that
-	for a complex query, several sorts and/or hashes might be
-	running in parallel, and each one will be allowed to use as much
-	memory as this value specifies before it starts to put data into
-	temporary files. Also, each running backend could be doing one
-	or more sorts simultaneously, so the total memory used could be
-	many times the value of <varname>SORT_MEM</varname>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>SQL_INHERITANCE</varname> (<type>bool</type>)</term>
-      <indexterm><primary>inheritance</></>
-      <listitem>
-       <para>
-        This controls the inheritance semantics, in particular whether
-        subtables are included by various commands by default. They were
-        not included in versions prior to 7.1. If you need the old
-        behavior you can set this variable to off, but in the long run
-        you are encouraged to change your applications to use the
-        <literal>ONLY</literal> keyword to exclude subtables. See the
-        SQL language reference and the <citetitle>User's
-        Guide</citetitle> for more information about inheritance.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <indexterm>
-       <primary>SSL</primary>
-      </indexterm>
-
-      <term><varname>SSL</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        Enables <acronym>SSL</> connections. Please read
-        <xref linkend="ssl-tcp"> before using this. The default
-        is off.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>TCPIP_SOCKET</varname> (<type>boolean</type>)</term>
-      <listitem>
-       <para>
-        If this is true, then the server will accept TCP/IP connections.
-        Otherwise only local Unix domain socket connections are
-        accepted. It is off by default. This option can only be set at
-        server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>TIMEZONE</varname> (<type>string</type>)</term>
-      <indexterm><primary>time zone</></>
-      <listitem>
-       <para>
-        Sets the time zone for displaying and interpreting timestamps.
-	The default is to use whatever the system environment
-	specifies as the timezone.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>TRANSFORM_NULL_EQUALS</varname> (<type>boolean</type>)</term>
-      <indexterm><primary>IS NULL</></>
-      <listitem>
-       <para>
-        When turned 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 behavior of
-        <literal><replaceable>expr</> = NULL</literal> is to always
-        return NULL (unknown). Therefore this option defaults to 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
-        NULLs, 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 NULL (using the correct 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, so this option is not on by default.
-       </para>
-
-       <para>
-        Note that this option only affects the literal <literal>=</>
-        operator, 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 the <citetitle>User's Guide</citetitle> for related
-        information.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>UNIX_SOCKET_DIRECTORY</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-	Specifies the directory of the Unix-domain socket on which the
-	<application>postmaster</application> 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><varname>UNIX_SOCKET_GROUP</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        Sets the group owner of the Unix domain socket.  (The owning
-        user of the socket is always the user that starts the
-        postmaster.)  In combination with the option
-        <option>UNIX_SOCKET_PERMISSIONS</option> this can be used as
-        an additional access control mechanism for this socket type.
-        By default this is the empty string, which uses the default
-        group for the current user.  This option can only be set at
-        server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>UNIX_SOCKET_PERMISSIONS</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Sets the access permissions of the Unix domain socket.  Unix
-        domain sockets use the usual Unix file system permission set.
-        The option value is expected to be an numeric mode
-        specification in the form 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 under
-        <option>UNIX_SOCKET_GROUP</option>) and <literal>0700</literal>
-        (only user). (Note that actually for a Unix socket, only write
-        permission matters and 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 option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>VACUUM_MEM</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-	Specifies the maximum amount of memory to be used by
-	<command>VACUUM</command> to keep track of to-be-reclaimed
-	tuples. The value is specified in kilobytes, and defaults to
-	8192 kilobytes. Larger settings may improve the speed of
-	vacuuming large tables that have many deleted tuples.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>VIRTUAL_HOST</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-	Specifies the TCP/IP host name or address on which the
-	<application>postmaster</application> is to listen for
-	connections from client applications. Defaults to listening on
-	all configured addresses (including <systemitem
-	class="systemname">localhost</>).
-       </para>
-      </listitem>
-     </varlistentry>
-
-    </variablelist>
-   </para>
-   </sect2>
-
-   <sect2 id="runtime-config-wal">
-    <title>WAL</title>
-
-   <para>
-    See also <xref linkend="wal-configuration"> for details on WAL
-    tuning.
-
-    <variablelist>
-     <varlistentry>
-      <term><varname>CHECKPOINT_SEGMENTS</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Maximum distance between automatic WAL checkpoints, in log file
-	segments (each segment is normally 16 megabytes).
-	This option can only be set at server start or in the
-	<filename>postgresql.conf</filename> file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>CHECKPOINT_TIMEOUT</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Maximum time between automatic WAL checkpoints, in seconds.
-	This option can only be set at server start or in the
-	<filename>postgresql.conf</filename> file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>COMMIT_DELAY</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Time delay between writing a commit record to the WAL buffer and
-        flushing the buffer out to disk, in microseconds. A nonzero
-        delay allows multiple transactions to be committed with only one
-        <function>fsync</function> system call, if system load is high
-        enough additional transactions may 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 COMMIT_SIBLINGS other transactions
-        are active at the instant that a backend has written its commit
-        record.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>COMMIT_SIBLINGS</varname> (<type>integer</type>)</term>
-      <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.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>WAL_BUFFERS</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Number of disk-page buffers in shared memory for WAL logging.
-	This option can only be set at server start.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>WAL_DEBUG</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        If non-zero, turn on WAL-related debugging output on standard
-        error.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>WAL_FILES</varname> (<type>integer</type>)</term>
-      <listitem>
-       <para>
-        Number of log files that are created in advance at checkpoint
-        time.  This option can only be set at server start or in the
-	<filename>postgresql.conf</filename> file.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><varname>WAL_SYNC_METHOD</varname> (<type>string</type>)</term>
-      <listitem>
-       <para>
-        Method used for forcing WAL updates out to disk.  Possible
-	values are
-	<literal>FSYNC</> (call <function>fsync()</> at each commit),
-	<literal>FDATASYNC</> (call <function>fdatasync()</> at each commit),
-	<literal>OPEN_SYNC</> (write WAL files with <function>open()</> option <symbol>O_SYNC</>), or
-	<literal>OPEN_DATASYNC</> (write WAL files with <function>open()</> option <symbol>O_DSYNC</>).
-	Not all of these choices are available on all platforms.
-        This option can only be set at server start or in the
-	<filename>postgresql.conf</filename> file.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-    </para>
-   </sect2>
-
-
-   <sect2 id="runtime-config-short">
-    <title>Short options</title>
-   <para>
-    For convenience there are also single letter option switches
-    available for many parameters. They are described in the following
-    table.
-
-    <table>
-     <title>Short option key</title>
-     <tgroup cols="3">
-      <colspec colnum="3" align="center">
-      <thead>
-       <row>
-        <entry>Short option</entry>
-        <entry>Equivalent</entry>
-        <entry>Remark</entry>
-       </row>
-      </thead>
-      <tbody>
-       <row>
-        <entry><option>-B <replaceable>x</replaceable></option></entry>
-        <entry><literal>shared_buffers = <replaceable>x</replaceable></></entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry><option>-d <replaceable>x</replaceable></option></entry>
-        <entry><literal>server_min_messages = <replaceable>DEBUGx</replaceable></></entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry><option>-F</option></entry>
-        <entry><literal>fsync = off</></entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry><option>-h <replaceable>x</replaceable></option></entry>
-        <entry><literal>virtual_host = <replaceable>x</replaceable></></entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry><option>-i</option></entry>
-        <entry><literal>tcpip_socket = on</></entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry><option>-k <replaceable>x</replaceable></option></entry>
-        <entry><literal>unix_socket_directory = <replaceable>x</replaceable></></entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry><option>-l</option></entry>
-        <entry><literal>ssl = on</></entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry><option>-N <replaceable>x</replaceable></option></entry>
-        <entry><literal>max_connections = <replaceable>x</replaceable></></entry>
-        <entry></entry>
-       </row>
-       <row>
-        <entry><option>-p <replaceable>x</replaceable></option></entry>
-        <entry><literal>port = <replaceable>x</replaceable></></entry>
-        <entry></entry>
-       </row>
-
-       <row>
-        <entry><option>-fi</option>, <option>-fh</option>, <option>-fm</option>, <option>-fn</option>, <option>-fs</option>, <option>-ft</option></entry>
-        <entry><literal>enable_indexscan=off</>, <literal>enable_hashjoin=off</>,
-        <literal>enable_mergejoin=off</>, <literal>enable_nestloop=off</>, <literal>enable_seqscan=off</>,
-        <literal>enable_tidscan=off</></entry>
-        <entry>*</entry>
-       </row>
-       <row>
-        <entry><option>-S <replaceable>x</replaceable></option></entry>
-        <entry><literal>sort_mem = <replaceable>x</replaceable></></entry>
-        <entry>*</entry>
-       </row>
-       <row>
-        <entry><option>-s</option></entry>
-        <entry><literal>show_query_stats = on</></entry>
-        <entry>*</entry>
-       </row>
-       <row>
-        <entry><option>-tpa</option>, <option>-tpl</option>, <option>-te</option></entry>
-        <entry><literal>show_parser_stats=on</>, <literal>show_planner_stats=on</>, <literal>show_executor_stats=on</></entry>
-        <entry>*</entry>
-       </row>
-      </tbody>
-     </tgroup>
-    </table>
-    For historical reasons, options marked <quote>*</quote> must be
-    passed to the individual backend process via the
-    <option>-o</option> postmaster option, for example,
-<screen>
-$ <userinput>postmaster -o '-S 1024 -s'</userinput>
-</screen>
-    or via <envar>PGOPTIONS</envar> from the client side, as explained
-    above.
-   </para>
-
-   </sect2>
- </sect1>
-
-
- <sect1 id="kernel-resources">
-  <title>Managing Kernel Resources</title>
-
-  <para>
-   A large <productname>PostgreSQL</> installation can quickly exhaust
-   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>
-
-   <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
-    relevant for <productname>PostgreSQL</>). Almost all modern
-    operating systems provide these features, but not all of them have
-    them turned on or sufficiently sized by default, especially systems
-    with BSD heritage. (For the <systemitem class="osname">QNX</> and
-    <systemitem class="osname">BeOS</> ports, <productname>PostgreSQL</>
-    provides its own replacement implementation of these facilities.)
-   </para>
-
-   <para>
-    The complete lack of these facilities is usually manifested by an
-    <errorname>Illegal system call</> error upon postmaster start. In
-    that case there's nothing left to do but to reconfigure your
-    kernel -- <productname>PostgreSQL</> won't work without them.
-   </para>
-
-   <para>
-    When <productname>PostgreSQL</> exceeds one of the various hard
-    <acronym>IPC</> limits, the postmaster will refuse to start and
-    should leave an instructive error message describing the problem
-    encountered and what to do about it. (See also <xref
-    linkend="postmaster-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.
-    Be warned that it is often necessary to reboot your machine, and
-    possibly even recompile the kernel, to change these settings.
-   </para>
-
-
-   <table id="sysvipc-parameters">
-    <title><systemitem class="osname">System V</> <acronym>IPC</> parameters</>
-
-    <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>250kB + 8.2kB * <varname>shared_buffers</> + 14.2kB * <varname>max_connections</> or infinity</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><literal>&gt;= ceil(max_connections / 16)</literal></>
-       </row>
-
-       <row>
-        <entry><varname>SEMMNS</></>
-        <entry>Maximum number of semaphores system-wide</>
-        <entry><literal>ceil(max_connections / 16) * 17</literal> + room for other applications</>
-       </row>
-
-       <row>
-        <entry><varname>SEMMSL</></>
-        <entry>Maximum number of semaphores per set</>
-        <entry>&gt;= 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>&gt;= 255  (The default is often 32767, don't change unless asked to.)</>
-       </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 <errorname>Invalid argument</>, it is
-    possible that this limit has been exceeded. The size of the required
-    shared memory segment varies both with the number of requested
-    buffers (<option>-B</> option) and the number of allowed connections
-    (<option>-N</> option), although the former is the most significant.
-    (You can, as a temporary solution, lower these settings to eliminate
-    the failure.) As a rough approximation, you can estimate the
-    required segment size by multiplying the number of buffers and the
-    block size (8 kB by default) plus ample overhead (at least half a
-    megabyte). Any error message you might get will contain the size of
-    the failed allocation request.
-   </para>
-
-   <para>
-    Less likely to cause problems is the minimum size for shared
-    memory segments (<varname>SHMMIN</>), which should be at most
-    approximately 256 kB for <productname>PostgreSQL</> (it is
-    usually just 1). The maximum number of segments system-wide
-    (<varname>SHMMNI</>) or per-process (<varname>SHMSEG</>) should
-    not cause a problem unless your system has them set to zero. Some
-    systems also have a limit on the total amount of shared memory in
-    the system; see the platform-specific instructions below.
-   </para>
-
-   <para>
-    <productname>PostgreSQL</> uses one semaphore per allowed connection
-    (<option>-N</> option), 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 the connection setting plus one extra for each 16
-    allowed connections (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 / 16)</>. Lowering the number
-    of allowed connections is a temporary workaround for failures,
-    which are usually confusingly worded <quote><errorname>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
-    <productname>PostgreSQL</>.
-   </para>
-
-   <para>
-    Various other settings related to <quote>semaphore undo</>, such as
-    <varname>SEMMNU</> and <varname>SEMUME</>, are not of concern
-    for <productname>PostgreSQL</>.
-   </para>
-
-
-   <para>
-    <variablelist>
-
-     <varlistentry>
-      <term><systemitem class="osname">BSD/OS</></term>
-      <indexterm><primary>BSD/OS</></>
-      <listitem>
-       <formalpara>
-        <title>Shared Memory</>
-        <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 number of shared buffers supported by the
-         postmaster, add the following to your kernel configuration
-         file. A <varname>SHMALL</> value of 1024 represents 4MB of
-         shared memory. The following increases the maximum shared
-         memory area to 32 MB:
-<programlisting>
-options "SHMALL=8192"
-options "SHMMAX=\(SHMALL*PAGE_SIZE\)"
-</programlisting>
-        </para>
-       </formalpara>
-
-       <para>
-        For those running 4.1 or later, just make the above changes,
-        recompile the kernel, and reboot. For those running earlier
-        releases, use <application>bpatch</> to find the
-        <varname>sysptsize</> value in the current kernel. This is
-        computed dynamically at boot time.
-<screen>
-$ <userinput>bpatch -r sysptsize</>
-<computeroutput>0x9 = 9</>
-</screen>
-        Next, add <varname>SYSPTSIZE</> as a hard-coded value in the
-        kernel configuration file. Increase the value you found using
-        <application>bpatch</>. Add 1 for every additional 4 MB of
-        shared memory you desire.
-<programlisting>
-options "SYSPTSIZE=16"
-</programlisting>
-        <varname>sysptsize</> cannot be changed by <command>sysctl</command>.
-       </para>
-
-       <formalpara>
-        <title>Semaphores</>
-        <para>
-         You may need to increase the number of semaphores. By default,
-         <productname>PostgreSQL</> allocates 34 semaphores, which is
-         over half the default system total of 60.
-        </para>
-       </formalpara>
-
-        <para>
-        Set the values you want in your kernel configuration file, e.g.:
-<programlisting>
-options "SEMMNI=40"
-options "SEMMNS=240"
-options "SEMUME=40"
-options "SEMMNU=120"
-</programlisting>
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">FreeBSD</></term>
-      <term><systemitem class="osname">NetBSD</></term>
-      <term><systemitem class="osname">OpenBSD</></term>
-      <indexterm><primary>FreeBSD</></>
-      <indexterm><primary>NetBSD</></>
-      <indexterm><primary>OpenBSD</></>
-      <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:
-<programlisting>
-options         SYSVSHM
-options         SHMMAXPGS=4096
-options         SHMSEG=256
-
-options         SYSVSEM
-options         SEMMNI=256
-options         SEMMNS=512
-options         SEMMNU=256
-options         SEMMAP=256
-</programlisting>
-        (On <systemitem class="osname">NetBSD</> and <systemitem
-        class="osname">OpenBSD</> the key word is actually
-        <literal>option</literal> singular.)
-       </para>
-       <para>
-        You may also want to use the <application>sysctl</> setting to
-        lock shared memory into RAM and prevent it from being paged out
-        to swap.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">HP-UX</></term>
-      <indexterm><primary>HP-UX</></>
-      <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</></>. Hit
-        <guibutton>Create A New Kernel</> when you're done.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">Linux</></term>
-      <indexterm><primary>Linux</></>
-      <listitem>
-       <para>
-        The default shared memory limit (both
-        <varname>SHMMAX</varname> and <varname>SHMALL</varname>) is 32
-        MB in 2.2 kernels, but it can be changed in the
-        <filename>proc</filename> file system (without reboot).  For
-        example, to allow 128 MB:
-<screen>
-<prompt>$</prompt> <userinput>echo 134217728 >/proc/sys/kernel/shmall</userinput>
-<prompt>$</prompt> <userinput>echo 134217728 >/proc/sys/kernel/shmmax</userinput>
-</screen>
-        You could put these commands into a script run at boot-time.
-       </para>
-
-       <para>
-        Alternatively, you can use
-        <citerefentry><refentrytitle>sysctl</refentrytitle>
-        <manvolnum>8</manvolnum></citerefentry>, if available, to
-        control these parameters.  Look for a file called
-        <filename>/etc/sysctl.conf</filename> and add lines like the
-        following to it:
-<programlisting>
-kernel.shmall = 134217728
-kernel.shmmax = 134217728
-</programlisting>
-        This file is usually processed at boot time, but
-        <application>sysctl</application> can also be called
-        explicitly later.
-       </para>
-
-       <para>
-        Other parameters are sufficiently sized for any application. If
-        you want to see for yourself look in
-        <filename>/usr/src/linux/include/asm-<replaceable>xxx</>/shmpara
-        m.h</> and <filename>/usr/src/linux/include/linux/sem.h</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">SCO OpenServer</></term>
-      <indexterm><primary>SCO OpenServer</></>
-      <listitem>
-       <para>
-        In the default configuration, only 512 kB of shared memory per
-        segment is allowed, which is about enough for <option>-B 24 -N
-        12</>. To increase the setting, first change directory to
-        <filename>/etc/conf/cf.d</>. To display the current value of
-        <varname>SHMMAX</>, in bytes, 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</></term>
-      <indexterm><primary>Solaris</></>
-      <listitem>
-       <para>
-        At least in version 2.6, the default maximum size of a shared
-        memory segments is too low for <productname>PostgreSQL</>. The
-        relevant settings can be changed in <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.
-       </para>
-
-       <para>
-        See also <ulink
-        url="http://www.sunworld.com/swol-09-1997/swol-09-insidesolaris.html"></>
-        for information on shared memory under
-        <productname>Solaris</>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-
-     <varlistentry>
-      <term><systemitem class="osname">UnixWare</></term>
-      <indexterm><primary>UnixWare</></>
-      <listitem>
-       <para>
-        On <productname>UnixWare</> 7, the maximum size for shared
-        memory segments is 512 kB in the default configuration. This
-        is enough for about <option>-B 24 -N 12</>. 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, in bytes. 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>
-
-   </para>
-  </sect2>
-
-
-  <sect2>
-   <title>Resource Limits</title>
-
-   <para>
-    Unix-like operating systems enforce various kinds of resource limits
-    that might interfere with the operation of your
-    <productname>PostgreSQL</productname> server. Of particular
-    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
-    <citerefentry><refentrytitle>login.conf</refentrytitle>
-    <manvolnum>5</manvolnum></citerefentry> 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>
-    The <productname>PostgreSQL</productname> server uses one process
-    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 may 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 don't want to alter the system-wide
-    limit, you can set <productname>PostgreSQL</productname>'s
-    <varname>max_files_per_process</varname> configuration parameter to
-    limit the consumption of open files.
-   </para>
-  </sect2>
-
- </sect1>
-
-
- <sect1 id="postmaster-shutdown">
-  <title>Shutting down the server</title>
-
-  <para>
-   There are several ways to shut down the database server. You control
-   the type of shutdown by sending different signals to the server
-   process.
-   <variablelist>
-    <varlistentry>
-     <term><systemitem>SIGTERM</systemitem></term>
-     <listitem>
-      <para>
-       After receiving <systemitem>SIGTERM</systemitem>, the postmaster
-       disallows new connections, but lets existing backends end their
-       work normally. It shuts down only after all of the backends
-       terminate normally. This is <firstterm>Smart
-       Shutdown</firstterm>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><systemitem>SIGINT</systemitem></term>
-     <listitem>
-      <para>
-       The postmaster disallows new connections and sends all existing
-       backends <systemitem>SIGTERM</systemitem>, which will cause them
-       to abort their current transactions and exit promptly. It then
-       waits for the backends to exit and finally shuts down. This is
-       <firstterm>Fast Shutdown</firstterm>.
-      </para>
-     </listitem>
-    </varlistentry>
-
-    <varlistentry>
-     <term><systemitem>SIGQUIT</systemitem></term>
-     <listitem>
-      <para> This is <firstterm>Immediate Shutdown</firstterm>, which
-      will cause the postmaster to send a
-      <systemitem>SIGQUIT</systemitem> to all backends and exit
-      immediately (without properly shutting itself down). The backends
-      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>
-
-   <important>
-    <para>
-     It is best not to use <systemitem>SIGKILL</systemitem> to shut down
-     the postmaster. This will prevent the postmaster from releasing
-     shared memory and semaphores, which may then have to be done by
-     manually.
-    </para>
-   </important>
-
-   The <acronym>PID</> of the postmaster process can be found using the
-   <application>ps</application> program, or from the file
-   <filename>postmaster.pid</filename> in the data directory. So for
-   example, to do a fast shutdown:
-<screen>
-$ <userinput>kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`</userinput>
-</screen>
-  </para>
-  <para>
-   The program <application>pg_ctl</application> is a shell script
-   that provides a more convenient interface for shutting down the
-   postmaster.
-  </para>
- </sect1>
-
- <sect1 id="ssl-tcp">
-  <title>Secure TCP/IP Connections with SSL</title>
-
-  <indexterm zone="ssl-tcp">
-   <primary>SSL</primary>
-  </indexterm>
-
-  <para>
-   <productname>PostgreSQL</> has native support for using
-   <acronym>SSL</> connections to encrypt client/server communications
-   for increased security. This requires
-   <productname>OpenSSL</productname> be installed on both client and
-   server systems and support enabled at build time (see <xref
-   linkend="installation">).
-  </para>
-
-  <para>
-   With SSL support compiled in, the <productname>PostgreSQL</> server
-   can be started with the argument <option>-l</> (ell) to enable
-   SSL connections. When starting in SSL mode, the server will look
-   for the files <filename>server.key</> and <filename>server.crt</> in
-   the data directory.  These files should contain the server private key
-   and certificate respectively. These files must be set up correctly
-   before an SSL-enabled server can start. 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>
-   The server will listen for both standard and SSL connections on the
-   same TCP/IP port, and will negotiate with any connecting client on
-   whether to use SSL. See <xref linkend="client-authentication"> about
-   how to force the server to only use of SSL for certain connections.
-  </para>
-
-  <para>
-   For details on how to create your server private key and certificate,
-   refer to the <productname>OpenSSL</> documentation. A simple
-   self-signed certificate can be used to get started for testing, but a
-   certificate signed by a <acronym>CA</> (either one of the global
-   <acronym>CAs</> or a local one) should be used in production so the
-   client can verify the server's identity. To create a quick
-   self-signed certificate, use the following
-   <productname>OpenSSL</productname> command:
-<programlisting>
-openssl req -new -text -out cert.req
-</programlisting>
-   Fill out the information that <command>openssl</> asks for. Make sure
-   that you enter the local host name as Common Name; the challenge
-   password can be left blank. The script will generate a key that is
-   passphrase protected; it will not accept a pass phrase 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 cert.pem
-</programlisting>
-   Enter the old passphrase to unlock the existing key. Now do
-<programlisting>
-openssl req -x509 -in cert.req -text -key cert.pem -out cert.cert
-cp cert.pem <replaceable>$PGDATA</replaceable>/server.key
-cp cert.cert <replaceable>$PGDATA</replaceable>/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.
-  </para>
- </sect1>
-
- <sect1 id="ssh-tunnels">
-  <title>Secure TCP/IP Connections with <application>SSH</application> tunnels</title>
-
-  <indexterm zone="ssh-tunnels">
-   <primary>ssh</primary>
-  </indexterm>
-
-  <note>
-   <title>Acknowledgement</title>
-   <para>
-    Idea taken from an email by Gene Selkov, Jr.
-    (<email>selkovjr@mcs.anl.gov</>) written on 1999-09-08 in response
-    to a question from Eric Marsden.
-   </para>
-  </note>
-
-  <para>
-   One can use <productname>ssh</productname> to encrypt the network
-   connection between clients and a
-   <productname>PostgreSQL</productname> server. Done properly, this
-   should lead to an adequately secure network connection.
-  </para>
-
-  <para>
-   First make sure that an <application>ssh</application> server is
-   running properly on the same machine as
-   <productname>PostgreSQL</productname> and that you can log in using
-   <command>ssh</command> as some user. Then you can establish a secure
-   tunnel with a command like this from the client machine:
-<programlisting>
-$ <userinput>ssh -L 3333:foo.com:5432 joe@foo.com</userinput>
-</programlisting>
-   The first number in the <option>-L</option> argument, 3333, is the
-   port number of your end of the tunnel; it can be chosen freely. The
-   second number, 5432, is the remote end of the tunnel -- the port
-   number your server is using. The name or the address in between
-   the port numbers is the host with the database server you are going
-   to connect to. In order to connect to the database server using
-   this tunnel, you connect to port 3333 on the local machine:
-<programlisting>
-psql -h localhost -p 3333 template1
-</programlisting>
-   To the database server it will then look as though you are really
-   user <literal>joe@foo.com</literal> and it will use whatever
-   authentication procedure was set up for this user. In order for the
-   tunnel setup to succeed you must be allowed to connect via
-   <command>ssh</command> as <systemitem>joe@foo.com</systemitem>, just
-   as if you had attempted to use <command>ssh</command> to set up a
-   terminal session.
-  </para>
-
-  <tip>
-   <para>
-    Several other products exist that can provide secure tunnels using
-    a procedure similar in concept to the one just described.
-   </para>
-  </tip>
-
- </sect1>
-
-</Chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/sources.sgml b/doc/src/sgml/sources.sgml
deleted file mode 100644
index c07264e5dba..00000000000
--- a/doc/src/sgml/sources.sgml
+++ /dev/null
@@ -1,84 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/sources.sgml,v 2.6 2002/01/20 22:19:56 petere Exp $
--->
-
- <chapter id="source">
-  <title>PostgreSQL Source Code</title>
-
-  <sect1 id="source-format">
-   <title>Formatting</title>
-
-   <para>
-    Source code formatting uses a 4 column tab spacing, currently with 
-    tabs preserved (i.e. tabs are not expanded to spaces).
-   </para>
-
-   <para>
-    For Emacs, add the following (or something similar)
-    to your <filename>~/.emacs</filename> 
-    initialization file:
-
-<programlisting>
-;; check for files with a path containing "postgres" or "pgsql"
-(setq auto-mode-alist
-  (cons '("\\(postgres\\|pgsql\\).*\\.[ch]\\'" . pgsql-c-mode)
-        auto-mode-alist))
-(setq auto-mode-alist
-  (cons '("\\(postgres\\|pgsql\\).*\\.cc\\'" . pgsql-c-mode)
-        auto-mode-alist))
-
-(defun pgsql-c-mode ()
-  ;; sets up formatting for PostgreSQL C code
-  (interactive)
-  (c-mode)
-  (setq-default tab-width 4)
-  (c-set-style "bsd")             ; set c-basic-offset to 4, plus other stuff
-  (c-set-offset 'case-label '+)   ; tweak case indent to match PG custom
-  (setq indent-tabs-mode t))      ; make sure we keep tabs when indenting
-</programlisting>
-   </para>
-
-   <para>
-    For <application>vi</application>, your
-    <filename>~/.vimrc</filename> or equivalent file should contain
-    the following:
-
-<programlisting>
-set tabstop=4
-</programlisting>
-
-    or equivalently from within vi, try
-
-<programlisting>
-:set ts=4
-</programlisting>
-   </para>
-
-   <para>
-    The text browsing tools <application>more</application> and
-    <application>less</application> can be invoked as
-
-<programlisting>
-more -x4
-less -x4
-</programlisting>
-   </para>
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/spi.sgml b/doc/src/sgml/spi.sgml
deleted file mode 100644
index ca6d62e1ae1..00000000000
--- a/doc/src/sgml/spi.sgml
+++ /dev/null
@@ -1,3921 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/spi.sgml,v 1.22 2002/03/22 19:20:30 petere Exp $
--->
-
-<Chapter id="spi">
-<DocInfo>
-<AuthorGroup>
-<Author>
-<FirstName>Vadim</FirstName>
-<Surname>Mikheev</Surname>
-</Author>
-</AuthorGroup>
-<Date>Transcribed 1998-01-16</Date>
-</DocInfo>
-
-<Title>Server Programming Interface</Title>
-
-<Para>
-The <FirstTerm>Server Programming Interface</FirstTerm> 
-(<Acronym>SPI</Acronym>) gives users the
-ability to run <Acronym>SQL</Acronym> queries inside user-defined 
-<Acronym>C</Acronym> functions.
-</Para>
-
-<note>
-<para>
-The available Procedural Languages (<Acronym>PL</Acronym>) give an alternate
-means to build functions that can execute queries.
-</para>
-</note>
-
-<Para>
-In fact, <Acronym>SPI</Acronym> is just a set of native interface functions
-to simplify access to the Parser, Planner, Optimizer and Executor. 
-<Acronym>SPI</Acronym> also does some memory management.
-</Para>
-
-<Para>
-To avoid misunderstanding we'll use <FirstTerm>function</FirstTerm> 
-to mean <Acronym>SPI</Acronym> interface functions and 
-<FirstTerm>procedure</FirstTerm> for user-defined C-functions 
-using <Acronym>SPI</Acronym>.
-</Para>
-
-<Para>
-Procedures which use <Acronym>SPI</Acronym> are called by the
-Executor.  The <Acronym>SPI</Acronym> calls recursively invoke the
-Executor in turn to run queries.  When the Executor is invoked
-recursively, it may itself call procedures which may make
-<Acronym>SPI</Acronym> calls.
-</Para>
-
-<Para>
-Note that if during execution of a query from a procedure the transaction is
-aborted, then control will not be returned to your procedure. Rather, all work
-will be rolled back and the server will wait for the next command from the
-client.  This will probably be changed in future versions.
-</Para>
-
-<Para>
-A related restriction is the inability to execute BEGIN, END and ABORT
-(transaction control statements).  This will also be
-changed in the future.
-</Para>
-
-<Para>
-If successful, <Acronym>SPI</Acronym> functions return a non-negative result (either via
-a returned integer value or in SPI_result global variable, as described below).
-On error, a negative or NULL result will be returned.
-</Para>
-
-<Sect1 id="spi-interface">
-<Title>Interface Functions</Title>
-
-<REFENTRY ID="SPI-SPICONNECT">
-<REFMETA>
-<REFENTRYTITLE>SPI_connect</REFENTRYTITLE>
-<REFMISCINFO>SPI - Connection Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_connect
-</REFNAME>
-<REFPURPOSE>
-   Connects your procedure to the SPI manager.
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICONNECT-1"><PRIMARY>SPI</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICONNECT-2"><PRIMARY>SPI_connect</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-int SPI_connect(void)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICONNECT-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICONNECT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>int
-</TERM>
-<LISTITEM>
-<PARA>
-Return status
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM><ReturnValue>SPI_OK_CONNECT</ReturnValue>
-</TERM>
-<LISTITEM>
-<PARA>
-   if connected
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM><ReturnValue>SPI_ERROR_CONNECT</ReturnValue>
-</TERM>
-<LISTITEM>
-<PARA>
-   if not connected
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICONNECT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_connect</FUNCTION> opens a connection from a procedure
-invocation to the SPI manager.
-   You must call this function if you will need to execute queries. Some
-   utility SPI functions may be called from un-connected procedures.
-</PARA>
-<PARA>
-   If your procedure is already connected,
-   <Function>SPI_connect</Function> will return an
-   <ReturnValue>SPI_ERROR_CONNECT</ReturnValue> error.  Note that this
-   may happen if a procedure which has called
-   <Function>SPI_connect</Function> directly calls another procedure
-   which itself calls <Function>SPI_connect</Function>.  While
-   recursive calls to the <Acronym>SPI</Acronym> manager are permitted
-   when an <Acronym>SPI</Acronym> query invokes another function which
-   uses <Acronym>SPI</Acronym>, directly nested calls to
-   <Function>SPI_connect</Function> and
-   <Function>SPI_finish</Function> are forbidden.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPICONNECT-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-<!--
-XXX thomas 1997-12-24
--->
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPICONNECT-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_connect</FUNCTION> performs the following:
-  Initializes the SPI internal
-   structures for query execution and memory management.
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICONNECT-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIFINISH">
-<REFMETA>
-<REFENTRYTITLE>SPI_finish</REFENTRYTITLE>
-<REFMISCINFO>SPI - Connection Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_finish
-</REFNAME>
-<REFPURPOSE>
-   Disconnects your procedure from the SPI manager.
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIFINISH-1"><PRIMARY>SPI</PRIMARY><SECONDARY>disconnecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIFINISH-2"><PRIMARY>SPI_finish</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_finish(void)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIFINISH-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIFINISH-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>int
-</TERM>
-<LISTITEM>
-<PARA>
-<SimpleList>
-<Member>
-<ReturnValue>SPI_OK_FINISH</ReturnValue>
-   if properly disconnected
-</Member>
-<Member>
-<ReturnValue>SPI_ERROR_UNCONNECTED</ReturnValue>
-   if called from an un-connected procedure
-</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIFINISH-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<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.
-</para>
-<PARA>
-   You may get the error return <ReturnValue>SPI_ERROR_UNCONNECTED</ReturnValue> if <Function>SPI_finish</Function> is
-   called without having a current valid connection.
- There is no fundamental problem
-   with this; it means that nothing was done by the SPI manager.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIFINISH-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-   <Function>SPI_finish</Function> <Emphasis>must</Emphasis> be called as a final step by a connected procedure,
- or you may get
-   unpredictable results!  However, you do not need to worry about making
-this happen if the transaction is aborted via elog(ERROR).  In that case
-SPI will clean itself up.
-
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIFINISH-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_finish</FUNCTION> performs the following:
-   Disconnects your procedure from the SPI manager and frees all memory
-   allocations made by your procedure via <Function>palloc</Function> since
- the <Function>SPI_connect</Function>. 
-   These allocations can't be used any more! See Memory management.
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIFINISH-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIEXEC">
-<REFMETA>
-<REFENTRYTITLE>SPI_exec</REFENTRYTITLE>
-<REFMISCINFO>SPI - Connection Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_exec
-</REFNAME>
-<REFPURPOSE>
-   Creates an execution plan (parser+planner+optimizer) and executes a query.
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIEXEC-1"><PRIMARY>SPI</PRIMARY><SECONDARY>executing</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIEXEC-2"><PRIMARY>SPI_exec</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_exec(<REPLACEABLE CLASS="PARAMETER">query</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIEXEC-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-char *<REPLACEABLE CLASS="PARAMETER">query</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-String containing query plan
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Maximum number of tuples to return
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIEXEC-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>int
-</TERM>
-<LISTITEM>
-<PARA>
-<SimpleList>
-<Member>
-   <ReturnValue>SPI_ERROR_UNCONNECTED</ReturnValue> if called from an un-connected procedure
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_ARGUMENT</ReturnValue> if query is NULL or <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE> < 0.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_UNCONNECTED</ReturnValue> if procedure is unconnected.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_COPY</ReturnValue> if COPY TO/FROM stdin.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_CURSOR</ReturnValue> if DECLARE/CLOSE CURSOR, FETCH.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_TRANSACTION</ReturnValue> if BEGIN/ABORT/END.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_OPUNKNOWN</ReturnValue> if type of query is unknown (this shouldn't occur).
-</Member>
-</SimpleList>
-</para>
-<Para>
-   If execution of your query was successful then one of the following
-   (non-negative) values will be returned:
-<SimpleList>
-<Member>
-   <ReturnValue>SPI_OK_UTILITY</ReturnValue> if some utility (e.g. CREATE TABLE ...) was executed
-</Member>
-<Member>
-   <ReturnValue>SPI_OK_SELECT</ReturnValue> if SELECT (but not SELECT ... INTO!) was executed
-</Member>
-<Member>
-   <ReturnValue>SPI_OK_SELINTO</ReturnValue> if SELECT ... INTO was executed
-</Member>
-<Member>
-   <ReturnValue>SPI_OK_INSERT</ReturnValue> if INSERT (or INSERT ... SELECT) was executed
-</Member>
-<Member>
-   <ReturnValue>SPI_OK_DELETE</ReturnValue> if DELETE was executed
-</Member>
-<Member>
-   <ReturnValue>SPI_OK_UPDATE</ReturnValue> if UPDATE was executed
-</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIEXEC-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_exec</FUNCTION> creates an execution plan (parser+planner+optimizer)
- and executes the query for <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE> tuples.
-
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIEXEC-2">
-<TITLE>Usage
-</TITLE>
-<PARA>
-  This should only be called from a connected procedure.
-   If <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE> is zero then it executes the query for all tuples returned by the
-   query scan. Using <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE> > 0 you may restrict the number of tuples for
-   which the query will be executed (much like a LIMIT clause). For example,
-
-<ProgramListing>
-SPI_exec ("INSERT INTO tab SELECT * FROM tab", 5);
-</ProgramListing>
-
-will allow at most 5 tuples to be inserted into table.
-
-   If execution of your query was successful then a non-negative value will be returned.
-
-<Note>
-<Para>
-You may pass multiple queries in one string or query string may be
-   re-written by RULEs. <Function>SPI_exec</Function> returns the result for the last query
-   executed.
-</Para>
-</Note>
-</para>
-<Para>
-   The actual number of tuples for which the (last) query was executed is
-   returned in the global variable SPI_processed (if not <ReturnValue>SPI_OK_UTILITY</ReturnValue>).
-
-   If <ReturnValue>SPI_OK_SELECT</ReturnValue> is returned and SPI_processed &gt; 0 then you may use global
-   pointer SPITupleTable *SPI_tuptable to access the result tuples.
-</Para>
-
-<Para>
-   <Function>SPI_exec</Function> may return one of the following (negative) values:
-<SimpleList>
-<Member>
-   <ReturnValue>SPI_ERROR_ARGUMENT</ReturnValue> if query is NULL or <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE> < 0.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_UNCONNECTED</ReturnValue> if procedure is unconnected.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_COPY</ReturnValue> if COPY TO/FROM stdin.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_CURSOR</ReturnValue> if DECLARE/CLOSE CURSOR, FETCH.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_TRANSACTION</ReturnValue> if BEGIN/ABORT/END.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_OPUNKNOWN</ReturnValue> if type of query is unknown (this shouldn't occur).
-</Member>
-</SimpleList>
-
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIEXEC-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
--->
-<REFSECT1 ID="R1-SPI-SPIEXEC-4">
-<TITLE>Structures
-</TITLE>
-<Para>
-   If <ReturnValue>SPI_OK_SELECT</ReturnValue> is returned and SPI_processed &gt; 0 then you may use the global
-   pointer SPITupleTable *SPI_tuptable to access the selected tuples.
-</Para>
-
-<Para>
-   Structure SPITupleTable is defined in spi.h:
-<ProgramListing>
-   typedef struct
-   {
-       MemoryContext tuptabcxt;    /* memory context of result table */
-       uint32      alloced;        /* # of alloced vals */
-       uint32      free;           /* # of free vals */
-       TupleDesc   tupdesc;        /* tuple descriptor */
-       HeapTuple  *vals;           /* tuples */
-   } SPITupleTable;
-</ProgramListing>
-</Para>
-
-<Para>
-   <structfield>vals</> is an array of pointers to tuples (the number of useful entries
-   is given by SPI_processed). <structfield>tupdesc</> is
-   a tuple descriptor which you may pass to SPI functions dealing with
-   tuples.  <structfield>tuptabcxt</>, <structfield>alloced</>, and <structfield>free</> are internal fields not intended
-   for use by SPI callers.
-</Para>
-
-<note>
-<Para>
-   Functions <Function>SPI_exec</Function>, <Function>SPI_execp</Function> and
-   <Function>SPI_prepare</Function> change both SPI_processed and SPI_tuptable
-   (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 of one <Function>SPI_exec</Function> or
-   <Function>SPI_execp</Function> across later calls.
-</Para>
-</note>
-
-<Para>
-   <Function>SPI_finish</Function> frees all SPITupleTables 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>
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIPREPARE">
-<REFMETA>
-<REFENTRYTITLE>SPI_prepare</REFENTRYTITLE>
-<REFMISCINFO>SPI - Plan Preparation</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_prepare
-</REFNAME>
-<REFPURPOSE>
-   Prepares a plan for a query, without executing it yet
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIPREPARE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIPREPARE-2"><PRIMARY>SPI_prepare</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_prepare(<REPLACEABLE CLASS="PARAMETER">query</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">nargs</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">argtypes</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIPREPARE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-<REPLACEABLE CLASS="PARAMETER">query</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Query string
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<REPLACEABLE CLASS="PARAMETER">nargs</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Number of input parameters ($1 ... $nargs - as in SQL-functions)
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-<REPLACEABLE CLASS="PARAMETER">argtypes</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Pointer to array of type <Acronym>OID</Acronym>s for input parameter types
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIPREPARE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>void *
-</TERM>
-<LISTITEM>
-<PARA>
-Pointer to an execution plan (parser+planner+optimizer)
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIPREPARE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_prepare</FUNCTION> 
-   creates and returns an execution plan (parser+planner+optimizer) but doesn't
-   execute the query. Should only be called from a connected procedure.
-
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIPREPARE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-   When the same or similar query is to be executed repeatedly, it may
-   be advantageous to perform query planning only once.
-   <FUNCTION>SPI_prepare</FUNCTION> converts a query string into an execution
-   plan that can be passed repeatedly to <FUNCTION>SPI_execp</FUNCTION>.
-</para>
-<PARA>
-   A prepared query can be generalized by writing parameters ($1, $2, etc)
-   in place of what would be constants in a normal query.  The values of
-   the parameters are then specified when <FUNCTION>SPI_execp</FUNCTION>
-   is called.  This allows the prepared query to be used over a wider
-   range of situations than would be possible without parameters.
-</para>
-<note>
-<PARA>
-   However, there is a disadvantage: since the planner does not know the
-   values that will be supplied for the parameters, it may make worse
-   query planning choices than it would make for a simple query with
-   all constants visible.
-</para>
-</note>
-<PARA>
-   If the query uses parameters, their number and data types must be
-   specified in the call to <FUNCTION>SPI_prepare</FUNCTION>.
-</para>
-<Para>
-The plan returned by <Function>SPI_prepare</Function> may be used only in current
-   invocation of the procedure since <Function>SPI_finish</Function> frees memory allocated for a plan. 
-   But see <Function>SPI_saveplan</Function> to save a plan for longer.
-</para>
-<Para>
-   If successful, a non-null pointer will be returned. Otherwise, you'll get
-   a NULL plan.  In both cases SPI_result will be set like the value returned
-   by SPI_exec, except that it is set to 
-   <ReturnValue>SPI_ERROR_ARGUMENT</ReturnValue> if query is NULL or nargs < 0 or nargs > 0 && argtypes
-   is NULL.
-
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIPREPARE-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_prepare</FUNCTION> performs the following:
-TBD
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPIPREPARE-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIEXECP">
-<REFMETA>
-<REFENTRYTITLE>SPI_execp</REFENTRYTITLE>
-<REFMISCINFO>SPI - Plan Execution</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_execp
-</REFNAME>
-<REFPURPOSE>
-Executes a plan from <Function>SPI_prepare</Function>
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIEXECP-1"><PRIMARY>SPI</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIEXECP-2"><PRIMARY>SPI_execp</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_execp(<REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">values</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">nulls</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIEXECP-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-void *<REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Execution plan
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-Datum *<REPLACEABLE CLASS="PARAMETER">values</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Actual parameter values
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-char *<REPLACEABLE CLASS="PARAMETER">nulls</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Array describing which parameters are NULLs
-<SimpleList>
-<Member><literal>n</literal> indicates NULL (values[] entry ignored)</Member>
-<Member>space indicates not NULL (values[] entry is valid)</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Number of tuples for which plan is to be executed
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIEXECP-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>int
-</TERM>
-<LISTITEM>
-<PARA>
-   Returns the same value as <Function>SPI_exec</Function> as well as
-<SimpleList>
-<Member>
- <ReturnValue>SPI_ERROR_ARGUMENT</ReturnValue>
- if <REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>
- is NULL or <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE> &lt; 0
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_PARAM</ReturnValue>
- if <REPLACEABLE CLASS="PARAMETER">values</REPLACEABLE>
- is NULL
- and <REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>
- was prepared with some parameters.
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>SPI_tuptable
-</TERM>
-<LISTITEM>
-<PARA>
-initialized as in
-   <Function>SPI_exec</Function> if successful
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>SPI_processed
-</TERM>
-<LISTITEM>
-<PARA>
-initialized as in
-   <Function>SPI_exec</Function> if successful
-</para>
-</listitem>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIEXECP-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_execp</FUNCTION> 
-   executes a plan prepared by <Function>SPI_prepare</Function>.
-   <REPLACEABLE CLASS="PARAMETER">tcount</REPLACEABLE> has the same
-   interpretation as in <Function>SPI_exec</Function>.
-</para>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIEXECP-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-   If <REPLACEABLE CLASS="PARAMETER">nulls</REPLACEABLE>
-is NULL then 
-   <Function>SPI_execp</Function> 
-assumes that all parameters (if any) are NOT NULL.
-
-<Note>
-<Para>
-   If one of the objects (a relation, function, etc.) referenced by the prepared
-   plan is dropped during your session (by your backend or another process) then the
-   results of <Function>SPI_execp</Function> for this plan will be unpredictable.
-</Para>
-</Note>
-
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIEXECP-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_execp</FUNCTION> performs the following:
-TBD
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPIEXECP-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPICURSOR-OPEN">
-<REFMETA>
-<REFENTRYTITLE>SPI_cursor_open</REFENTRYTITLE>
-<REFMISCINFO>SPI - Cursor Support</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_cursor_open
-</REFNAME>
-<REFPURPOSE>
-Sets up a cursor using a plan created with <Function>SPI_prepare</Function>
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICURSOR-OPEN-1"><PRIMARY>SPI</PRIMARY><SECONDARY>cursors</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICURSOR-OPEN-2"><PRIMARY>SPI_cursor_open</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2001-11-14</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_cursor_open(<REPLACEABLE CLASS="PARAMETER">name</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">values</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">nulls</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-OPEN-1">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-char *<REPLACEABLE CLASS="PARAMETER">name</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Name for portal, or NULL to let the system select a name
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-void *<REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Execution plan
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-Datum *<REPLACEABLE CLASS="PARAMETER">values</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Actual parameter values
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-char *<REPLACEABLE CLASS="PARAMETER">nulls</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Array describing which parameters are NULLs
-<SimpleList>
-<Member><literal>n</literal> indicates NULL (values[] entry ignored)</Member>
-<Member>space indicates not NULL (values[] entry is valid)</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-OPEN-2">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>Portal
-</TERM>
-<LISTITEM>
-<PARA>
-   Pointer to Portal containing cursor, or NULL on error
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICURSOR-OPEN-1">
-<REFSECT1INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT1INFO>
-<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>.
-</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 rowset result.
-</para>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPICURSOR-OPEN-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-   If <REPLACEABLE CLASS="PARAMETER">nulls</REPLACEABLE>
-is NULL then 
-   <Function>SPI_cursor_open</Function> 
-assumes that all parameters (if any) are NOT NULL.
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICURSOR-OPEN-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_cursor_open</FUNCTION> performs the following:
-TBD
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPICURSOR-FIND">
-<REFMETA>
-<REFENTRYTITLE>SPI_cursor_find</REFENTRYTITLE>
-<REFMISCINFO>SPI - Cursor Support</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_cursor_find
-</REFNAME>
-<REFPURPOSE>
-Finds an existing cursor (Portal) by name
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICURSOR-FIND-1"><PRIMARY>SPI</PRIMARY><SECONDARY>cursors</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICURSOR-FIND-2"><PRIMARY>SPI_cursor_find</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2001-11-14</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_cursor_find(<REPLACEABLE CLASS="PARAMETER">name</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-FIND-1">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-char *<REPLACEABLE CLASS="PARAMETER">name</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Name of portal
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-FIND-2">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>Portal
-</TERM>
-<LISTITEM>
-<PARA>
-   Pointer to Portal with given name, or NULL if not found
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICURSOR-FIND-1">
-<REFSECT1INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_cursor_find</FUNCTION> 
-   finds a pre-existing Portal by name.  This is primarily useful
-   to resolve a cursor name returned as text by some other function.
-</para>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICURSOR-FIND-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPICURSOR-FIND-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_cursor_find</FUNCTION> performs the following:
-TBD
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPICURSOR-FETCH">
-<REFMETA>
-<REFENTRYTITLE>SPI_cursor_fetch</REFENTRYTITLE>
-<REFMISCINFO>SPI - Cursor Support</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_cursor_fetch
-</REFNAME>
-<REFPURPOSE>
-Fetches some rows from a cursor
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICURSOR-FETCH-1"><PRIMARY>SPI</PRIMARY><SECONDARY>cursors</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICURSOR-FETCH-2"><PRIMARY>SPI_cursor_fetch</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2001-11-14</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_cursor_fetch(<REPLACEABLE CLASS="PARAMETER">portal</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">forward</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">count</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-FETCH-1">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-Portal <REPLACEABLE CLASS="PARAMETER">portal</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Portal containing cursor
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-bool <REPLACEABLE CLASS="PARAMETER">forward</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-True for fetch forward, false for fetch backward
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">count</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Maximum number of rows to fetch
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-FETCH-2">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>SPI_tuptable
-</TERM>
-<LISTITEM>
-<PARA>
-initialized as in
-   <Function>SPI_exec</Function> if successful
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>SPI_processed
-</TERM>
-<LISTITEM>
-<PARA>
-initialized as in
-   <Function>SPI_exec</Function> if successful
-</para>
-</listitem>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICURSOR-FETCH-1">
-<REFSECT1INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_cursor_fetch</FUNCTION> 
-   fetches some (more) rows from a cursor.  This is equivalent to the
-   SQL command <command>FETCH</>.
-</para>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICURSOR-FETCH-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPICURSOR-FETCH-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_cursor_fetch</FUNCTION> performs the following:
-TBD
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPICURSOR-MOVE">
-<REFMETA>
-<REFENTRYTITLE>SPI_cursor_move</REFENTRYTITLE>
-<REFMISCINFO>SPI - Cursor Support</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_cursor_move
-</REFNAME>
-<REFPURPOSE>
-Moves a cursor
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICURSOR-MOVE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>cursors</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICURSOR-MOVE-2"><PRIMARY>SPI_cursor_move</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2001-11-14</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_cursor_move(<REPLACEABLE CLASS="PARAMETER">portal</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">forward</REPLACEABLE>,
-<REPLACEABLE CLASS="PARAMETER">count</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-MOVE-1">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-Portal <REPLACEABLE CLASS="PARAMETER">portal</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Portal containing cursor
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-bool <REPLACEABLE CLASS="PARAMETER">forward</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-True for move forward, false for move backward
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">count</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Maximum number of rows to move
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-MOVE-2">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>None
-</TERM>
-<LISTITEM>
-<PARA>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICURSOR-MOVE-1">
-<REFSECT1INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_cursor_move</FUNCTION> 
-   skips over some number of rows in a cursor.  This is equivalent to the
-   SQL command <command>MOVE</>.
-</para>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICURSOR-MOVE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPICURSOR-MOVE-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_cursor_move</FUNCTION> performs the following:
-TBD
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPICURSOR-CLOSE">
-<REFMETA>
-<REFENTRYTITLE>SPI_cursor_close</REFENTRYTITLE>
-<REFMISCINFO>SPI - Cursor Support</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_cursor_close
-</REFNAME>
-<REFPURPOSE>
-Closes a cursor
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICURSOR-CLOSE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>cursors</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICURSOR-CLOSE-2"><PRIMARY>SPI_cursor_close</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2001-11-14</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_cursor_close(<REPLACEABLE CLASS="PARAMETER">portal</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-CLOSE-1">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-Portal <REPLACEABLE CLASS="PARAMETER">portal</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Portal containing cursor
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICURSOR-CLOSE-2">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>None
-</TERM>
-<LISTITEM>
-<PARA>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICURSOR-CLOSE-1">
-<REFSECT1INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_cursor_close</FUNCTION> 
-   closes a previously created cursor and releases its Portal storage.
-</para>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPICURSOR-CLOSE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-   All open cursors are closed implicitly at transaction end.
-   <FUNCTION>SPI_cursor_close</FUNCTION> need only be invoked if
-   it is desirable to release resources sooner.
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICURSOR-CLOSE-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_cursor_close</FUNCTION> performs the following:
-TBD
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPISAVEPLAN">
-<REFMETA>
-<REFENTRYTITLE>SPI_saveplan</REFENTRYTITLE>
-<REFMISCINFO>SPI - Plan Storage</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_saveplan
-</REFNAME>
-<REFPURPOSE>
-   Saves a passed plan
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPISAVEPLAN-1"><PRIMARY>SPI</PRIMARY><SECONDARY>connecting</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPISAVEPLAN-2"><PRIMARY>SPI_saveplan</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_saveplan(<REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPISAVEPLAN-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-void *<REPLACEABLE CLASS="PARAMETER">query</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Passed plan
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPISAVEPLAN-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>void *
-</TERM>
-<LISTITEM>
-<PARA>
-Execution plan location. NULL if unsuccessful.
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>SPI_result
-</TERM>
-<LISTITEM>
-<PARA>
-<SimpleList>
-<Member>
-   <ReturnValue>SPI_ERROR_ARGUMENT</ReturnValue> if plan is NULL
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_UNCONNECTED</ReturnValue> if procedure is un-connected
-</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPISAVEPLAN-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_saveplan</FUNCTION> 
-   stores a plan prepared by <Function>SPI_prepare</Function> in safe memory
-   protected from freeing by <Function>SPI_finish</Function> or the transaction manager.
-</para>
-<Para>
-   In the current version of <ProductName>PostgreSQL</ProductName> there is no ability to
- store prepared plans in the system
-   catalog and fetch them from there for execution. This will be implemented
-   in future versions.
-
-   As an alternative, there is the ability to reuse prepared plans in the
-   subsequent invocations of your procedure in the current session.
-   Use <Function>SPI_execp</Function> to execute this saved plan.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPISAVEPLAN-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-   <Function>SPI_saveplan</Function> saves a passed plan (prepared by <Function>SPI_prepare</Function>) in memory
-   protected from freeing by <Function>SPI_finish</Function> and by the transaction manager and
-   returns a pointer to the saved plan.  You may save the pointer returned in
-   a local variable.  Always check if this pointer is NULL or not either when
-   preparing a plan or using an already prepared plan in SPI_execp (see below).
-
-<Note>
-<Para>
-   If one of the objects (a relation, function, etc.) referenced by the prepared
-   plan is dropped during your session (by your backend or another process) then the
-   results of <Function>SPI_execp</Function> for this plan will be unpredictable.
-</Para>
-</Note>
-
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPISAVEPLAN-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA><FUNCTION>SPI_saveplan</FUNCTION> performs the following:
-TBD
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPISAVEPLAN-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-</Sect1>
-
-<Sect1 id="spi-interface-support">
-<Title>Interface Support Functions</Title>
-
-<Para>
-The functions described here provide convenient interfaces for extracting
-information from tuple sets returned by <function>SPI_exec</> and other
-SPI interface functions.
-</Para>
-
-<Para>
-All functions described in this section may be used by both connected and
-unconnected procedures.
-</Para>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIFNUMBER">
-<REFMETA>
-<REFENTRYTITLE>SPI_fnumber</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Information</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_fnumber
-</REFNAME>
-<REFPURPOSE>
-Finds the attribute number for specified attribute name
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIFNUMBER-1"><PRIMARY>SPI</PRIMARY><SECONDARY>decoding tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIFNUMBER-2"><PRIMARY>SPI_fnumber</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_fnumber(<REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">fname</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIFNUMBER-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-TupleDesc <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple description
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-char * <REPLACEABLE CLASS="PARAMETER">fname</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Field name
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIFNUMBER-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-int
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute number
-<SimpleList>
-<Member>
-Valid one-based index number of attribute
-</Member>
-<Member>
-<ReturnValue>SPI_ERROR_NOATTRIBUTE</ReturnValue> if the named attribute is not found
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIFNUMBER-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_fnumber</FUNCTION> 
-   returns the attribute number for the attribute with name in fname.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIFNUMBER-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-Attribute numbers are 1 based.
-</Para>
-<Para>
-If the given fname refers to a system attribute (eg, <literal>oid</>)
-then the appropriate negative attribute number will be returned.
-The caller should be careful to test for exact equality to 
-<ReturnValue>SPI_ERROR_NOATTRIBUTE</ReturnValue> to detect error;
-testing for result &lt;= 0 is not correct unless system attributes
-should be rejected.
-</Para>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIFNUMBER-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPIFNUMBER-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIFNAME">
-<REFMETA>
-<REFENTRYTITLE>SPI_fname</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Information</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_fname
-</REFNAME>
-<REFPURPOSE>
-Finds the attribute name for the specified attribute number
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIFNAME-1"><PRIMARY>SPI</PRIMARY><SECONDARY>decoding tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIFNAME-2"><PRIMARY>SPI_fname</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_fname(<REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIFNAME-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-TupleDesc <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple description
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute number
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIFNAME-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-char *
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute name
-<SimpleList>
-<Member>
-NULL if fnumber is out of range
-</Member>
-<Member>
-SPI_result set to
-<ReturnValue>SPI_ERROR_NOATTRIBUTE</ReturnValue> on error
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIFNAME-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_fname</FUNCTION> 
-   returns the attribute name for the specified attribute.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIFNAME-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-Attribute numbers are 1 based.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIFNAME-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-Returns a newly-allocated copy of the attribute name.
-(Use pfree() to release the copy when done with it.)
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIFNAME-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIGETVALUE">
-<REFMETA>
-<REFENTRYTITLE>SPI_getvalue</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Information</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_getvalue
-</REFNAME>
-<REFPURPOSE>
-Returns the string value of the specified attribute
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIGETVALUE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>decoding tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIGETVALUE-2"><PRIMARY>SPI_getvalue</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_getvalue(<REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIGETVALUE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-HeapTuple <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple to be examined
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-TupleDesc <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple description
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute number
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIGETVALUE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-char *
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute value or NULL if
-<SimpleList>
-<Member>
-attribute is NULL
-</Member>
-<Member>
-fnumber is out of range
-(SPI_result set to
-<ReturnValue>SPI_ERROR_NOATTRIBUTE</ReturnValue>)
-</Member>
-<Member>
-no output function available
-(SPI_result set to
-<ReturnValue>SPI_ERROR_NOOUTFUNC</ReturnValue>)
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIGETVALUE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_getvalue</FUNCTION> 
-   returns an external (string) representation of the value of the specified attribute.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIGETVALUE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-Attribute numbers are 1 based.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIGETVALUE-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-The result is returned as a palloc'd string.
-(Use pfree() to release the string when done with it.)
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIGETVALUE-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIGETBINVAL">
-<REFMETA>
-<REFENTRYTITLE>SPI_getbinval</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Information</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_getbinval
-</REFNAME>
-<REFPURPOSE>
-Returns the binary value of the specified attribute
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIGETBINVAL-1"><PRIMARY>SPI</PRIMARY><SECONDARY>decoding tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIGETBINVAL-2"><PRIMARY>SPI_getbinval</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_getbinval(<REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">isnull</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIGETBINVAL-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-HeapTuple <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple to be examined
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-TupleDesc <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple description
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute number
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIGETBINVAL-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-Datum
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute binary value
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-bool * <REPLACEABLE CLASS="PARAMETER">isnull</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-flag for null value in attribute
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-SPI_result
-</TERM>
-<LISTITEM>
-<PARA>
-<SimpleList>
-<Member>
-<ReturnValue>SPI_ERROR_NOATTRIBUTE</ReturnValue>
-</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIGETBINVAL-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_getbinval</FUNCTION> 
-   returns the specified attribute's value in internal form (as a Datum).
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIGETBINVAL-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-Attribute numbers are 1 based.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIGETBINVAL-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-Does not allocate new space for the datum.  In the case of a pass-by-
-reference data type, the Datum will be a pointer into the given tuple.
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIGETBINVAL-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIGETTYPE">
-<REFMETA>
-<REFENTRYTITLE>SPI_gettype</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Information</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_gettype
-</REFNAME>
-<REFPURPOSE>
-Returns the type name of the specified attribute
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIGETTYPE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>decoding tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIGETTYPE-2"><PRIMARY>SPI_gettype</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_gettype(<REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIGETTYPE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-TupleDesc <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple description
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute number
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIGETTYPE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-char *
-</TERM>
-<LISTITEM>
-<PARA>
-The type name for the specified attribute number
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-SPI_result
-</TERM>
-<LISTITEM>
-<PARA>
-<SimpleList>
-<Member>
-<ReturnValue>SPI_ERROR_NOATTRIBUTE</ReturnValue>
-</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIGETTYPE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_gettype</FUNCTION> 
-   returns a copy of the type name for the specified attribute,
-   or NULL on error.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIGETTYPE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-Attribute numbers are 1 based.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIGETTYPE-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-Returns a newly-allocated copy of the type name.
-(Use pfree() to release the copy when done with it.)
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIGETTYPE-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIGETTYPEID">
-<REFMETA>
-<REFENTRYTITLE>SPI_gettypeid</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Information</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_gettypeid
-</REFNAME>
-<REFPURPOSE>
-Returns the type <Acronym>OID</Acronym> of the specified attribute
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIGETTYPEID-1"><PRIMARY>SPI</PRIMARY><SECONDARY>decoding tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIGETTYPEID-2"><PRIMARY>SPI_gettypeid</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_gettypeid(<REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIGETTYPEID-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-TupleDesc <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple description
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">fnumber</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Attribute number
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIGETTYPEID-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-<Acronym>OID</Acronym>
-</TERM>
-<LISTITEM>
-<PARA>
-The type <Acronym>OID</Acronym> for the specified attribute number
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-SPI_result
-</TERM>
-<LISTITEM>
-<PARA>
-<SimpleList>
-<Member>
-<ReturnValue>SPI_ERROR_NOATTRIBUTE</ReturnValue>
-</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIGETTYPEID-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_gettypeid</FUNCTION> 
-   returns the type <Acronym>OID</Acronym> for the specified attribute.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIGETTYPEID-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-Attribute numbers are 1 based.
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIGETTYPEID-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-TBD
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPIGETTYPEID-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIGETRELNAME">
-<REFMETA>
-<REFENTRYTITLE>SPI_getrelname</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Information</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_getrelname
-</REFNAME>
-<REFPURPOSE>
-Returns the name of the specified relation
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIGETRELNAME-1"><PRIMARY>SPI</PRIMARY><SECONDARY>decoding tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIGETRELNAME-2"><PRIMARY>SPI_getrelname</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_getrelname(<REPLACEABLE CLASS="PARAMETER">rel</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIGETRELNAME-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-Relation <REPLACEABLE CLASS="PARAMETER">rel</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input relation
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIGETRELNAME-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-char *
-</TERM>
-<LISTITEM>
-<PARA>
-The name of the specified relation
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIGETRELNAME-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_getrelname</FUNCTION> 
-   returns the name of the specified relation.
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIGETRELNAME-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-TBD
-</PARA>
-</REFSECT1>
--->
-<REFSECT1 ID="R1-SPI-SPIGETRELNAME-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-Returns a newly-allocated copy of the rel name.
-(Use pfree() to release the copy when done with it.)
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIGETRELNAME-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-</Sect1>
-
-<Sect1 id="spi-memory">
-<Title>Memory Management</Title>
-
-<Para>
-<ProductName>PostgreSQL</ProductName> allocates memory within memory
-<firstterm>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 --- 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 allocated memory object
-(such as a value of a pass-by-reference data type), you can't allocate
-the return object using <Function>palloc</Function>, at least not while
-you are connected to SPI.  If you try, the object will be deallocated
-during <Function>SPI_finish</Function>, and your procedure will not
-work reliably!
-</Para>
-<Para>
-To solve this problem, use <Function>SPI_palloc</Function> to allocate
-your return object.  <Function>SPI_palloc</Function> allocates space
-from <quote>upper Executor</> memory --- that is, the memory context
-that was current when <Function>SPI_connect</Function> was called,
-which is precisely the right context for return values of your procedure.
-</Para>
-<Para>
-If called while not connected to SPI, <Function>SPI_palloc</Function>
-acts the same as plain <Function>palloc</Function>.
-</Para>
-<Para>
-   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>
-   After <Function>SPI_connect</Function> is called, the current context is
-   the procedure's private context made by <Function>SPI_connect</Function>.
-   All allocations made via
-<Function>palloc</Function>/<Function>repalloc</Function> or by SPI utility
-functions (except for <Function>SPI_copytuple</Function>,
-<Function>SPI_copytupledesc</Function>,
-<Function>SPI_copytupleintoslot</Function>,
-<Function>SPI_modifytuple</Function>,
-and <Function>SPI_palloc</Function>) are
-made in this context.
-</Para>
-<Para>
-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 can't be used any more!
-</Para>
-
-<Para>
-All functions described in this section may be used by both connected and
-unconnected procedures.  In an unconnected procedure, they act the same
-as the underlying ordinary backend functions (<function>palloc</> etc).
-</Para>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPICOPYTUPLE">
-<REFMETA>
-<REFENTRYTITLE>SPI_copytuple</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Copy</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_copytuple
-</REFNAME>
-<REFPURPOSE>
-Makes copy of tuple in upper Executor context
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICOPYTUPLE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>copying tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICOPYTUPLE-2"><PRIMARY>SPI_copytuple</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_copytuple(<REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICOPYTUPLE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-HeapTuple <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple to be copied
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICOPYTUPLE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-HeapTuple
-</TERM>
-<LISTITEM>
-<PARA>
-Copied tuple
-<SimpleList>
-<Member>
- <ReturnValue>non-NULL</ReturnValue>
- if <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
- is not NULL and the copy was successful
-</Member>
-<Member>
-   <ReturnValue>NULL</ReturnValue>
- only if <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
- is NULL
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_copytuple</FUNCTION> 
-   makes a copy of tuple in upper Executor context.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-TBD
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLE-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLE-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPICOPYTUPLEDESC">
-<REFMETA>
-<REFENTRYTITLE>SPI_copytupledesc</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Descriptor Copy</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_copytupledesc
-</REFNAME>
-<REFPURPOSE>
-Makes copy of tuple descriptor in upper Executor context
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICOPYTUPLEDESC-1"><PRIMARY>SPI</PRIMARY><SECONDARY>copying tuple descriptors</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICOPYTUPLEDESC-2"><PRIMARY>SPI_copytupledesc</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2001-08-02</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_copytupledesc(<REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICOPYTUPLEDESC-1">
-<REFSECT2INFO>
-<DATE>2001-08-02</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-TupleDesc <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple descriptor to be copied
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICOPYTUPLEDESC-2">
-<REFSECT2INFO>
-<DATE>2001-08-02</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-TupleDesc
-</TERM>
-<LISTITEM>
-<PARA>
-Copied tuple descriptor
-<SimpleList>
-<Member>
- <ReturnValue>non-NULL</ReturnValue>
- if <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
- is not NULL and the copy was successful
-</Member>
-<Member>
-   <ReturnValue>NULL</ReturnValue>
- only if <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
- is NULL
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLEDESC-1">
-<REFSECT1INFO>
-<DATE>2001-08-02</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_copytupledesc</FUNCTION> 
-   makes a copy of tupdesc in upper Executor context.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLEDESC-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-TBD
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLEDESC-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLEDESC-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPICOPYTUPLEINTOSLOT">
-<REFMETA>
-<REFENTRYTITLE>SPI_copytupleintoslot</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple and Descriptor Copy</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_copytupleintoslot
-</REFNAME>
-<REFPURPOSE>
-Makes copy of tuple and descriptor in upper Executor context
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPICOPYTUPLEINTOSLOT-1"><PRIMARY>SPI</PRIMARY><SECONDARY>copying tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPICOPYTUPLEINTOSLOT-2"><PRIMARY>SPI_copytupleintoslot</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_copytupleintoslot(<REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPICOPYTUPLEINTOSLOT-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-HeapTuple <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple to be copied
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-TupleDesc <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple descriptor to be copied
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPICOPYTUPLEINTOSLOT-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-TupleTableSlot *
-</TERM>
-<LISTITEM>
-<PARA>
-Tuple slot containing copied tuple and descriptor
-<SimpleList>
-<Member>
- <ReturnValue>non-NULL</ReturnValue>
- if <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
- and <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
- are not NULL and the copy was successful
-</Member>
-<Member>
-   <ReturnValue>NULL</ReturnValue>
- only if <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
- or <REPLACEABLE CLASS="PARAMETER">tupdesc</REPLACEABLE>
- is NULL
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLEINTOSLOT-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_copytupleintoslot</FUNCTION> 
-   makes a copy of tuple in upper Executor context, returning it in the
-   form of a filled-in TupleTableSlot.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLEINTOSLOT-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-TBD
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLEINTOSLOT-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPICOPYTUPLEINTOSLOT-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIMODIFYTUPLE">
-<REFMETA>
-<REFENTRYTITLE>SPI_modifytuple</REFENTRYTITLE>
-<REFMISCINFO>SPI - Tuple Modify</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_modifytuple
-</REFNAME>
-<REFPURPOSE>
-Creates a tuple by replacing selected fields of a given tuple
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIMODIFYTUPLE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>modifying tuples</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIMODIFYTUPLE-2"><PRIMARY>SPI_modifytuple</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_modifytuple(<REPLACEABLE CLASS="PARAMETER">rel</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">nattrs</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">attnum</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">Values</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">Nulls</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIMODIFYTUPLE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-Relation <REPLACEABLE CLASS="PARAMETER">rel</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Used only as source of tuple descriptor for tuple.  (Passing a relation
-rather than a tuple descriptor is a misfeature.)
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-HeapTuple <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Input tuple to be modified
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int <REPLACEABLE CLASS="PARAMETER">nattrs</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Number of attribute numbers in attnum array
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-int * <REPLACEABLE CLASS="PARAMETER">attnum</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Array of numbers of the attributes that are to be changed
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-Datum * <REPLACEABLE CLASS="PARAMETER">Values</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-New values for the attributes specified
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-char * <REPLACEABLE CLASS="PARAMETER">Nulls</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Which new values are NULL, if any
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIMODIFYTUPLE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-HeapTuple
-</TERM>
-<LISTITEM>
-<PARA>
-New tuple with modifications
-<SimpleList>
-<Member>
- <ReturnValue>non-NULL</ReturnValue>
- if <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
- is not NULL and the modify was successful
-</Member>
-<Member>
-   <ReturnValue>NULL</ReturnValue>
- only if <REPLACEABLE CLASS="PARAMETER">tuple</REPLACEABLE>
- is NULL
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-SPI_result
-</TERM>
-<LISTITEM>
-<PARA>
-<SimpleList>
-<Member>
-   <ReturnValue>SPI_ERROR_ARGUMENT</ReturnValue> if rel is NULL or tuple is NULL or natts &lt;= 0 or
-   attnum is NULL or Values is NULL.
-</Member>
-<Member>
-   <ReturnValue>SPI_ERROR_NOATTRIBUTE</ReturnValue> if there is an invalid 
-   attribute number in attnum (attnum &lt;= 0 or &gt; number of
-   attributes in tuple)
-</Member>
-</SimpleList>
-</para>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIMODIFYTUPLE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_modifytuple</FUNCTION> 
-creates a new tuple by substituting new values for selected attributes,
-copying the original tuple's attributes at other positions.  The input
-tuple is not modified.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIMODIFYTUPLE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-If successful, a pointer to the new tuple is returned. The new tuple is
-allocated in upper Executor context.
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIMODIFYTUPLE-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPIMODIFYTUPLE-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIPALLOC">
-<REFMETA>
-<REFENTRYTITLE>SPI_palloc</REFENTRYTITLE>
-<REFMISCINFO>SPI - Memory Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_palloc
-</REFNAME>
-<REFPURPOSE>
-Allocates memory in upper Executor context
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIPALLOC-1"><PRIMARY>SPI</PRIMARY><SECONDARY>allocating space</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIPALLOC-2"><PRIMARY>SPI_palloc</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_palloc(<REPLACEABLE CLASS="PARAMETER">size</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIPALLOC-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-Size <REPLACEABLE CLASS="PARAMETER">size</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Octet size of storage to allocate
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIPALLOC-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-void *
-</TERM>
-<LISTITEM>
-<PARA>
-New storage space of specified size
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIPALLOC-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_palloc</FUNCTION> 
-   allocates memory in upper Executor context.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIPALLOC-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-TBD
-</PARA>
-</REFSECT1>
-<!--
-<REFSECT1 ID="R1-SPI-SPIPALLOC-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-TBD
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPIPALLOC-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIREPALLOC">
-<REFMETA>
-<REFENTRYTITLE>SPI_repalloc</REFENTRYTITLE>
-<REFMISCINFO>SPI - Memory Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_repalloc
-</REFNAME>
-<REFPURPOSE>
-Re-allocates memory in upper Executor context
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIREPALLOC-1"><PRIMARY>SPI</PRIMARY><SECONDARY>allocating space</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIREPALLOC-2"><PRIMARY>SPI_repalloc</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_repalloc(<REPLACEABLE CLASS="PARAMETER">pointer</REPLACEABLE>, <REPLACEABLE CLASS="PARAMETER">size</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIREPALLOC-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-void * <REPLACEABLE CLASS="PARAMETER">pointer</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Pointer to existing storage
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-<VARLISTENTRY>
-<TERM>
-Size <REPLACEABLE CLASS="PARAMETER">size</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Octet size of storage to allocate
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIREPALLOC-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-void *
-</TERM>
-<LISTITEM>
-<PARA>
-New storage space of specified size with contents copied from existing area
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIREPALLOC-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_repalloc</FUNCTION> 
-   re-allocates memory in upper Executor context.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIREPALLOC-2">
-<TITLE>Usage
-</TITLE>
-<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 ID="R1-SPI-SPIREPALLOC-3">
-<TITLE>Algorithm
-</TITLE>
-<PARA>
-TBD
-</PARA>
-</REFSECT1>
--->
-<!--
-<REFSECT1 ID="R1-SPI-SPIREPALLOC-4">
-<TITLE>Structures
-</TITLE>
-<PARA>None
-</PARA>
-</REFSECT1>
--->
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIPFREE">
-<REFMETA>
-<REFENTRYTITLE>SPI_pfree</REFENTRYTITLE>
-<REFMISCINFO>SPI - Memory Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_pfree
-</REFNAME>
-<REFPURPOSE>
-Frees memory in upper Executor context
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIPFREE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>allocating space</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIPFREE-2"><PRIMARY>SPI_pfree</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_pfree(<REPLACEABLE CLASS="PARAMETER">pointer</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIPFREE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-void * <REPLACEABLE CLASS="PARAMETER">pointer</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Pointer to existing storage
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIPFREE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-None
-</TERM>
-<LISTITEM>
-<PARA>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIPFREE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_pfree</FUNCTION> 
-   frees memory in upper Executor context.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIPFREE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-This function is no longer different from plain <FUNCTION>pfree</FUNCTION>.
-It's kept just for backward compatibility of existing code.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIFREETUPLE">
-<REFMETA>
-<REFENTRYTITLE>SPI_freetuple</REFENTRYTITLE>
-<REFMISCINFO>SPI - Memory Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_freetuple
-</REFNAME>
-<REFPURPOSE>
-Frees a tuple allocated in upper Executor context
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIFREETUPLE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>allocating space</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIFREETUPLE-2"><PRIMARY>SPI_freetuple</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>1997-12-24</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_freetuple(<REPLACEABLE CLASS="PARAMETER">pointer</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIFREETUPLE-1">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-HeapTuple <REPLACEABLE CLASS="PARAMETER">pointer</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Pointer to allocated tuple
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIFREETUPLE-2">
-<REFSECT2INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-None
-</TERM>
-<LISTITEM>
-<PARA>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIFREETUPLE-1">
-<REFSECT1INFO>
-<DATE>1997-12-24</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_freetuple</FUNCTION> 
-   frees a tuple previously allocated in upper Executor context.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIFREETUPLE-2">
-<TITLE>Usage
-</TITLE>
-<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>
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIFREETUPTABLE">
-<REFMETA>
-<REFENTRYTITLE>SPI_freetuptable</REFENTRYTITLE>
-<REFMISCINFO>SPI - Memory Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_freetuptable
-</REFNAME>
-<REFPURPOSE>
-Frees a tuple set created by <function>SPI_exec</> or similar function
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIFREETUPTABLE-1"><PRIMARY>SPI</PRIMARY><SECONDARY>allocating space</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIFREETUPTABLE-2"><PRIMARY>SPI_freetuptable</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2001-11-14</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_freetuptable(<REPLACEABLE CLASS="PARAMETER">tuptable</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIFREETUPTABLE-1">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-SPITupleTable * <REPLACEABLE CLASS="PARAMETER">tuptable</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Pointer to tuple table
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIFREETUPTABLE-2">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-None
-</TERM>
-<LISTITEM>
-<PARA>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIFREETUPTABLE-1">
-<REFSECT1INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_freetuptable</FUNCTION> 
-   frees a tuple set created by a prior SPI query function, such as
-   <function>SPI_exec</>.
-</PARA>
-</REFSECT1>
-<REFSECT1 ID="R1-SPI-SPIFREETUPTABLE-2">
-<TITLE>Usage
-</TITLE>
-<Para>
-This function is useful if a SPI procedure needs to execute multiple
-queries and does not want to keep the results of earlier queries around
-until it ends.  Note that any unfreed tuple sets will be freed anyway
-at <function>SPI_finish</>.
-</PARA>
-</REFSECT1>
-</REFENTRY>
-
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-<!-- *********************************************** -->
-
-<REFENTRY ID="SPI-SPIFREEPLAN">
-<REFMETA>
-<REFENTRYTITLE>SPI_freeplan</REFENTRYTITLE>
-<REFMISCINFO>SPI - Memory Management</REFMISCINFO>
-</REFMETA>
-<REFNAMEDIV>
-<REFNAME>SPI_freeplan
-</REFNAME>
-<REFPURPOSE>
-   Releases a previously saved plan
-</REFPURPOSE>
-<INDEXTERM ID="IX-SPI-SPIFREEPLAN-1"><PRIMARY>SPI</PRIMARY><SECONDARY>allocating space</SECONDARY></INDEXTERM>
-<INDEXTERM ID="IX-SPI-SPIFREEPLAN-2"><PRIMARY>SPI_freeplan</PRIMARY></INDEXTERM>
-</REFNAMEDIV>
-<REFSYNOPSISDIV>
-<REFSYNOPSISDIVINFO>
-<DATE>2001-11-14</DATE>
-</REFSYNOPSISDIVINFO>
-<SYNOPSIS>
-SPI_freeplan(<REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>)
-</SYNOPSIS>
-
-<REFSECT2 ID="R2-SPI-SPIFREEPLAN-1">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Inputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>
-void *<REPLACEABLE CLASS="PARAMETER">plan</REPLACEABLE>
-</TERM>
-<LISTITEM>
-<PARA>
-Passed plan
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-
-<REFSECT2 ID="R2-SPI-SPIFREEPLAN-2">
-<REFSECT2INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT2INFO>
-<TITLE>Outputs
-</TITLE>
-<VARIABLELIST>
-<VARLISTENTRY>
-<TERM>int
-</TERM>
-<LISTITEM>
-<PARA>
-<SimpleList>
-<Member>
-   <ReturnValue>SPI_ERROR_ARGUMENT</ReturnValue> if plan is NULL
-</Member>
-</SimpleList>
-</PARA>
-</LISTITEM>
-</VARLISTENTRY>
-</VARIABLELIST>
-</REFSECT2>
-</REFSYNOPSISDIV>
-
-<REFSECT1 ID="R1-SPI-SPIFREEPLAN-1">
-<REFSECT1INFO>
-<DATE>2001-11-14</DATE>
-</REFSECT1INFO>
-<TITLE>Description
-</TITLE>
-<PARA>
-<FUNCTION>SPI_freeplan</FUNCTION> 
-   releases a query plan previously returned by
-   <Function>SPI_prepare</Function> or saved by
-   <Function>SPI_saveplan</Function>.
-</para>
-</REFSECT1>
-</REFENTRY>
-
-</Sect1>
-
-<Sect1 id="spi-visibility">
-<Title>Visibility of Data Changes</Title>
-
-<Para>
-<ProductName>PostgreSQL</ProductName> data changes visibility rule: during a query execution, data
-changes made by the query itself (via SQL-function, SPI-function, triggers)
-are invisible to the query scan.  For example, in query
-<programlisting>
-   INSERT INTO a SELECT * FROM a
-</programlisting>
-   tuples inserted are invisible for SELECT's scan.  In effect, this
-duplicates the database table within itself (subject to unique index
-rules, of course) without recursing.
-</Para>
-
-<Para>
-   Changes made by query Q are visible to queries that are started after
-query Q, no matter whether they are started inside Q (during the execution
-of Q) or after Q is done.
-</Para>
-</Sect1>
-
-<Sect1 id="spi-examples">
-<Title>Examples</Title>
-
-<Para>
-   This example of SPI usage demonstrates the visibility rule.
-   There are more complex examples in src/test/regress/regress.c and
-in contrib/spi.
-</Para>
-
-<Para>
-   This is a very simple example of SPI usage. The procedure execq accepts
-an SQL-query in its first argument and tcount in its second, executes the
-query using SPI_exec and returns the number of tuples for which the query
-executed:
-
-<ProgramListing>
-#include "executor/spi.h"   /* this is what you need to work with SPI */
-
-int execq(text *sql, int cnt);
-
-int
-execq(text *sql, int cnt)
-{
-    char *query;
-    int ret;
-    int proc;
-
-    /* Convert given TEXT object to a C string */
-    query = DatumGetCString(DirectFunctionCall1(textout,
-                                                PointerGetDatum(sql)));
-
-    SPI_connect();
-    
-    ret = SPI_exec(query, cnt);
-    
-    proc = SPI_processed;
-    /*
-     * If this is SELECT and some tuple(s) fetched -
-     * returns tuples to the caller via elog (INFO).
-     */
-    if ( ret == SPI_OK_SELECT && SPI_processed > 0 )
-    {
-        TupleDesc tupdesc = SPI_tuptable->tupdesc;
-        SPITupleTable *tuptable = SPI_tuptable;
-        char buf[8192];
-        int i,j;
-        
-        for (j = 0; j < proc; j++)
-        {
-            HeapTuple tuple = tuptable->vals[j];
-            
-            for (i = 1, buf[0] = 0; i <= tupdesc->natts; i++)
-                sprintf(buf + strlen (buf), " %s%s",
-                        SPI_getvalue(tuple, tupdesc, i),
-                        (i == tupdesc->natts) ? " " : " |");
-            elog (INFO, "EXECQ: %s", buf);
-        }
-    }
-
-    SPI_finish();
-
-    pfree(query);
-
-    return (proc);
-}
-</ProgramListing>
-</Para>
-
-<Para>
-   Now, compile and create the function:
-
-<ProgramListing>
-CREATE FUNCTION execq (text, integer) RETURNS integer
-    AS '...path_to_so'
-    LANGUAGE C;
-</ProgramListing>
-
-<ProgramListing>
-vac=> SELECT execq('CREATE TABLE a (x INTEGER)', 0);
-execq
------
-    0
-(1 row)
-
-vac=> INSERT INTO a VALUES (execq('INSERT INTO a VALUES (0)',0));
-INSERT 167631 1
-vac=> SELECT execq('SELECT * FROM a',0);
-INFO:  EXECQ:  0 <<< inserted by execq
-
-INFO:  EXECQ:  1 <<< value returned by execq and inserted by upper INSERT
-
-execq
------
-    2
-(1 row)
-
-vac=> SELECT execq('INSERT INTO a SELECT x + 2 FROM a',1);
-execq
------
-    1
-(1 row)
-
-vac=> SELECT execq('SELECT * FROM a', 10);
-INFO:  EXECQ:  0 
-
-INFO:  EXECQ:  1 
-
-INFO:  EXECQ:  2 <<< 0 + 2, only one tuple inserted - as specified
-
-execq
------
-    3            <<< 10 is max value only, 3 is real # of tuples
-(1 row)
-
-vac=> DELETE FROM a;
-DELETE 3
-vac=> INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1);
-INSERT 167712 1
-vac=> SELECT * FROM a;
-x
--
-1                <<< no tuples in a (0) + 1
-(1 row)
-
-vac=> INSERT INTO a VALUES (execq('SELECT * FROM a', 0) + 1);
-INFO:  EXECQ:  0 
-INSERT 167713 1
-vac=> SELECT * FROM a;
-x
--
-1
-2                <<< there was single tuple in a + 1
-(2 rows)
-
---   This demonstrates data changes visibility rule:
-
-vac=> 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
-vac=> SELECT * FROM a;
-x
--
-1
-2
-2                <<< 2 tuples * 1 (x in first tuple)
-6                <<< 3 tuples (2 + 1 just inserted) * 2 (x in second tuple)
-(4 rows)             ^^^^^^^^ 
-                     tuples visible to execq() in different invocations
-</ProgramListing>
-</Para>
-</Sect1>
-</Chapter>
diff --git a/doc/src/sgml/sql.sgml b/doc/src/sgml/sql.sgml
deleted file mode 100644
index 2c6247ff918..00000000000
--- a/doc/src/sgml/sql.sgml
+++ /dev/null
@@ -1,2156 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/sql.sgml,v 1.26 2002/03/15 16:16:31 momjian Exp $
--->
-
- <chapter id="sql">
-  <title>SQL</title>
-
-  <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 "<acronym>SQL</acronym>" 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 "<abbrev>SQL/86</abbrev>". In 1989 the original
-   standard was extended
-   and this new standard is often, again informally, referred to as
-   "<abbrev>SQL/89</abbrev>". 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 - "International Standard ISO/IEC 9075:1992,
-   Database Language <acronym>SQL</acronym>" - in late 1992.
-   <acronym>SQL/92</acronym> is the version
-   normally meant when people refer to "the <acronym>SQL</acronym>
-   standard". 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 is a very complex task and therefore the completion of
-   the new standard can not be expected before 1999.
-  </para>
-
-  <sect1 id="rel-model">
-   <title>The Relational Data Model</title>
-
-  <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>
-     <programlisting>
-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
-     </programlisting>
-    </example>
-   </para>
-
-   <para>
-    The tables PART and SUPPLIER may be regarded as
-    <firstterm>entities</firstterm> and
-    SELLS may 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>
-
-   <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>
-
-    <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>
-
-   <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>
-
-    <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:
-
-	 <programlisting>
-R:                 S:
- A | B | C          C | D | E
----+---+---        ---+---+---
- 1 | 2 | 3          3 | a | b
- 4 | 5 | 6          6 | c | d
- 7 | 8 | 9
-	 </programlisting>
-	</para>
-       </example>
-
-       <para>
-	First we calculate the Cartesian product
-	<classname>R</classname> &times; <classname>S</classname> and
-	get:
-
-	<programlisting>
-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
-	</programlisting>
-       </para>
-
-       <para>
-	After the selection
-	&sigma;<subscript>R.C=S.C</subscript>(R &times; S)
-	we get:
-
-	<programlisting>
- A | B | R.C | S.C | D | E
----+---+-----+-----+---+---
- 1 | 2 |  3  |  3  | a | b
- 4 | 5 |  6  |  6  | c | d
-	</programlisting>
-       </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:
-
-	<programlisting>
- A | B | C | D | E
----+---+---+---+---
- 1 | 2 | 3 | a | b
- 4 | 5 | 6 | c | d
-	</programlisting>
-       </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
-
-	<programlisting>
-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
-	</programlisting>
-
-	R &divide; S
-	is derived as
-
-	<programlisting>
- A | B
----+---
- a | b
- e | d
-	</programlisting>
-       </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="DATE94" endterm="DATE94">].
-    </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:
-
-      <programlisting>
- SNAME
--------
- Smith
- Adams
-      </programlisting>
-     </para>
-    </example>
-   </sect2>
-
-   <sect2 id="rel-calc">
-    <title>Relational Calculus</title>
-
-    <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="DATE94" endterm="DATE94">
-     or
-     <xref linkend="ULL88" endterm="ULL88">.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Tuple Relational Calculus</title>
-
-    <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>
-
-    <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 ("Codd's reduction
-     algorithm") 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="DATE94" endterm="DATE94">
-     and
-     <xref linkend="ULL88" endterm="ULL88">.
-    </para>
-
-    <para>
-     It is sometimes said that languages based on the relational calculus
-     are "higher level" or "more declarative" 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>
-
-   <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>
-
-    <para>
-     The most often used command in <acronym>SQL</acronym> is the
-     SELECT statement,
-     used to retrieve data. The syntax is:
-
-     <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> ] [, ...] ]
-    [ FOR UPDATE [ OF <replaceable class="PARAMETER">class_name</replaceable> [, ...] ] ]
-    [ LIMIT { <replaceable class="PARAMETER">count</replaceable> | ALL } ]
-    [ OFFSET <replaceable class="PARAMETER">start</replaceable> ]
-     </synopsis>
-    </para>
-
-    <para>
-     Now we will illustrate the complex syntax of the SELECT 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>
-
-     <para>
-      Here are some simple examples using a SELECT 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 > 10;
-	</programlisting>
-
-	and get the table:
-
-	<programlisting>
- PNO |  PNAME  |  PRICE
------+---------+--------
-  3  |  Bolt   |   15
-  4  |  Cam    |   25
-	</programlisting>
-       </para>
-
-       <para>
-	Using "*" in the SELECT 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 > 10;
-	</programlisting>
-
-	In this case the result is:
-
-	<programlisting>
-                      PNAME  |  PRICE
-                     --------+--------
-                      Bolt   |   15
-                      Cam    |   25
-	</programlisting>
-
-	Note that the <acronym>SQL</acronym> SELECT corresponds to the 
-	"projection" in relational algebra not to the "selection"
-	(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 <= 15);
-	</programlisting>
-
-	will lead to the result:
-
-	<programlisting>
- PNAME  |  PRICE
---------+--------
- Bolt   |   15
-	</programlisting>
-       </para>
-
-       <para>
-	Arithmetic operations may 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 < 50;
-	</programlisting>
-
-	and we get:
-
-	<programlisting>
- PNAME  |  DOUBLE
---------+---------
- Screw  |    20
- Nut    |    16
- Bolt   |    30
-	</programlisting>
-
-	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>
-
-     <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:
-
-      <programlisting>
- SNAME | PNAME
--------+-------
- Smith | Screw
- Smith | Nut
- Jones | Cam
- Adams | Screw
- Adams | Bolt
- Blake | Nut
- Blake | Bolt
- Blake | Cam
-      </programlisting>
-     </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:
-	<programlisting>
- sname | pname
--------+-------
- Smith | Screw
- Adams | Screw
- Smith | Nut
- Blake | Nut
- Adams | Bolt
- Blake | Bolt
- Jones | Cam
- Blake | Cam
-(8 rows) 
-	 </programlisting>
-	 </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, may 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> may 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 Operators</title>
-
-     <para>
-      <acronym>SQL</acronym> provides aggregate operators
-      (e.g. AVG, COUNT, SUM, MIN, MAX) that
-      take an expression as argument.  The expression is evaluated at
-      each row that satisfies the WHERE clause, and the aggregate operator
-      is calculated over this set of input values.  Normally, an aggregate
-      delivers a single result for a whole SELECT 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:
-
-	<programlisting>
- AVG_PRICE
------------
-   14.5
-	</programlisting>
-       </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:
-
-	<programlisting>
- COUNT
--------
-   4
-	</programlisting>
-
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Aggregation by Groups</title>
-
-     <para>
-      <acronym>SQL</acronym> allows one to partition the tuples of a table
-      into groups. Then the
-      aggregate operators described above can be applied to the groups ---
-      i.e. the value of the aggregate operator is no longer calculated over
-      all the values of the specified column but over all values of a
-      group. Thus the aggregate operator 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:
-
-	<programlisting>
- SNO | SNAME | COUNT
------+-------+-------
-  1  | Smith |   2
-  2  | Jones |   1
-  3  | Adams |   2
-  4  | Blake |   3
-	</programlisting>
-       </para>
-
-       <para>
-	Now let's have a look of what is happening here.
-	First the join of the
-	tables SUPPLIER and SELLS is derived:
-
-	<programlisting>
- 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
-	</programlisting>
-       </para>
-
-       <para>
-	Next we partition the tuples into groups by putting all tuples
-	together that agree on both attributes S.SNO and S.SNAME:
-
-	<programlisting>
- S.SNO | S.SNAME | SE.PNO
--------+---------+--------
-   1   |  Smith  |   1
-                 |   2
---------------------------
-   2   |  Jones  |   4
---------------------------
-   3   |  Adams  |   1
-                 |   3
---------------------------
-   4   |  Blake  |   2
-                 |   3
-                 |   4
-	</programlisting>
-       </para>
-
-       <para>
-	In our example we got four groups and now we can apply the aggregate
-	operator 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
-      operators to make sense the target list can only refer directly to
-      the attributes being grouped by.  Other attributes may only be used
-      inside the argument of an aggregate function.  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 SELECT 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>
-
-     <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) > 1;
-	</programlisting>
-
-	and get:
-
-	<programlisting>
- SNO | SNAME | COUNT
------+-------+-------
-  1  | Smith |   2
-  3  | Adams |   2
-  4  | Blake |   3
-	</programlisting>
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Subqueries</title>
-
-     <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 > (SELECT PRICE FROM PART
-                   WHERE PNAME='Screw');
-	</programlisting>
-       </para>
-
-       <para>
-	The result is:
-
-	<programlisting>
- PNO |  PNAME  |  PRICE
------+---------+--------
-  3  |  Bolt   |   15
-  4  |  Cam    |   25
-	</programlisting>
-       </para>
-
-       <para>
-	When we look at the above query we can see
-	the keyword SELECT two times. The first one at the beginning of the
-	query - we will refer to it as outer SELECT - and the one in the WHERE
-	clause which begins a nested query - we will refer to it as inner
-	SELECT. For every tuple of the outer SELECT the inner SELECT 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 SELECT within
-	the WHERE clause of the inner SELECT. 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 SELECT. 
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Subqueries in FROM</title>
-
-     <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 can't 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>
-
-     <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:
-
-	<programlisting>
- SNO | SNAME |  CITY
------+-------+--------
-  2  | Jones | Paris
-  3  | Adams | Vienna
-	</programlisting>
-       </para>
-
-       <para>
-	Here is an example for INTERSECT:
-
-	<programlisting>
-SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNO > 1
-INTERSECT
-    SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNO < 3;
-	</programlisting>
-
-	gives the result:
-
-	<programlisting>
- SNO | SNAME |  CITY
------+-------+--------
-  2  | Jones | Paris
-	</programlisting>
-
-	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 > 1
-EXCEPT
-    SELECT S.SNO, S.SNAME, S.CITY
-    FROM SUPPLIER S
-    WHERE S.SNO > 3;
-	</programlisting>
-
-	gives the result:
-
-	<programlisting>
- SNO | SNAME |  CITY
------+-------+--------
-  2  | Jones | Paris
-  3  | Adams | Vienna
-	</programlisting>
-       </para>
-      </example>
-     </para>
-    </sect3>
-   </sect2>
-
-   <sect2 id="datadef">
-    <title>Data Definition</title>
-
-    <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>
-
-     <para>
-      The most fundamental command for data definition is the
-      one that creates a new relation (a new table). The syntax of the
-      CREATE TABLE 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>
-
-     <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>
-	 CHAR(<replaceable class="parameter">n</replaceable>):
-	 fixed length character string of length
-	 <replaceable class="parameter">n</replaceable>.
-	</para>
-       </listitem>
-
-       <listitem>
-	<para>
-	 VARCHAR(<replaceable class="parameter">n</replaceable>):
-	 varying length character string of maximum length
-	 <replaceable class="parameter">n</replaceable>.
-	</para>
-       </listitem>
-      </itemizedlist>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Create Index</title>
-
-     <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 CREATE INDEX 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 SELECT and decreases in speed of updates.
-       </para>
-      </example>
-     </para>
-    </sect3>
-
-    <sect3>
-     <title>Create View</title>
-
-     <para>
-      A view may 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:
-
-      <programlisting>
- SNAME | PNAME
--------+-------
- Smith | Screw                 
-      </programlisting>
-     </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>
-
-     <para>
-      To destroy a table (including all tuples stored in that table) the
-      DROP TABLE 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 DROP INDEX 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 DROP VIEW:
-
-      <programlisting>
-DROP VIEW <replaceable class="parameter">view_name</replaceable>;
-      </programlisting>
-     </para>
-    </sect3>
-   </sect2>
-
-   <sect2>
-    <title>Data Manipulation</title>
-
-    <sect3>
-     <title>Insert Into</title>
-
-     <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>
-
-     <para>
-      To change one or more attribute values of tuples in a relation the
-      UPDATE 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>
-
-     <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>
-
-    <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="DATE94" endterm="DATE94">.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Embedded <acronym>SQL</acronym></title>
-
-    <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 FETCH 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="DATE94" endterm="DATE94">,
-     or
-     <xref linkend="ULL88" endterm="ULL88">.
-    </para>
-   </sect2>
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/standalone-install.sgml b/doc/src/sgml/standalone-install.sgml
deleted file mode 100644
index 2e657acb93a..00000000000
--- a/doc/src/sgml/standalone-install.sgml
+++ /dev/null
@@ -1,42 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/standalone-install.sgml,v 2.3 2001/09/21 18:37:05 petere Exp $ -->
-
-<!--
-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 V3.1//EN" [
-
-<!entity % version SYSTEM "version.sgml">
-%version;
-
-<!--
-The standalone version has some portions that are different from the
-version that is integrated into the Administrator's Guide, 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 Administrator's Guide, you want to flip the
-IGNORE and INCLUDE.
--->
-]>
diff --git a/doc/src/sgml/start.sgml b/doc/src/sgml/start.sgml
deleted file mode 100644
index 439f65e98f0..00000000000
--- a/doc/src/sgml/start.sgml
+++ /dev/null
@@ -1,420 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/start.sgml,v 1.22 2002/01/20 22:19:56 petere Exp $
--->
-
- <chapter id="tutorial-start">
-  <title>Getting Started</title>
-
-  <sect1 id="tutorial-install">
-   <title>Installation</title>
-
-   <para>
-    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>.
-   </para>
-
-   <para>
-    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.
-   </para>
-
-   <para>
-    If you are installing <productname>PostgreSQL</productname>
-    yourself, then refer to the <citetitle>Administrator's
-    Guide</citetitle> 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.
-   </para>
-
-   <para>
-    If your site administrator has not set things up in the default
-    way, you may 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> may 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>
-
-   <para>
-    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.
-   </para>
-
-   <para>
-    In database jargon, <productname>PostgreSQL</productname> uses a
-    client/server model.  A <productname>PostgreSQL</productname>
-    session consists of the following cooperating processes
-    (programs):
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       A server process, which manages the database files, accepts
-       connections to the database from client applications, and
-       performs actions on the database on behalf of the clients.  The
-       database server program is called
-       <filename>postmaster</filename>.
-       <indexterm><primary>postmaster</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:  They 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
-       <productname>PostgreSQL</productname> distribution, most are
-       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>
-    The <productname>PostgreSQL</productname> server can handle
-    multiple concurrent connections from clients.  For that purpose 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>postmaster</filename> process.  Thus, the
-    <filename>postmaster</filename> 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.)
-   </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>
-
-   <para>
-    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.
-   </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 this 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>
-    This should produce as response:
-<screen>
-CREATE DATABASE
-</screen>
-    If so, 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>
-    then <productname>PostgreSQL</> was not installed properly.  Either it was not
-    installed at all or the search path was not set correctly.  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 back in the installation instructions to
-    correct the situation.
-   </para>
-
-   <para>
-    Another response could be this:
-<screen>
-psql: could not connect to server: Connection refused
-        Is the server running locally and accepting
-        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
-createdb: database creation failed
-</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>
-    If you do not have the privileges required to create a database,
-    you will see the following:
-<screen>
-ERROR:  CREATE DATABASE: permission denied
-createdb: database creation failed
-</screen>
-    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.
-
-    <footnote>
-     <para>
-      As an explanation for why this works:
-      <productname>PostgreSQL</productname> user names are separate
-      from operating system user accounts.  If 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.
-     </para>
-    </footnote>
-   </para>
-
-   <para>
-    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 31 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
-<screen>
-<prompt>$</prompt> <userinput>createdb</userinput>
-</screen>
-   </para>
-
-   <para>
-    If you don't 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>
-  </sect1>
-
-
-  <sect1 id="tutorial-accessdb">
-   <title>Accessing a Database</title>
-
-   <indexterm zone="tutorial-accessdb">
-    <primary>psql</primary>
-   </indexterm>
-
-   <para>
-    Once you have created a database, you can access it by:
-
-    <itemizedlist spacing="compact" mark="bullet">
-     <listitem>
-      <para>
-       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.
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       Using an existing graphical frontend tool like
-       <application>PgAccess</application> or
-       <application>ApplixWare</application> (via
-       <acronym>ODBC</acronym>) 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 <citetitle>The PostgreSQL Programmer's
-       Guide</citetitle>.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    You probably want to start up <command>psql</command>, to try out
-    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 leave off the database name then it will default to your
-    user account name.  You already discovered this scheme in the
-    previous section.
-   </para>
-
-   <para>
-    In <command>psql</command>, you will be greeted with the following
-    message:
-<screen>
-Welcome to psql, the PostgreSQL interactive terminal.
- 
-Type:  \copyright for distribution terms
-       \h for help with SQL commands
-       \? for help on internal slash commands
-       \g or terminate with semicolon to execute query
-       \q to quit
- 
-mydb=&gt;
-</screen>
-    <indexterm><primary>superuser</primary></indexterm>
-    The last line could also be
-<screen>
-mydb=#
-</screen>
-    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 purpose of this tutorial this is not of
-    importance.
-   </para>
-
-   <para>
-    If you have encountered problems starting <command>psql</command>
-    then go back to the previous section.  The diagnostics of
-    <command>psql</command> and <command>createdb</command> are
-    similar, and if the latter worked the former should work as well.
-   </para>
-
-   <para>
-    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 7.2devel on i586-pc-linux-gnu, compiled by GCC 2.96
-(1 row)
-
-<prompt>mydb=&gt;</prompt> <userinput>SELECT current_date;</userinput>
-    date
-------------
- 2001-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>.  Some of these
-    commands were listed in the welcome message.  For example,
-    you can get help on the syntax of various
-    <productname>PostgreSQL</productname> <acronym>SQL</acronym>
-    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 the
-    <citetitle>Reference Manual</citetitle>.  If <productname>PostgreSQL</> is
-    installed correctly you can also type <literal>man psql</literal>
-    at the operating system shell prompt to see the documentation.  In
-    this tutorial we will not use these features explicitly, but you
-    can use them yourself when you see fit.
-   </para>
-
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/stylesheet.css b/doc/src/sgml/stylesheet.css
deleted file mode 100644
index 2dacf601323..00000000000
--- a/doc/src/sgml/stylesheet.css
+++ /dev/null
@@ -1,59 +0,0 @@
-/* $Header: /cvsroot/pgsql/doc/src/sgml/stylesheet.css,v 1.3 2002/03/11 05:02:04 petere Exp $ */
-
-/* color scheme similar to www.postgresql.org */
-
-BODY {
-	color: #000000;
-	background: #FFFFFF;
-}
-
-A:link		{ color: #000066; }
-A:visited	{ color: #000099; }
-A:active	{ color: #FF0000; }
-
-/* center titles */
-
-BODY.BOOK H1.TITLE, BODY.SET H1.TITLE {
-	text-align: center;
-	font-size: 250%;
-	font-family: sans-serif;
-	color: #020167;
-}
-
-BODY.BOOK H3.CORPAUTHOR, BODY.SET H3.CORPAUTHOR {
-	text-align: center;
-	font-style: italic;
-	font-weight: normal;
-}
-
-BODY.BOOK .COPYRIGHT, BODY.SET .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 */
-
-.SET .TOC DL DT, .BOOK .TOC DL DT {
-	padding-top: 1.5ex;
-	padding-bottom: 1.5ex;
-}
-
-.SET .TOC DL DL DT, .BOOK .TOC DL DL DT {
-	padding-top: 0ex;
-	padding-bottom: 0ex;
-}
-
-/* miscellaneous */
-
-.NAVHEADER TH	{ font-style: italic; }
-.COMMENT	{ color: red; }
diff --git a/doc/src/sgml/stylesheet.dsl b/doc/src/sgml/stylesheet.dsl
deleted file mode 100644
index 44b6c0399d6..00000000000
--- a/doc/src/sgml/stylesheet.dsl
+++ /dev/null
@@ -1,623 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/stylesheet.dsl,v 1.20 2002/06/01 20:56:00 petere Exp $ -->
-<!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 pgsql-docs-list "pgsql-docs@postgresql.org")
-
-;; 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)
-
-;; Don't show comments.  (We ought to show them, at least during the
-;; development stage.)
-(define %show-comments%         #f)
-
-;; 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 envar ($mono-seq$))
-(element lineannotation ($italic-seq$))
-(element structfield ($mono-seq$))
-(element structname ($mono-seq$))
-(element symbol ($mono-seq$))
-(element type ($mono-seq$))
-
-;; Indentation of verbatim environments
-(define %indent-programlisting-lines% "    ")
-(define %indent-screen-lines% "    ")
-(define %indent-synopsis-lines% "    ")
-
-
-;; 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)))
-
-  (element pagenums
-    (make sequence
-      (literal "p. ")
-      (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...
-
-
-<!-- HTML output customization ..................................... -->
-
-<![ %output-html; [
-
-(define %section-autolabel%     #t)
-(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")
-
-;; Returns the depth of auto TOC that should be made at the nd-level
-(define (toc-depth nd)
-  (cond ((string=? (gi nd) (normalize "book")) 3)
-	((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)))
-
-;; Put date of creation into HTML header
-(define %html-header-tags% 
-  (list (list "META" '("NAME" "creation") (list "CONTENT" (time->string (time) #t)))))
-
-;; Create an index
-(define html-index #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))))
-
-]]> <!-- %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)
-
-
-;; 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/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml
deleted file mode 100644
index fb727a8433c..00000000000
--- a/doc/src/sgml/syntax.sgml
+++ /dev/null
@@ -1,1503 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/syntax.sgml,v 1.63 2002/06/15 22:15:03 tgl Exp $
--->
-
-<chapter id="sql-syntax">
- <title>SQL Syntax</title>
-
- <indexterm zone="sql-syntax">
-  <primary>syntax</primary>
-  <secondary>SQL</secondary>
- </indexterm>
-
-  <abstract>
-   <para>
-    This chapter describes the syntax of SQL.
-   </para>
-  </abstract>
-
- <sect1 id="sql-syntax-lexical">
-  <title>Lexical Structure</title>
-
-  <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>
-   Additionally, <firstterm>comments</firstterm> can occur in SQL
-   input.  They are not tokens, they are effectively equivalent to
-   whitespace.
-  </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>
-   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 the
-   <citetitle>Reference Manual</citetitle>.
-  </para>
-
-  <sect2 id="sql-syntax-identifiers">
-   <title>Identifiers and Key Words</title>
-
-   <indexterm zone="sql-syntax-identifiers">
-    <primary>identifiers</primary>
-   </indexterm>
-
-   <indexterm zone="sql-syntax-identifiers">
-    <primary>key words</primary>
-    <secondary>syntax</secondary>
-   </indexterm>
-
-   <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, digits
-    (<literal>0</literal>-<literal>9</literal>), or underscores,
-    although the SQL standard will not define a key word that contains
-    digits or starts or ends with an underscore.
-   </para>
-
-   <para>
-    The system uses no more than <symbol>NAMEDATALEN</symbol>-1
-    characters of an identifier; longer names can be written in
-    commands, but they will be truncated.  By default,
-    <symbol>NAMEDATALEN</symbol> is 32 so the maximum identifier length
-    is 31 (but at the time the system is built,
-    <symbol>NAMEDATALEN</symbol> can be changed in
-    <filename>src/include/postgres_ext.h</filename>).
-   </para>
-
-   <para>
-    <indexterm>
-     <primary>case sensitivity</primary>
-     <secondary>SQL commands</secondary>
-    </indexterm>
-    Identifier and key word names 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>quotes</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 other than a double
-    quote itself.  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>
-
-   <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
-    <productname>PostgreSQL</productname>, but <literal>"Foo"</literal>
-    and <literal>"FOO"</literal> are different from these three and
-    each other.
-    <footnote>
-     <para>
-      The folding of unquoted names to lower case in <productname>PostgreSQL</>
-      is 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>
-    </footnote>
-   </para>
-  </sect2>
-
-
-  <sect2 id="sql-syntax-constants">
-   <title>Constants</title>
-
-   <indexterm zone="sql-syntax-constants">
-    <primary>constants</primary>
-   </indexterm>
-
-   <para>
-    There are four kinds of <firstterm>implicitly-typed
-    constants</firstterm> in <productname>PostgreSQL</productname>:
-    strings, bit strings, integers, and floating-point numbers.
-    Constants can also be specified with explicit types, which can
-    enable more accurate representation and more efficient handling by
-    the system. The implicit constants are described below; explicit
-    constants are discussed afterwards.
-   </para>
-
-   <sect3 id="sql-syntax-strings">
-    <title>String Constants</title>
-
-    <indexterm zone="sql-syntax-strings">
-     <primary>character strings</primary>
-     <secondary>constants</secondary>
-    </indexterm>
-
-    <para>
-     <indexterm>
-      <primary>quotes</primary>
-      <secondary>escaping</secondary>
-     </indexterm>
-     A string constant in SQL is an arbitrary sequence of characters
-     bounded by single quotes (<quote>'</quote>), e.g., <literal>'This
-     is a string'</literal>.  SQL allows single quotes to be embedded
-     in strings by typing two adjacent single quotes (e.g.,
-     <literal>'Dianne''s horse'</literal>).  In
-     <productname>PostgreSQL</productname> single quotes may
-     alternatively be escaped with a backslash (<quote>\</quote>,
-     e.g., <literal>'Dianne\'s horse'</literal>).
-    </para>
-
-    <para>
-     C-style backslash escapes are also available:
-     <literal>\b</literal> is a backspace, <literal>\f</literal> is a
-     form feed, <literal>\n</literal> is a newline,
-     <literal>\r</literal> is a carriage return, <literal>\t</literal>
-     is a tab, and <literal>\<replaceable>xxx</replaceable></literal>,
-     where <replaceable>xxx</replaceable> is an octal number, is the
-     character with the corresponding ASCII code.  Any other character
-     following a backslash is taken literally.  Thus, to include a
-     backslash in a string constant, type two backslashes.
-    </para>
-
-    <para>
-     The character with the code zero cannot be in a string constant.
-    </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 in 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, and <productname>PostgreSQL</productname> is
-      consistent with <acronym>SQL9x</acronym> in this regard.
-    </para>
-   </sect3>
-
-   <sect3 id="sql-syntax-bit-strings">
-    <title>Bit-String Constants</title>
-
-    <indexterm zone="sql-syntax-bit-strings">
-     <primary>bit strings</primary>
-     <secondary>constants</secondary>
-    </indexterm>
-
-    <para>
-     Bit-string constants look like 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>.  Bit-string constants can be continued
-     across lines in the same way as regular string constants.
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Integer Constants</title>
-
-    <para>
-     Integer constants in SQL are sequences of decimal digits (0
-     though 9) with no decimal point and no exponent.  The range of legal values
-     depends on which integer data type is used, but the plain
-     <type>integer</type> type accepts values ranging from -2147483648
-     to +2147483647.  (The optional plus or minus sign is actually a
-     separate unary operator and not part of the integer constant.)
-    </para>
-   </sect3>
-
-   <sect3>
-    <title>Floating-Point Constants</title>
-
-    <indexterm>
-     <primary>floating point</primary>
-     <secondary>constants</secondary>
-    </indexterm>
-
-    <para>
-     Floating-point constants are accepted in these general forms:
-<synopsis>
-<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.  At least one digit must be before or after the decimal
-     point. At least one digit must follow the exponent delimiter
-      (<literal>e</literal>) if that field is present.
-     Thus, a floating-point constant is distinguished from an integer
-     constant by the presence of either the decimal point or the
-     exponent clause (or both).  There must not be a space or other
-     characters embedded in the constant.
-    </para>
-
-    <para>
-     These are some examples of valid floating-point constants:
-<literallayout>
-3.5
-4.
-.001
-5e2
-1.925e-3
-</literallayout>
-    </para>
-
-    <para>
-     Floating-point constants are of type <type>DOUBLE
-     PRECISION</type>. <type>REAL</type> can be specified explicitly
-     by using <acronym>SQL</acronym> string notation or
-     <productname>PostgreSQL</productname> type notation:
-
-<programlisting>
-REAL '1.23'  -- string style
-'1.23'::REAL -- PostgreSQL (historical) style
-</programlisting>
-     </para>
-    </sect3>
-
-   <sect3 id="sql-syntax-constants-generic">
-    <title>Constants of Other Types</title>
-
-    <indexterm>
-     <primary>data types</primary>
-     <secondary>constants</secondary>
-    </indexterm>
-
-    <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'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 may be omitted if there is no ambiguity as to the type the
-     constant must be (for example, when it is passed as an argument
-     to a non-overloaded function), in which case it is automatically
-     coerced.
-    </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 may 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">.  But the form
-     <replaceable>type</replaceable> '<replaceable>string</replaceable>'
-     can only be used to specify the type of a literal constant.
-     Another restriction on
-     <replaceable>type</replaceable> '<replaceable>string</replaceable>'
-     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>
-   </sect3>
-
-   <sect3>
-    <title>Array constants</title>
-
-    <indexterm>
-     <primary>arrays</primary>
-     <secondary>constants</secondary>
-    </indexterm>
-
-    <para>
-     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.  (For all built-in types, this is the comma character
-     <quote><literal>,</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>
-     Individual array elements can be placed between double-quote
-     marks (<literal>"</literal>) <!-- " --> to avoid ambiguity
-     problems with respect to whitespace.  Without quote marks, the
-     array-value parser will skip leading whitespace.
-    </para>
-
-    <para>
-     (Array constants are actually only a special case of the generic
-     type constants discussed in the previous section.  The constant
-     is initially treated as a string and passed to the array input
-     conversion routine.  An explicit type specification might be
-     necessary.)
-    </para>
-   </sect3>
-  </sect2>
-
-
-  <sect2 id="sql-syntax-operators">
-   <title>Operators</title>
-
-   <indexterm zone="sql-syntax-operators">
-    <primary>operators</primary>
-    <secondary>syntax</secondary>
-   </indexterm>
-
-   <para>
-    An operator is a sequence of up to <symbol>NAMEDATALEN</symbol>-1
-    (31 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>$</> (dollar) cannot be a single-character operator, although it
-       can be part of a multiple-character operator name.
-      </para>
-     </listitem>
-
-     <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
-       <productname>PostgreSQL</productname> to parse SQL-compliant
-       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
-    <productname>PostgreSQL</productname> reads it as two operator names
-    not one.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Special Characters</title>
-
-  <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 the positional parameters in the body of a function
-      definition.  In other contexts the dollar sign may be part of an
-      operator name.
-     </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>) has a special meaning when
-      used in the <command>SELECT</command> command or with the
-      <function>COUNT</function> aggregate function.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      The period (<literal>.</literal>) is used in floating-point
-      constants, and to separate table and column names.
-     </para>
-    </listitem>
-   </itemizedlist>
-
-   </para>
-  </sect2>
-
-  <sect2 id="sql-syntax-comments">
-   <title>Comments</title>
-
-   <indexterm zone="sql-syntax-comments">
-    <primary>comments</primary>
-    <secondary>in SQL</secondary>
-   </indexterm>
-
-   <para>
-    A comment is an arbitrary sequence of characters beginning with
-    double dashes and extending to the end of the line, e.g.:
-<programlisting>
--- This is a standard SQL92 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 SQL99 but unlike C, so that one can
-    comment out larger blocks of code that may 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>Lexical Precedence</title>
-
-   <indexterm zone="sql-precedence">
-    <primary>operators</primary>
-    <secondary>precedence</secondary>
-   </indexterm>
-
-   <para>
-    The precedence and associativity of the operators is hard-wired
-    into the parser.  Most operators have the same precedence and are
-    left-associative.  This may 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 -- until it is too late -- 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 tocentry="1">
-    <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>
-       <entry><productname>PostgreSQL</productname>-style typecast</entry>
-      </row>
-
-      <row>
-       <entry><token>[</token> <token>]</token></entry>
-       <entry>left</entry>
-       <entry>array element selection</entry>
-      </row>
-
-      <row>
-       <entry><token>-</token></entry>
-       <entry>right</entry>
-       <entry>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>test for TRUE, FALSE, UNKNOWN, NULL</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>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></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>
-  </sect2>
- </sect1>
-
- <sect1 id="sql-naming">
-  <title>Schemas and naming conventions</title>
-
-     <indexterm>
-      <primary>schemas</primary>
-     </indexterm>
-
-     <indexterm>
-      <primary>search path</primary>
-     </indexterm>
-
-     <indexterm>
-      <primary>namespaces</primary>
-     </indexterm>
-
-   <para>
-    A <productname>PostgreSQL</productname> database cluster (installation)
-    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 datatypes, functions, and operators.  The same
-    object name can be used in different schemas without conflict; for
-    example, both <literal>schema1</> and <literal>myschema</> may
-    contain tables named <literal>mytable</>.  Unlike databases, schemas
-    are not rigidly separated: a user may access objects in any of the
-    schemas in the database he is connected to, if he has privileges
-    to do so.
-   </para>
-
-     <indexterm>
-      <primary>qualified names</primary>
-     </indexterm>
-
-     <indexterm>
-      <primary>names</primary>
-      <secondary>qualified</secondary>
-     </indexterm>
-
-   <para>
-    To name a table precisely, write a <firstterm>qualified name</> consisting
-    of the schema name and table name separated by a dot:
-<synopsis>
-    <replaceable>schema</><literal>.</><replaceable>table</>
-</synopsis>
-    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 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>
-
-     <indexterm>
-      <primary>unqualified names</primary>
-     </indexterm>
-
-     <indexterm>
-      <primary>names</primary>
-      <secondary>unqualified</secondary>
-     </indexterm>
-
-   <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>
-
-   <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>
-
-   <para>
-    The search path works in the same way for datatype names, function names,
-    and operator names as it does for table names.  Datatype 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>
-
-   <para>
-    The standard search path in <productname>PostgreSQL</productname>
-    contains first the schema having the same name as the session user
-    (if it exists), and second the schema named <literal>public</>
-    (if it exists, which it does by default).  This arrangement allows
-    a flexible combination of private and shared tables.  If no per-user
-    schemas are created then all user tables will exist in the shared
-    <literal>public</> schema, providing behavior that is backwards-compatible
-    with pre-7.3 <productname>PostgreSQL</productname> releases.
-   </para>
-
-   <note>
-    <para>
-     There is no concept of a <literal>public</> schema in the SQL standard.
-     To achieve closest conformance to the standard, the DBA should
-     create per-user schemas for every user, and not use (perhaps even
-     remove) the <literal>public</> schema.
-    </para>
-   </note>
-
-   <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 datatypes, 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 may 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>
-
-  <sect2 id="sql-reserved-names">
-   <title>Reserved names</title>
-
-     <indexterm>
-      <primary>reserved names</primary>
-     </indexterm>
-
-     <indexterm>
-      <primary>names</primary>
-      <secondary>reserved</secondary>
-     </indexterm>
-
-    <para>
-     There are several restrictions on the names that can be chosen for
-     user-defined database objects.  These restrictions vary depending
-     on the kind of object.  (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.)
-    </para>
-
-    <para>
-     Schema names beginning with <literal>pg_</> are reserved for system
-     purposes and may not be created by users.
-    </para>
-
-    <para>
-     In <productname>PostgreSQL</productname> versions before 7.3, table
-     names beginning with <literal>pg_</> were reserved.  This is no longer
-     true: you may 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 catalog named the same as your table.  (With the
-     default search path, an unqualified reference to your table name
-     would be resolved as the system catalog instead.)  System catalogs 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>
-
-    <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:
-
-     <indexterm>
-      <primary>columns</primary>
-      <secondary>system columns</secondary>
-     </indexterm>
-
-     <variablelist>
-      <varlistentry>
-       <term><structfield>oid</></term>
-       <listitem>
-	<para>
-	 <indexterm>
-	  <primary>OID</primary>
-	 </indexterm>
-	 The object identifier (object ID) of a row.  This is a serial number
-	 that is automatically added by <productname>PostgreSQL</productname> to all table rows (unless
-	 the table was created WITHOUT OIDS, in which case this column is
-	 not present).  See <xref linkend="datatype-oid"> for more info.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-      <term><structfield>tableoid</></term>
-       <listitem>
-	<para>
-	 The OID of the table containing this row.  This attribute is
-	 particularly handy for queries that select from inheritance
-	 hierarchies, 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
-	 <classname>pg_class</classname> to obtain the table name.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term><structfield>xmin</></term>
-       <listitem>
-	<para>
-	 The identity (transaction ID) of the inserting transaction for
-	 this tuple.  (Note: A tuple is an individual state of a row;
-	 each update of a row creates a new tuple for the same logical row.)
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-      <term><structfield>cmin</></term>
-       <listitem>
-	<para>
-	 The command identifier (starting at zero) within the inserting
-	 transaction.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-      <term><structfield>xmax</></term>
-       <listitem>
-	<para>
-	 The identity (transaction ID) of the deleting transaction,
-	 or zero for an undeleted tuple.  It is possible for this field
-	 to be nonzero in a visible tuple: 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>
-	<para>
-	 The command identifier within the deleting transaction, or zero.
-	</para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-      <term><structfield>ctid</></term>
-       <listitem>
-	<para>
-	 The physical location of the tuple within its table.
-	 Note that although the <structfield>ctid</structfield>
-	 can be used to locate the tuple very quickly, a row's
-	 <structfield>ctid</structfield> will change each time 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>
-       </listitem>
-      </varlistentry>
-     </variablelist>
-    </para>
-  </sect2>
- </sect1>
-
- <sect1 id="sql-expressions">
-  <title>Value Expressions</title>
-
-  <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; see <xref linkend="sql-syntax-constants">.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A column reference.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A positional parameter reference, in the body of a function declaration.
-     </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 type cast.
-     </para>
-    </listitem>
-
-    <listitem>
-     <para>
-      A scalar subquery.
-     </para>
-    </listitem>
-
-    <listitem>
-<synopsis>( <replaceable>expression</replaceable> )</synopsis>
-     <para>
-      Parentheses are used to group subexpressions and override precedence.
-     </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>
-
-   <para>
-    A column can be referenced in the form:
-<synopsis>
-<replaceable>correlation</replaceable>.<replaceable>columnname</replaceable> `['<replaceable>subscript</replaceable>`]'
-</synopsis>
-
-    <replaceable>correlation</replaceable> is the name of a
-    table (possibly qualified), or an alias for a table defined by means of a
-    FROM clause, or 
-    the key words <literal>NEW</literal> or <literal>OLD</literal>.
-    (NEW and OLD can only appear in the action portion of a rule,
-    while other correlation names can be used in any SQL statement.)
-    The correlation name and separating dot may be omitted if the column name
-    is unique 
-    across all the tables being used in the current query.  If
-    <replaceable>column</replaceable> is of an array type, then the
-    optional <replaceable>subscript</replaceable> selects a specific
-    element or elements in the array.  If no subscript is provided, then the
-    whole array is selected.  (See <xref linkend="arrays"> for more about
-    arrays.)
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Positional Parameters</title>
-
-   <para>
-    A positional parameter reference is used to indicate a parameter
-    in an SQL function.  Typically this is used in SQL function
-    definition statements.  The form of a parameter 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> will be replaced by the first
-    function argument when the function is invoked.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Operator Invocations</title>
-
-   <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
-    keywords <token>AND</token>, <token>OR</token>, and
-    <token>NOT</token>, or is a qualified operator name
-<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>
-
-   <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</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 may be added by the user.
-   </para>
-  </sect2>
-
-  <sect2 id="syntax-aggregates">
-   <title>Aggregate Expressions</title>
-
-   <indexterm zone="syntax-aggregates">
-    <primary>aggregate functions</primary>
-   </indexterm>
-
-   <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:
-
-    <simplelist>
-     <member><replaceable>aggregate_name</replaceable> (<replaceable>expression</replaceable>)</member>
-     <member><replaceable>aggregate_name</replaceable> (ALL <replaceable>expression</replaceable>)</member>
-     <member><replaceable>aggregate_name</replaceable> (DISTINCT <replaceable>expression</replaceable>)</member>
-     <member><replaceable>aggregate_name</replaceable> ( * )</member>
-    </simplelist>
-
-    where <replaceable>aggregate_name</replaceable> is a previously
-    defined aggregate (possibly a qualified name), and
-    <replaceable>expression</replaceable> is 
-    any value expression that does not itself contain an aggregate
-    expression.
-   </para>
-
-   <para>
-    The first form of aggregate expression invokes the aggregate
-    across all input rows for which the given expression yields a
-    non-NULL value.  (Actually, it is up to the aggregate function
-    whether to ignore NULLs or not --- but all the standard ones do.)
-    The second form is the same as the first, since
-    <literal>ALL</literal> is the default.  The third form invokes the
-    aggregate for all distinct non-NULL values of the expression found
-    in the input rows.  The last form invokes the aggregate once for
-    each input row regardless of NULL or non-NULL values; since no
-    particular input value is specified, it is generally only useful
-    for the <function>count()</function> aggregate function.
-   </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;
-    <literal>count(distinct f1)</literal> yields the number of
-    distinct non-NULL values of <literal>f1</literal>.
-   </para>
-
-   <para>
-    The predefined aggregate functions are described in <xref
-    linkend="functions-aggregate">.  Other aggregate functions may be added
-    by the user. 
-   </para>
-  </sect2>
-
-  <sect2 id="sql-syntax-type-casts">
-   <title>Type Casts</title>
-
-    <indexterm>
-     <primary>data types</primary>
-     <secondary>type casts</secondary>
-    </indexterm>
-
-   <para>
-    A type cast specifies a conversion from one data type to another.
-    <productname>PostgreSQL</productname> accepts two equivalent syntaxes
-    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 SQL92; the syntax with
-    <literal>::</literal> is historical <productname>PostgreSQL</productname>
-    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 function is available.  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 may 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
-    cast functions that are marked <quote>okay to apply implicitly</>
-    in the system catalogs.  Other cast functions 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>
-    can't 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 in new applications.
-   </para>
-  </sect2>
-
-  <sect2>
-   <title>Scalar Subqueries</title>
-
-   <para>
-    A scalar subquery is an ordinary
-    <command>SELECT</command> in parentheses that returns exactly one
-    row with one column.  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">.
-   </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>
-   <title>Expression Evaluation</title>
-
-   <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 WHERE and HAVING clauses,
-    since those clauses are extensively reprocessed as part of
-    developing an execution plan.  Boolean
-    expressions (AND/OR/NOT combinations) in those clauses may be reorganized
-    in any manner allowed by the laws of Boolean algebra.
-   </para>
-
-   <para>
-    When it is essential to force evaluation order, a CASE construct may
-    be used.  For example, this is an untrustworthy way of trying to
-    avoid division by zero in a WHERE clause:
-<programlisting>
-SELECT ... WHERE x &lt;&gt; 0 AND y/x &gt; 1.5;
-</programlisting>
-    but this is safe:
-<programlisting>
-SELECT ... WHERE CASE WHEN x &lt;&gt; 0 THEN y/x &gt; 1.5 ELSE false END;
-</programlisting>
-    A CASE construct used in this fashion will defeat optimization attempts,
-    so it should only be done when necessary.
-   </para>
-  </sect2>
- </sect1>
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
deleted file mode 100644
index 5456f4d0cdb..00000000000
--- a/doc/src/sgml/trigger.sgml
+++ /dev/null
@@ -1,635 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/trigger.sgml,v 1.23 2002/04/19 16:36:08 tgl Exp $
--->
-
- <chapter id="triggers">
-  <title>Triggers</title>
-
-  <para>
-   <productname>PostgreSQL</productname> has various server-side function
-   interfaces. Server-side functions can be written in SQL, PL/pgSQL,
-   Tcl, or C. Trigger functions can be written in any of these
-   languages except SQL. Note that statement-level trigger events are not
-   supported in the current version. You can currently specify BEFORE or
-   AFTER on INSERT, DELETE or UPDATE of a tuple as a trigger event.
-  </para>
-
-  <sect1 id="trigger-definition">
-   <title>Trigger Definition</title>
-
-   <para>
-    If a trigger event occurs, the trigger manager (called by the Executor)
-    sets up a TriggerData information structure (described below) and calls
-    the trigger function to handle the event.
-   </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>opaque</>.
-    (The trigger function receives its input through a TriggerData
-    structure, not in the form of ordinary function arguments.)
-    If the function is written in C, it must use the <quote>version 1</>
-    function manager interface.
-   </para>
-
-   <para>
-    The syntax for creating triggers is:
-
-    <programlisting>
-CREATE TRIGGER <replaceable>trigger</replaceable> [ BEFORE | AFTER ] [ INSERT | DELETE | UPDATE [ OR ... ] ]
-    ON <replaceable>relation</replaceable> FOR EACH [ ROW | STATEMENT ]
-    EXECUTE PROCEDURE <replaceable>procedure</replaceable>
-     (<replaceable>args</replaceable>);
-    </programlisting>
-
-    where the arguments are:
-
-    <variablelist>
-     <varlistentry>
-      <term>
-       <replaceable>trigger</replaceable>
-      </term>
-      <listitem>
-       <para>
-        The trigger must have a name distinct from all other triggers on
-	the same table.  The name is needed
-	if you ever have to delete the trigger.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>BEFORE</term>
-      <term>AFTER</term>
-      <listitem>
-       <para>
-	Determines whether the function is called before or after
-	the event.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>INSERT</term>
-      <term>DELETE</term>
-      <term>UPDATE</term>
-      <listitem>
-       <para>
-	The next element of the command determines what event(s) will trigger
-	the function.  Multiple events can be specified separated by OR.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>relation</replaceable></term>
-      <listitem>
-       <para>
-	The relation name indicates which table the event applies to.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>ROW</term>
-      <term>STATEMENT</term>
-      <listitem>
-       <para>
-	The FOR EACH clause determines whether the trigger is fired for each
-	affected row or before (or after) the entire statement has completed.
-	Currently only the ROW case is supported.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>procedure</replaceable></term>
-      <listitem>
-       <para>
-	The procedure name is the function to be called.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term><replaceable>args</replaceable></term>
-      <listitem>
-       <para>
-	The arguments passed to the function in the TriggerData structure.
-	This is either empty or a list of one or more simple literal
-	constants (which will be passed to the function as strings).
-       </para>
-
-       <para>
-	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 field names and puts the
-	current user in one and the current timestamp 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 INSERT events on any table with suitable fields,
-	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 UPDATE trigger.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-
-   <para>
-    Trigger functions return a HeapTuple to the calling Executor.  The return
-    value is ignored for triggers fired AFTER an operation,
-    but it allows BEFORE triggers to:
-
-    <itemizedlist>
-     <listitem>
-      <para>
-       Return NULL to skip the operation for the current tuple (and so the
-       tuple will not be inserted/updated/deleted).
-      </para>
-     </listitem>
-
-     <listitem>
-      <para>
-       For INSERT and UPDATE triggers only, the returned tuple becomes the
-       tuple which will be inserted or will replace the tuple being updated.
-       This allows the trigger function to modify the row being inserted or
-       updated.
-      </para>
-     </listitem>
-    </itemizedlist>
-
-    A BEFORE trigger that does not intend to cause either of these behaviors
-    must be careful to return the same NEW tuple it is passed.
-   </para>
-
-   <para>
-    Note that there is no initialization performed by the CREATE TRIGGER
-    handler.  This may be changed in the future.
-   </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 name.  In the case of BEFORE triggers,
-    the possibly-modified tuple returned by each trigger becomes the input
-    to the next trigger.  If any BEFORE trigger returns NULL, the operation
-    is abandoned and subsequent triggers are not fired.
-   </para>
-
-   <para>
-    If a trigger function executes SQL-queries (using SPI) then these queries
-    may 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 recursive invocation of the same trigger --- for
-    example, an INSERT trigger might execute a query that inserts an
-    additional tuple into the same table, causing the INSERT trigger to be
-    fired again.  It is the trigger programmer's
-    responsibility to avoid infinite recursion in such scenarios.
-   </para>
-  </sect1>
-
-  <sect1 id="trigger-manager">
-   <title>Interaction with the Trigger Manager</title>
-
-   <para>
-    This section describes the low-level details of the interface to a
-    trigger function.  This information is only needed when writing a
-    trigger function in C.  If you are using a higher-level function
-    language then these details are handled for you.
-   </para>
-
-    <note>
-     <para>
-      The interface described here applies for
-      <productname>PostgreSQL</productname> 7.1 and later.
-      Earlier versions passed the TriggerData pointer in a global
-      variable CurrentTriggerData.
-     </para>
-    </note>
-
-   <para>
-    When a function is called by the trigger manager, it is not passed any
-    normal parameters, but it is passed a <quote>context</> pointer pointing to a
-    TriggerData structure.  C functions can check whether they were called
-    from the trigger manager or not by executing the macro
-    <literal>CALLED_AS_TRIGGER(fcinfo)</literal>, which expands to
-    <programlisting>
-        ((fcinfo)->context != NULL && IsA((fcinfo)->context, TriggerData))
-    </programlisting>
-    If this returns TRUE, then it is safe to cast fcinfo->context to type
-    <literal>TriggerData *</literal> and make use of the pointed-to
-    TriggerData structure.
-    The function must <emphasis>not</emphasis> alter the 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;
-} TriggerData;
-</programlisting>
-
-    where the members are defined as follows:
-
-    <variablelist>
-     <varlistentry>
-      <term>type</term>
-      <listitem>
-       <para>
-        Always <literal>T_TriggerData</literal> if this is a trigger event.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>tg_event</term>
-      <listitem>
-       <para>
-	describes the event for which the function is called. You may use the
-	following macros to examine <literal>tg_event</literal>:
-
-	<variablelist>
-	 <varlistentry>
-	  <term>TRIGGER_FIRED_BEFORE(tg_event)</term>
-	  <listitem>
-	   <para>
-	    returns TRUE if trigger fired BEFORE.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>TRIGGER_FIRED_AFTER(tg_event)</term>
-	  <listitem>
-	   <para>
-	    Returns TRUE if trigger fired AFTER.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>TRIGGER_FIRED_FOR_ROW(event)</term>
-	  <listitem>
-	   <para>
-	    Returns TRUE if trigger fired for
-	    a ROW-level event.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>TRIGGER_FIRED_FOR_STATEMENT(event)</term>
-	  <listitem>
-	   <para>
-	    Returns TRUE if trigger fired for
-	    STATEMENT-level event.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>TRIGGER_FIRED_BY_INSERT(event)</term>
-	  <listitem>
-	   <para>
-	    Returns TRUE if trigger fired by INSERT.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>TRIGGER_FIRED_BY_DELETE(event)</term>
-	  <listitem>
-	   <para>
-	    Returns TRUE if trigger fired by DELETE.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-
-	 <varlistentry>
-	  <term>TRIGGER_FIRED_BY_UPDATE(event)</term>
-	  <listitem>
-	   <para>
-	    Returns TRUE if trigger fired by UPDATE.
-	   </para>
-	  </listitem>
-	 </varlistentry>
-	</variablelist>
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>tg_relation</term>
-      <listitem>
-       <para>
-	is a pointer to structure describing the triggered relation. Look at
-	src/include/utils/rel.h for details about this structure.  The most
-	interesting things are tg_relation->rd_att (descriptor of the relation
-	tuples) and tg_relation->rd_rel->relname (relation's name. This is not
-	char*, but NameData.  Use SPI_getrelname(tg_relation) to get char* if
-	you need a copy of name).
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>tg_trigtuple</term>
-      <listitem>
-       <para>
-	is a pointer to the tuple for which the trigger is fired. This is the tuple
-	being inserted (if INSERT), deleted (if DELETE) or updated (if UPDATE).
-	If INSERT/DELETE then this is what you are to return to Executor if 
-	you don't want to replace tuple with another one (INSERT) or skip the
-	operation.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>tg_newtuple</term>
-      <listitem>
-       <para>
-	is a pointer to the new version of tuple if UPDATE and NULL if this is
-	for an INSERT or a DELETE. This is what you are to return to Executor if
-	UPDATE and you don't want to replace this tuple with another one or skip
-	the operation.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>tg_trigger</term>
-      <listitem>
-       <para>
-	is pointer to structure Trigger defined in src/include/utils/rel.h:
-
-	<programlisting>
-typedef struct Trigger
-{
-    Oid         tgoid;
-    char       *tgname;
-    Oid         tgfoid;
-    int16       tgtype;
-    bool        tgenabled;
-    bool        tgisconstraint;
-    Oid         tgconstrrelid;
-    bool        tgdeferrable;
-    bool        tginitdeferred;
-    int16       tgnargs;
-    int16       tgattr[FUNC_MAX_ARGS];
-    char      **tgargs;
-} Trigger;
-	</programlisting>
-
-	where
-	tgname is the trigger's name, tgnargs is number of arguments in tgargs,
-	tgargs is an array of pointers to the arguments specified in the CREATE
-	TRIGGER statement. Other members are for internal use only.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-   </para>
-  </sect1>
-
-  <sect1 id="trigger-datachanges">
-   <title>Visibility of Data Changes</title>
-
-   <para>
-    <productname>PostgreSQL</productname> data changes visibility rule: during a query execution, data
-    changes made by the query itself (via SQL-function, SPI-function, triggers)
-    are invisible to the query scan.  For example, in query
-
-    <programlisting>
-INSERT INTO a SELECT * FROM a;
-    </programlisting>
-
-    tuples inserted are invisible for SELECT scan.  In effect, this
-    duplicates the database table within itself (subject to unique index
-    rules, of course) without recursing.
-   </para>
-
-   <para>
-    But keep in mind this notice about visibility in the SPI documentation:
-
-    <blockquote>
-     <para>
-Changes made by query Q are visible by queries that are started after
-query Q, no matter whether they are started inside Q (during the
-execution of Q) or after Q is done.
-     </para>
-    </blockquote>
-   </para>
-
-   <para>
-    This is true for triggers as well so, though a tuple being inserted
-    (tg_trigtuple) is not visible to queries in a BEFORE trigger, this tuple
-    (just inserted) is visible to queries in an AFTER trigger, and to queries
-    in BEFORE/AFTER triggers fired after this!
-   </para>
-  </sect1>
-
-  <sect1 id="trigger-examples">
-   <title>Examples</title>
-
-   <para>
-    There are more complex examples in
-    <filename>src/test/regress/regress.c</filename> and
-    in <filename>contrib/spi</filename>.
-   </para>
-
-   <para>
-    Here is a very simple example of trigger usage.  Function trigf reports
-    the number of tuples in the triggered relation ttest and skips the
-    operation if the query attempts to insert NULL into x (i.e - it acts as a
-    NOT NULL constraint but doesn't abort the transaction).
-
-    <programlisting>
-#include "executor/spi.h"	/* this is what you need to work with SPI */
-#include "commands/trigger.h"	/* -"- and triggers */
-
-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 trigdata is pointing at what I expect */
-	if (!CALLED_AS_TRIGGER(fcinfo))
-		elog(ERROR, "trigf: not fired 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 NULLs ? */
-	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(INFO, "trigf (fired %s): SPI_connect returned %d", when, ret);
-	
-	/* Get number of tuples in relation */
-	ret = SPI_exec("SELECT count(*) FROM ttest", 0);
-	
-	if (ret < 0)
-		elog(NOTICE, "trigf (fired %s): SPI_exec returned %d", when, ret);
-
-	/* count(*) returns int8 as of PG 7.2, so be careful to convert */
-	i = (int) DatumGetInt64(SPI_getbinval(SPI_tuptable->vals[0],
-					      SPI_tuptable->tupdesc,
-					      1,
-					      &amp;isnull));
-	
-	elog (NOTICE, "trigf (fired %s): there are %d tuples in ttest", when, i);
-	
-	SPI_finish();
-	
-	if (checknull)
-	{
-		(void) SPI_getbinval(rettuple, tupdesc, 1, &amp;isnull);
-		if (isnull)
-			rettuple = NULL;
-	}
-
-	return PointerGetDatum(rettuple);
-}
-    </programlisting>
-   </para>
-
-   <para>
-    Now, compile and create the trigger function:
-
-    <programlisting>
-CREATE FUNCTION trigf () RETURNS OPAQUE AS 
-'...path_to_so' LANGUAGE 'C';
-
-CREATE TABLE ttest (x int4);
-    </programlisting>
-
-    <programlisting>
-vac=> CREATE TRIGGER tbefore BEFORE INSERT OR UPDATE OR DELETE ON ttest 
-FOR EACH ROW EXECUTE PROCEDURE trigf();
-CREATE
-vac=> CREATE TRIGGER tafter AFTER INSERT OR UPDATE OR DELETE ON ttest 
-FOR EACH ROW EXECUTE PROCEDURE trigf();
-CREATE
-vac=> INSERT INTO ttest VALUES (NULL);
-WARNING:  trigf (fired before): there are 0 tuples in ttest
-INSERT 0 0
-
--- Insertion skipped and AFTER trigger is not fired
-
-vac=> SELECT * FROM ttest;
-x
--
-(0 rows)
-
-vac=> INSERT INTO ttest VALUES (1);
-INFO:  trigf (fired before): there are 0 tuples in ttest
-INFO:  trigf (fired after ): there are 1 tuples in ttest
-                                       ^^^^^^^^
-                             remember what we said about visibility.
-INSERT 167793 1
-vac=> SELECT * FROM ttest;
-x
--
-1
-(1 row)
-
-vac=> INSERT INTO ttest SELECT x * 2 FROM ttest;
-INFO:  trigf (fired before): there are 1 tuples in ttest
-INFO:  trigf (fired after ): there are 2 tuples in ttest
-                                       ^^^^^^^^
-                             remember what we said about visibility.
-INSERT 167794 1
-vac=> SELECT * FROM ttest;
-x
--
-1
-2
-(2 rows)
-
-vac=> UPDATE ttest SET x = null WHERE x = 2;
-INFO:  trigf (fired before): there are 2 tuples in ttest
-UPDATE 0
-vac=> UPDATE ttest SET x = 4 WHERE x = 2;
-INFO:  trigf (fired before): there are 2 tuples in ttest
-INFO:  trigf (fired after ): there are 2 tuples in ttest
-UPDATE 1
-vac=> SELECT * FROM ttest;
-x
--
-1
-4
-(2 rows)
-
-vac=> DELETE FROM ttest;
-INFO:  trigf (fired before): there are 2 tuples in ttest
-INFO:  trigf (fired after ): there are 1 tuples in ttest
-INFO:  trigf (fired before): there are 1 tuples in ttest
-INFO:  trigf (fired after ): there are 0 tuples in ttest
-                                       ^^^^^^^^
-                             remember what we said about visibility.
-DELETE 2
-vac=> SELECT * FROM ttest;
-x
--
-(0 rows)
-    </programlisting>
-
-   </para>
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/tutorial.sgml b/doc/src/sgml/tutorial.sgml
deleted file mode 100644
index 812fb9d3904..00000000000
--- a/doc/src/sgml/tutorial.sgml
+++ /dev/null
@@ -1,72 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/tutorial.sgml,v 1.15 2001/09/02 23:27:49 petere Exp $
--->
-
-<book id="tutorial">
-
- <title>PostgreSQL &version; Tutorial</title>
- <bookinfo>
-  <corpauthor>The PostgreSQL Global Development Group</corpauthor>
-  &legal;
- </bookinfo>
-
- <preface id="tutorial-welcome">
-  <title>Welcome</title>
-
-  <para>
-   Welcome to <productname>PostgreSQL</productname> and the
-   <citetitle>PostgreSQL Tutorial</citetitle>.  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.
-  </para>
-
-  <para>
-   After you have worked through this tutorial you might want to move on
-   to reading the <![%single-book;[<citetitle>User's
-   Guide</citetitle>]]><![%set-of-books;[<xref linkend="user">]]> to
-   gain a more formal knowledge of the SQL language, or the
-   <![%single-book;[<citetitle>Programmer's
-   Guide</citetitle>]]><![%set-of-books;[<xref linkend="programmer">]]>
-   for information about developing applications for
-   <productname>PostgreSQL</productname>.
-  </para>
-
-  <para>
-   We hope you have a pleasant experience with
-   <productname>PostgreSQL</productname>.
-  </para>
- </preface>
-
-<![%single-book;[
-  &intro;
-]]>
-  &start;
-  &query;
-  &advanced;
-<![%single-book;[
-  &biblio;
-  &bookindex;
-]]>
-
-</book>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/typeconv.sgml b/doc/src/sgml/typeconv.sgml
deleted file mode 100644
index 58427d205de..00000000000
--- a/doc/src/sgml/typeconv.sgml
+++ /dev/null
@@ -1,903 +0,0 @@
-<chapter Id="typeconv">
-<title>Type Conversion</title>
-
- <sect1 id="typeconv-intro">
-  <title>Introduction</title>
-
-<para>
-<acronym>SQL</acronym> queries can, intentionally or not, require
-mixing of different data types in the same expression. 
-<productname>PostgreSQL</productname> has extensive facilities for
-evaluating mixed-type expressions.
-</para>
-
-<para>
-In many cases a user will not need
-to understand the details of the type conversion mechanism.
-However, the implicit conversions done by <productname>PostgreSQL</productname>
-can affect the results of a query.  When necessary, these results
-can be tailored by a user or programmer
-using <emphasis>explicit</emphasis> type coercion.
-</para>
-
-<para>
-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.
-</para>
-
-<para>
-The <citetitle>Programmer's Guide</citetitle> has more details on the exact algorithms used for
-implicit type conversion and coercion.
-</para>
- </sect1>
-
-<sect1 id="typeconv-overview">
-<title>Overview</title>
-
-<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
-much more general and flexible than other <acronym>RDBMS</acronym> implementations.
-Hence, most type conversion behavior in <productname>PostgreSQL</productname>
-should be governed by general rules rather than by <foreignphrase>ad hoc</> heuristics, to allow
-mixed-type expressions to be meaningful even with user-defined types.
-</para>
-
-<para>
-The <productname>PostgreSQL</productname> scanner/parser decodes lexical
-elements into only five fundamental categories: integers, floating-point numbers, strings,
-names, and key words.  Most extended types are first tokenized into
-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
-
-<screen>
-tgl=> 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
-<firstterm>unknown</firstterm> is assigned initially, to be resolved in later
-stages as described below.
-</para>
-
-<para>
-There are four fundamental <acronym>SQL</acronym> constructs requiring
-distinct type conversion rules in the <productname>PostgreSQL</productname>
-parser:
-</para>
-
-<variablelist>
-<varlistentry>
-<term>
-Operators
-</term>
-<listitem>
-<para>
-<productname>PostgreSQL</productname> allows expressions with
-prefix and postfix unary (one-argument) operators,
-as well as binary (two-argument) operators.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-Function calls
-</term>
-<listitem>
-<para>
-Much of the <productname>PostgreSQL</productname> type system is built around a
-rich set of functions. Function calls have one or more arguments which, for
-any specific query, must be matched to the functions available in the system
-catalog.  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>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-Query targets
-</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 query must be matched up
-with, and perhaps converted to, the types of the target columns.
-</para>
-</listitem>
-</varlistentry>
-<varlistentry>
-<term>
-<literal>UNION</literal> and <literal>CASE</literal> constructs
-</term>
-<listitem>
-<para>
-Since all select results from a unionized <literal>SELECT</literal> statement must appear in a single
-set of columns, the types of the results
-of each <literal>SELECT</> clause must be matched up and converted to a uniform set.
-Similarly, the result expressions of a <literal>CASE</> construct must be coerced to
-a common type so that the <literal>CASE</> expression as a whole has a known output type.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
-
-<para>
-Many of the general type conversion rules use simple conventions built on
-the <productname>PostgreSQL</productname> function and operator system tables.
-There are some heuristics included in the conversion rules to better support
-conventions for the <acronym>SQL</acronym> standard native types such as
-<type>smallint</type>, <type>integer</type>, and <type>real</type>.
-</para>
-
-<para>
-The <productname>PostgreSQL</productname> parser uses the convention that all
-type conversion functions take a single argument of the source type and are
-named with the same name as the target type. Any function meeting these
-criteria is considered to be a valid conversion function, and may be used
-by the parser as such. This simple assumption gives the parser the power
-to explore type conversion possibilities without hardcoding, allowing
-extended user-defined types to use these same features transparently.
-</para>
-
-<para>
-An additional heuristic is provided in the parser to allow better guesses
-at proper behavior for <acronym>SQL</acronym> standard types. There are
-several basic <firstterm>type categories</firstterm> defined: <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. Each category, with the exception of user-defined, has
-a <firstterm>preferred type</firstterm> which is preferentially selected
-when there is ambiguity.
-In the user-defined category, each type is its own preferred type.
-Ambiguous expressions (those with multiple candidate parsing solutions)
-can often be resolved when there are multiple possible built-in types, but
-they will raise an error when there are multiple choices for user-defined
-types.
-</para>
-
-<para>
-All type conversion rules are designed with several principles in mind:
-
-<itemizedlist mark="bullet" spacing="compact">
-<listitem>
-<para>
-Implicit conversions should never have surprising or unpredictable outcomes.
-</para>
-</listitem>
-
-<listitem>
-<para>
-User-defined types, of which the parser has no <foreignphrase>a priori</> knowledge, should be
-<quote>higher</quote> in the type hierarchy. In mixed-type expressions, native types shall always
-be converted to a user-defined type (of course, only if conversion is necessary).
-</para>
-</listitem>
-
-<listitem>
-<para>
-User-defined types are not related. Currently, <productname>PostgreSQL</productname>
-does not have information available to it on relationships between types, other than
-hardcoded heuristics for built-in types and implicit relationships based on available functions
-in the catalog.
-</para>
-</listitem>
-
-<listitem>
-<para>
-There should be no extra overhead from the parser or executor
-if a query does not need implicit type conversion.
-That is, if a query is well formulated and the types already match up, then the query should proceed
-without spending extra time in the parser and without introducing unnecessary implicit conversion
-functions into the query.
-</para>
-
-<para>
-Additionally, if a query usually requires an implicit conversion for a function, and
-if then the user defines an explicit function with the correct argument types, the parser
-should use this new function and will no longer do the implicit conversion using the old function.
-</para>
-</listitem>
-</itemizedlist>
-</para>
-
-</sect1>
-
-<sect1 id="typeconv-oper">
-<title>Operators</title>
-
-  <para>
-   The operand types of an operator invocation are resolved following
-   the procedure below.  Note that this procedure is indirectly affected
-   by the precedence of the involved operators.  See <xref
-   linkend="sql-precedence"> for more information.
-  </para>
-
-<procedure>
-<title>Operand Type Resolution</title>
-
-<step performance="required">
-<para>
-Select the operators to be considered from the
-<classname>pg_operator</classname> system catalog.  If an unqualified
-operator name is used (the usual case), the operators
-considered are those of the right name and argument count that are
-visible in the current search path (see <xref linkend="sql-naming">).
-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 of identical argument types,
-only the one appearing earliest in the path is considered.  But operators of
-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 is <type>unknown</type> type,
-then assume it is the same type as the other argument for this check.
-Other cases involving <type>unknown</type> 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 coerced (using an implicit coercion function) to match.
-<type>unknown</type> literals are
-assumed to be coercible 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.  Keep all candidates if none have any 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 with the most exact or
-binary-compatible matches on input types.  Keep all candidates if none have
-any exact or binary-compatible 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 at
-the most positions where type coercion 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 <quote>unknown</quote>, check the type
-categories accepted at those argument positions by the remaining
-candidates.  At each position, select the "string" category if any
-candidate accepts that category (this bias towards string is appropriate
-since an unknown-type literal does look 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.  Also note whether any of the candidates accept a
-preferred data type within the selected category. Now discard operator
-candidates that do not accept the selected type category; furthermore,
-if any candidate accepts a preferred type at a given argument position,
-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>
-
-<bridgehead renderas="sect2">Examples</bridgehead>
-
-<example>
-<title>Exponentiation Operator Type Resolution</title>
-
-<para>
-There is only one exponentiation
-operator defined in the catalog, and it takes arguments of type 
-<type>double precision</type>.
-The scanner assigns an initial type of <type>integer</type> to both arguments
-of this query expression:
-<screen>
-tgl=> SELECT 2 ^ 3 AS "Exp";
- Exp
------
-   8
-(1 row)
-</screen>
-
-So the parser does a type conversion on both operands and the query
-is equivalent to
-
-<screen>
-tgl=> SELECT CAST(2 AS double precision) ^ CAST(3 AS double precision) AS "Exp";
- Exp
------
-   8
-(1 row)
-</screen>
-
-or
-
-<screen>
-tgl=> SELECT 2.0 ^ 3.0 AS "Exp";
- Exp
------
-   8
-(1 row)
-</screen>
-
-<note>
-<para>
-This last form has the least overhead, since no functions are called to do
-implicit type conversion. This is not an issue for small queries, but may
-have an impact on the performance of queries involving large tables.
-</para>
-</note>
-</para>
-</example>
-
-<example>
-<title>String Concatenation Operator Type Resolution</title>
-
-<para>
-A string-like syntax is used for working with string types as well as for
-working with complex extended types.
-Strings with unspecified type are matched with likely operator candidates.
-</para>
-
-<para>
-An example with one unspecified argument:
-<screen>
-tgl=> 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 of type <type>text</type>.
-</para>
-
-<para>
-Concatenation on unspecified types:
-<screen>
-tgl=> 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 
-<quote>preferred type</quote> for strings, <type>text</type>, is used as the specific
-type to resolve the unknown literals to.
-</para>
-</example>
-
-<example>
-<title>Absolute-Value and Factorial Operator Type Resolution</title>
-
-<para>
-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 a non-numeric input:
-<screen>
-tgl=> select @ text '-4.5' as "abs";
- abs
------
- 4.5
-(1 row)
-</screen>
-Here the system has performed an implicit text-to-float8 conversion
-before applying the chosen operator.  We can verify that float8 and
-not some other type was used:
-<screen>
-tgl=> select @ text '-4.5e500' as "abs";
-ERROR:  Input '-4.5e500' is out of range for float8
-</screen>
-</para>
-
-<para>
-On the other hand, the postfix operator <literal>!</> (factorial)
-is defined only for integer data types, not for float8.  So, if we
-try a similar case with <literal>!</>, we get:
-<screen>
-tgl=> select text '20' ! as "factorial";
-ERROR:  Unable to identify a postfix operator '!' for type 'text'
-        You may need to add parentheses or an explicit cast
-</screen>
-This happens because the system can't decide which of the several
-possible <literal>!</> operators should be preferred.  We can help
-it out with an explicit cast:
-<screen>
-tgl=> select cast(text '20' as int8) ! as "factorial";
-      factorial
----------------------
- 2432902008176640000
-(1 row)
-</screen>
-</para>
-</example>
-
-</sect1>
-
-<sect1 id="typeconv-func">
-<title>Functions</title>
-
-  <para>
-   The argument types of function calls are resolved according to the
-   following steps.
-  </para>
-
-<procedure>
-<title>Function Argument Type Resolution</title>
-
-<step performance="required">
-<para>
-Select the functions to be considered from the
-<classname>pg_proc</classname> system catalog.  If an unqualified
-function name is used, the functions
-considered are those of the right name and argument count that are
-visible in the current search path (see <xref linkend="sql-naming">).
-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.  But functions of
-different argument types are considered on an equal footing regardless of
-search path position.
-</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 whether the function call appears
-to be a trivial type coercion 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-compatible with the named
-data type.  When these conditions are met, the function argument is coerced
-to the named data type without any explicit function call.
-</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 coerced (using an implicit coercion function) to match.
-<type>unknown</type> literals are
-assumed to be coercible 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.  Keep all candidates if none have any 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 with the most exact or
-binary-compatible matches on input types.  Keep all candidates if none have
-any exact or binary-compatible 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 at
-the most positions where type coercion 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 does look 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.  Also note whether
-any of the candidates accept a preferred data type within the selected category.
-Now discard candidates that do not accept the selected type category;
-furthermore, if any candidate accepts a preferred type at a given argument
-position, 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>
-
-<bridgehead renderas="sect2">Examples</bridgehead>
-
-<example>
-<title>Factorial Function Argument Type Resolution</title>
-
-<para>
-There is only one <function>int4fac</function> function defined in the
-<classname>pg_proc</classname> catalog.
-So the following query automatically converts the <type>int2</type> argument
-to <type>int4</type>:
-
-<screen>
-tgl=> SELECT int4fac(int2 '4');
- int4fac
----------
-      24
-(1 row)
-</screen>
-
-and is actually transformed by the parser to
-<screen>
-tgl=> SELECT int4fac(int4(int2 '4'));
- int4fac
----------
-      24
-(1 row)
-</screen>
-</para>
-</example>
-
-<example>
-<title>Substring Function Type Resolution</title>
-
-<para>
-There are two <function>substr</function> functions declared in <classname>pg_proc</classname>. However,
-only one takes two arguments, of types <type>text</type> and <type>int4</type>.
-</para>
-
-<para>
-If called with a string constant of unspecified type, the type is matched up
-directly with the only candidate function type:
-<screen>
-tgl=> 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 coerce it to become <type>text</type>:
-<screen>
-tgl=> SELECT substr(varchar '1234', 3);
- substr
---------
-     34
-(1 row)
-</screen>
-which is transformed by the parser to become
-<screen>
-tgl=> SELECT substr(text(varchar '1234'), 3);
- substr
---------
-     34
-(1 row)
-</screen>
-</para>
-<para>
-<note>
-<para>
-Actually, the parser is aware that <type>text</type> and <type>varchar</type>
-are <firstterm>binary-compatible</>, meaning that one can be passed to a function that
-accepts the other without doing any physical conversion.  Therefore, no
-explicit type conversion call is really inserted in this case.
-</para>
-</note>
-</para>
-
-<para>
-And, if the function is called with an <type>int4</type>, the parser will
-try to convert that to <type>text</type>:
-<screen>
-tgl=> SELECT substr(1234, 3);
- substr
---------
-     34
-(1 row)
-</screen>
-which actually executes as
-<screen>
-tgl=> SELECT substr(text(1234), 3);
- substr
---------
-     34
-(1 row)
-</screen>
-This succeeds because there is a conversion function text(int4) in the
-system catalog.
-</para>
-</example>
-
-</sect1>
-
-<sect1 id="typeconv-query">
-<title>Query Targets</title>
-
-  <para>
-   Values to be inserted into a table are coerced to the destination
-   column's data type according to the
-   following steps.
-  </para>
-
-<procedure>
-<title>Query Target Type Resolution</title>
-
-<step performance="required">
-<para>
-Check for an exact match with the target.
-</para></step>
-<step performance="required">
-<para>
-Otherwise, try to coerce the expression to the target type.  This will succeed
-if the two types are known binary-compatible, or if there is a conversion
-function.  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>
-If the target is a fixed-length type (e.g. <type>char</type> or <type>varchar</type>
-declared with a length) then try to find a sizing function for the target
-type.  A sizing function is a function of the same name as the type,
-taking two arguments of which the first is that type and the second is an
-integer, and returning the same type.  If one is found, it is applied,
-passing the column's declared length as the second parameter.
-</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 query
-ensures that the target is sized correctly:
-
-<screen>
-tgl=> CREATE TABLE vv (v character(20));
-CREATE
-tgl=> INSERT INTO vv SELECT 'abc' || 'def';
-INSERT 392905 1
-tgl=> SELECT v, length(v) FROM vv;
-          v           | length
-----------------------+--------
- abcdef               |     20
-(1 row)
-</screen>
-
-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 coerced to <type>bpchar</type> (<quote>blank-padded
-char</>, the internal name of the character data type) to match the target
-column type.  (Since the parser knows that <type>text</type> and
-<type>bpchar</type> are binary-compatible, this coercion is implicit and does
-not insert any real function call.)  Finally, the sizing function
-<literal>bpchar(bpchar, integer)</literal> is found in the system catalogs
-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</> and <literal>CASE</> Constructs</title>
-
-<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</>.
-A <literal>CASE</> construct also uses the identical algorithm to match up its
-component expressions and select a result data type.
-</para>
-<procedure>
-<title><literal>UNION</> and <literal>CASE</> Type Resolution</title>
-
-<step performance="required">
-<para>
-If all inputs are of type <type>unknown</type>, resolve as type
-<type>text</type> (the preferred type for string category).
-Otherwise, ignore the <type>unknown</type> inputs while choosing the type.
-</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>
-If one or more non-unknown inputs are of a preferred type in that category,
-resolve as that type.
-</para></step>
-
-<step performance="required">
-<para>
-Otherwise, resolve as the type of the first non-unknown input.
-</para></step>
-
-<step performance="required">
-<para>
-Coerce all inputs to the selected type.
-</para></step>
-</procedure>
-
-<bridgehead renderas="sect2">Examples</bridgehead>
-
-<example>
-<title>Underspecified Types in a Union</title>
-
-<para>
-<screen>
-tgl=> 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 as type text.
-</para>
-</example>
-
-<example>
-<title>Type Conversion in a Simple Union</title>
-
-<para>
-<screen>
-tgl=> SELECT 1.2 AS "Double" UNION SELECT 1;
- Double
---------
-      1
-    1.2
-(2 rows)
-</screen>
-The literal <literal>1.2</> is of type <type>double precision</>,
-the preferred type in the numeric category, so that type is used.
-</para>
-</example>
-
-<example>
-<title>Type Conversion in a Transposed Union</title>
-
-<para>
-Here the output type of the union is forced to match the type of
-the first clause in the union:
-
-<screen>
-tgl=> SELECT 1 AS "All integers"
-tgl-> UNION SELECT CAST('2.2' AS REAL);
- All integers
---------------
-            1
-            2
-(2 rows)
-</screen>
-</para>
-<para>
-Since <type>REAL</type> is not a preferred type, the parser sees no reason
-to select it over <type>INTEGER</type> (which is what the 1 is), and instead
-falls back on the use-the-first-alternative rule.
-This example demonstrates that the preferred-type mechanism doesn't encode
-as much information as we'd like.  Future versions of
-<productname>PostgreSQL</productname> may support a more general notion of
-type preferences.
-</para>
-</example>
-
-</sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:t
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml
deleted file mode 100644
index 63517357ec3..00000000000
--- a/doc/src/sgml/user-manag.sgml
+++ /dev/null
@@ -1,212 +0,0 @@
-<Chapter id="user-manag">
- <title>Database Users and Permissions</title>
-
- <para>
-  Managing database users and their privileges is in concept similar
-  to managing users of a Unix operating system, but the details are not
-  identical.
- </para>
-
- <sect1 id="database-users">
-  <title>Database Users</title>
-
-  <para>
-   Database users are conceptually completely separate from
-   operating system users. In practice it might be convenient to
-   maintain a correspondence, but this is not required. Database user
-   names are global across a database cluster installation (and not
-   per individual database). To create a user use the <command>CREATE
-   USER</command> SQL command:
-<synopsis>
-CREATE USER <replaceable>name</replaceable>
-</synopsis>
-   <replaceable>name</replaceable> follows the rules for SQL
-   identifiers: either unadorned without special characters, or
-   double-quoted. To remove an existing user, use the analogous
-   <command>DROP USER</command> command.
-  </para>
-
-  <para>
-   For convenience, the shell scripts <filename>createuser</filename>
-   and <filename>dropuser</filename> are provided as wrappers around these SQL
-   commands.
-  </para>
-
-  <para>
-   In order to bootstrap the database system, a freshly initialized
-   system always contains one predefined user. This user will have the
-   fixed id 1, and by default (unless altered when running
-   <command>initdb</command>) it will have the same name as the
-   operating system user that initialized the area (and is presumably
-   being used as the user that runs the server). Customarily, this user
-   will be named <systemitem>postgres</systemitem>. In order to create more
-   users you first have to connect as this initial user.
-  </para>
-
-  <para>
-   The user 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 user to connect as. The set of
-   database users a given client connection may connect as is
-   determined by the client authentication setup, as explained in
-   <xref linkend="client-authentication">. (Thus, a client is not
-   necessarily limited to connect as the user with the same name as
-   its operating system user, in the same way a person is not
-   constrained in its login name by her real name.)
-  </para>
-
-  <sect2 id="user-attributes">
-   <title>User attributes</title>
-
-   <para>
-    A database user may have a number of attributes that define its
-    privileges and interact with the client authentication system.
-
-    <variablelist>
-     <varlistentry>
-      <term>superuser</term>
-      <listitem>
-       <para>
-        A database superuser bypasses all permission checks. Also,
-        only a superuser can create new users. To create a database
-        superuser, use <literal>CREATE USER name
-        CREATEUSER</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>database creation</term>
-      <listitem>
-       <para>
-        A user must be explicitly given permission to create databases
-        (except for superusers, since those bypass all permission
-        checks). To create such a user, use <literal>CREATE USER name
-        CREATEDB</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-
-     <varlistentry>
-      <term>password</term>
-      <listitem>
-       <para>
-        A password is only significant if password authentication is
-        used for client authentication. Database passwords are separate
-        from operating system passwords. Specify a password upon
-        user creation with <literal>CREATE USER name PASSWORD
-        'string'</literal>.
-       </para>
-      </listitem>
-     </varlistentry>
-    </variablelist>
-
-    A user's attributes can be modified after creation with
-    <command>ALTER USER</command>.
-    See the reference pages for <command>CREATE USER</command> and
-    <command>ALTER USER</command> for details.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="groups">
-  <title>Groups</title>
-
-  <para>
-   As in Unix, groups are a way of logically grouping users to ease
-   management of permissions: permissions can be granted to, or revoked
-   from, a group as a whole.  To create a group, use
-<synopsis>
-CREATE GROUP <replaceable>name</replaceable>
-</synopsis>
-   To add users to or remove users from a group, use
-<synopsis>
-ALTER GROUP <replaceable>name</replaceable> ADD USER <replaceable>uname1</replaceable>, ...
-ALTER GROUP <replaceable>name</replaceable> DROP USER <replaceable>uname1</replaceable>, ...
-</synopsis>
-  </para>
- </sect1>
-
- <sect1 id="privileges">
-  <title>Privileges</title>
-
-  <para>
-   When a database object is created, it is assigned an owner. The
-   owner is the user that executed the creation statement. There is
-   currently no polished interface for changing the owner of a database
-   object. By default, only an owner (or a superuser) can do anything
-   with the object. In order to allow other users to use it,
-   <firstterm>privileges</firstterm> must be granted.
-  </para>
-
-  <para>
-   There are several different privileges: <literal>SELECT</literal>
-   (read), <literal>INSERT</literal> (append), <literal>UPDATE</literal>
-   (write), <literal>DELETE</literal>, <literal>RULE</literal>,
-   <literal>REFERENCES</literal> (foreign key), and
-   <literal>TRIGGER</literal>. (See the <command>GRANT</command> manual
-   page for more detailed information.) The right to modify or destroy
-   an object is always the privilege of the owner only. To assign
-   privileges, the <command>GRANT</command> command is used. So, if
-   <literal>joe</literal> is an existing user, and
-   <literal>accounts</literal> is an existing table, write access can be
-   granted with
-<programlisting>
-GRANT UPDATE ON accounts TO joe;
-</programlisting>
-   The user executing this command must be the owner of the table. To
-   grant a privilege to a group, use
-<programlisting>
-GRANT SELECT ON accounts TO GROUP staff;
-</programlisting>
-   The special <quote>user</quote> name <literal>PUBLIC</literal> can
-   be used to grant a privilege to every user on the system. Writing
-   <literal>ALL</literal> in place of a specific privilege specifies that all
-   privileges will be granted.
-  </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 table 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 table owner can choose
-   to revoke his own ordinary privileges, for example to make a
-   table read-only for himself as well as others.
-  </para>
- </sect1>
-
- <sect1 id="perm-functions">
-  <title>Functions and Triggers</title>
-
-  <para>
-   Functions and triggers allow users to insert code into the backend
-   server that other users may execute without knowing it. Hence, both
-   mechanisms permit users to <firstterm>Trojan horse</firstterm>
-   others with relative impunity. The only real protection is tight
-   control over who can define functions (e.g., write to relations
-   with SQL fields) and triggers. Audit trails and alerters on the
-   system catalogs <literal>pg_class</literal>,
-   <literal>pg_shadow</literal> and <literal>pg_group</literal> are also
-   possible.
-  </para>
-
-  <para>
-   Functions written in any language except SQL run inside the backend
-   server process with the operating systems permissions of the
-   database server daemon process. It is possible to change the
-   server's internal data structures from inside of trusted functions.
-   Hence, among many other things, such functions can circumvent any
-   system access controls. This is an inherent problem with
-   user-defined C functions.
-  </para>
-
- </sect1>
-
-</Chapter>
diff --git a/doc/src/sgml/user.sgml b/doc/src/sgml/user.sgml
deleted file mode 100644
index 79ed594ff7e..00000000000
--- a/doc/src/sgml/user.sgml
+++ /dev/null
@@ -1,59 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/user.sgml,v 1.30 2002/06/15 02:59:55 thomas Exp $
--->
-
-<book id="user">
-
-<!-- Title information -->
-
- <title>PostgreSQL &version; User's Guide</title>
-
- <bookinfo>
-  <corpauthor>The PostgreSQL Global Development Group</corpauthor>
-  &legal;
- </bookinfo>
-
- &intro;
-
- &syntax;
- &queries;
- &datatype;
- &func;
- &typeconv;
- &array;
- &indices;
- &inherit;
- &mvcc;
- &manage;
- &perform;
-
- <!-- appendices -->
-
- &datetime;
- &keywords;
- &features;
-
- &biblio;
-
- <![%single-book;[
- &bookindex;
- ]]>
-
-</book>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/version.sgml b/doc/src/sgml/version.sgml
deleted file mode 100644
index 94f173eb49f..00000000000
--- a/doc/src/sgml/version.sgml
+++ /dev/null
@@ -1,7 +0,0 @@
-<!--
-Update this file to propagate correct current version numbers to the
-documentation.  In text, use for example &version; to refer to them.
--->
-
-<!entity version "7.3devel">
-<!entity majorversion "7.3">
diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml
deleted file mode 100644
index f080c6d9873..00000000000
--- a/doc/src/sgml/wal.sgml
+++ /dev/null
@@ -1,379 +0,0 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/wal.sgml,v 1.15 2002/02/11 23:25:14 momjian Exp $ -->
-
-<chapter id="wal">
- <title>Write-Ahead Logging (<acronym>WAL</acronym>)</title>
-
- <note>
-  <title>Author</title>
-  <para>
-   Vadim Mikheev and Oliver Elphick
-  </para>
- </note>
-
- <sect1 id="wal-general">
-  <title>General Description</Title>
-
-  <para>
-   <firstterm>Write Ahead Logging</firstterm> (<acronym>WAL</acronym>)
-   is a standard approach to transaction logging.  Its detailed
-   description may 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, when log records have been flushed to permanent
-   storage. When 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 will first be redone from the log records (this is
-   roll-forward recovery, also known as REDO) and then changes made by
-   uncommitted transactions will be removed from the data pages
-   (roll-backward recovery - UNDO).
-  </para>
-
-  <sect2 id="wal-benefits-now">
-   <title>Immediate Benefits of <acronym>WAL</acronym></title>
-
-   <para>
-    The first obvious benefit of using <acronym>WAL</acronym> is a
-    significantly reduced number of disk writes, since only the log
-    file needs to be flushed to disk at the time of transaction
-    commit; in multiuser environments, commits of many transactions
-    may be accomplished with a single <function>fsync()</function> of
-    the log file. Furthermore, 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.
-   </para>
-
-   <para>
-    The next benefit is consistency of the data pages. The truth is
-    that, before <acronym>WAL</acronym>,
-    <productname>PostgreSQL</productname> was never able to guarantee
-    consistency in the case of a crash.  Before
-    <acronym>WAL</acronym>, any crash during writing could result in:
-
-    <orderedlist>
-     <listitem>
-      <simpara>index tuples pointing to nonexistent table rows</simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>index tuples lost in split operations</simpara>
-     </listitem>
-
-     <listitem>
-      <simpara>totally corrupted table or index page content, because
-      of partially written data pages</simpara>
-     </listitem>
-    </orderedlist>
-
-    Problems with indexes (problems 1 and 2) could possibly have been
-    fixed by additional <function>fsync()</function> calls, but it is
-    not obvious how to handle the last case without
-    <acronym>WAL</acronym>; <acronym>WAL</acronym> saves the entire data
-    page content in the log if that is required to ensure page
-    consistency for after-crash recovery.
-   </para>
-  </sect2>
-  
-  <sect2 id="wal-benefits-later">
-   <title>Future Benefits</title>
-
-   <para>
-    In this first release of <acronym>WAL</acronym>, UNDO operation is
-    not implemented, because of lack of time. This means that changes
-    made by aborted transactions will still occupy disk space and that
-    we still need a permanent <filename>pg_clog</filename> file to hold
-    the status of transactions, since we are not able to re-use
-    transaction identifiers. Once UNDO is implemented,
-    <filename>pg_clog</filename> will no longer be required to be
-    permanent; it will be possible to remove
-    <filename>pg_clog</filename> at shutdown. (However, the urgency of
-    this concern has decreased greatly with the adoption of a segmented
-    storage method for <filename>pg_clog</filename> --- it is no longer
-    necessary to keep old <filename>pg_clog</filename> entries around
-    forever.)
-   </para>
-
-   <para>
-    With UNDO, it will also be possible to implement
-    <firstterm>savepoints</firstterm> to allow partial rollback of
-    invalid transaction operations (parser errors caused by mistyping
-    commands, insertion of duplicate primary/unique keys and so on)
-    with the ability to continue or commit valid operations made by
-    the transaction before the error.  At present, any error will
-    invalidate the whole transaction and require a transaction abort.
-   </para>
-
-   <para>
-    <acronym>WAL</acronym> offers the opportunity for a new method for
-    database on-line backup and restore (<acronym>BAR</acronym>).  To
-    use this method, one would have to make periodic saves of data
-    files to another disk, a tape or another host and also archive the
-    <acronym>WAL</acronym> log files.  The database file copy and the
-    archived log files could be used to restore just as if one were
-    restoring after a crash. Each time a new database file copy was
-    made the old log files could be removed.  Implementing this
-    facility will require the logging of data file and index creation
-    and deletion; it will also require development of a method for
-    copying the data files (operating system copy commands are not
-    suitable).
-   </para>
-
-   <para>
-    A difficulty standing in the way of realizing these benefits is that
-    they require saving <acronym>WAL</acronym> entries for considerable
-    periods of time (eg, as long as the longest possible transaction if
-    transaction UNDO is wanted). The present <acronym>WAL</acronym>
-    format is extremely bulky since it includes many disk page
-    snapshots. This is not a serious concern at present, since the
-    entries only need to be kept for one or two checkpoint intervals;
-    but to achieve these future benefits some sort of compressed
-    <acronym>WAL</acronym> format will be needed.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="wal-implementation">
-  <title>Implementation</title>
-
-  <para>
-   <acronym>WAL</acronym> is automatically enabled from release 7.1
-   onwards. No action is required from the administrator with the
-   exception of ensuring that the additional disk-space requirements
-   of 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><replaceable>$PGDATA</replaceable>/pg_xlog</Filename>, as
-   a set of segment files, each 16 MB in size.  Each segment is
-   divided into 8 kB pages. The log record headers are described in
-   <filename>access/xlog.h</filename>; 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>0000000000000000</filename>.  The numbers do not wrap, at
-   present, but it should take a very long time to exhaust the
-   available stock of numbers.
-  </para>
-
-  <para>
-   The <acronym>WAL</acronym> buffers and control structure are in
-   shared memory, and are handled by the backends; they are protected
-   by lightweight locks.  The demand on shared memory is dependent on the
-   number of buffers.  The default size of the <acronym>WAL</acronym>
-   buffers is 8 buffers of 8 kB each, or 64 kB total.
-  </para>
-
-  <para>
-   It is of advantage if the log is located on another disk than the
-   main database files.  This may be achieved by moving the directory,
-   <filename>pg_xlog</filename>, to another location (while the
-   postmaster is shut down, of course) and creating a symbolic link
-   from the original location in <replaceable>$PGDATA</replaceable> to
-   the new location.
-  </para>
-
-  <para>
-   The aim of <acronym>WAL</acronym>, to ensure that the log is
-   written before database records are altered, may be subverted by
-   disk drives 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 may still lead to
-   irrecoverable data corruption.  Administrators should try to ensure
-   that disks holding <productname>PostgreSQL</productname>'s
-   log files do not make such false reports.
-  </para>
-
-  <sect2 id="wal-recovery">
-   <title>Database Recovery with <acronym>WAL</acronym></title>
-
-   <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, when recovery is to be
-    done, the backend 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, all pages changed since
-    the checkpoint will be restored to a consistent state.
-   </para>
-
-   <para>
-    Using <filename>pg_control</filename> to get the checkpoint
-    position speeds up the recovery process, but to handle possible
-    corruption of <filename>pg_control</filename>, we should actually
-    implement the reading of existing log segments in reverse order --
-    newest to oldest -- in order to find the last checkpoint.  This has
-    not been implemented, yet.
-   </para>
-  </sect2>
- </sect1>
-
- <sect1 id="wal-configuration">
-  <title><acronym>WAL</acronym> Configuration</title>
-
-  <para>
-   There are several <acronym>WAL</acronym>-related parameters that
-   affect database performance. This section explains their use.
-   Consult <xref linkend="runtime-config"> for details about setting
-   configuration parameters.
-  </para>
-
-  <para>
-   There are two commonly used <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,
-   tuple 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 may
-   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 may
-   not occur often enough to prevent <acronym>WAL</acronym> buffers
-   being written by <function>LogInsert</function>. On such systems
-   one should increase the number of <acronym>WAL</acronym> buffers by
-   modifying the <filename>postgresql.conf</filename> <varname>
-   WAL_BUFFERS</varname> parameter. The default number of <acronym>
-   WAL</acronym> buffers is 8.  Increasing this value will 
-   correspondingly increase shared memory usage.
-  </para>
-
-  <para>
-   <firstterm>Checkpoints</firstterm> are points in the sequence of
-   transactions at which it is guaranteed that the data files have
-   been updated with all information logged 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. As result, in
-   the event of a crash, the recoverer knows from what record in the
-   log (known as the redo record) it should start the REDO operation,
-   since any changes made to data files before that record are already
-   on disk. After a checkpoint has been made, any log segments written
-   before the undo records are no longer needed and can be recycled or
-   removed. (When <acronym>WAL</acronym>-based <acronym>BAR</acronym> is
-   implemented, the log segments would be archived before being recycled
-   or removed.)
-  </para>
-
-  <para>
-   The checkpoint maker is also able to create a few log segments for
-   future use, so as to avoid the need for
-   <function>LogInsert</function> or <function>LogFlush</function> to
-   spend time in creating them.  (If that happens, the entire database
-   system will be delayed by the creation operation, so it's better if
-   the files can be created in the checkpoint maker, which is not on
-   anyone's critical path.)
-   By default a new 16MB segment file is created only if more than 75% of
-   the current segment has been used.  This is inadequate if the system
-   generates more than 4MB of log output between checkpoints.
-   One can instruct the server to pre-create up to 64 log segments
-   at checkpoint time by modifying the <varname>WAL_FILES</varname>
-   configuration parameter.
-  </para>
-
-  <para>
-   The postmaster spawns a special backend process every so often
-   to create the next checkpoint.  A checkpoint is created every
-   <varname>CHECKPOINT_SEGMENTS</varname> log segments, or every
-   <varname>CHECKPOINT_TIMEOUT</varname> seconds, whichever comes first.
-   The default settings are 3 segments and 300 seconds 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 be done
-   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. In addition,
-   to ensure data page consistency, the first modification of a data
-   page after each checkpoint results in logging the entire page
-   content. Thus a smaller checkpoint interval increases the volume of
-   output to the log, partially negating the goal of using a smaller
-   interval, and in any case causing more disk I/O.
-  </para>
-
-  <para>
-   The number of 16MB segment files will always be at least
-   <varname>WAL_FILES</varname> + 1, and will normally not exceed
-   <varname>WAL_FILES</varname> + MAX(<varname>WAL_FILES</varname>,
-   <varname>CHECKPOINT_SEGMENTS</varname>) + 1. This may be used to
-   estimate space requirements for WAL. Ordinarily, when an old log
-   segment files are no longer needed, they are recycled (renamed to
-   become the next sequential future segments). If, due to a short-term
-   peak of log output rate, there are more than
-   <varname>WAL_FILES</varname> + MAX(<varname>WAL_FILES</varname>,
-   <varname>CHECKPOINT_SEGMENTS</varname>) + 1 segment files, then
-   unneeded segment files will be deleted instead of recycled until the
-   system gets back under this limit. (If this happens on a regular
-   basis, <varname>WAL_FILES</varname> should be increased to avoid it.
-   Deleting log segments that will only have to be created again later
-   is expensive and pointless.)
-  </para>
-
-  <para>
-   The <varname>COMMIT_DELAY</varname> parameter defines for how many
-   microseconds the backend 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
-   backends 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 <varname>fsync</varname>
-   is not enabled or if fewer than <varname>COMMIT_SIBLINGS</varname>
-   other backends are not currently in active transactions; this avoids
-   sleeping when it's unlikely that any other backend 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 will have the same effect.
-   Good values for these parameters are not yet clear; experimentation
-   is encouraged.
-  </para>
-
-  <para>
-   The <varname>WAL_SYNC_METHOD</varname> parameter determines how
-   <productname>PostgreSQL</productname> will ask the kernel to force
-    WAL updates out to disk. 
-   All the options should be the same as far as reliability goes,
-   but it's quite platform-specific which one will be the fastest.
-   Note that this parameter is irrelevant if <varname>FSYNC</varname>
-   has been turned off.
-  </para>
-
-  <para>
-   Setting the <varname>WAL_DEBUG</varname> parameter to any nonzero
-   value will result in each <function>LogInsert</function> and
-   <function>LogFlush</function> <acronym>WAL</acronym> call being
-   logged to standard error.  At present, it makes no difference what
-   the nonzero value is.  This option may be replaced by a more
-   general mechanism in the future.
-  </para>
- </sect1>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/xaggr.sgml b/doc/src/sgml/xaggr.sgml
deleted file mode 100644
index e82406ec022..00000000000
--- a/doc/src/sgml/xaggr.sgml
+++ /dev/null
@@ -1,137 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/xaggr.sgml,v 1.16 2002/01/07 02:29:14 petere Exp $
--->
-
- <chapter id="xaggr">
-  <title>Extending <acronym>SQL</acronym>: Aggregates</title>
-
-  <indexterm zone="xaggr">
-   <primary>aggregate functions</primary>
-   <secondary>extending</secondary>
-  </indexterm>
-
-  <para>
-   Aggregate functions  in <productname>PostgreSQL</productname> 
-   are expressed as <firstterm>state values</firstterm>
-   and <firstterm>state transition functions</firstterm>.
-   That is,  an  aggregate  can  be
-   defined  in terms of state that is modified whenever an
-   input item 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 output of the aggregate
-   is different from the data that needs to be kept in the running
-   state value.
-  </para>
-
-  <para>
-   Thus, in addition to the input and result data types seen by a user
-   of the aggregate, there is an internal state-value data type that
-   may be different from both the input 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 is:
-   
-<programlisting>
-CREATE AGGREGATE complex_sum (
-    sfunc = complex_add,
-    basetype = complex,
-    stype = complex,
-    initcond = '(0,0)'
-);
-</programlisting>
-
-<screen>
-SELECT complex_sum(a) FROM test_complex;
-
- complex_sum
--------------
- (34,53.9)
-</screen>
-
-   (In practice, we'd just name the aggregate <function>sum</function>, and rely on
-   <productname>PostgreSQL</productname> to figure out which kind
-   of sum to apply to a column of type <type>complex</type>.)
-  </para>
-
-  <para>
-   The above definition of <function>sum</function> will return zero (the initial
-   state condition) if there are no non-null input values.
-   Perhaps we want to return NULL in that case instead --- 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's sufficient to insert the first non-null input value into
-   the state variable and then start applying the transition function
-   at the second non-null 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>
-  
-  <para>
-   Another bit of default behavior for a <quote>strict</> transition function
-   is that the previous state value is retained unchanged whenever a
-   NULL input value is encountered.  Thus, NULLs are ignored.  If you
-   need some other behavior for NULL inputs, just define your transition
-   function as non-strict, and code it to test for NULL inputs and 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 transition state value.  For example,
-   the built-in implementation of <function>avg(float8)</function>
-   looks like:
-
-<programlisting>
-CREATE AGGREGATE avg (
-    sfunc = float8_accum,
-    basetype = float8,
-    stype = float8[],
-    finalfunc = float8_avg,
-    initcond = '{0,0}'
-);
-</programlisting>
-  </para>
-
-  <para>
-   For further details see the description of the <command>CREATE
-   AGGREGATE</command> command in the <citetitle>Reference
-   Manual</citetitle>.
-  </para>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
deleted file mode 100644
index 6de67ebf30e..00000000000
--- a/doc/src/sgml/xfunc.sgml
+++ /dev/null
@@ -1,1887 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v 1.52 2002/06/20 16:57:00 momjian Exp $
--->
-
- <chapter id="xfunc">
-  <title id="xfunc-title">Extending <acronym>SQL</acronym>: Functions</title>
-
-  <indexterm zone="xfunc"><primary>function</></>
-
-  <sect1 id="xfunc-intro">
-   <title>Introduction</title>
-
-  <comment>
-   Historically, functions were perhaps considered a tool for creating
-   types.  Today, few people build their own types but many write
-   their own functions.  This introduction ought to be changed to
-   reflect this.
-  </comment>
-
-  <para>
-   As  it  turns  out,  part of defining a new type is the
-   definition of functions  that  describe  its  behavior.
-   Consequently,  while  it  is  possible  to define a new
-   function without defining a new type,  the  reverse  is
-   not  true.   We therefore describe how to add new functions 
-   to <productname>PostgreSQL</productname> before  describing  
-   how  to  add  new types.
-  </para>
-
-  <para>
-   <productname>PostgreSQL</productname> provides four kinds of
-   functions:
-
-   <itemizedlist>
-    <listitem>
-     <para>
-      query language functions 
-      (functions written in <acronym>SQL</acronym>)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      procedural language 
-      functions (functions written in, for example, <application>PL/Tcl</> or <application>PL/pgSQL</>)
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      internal functions
-     </para>
-    </listitem>
-    <listitem>
-     <para>
-      C language functions
-     </para>
-    </listitem>
-   </itemizedlist>
-  </para>
-
-  <para>
-   Every kind
-   of  function  can take a base type, a composite type, or
-   some combination as arguments (parameters).   In  addition, 
-   every kind of function can return a base type or
-   a composite type.  It's easiest to define <acronym>SQL</acronym> 
-   functions, so we'll start with those.  Examples in this section 
-   can also be found in <filename>funcs.sql</filename> 
-   and <filename>funcs.c</filename> in the tutorial directory.
-  </para>
-
-  <para>
-   Throughout this chapter, it can be useful to look at the reference
-   page of the <command>CREATE FUNCTION</command> command to
-   understand the examples better.
-  </para>
-  </sect1>
-
-  <sect1 id="xfunc-sql">
-   <title>Query Language (<acronym>SQL</acronym>) Functions</title>
-
-   <indexterm zone="xfunc-sql"><primary>function</><secondary>SQL</></>
-
-   <para>
-    SQL functions execute an arbitrary list of SQL statements, returning
-    the result of the last query in the list, which must be a
-    <literal>SELECT</>.
-    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, NULL will be returned.
-   </para>
-
-   <para>
-    <indexterm><primary>SETOF</><seealso>function</></>
-    Alternatively, an SQL function may be declared to return a set,
-    by specifying the function's return type
-    as <literal>SETOF</literal> <replaceable>sometype</>.  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 should be a list of one or more SQL
-    statements separated by semicolons.  Note that because the syntax
-    of the <command>CREATE FUNCTION</command> command requires the body of the
-    function to be enclosed in single quotes, single quote marks
-    (<literal>'</>) used
-    in the body of the function must be escaped, by writing two single
-    quotes (<literal>''</>) or a backslash (<literal>\'</>) where each
-    quote is desired.
-   </para>
-
-   <para>
-    Arguments to the SQL function may be referenced in the function
-    body using the syntax <literal>$<replaceable>n</></>: $1 refers to
-    the first argument, $2 to the second, and so on.  If an argument
-    is of a composite type, then the <quote>dot notation</quote>,
-    e.g., <literal>$1.emp</literal>, may be used to access attributes
-    of the argument.
-   </para>
-
-   <sect2>
-    <title>Examples</title>
-
-    <para>
-     To illustrate a simple SQL function, consider the following,
-     which might be used to debit a bank account:
-
-<programlisting>
-CREATE FUNCTION tp1 (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 tp1(17, 100.0);
-</programlisting>
-    </para>
-
-    <para>
-     In practice one would probably like a more useful result from the
-     function than a constant <quote>1</>, so a more likely definition
-     is
-
-<programlisting>
-CREATE FUNCTION tp1 (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.
-    </para>
-
-    <para>
-     Any collection of commands in the  <acronym>SQL</acronym>
-     language can be packaged together and defined as a function.
-     The commands can include data modification (i.e.,
-     <command>INSERT</command>, <command>UPDATE</command>, and
-     <command>DELETE</command>) as well
-     as <command>SELECT</command> queries.  However, the final command 
-     must be a <command>SELECT</command> that returns whatever is
-     specified as the function's return type.
-
-<programlisting>
-CREATE FUNCTION clean_EMP () RETURNS integer AS '
-    DELETE FROM EMP 
-        WHERE EMP.salary &lt;= 0;
-    SELECT 1 AS ignore_this;
-' LANGUAGE SQL;
-
-SELECT clean_EMP();
-</programlisting>
-
-<screen>
- x
----
- 1
-</screen>
-    </para>
-
-   </sect2>
-
-   <sect2>
-    <title><acronym>SQL</acronym> Functions on Base Types</title>
-
-    <para>
-     The simplest possible <acronym>SQL</acronym> function has no arguments and
-     simply returns a base type, such as <type>integer</type>:
-     
-<programlisting>
-CREATE FUNCTION one() RETURNS integer AS '
-    SELECT 1 as RESULT;
-' LANGUAGE SQL;
-
-SELECT one();
-</programlisting>
-
-<screen>
- 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</>:
-
-<programlisting>
-CREATE FUNCTION add_em(integer, integer) RETURNS integer AS '
-    SELECT $1 + $2;
-' LANGUAGE SQL;
-
-SELECT add_em(1, 2) AS answer;
-</programlisting>
-
-<screen>
- answer
---------
-      3
-</screen>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title><acronym>SQL</acronym> Functions on Composite Types</title>
-
-    <para>
-     When  specifying  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 attributes 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 your
-     salary would be if it were doubled:
-
-<programlisting>
-CREATE FUNCTION double_salary(EMP) RETURNS integer AS '
-    SELECT $1.salary * 2 AS salary;
-' LANGUAGE SQL;
-
-SELECT name, double_salary(EMP) AS dream
-    FROM EMP
-    WHERE EMP.cubicle ~= point '(2,1)';
-</programlisting>
-
-<screen>
- name | dream
-------+-------
- Sam  |  2400
-</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 a table name to denote
-     the entire current row of that table as a composite value.
-    </para>
-
-    <para>
-     It is also possible to build a function that returns a composite type.
-     (However, as we'll see below, there are some
-     unfortunate restrictions on how the function may be used.)
-     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 AS salary,
-        25 AS age,
-        point ''(2,2)'' AS cubicle;
-' LANGUAGE SQL;
-</programlisting>
-    </para>
-
-    <para>
-     In this case we have specified each of  the  attributes
-     with  a  constant value, but any computation or expression 
-     could have been substituted for these constants.
-     Note two important things about defining the function:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-	The  target  list  order 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>
-     In the present release of <productname>PostgreSQL</productname>
-     there are some unpleasant restrictions on how functions returning
-     composite types can be used.  Briefly, when calling a function that
-     returns a row, we cannot retrieve the entire row.  We must either
-     extract a single attribute out of the row or pass the entire row into
-     another function.  (Trying to display the entire row value will yield
-     a meaningless number.)  For example,
-
-<programlisting>
-SELECT (new_emp()).name;
-</programlisting>
-
-<screen>
- name
-------
- None
-</screen>
-
-     We need the extra parentheses to keep the parser from getting confused:
-
-<screen>
-SELECT new_emp().name;
-ERROR:  parser: parse error at or near "."
-</screen>
-    </para>
-
-    <para>
-     Another approach is to use
-     functional notation for extracting attributes.  The  simple  way 
-     to explain this is that we can use the
-     notations <literal>attribute(table)</>  and  <literal>table.attribute</>
-     interchangeably:
-
-<programlisting>
-SELECT name(new_emp());
-</programlisting>
-
-<screen>
- name
-------
- None
-</screen>
-
-<programlisting>
---
--- 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;
-</programlisting>
-
-<screen>
- youngster
------------
- Sam
-</screen>
-    </para>
-
-    <para>
-     Another way to use a function returning a row result is to declare a
-     second function accepting a row type parameter, and pass the function
-     result to it:
-
-<programlisting>
-CREATE FUNCTION getname(emp) RETURNS text AS
-'SELECT $1.name;'
-LANGUAGE SQL;
-</programlisting>
-
-<screen>
-SELECT getname(new_emp());
- getname
----------
- None
-(1 row)
-</screen>
-    </para>     
-   </sect2>
-
-   <sect2>
-    <title><acronym>SQL</acronym> Table Functions (Functions Returning Sets)</title>
-
-    <para>
-     A table function is one that may be used in the <command>FROM</command>
-     clause of a query. All SQL Language functions may be used in this manner.
-     If the function is defined to return a base type, the table function
-     produces a one column result set. If the function is defined to
-     return <literal>SETOF <replaceable>sometype</></literal>, the table
-     function returns multiple rows. To illustrate a SQL table function,
-     consider the following, which returns <literal>SETOF</literal> a
-     composite type:
-
-<programlisting>
-CREATE TABLE foo (fooid int, foosubid int, fooname text, primary key(fooid,foosubid));
-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 setof foo AS '
-    SELECT * FROM foo WHERE fooid = $1;
-' LANGUAGE SQL;
-SELECT * FROM getfoo(1) AS t1;
-</programlisting>
-
-<screen>
- fooid | foosubid | fooname
--------+----------+---------
-     1 |        1 | Joe
-     1 |        2 | Ed
-(2 rows)
-</screen>
-    </para>
-
-    <para>
-     When an SQL function is declared as returning <literal>SETOF
-     <replaceable>sometype</></literal>, the function's final
-     <command>SELECT</> query is executed to completion, and each row it
-     outputs is returned as an element of the set.
-    </para>
-
-    <para>
-     Functions returning sets may also currently be called in the target list
-     of a <command>SELECT</> query.  For each row that the <command>SELECT</>
-     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 may be removed in future
-     releases. The following is an example function returning a set from the
-     target list:
-
-<programlisting>
-CREATE FUNCTION listchildren(text) RETURNS SETOF text AS
-'SELECT name FROM nodes WHERE parent = $1'
-LANGUAGE SQL;
-</programlisting>
-
-<screen>
-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 inputs, so no output rows are generated.
-    </para>
-   </sect2>
-  </sect1>
-
-  <sect1 id="xfunc-pl">
-   <title>Procedural Language Functions</title>
-
-   <para>
-    Procedural languages aren't built into the <productname>PostgreSQL</productname> server; they are offered
-    by loadable modules. Please refer to the documentation of the
-    procedural language in question for details about the syntax and how the function body
-    is interpreted for each language.
-   </para>
-
-   <para>
-    There are currently four procedural languages available in the
-    standard <productname>PostgreSQL</productname> distribution:
-    <application>PL/pgSQL</application>, <application>PL/Tcl</application>,
-    <application>PL/Perl</application>, and <application>PL/Python</application>.  Other languages can be
-    defined by users.  Refer to <xref linkend="xplang"> for more
-    information.  The basics of developing a new procedural language are covered in <xref linkend="xfunc-plhandler">.
-   </para>
-  </sect1>
-
-  <sect1 id="xfunc-internal">
-   <title>Internal Functions</title>
-
-   <indexterm zone="xfunc-internal"><primary>function</><secondary>internal</></>
-
-   <para>
-    Internal functions are functions written in C that have been statically
-    linked into the <productname>PostgreSQL</productname> server.
-    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 backwards 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
-    backend are declared during the initialization of the database cluster (<command>initdb</command>),
-    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
-    WITH (isStrict);
-</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>
-
-   <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 --- 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
-    ("version 0") 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>
-
-   <para>
-    The first time a user-defined function in a particular
-    loadable object file is called in a backend 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>,
-       that part is replaced by the <productname>PostgreSQL</> package
-	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
-       <varname>dynamic_library_path</varname>.<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>
-
-   <note>
-    <para>
-     The user ID the <application>PostgreSQL</application> server runs
-     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>
-   </note>
-
-   <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>
-     <application>PostgreSQL</application> will not compile a C function
-     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>
-
-   <note>
-    <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, use the <command>LOAD</> command or
-     begin a fresh session.
-    </para>
-   </note>
-
-   <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>
-
-   <note>
-    <para>
-     Before <application>PostgreSQL</application> release 7.2, only exact
-     absolute paths to object files could be specified in <command>CREATE
-     FUNCTION</>.  This approach is now deprecated since it makes the
-     function definition unnecessarily unportable.  It's best to specify
-     just the shared library name with no path nor extension, and let
-     the search mechanism provide that information instead.
-    </para>
-   </note>
-
-  </sect2>
-
-   <sect2>
-    <title>Base Types in C-Language Functions</title>
-
-    <para>
-     <xref linkend="xfunc-c-type-table"> gives the C type required for
-     parameters in the C functions that will be loaded into 
-     <productname>PostgreSQL</>.
-     The <quote>Defined In</quote> column gives the header file that
-     needs to be included to get the type definition.  (The actual
-     definition may 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 <productname>PostgreSQL</productname> Types</title>
-      <titleabbrev>Equivalent C Types</titleabbrev>
-      <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>
-     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.
-     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>
-
-     <productname>PostgreSQL</productname> automatically figures
-     things out so that the integer types really have the size they
-     advertise.
-    </para>
-
-    <para>
-     On  the  other hand, fixed-length types of any size may
-     be passed by-reference.  For example, here is a  sample
-     implementation of a <productname>PostgreSQL</productname> type:
-     
-<programlisting>
-/* 16-byte structure, passed by reference */
-typedef struct
-{
-    double  x, y;
-} Point;
-</programlisting>
-    </para>
-
-    <para>
-     Only  pointers  to  such types can be used when passing
-     them in and out of <productname>PostgreSQL</productname> functions.
-     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.  (Alternatively, you can return an input
-     value of the same type by returning its pointer.  <emphasis>Never</>
-     modify the contents of a pass-by-reference input value, however.)
-    </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  is  the  total  length  of the structure
-     (i.e.,  it  includes  the  size  of  the  length  field
-     itself).  We can define the text type as follows:
-
-<programlisting>
-typedef struct {
-    int4 length;
-    char data[1];
-} text;
-</programlisting>
-    </para>
-
-    <para>
-     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.  (If this isn't a familiar trick to
-     you, you may wish to spend some time with an introductory
-     <acronym>C</acronym> programming textbook before delving deeper into
-     <productname>PostgreSQL</productname> server programming.)
-     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  text
-     structure, we might use a code fragment like this:
-
-<programlisting>
-#include "postgres.h"
-...
-char buffer[40]; /* our source data */
-...
-text *destination = (text *) palloc(VARHDRSZ + 40);
-destination-&gt;length = VARHDRSZ + 40;
-memcpy(destination-&gt;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>
-     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 for C-Language Functions</title>
-
-    <para>
-     We present the <quote>old style</quote> calling convention first --- 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>
-#include "postgres.h"
-#include &lt;string.h&gt;
-
-/* 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));
-    VARATT_SIZEP(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);
-
-    VARATT_SIZEP(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,
-     we could define the functions to <productname>PostgreSQL</productname>
-     with commands like this:
-     
-<programlisting>
-CREATE FUNCTION add_one(int4) RETURNS int4
-     AS '<replaceable>PGROOT</replaceable>/tutorial/funcs' LANGUAGE C
-     WITH (isStrict);
-
--- note overloading of SQL function name add_one()
-CREATE FUNCTION add_one(float8) RETURNS float8
-     AS '<replaceable>PGROOT</replaceable>/tutorial/funcs',
-        'add_one_float8'
-     LANGUAGE C WITH (isStrict);
-
-CREATE FUNCTION makepoint(point, point) RETURNS point
-     AS '<replaceable>PGROOT</replaceable>/tutorial/funcs' LANGUAGE C
-     WITH (isStrict);
-                         
-CREATE FUNCTION copytext(text) RETURNS text
-     AS '<replaceable>PGROOT</replaceable>/tutorial/funcs' LANGUAGE C
-     WITH (isStrict);
-
-CREATE FUNCTION concat_text(text, text) RETURNS text
-     AS '<replaceable>PGROOT</replaceable>/tutorial/funcs' LANGUAGE C
-     WITH (isStrict);
-</programlisting>
-    </para>
-
-    <para>
-     Here <replaceable>PGROOT</replaceable> stands for the full path to
-     the <productname>PostgreSQL</productname> source tree. (Better style would
-     be to use just <literal>'funcs'</> in the <literal>AS</> clause,
-     after having added <replaceable>PGROOT</replaceable><literal>/tutorial</>
-     to the search path.  In any case, we may 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 NULLs
-     explicitly, for example 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 smaller-than-int data types 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 for C-Language Functions</title>
-
-    <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
-     <productname>PostgreSQL</> currently
-     assumes all internal functions are version-1.  However, it is
-     <emphasis>required</emphasis> 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.
-    </para>
-
-    <para>
-     Here we show the same functions as above, coded in version-1 style:
-
-<programlisting>
-#include "postgres.h"
-#include &lt;string.h&gt;
-#include "fmgr.h"
-
-/* 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));
-    VARATT_SIZEP(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);
-
-    VARATT_SIZEP(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 may appear to
-     be just pointless obscurantism.  However, they do 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 hide
-     the need to deal with fetching <quote>toasted</quote> (compressed or
-     out-of-line) values.  The old-style <function>copytext</function>
-     and <function>concat_text</function> functions shown above are
-     actually wrong in the presence of toasted values, because they
-     don't call <function>pg_detoast_datum()</function> on their
-     inputs.  (The handler for old-style dynamically-loaded functions
-     currently takes care of this detail, but it does so less
-     efficiently than is possible for a version-1 function.)
-    </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 parameter which is
-     safe for writing into. (The normal macros will sometimes return a
-     pointer to the value which must not be written to. Using the
-     <function>PG_GETARG_<replaceable>xxx</replaceable>_COPY()</function>
-     macros guarantees a writable result.)
-    </para>
-
-    <para>
-    The second variant consists of the
-    <function>PG_GETARG_<replaceable>xxx</replaceable>_SLICE()</function>
-    macros which take three parameters. The first is the number of the
-    parameter (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 routines provide more efficient access to
-    parts of large values in the case where they have storage type
-    "external". (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>. Storage type is one of
-    <literal>plain</>, <literal>external</>, <literal>extended</literal>,
-     or <literal>main</>.)
-    </para>
-
-    <para>
-     The version-1 function call conventions make it possible to
-     return <quote>set</quote> results and implement trigger functions and
-     procedural-language call handlers.  Version-1 code is also more
-     portable than version-0, because it does not break ANSI C restrictions
-     on function call protocol.  For more details see
-     <filename>src/backend/utils/fmgr/README</filename> in the source
-     distribution.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Composite Types in C-Language Functions</title>
-
-    <para>
-     Composite types do not  have  a  fixed  layout  like  C
-     structures.   Instances of a composite type may contain
-     null fields.  In addition,  composite  types  that  are
-     part  of  an  inheritance  hierarchy may have different
-     fields than other members of the same inheritance hierarchy.    
-     Therefore,  <productname>PostgreSQL</productname>  provides  
-     a  procedural interface for accessing fields of composite types  
-     from C.  As <productname>PostgreSQL</productname> processes 
-     a set of rows, each row will be passed into your 
-     function as an  opaque  structure of type <literal>TUPLE</literal>.
-     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>
-
-     In the query above, we can define <function>c_overpaid</> as:
-     
-<programlisting>
-#include "postgres.h"
-#include "executor/executor.h"  /* for GetAttributeByName() */
-
-bool
-c_overpaid(TupleTableSlot *t, /* the current row of EMP */
-           int32 limit)
-{
-    bool isnull;
-    int32 salary;
-
-    salary = DatumGetInt32(GetAttributeByName(t, "salary", &amp;isnull));
-    if (isnull)
-        return (false);
-    return salary &gt; limit;
-}
-
-/* In version-1 coding, the above would look like this: */
-
-PG_FUNCTION_INFO_V1(c_overpaid);
-
-Datum
-c_overpaid(PG_FUNCTION_ARGS)
-{
-    TupleTableSlot  *t = (TupleTableSlot *) PG_GETARG_POINTER(0);
-    int32            limit = PG_GETARG_INT32(1);
-    bool isnull;
-    int32 salary;
-
-    salary = DatumGetInt32(GetAttributeByName(t, "salary", &amp;isnull));
-    if (isnull)
-        PG_RETURN_BOOL(false);
-    /* Alternatively, we might prefer to do PG_RETURN_NULL() for null salary */
-
-    PG_RETURN_BOOL(salary &gt; limit);
-}
-</programlisting>
-    </para>
-
-    <para>
-     <function>GetAttributeByName</function> is the 
-     <productname>PostgreSQL</productname> system function that
-     returns attributes out of the current row.  It has
-     three arguments: the argument of type <type>TupleTableSlot*</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.
-    </para>
-
-    <para>
-     The  following  command  lets  <productname>PostgreSQL</productname>  
-     know  about  the <function>c_overpaid</function> function:
-
-<programlisting>
-CREATE FUNCTION c_overpaid(emp, int4) 
-RETURNS bool
-AS '<replaceable>PGROOT</replaceable>/tutorial/funcs' 
-LANGUAGE C;
-</programlisting>
-    </para>
-
-    <para>
-     While there are ways to construct new rows or modify  
-     existing rows from within a C function, these
-     are far too complex to discuss in this manual.
-     Consult the backend source code for examples.
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>Writing Code</title>
-
-    <para>
-     We now turn to the more difficult task of writing  
-     programming  language  functions.  Be warned: this section
-     of the manual will not make you a programmer.  You must
-     have  a  good  understanding of <acronym>C</acronym>
-     (including the use of pointers and the malloc memory manager)  
-     before  trying to write <acronym>C</acronym> functions for 
-     use with <productname>PostgreSQL</productname>. While  it may 
-     be possible to load functions written in languages other 
-     than <acronym>C</acronym> into  <productname>PostgreSQL</productname>,  
-     this  is  often difficult  (when  it  is possible at all) 
-     because other languages, such as <acronym>FORTRAN</acronym> 
-     and <acronym>Pascal</acronym> often do not follow the same 
-     <firstterm>calling convention</firstterm>
-     as <acronym>C</acronym>.  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  programming  language  functions
-     are written in <acronym>C</acronym>.
-    </para>
-
-    <para>
-     The  basic  rules  for building <acronym>C</acronym> functions 
-     are as follows:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-	Use <literal>pg_config --includedir-server</literal><indexterm><primary>pg_config</></> to find
-	out where the <productname>PostgreSQL</> server header files are installed on
-	your system (or the system that your users will be running
-	on).  This option is new with <productname>PostgreSQL</> 7.2.
-	For <productname>PostgreSQL</>
-	7.1 you should use the option <option>--includedir</option>.
-	(<command>pg_config</command> will exit with a non-zero status
-	if it encounters an unknown option.)  For releases prior to
-	7.1 you will have to guess, but since that was before the
-	current calling conventions were introduced, it is unlikely
-	that you want to support those releases.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-	When allocating memory, use the
-	<productname>PostgreSQL</productname> routines
-	<function>palloc</function> and <function>pfree</function>
-	instead of the corresponding <acronym>C</acronym> library
-	routines <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> or <function>bzero</function>.
-	Several routines (such as the hash access method, hash join
-	and the sort algorithm) compute functions of the raw bits
-	contained in your structure.  Even if you initialize all
-	fields of your structure, there may be several bytes of
-	alignment padding (holes in the structure) that may contain
-	garbage values.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Most of the internal <productname>PostgreSQL</productname> 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
-        <productname>PostgreSQL</productname> server executable.  You
-        will have to rename your functions or variables if you get
-        error messages to this effect.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-	Compiling and linking your object code  so  that
-	it  can  be  dynamically  loaded  into  
-	<productname>PostgreSQL</productname>
-	always requires special flags.
-	See <xref linkend="dfunc">
-	for  a  detailed explanation of how to do it for
-	your particular operating system.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-&dfunc;
-
-  </sect1>
-
-  <sect1 id="xfunc-overload">
-   <title>Function Overloading</title>
-
-   <indexterm zone="xfunc-overload"><primary>overloading</></>
-
-   <para>
-    More than one function may 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>
-    A function may also have the same name as an attribute.  In the case
-    that there is an ambiguity between a function on a complex type and
-    an attribute of the complex type, the attribute will always be used.
-   </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 the
-    <citetitle>User's Guide</citetitle>, but it is unwise to design a
-    system that subtly relies on this behavior.
-   </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.  E.g.,
-<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>
-
-   <para>
-    Prior to <productname>PostgreSQL</productname> 7.0, this
-    alternative syntax did not exist.  There is a trick to get around
-    the problem, by defining a set of C functions with different names
-    and then define a set of identically-named SQL function wrappers
-    that take the appropriate argument types and call the matching C
-    function.
-   </para>
-  </sect1>
-
-  <sect1 id="xfunc-tablefunctions">
-   <title>Table Functions</title>
-
-   <indexterm zone="xfunc-tablefunctions"><primary>function</></>
-
-   <para>
-    Table functions are functions that produce a set of rows, made up of
-    either base (scalar) data types, or composite (multi-column) data types.
-    They are used like a table, view, or subselect in the <literal>FROM</>
-    clause of a query. Columns returned by table functions may be included in
-    <literal>SELECT</>, <literal>JOIN</>, or <literal>WHERE</> clauses in the
-    same manner as a table, view, or subselect column.
-   </para>
-
-   <para>
-    If a table function returns a base data type, the single result column
-    is named for the function. 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 may be aliased in the <literal>FROM</> clause, but it also
-    may be left unaliased. If a function is used in the FROM clause with no
-    alias, the function name is used as the relation name.
-   </para>
-
-   <para>
-    Table functions work wherever tables do in <literal>SELECT</> statements.
-    For example
-<programlisting>
-CREATE TABLE foo (fooid int, foosubid int, fooname text, primary key(fooid,foosubid));
-CREATE FUNCTION getfoo(int) RETURNS 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>
-    are all valid statements.
-   </para>
-
-   <para>
-    Currently, table functions are supported as SQL language functions
-    (<xref linkend="xfunc-sql">) and C language functions
-    (<xref linkend="xfunc-c">). See these individual sections for more
-    details.
-   </para>
-
-  </sect1>
-
-  <sect1 id="xfunc-plhandler">
-   <title>Procedural Language Handlers</title>
-
-   <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 section
-    describes how a language call handler can be written.  This is not
-    a common task, in fact, it has only been done a handful of times
-    in the history of <productname>PostgreSQL</productname>, but the
-    topic naturally belongs in this chapter, and the material might
-    give some insight into the extensible nature of the
-    <productname>PostgreSQL</productname> system.
-   </para>
-
-   <para>
-    The call handler for a procedural language is a
-    <quote>normal</quote> function, which must be written in a
-    compiled language such as C and registered with
-    <productname>PostgreSQL</productname> as taking no arguments and
-    returning the <type>opaque</type> type, a placeholder for
-    unspecified or undefined types.  This prevents the call handler
-    from being called directly as a function from queries.  (However,
-    arguments may be supplied in the actual call to the handler when a
-    function in the language offered by the handler is to be
-    executed.)
-   </para>
-
-   <note>
-    <para>
-     In <productname>PostgreSQL</productname> 7.1 and later, call
-     handlers must adhere to the <quote>version 1</quote> function
-     manager interface, not the old-style interface.
-    </para>
-   </note>
-
-   <para>
-    The call handler is called in the same way as any other function:
-    It receives a pointer to a
-    <structname>FunctionCallInfoData</structname> 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> struct, 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> struct 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
-    <classname>pg_proc</classname> entry and to analyze the argument
-    and return types of the called procedure. The AS clause from the
-    <command>CREATE FUNCTION</command> of the procedure will be found
-    in the <literal>prosrc</literal> attribute of the
-    <classname>pg_proc</classname> table entry. This may be the source
-    text in the procedural language itself (like for PL/Tcl), 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 NULL, but can be set by the call handler to point at
-    information about the PL function.  On subsequent calls, if
-    <structfield>flinfo-&gt;fn_extra</structfield> is already non-NULL
-    then it can be used and the information lookup step skipped.  The
-    call handler must be careful 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 context so that it can cache
-    function definition information across queries.
-   </para>
-
-   <para>
-    When a PL function is invoked as a trigger, no explicit arguments
-    are passed, but the
-    <structname>FunctionCallInfoData</structname>'s
-    <structfield>context</structfield> field points at a
-    <structname>TriggerData</structname> node, rather than being NULL
-    as it is in a plain function call.  A language handler should
-    provide mechanisms for PL functions to get at the trigger
-    information.
-   </para>
-
-   <para>
-    This is a template for a PL handler written in C:
-<programlisting>
-#include "postgres.h"
-#include "executor/spi.h"
-#include "commands/trigger.h"
-#include "utils/elog.h"
-#include "fmgr.h"
-#include "access/heapam.h"
-#include "utils/syscache.h"
-#include "catalog/pg_proc.h"
-#include "catalog/pg_type.h"
-
-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->context;
-
-        retval = ...
-    }
-    else {
-        /*
-         * Called as a function
-         */
-
-        retval = ...
-    }
-
-    return retval;
-}
-</programlisting>
-   </para>
-
-   <para>
-    Only a few thousand lines of code have to be added instead of the
-    dots to complete the call handler.  See <xref linkend="xfunc-c">
-    for information on how to compile it into a loadable module.
-   </para>
-
-   <para>
-    The following commands then register the sample procedural
-    language:
-<programlisting>
-CREATE FUNCTION plsample_call_handler () RETURNS opaque
-    AS '/usr/local/pgsql/lib/plsample'
-    LANGUAGE C;
-CREATE LANGUAGE plsample
-    HANDLER plsample_call_handler;
-</programlisting>
-   </para>
-  </sect1>
- </chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/xindex.sgml b/doc/src/sgml/xindex.sgml
deleted file mode 100644
index c6bfb0e19f3..00000000000
--- a/doc/src/sgml/xindex.sgml
+++ /dev/null
@@ -1,595 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/xindex.sgml,v 1.25 2002/05/29 17:36:40 tgl Exp $
-PostgreSQL documentation
--->
-
-<chapter id="xindex">
- <title>Interfacing Extensions To Indexes</title>
-
- <sect1 id="xindex-intro">
-  <title>Introduction</title>
-
-  <para>
-   The procedures described thus far let you define new types, new
-   functions, and new operators.  However, we cannot yet define a secondary
-   index (such as a B-tree, R-tree, or
-   hash access method) over a new type or its operators.
-  </para>
-
-  <para>
-   Look back at
-   <xref linkend="EXTEND-CATALOGS">.
-   The right half shows the  catalogs  that we must modify in order to tell
-   <productname>PostgreSQL</productname> how to use a user-defined type and/or
-   user-defined  operators with an index (i.e., <filename>pg_am, pg_amop,
-    pg_amproc, pg_operator</filename> and <filename>pg_opclass</filename>).
-   Unfortunately, there is no simple command to do this.  We will demonstrate
-   how to modify these catalogs through a running example:  a  new  operator
-   class for the B-tree access method that stores and
-   sorts complex numbers in ascending absolute value order.
-  </para>
- </sect1>
-
- <sect1 id="xindex-am">
-  <title>Access Methods</title>
-
-  <para>
-   The <filename>pg_am</filename> table contains one row for every
-   index access method.  Support for the heap access method is built
-   into <productname>PostgreSQL</productname>, but all other access
-   methods are described in <filename>pg_am</filename>.  The schema is
-   shown in <xref linkend="xindex-pgam-table">.
-
-   <table tocentry="1" id="xindex-pgam-table">
-    <title>Index Access Method Schema</title>
-
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Column</entry>
-       <entry>Description</entry>
-      </row>
-     </thead>
-     <tbody>
-      <row>
-       <entry>amname</entry>
-       <entry>name of the access method</entry>
-      </row>
-      <row>
-       <entry>amowner</entry>
-       <entry>user ID of the owner (currently not used)</entry>
-      </row>
-      <row>
-       <entry>amstrategies</entry>
-       <entry>number of strategies for this access method (see below)</entry>
-      </row>
-      <row>
-       <entry>amsupport</entry>
-       <entry>number of support routines for this access method (see below)</entry>
-      </row>
-      <row>
-       <entry>amorderstrategy</entry>
-       <entry>zero if the index offers no sort order, otherwise the strategy
-        number of the strategy operator that describes the sort order</entry>
-      </row>
-      <row>
-       <entry>amcanunique</entry>
-       <entry>does AM support unique indexes?</entry>
-      </row>
-      <row>
-       <entry>amcanmulticol</entry>
-       <entry>does AM support multicolumn indexes?</entry>
-      </row>
-      <row>
-       <entry>amindexnulls</entry>
-       <entry>does AM support NULL index entries?</entry>
-      </row>
-      <row>
-       <entry>amconcurrent</entry>
-       <entry>does AM support concurrent updates?</entry>
-      </row>
-      <row>
-       <entry>amgettuple</entry>
-      </row>
-      <row>
-       <entry>aminsert</entry>
-      </row>
-      <row>
-       <entry>...</entry>
-       <entry>procedure  identifiers  for  interface routines to the access
-        method.  For example, regproc IDs for opening,  closing,  and
-        getting rows from the access method appear here.</entry>
-      </row>
-     </tbody>
-    </tgroup>
-   </table>
-  </para>
-
-  <note>
-   <para>
-    An index AM that supports multiple columns (has
-    <structfield>amcanmulticol</structfield> true) <emphasis>must</>
-    support indexing nulls in columns after the first, because the planner
-    will assume the index can be used for queries on just the first
-    column(s).  For example, consider an index on (a,b) and a query
-    WHERE a = 4.  The system will assume the index can be used to scan for
-    rows with a = 4, which is wrong if the index omits rows where b is null.
-    However it is okay to omit rows where the first indexed column is null.
-    (GiST currently does so.)
-    <structfield>amindexnulls</structfield> should be set true only if the
-    index AM indexes all rows, including arbitrary combinations of nulls.
-   </para>
-  </note>
-
-  <para>
-   The <acronym>OID</acronym> of the row in
-   <filename>pg_am</filename> is used as a foreign key in a lot of other
-   tables.  You  do not  need to  add a new row to this table; all that
-   you are interested in is the <acronym>OID</acronym> of the access
-   method you want to extend:
-
-<screen>
-SELECT oid FROM pg_am WHERE amname = 'btree';
-
- oid
------
- 403
-(1 row)
-</screen>
-
-   We will use that query in a <literal>WHERE</literal>
-   clause later.
-  </para>
- </sect1>
-
- <sect1 id="xindex-strategies">
-  <title>Access Method Strategies</title>
-
-  <para>
-   The <structfield>amstrategies</structfield> column exists to standardize
-   comparisons across data types.  For example, B-trees
-   impose a strict ordering on keys, lesser to greater.  Since
-   <productname>PostgreSQL</productname> allows the user to define operators,
-   <productname>PostgreSQL</productname> cannot look at the name of an operator
-   (e.g., <literal>&gt;</> or <literal>&lt;</>) and tell what kind of comparison it is.  In fact,
-   some  access methods don't impose any ordering at all.  For example,
-   R-trees express a rectangle-containment relationship,
-   whereas a hashed data structure expresses only bitwise similarity based
-   on the value of a hash function.  <productname>PostgreSQL</productname>
-   needs some consistent way of taking a qualification in your query,
-   looking at the operator, and then deciding if a usable index exists.  This
-   implies that <productname>PostgreSQL</productname> needs to know, for
-   example, that the  <literal>&lt;=</>  and  <literal>&gt;</> operators partition a
-   B-tree.  <productname>PostgreSQL</productname>
-   uses <firstterm>strategies</firstterm> to express these relationships  between
-   operators and the way they can be used to scan indexes.
-  </para>
-
-  <para>
-   Defining a new set of strategies is beyond the scope of this
-   discussion, but we'll explain how B-tree strategies work because
-   you'll need to know that to add a new B-tree operator class. In the
-   <classname>pg_am</classname> table, the
-   <structfield>amstrategies</structfield> column sets the number of
-   strategies defined for this access method. For B-trees, this number
-   is 5.  The meanings of these strategies are shown in <xref
-   linkend="xindex-btree-table">.
-  </para>
-
-   <table tocentry="1" id="xindex-btree-table">
-    <title>B-tree Strategies</title>
-    <titleabbrev>B-tree</titleabbrev>
-    <tgroup cols="2">
-     <thead>
-      <row>
-       <entry>Operation</entry>
-       <entry>Index</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>
-   The idea is that you'll need to add operators corresponding to these strategies
-   to the <classname>pg_amop</classname> relation (see below).
-   The access method code can use these strategy numbers, regardless of data
-   type, to figure out how to partition the B-tree,
-   compute selectivity, and so on.  Don't worry about the details of adding
-   operators yet; just understand that there must be a set of these
-   operators for <type>int2</>, <type>int4</>, <type>oid</>, and all other
-   data types on which a B-tree can operate.
-  </para>
- </sect1>
-
- <sect1 id="xindex-support">
-  <title>Access Method Support Routines</title>
-
-  <para>
-   Sometimes, strategies aren't enough information for the system to figure
-   out how to use an index.  Some access methods require additional support
-   routines in order to work. For example, the B-tree
-   access method must be able to compare two keys and determine whether one
-   is greater than, equal to, or less than the other.  Similarly, the
-   R-tree access method must be able to compute
-   intersections,  unions, and sizes of rectangles.  These
-   operations do not correspond to operators used in qualifications in
-   SQL queries;  they are administrative routines used by
-   the access methods, internally.
-  </para>
-
-  <para>
-   In order to manage diverse support routines consistently across all
-   <productname>PostgreSQL</productname> access methods,
-   <classname>pg_am</classname> includes a column called
-   <structfield>amsupport</structfield>.  This column records the
-   number of support routines used by an access method.  For B-trees,
-   this number is one: the routine to take two keys and return -1, 0,
-   or +1, depending on whether the first key is less than, equal to,
-   or greater than the second. (Strictly speaking, this routine can
-   return a negative number (&lt; 0), zero, or a non-zero positive
-   number (&gt; 0).)
-  </para>
-
-  <para>
-   The <structfield>amstrategies</structfield> entry in
-   <classname>pg_am</classname> is just the number of strategies
-   defined for the access method in question.  The operators for less
-   than, less equal, and so on don't appear in
-   <classname>pg_am</classname>.  Similarly,
-   <structfield>amsupport</structfield> is just the number of support
-   routines required by the access method.  The actual routines are
-   listed elsewhere.
-  </para>
-
-  <para>
-   By the way, the <structfield>amorderstrategy</structfield> column tells whether
-   the access method supports ordered scan.  Zero means it doesn't; if it
-   does, <structfield>amorderstrategy</structfield> is the number of the strategy
-   routine that corresponds to the ordering operator.  For example, B-tree
-   has <structfield>amorderstrategy</structfield> = 1, which is its
-   <quote>less than</quote> strategy number.
-  </para>
- </sect1>
-
- <sect1 id="xindex-opclass">
-  <title>Operator Classes</title>
-
-  <para>
-   The next table of interest is <classname>pg_opclass</classname>.  This table
-   defines operator class names and input data types for each of the operator
-   classes supported by a given index access method.  The same class name
-   can be used for several different access methods (for example, both B-tree
-   and hash access methods have operator classes named
-   <literal>oid_ops</literal>), but a separate
-   <filename>pg_opclass</filename> row must appear for each access method.
-   The OID of the <classname>pg_opclass</classname> row is
-   used as a foreign 
-   key in other tables to associate specific operators and support routines
-   with the operator class.
-  </para>
-
-  <para>
-   You need to add a row with your operator class name (for example,
-   <literal>complex_abs_ops</literal>) to
-   <classname>pg_opclass</classname>:
-
-<programlisting>
-INSERT INTO pg_opclass (opcamid, opcname, opcnamespace, opcowner, opcintype, opcdefault, opckeytype)
-    VALUES (
-        (SELECT oid FROM pg_am WHERE amname = 'btree'),
-        'complex_abs_ops',
-        (SELECT oid FROM pg_namespace WHERE nspname = 'pg_catalog'),
-        1,	-- UID of superuser is hardwired to 1 as of PG 7.3
-        (SELECT oid FROM pg_type WHERE typname = 'complex'),
-        true,
-        0);
-
-SELECT oid, *
-    FROM pg_opclass
-    WHERE opcname = 'complex_abs_ops';
-
-  oid   | opcamid |     opcname     | opcnamespace | opcowner | opcintype | opcdefault | opckeytype
---------+---------+-----------------+--------------+----------+-----------+------------+------------
- 277975 |     403 | complex_abs_ops |           11 |        1 |    277946 | t          |          0
-(1 row)
-</programlisting>
-
-   Note that the OID for your <classname>pg_opclass</classname> row will
-   be different!  Don't worry about this though.  We'll get this number
-   from the system later just like we got the OID of the type here.
-  </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 set <structfield>opcdefault</structfield> to false instead.
-   <structfield>opckeytype</structfield> is not described here; it should always
-   be zero for B-tree operator classes.
-  </para>
- </sect1>
-
- <sect1 id="xindex-operators">
-  <title>Creating the Operators and Support Routines</title>
-
-  <para>
-   So now we have an access method and an operator  class.
-   We  still  need  a  set of operators.  The procedure for
-   defining operators was discussed in <xref linkend="xoper">.
-   For  the  <literal>complex_abs_ops</literal>  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>
-   Suppose the code that implements these functions
-   is stored in the file
-   <filename><replaceable>PGROOT</replaceable>/src/tutorial/complex.c</filename>,
-   which we have compiled into
-   <filename><replaceable>PGROOT</replaceable>/src/tutorial/complex.so</filename>.
-   Part of the C code looks like this:
-
-<programlisting>
-#define Mag(c) ((c)-&gt;x*(c)-&gt;x + (c)-&gt;y*(c)-&gt;y)
-
-         bool
-         complex_abs_eq(Complex *a, Complex *b)
-         {
-             double amag = Mag(a), bmag = Mag(b);
-             return (amag==bmag);
-         }
-</programlisting>
-   (Note that we will only show the equality operator for the rest of
-   the examples.  The other four operators are very similar.  Refer to
-   <filename>complex.c</filename> or
-   <filename>complex.source</filename> for the details.)
-  </para>
-
-  <para>
-   We make the function known to <productname>PostgreSQL</productname> like this:
-<programlisting>
-CREATE FUNCTION complex_abs_eq(complex, complex) RETURNS boolean
-    AS '<replaceable>PGROOT</replaceable>/src/tutorial/complex'
-    LANGUAGE C;
-</programlisting>
-  </para>
-
-  <para>
-   There are some important things that are happening here:
-
-  <itemizedlist>
-   <listitem>
-  <para>
-   First, note that operators for less-than, less-than-or-equal, equal,
-   greater-than-or-equal, and greater-than for <filename>complex</filename>
-   are being defined.  We can only have one operator named, say, = and
-   taking type <filename>complex</filename> for both operands.  In this case
-   we don't have any other operator = for <filename>complex</filename>,
-   but if we were building a practical data type we'd probably want = to
-   be the ordinary equality operation for complex numbers.  In that case,
-   we'd need to use some other operator name for <function>complex_abs_eq</>.
-  </para>
-   </listitem>
-
-   <listitem>
-  <para>
-   Second, although <productname>PostgreSQL</productname> can cope with operators having
-   the same name as long as they have different input data types, C can only
-   cope with one global routine having a given name, period.  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>
-   Third, we could have made the <productname>PostgreSQL</productname> name of the function
-   <filename>abs_eq</filename>, relying on <productname>PostgreSQL</productname> to distinguish it
-   by input data types from any other <productname>PostgreSQL</productname> function of the same name.
-   To keep the example simple, we make the function have the same names
-   at the C level and <productname>PostgreSQL</productname> level.
-  </para>
-   </listitem>
-
-   <listitem>
-  <para>
-   Finally, note that these operator functions return Boolean values.
-   In practice, all operators defined as index access method
-   strategies 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.
-   (On the other hand, the support function returns whatever the
-   particular access method expects -- in this case, a signed
-   integer.)
-  </para>
-   </listitem>
-  </itemizedlist>
-  </para>
-
-  <para>
-   The final routine in the file is the <quote>support routine</quote>
-   mentioned when we discussed the <structfield>amsupport</> column of the
-   <classname>pg_am</classname> table.  We will use this later on.  For
-   now, ignore it.
-  </para>
-
-  <para>
-   Now we are ready to define the operators:
-
-<programlisting>
-CREATE OPERATOR = (
-     leftarg = complex, rightarg = complex,
-     procedure = complex_abs_eq,
-     restrict = eqsel, join = eqjoinsel
-         );
-</programlisting>
-
-   The important
-   things here are the procedure names (which are the C
-   functions defined above) and the restriction and join selectivity
-   functions.  You should just use the selectivity functions used in
-   the example (see <filename>complex.source</filename>).
-   Note that there
-   are different such functions for the less-than, equal, and greater-than
-   cases.  These must be supplied or the optimizer will be unable to
-   make effective use of the index.
-  </para>
-
-  <para>
-   The next step is to add entries for these operators to
-   the <classname>pg_amop</classname> relation.  To do this,
-   we'll need the OIDs of the operators we just
-   defined.  We'll look up the names of all the operators that take
-   two operands of type <type>complex</type>, and pick ours out:
-   
-<screen>
-SELECT o.oid AS opoid, o.oprname
-    INTO TEMP TABLE complex_ops_tmp
-    FROM pg_operator o, pg_type t
-    WHERE o.oprleft = t.oid and o.oprright = t.oid
-      and t.typname = 'complex';
-
- opoid  | oprname
---------+---------
- 277963 | +
- 277970 | &lt;
- 277971 | &lt;=
- 277972 | =
- 277973 | &gt;=
- 277974 | &gt;
-(6 rows)
-</screen>
-
-   (Again, some of your OID numbers will almost
-   certainly be different.)  The operators we are interested in are those
-   with OIDs 277970 through 277974.  The values you
-   get will probably be different, and you should substitute them for the
-   values below.  We will do this with a select statement.
-  </para>
-
-  <para>
-   Now we are ready to insert entries into <classname>pg_amop</classname> for
-   our new operator class.  These entries must associate the correct
-   B-tree strategy numbers with each of the operators we need.
-   The command to insert the less-than operator looks like:
-
-<programlisting>
-INSERT INTO pg_amop (amopclaid, amopstrategy, amopreqcheck, amopopr)
-    SELECT opcl.oid, 1, false, c.opoid
-        FROM pg_opclass opcl, complex_ops_tmp c
-        WHERE
-            opcamid = (SELECT oid FROM pg_am WHERE amname = 'btree') AND
-            opcname = 'complex_abs_ops' AND
-            c.oprname = '&lt;';
-</programlisting>
-
-   Now do this for the other operators substituting for the <literal>1</> in the
-   second line above and the <literal>&lt;</> in the last line.  Note the order:
-   <quote>less than</> is 1, <quote>less than or equal</> is 2,
-   <quote>equal</> is 3, <quote>greater than or equal</quote> is 4, and
-   <quote>greater than</quote> is 5.
-  </para>
-
-  <para>
-   The field <filename>amopreqcheck</filename> is not discussed here; it
-   should always be false for B-tree operators.
-  </para>
-
-  <para>
-   The final step is the registration of the <quote>support routine</quote> previously
-   described in our discussion of <classname>pg_am</classname>.  The
-   OID of this support routine is stored in the
-   <classname>pg_amproc</classname> table, keyed by the operator class
-   OID and the support routine number.
-  </para>
-
-  <para>
-   First, we need to register the function in
-   <productname>PostgreSQL</productname> (recall that we put the
-   C code that implements this routine in the bottom of
-   the file in which we implemented the operator routines):
-
-<programlisting>
-CREATE FUNCTION complex_abs_cmp(complex, complex)
-    RETURNS integer
-    AS '<replaceable>PGROOT</replaceable>/src/tutorial/complex'
-    LANGUAGE C;
-
-SELECT oid, proname FROM pg_proc
-    WHERE proname = 'complex_abs_cmp';
-
-  oid   |     proname
---------+-----------------
- 277997 | complex_abs_cmp
-(1 row)
-</programlisting>
-
-   (Again, your OID number will probably be different.)
-  </para>
-
-  <para>
-   We can add the new row as follows:
-
-<programlisting>
-INSERT INTO pg_amproc (amopclaid, amprocnum, amproc)
-    SELECT opcl.oid, 1, p.oid
-        FROM pg_opclass opcl, pg_proc p
-        WHERE
-            opcamid = (SELECT oid FROM pg_am WHERE amname = 'btree') AND
-            opcname = 'complex_abs_ops' AND
-            p.proname = 'complex_abs_cmp';
-</programlisting>
-  </para>
-
-  <para>
-   And we're done!  (Whew.)  It should now be possible to create
-   and use B-tree indexes on <type>complex</type> columns.
-  </para>
- </sect1>
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/xoper.sgml b/doc/src/sgml/xoper.sgml
deleted file mode 100644
index 079caad5cbd..00000000000
--- a/doc/src/sgml/xoper.sgml
+++ /dev/null
@@ -1,507 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/xoper.sgml,v 1.19 2002/05/11 02:09:41 tgl Exp $
--->
-
- <Chapter Id="xoper">
-  <Title>Extending <Acronym>SQL</Acronym>: Operators</Title>
-
- <sect1 id="xoper-intro">
-  <title>Introduction</title>
-
-  <Para>
-   <ProductName>PostgreSQL</ProductName> supports left unary,
-   right  unary,  and  binary
-   operators.   Operators  can  be  overloaded; that is,
-   the same operator name can be used for different operators
-   that have different numbers and types of operands.   If
-   there  is  an ambiguous situation and the system cannot
-   determine the correct operator to use, it  will  return
-   an  error.  You may have to type-cast the left and/or
-   right operands to help it understand which operator you
-   meant to use.
-  </Para>
-
-  <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.  Much of this chapter will be devoted to explaining
-   that additional information.
-  </Para>
- </sect1>
-
- <sect1 id="xoper-example">
-  <title>Example</title>
-
-  <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>PGROOT</replaceable>/tutorial/complex'
-    LANGUAGE C;
-
-CREATE OPERATOR + (
-    leftarg = complex,
-    rightarg = complex,
-    procedure = complex_add,
-    commutator = +
-);
-</ProgramListing>
-  </Para>
-
-  <Para>
-   Now we can do:
-     
-<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 below.
-  </Para>
- </sect1>
-
-  <sect1 id="xoper-optimization">
-   <title>Operator Optimization Information</title>
-
-   <note>
-    <title>Author</title>
-    <para>
-     Written by Tom Lane.
-    </para>
-   </note>
-
-   <para>
-    A <ProductName>PostgreSQL</ProductName> operator definition can include
-    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 backend crashes, 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
-    <ProductName>PostgreSQL</ProductName>.  The ones described here are all
-    the ones that release &version; understands.
-   </para>
-
-   <sect2>
-    <title>COMMUTATOR</title>
-
-    <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 commuted operator is the same as the
-     right operand type of its commutator, and vice versa.  So the name of
-     the commutator operator is all that <ProductName>PostgreSQL</ProductName>
-     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>
-     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.
-	Since <ProductName>PostgreSQL</ProductName> knows that commutative
-	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
-	in both definitions.  When <ProductName>PostgreSQL</ProductName> processes
-	the first definition and realizes that <literal>COMMUTATOR</> refers to a non-existent
-	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,
-	since that's all that <ProductName>PostgreSQL</ProductName> can deduce
-	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.  (Note: This procedure did not work
-	reliably in <ProductName>PostgreSQL</ProductName> versions before 6.5,
-	but it is now the recommended way to do things.)
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-   </sect2>
-
-   <sect2>
-    <title>NEGATOR</title>
-
-    <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 itself, 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 NOT (x = y) to be simplified into
-    x &lt;&gt; y.  This comes up more often than you might think, because
-    NOTs 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>RESTRICT</title>
-
-   <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 may 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 routine <function>convert_to_scalar()</function> in <filename>src/backend/utils/adt/selfuncs.c</filename>.
-    (Eventually, this routine 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 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 may want
-    to use them (or even better, improve them) anyway.
-   </para>
-   </sect2>
-
-   <sect2>
-    <title>JOIN</title>
-
-    <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>HASHES</title>
-
-    <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 binary operators that
-     return <literal>boolean</>, and in practice the operator had better be
-     equality for some data type.
-    </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 equality.
-    </para>
-
-    <para>
-     In fact, logical equality is not good enough either; the operator
-     had better represent pure bitwise equality, because the hash function
-     will be computed on the memory representation of the values regardless
-     of what the bits mean.  For example, equality of
-     time intervals is not bitwise equality; the interval equality operator
-     considers two time intervals equal if they have the same
-     duration, whether or not their endpoints are identical.  What this means
-     is that a join using <literal>=</literal> between interval fields would yield different
-     results if implemented as a hash join than if implemented another way,
-     because a large fraction of the pairs that should match will hash to
-     different values and will never be compared by the hash join.  But
-     if the optimizer chose to use a different kind of join, all the pairs
-     that the equality operator says are equal will be found.
-     We don't want that kind of inconsistency, so we don't mark interval
-     equality as hashable.
-    </para>
-
-    <para>
-     There are also machine-dependent ways in which a hash join might fail
-     to do the right thing.  For example, if your data type
-     is a structure in which there may be uninteresting pad bits, it's unsafe
-     to mark the equality operator <literal>HASHES</>.  (Unless, perhaps, you write
-     your other operators to ensure that the unused bits are always zero.)
-     Another example is that the floating-point data types are unsafe for hash
-     joins.  On machines that meet the <acronym>IEEE</> floating-point standard, minus
-     zero and plus zero are different values (different bit patterns) but
-     they are defined to compare equal.  So, if the equality operator on floating-point data types were marked
-     <literal>HASHES</>, a minus zero and a plus zero would probably not be matched up
-     by a hash join, but they would be matched up by any other join process.
-    </para>
-
-    <para>
-     The bottom line is that you should probably only use <literal>HASHES</literal> for
-     equality operators that are (or could be) implemented by <function>memcmp()</function>.
-    </para>
-
-   </sect2>
-
-   <sect2>
-    <title>MERGES (SORT1, SORT2, LTCMP, GTCMP)</title>
-
-    <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 binary operators that
-     return <literal>boolean</>, and in practice the operator must represent
-     equality for some datatype or pair of datatypes.
-    </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 unlike hash join, where the left and right
-     data types had better be the same (or at least bitwise equivalent),
-     it is possible to merge-join two
-     distinct data types so long as they are logically compatible.  For
-     example, the <type>int2</type>-versus-<type>int4</type> equality operator
-     is mergejoinable.
-     We only need sorting operators that will bring both data types into a
-     logically compatible sequence.
-    </para>
-
-    <para>
-     Execution of a merge join requires that the system be able to identify
-     four operators related to the mergejoin equality operator: less-than
-     comparison for the left input datatype, less-than comparison for the
-     right input datatype, less-than comparison between the two datatypes, and
-     greater-than comparison between the two datatypes.  (These are actually
-     four distinct operators if the mergejoinable operator has two different
-     input datatypes; but when the input types are the same the three
-     less-than operators are all the same operator.)
-     It is possible to
-     specify these operators individually by name, as the <literal>SORT1</>,
-     <literal>SORT2</>, <literal>LTCMP</>, and <literal>GTCMP</> options
-     respectively.  The system will fill in the default names
-     <literal>&lt;</>, <literal>&lt;</>, <literal>&lt;</>, <literal>&gt;</>
-     respectively if any of these are omitted when <literal>MERGES</> is
-     specified.  Also, <literal>MERGES</> will be assumed to be implied if any
-     of these four operator options appear, so it is possible to specify
-     just some of them and let the system fill in the rest.
-    </para>
-
-    <para>
-     The input datatypes of the four comparison operators can be deduced
-     from the input types of the mergejoinable operator, so just as with
-     <literal>COMMUTATOR</>, only the operator names need be given in these
-     clauses.  Unless you are using peculiar choices of operator names,
-     it's sufficient to write <literal>MERGES</> and let the system fill in
-     the details.
-     (As with <literal>COMMUTATOR</> and <literal>NEGATOR</>, the system is
-     able to make dummy
-     operator entries if you happen to define the equality operator before
-     the other ones.)
-    </para>
-
-    <para>
-     There are additional restrictions on operators that you mark
-     mergejoinable.  These restrictions are not currently checked by
-     <command>CREATE OPERATOR</command>, but errors may occur when
-     the operator is used if any are not true:
-
-     <itemizedlist>
-      <listitem>
-       <para>
-	A mergejoinable equality operator must have a mergejoinable
-        commutator (itself if the two data types are the same, or a related
-        equality operator if they are different).
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        If there is a mergejoinable operator relating any two data types
-	A and B, and another mergejoinable operator relating B to any
-	third data type C, then A and C must also have a mergejoinable
-	operator; in other words, having a mergejoinable operator must
-	be transitive.
-       </para>
-      </listitem>
-
-      <listitem>
-       <para>
-        Bizarre results will ensue at runtime if the four comparison
-	operators you name do not sort the data values compatibly.
-       </para>
-      </listitem>
-     </itemizedlist>
-    </para>
-
-    <note>
-    <para>
-     In <ProductName>PostgreSQL</ProductName> versions before 7.3,
-     the <literal>MERGES</> shorthand was not available: to make a
-     mergejoinable operator one had to write both <literal>SORT1</> and
-     <literal>SORT2</> explicitly.  Also, the <literal>LTCMP</> and
-     <literal>GTCMP</>
-     options did not exist; the names of those operators were hardwired as
-     <literal>&lt;</> and <literal>&gt;</> respectively.
-    </para>
-    </note>
-
-   </sect2>
-
-  </sect1>
- </Chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/xplang.sgml b/doc/src/sgml/xplang.sgml
deleted file mode 100644
index 9accf8daa76..00000000000
--- a/doc/src/sgml/xplang.sgml
+++ /dev/null
@@ -1,179 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/xplang.sgml,v 1.17 2002/01/07 02:29:14 petere Exp $
--->
-
- <chapter id="xplang">
-  <title id="xplang-title">Procedural Languages</title>
-
-  <sect1 id="xplang-intro">
-   <title>Introduction</title>
-
-  <para>
-   <productname>PostgreSQL</productname> allows users to add new
-   programming languages to be available for writing functions and
-   procedures.  These are called <firstterm>procedural
-   languages</firstterm> (PL).  In the case of a function or trigger
-   procedure 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
-   <productname>PostgreSQL</productname> and an existing implementation
-   of a programming language.  The handler itself is a special
-   programming language function compiled into a shared object and
-   loaded on demand.
-  </para>
-
-  <para>
-   Writing a handler for a new procedural language is described in
-   <xref linkend="xfunc-plhandler">.  Several procedural languages are
-   available in the standard <productname>PostgreSQL</productname>
-   distribution, which can serve as examples.
-  </para>
-  </sect1>
-
-  <sect1 id="xplang-install">
-   <title>Installing Procedural Languages</title>
-
-   <para>
-    A procedural language must be <quote>installed</quote> into each
-    database where it is to be used.  But procedural languages installed in
-    the template1 database are automatically available in all
-    subsequently created databases. 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, the
-    shell script <filename>createlang</filename> may be used instead
-    of carrying out the details by hand.  For example, to install <application>PL/pgSQL</application>
-    into the template1 database, use
-<programlisting>
-createlang plpgsql template1
-</programlisting>
-    The manual procedure described below is only recommended for
-    installing custom languages that <filename>createlang</filename>
-    does not know about.
-   </para>
-
-   <procedure>
-    <title>
-     Manual Procedural Language Installation
-    </title>
-
-    <para>
-     A procedural language is installed in the database in three
-     steps, which must be carried out by a database superuser.
-    </para>
-
-    <step performance="required">
-     <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">.
-     </para>
-    </step>
-
-    <step performance="required" id="xplang-install-cr1">
-     <para>
-      The handler must be declared with the command
-<synopsis>
-CREATE FUNCTION <replaceable>handler_function_name</replaceable> ()
-    RETURNS OPAQUE AS
-    '<replaceable>path-to-shared-object</replaceable>' LANGUAGE C;
-</synopsis>
-      The special return type of <type>OPAQUE</type> tells
-      the database 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="required" id="xplang-install-cr2">
-     <para>
-      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>;
-</synopsis>
-      The optional key word <literal>TRUSTED</literal> tells whether
-      ordinary database users that have no superuser privileges should
-      be allowed to use this language to 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>,
-      <application>PL/Perl</application>, and
-      <application>PL/Python</application> are known to be trusted;
-      the languages <application>PL/TclU</application> and
-      <application>PL/PerlU</application> are designed to provide
-      unlimited functionality should <emphasis>not</emphasis> be
-      marked trusted.
-     </para>
-    </step>
-   </procedure>
-
-   <para>
-    In a default <productname>PostgreSQL</productname> installation,
-    the handler for the <application>PL/pgSQL</application> language
-    is built and installed into the <quote>library</quote>
-    directory. If Tcl/Tk support is configured in, the handlers for
-    PL/Tcl and PL/TclU are also built and installed in the same
-    location.  Likewise, the PL/Perl and PL/PerlU handlers are built
-    and installed if Perl support is configured, and PL/Python is
-    installed if Python support is configured.  The
-    <filename>createlang</filename> script automates <xref
-    linkend="xplang-install-cr1"> and <xref
-    linkend="xplang-install-cr2"> described above.
-   </para>
-
-   <example>
-    <title>Manual Installation of <application>PL/pgSQL</application></title>
-
-     <para>
-      The following command tells the database server where to find the 
-      shared object for the <application>PL/pgSQL</application> language's call handler function.
-
-<programlisting>
-CREATE FUNCTION plpgsql_call_handler () RETURNS OPAQUE AS
-    '$libdir/plpgsql' LANGUAGE C;
-</programlisting>
-     </para>
-
-     <para>
-      The command
-<programlisting>
-CREATE TRUSTED PROCEDURAL LANGUAGE plpgsql
-    HANDLER plpgsql_call_handler;
-</programlisting>
-      then defines that the previously declared call handler function
-      should be invoked for functions and trigger procedures where the
-      language attribute is <literal>plpgsql</literal>.
-     </para>
-  </example>
-
-  </sect1>
-
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/xtypes.sgml b/doc/src/sgml/xtypes.sgml
deleted file mode 100644
index 9886e7a3c33..00000000000
--- a/doc/src/sgml/xtypes.sgml
+++ /dev/null
@@ -1,207 +0,0 @@
- <chapter id="xtypes">
-  <title>Extending <acronym>SQL</acronym>: Types</title>
-
-  <indexterm zone="xtypes">
-   <primary>data types</primary>
-   <secondary>extending</secondary>
-  </indexterm>
-
- <comment>
-  This chapter needs to be updated for the version-1 function manager
-  interface.
- </comment>
-
-  <para>
-   As previously mentioned, there are two kinds of types in
-   <productname>PostgreSQL</productname>: base types (defined in a
-   programming language) and composite types. This chapter describes
-   how to define new base types.
-  </para>
-
-  <para>
-   The examples in this section can be found in
-   <filename>complex.sql</filename> and <filename>complex.c</filename>
-   in the tutorial directory.  Composite examples are in
-   <filename>funcs.sql</filename>.
-  </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 input and returns the internal (in memory) representation of
-  the type.  The output function takes the internal representation of
-  the type and returns a null-terminated character string.
- </para>
-
- <para>
-  Suppose we want to define a complex type which represents complex
-  numbers. Naturally, we would choose to represent a complex in memory
-  as the following <acronym>C</acronym> structure:
-
-<programlisting>
-typedef struct Complex {
-    double      x;
-    double      y;
-} Complex;
-</programlisting>
-
-  and  a  string of the form <literal>(x,y)</literal> as the external string
-  representation.
- </para>
-
- <para>
-  The functions are usually not hard to write, especially the output
-  function.  However, there are a number of points to remember:
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     When defining your external (string) representation, remember
-     that you must eventually write a complete and robust parser for
-     that representation as your input function!
-    </para>
-
-    <para>
-     For instance:
-
-<programlisting>
-Complex *
-complex_in(char *str)
-{
-    double x, y;
-    Complex *result;
-    if (sscanf(str, " ( %lf , %lf )", &amp;x, &amp;y) != 2) {
-        elog(ERROR, "complex_in: error in parsing %s", str);
-        return NULL;
-    }
-    result = (Complex *)palloc(sizeof(Complex));
-    result-&gt;x = x;
-    result-&gt;y = y;
-    return (result);
-}
-</programlisting>
-    </para>
-
-    <para>
-     The output function can simply be:
-
-<programlisting>
-char *
-complex_out(Complex *complex)
-{
-    char *result;
-    if (complex == NULL)
-        return(NULL);
-    result = (char *) palloc(60);
-    sprintf(result, "(%g,%g)", complex-&gt;x, complex-&gt;y);
-    return(result);
-}
-</programlisting>
-
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     You should try 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
-     (say, into someone else's database on another computer).  This is
-     a particularly common problem when floating-point numbers are
-     involved.
-    </para>
-   </listitem>
-  </itemizedlist>
- </para>
-
- <para>
-  To define the <type>complex</type> type, we need to create the two
-  user-defined functions <function>complex_in</function> and
-  <function>complex_out</function> before creating the type:
-
-<programlisting>
-CREATE FUNCTION complex_in(opaque)
-    RETURNS complex
-    AS '<replaceable>PGROOT</replaceable>/tutorial/complex'
-    LANGUAGE C;
-
-CREATE FUNCTION complex_out(opaque)
-    RETURNS opaque
-    AS '<replaceable>PGROOT</replaceable>/tutorial/complex'
-    LANGUAGE C;
-</programlisting>
- </para>
-
- <para>
-  Finally, we can declare the data type:
-<programlisting>
-CREATE TYPE complex (
-    internallength = 16,
-    input = complex_in,
-    output = complex_out
-);
-</programlisting>
- </para>
-
- <para>
-  <indexterm>
-   <primary>arrays</primary>
-  </indexterm>
-  As discussed earlier, <productname>PostgreSQL</productname> fully
-  supports arrays of base types.  Additionally,
-  <productname>PostgreSQL</productname> supports arrays of
-  user-defined types as well.  When you define a type,
-  <productname>PostgreSQL</productname> automatically provides support
-  for arrays of that type.  For historical reasons, the array type has
-  the same name as the user-defined type with the underscore character
-  <literal>_</> prepended.
- </para>
-
- <para>
-  Composite types do not need any function defined on them, since the
-  system already understands what they look like inside.
- </para>
-
- <para>
-  <indexterm>
-   <primary>TOAST</primary>
-   <secondary>and user-defined types</secondary>
-  </indexterm>
-  If the values of your data type might exceed a few hundred bytes in
-  size (in internal form), you should be careful to mark them
-  TOAST-able.  To do this, the internal representation must follow the
-  standard layout for variable-length data: the first four bytes must
-  be an <type>int32</type> containing the total length in bytes of the
-  datum (including itself).  Then, all your functions that accept
-  values of the type must be careful to call
-  <function>pg_detoast_datum()</function> on the supplied values ---
-  after checking that the value is not NULL, if your function is not
-  strict.  Finally, select the appropriate storage option when giving
-  the <command>CREATE TYPE</command> command.
- </para>
-</chapter>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
diff --git a/doc/src/sgml/y2k.sgml b/doc/src/sgml/y2k.sgml
deleted file mode 100644
index 60ad62e51ed..00000000000
--- a/doc/src/sgml/y2k.sgml
+++ /dev/null
@@ -1,95 +0,0 @@
-<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/Attic/y2k.sgml,v 1.14 2002/01/08 20:03:58 momjian Exp $
--->
-
-<sect1 id="y2k">
- <title>Y2K Statement</title>
-
- <note>
-  <title>Author</title>
-
-  <para>
-   Written by Thomas Lockhart
-   (<email>lockhart@fourpalms.org</email>)
-   on 1998-10-22. Updated 2000-03-31.
-  </para>
- </note>
-
- <para>
-  The <productname>PostgreSQL</productname> Global Development Group provides
-  the <productname>PostgreSQL</productname> software code tree as a public service,
-  without warranty and without liability for its behavior or performance.
-  However, at the time of writing:
- </para>
-
- <itemizedlist>
-  <listitem>
-   <para>
-    The author of this statement, a volunteer on the
-    <productname>PostgreSQL</productname>
-    support team since November, 1996, is not aware of 
-    any problems in the <productname>PostgreSQL</productname> code base related
-    to time transitions around Jan 1, 2000 (Y2K).
-   </para>
-  </listitem>
-
-  <listitem>
-   <para>
-    The author of this statement is not aware of any reports of Y2K problems 
-    uncovered in regression testing
-    or in other field use of recent or current versions
-    of <productname>PostgreSQL</productname>. We might have expected
-    to hear about problems if they existed, given the installed base and
-    the active participation of users on the support mailing lists.
-   </para>
-  </listitem>
-
-  <listitem>
-   <para>
-    To the best of the author's knowledge, the
-    assumptions <productname>PostgreSQL</productname>
-    makes about dates specified with a two-digit year
-    are documented in the current <citetitle>User's Guide</citetitle>
-    in the chapter on data types.
-    For two-digit years, the significant transition year is 1970, not 2000;
-    e.g. <literal>70-01-01</literal> is interpreted as 1970-01-01,
-    whereas <literal>69-01-01</literal> is interpreted as 2069-01-01.
-   </para>
-  </listitem>
-
-  <listitem>
-   <para>
-    Any Y2K problems in the underlying OS related to obtaining the
-    <quote>current time</quote> may propagate into apparent Y2K problems in
-    <productname>PostgreSQL</productname>.
-   </para>
-  </listitem>
- </itemizedlist>
-
- <para>
-  Refer to 
-  <ulink url="http://www.gnu.org/software/year2000.html">The GNU Project</ulink>
-  and
-  <ulink url="http://language.perl.com/news/y2k.html">The Perl Institute</ulink>
-  for further discussion of Y2K issues, particularly
-  as it relates to open source, no fee software.
- </para>
-
-</sect1>
-
-<!-- Keep this comment at the end of the file
-Local variables:
-mode:sgml
-sgml-omittag:nil
-sgml-shorttag:t
-sgml-minimize-attributes:nil
-sgml-always-quote-attributes:t
-sgml-indent-step:1
-sgml-indent-data:t
-sgml-parent-document:nil
-sgml-default-dtd-file:"./reference.ced"
-sgml-exposed-tags:nil
-sgml-local-catalogs:("/usr/lib/sgml/catalog")
-sgml-local-ecat-files:nil
-End:
--->
-- 
cgit v1.2.3