From b6ea172acee95d98c309819b5884a561e5d1def0 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Fri, 22 Mar 2002 19:20:45 +0000 Subject: [PATCH] Spell checking and markup additions --- doc/src/sgml/bki.sgml | 8 +- doc/src/sgml/catalogs.sgml | 26 +++---- doc/src/sgml/charset.sgml | 4 +- doc/src/sgml/client-auth.sgml | 6 +- doc/src/sgml/datatype.sgml | 38 +++++----- doc/src/sgml/datetime.sgml | 20 ++--- doc/src/sgml/docguide.sgml | 26 +++---- doc/src/sgml/func.sgml | 8 +- doc/src/sgml/indexcost.sgml | 4 +- doc/src/sgml/jdbc.sgml | 6 +- doc/src/sgml/libpgtcl.sgml | 4 +- doc/src/sgml/libpq++.sgml | 4 +- doc/src/sgml/libpq.sgml | 4 +- doc/src/sgml/monitoring.sgml | 4 +- doc/src/sgml/nls.sgml | 8 +- doc/src/sgml/odbc.sgml | 32 ++++---- doc/src/sgml/perform.sgml | 12 +-- doc/src/sgml/plpython.sgml | 4 +- doc/src/sgml/plsql.sgml | 46 ++++++------ doc/src/sgml/pltcl.sgml | 4 +- doc/src/sgml/protocol.sgml | 4 +- doc/src/sgml/ref/alter_user.sgml | 4 +- doc/src/sgml/ref/copy.sgml | 4 +- doc/src/sgml/ref/create_function.sgml | 4 +- doc/src/sgml/ref/create_index.sgml | 16 ++-- doc/src/sgml/ref/create_operator.sgml | 4 +- doc/src/sgml/ref/create_rule.sgml | 6 +- doc/src/sgml/ref/create_sequence.sgml | 4 +- doc/src/sgml/ref/create_table.sgml | 4 +- doc/src/sgml/ref/explain.sgml | 4 +- doc/src/sgml/ref/pg_ctl-ref.sgml | 10 +-- doc/src/sgml/ref/pg_dump.sgml | 102 ++++++++++++------------- doc/src/sgml/ref/pg_restore.sgml | 104 +++++++++++++------------- doc/src/sgml/ref/postgres-ref.sgml | 44 +++++------ doc/src/sgml/ref/postmaster.sgml | 4 +- doc/src/sgml/ref/psql-ref.sgml | 18 ++--- doc/src/sgml/ref/reindex.sgml | 4 +- doc/src/sgml/ref/select.sgml | 8 +- doc/src/sgml/release.sgml | 46 ++++++------ doc/src/sgml/rules.sgml | 4 +- doc/src/sgml/runtime.sgml | 6 +- doc/src/sgml/spi.sgml | 14 ++-- doc/src/sgml/syntax.sgml | 4 +- doc/src/sgml/trigger.sgml | 15 ++-- doc/src/sgml/xfunc.sgml | 9 +-- doc/src/sgml/xoper.sgml | 4 +- doc/src/sgml/xtypes.sgml | 2 +- 47 files changed, 360 insertions(+), 360 deletions(-) diff --git a/doc/src/sgml/bki.sgml b/doc/src/sgml/bki.sgml index 75d32e42cb..4ea0f5f92b 100644 --- a/doc/src/sgml/bki.sgml +++ b/doc/src/sgml/bki.sgml @@ -1,5 +1,5 @@ @@ -23,7 +23,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/bki.sgml,v 1.9 2001/11/21 22:57:01 tgl Exp part of building and installing PostgreSQL by a program named genbki.sh from some specially formatted C header files in the source tree. The created - BKI file is called postgres.bki and is + BKI file is called postgres.bki and is normally installed in the share subdirectory of the installation tree. @@ -46,7 +46,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/bki.sgml,v 1.9 2001/11/21 22:57:01 tgl Exp - BKI input consists of a sequence of commands. Commands are made up + BKI 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 @@ -64,7 +64,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/bki.sgml,v 1.9 2001/11/21 22:57:01 tgl Exp - BKI Commands + <acronym>BKI</acronym> Commands diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index 5db408f6d0..b72b083617 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -1,6 +1,6 @@ @@ -222,7 +222,7 @@ aggbasetype oid pg_type.oid - The input datatype for this aggregate function + The input data type for this aggregate function aggtranstype @@ -386,8 +386,8 @@ of statistics accumulated for this column by ANALYZE. A zero value indicates that no statistics should be collected. - The exact meaning of positive values is datatype-dependent. - For scalar datatypes, attstattarget + The exact meaning of positive values is data type-dependent. + For scalar data types, attstattarget is both the target number of most common values to collect, and the target number of histogram bins to create. @@ -533,7 +533,7 @@ pg_class - pg_class catalogues tables and mostly + pg_class catalogs tables and mostly everything else that has columns or is otherwise similar to a table. This includes indexes (but see also pg_index), sequences, views, and some @@ -584,7 +584,7 @@ relam oid pg_am.oid - If this is an index, the access method used (btree, hash, etc.) + If this is an index, the access method used (B-tree, hash, etc.) @@ -624,7 +624,7 @@ oid pg_class.oid - Oid of the TOAST table associated with this table, 0 if none. + OID of the TOAST table associated with this table, 0 if none. The TOAST table stores large attributes out of line in a secondary table. @@ -909,7 +909,7 @@ The pg_description table can store an optional description or comment for each database object. Descriptions can be manipulated with the COMMENT command. Client applications - can view the descriptions by joining with this table. Many builtin + can view the descriptions by joining with this table. Many built-in system objects have comments associated with them that are shown by psql's \d commands. @@ -1648,7 +1648,7 @@ bool Function returns a set (ie, multiple values of the specified - datatype) + data type) @@ -2128,7 +2128,7 @@ Column data values of the appropriate kind for the Nth slot, or NULL if the slot kind does not store any data values. - For datatype independence, all column data values are converted + For data-type independence, all column data values are converted to external textual form and stored as TEXT datums. @@ -2271,7 +2271,7 @@ pg_type - This catalog stores information about datatypes. Scalar types + This catalog stores information about data types. Scalar types (base types) are created with CREATE TYPE. 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 @@ -2369,7 +2369,7 @@ Character that separates two values of this type when parsing array input. Note that the delimiter is associated with the array - element datatype, not the array datatype. + element data type, not the array data type. @@ -2402,7 +2402,7 @@ name and oidvector. If a fixed-length type has a typelem then its internal representation must be N values of the - typelem datatype with no other data. + typelem data type with no other data. Variable-length array types have a header defined by the array subroutines. diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index a5f1506145..29cc7e528e 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -1,4 +1,4 @@ - + Localization</> @@ -178,7 +178,7 @@ export LANG=sv_SE by recording the values of <envar>LC_COLLATE</> and <envar>LC_CTYPE</> that are seen by <application>initdb</>. The server automatically adopts those two values when it is started; only the other <envar>LC_</> - categories can be set from the environment at server startup. + categories can be set from the environment at server start-up. In short, only one collation order can be used in a database cluster, and it is chosen at <application>initdb</> time. </para> diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index 0f0b2eeac6..76542f9872 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.32 2002/01/20 22:19:55 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.33 2002/03/22 19:20:06 petere Exp $ --> <chapter id="client-authentication"> @@ -366,7 +366,7 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable <indexterm> <primary>SIGHUP</primary> </indexterm> - The <filename>pg_hba.conf</filename> file is read on startup + 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</> @@ -750,7 +750,7 @@ local all md5 admins <indexterm> <primary>SIGHUP</primary> </indexterm> - The <filename>pg_ident.conf</filename> file is read on startup + 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</> diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 4738954ab7..a792d52e42 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.85 2002/03/05 06:14:45 momjian Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.86 2002/03/22 19:20:07 petere Exp $ --> <chapter id="datatype"> @@ -1522,31 +1522,31 @@ SELECT b, char_length(b) FROM test2; </thead> <tbody> <row> - <entry>04:05:06.789</entry> + <entry><literal>04:05:06.789</literal></entry> <entry>ISO 8601</entry> </row> <row> - <entry>04:05:06</entry> + <entry><literal>04:05:06</literal></entry> <entry>ISO 8601</entry> </row> <row> - <entry>04:05</entry> + <entry><literal>04:05</literal></entry> <entry>ISO 8601</entry> </row> <row> - <entry>040506</entry> + <entry><literal>040506</literal></entry> <entry>ISO 8601</entry> </row> <row> - <entry>04:05 AM</entry> + <entry><literal>04:05 AM</literal></entry> <entry>Same as 04:05; AM does not affect value</entry> </row> <row> - <entry>04:05 PM</entry> + <entry><literal>04:05 PM</literal></entry> <entry>Same as 16:05; input hour must be <= 12</entry> </row> <row> - <entry>allballs</entry> + <entry><literal>allballs</literal></entry> <entry>Same as 00:00:00</entry> </row> </tbody> @@ -1811,39 +1811,39 @@ January 8 04:05:06 1999 PST </thead> <tbody> <row> - <entry>epoch</entry> + <entry><literal>epoch</literal></entry> <entry>1970-01-01 00:00:00+00 (Unix system time zero)</entry> </row> <row> - <entry>infinity</entry> + <entry><literal>infinity</literal></entry> <entry>Later than other valid times</entry> </row> <row> - <entry>-infinity</entry> + <entry><literal>-infinity</literal></entry> <entry>Earlier than other valid times</entry> </row> <row> - <entry>invalid</entry> + <entry><literal>invalid</literal></entry> <entry>Illegal entry</entry> </row> <row> - <entry>now</entry> + <entry><literal>now</literal></entry> <entry>Current transaction time</entry> </row> <row> - <entry>today</entry> + <entry><literal>today</literal></entry> <entry>Midnight today</entry> </row> <row> - <entry>tomorrow</entry> + <entry><literal>tomorrow</literal></entry> <entry>Midnight tomorrow</entry> </row> <row> - <entry>yesterday</entry> + <entry><literal>yesterday</literal></entry> <entry>Midnight yesterday</entry> </row> <row> - <entry>zulu, allballs, z</entry> + <entry><literal>zulu</>, <literal>allballs</>, <literal>z</></entry> <entry>00:00:00.00 GMT</entry> </row> </tbody> @@ -2083,7 +2083,7 @@ January 8 04:05:06 1999 PST </listitem> <listitem> <para> - The <envar>PGTZ</envar> environment variable, if set at the client, is used by libpq + 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> @@ -2117,7 +2117,7 @@ January 8 04:05:06 1999 PST <note> <para> - If the runtime option <literal>AUSTRALIAN_TIMEZONES</literal> is set + 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> diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml index 2bafee8853..47f857af8b 100644 --- a/doc/src/sgml/datetime.sgml +++ b/doc/src/sgml/datetime.sgml @@ -1,5 +1,5 @@ <!-- -$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.26 2002/01/20 22:19:55 petere Exp $ +$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.27 2002/03/22 19:20:07 petere Exp $ Date/time details --> @@ -150,31 +150,31 @@ Date/time details </thead> <tbody> <row> - <entry>ABSTIME</entry> + <entry><literal>ABSTIME</literal></entry> <entry>Keyword ignored</entry> </row> <row> - <entry>AM</entry> + <entry><literal>AM</literal></entry> <entry>Time is before 12:00</entry> </row> <row> - <entry>AT</entry> + <entry><literal>AT</literal></entry> <entry>Keyword ignored</entry> </row> <row> - <entry>JULIAN, JD, J</entry> + <entry><literal>JULIAN</>, <literal>JD</>, <literal>J</></entry> <entry>Next field is Julian Day</entry> </row> <row> - <entry>ON</entry> + <entry><literal>ON</literal></entry> <entry>Keyword ignored</entry> </row> <row> - <entry>PM</entry> + <entry><literal>PM</literal></entry> <entry>Time is on or after after 12:00</entry> </row> <row> - <entry>T</entry> + <entry><literal>T</literal></entry> <entry>Next field is time</entry> </row> </tbody> @@ -186,7 +186,7 @@ Date/time details 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 <quote>Invalid Abstime</quote>. This is no + 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> @@ -753,7 +753,7 @@ Date/time details </para> <para> - If the runtime option <literal>AUSTRALIAN_TIMEZONES</literal> is set + 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, diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml index 4d975d73b5..7df4995cfb 100644 --- a/doc/src/sgml/docguide.sgml +++ b/doc/src/sgml/docguide.sgml @@ -1,4 +1,4 @@ -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.40 2002/01/20 22:19:55 petere Exp $ --> +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.41 2002/03/22 19:20:08 petere Exp $ --> <appendix id="docguide"> <title>Documentation @@ -116,7 +116,7 @@ - Toolsets + Tool Sets The following tools are used to process the documentation. Some @@ -304,7 +304,7 @@ apt-get install docbook-stylesheets 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 reasonabley standard + We describe here only a standard setup, with reasonably standard installation paths, and no fancy features. For details, you should study the documentation of the respective package, and read SGML introductory material. @@ -682,7 +682,7 @@ gmake man The hardcopy Postscript documentation is generated by converting the SGML source code to RTF, then - importing into ApplixWare. + importing into Applixware. After a little cleanup (see the following section) the output is printed to a postscript file. @@ -710,14 +710,14 @@ gmake man - Applixware <acronym>RTF</acronym> Cleanup + <productname>Applixware</productname> <acronym>RTF</acronym> Cleanup jade, 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 ApplixWare folks the symptom was diagnosed and a + from the Applixware folks the symptom was diagnosed and a workaround is available. @@ -759,7 +759,7 @@ gmake man The script adds {\s0 Normal;} as - the zero-th style in the document. According to ApplixWare, the + the zero-th style in the document. According to Applixware, the RTF standard would prohibit adding an implicit zero-th style, though M$Word happens to handle this case. For repairing REFENTRY sections, the script replaces @@ -769,14 +769,14 @@ gmake man - Open a new document in Applix Words and + Open a new document in Applixware Words and then import the RTF file. - Generate a new ToC using ApplixWare. + Generate a new ToC using Applixware. @@ -795,7 +795,7 @@ gmake man first three levels of headers for inclusion in the ToC. This will replace the existing lines imported in the RTF with a native - ApplixWare ToC. + Applixware ToC. @@ -887,7 +887,7 @@ gmake man Insert figures into the document. Center each figure on the page using - the centering margins button on the ApplixWare toolbar. + the centering margins button on the Applixware toolbar. @@ -969,7 +969,7 @@ Later stylesheets seem to not need this adjustment - thomas 2001-11-29 - Save the document as native Applix Words format to allow easier last + Save the document as native Applixware Words format to allow easier last minute editing later. @@ -1110,7 +1110,7 @@ Later stylesheets seem to not need this adjustment - thomas 2001-11-29 SGML and DocBook do not suffer from an oversupply of open-source authoring tools. The - most common toolset is the + most common tool set is the Emacs/XEmacs editor with appropriate editing mode. On some systems these tools are provided in a typical full installation. diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 56c7b6ac05..c62394e914 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -1,5 +1,5 @@ @@ -3592,13 +3592,13 @@ SELECT TIMESTAMP 'now'; lseg(box) lseg - box diagonal to lseg + box diagonal to lseg lseg(box '((-1,0),(1,0))') lseg(point, point) lseg - points to lseg + points to lseg lseg(point '(-1,0)', point '(1,0)') @@ -3773,7 +3773,7 @@ SELECT TIMESTAMP 'now'; set_masklen(inet,integer) inet - set netmask length for inet value + set netmask length for inet value set_masklen('192.168.1.5/24',16) 192.168.1.5/16 diff --git a/doc/src/sgml/indexcost.sgml b/doc/src/sgml/indexcost.sgml index af66a9f94a..c30be63166 100644 --- a/doc/src/sgml/indexcost.sgml +++ b/doc/src/sgml/indexcost.sgml @@ -1,5 +1,5 @@ @@ -201,7 +201,7 @@ amcostestimate (Query *root, 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 clauselist_selectivity(): + knowledge, use the standard optimizer function clauselist_selectivity(): *indexSelectivity = clauselist_selectivity(root, indexQuals, diff --git a/doc/src/sgml/jdbc.sgml b/doc/src/sgml/jdbc.sgml index 241be88054..c77817d16a 100644 --- a/doc/src/sgml/jdbc.sgml +++ b/doc/src/sgml/jdbc.sgml @@ -1,5 +1,5 @@ @@ -1210,7 +1210,7 @@ public void addFunctions(ResultSet rs) throws SQLException - Do not think that manually converting them to the oid's will + 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 @@ -2505,7 +2505,7 @@ public void unlink(int oid) throws SQLException - Using the driver in a multi-threaded or a servlet environment + Using the driver in a multithreaded or a servlet environment A problem with many JDBC drivers is that only diff --git a/doc/src/sgml/libpgtcl.sgml b/doc/src/sgml/libpgtcl.sgml index a6ebe9bf5a..7257062c00 100644 --- a/doc/src/sgml/libpgtcl.sgml +++ b/doc/src/sgml/libpgtcl.sgml @@ -1173,7 +1173,7 @@ pg_lo_creat conn -The oid of the large object created. +The OID of the large object created. @@ -1247,7 +1247,7 @@ pg_lo_open conn objOid -Specifies a valid large object oid. +Specifies a valid large object OID. diff --git a/doc/src/sgml/libpq++.sgml b/doc/src/sgml/libpq++.sgml index b5a24e0e2e..cd6d2a6a91 100644 --- a/doc/src/sgml/libpq++.sgml +++ b/doc/src/sgml/libpq++.sgml @@ -1,5 +1,5 @@ @@ -139,7 +139,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpq++.sgml,v 1.40 2002/01/07 02:29: - PGOPTIONS sets additional runtime options for + PGOPTIONS sets additional run-time options for the PostgreSQL backend. diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 843e96be88..1fb6519806 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,5 +1,5 @@ @@ -2056,7 +2056,7 @@ used if Kerberos authentication is selected by the backend. -PGOPTIONS sets additional runtime options for +PGOPTIONS sets additional run-time options for the PostgreSQL backend. diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index 882a98382f..88b7e29a92 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -1,5 +1,5 @@ @@ -132,7 +132,7 @@ postgres: user database host STATS_COMMAND_STRING, STATS_BLOCK_LEVEL, and STATS_ROW_LEVEL control how much information is - actually sent to the collector, and thus determine how much runtime + 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 diff --git a/doc/src/sgml/nls.sgml b/doc/src/sgml/nls.sgml index 8bef35c572..75dc5859cd 100644 --- a/doc/src/sgml/nls.sgml +++ b/doc/src/sgml/nls.sgml @@ -1,4 +1,4 @@ - + @@ -141,7 +141,7 @@ msgstr "another translated" Creating and maintaining message catalogs - Okay, so how does one create a blank message + OK, so how does one create a blank message catalog? First, go into the directory that contains the program whose messages you want to translate. If there is a file nls.mk, then this program has been prepared @@ -312,7 +312,7 @@ msgstr "Die Datei %2$s hat %1$u Zeichen." - Insert this code into the startup sequence of the program: + Insert this code into the start-up sequence of the program: #ifdef ENABLE_NLS #include <locale.h> @@ -473,7 +473,7 @@ printf("number of copied files: %d", n); 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 occurrance of the string with a comment that starts + precede the occurrence of the string with a comment that starts with translator, e.g., /* translator: This message is not what it seems to be. */ diff --git a/doc/src/sgml/odbc.sgml b/doc/src/sgml/odbc.sgml index af6e2a8aef..cbc4062476 100644 --- a/doc/src/sgml/odbc.sgml +++ b/doc/src/sgml/odbc.sgml @@ -1,5 +1,5 @@ @@ -328,14 +328,14 @@ InstallDir = /opt/applix/axdata/axshlib <application>ApplixWare</application> - ApplixWare + Applixware - ApplixWare has an + Applixware has an ODBC database interface supported on at least some platforms. - ApplixWare 4.4.2 has been + Applixware 4.4.2 has been demonstrated under Linux with PostgreSQL 7.0 using the psqlODBC driver contained in the PostgreSQL distribution. @@ -345,18 +345,18 @@ InstallDir = /opt/applix/axdata/axshlib Configuration - ApplixWare must be configured correctly + Applixware must be configured correctly in order for it to be able to access the PostgreSQL ODBC software drivers. - Enabling <application>ApplixWare</application> Database Access + Enabling <application>Applixware</application> Database Access These instructions are for the 4.4.2 release of - ApplixWare on Linux. + Applixware on Linux. Refer to the Linux Sys Admin on-line book for more detailed information. @@ -367,7 +367,7 @@ InstallDir = /opt/applix/axdata/axshlib elfodbc can find libodbc.so (the ODBC driver manager) shared library. - This library is included with the ApplixWare distribution, + This library is included with the Applixware distribution, but axnet.cnf needs to be modified to point to the correct location. @@ -425,7 +425,7 @@ TextAsLongVarchar=0 - Testing <application>ApplixWare</application> ODBC Connections + Testing <application>Applixware</application> ODBC Connections @@ -550,7 +550,7 @@ TextAsLongVarchar=0 - The September release of ApplixWare 4.4.1 (the first release with official + The September release of Applixware 4.4.1 (the first release with official ODBC support under Linux) shows problems when user names exceed eight (8) characters in length. Problem description contributed by Steve Campbell @@ -583,7 +583,7 @@ TextAsLongVarchar=0 - Debugging <application>ApplixWare</application> ODBC Connections + Debugging <application>Applixware</application> ODBC Connections One good tool for debugging connection problems uses the Unix system @@ -594,7 +594,7 @@ TextAsLongVarchar=0 - Start ApplixWare. + Start Applixware. @@ -631,7 +631,7 @@ cary 27883 0.9 31.0 12692 4596 ? S 10:24 0:04 axmain Note from Cary - Many of the error messages from ApplixWare + Many of the error messages from Applixware go to stderr, but I'm not sure where stderr is sent, so strace is the way to find out. @@ -656,13 +656,13 @@ cary 27883 0.9 31.0 12692 4596 ? S 10:24 0:04 axmain - Running the <application>ApplixWare</application> Demo + Running the <application>Applixware</application> Demo I think the condition this refers to is gone. -- petere 2002-01-07 In order to go through the - ApplixWare Data Tutorial, you need to create + Applixware Data Tutorial, 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, @@ -674,7 +674,7 @@ cary 27883 0.9 31.0 12692 4596 ? S 10:24 0:04 axmain - Modifying the <application>ApplixWare</application> Demo + Modifying the <application>Applixware</application> Demo diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml index d4f0c9bcd7..94f49921f7 100644 --- a/doc/src/sgml/perform.sgml +++ b/doc/src/sgml/perform.sgml @@ -1,5 +1,5 @@ @@ -252,7 +252,7 @@ Hash Join (cost=181.22..564.83 rows=49 width=296) 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 runtime accumulated within each plan node + 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: @@ -289,12 +289,12 @@ Total runtime: 30.67 msec - The total runtime shown by EXPLAIN ANALYZE includes - executor startup and shutdown time, as well as time spent processing + The Total runtime shown by EXPLAIN ANALYZE 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 runtime will normally be just a + 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 runtime may be + For INSERT, UPDATE, and DELETE queries, the total run time may be considerably larger, because it includes the time spent processing the output tuples. In these queries, the time for the top plan node essentially is the time spent computing the new tuples and/or locating diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml index e0840c822a..2e38a5c791 100644 --- a/doc/src/sgml/plpython.sgml +++ b/doc/src/sgml/plpython.sgml @@ -1,4 +1,4 @@ - + PL/Python - Python Procedural Language @@ -92,7 +92,7 @@ def __plpython_procedure_myfunc_23456(): return args[0] - where 23456 is the Oid of the function. + where 23456 is the OID of the function. diff --git a/doc/src/sgml/plsql.sgml b/doc/src/sgml/plsql.sgml index b05e965bd4..8e87b41d9b 100644 --- a/doc/src/sgml/plsql.sgml +++ b/doc/src/sgml/plsql.sgml @@ -1,5 +1,5 @@ @@ -392,7 +392,7 @@ url VARCHAR; 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 runtime + 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. @@ -453,7 +453,7 @@ END; - Rowtypes + Row Types @@ -463,7 +463,7 @@ END; A variable of a composite type is called a row - variable (or rowtype variable). Such a variable can hold a + variable (or 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 @@ -487,8 +487,8 @@ END; Only the user-defined attributes of a table row are accessible in a - rowtype variable, not OID or other system attributes (because the - row could be from a view). The fields of the rowtype inherit the + 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 char(n). @@ -504,17 +504,17 @@ END; - Record variables are similar to rowtype variables, but they have no + 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, it has no substructure, and any attempt to access a - field in it will draw a runtime error. + field in it will draw a run-time error. - Note that RECORD is not a true datatype, only a placeholder. + Note that RECORD is not a true data type, only a placeholder. Thus, for example, one cannot declare a function returning RECORD. @@ -711,7 +711,7 @@ CREATE FUNCTION logfunc2 (TEXT) RETURNS TIMESTAMP AS ' PL/pgSQL interpreter casts this string to the timestamp type by calling the text_out() and timestamp_in() - functions for the conversion. So, the computed timestamp is updated + functions for the conversion. So, the computed time stamp is updated on each execution as the programmer expects. @@ -720,7 +720,7 @@ CREATE FUNCTION logfunc2 (TEXT) RETURNS TIMESTAMP AS ' 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 datatype that is present + 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 @@ -766,7 +766,7 @@ CREATE FUNCTION logfunc2 (TEXT) RETURNS TIMESTAMP AS ' converted by the PL/pgSQL interpreter using the result type's output-function and the variable type's input-function. Note that this could potentially - result in runtime errors generated by the input function, if the + 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. @@ -784,7 +784,7 @@ tax := subtotal * 0.06; The result of a SELECT command yielding multiple columns (but - only one row) can be assigned to a record variable, rowtype + only one row) can be assigned to a record variable, row-type variable, or list of scalar variables. This is done by: @@ -802,9 +802,9 @@ SELECT INTO target expressions 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 runtime error + 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 rowtype of the query result columns. + configures itself to the row type of the query result columns. @@ -908,7 +908,7 @@ PERFORM create_mv(''cs_session_page_requests_mv'','' Oftentimes you will want to generate dynamic queries inside your PL/pgSQL functions, that is, - queries that will involve different tables or different datatypes + queries that will involve different tables or different data types each time they are executed. PL/pgSQL's normal attempts to cache plans for queries will not work in such scenarios. To handle this sort of problem, the EXECUTE statement @@ -1034,7 +1034,7 @@ GET DIAGNOSTICS variable = itemROW_COUNT, the number of rows processed by the last SQL query sent down to the SQL engine; and RESULT_OID, - the Oid of the last row inserted by the most recent + the OID of the last row inserted by the most recent SQL query. Note that RESULT_OID is only useful after an INSERT query. @@ -1063,14 +1063,14 @@ RETURN expression; The function terminates and the value of expression will be returned to the upper executor. - The expression's result will be automatically casted into the + The expression's result will be automatically cast into the function's return type as described for assignments. 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 runtime error + the function without hitting a RETURN statement, a run-time error will occur. @@ -1429,7 +1429,7 @@ END LOOP; 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 unintuitive error + 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. @@ -1450,7 +1450,7 @@ END LOOP; use a cursor internally to avoid memory problems.) A more interesting possibility is that a function can return a reference to a cursor that it has set up, allowing the caller to read the rows. This - provides one way of returning a rowset from a function. + provides one way of returning a row set from a function. @@ -1458,7 +1458,7 @@ END LOOP; All access to cursors in PL/pgSQL goes through - cursor variables, which are always of the special datatype + cursor variables, which are always of the special data type refcursor. One way to create a cursor variable is just to declare it as a variable of type refcursor. Another way is to use the cursor declaration syntax, @@ -1482,7 +1482,7 @@ DECLARE curs2 CURSOR FOR SELECT * from tenk1; curs3 CURSOR (key int) IS SELECT * from tenk1 where unique1 = key; - All three of these variables have the datatype refcursor, + All three of these variables have the data type refcursor, but the first may be used with any query, while the second has a fully specified query already bound to it, and the last has a parameterized query bound to it. (key will be diff --git a/doc/src/sgml/pltcl.sgml b/doc/src/sgml/pltcl.sgml index af00cb7332..a6109b0195 100644 --- a/doc/src/sgml/pltcl.sgml +++ b/doc/src/sgml/pltcl.sgml @@ -1,5 +1,5 @@ @@ -120,7 +120,7 @@ CREATE FUNCTION tcl_max (integer, integer) RETURNS integer AS ' if the actual value of an argument is NULL, the corresponding $n variable will be set to an empty string. To detect whether a particular argument is NULL, use the function - argisnull. For example, suppose that we wanted tcl_max + argisnull. For example, suppose that we wanted tcl_max with one null and one non-null argument to return the non-null argument, rather than NULL: diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index f8848a3fe4..06901a8e33 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -1,4 +1,4 @@ - + Frontend/Backend Protocol @@ -67,7 +67,7 @@ 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 startup and authentication exchange, + 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. diff --git a/doc/src/sgml/ref/alter_user.sgml b/doc/src/sgml/ref/alter_user.sgml index 3819bf8d96..d8461c4f4f 100644 --- a/doc/src/sgml/ref/alter_user.sgml +++ b/doc/src/sgml/ref/alter_user.sgml @@ -1,5 +1,5 @@ @@ -189,7 +189,7 @@ ALTER USER username RESET Use to add new users, and to remoe a user. + endterm="SQL-DROPUSER-title"> to remove a user. diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index b4a226876a..a2bbd1c0aa 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -1,5 +1,5 @@ @@ -279,7 +279,7 @@ ERROR: reason - It is recommended that the filename used in COPY + It is recommended that the file name used in COPY always be specified as an absolute path. This is enforced by the backend in the case of COPY TO, but for COPY FROM you do have the option of reading from a file specified diff --git a/doc/src/sgml/ref/create_function.sgml b/doc/src/sgml/ref/create_function.sgml index 25c33c7b6c..c6ee3e25ef 100644 --- a/doc/src/sgml/ref/create_function.sgml +++ b/doc/src/sgml/ref/create_function.sgml @@ -1,5 +1,5 @@ @@ -332,7 +332,7 @@ CREATE TABLE product ( user-defined type complex, and the internal 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 exact pathname to the shared object file). + of specifying the absolute file name to the shared object file). For PostgreSQL to find a type conversion function automatically, the SQL function has to have the same name as the return type, and so overloading is diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index a3f11d8b0e..ed4bb66aad 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -1,5 +1,5 @@ @@ -82,7 +82,7 @@ CREATE [ UNIQUE ] INDEX index_name - BTREE + BTREE an implementation of Lehman-Yao @@ -92,7 +92,7 @@ CREATE [ UNIQUE ] INDEX index_name - RTREE + RTREE implements standard R-trees using Guttman's quadratic split algorithm. @@ -101,7 +101,7 @@ CREATE [ UNIQUE ] INDEX index_name - HASH + HASH an implementation of Litwin's linear hashing. @@ -110,7 +110,7 @@ CREATE [ UNIQUE ] INDEX index_name - GIST + GIST Generalized Index Search Trees. @@ -270,11 +270,11 @@ ERROR: Cannot create index: 'index_name' already exists. All functions and operators used in an index definition must be - cachable, that is, their results must depend only on + cacheable, 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 cachable + user-defined function in an index, remember to mark the function cacheable when you create it. @@ -329,7 +329,7 @@ ERROR: Cannot create index: 'index_name' already exists. - Currently, only the B-tree and gist access methods support multi-column + 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 PostgreSQL). Only B-tree currently supports diff --git a/doc/src/sgml/ref/create_operator.sgml b/doc/src/sgml/ref/create_operator.sgml index 7f33ca47fa..e3b41ec5da 100644 --- a/doc/src/sgml/ref/create_operator.sgml +++ b/doc/src/sgml/ref/create_operator.sgml @@ -1,5 +1,5 @@ @@ -309,7 +309,7 @@ MYBOXES.description !== box '((0,0), (1,1))' 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 hashjoined.) + not be hash-joined.) The HASHES flag indicates to the query optimizer that a hash join may safely be used with this operator. diff --git a/doc/src/sgml/ref/create_rule.sgml b/doc/src/sgml/ref/create_rule.sgml index ab1a8eeba1..c9cc209843 100644 --- a/doc/src/sgml/ref/create_rule.sgml +++ b/doc/src/sgml/ref/create_rule.sgml @@ -1,5 +1,5 @@ @@ -78,7 +78,7 @@ NOTHING condition - Any SQL boolean-condition expression. The condition expression may not + Any SQL conditional expression (returning boolean). The condition expression may not refer to any tables except new and old. @@ -269,7 +269,7 @@ CREATE RULE "_RETtoyemp" AS SELECT * FROM emp; - This attempt to select from EMP will cause + This attempt to select from EMP will cause PostgreSQL to issue an error because the queries cycled too many times: diff --git a/doc/src/sgml/ref/create_sequence.sgml b/doc/src/sgml/ref/create_sequence.sgml index 115b833d49..ae69bf5b2a 100644 --- a/doc/src/sgml/ref/create_sequence.sgml +++ b/doc/src/sgml/ref/create_sequence.sgml @@ -1,5 +1,5 @@ @@ -268,7 +268,7 @@ SELECT * FROM seqname; setting of 10, backend A might reserve values 1..10 and return nextval=1, then backend B might reserve values 11..20 and return nextval=11 before backend - A has generated nextval=2.) Thus, with a cache setting of one it is safe + A has generated nextval=2.) Thus, with a cache setting of one it is safe to assume that nextval values are generated sequentially; with a cache setting greater than one you should only assume that the nextval values are all distinct, not that they are generated purely sequentially. diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml index 0ae9222d0f..671a49d739 100644 --- a/doc/src/sgml/ref/create_table.sgml +++ b/doc/src/sgml/ref/create_table.sgml @@ -1,5 +1,5 @@ @@ -520,7 +520,7 @@ and table_constraint is: accompanied by some descriptive text, such as: ERROR: Relation 'table' already - exists, which occurs at runtime if the table + exists, which occurs at run time if the table specified already exists in the database. diff --git a/doc/src/sgml/ref/explain.sgml b/doc/src/sgml/ref/explain.sgml index d9ed871b28..33c9add453 100644 --- a/doc/src/sgml/ref/explain.sgml +++ b/doc/src/sgml/ref/explain.sgml @@ -1,5 +1,5 @@ @@ -41,7 +41,7 @@ EXPLAIN [ ANALYZE ] [ VERBOSE ] queryANALYZE - Flag to carry out the query and show actual runtimes. + Flag to carry out the query and show actual run times. diff --git a/doc/src/sgml/ref/pg_ctl-ref.sgml b/doc/src/sgml/ref/pg_ctl-ref.sgml index 63b57fc11d..3ef1a1a7a2 100644 --- a/doc/src/sgml/ref/pg_ctl-ref.sgml +++ b/doc/src/sgml/ref/pg_ctl-ref.sgml @@ -1,5 +1,5 @@ @@ -76,7 +76,7 @@ PostgreSQL documentation stopping, or restarting , the PostgreSQL backend server, or displaying the status of a running postmaster. Although the postmaster can be - started manually, pg_ctl encapulates + started manually, pg_ctl encapsulates tasks such as redirecting log output, properly detaching from the terminal and process group, and it provides convenient options for controlled shutdown. @@ -190,7 +190,7 @@ PostgreSQL documentation Specifies the location of the postmaster executable. By default the postmaster is taken from the same - directory as pg_ctl, or failing that, the hard-wired + directory as 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. @@ -291,7 +291,7 @@ PostgreSQL documentation This is almost equivalent to stopping the postmaster and starting it again - except that pg_ctl saves and reuses the command line options that + except that pg_ctl saves and reuses the command line options that were passed to the previously running instance. To restart the postmaster in the simplest form: @@ -308,7 +308,7 @@ PostgreSQL documentation - To restart using port 5433 and disabling fsync after restarting: + To restart using port 5433 and disabling fsync after restarting: $ pg_ctl -o "-F -p 5433" restart diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 0169043e96..f58d3c39f4 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ @@ -138,8 +138,8 @@ PostgreSQL documentation - -a - --data-only + + Dump only the data, not the schema (data definitions). @@ -154,8 +154,8 @@ PostgreSQL documentation - -b - --blobs + + Include large objects in dump. @@ -164,8 +164,8 @@ PostgreSQL documentation - -c - --clean + + Output commands to clean (drop) @@ -181,8 +181,8 @@ PostgreSQL documentation - -C - --create + + Begin the output with a command to create the @@ -200,8 +200,8 @@ PostgreSQL documentation - -d - --inserts + + Dump data as INSERT commands (rather @@ -213,9 +213,9 @@ PostgreSQL documentation - -D - --column-inserts - --attribute-inserts + + + Dump data as INSERT commands with explicit @@ -229,8 +229,8 @@ PostgreSQL documentation - -f file - --file=file + + Send output to the specified file. If this is omitted, the @@ -240,8 +240,8 @@ PostgreSQL documentation - -F format - --format=format + + Selects the format of the output. @@ -289,8 +289,8 @@ PostgreSQL documentation - -i - --ignore-version + + Ignore version mismatch between pg_dump @@ -306,8 +306,8 @@ PostgreSQL documentation - -n - --no-quotes + + Suppress double quotes around identifiers unless absolutely necessary. @@ -320,8 +320,8 @@ PostgreSQL documentation - -N - --quotes + + Include double quotes around identifiers. @@ -331,8 +331,8 @@ PostgreSQL documentation - -o - --oids + + Dump object identifiers (OIDs) for every @@ -344,8 +344,8 @@ PostgreSQL documentation - -O - --no-owner + + Do not output commands to set the @@ -369,8 +369,8 @@ PostgreSQL documentation - -R - --no-reconnect + + Prohibit pg_dump @@ -399,8 +399,8 @@ PostgreSQL documentation - -s - --schema-only + + Dump only the schema (data definitions), no data. @@ -409,8 +409,8 @@ PostgreSQL documentation - -S username - --superuser=username + + The scripts or archives created by pg_dump @@ -422,8 +422,8 @@ PostgreSQL documentation - -t table - --table=table + + Dump data for table only. @@ -432,8 +432,8 @@ PostgreSQL documentation - -v - --verbose + + Specifies verbose mode. @@ -442,9 +442,9 @@ PostgreSQL documentation - -x - --no-privileges - --no-acl + + + Prevent dumping of access privileges (grant/revoke commands). @@ -453,8 +453,8 @@ PostgreSQL documentation - -X use-set-session-authorization - --use-set-session-authorization + + Normally, if a (plain-text mode) script generated by @@ -488,8 +488,8 @@ PostgreSQL documentation - -Z 0..9 - --compress=0..9 + + Specify the compression level to use in archive formats that support @@ -507,8 +507,8 @@ PostgreSQL documentation - -h host - --host=host + + Specifies the host name of the machine on which the @@ -520,8 +520,8 @@ PostgreSQL documentation - -p port - --port=port + + Specifies the Internet TCP/IP port or local Unix domain socket file @@ -534,7 +534,7 @@ PostgreSQL documentation - -U username + Connect as the given user. @@ -543,7 +543,7 @@ PostgreSQL documentation - -W + Force a password prompt. This should happen automatically if diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index b88bb4ae74..c8d0298acc 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -1,4 +1,4 @@ - + @@ -117,8 +117,8 @@ - -a - --data-only + + Restore only the data, no schema (definitions). @@ -127,8 +127,8 @@ - -c - --clean + + Clean (drop) database objects before recreating them. @@ -137,8 +137,8 @@ - -C - --create + + Create the database before restoring into it. @@ -151,8 +151,8 @@ - -d dbname - --dbname=dbname + + Connect to database dbname and restore @@ -162,8 +162,8 @@ - -f filename - --file=filename + + Specify output file for generated script, or for the listing @@ -173,8 +173,8 @@ - -F format - --format=format + + Specify format of the archive. @@ -212,8 +212,8 @@ - -i index - --index=index + + Restore definition for named index only. @@ -222,8 +222,8 @@ - -l - --list + + List the contents of the archive. The output of this command can be used with the option @@ -233,8 +233,8 @@ - -L list-file - --use-list=list-file + + Restore elements in list-file only, and in the @@ -245,8 +245,8 @@ - -N - --orig-order + + Restore items in the original dump order. By default pg_dump will dump items in an order convenient @@ -256,8 +256,8 @@ - -o - --oid-order + + Restore items in the OID order. By default pg_dump will dump items in an order convenient @@ -267,8 +267,8 @@ - -O - --no-owner + + Prevent any attempt to restore original object ownership. Objects will be owned by the user name used @@ -278,8 +278,8 @@ - -P function-name - --function=function-name + + Specify a procedure or function to be restored. @@ -288,8 +288,8 @@ - -r - --rearrange + + Restore items in modified OID order. By default pg_dump will dump items in an order convenient @@ -301,8 +301,8 @@ - -R - --no-reconnect + + While restoring an archive, pg_restore @@ -324,8 +324,8 @@ - -s - --schema-only + + Restore the schema (definitions), no data. Sequence values will be reset. @@ -334,8 +334,8 @@ - -S username - --superuser=username + + Specify the superuser user name to use when disabling triggers and/or setting ownership of schema elements. @@ -345,8 +345,8 @@ - -t table - --table=table + + Restore schema/data for table only. @@ -355,8 +355,8 @@ - -T trigger - --trigger=trigger + + Restore definition of trigger only. @@ -365,8 +365,8 @@ - -v - --verbose + + Specifies verbose mode. @@ -375,9 +375,9 @@ - -x - --no-privileges - --no-acl + + + Prevent restoration of access privileges (grant/revoke commands). @@ -386,8 +386,8 @@ - -X use-set-session-authorization - --use-set-session-authorization + + Normally, if restoring an archive requires altering the @@ -413,8 +413,8 @@ - -h host - --host=host + + Specifies the host name of the machine on which the @@ -426,8 +426,8 @@ - -p port - --port=port + + Specifies the Internet TCP/IP port or local Unix domain socket file @@ -440,7 +440,7 @@ - -U username + Connect as the given user. @@ -449,7 +449,7 @@ - -W + Force a password prompt. This should happen automatically if diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index 93cf8de8bd..cf6f785b86 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,5 +1,5 @@ @@ -79,7 +79,7 @@ PostgreSQL documentation The postgres executable is the actual PostgreSQL server process that processes queries. It is normally not called directly; instead a multi-user server is started. + linkend="app-postmaster"> multiuser server is started. @@ -130,7 +130,7 @@ PostgreSQL documentation Guide for details. Some (safe) options can also be set from the connecting client in an application-dependent way. For example, if the environment variable PGOPTIONS - is set, then libpq-based clients will pass that string to the + is set, then libpq-based clients will pass that string to the server, which will interpret it as postgres command-line options. @@ -144,12 +144,12 @@ PostgreSQL documentation , and - -e + Sets the default date style to European, which @@ -163,21 +163,21 @@ PostgreSQL documentation - -o filename + filename Sends all debugging and error output to filename. If the backend is running under the postmaster, this option is ignored, - and the stderr inherited from the + and the stderr inherited from the postmaster is used. - -P + Ignore system indexes while scanning/updating system tuples. The @@ -188,7 +188,7 @@ PostgreSQL documentation - -s + Print time information and other statistics at the end of each query. @@ -199,7 +199,7 @@ PostgreSQL documentation - -S sort-mem + sort-mem Specifies the amount of memory to be used by internal sorts and hashes @@ -231,7 +231,7 @@ PostgreSQL documentation - -E + Echo all queries. @@ -240,7 +240,7 @@ PostgreSQL documentation - -N + Disables use of newline as a query delimiter. @@ -264,7 +264,7 @@ PostgreSQL documentation - -f { s | i | m | n | h } + { s | i | m | n | h } Forbids the use of particular scan and join methods: @@ -286,7 +286,7 @@ PostgreSQL documentation - -i + Prevents query execution, but shows the plan tree. @@ -295,7 +295,7 @@ PostgreSQL documentation - -O + Allows the structure of system tables to be modified. This is @@ -305,7 +305,7 @@ PostgreSQL documentation - -p database + database Indicates that this server has been started by a @@ -317,7 +317,7 @@ PostgreSQL documentation - -t pa[rser] | pl[anner] | e[xecutor] + pa[rser] | pl[anner] | e[xecutor] Print timing statistics for each query relating to each of the @@ -328,7 +328,7 @@ PostgreSQL documentation - -v protocol + protocol Specifies the version number of the frontend/backend protocol @@ -338,7 +338,7 @@ PostgreSQL documentation - -W seconds + seconds As soon as this option is encountered, the process sleeps for @@ -377,16 +377,16 @@ PostgreSQL documentation But if you use the - To quit the session, type EOF + To quit the session, type EOF (ControlD, usually). If you've - used diff --git a/doc/src/sgml/ref/postmaster.sgml b/doc/src/sgml/ref/postmaster.sgml index 011144c1d5..e5f7113f69 100644 --- a/doc/src/sgml/ref/postmaster.sgml +++ b/doc/src/sgml/ref/postmaster.sgml @@ -1,5 +1,5 @@ @@ -478,7 +478,7 @@ StreamServerPort: cannot bind to port - Named runtime parameters can be set in either of these styles: + Named run-time parameters can be set in either of these styles: $ postmaster -c sort_mem=1234 $ postmaster --sort-mem=1234 diff --git a/doc/src/sgml/ref/psql-ref.sgml b/doc/src/sgml/ref/psql-ref.sgml index 40ba18716c..2dede1c99c 100644 --- a/doc/src/sgml/ref/psql-ref.sgml +++ b/doc/src/sgml/ref/psql-ref.sgml @@ -1,5 +1,5 @@ @@ -66,7 +66,7 @@ PostgreSQL documentation psql is a regular PostgreSQL client application. In order to connect to a database you need to know the - name of your target database, the hostname and port number of the server + name of your target database, the host name and port number of the server and what user name you want to connect as. psql can be told about those parameters via command line options, namely , , , and respectively. @@ -77,9 +77,9 @@ PostgreSQL documentation 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 username, as is the default + 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 username. Your database + 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 PGDATABASE, PGHOST, PGPORT and PGUSER @@ -270,7 +270,7 @@ testdb=> - If the connection attempt failed (wrong username, access denied, etc.), the + If the connection attempt failed (wrong user name, access denied, etc.), the previous connection will be kept if and only if psql is in interactive mode. When executing a non-interactive script, processing will immediately stop with an error. This distinction was chosen as a user @@ -1701,7 +1701,7 @@ bar psql'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 psql. - They indicate certain option settings that can be changed at runtime + 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 @@ -2037,7 +2037,7 @@ testdb=> \set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\' %M - The full hostname (with domain name) of the database server, + The full host name (with domain name) of the database server, or [local] if the connection is over a Unix domain socket, or [local:/dir/name], @@ -2051,7 +2051,7 @@ testdb=> \set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\' %m - The hostname of the database server, truncated after the + The host name of the database server, truncated after the first dot, or [local] if the connection is over a Unix domain socket. @@ -2065,7 +2065,7 @@ testdb=> \set content '\'' `sed -e "s/'/\\\\\\'/g" < my_file.txt` '\' %n - The username you are connected as (not your local system + The user name you are connected as (not your local system user name). diff --git a/doc/src/sgml/ref/reindex.sgml b/doc/src/sgml/ref/reindex.sgml index bb443f8d46..f39766a572 100644 --- a/doc/src/sgml/ref/reindex.sgml +++ b/doc/src/sgml/ref/reindex.sgml @@ -1,5 +1,5 @@ @@ -145,7 +145,7 @@ REINDEX 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 startup, due to reliance on the corrupted + 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 PostgreSQL backend must be started instead, giving it diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml index ed080d3534..e1d419e811 100644 --- a/doc/src/sgml/ref/select.sgml +++ b/doc/src/sgml/ref/select.sgml @@ -1,5 +1,5 @@ @@ -91,7 +91,7 @@ where from_item can be: condition - A boolean expression giving a result of true or false. + A Boolean expression giving a result of true or false. See the WHERE and HAVING clause descriptions below. @@ -368,7 +368,7 @@ where from_item can be: PostgreSQL 7.1, this was the default result, and adding sub-tables was done by appending * to the table name. - This old behaviour is available via the command + This old behavior is available via the command SET SQL_Inheritance TO OFF; @@ -449,7 +449,7 @@ WHERE boolean_expr boolean_expr - can consist of any expression which evaluates to a boolean value. + can consist of any expression which evaluates to a Boolean value. In many cases, this expression will be: diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 1692e522a4..4900f1b748 100644 --- a/doc/src/sgml/release.sgml +++ b/doc/src/sgml/release.sgml @@ -1,5 +1,5 @@ @@ -127,11 +127,11 @@ Fix for array subscripts handling (Tom) - OID's + OIDs - OID's are now optional. Users can now create tables without - OID's for cases where OID usage is excessive. + OIDs are now optional. Users can now create tables without + OIDs for cases where OID usage is excessive. @@ -268,7 +268,7 @@ 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 OID's from some system tables (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) @@ -873,7 +873,7 @@ Subqueries in FROM are now supported. Bug Fixes --------- -Many multi-byte/Unicode/locale fixes (Tatsuo and others) +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) @@ -1096,7 +1096,7 @@ 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 multi-byte enabled (Tatsuo) +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) @@ -1773,7 +1773,7 @@ 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 multi-column constraints(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 @@ -1828,7 +1828,7 @@ 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 multi-segment tables(Hiroshi) +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) @@ -1873,7 +1873,7 @@ Add Win1250 (Czech) support (Pavel Behal) - Multi-version concurrency control(MVCC) + Multiversion concurrency control(MVCC) @@ -1881,7 +1881,7 @@ Add Win1250 (Czech) support (Pavel Behal) 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 multi-version nature of PostgreSQL + 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 @@ -2020,15 +2020,15 @@ Add Win1250 (Czech) support (Pavel Behal) - The new Multi-Version Concurrency Control (MVCC) features can - give somewhat different behaviors in multi-user + The new Multiversion Concurrency Control (MVCC) features can + give somewhat different behaviors in multiuser environments. Read and understand the following section to ensure that your existing applications will give you the behavior you need. - Multi-Version Concurrency Control + Multiversion Concurrency Control Because readers in 6.5 don't lock data, regardless of transaction @@ -2122,7 +2122,7 @@ 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 multi-segment file size limit to 1GB(Peter) +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) @@ -2134,7 +2134,7 @@ 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 multi-segment uses of DROP/RENAME table, indexes(Ole Gjerde) +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) @@ -2159,7 +2159,7 @@ Update to pgaccess 0.96(Constantin) Add routines for single-byte "char" type(Thomas) Improved substr() function(Thomas) Improved multibyte handling(Tatsuo) -Multi-version concurrency control/MVCC(Vadim) +Multiversion concurrency control/MVCC(Vadim) New Serialized mode(Vadim) Fix for tables over 2gigs(Peter) New SET TRANSACTION ISOLATION LEVEL(Vadim) @@ -2577,7 +2577,7 @@ New rewrite system fixes many problems with rules and views(Jan) * handle subselects * handle aggregates on views * handle insert into select from view works -System indexes are now multi-key(Bruce) +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) @@ -3471,7 +3471,7 @@ Bug Fixes packet length checking in library routines lock manager priority patch check for under/over flow of float8(Bruce) -multi-table join fix(Vadim) +multitable join fix(Vadim) SIGPIPE crash fix(Darren) large object fixes(Sven) allow btree indexes to handle NULLs(Vadim) @@ -3503,7 +3503,7 @@ 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 multi-table optimization(Martin) +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) @@ -3514,7 +3514,7 @@ 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) -multi-column btree indexes(Vadim) +multicolumn btree indexes(Vadim) new SET var TO value command(Martin) update transaction status on reads(Dan) new locale settings for character types(Oleg) @@ -3627,7 +3627,7 @@ 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 oid's +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) @@ -3662,7 +3662,7 @@ Implement IN qualifier(Bruce) Libpq has PQgetisnull()(Bruce) Libpq++ improvements New options to initdb(Bryan) -Pg_dump allow dump of oid's(Bruce) +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) diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml index 34ee7473db..5385a90022 100644 --- a/doc/src/sgml/rules.sgml +++ b/doc/src/sgml/rules.sgml @@ -1,4 +1,4 @@ - + The Rule System @@ -1140,7 +1140,7 @@ INSERT INTO shoelace_log VALUES( 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 querytree. + INSERT command's query tree. diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index fc840a2ae6..ddeac7ce1d 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,9 +1,9 @@ - Server Runtime Environment + Server Run-time Environment This chapter discusses how to set up and run the database server @@ -467,7 +467,7 @@ psql: could not connect to server: Connection refused All parameter names are case-insensitive. Every parameter takes a - value of one of the four types: boolean, integer, floating point, + value of one of the four types: Boolean, integer, floating point, and string. Boolean values are ON, OFF, TRUE, FALSE, YES, diff --git a/doc/src/sgml/spi.sgml b/doc/src/sgml/spi.sgml index 533a0f2979..ca6d62e1ae 100644 --- a/doc/src/sgml/spi.sgml +++ b/doc/src/sgml/spi.sgml @@ -1,5 +1,5 @@ @@ -536,10 +536,10 @@ You may pass multiple queries in one string or query string may be - vals is an array of pointers to tuples (the number of useful entries - is given by SPI_processed). TupleDesc tupdesc is + vals is an array of pointers to tuples (the number of useful entries + is given by SPI_processed). tupdesc is a tuple descriptor which you may pass to SPI functions dealing with - tuples. tuptabcxt, alloced, and free are internal fields not intended + tuples. tuptabcxt, alloced, and free are internal fields not intended for use by SPI callers. @@ -686,7 +686,7 @@ Pointer to an execution plan (parser+planner+optimizer) - If the query uses parameters, their number and datatypes must be + If the query uses parameters, their number and data types must be specified in the call to SPI_prepare. @@ -2177,7 +2177,7 @@ Attribute numbers are 1 based. Does not allocate new space for the datum. In the case of a pass-by- -reference datatype, the Datum will be a pointer into the given tuple. +reference data type, the Datum will be a pointer into the given tuple. @@ -391,7 +391,7 @@ CAST ( 'string' AS type ) The ::, CAST(), and - function-call syntaxes can also be used to specify runtime type + function-call syntaxes can also be used to specify run-time type conversions of arbitrary expressions, as discussed in . But the form type 'string' diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml index d2441ce08b..34ab2840ee 100644 --- a/doc/src/sgml/trigger.sgml +++ b/doc/src/sgml/trigger.sgml @@ -1,5 +1,5 @@ @@ -7,9 +7,9 @@ $Header: /cvsroot/pgsql/doc/src/sgml/trigger.sgml,v 1.20 2002/03/06 06:44:33 mom PostgreSQL has various server-side function - interfaces. Server-side functions can be written in SQL, PLPGSQL, - TCL, or C. Trigger functions can be written in any of these - languages except SQL. Note that STATEMENT-level trigger events are not + 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. @@ -216,9 +216,10 @@ CREATE TRIGGER trigger [ BEFORE | AFTER ] [ INSERT | - struct TriggerData is defined in src/include/commands/trigger.h: + struct TriggerData is defined in + commands/trigger.h: - + typedef struct TriggerData { NodeTag type; @@ -228,7 +229,7 @@ typedef struct TriggerData HeapTuple tg_newtuple; Trigger *tg_trigger; } TriggerData; - + where the members are defined as follows: diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml index 262c1e2e8c..9cc87965a4 100644 --- a/doc/src/sgml/xfunc.sgml +++ b/doc/src/sgml/xfunc.sgml @@ -1,5 +1,5 @@ @@ -86,7 +86,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v 1.50 2002/03/21 16:00:28 tgl E SELECT. In the simple (non-set) case, the first row of the last query's result will be returned. - (Bear in mind that the first row of a multi-row + (Bear in mind that the first row of a multirow result is not well-defined unless you use ORDER BY.) If the last query happens to return no rows at all, NULL will be returned. @@ -367,7 +367,6 @@ SELECT name(new_emp()); ------ None - -- @@ -622,7 +621,7 @@ CREATE FUNCTION square_root(double precision) RETURNS double precision The user ID the PostgreSQL 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 postgres user is a + and/or not executable by the postgres user is a common mistake. @@ -1169,7 +1168,7 @@ PG_FUNCTION_INFO_V1(funcname); In a version-1 function, each actual argument is fetched using a PG_GETARG_xxx() - macro that corresponds to the argument's datatype, and the result + macro that corresponds to the argument's data type, and the result is returned using a PG_RETURN_xxx() macro for the return type. diff --git a/doc/src/sgml/xoper.sgml b/doc/src/sgml/xoper.sgml index 9a85d81b4d..5967ddbfb6 100644 --- a/doc/src/sgml/xoper.sgml +++ b/doc/src/sgml/xoper.sgml @@ -1,5 +1,5 @@ @@ -389,7 +389,7 @@ table1.column1 OP table2.column2 - Merge join is based on the idea of sorting the left and righthand tables + 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 same place diff --git a/doc/src/sgml/xtypes.sgml b/doc/src/sgml/xtypes.sgml index 5d3146a96c..9886e7a3c3 100644 --- a/doc/src/sgml/xtypes.sgml +++ b/doc/src/sgml/xtypes.sgml @@ -175,7 +175,7 @@ CREATE TYPE complex ( TOAST and user-defined types - If the values of your datatype might exceed a few hundred bytes in + 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 -- GitLab