From fc946c39aeacdff7df60c83fca6582985e8546c8 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Tue, 23 Nov 2010 22:27:50 +0200 Subject: Remove useless whitespace at end of lines --- doc/src/sgml/Makefile | 2 +- doc/src/sgml/auto-explain.sgml | 4 +- doc/src/sgml/biblio.sgml | 4 +- doc/src/sgml/charset.sgml | 2 +- doc/src/sgml/config.sgml | 76 ++++++++-------- doc/src/sgml/contacts.sgml | 2 +- doc/src/sgml/contrib.sgml | 2 +- doc/src/sgml/datatype.sgml | 52 +++++------ doc/src/sgml/datetime.sgml | 16 ++-- doc/src/sgml/dfunc.sgml | 6 +- doc/src/sgml/docguide.sgml | 28 +++--- doc/src/sgml/ecpg.sgml | 71 ++++++++------- doc/src/sgml/extend.sgml | 14 +-- doc/src/sgml/external-projects.sgml | 4 +- doc/src/sgml/filelist.sgml | 2 +- doc/src/sgml/func.sgml | 144 +++++++++++++++--------------- doc/src/sgml/history.sgml | 4 +- doc/src/sgml/info.sgml | 2 +- doc/src/sgml/install-windows.sgml | 14 +-- doc/src/sgml/keywords.sgml | 2 +- doc/src/sgml/legal.sgml | 2 +- doc/src/sgml/libpq.sgml | 2 +- doc/src/sgml/lobj.sgml | 16 ++-- doc/src/sgml/mvcc.sgml | 8 +- doc/src/sgml/pgarchivecleanup.sgml | 2 +- doc/src/sgml/pgupgrade.sgml | 124 ++++++++++++------------- doc/src/sgml/plperl.sgml | 10 +-- doc/src/sgml/pltcl.sgml | 4 +- doc/src/sgml/problems.sgml | 6 +- doc/src/sgml/ref/abort.sgml | 2 +- doc/src/sgml/ref/alter_aggregate.sgml | 8 +- doc/src/sgml/ref/alter_conversion.sgml | 8 +- doc/src/sgml/ref/alter_database.sgml | 8 +- doc/src/sgml/ref/alter_domain.sgml | 6 +- doc/src/sgml/ref/alter_function.sgml | 10 +-- doc/src/sgml/ref/alter_group.sgml | 4 +- doc/src/sgml/ref/alter_index.sgml | 8 +- doc/src/sgml/ref/alter_language.sgml | 2 +- doc/src/sgml/ref/alter_large_object.sgml | 2 +- doc/src/sgml/ref/alter_opclass.sgml | 8 +- doc/src/sgml/ref/alter_operator.sgml | 10 +-- doc/src/sgml/ref/alter_opfamily.sgml | 16 ++-- doc/src/sgml/ref/alter_schema.sgml | 2 +- doc/src/sgml/ref/alter_sequence.sgml | 2 +- doc/src/sgml/ref/alter_tablespace.sgml | 10 +-- doc/src/sgml/ref/alter_tsconfig.sgml | 10 +-- doc/src/sgml/ref/alter_tsdictionary.sgml | 14 +-- doc/src/sgml/ref/alter_tsparser.sgml | 8 +- doc/src/sgml/ref/alter_tstemplate.sgml | 8 +- doc/src/sgml/ref/alter_user.sgml | 6 +- doc/src/sgml/ref/alter_view.sgml | 8 +- doc/src/sgml/ref/begin.sgml | 14 +-- doc/src/sgml/ref/close.sgml | 6 +- doc/src/sgml/ref/clusterdb.sgml | 10 +-- doc/src/sgml/ref/comment.sgml | 10 +-- doc/src/sgml/ref/commit.sgml | 6 +- doc/src/sgml/ref/commit_prepared.sgml | 4 +- doc/src/sgml/ref/create_aggregate.sgml | 12 +-- doc/src/sgml/ref/create_conversion.sgml | 4 +- doc/src/sgml/ref/create_function.sgml | 2 +- doc/src/sgml/ref/create_group.sgml | 12 +-- doc/src/sgml/ref/create_opclass.sgml | 12 +-- doc/src/sgml/ref/create_operator.sgml | 10 +-- doc/src/sgml/ref/create_opfamily.sgml | 4 +- doc/src/sgml/ref/create_role.sgml | 14 +-- doc/src/sgml/ref/create_sequence.sgml | 2 +- doc/src/sgml/ref/create_table_as.sgml | 4 +- doc/src/sgml/ref/create_tsconfig.sgml | 6 +- doc/src/sgml/ref/create_tsdictionary.sgml | 8 +- doc/src/sgml/ref/create_tsparser.sgml | 4 +- doc/src/sgml/ref/create_tstemplate.sgml | 4 +- doc/src/sgml/ref/create_user.sgml | 10 +-- doc/src/sgml/ref/createdb.sgml | 10 +-- doc/src/sgml/ref/createlang.sgml | 20 ++--- doc/src/sgml/ref/createuser.sgml | 14 +-- doc/src/sgml/ref/drop_cast.sgml | 6 +- doc/src/sgml/ref/drop_conversion.sgml | 4 +- doc/src/sgml/ref/drop_database.sgml | 6 +- doc/src/sgml/ref/drop_domain.sgml | 6 +- doc/src/sgml/ref/drop_function.sgml | 6 +- doc/src/sgml/ref/drop_index.sgml | 2 +- doc/src/sgml/ref/drop_language.sgml | 8 +- doc/src/sgml/ref/drop_opclass.sgml | 10 +-- doc/src/sgml/ref/drop_operator.sgml | 8 +- doc/src/sgml/ref/drop_opfamily.sgml | 6 +- doc/src/sgml/ref/drop_role.sgml | 6 +- doc/src/sgml/ref/drop_rule.sgml | 4 +- doc/src/sgml/ref/drop_schema.sgml | 12 +-- doc/src/sgml/ref/drop_sequence.sgml | 12 +-- doc/src/sgml/ref/drop_table.sgml | 14 +-- doc/src/sgml/ref/drop_tablespace.sgml | 2 +- doc/src/sgml/ref/drop_trigger.sgml | 10 +-- doc/src/sgml/ref/drop_tsconfig.sgml | 6 +- doc/src/sgml/ref/drop_tsdictionary.sgml | 6 +- doc/src/sgml/ref/drop_tsparser.sgml | 6 +- doc/src/sgml/ref/drop_tstemplate.sgml | 6 +- doc/src/sgml/ref/drop_type.sgml | 6 +- doc/src/sgml/ref/drop_view.sgml | 12 +-- doc/src/sgml/ref/dropdb.sgml | 8 +- doc/src/sgml/ref/droplang.sgml | 20 ++--- doc/src/sgml/ref/dropuser.sgml | 12 +-- doc/src/sgml/ref/ecpg-ref.sgml | 2 +- doc/src/sgml/ref/end.sgml | 6 +- doc/src/sgml/ref/fetch.sgml | 2 +- doc/src/sgml/ref/initdb.sgml | 10 +-- doc/src/sgml/ref/lock.sgml | 8 +- doc/src/sgml/ref/move.sgml | 2 +- doc/src/sgml/ref/pg_config-ref.sgml | 2 +- doc/src/sgml/ref/pg_controldata.sgml | 4 +- doc/src/sgml/ref/pg_dumpall.sgml | 2 +- doc/src/sgml/ref/pg_resetxlog.sgml | 4 +- doc/src/sgml/ref/postgres-ref.sgml | 8 +- doc/src/sgml/ref/prepare.sgml | 2 +- doc/src/sgml/ref/reindexdb.sgml | 10 +-- doc/src/sgml/ref/release_savepoint.sgml | 4 +- doc/src/sgml/ref/rollback_prepared.sgml | 4 +- doc/src/sgml/ref/savepoint.sgml | 6 +- doc/src/sgml/ref/security_label.sgml | 2 +- doc/src/sgml/ref/set.sgml | 4 +- doc/src/sgml/ref/values.sgml | 2 +- doc/src/sgml/regress.sgml | 28 +++--- doc/src/sgml/rowtypes.sgml | 4 +- doc/src/sgml/runtime.sgml | 16 ++-- doc/src/sgml/sql.sgml | 88 +++++++++--------- doc/src/sgml/start.sgml | 2 +- doc/src/sgml/stylesheet.css | 2 +- doc/src/sgml/stylesheet.dsl | 32 +++---- doc/src/sgml/vacuumlo.sgml | 2 +- doc/src/sgml/wal.sgml | 2 +- doc/src/sgml/xindex.sgml | 8 +- doc/src/sgml/xoper.sgml | 2 +- doc/src/sgml/xtypes.sgml | 2 +- 132 files changed, 731 insertions(+), 732 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/Makefile b/doc/src/sgml/Makefile index a7f0c8d6340..a797499c792 100644 --- a/doc/src/sgml/Makefile +++ b/doc/src/sgml/Makefile @@ -64,7 +64,7 @@ CATALOG = -c $(DOCBOOKSTYLE)/catalog endif # Enable some extra warnings -# -wfully-tagged needed to throw a warning on missing tags +# -wfully-tagged needed to throw a warning on missing tags # for older tool chains, 2007-08-31 # Note: try "make SPFLAGS=-wxml" to catch a lot of other dubious constructs, # in particular < and & that haven't been made into entities. It's far too diff --git a/doc/src/sgml/auto-explain.sgml b/doc/src/sgml/auto-explain.sgml index 82b209f9c6a..027138b92e3 100644 --- a/doc/src/sgml/auto-explain.sgml +++ b/doc/src/sgml/auto-explain.sgml @@ -112,8 +112,8 @@ LOAD 'auto_explain'; auto_explain.log_buffers causes EXPLAIN - (ANALYZE, BUFFERS) output, rather than just EXPLAIN - output, to be printed when an execution plan is logged. This parameter is + (ANALYZE, BUFFERS) output, rather than just EXPLAIN + output, to be printed when an execution plan is logged. This parameter is off by default. Only superusers can change this setting. This parameter has no effect unless auto_explain.log_analyze parameter is set. diff --git a/doc/src/sgml/biblio.sgml b/doc/src/sgml/biblio.sgml index e02f443566a..edc59bdbb6a 100644 --- a/doc/src/sgml/biblio.sgml +++ b/doc/src/sgml/biblio.sgml @@ -257,7 +257,7 @@ ssimkovi@ag.or.at Proceedings and Articles This section is for articles and newsletters. - + Partial indexing in POSTGRES: research project Olson, 1993 @@ -328,7 +328,7 @@ ssimkovi@ag.or.at Generalized Partial Indexes <ulink url="http://citeseer.ist.psu.edu/seshadri95generalized.html">(cached version) -<!-- +<!-- Original URL: http://citeseer.ist.psu.edu/seshadri95generalized.html --> </ulink> diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index e94922124c2..9e047e7dbda 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -71,7 +71,7 @@ initdb --locale=sv_SE locale then the specifications can take the form <replaceable>language_territory.codeset</>. For example, <literal>fr_BE.UTF-8</> represents the French language (fr) as - spoken in Belgium (BE), with a <acronym>UTF-8</> character set + spoken in Belgium (BE), with a <acronym>UTF-8</> character set encoding. </para> diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 898cdacbb10..96f1ef49b25 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -718,7 +718,7 @@ SET ENABLE_SEQSCAN TO OFF; <listitem> <para> Sets the location of the Kerberos server key file. See - <xref linkend="kerberos-auth"> or <xref linkend="gssapi-auth"> + <xref linkend="kerberos-auth"> or <xref linkend="gssapi-auth"> for details. This parameter can only be set in the <filename>postgresql.conf</> file or on the server command line. </para> @@ -748,7 +748,7 @@ SET ENABLE_SEQSCAN TO OFF; <para> Sets whether Kerberos and GSSAPI user names should be treated case-insensitively. - The default is <literal>off</> (case sensitive). This parameter can only be + The default is <literal>off</> (case sensitive). This parameter can only be set in the <filename>postgresql.conf</> file or on the server command line. </para> </listitem> @@ -1044,7 +1044,7 @@ SET ENABLE_SEQSCAN TO OFF; </para> </listitem> </varlistentry> - + <varlistentry id="guc-shared-preload-libraries" xreflabel="shared_preload_libraries"> <term><varname>shared_preload_libraries</varname> (<type>string</type>)</term> <indexterm> @@ -1076,7 +1076,7 @@ SET ENABLE_SEQSCAN TO OFF; when the library is first used. However, the time to start each new server process might increase slightly, even if that process never uses the library. So this parameter is recommended only for - libraries that will be used in most sessions. + libraries that will be used in most sessions. </para> <note> @@ -1084,7 +1084,7 @@ SET ENABLE_SEQSCAN TO OFF; On Windows hosts, preloading a library at server start will not reduce the time required to start each new server process; each server process will re-load all preload libraries. However, <varname>shared_preload_libraries - </varname> is still useful on Windows hosts because some shared libraries may + </varname> is still useful on Windows hosts because some shared libraries may need to perform certain operations that only take place at postmaster start (for example, a shared library may need to reserve lightweight locks or shared memory and you can't do that after the postmaster has started). @@ -1097,8 +1097,8 @@ SET ENABLE_SEQSCAN TO OFF; <para> Every PostgreSQL-supported library has a <quote>magic - block</> that is checked to guarantee compatibility. - For this reason, non-PostgreSQL libraries cannot be + block</> that is checked to guarantee compatibility. + For this reason, non-PostgreSQL libraries cannot be loaded in this way. </para> </listitem> @@ -1487,7 +1487,7 @@ SET ENABLE_SEQSCAN TO OFF; <para> <varname>fsync</varname> can only be set in the <filename>postgresql.conf</> file or on the server command line. - If you turn this parameter off, also consider turning off + If you turn this parameter off, also consider turning off <xref linkend="guc-full-page-writes">. </para> </listitem> @@ -1528,7 +1528,7 @@ SET ENABLE_SEQSCAN TO OFF; </para> </listitem> </varlistentry> - + <varlistentry id="guc-wal-sync-method" xreflabel="wal_sync_method"> <term><varname>wal_sync_method</varname> (<type>enum</type>)</term> <indexterm> @@ -1584,7 +1584,7 @@ SET ENABLE_SEQSCAN TO OFF; </para> </listitem> </varlistentry> - + <varlistentry id="guc-full-page-writes" xreflabel="full_page_writes"> <indexterm> <primary><varname>full_page_writes</> configuration parameter</primary> @@ -1848,7 +1848,7 @@ SET ENABLE_SEQSCAN TO OFF; </para> </listitem> </varlistentry> - + <varlistentry id="guc-archive-timeout" xreflabel="archive_timeout"> <term><varname>archive_timeout</varname> (<type>integer</type>)</term> <indexterm> @@ -2257,7 +2257,7 @@ SET ENABLE_SEQSCAN TO OFF; </para> </listitem> </varlistentry> - + </variablelist> </sect2> <sect2 id="runtime-config-query-constants"> @@ -2368,7 +2368,7 @@ SET ENABLE_SEQSCAN TO OFF; </para> </listitem> </varlistentry> - + <varlistentry id="guc-cpu-operator-cost" xreflabel="cpu_operator_cost"> <term><varname>cpu_operator_cost</varname> (<type>floating point</type>)</term> <indexterm> @@ -2382,7 +2382,7 @@ SET ENABLE_SEQSCAN TO OFF; </para> </listitem> </varlistentry> - + <varlistentry id="guc-effective-cache-size" xreflabel="effective_cache_size"> <term><varname>effective_cache_size</varname> (<type>integer</type>)</term> <indexterm> @@ -2745,10 +2745,10 @@ SELECT * FROM parent WHERE key = 2400; <productname>PostgreSQL</productname> supports several methods for logging server messages, including <systemitem>stderr</systemitem>, <systemitem>csvlog</systemitem> and - <systemitem>syslog</systemitem>. On Windows, + <systemitem>syslog</systemitem>. On Windows, <systemitem>eventlog</systemitem> is also supported. Set this parameter to a list of desired log destinations separated by - commas. The default is to log to <systemitem>stderr</systemitem> + commas. The default is to log to <systemitem>stderr</systemitem> only. This parameter can only be set in the <filename>postgresql.conf</> file or on the server command line. @@ -2759,7 +2759,7 @@ SELECT * FROM parent WHERE key = 2400; value</> (<acronym>CSV</>) format, which is convenient for loading logs into programs. See <xref linkend="runtime-config-logging-csvlog"> for details. - <varname>logging_collector</varname> must be enabled to generate + <varname>logging_collector</varname> must be enabled to generate CSV-format log output. </para> @@ -2822,7 +2822,7 @@ local0.* /var/log/postgresql </indexterm> <listitem> <para> - When <varname>logging_collector</> is enabled, + When <varname>logging_collector</> is enabled, this parameter determines the directory in which log files will be created. It can be specified as an absolute path, or relative to the cluster data directory. @@ -2861,7 +2861,7 @@ local0.* /var/log/postgresql </para> <para> If CSV-format output is enabled in <varname>log_destination</>, - <literal>.csv</> will be appended to the timestamped + <literal>.csv</> will be appended to the timestamped log file name to create the file name for CSV-format output. (If <varname>log_filename</> ends in <literal>.log</>, the suffix is replaced instead.) @@ -2966,18 +2966,18 @@ local0.* /var/log/postgresql </para> <para> Example: To keep 7 days of logs, one log file per day named - <literal>server_log.Mon</literal>, <literal>server_log.Tue</literal>, + <literal>server_log.Mon</literal>, <literal>server_log.Tue</literal>, etc, and automatically overwrite last week's log with this week's log, - set <varname>log_filename</varname> to <literal>server_log.%a</literal>, - <varname>log_truncate_on_rotation</varname> to <literal>on</literal>, and + set <varname>log_filename</varname> to <literal>server_log.%a</literal>, + <varname>log_truncate_on_rotation</varname> to <literal>on</literal>, and <varname>log_rotation_age</varname> to <literal>1440</literal>. </para> <para> - Example: To keep 24 hours of logs, one log file per hour, but - also rotate sooner if the log file size exceeds 1GB, set - <varname>log_filename</varname> to <literal>server_log.%H%M</literal>, - <varname>log_truncate_on_rotation</varname> to <literal>on</literal>, - <varname>log_rotation_age</varname> to <literal>60</literal>, and + Example: To keep 24 hours of logs, one log file per hour, but + also rotate sooner if the log file size exceeds 1GB, set + <varname>log_filename</varname> to <literal>server_log.%H%M</literal>, + <varname>log_truncate_on_rotation</varname> to <literal>on</literal>, + <varname>log_rotation_age</varname> to <literal>60</literal>, and <varname>log_rotation_size</varname> to <literal>1000000</literal>. Including <literal>%M</> in <varname>log_filename</varname> allows any size-driven rotations that might occur to select a file name @@ -3007,7 +3007,7 @@ local0.* /var/log/postgresql </para> </listitem> </varlistentry> - + <varlistentry id="guc-syslog-ident" xreflabel="syslog_ident"> <term><varname>syslog_ident</varname> (<type>string</type>)</term> <indexterm> @@ -3132,7 +3132,7 @@ local0.* /var/log/postgresql </para> </listitem> </varlistentry> - + <varlistentry id="guc-log-min-duration-statement" xreflabel="log_min_duration_statement"> <term><varname>log_min_duration_statement</varname> (<type>integer</type>)</term> <indexterm> @@ -3163,7 +3163,7 @@ local0.* /var/log/postgresql the text of statements that are logged because of <varname>log_statement</> will not be repeated in the duration log message. - If you are not using <application>syslog</>, it is recommended + If you are not using <application>syslog</>, it is recommended that you log the PID or session ID using <xref linkend="guc-log-line-prefix"> so that you can link the statement message to the later @@ -3365,8 +3365,8 @@ local0.* /var/log/postgresql <note> <para> - Some client programs, like <application>psql</>, attempt - to connect twice while determining if a password is required, so + Some client programs, like <application>psql</>, attempt + to connect twice while determining if a password is required, so duplicate <quote>connection received</> messages do not necessarily indicate a problem. </para> @@ -3462,7 +3462,7 @@ local0.* /var/log/postgresql </para> </listitem> </varlistentry> - + <varlistentry id="guc-log-line-prefix" xreflabel="log_line_prefix"> <term><varname>log_line_prefix</varname> (<type>string</type>)</term> <indexterm> @@ -3607,7 +3607,7 @@ FROM pg_stat_activity; <tip> <para> - <application>Syslog</> produces its own + <application>Syslog</> produces its own time stamp and process ID information, so you probably do not want to include those escapes if you are logging to <application>syslog</>. </para> @@ -3808,9 +3808,9 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv; <listitem> <para> - Set <varname>log_rotation_size</varname> to 0 to disable - size-based log rotation, as it makes the log file name difficult - to predict. + Set <varname>log_rotation_size</varname> to 0 to disable + size-based log rotation, as it makes the log file name difficult + to predict. </para> </listitem> @@ -5000,7 +5000,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' <para> Every PostgreSQL-supported library has a <quote>magic - block</> that is checked to guarantee compatibility. + block</> that is checked to guarantee compatibility. For this reason, non-PostgreSQL libraries cannot be loaded in this way. </para> diff --git a/doc/src/sgml/contacts.sgml b/doc/src/sgml/contacts.sgml index 996c0771bb5..a9816250279 100644 --- a/doc/src/sgml/contacts.sgml +++ b/doc/src/sgml/contacts.sgml @@ -15,7 +15,7 @@ and the mailing lists themselves. <para> Refer to the introduction in this manual or to the -<productname>PostgreSQL</productname> +<productname>PostgreSQL</productname> <ulink url="http://www.postgresql.org">web page</ulink> for subscription information to the no-cost mailing lists. </para> diff --git a/doc/src/sgml/contrib.sgml b/doc/src/sgml/contrib.sgml index 90579960148..a7c2a1d43eb 100644 --- a/doc/src/sgml/contrib.sgml +++ b/doc/src/sgml/contrib.sgml @@ -16,7 +16,7 @@ <para> When building from the source distribution, these modules are not built - automatically, unless you build the "world" target + automatically, unless you build the "world" target (see <xref linkend="build">). You can build and install all of them by running: <screen> diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 02eaedf9434..66aef156082 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -21,7 +21,7 @@ <para> <xref linkend="datatype-table"> shows all the built-in general-purpose data - types. Most of the alternative names listed in the + types. 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, @@ -555,7 +555,7 @@ NUMERIC <para> In addition to ordinary numeric values, the <type>numeric</type> - type allows the special value <literal>NaN</>, meaning + type allows the special value <literal>NaN</>, meaning <quote>not-a-number</quote>. Any operation on <literal>NaN</> yields another <literal>NaN</>. When writing this value as a constant in an SQL command, you must put quotes around it, @@ -703,9 +703,9 @@ NUMERIC <type>float(<replaceable>p</replaceable>)</type> for specifying inexact numeric types. Here, <replaceable>p</replaceable> specifies the minimum acceptable precision in <emphasis>binary</> digits. - <productname>PostgreSQL</productname> accepts + <productname>PostgreSQL</productname> accepts <type>float(1)</type> to <type>float(24)</type> as selecting the - <type>real</type> type, while + <type>real</type> type, while <type>float(25)</type> to <type>float(53)</type> select <type>double precision</type>. Values of <replaceable>p</replaceable> outside the allowed range draw an error. @@ -1628,7 +1628,7 @@ MINUTE TO SECOND <para> Date and time input is accepted in almost any reasonable format, including - ISO 8601, <acronym>SQL</acronym>-compatible, + ISO 8601, <acronym>SQL</acronym>-compatible, traditional <productname>POSTGRES</productname>, and others. For some formats, ordering of day, month, and year in date input is ambiguous and there is support for specifying the expected @@ -1645,12 +1645,12 @@ MINUTE TO SECOND 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. + time zones. </para> <para> Remember that any date or time literal input needs to be enclosed - in single quotes, like text strings. Refer to + in single quotes, like text strings. Refer to <xref linkend="sql-syntax-constants-generic"> for more information. <acronym>SQL</acronym> requires the following syntax @@ -1672,7 +1672,7 @@ MINUTE TO SECOND <indexterm> <primary>date</primary> </indexterm> - + <para> <xref linkend="datatype-datetime-date-table"> shows some possible inputs for the <type>date</type> type. @@ -1787,7 +1787,7 @@ MINUTE TO SECOND <para> Valid input for these types consists of a time of day followed by an optional time zone. (See <xref - linkend="datatype-datetime-time-table"> + linkend="datatype-datetime-time-table"> and <xref linkend="datatype-timezone-table">.) If a time zone is specified in the input for <type>time without time zone</type>, it is silently ignored. You can also specify a date but it will @@ -1954,8 +1954,8 @@ January 8 04:05:06 1999 PST <para> The <acronym>SQL</acronym> standard differentiates - <type>timestamp without time zone</type> - and <type>timestamp with time zone</type> literals by the presence of a + <type>timestamp without time zone</type> + and <type>timestamp with time zone</type> literals by the presence of a <quote>+</quote> or <quote>-</quote> symbol and time zone offset after the time. Hence, according to the standard, @@ -2097,10 +2097,10 @@ January 8 04:05:06 1999 PST The following <acronym>SQL</acronym>-compatible functions can also be used to obtain the current time value for the corresponding data type: - <literal>CURRENT_DATE</literal>, <literal>CURRENT_TIME</literal>, - <literal>CURRENT_TIMESTAMP</literal>, <literal>LOCALTIME</literal>, - <literal>LOCALTIMESTAMP</literal>. The latter four accept an - optional subsecond precision specification. (See <xref + <literal>CURRENT_DATE</literal>, <literal>CURRENT_TIME</literal>, + <literal>CURRENT_TIMESTAMP</literal>, <literal>LOCALTIME</literal>, + <literal>LOCALTIMESTAMP</literal>. The latter four accept an + optional subsecond precision specification. (See <xref linkend="functions-datetime-current">.) Note that these are SQL functions and are <emphasis>not</> recognized in data input strings. </para> @@ -2255,10 +2255,10 @@ January 8 04:05:06 1999 PST <itemizedlist> <listitem> <para> - Although the <type>date</type> type + Although the <type>date</type> type cannot have an associated time zone, the <type>time</type> type can. - Time zones in the real world have little meaning unless + Time zones in the real world have little meaning unless associated with a date as well as a time, since the offset can vary through the year with daylight-saving time boundaries. @@ -2267,7 +2267,7 @@ January 8 04:05:06 1999 PST <listitem> <para> - The default time zone is specified as a constant numeric offset + The default time zone is specified as a constant numeric offset from <acronym>UTC</>. It is therefore impossible to adapt to daylight-saving time when doing date/time arithmetic across <acronym>DST</acronym> boundaries. @@ -2901,7 +2901,7 @@ SELECT * FROM person WHERE current_mood = 'happy'; order in which the values were listed when the type was created. All standard comparison operators and related aggregate functions are supported for enums. For example: - + <programlisting> INSERT INTO person VALUES ('Larry', 'sad'); INSERT INTO person VALUES ('Curly', 'ok'); @@ -2919,7 +2919,7 @@ SELECT * FROM person WHERE current_mood > 'sad' ORDER BY current_mood; Moe | happy (2 rows) -SELECT name +SELECT name FROM person WHERE current_mood = (SELECT MIN(current_mood) FROM person); name @@ -2972,7 +2972,7 @@ SELECT person.name, holidays.num_weeks FROM person, holidays <sect2> <title>Implementation Details - + An enum value occupies four bytes on disk. The length of an enum value's textual label is limited by the NAMEDATALEN @@ -3409,8 +3409,8 @@ SELECT person.name, holidays.num_weeks FROM person, holidays <type>cidr</> Type Input Examples - - + + cidr Input cidr Output abbrev(cidr) @@ -3772,7 +3772,7 @@ select 'The Fat Rats'::tsvector; for searching: -SELECT to_tsvector('english', 'The Fat Rats'); +SELECT to_tsvector('english', 'The Fat Rats'); to_tsvector ----------------- 'fat':2 'rat':3 @@ -3913,7 +3913,7 @@ a0ee-bc99-9c0b-4ef8-bb6d-6bb9-bd38-0a11 functions for UUIDs, but the core database does not include any function for generating UUIDs, because no single algorithm is well suited for every application. The contrib module - contrib/uuid-ossp provides functions that implement + contrib/uuid-ossp provides functions that implement several standard algorithms. Alternatively, UUIDs could be generated by client applications or other libraries invoked through a server-side function. @@ -3933,7 +3933,7 @@ a0ee-bc99-9c0b-4ef8-bb6d-6bb9-bd38-0a11 checks the input values for well-formedness, and there are support functions to perform type-safe operations on it; see . Use of this data type requires the - installation to have been built with configure + installation to have been built with configure --with-libxml. diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml index fb75a1e8b08..0b554462451 100644 --- a/doc/src/sgml/datetime.sgml +++ b/doc/src/sgml/datetime.sgml @@ -75,7 +75,7 @@ If the token is a text string, match up with possible strings: - + @@ -83,7 +83,7 @@ abbreviation. - + If not found, do a similar binary-search table lookup to match @@ -101,7 +101,7 @@ - + When the token is a number or number field: @@ -111,7 +111,7 @@ If there are eight or six digits, - and if no other date fields have been previously read, then interpret + and if no other date fields have been previously read, then interpret as a concatenated date (e.g., 19990118 or 990118). The interpretation is YYYYMMDD or YYMMDD. @@ -124,7 +124,7 @@ and a year has already been read, then interpret as day of year. - + If four or six digits and a year has already been read, then @@ -465,7 +465,7 @@ 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. @@ -544,7 +544,7 @@ $ cal 9 1752 the beginnings of the Chinese calendar can be traced back to the 14th century BC. Legend has it that the Emperor Huangdi invented that calendar in 2637 BC. - + The People's Republic of China uses the Gregorian calendar for civil purposes. The Chinese calendar is used for determining festivals. @@ -552,7 +552,7 @@ $ cal 9 1752 The Julian Date is unrelated to the Julian - calendar. + calendar. The Julian Date system was invented by the French scholar Joseph Justus Scaliger (1540-1609) and probably takes its name from Scaliger's father, diff --git a/doc/src/sgml/dfunc.sgml b/doc/src/sgml/dfunc.sgml index 689b14ffa55..155207bd3e4 100644 --- a/doc/src/sgml/dfunc.sgml +++ b/doc/src/sgml/dfunc.sgml @@ -160,7 +160,7 @@ cc -shared -o foo.so foo.o Here is an example. It assumes the developer tools are installed. -cc -c foo.c +cc -c foo.c cc -bundle -flat_namespace -undefined suppress -o foo.so foo.o @@ -226,7 +226,7 @@ gcc -G -o foo.so foo.o - Tru64 UNIX + Tru64 UNIX Tru64 UNIXshared library Digital UNIXTru64 UNIX @@ -272,7 +272,7 @@ gcc -shared -o foo.so foo.o - If this is too complicated for you, you should consider using + If this is too complicated for you, you should consider using GNU Libtool, which hides the platform differences behind a uniform interface. diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml index 5da2d61b20b..008ebcdcf61 100644 --- a/doc/src/sgml/docguide.sgml +++ b/doc/src/sgml/docguide.sgml @@ -240,7 +240,7 @@ It's possible that the ports do not update the main catalog file - in /usr/local/share/sgml/catalog.ports or order + in /usr/local/share/sgml/catalog.ports or order isn't proper . Be sure to have the following lines in beginning of file: CATALOG "openjade/catalog" @@ -613,7 +613,7 @@ gmake man - + To make a PDF: @@ -1059,7 +1059,7 @@ save_size.pdfjadetex = 15000 Norm Walsh offers a major mode - specifically for DocBook which also has font-lock and a number of features to + specifically for DocBook which also has font-lock and a number of features to reduce typing. @@ -1114,7 +1114,7 @@ save_size.pdfjadetex = 15000 - + Description @@ -1123,7 +1123,7 @@ save_size.pdfjadetex = 15000 - + Options @@ -1133,7 +1133,7 @@ save_size.pdfjadetex = 15000 - + Exit Status @@ -1144,7 +1144,7 @@ save_size.pdfjadetex = 15000 - + Usage @@ -1156,7 +1156,7 @@ save_size.pdfjadetex = 15000 - + Environment @@ -1167,7 +1167,7 @@ save_size.pdfjadetex = 15000 - + Files @@ -1178,7 +1178,7 @@ save_size.pdfjadetex = 15000 - + Diagnostics @@ -1191,7 +1191,7 @@ save_size.pdfjadetex = 15000 - + Notes @@ -1202,7 +1202,7 @@ save_size.pdfjadetex = 15000 - + Examples @@ -1211,7 +1211,7 @@ save_size.pdfjadetex = 15000 - + History @@ -1222,7 +1222,7 @@ save_size.pdfjadetex = 15000 - + See Also diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 387f50d6d02..83f396ad21a 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -110,7 +110,7 @@ EXEC SQL CONNECT TO target AS unix:postgresql://hostname:port/dbname?options - + an SQL string literal containing one of the above forms @@ -122,7 +122,7 @@ EXEC SQL CONNECT TO target AS a reference to a character variable containing one of the above forms (see examples) - + DEFAULT @@ -2743,7 +2743,6 @@ timestamp PGTYPEStimestamp_from_asc(char *str, char **endptr); The function returns the parsed timestamp on success. On error, PGTYPESInvalidTimestamp is returned and errno is set to PGTYPES_TS_BAD_TIMESTAMP. See for important notes on this value. - In general, the input string can contain any combination of an allowed @@ -2839,7 +2838,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt You can use the following format specifiers for the format mask. The format specifiers are the same ones that are used in the strftime function in libc. Any - non-format specifier will be copied into the output buffer. + non-format specifier will be copied into the output buffer. @@ -2897,24 +2896,24 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt %E* %O* - POSIX locale extensions. The sequences %Ec - %EC - %Ex - %EX - %Ey - %EY - %Od + %EC + %Ex + %EX + %Ey + %EY + %Od %Oe - %OH - %OI - %Om - %OM - %OS - %Ou - %OU - %OV - %Ow - %OW - %Oy + %OH + %OI + %Om + %OM + %OS + %Ou + %OU + %OV + %Ow + %OW + %Oy are supposed to provide alternative representations. @@ -5763,10 +5762,10 @@ ECPG = ecpg On Windows, if the ecpg libraries and an application are - compiled with different flags, this function call will crash the - application because the internal representation of the + compiled with different flags, this function call will crash the + application because the internal representation of the FILE pointers differ. Specifically, - multithreaded/single-threaded, release/debug, and static/dynamic + multithreaded/single-threaded, release/debug, and static/dynamic flags should be the same for the library and all applications using that library. @@ -5778,7 +5777,7 @@ ECPG = ecpg ECPGget_PGconn(const char *connection_name) returns the library database connection handle identified by the given name. If connection_name is set to NULL, the current - connection handle is returned. If no connection handle can be identified, the function returns + connection handle is returned. If no connection handle can be identified, the function returns NULL. The returned connection handle can be used to call any other functions from libpq, if necessary. @@ -5803,7 +5802,7 @@ ECPG = ecpg ECPGstatus(int lineno, const char* connection_name) returns true if you are connected to a database and false if not. - connection_name can be NULL + connection_name can be NULL if a single connection is being used. @@ -8064,7 +8063,7 @@ typedef struct sqlda_compat sqlda_t; Pointer to the field data. The pointer is of char * type, the data pointed by it is in a binary format. Example: -int intval; +int intval; switch (sqldata->sqlvar[i].sqltype) { @@ -8083,7 +8082,7 @@ switch (sqldata->sqlvar[i].sqltype) Pointer to the NULL indicator. If returned by DESCRIBE or FETCH then it's always a valid pointer. - If used as input for EXECUTE ... USING sqlda; then NULL-pointer value means + If used as input for EXECUTE ... USING sqlda; then NULL-pointer value means that the value for this field is non-NULL. Otherwise a valid pointer and sqlitype has to be properly set. Example: @@ -8117,7 +8116,7 @@ if (*(int2 *)sqldata->sqlvar[i].sqlind != 0) Type of the NULL indicator data. It's always SQLSMINT when returning data from the server. - When the SQLDA is used for a parametrized query, the data is treated + When the SQLDA is used for a parametrized query, the data is treated according to the set type. @@ -8143,13 +8142,13 @@ if (*(int2 *)sqldata->sqlvar[i].sqlind != 0) sqltypename - sqltypelen + sqltypelen sqlownerlen sqlsourcetype - sqlownername - sqlsourceid - sqlflags - sqlreserved + sqlownername + sqlsourceid + sqlflags + sqlreserved Unused. @@ -8469,7 +8468,7 @@ int dectoasc(decimal *np, char *cp, int len, int right) The function returns either -1 if the buffer cp was too small or ECPG_INFORMIX_OUT_OF_MEMORY if memory was - exhausted. + exhausted. @@ -9548,7 +9547,7 @@ risnull(CINTTYPE, (char *) &i); - + A pointer to the value or a pointer to the pointer. diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 2e8f77cf4fa..246451a42eb 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -9,7 +9,7 @@ In the sections that follow, we will discuss how you - can extend the PostgreSQL + can extend the PostgreSQL SQL query language by adding: @@ -45,8 +45,8 @@ How Extensibility Works - PostgreSQL is extensible because its operation is - catalog-driven. If you are familiar with standard + PostgreSQL is extensible because its operation is + catalog-driven. If you are familiar with standard relational database systems, you know that they store information about databases, tables, columns, etc., in what are commonly known as system catalogs. (Some systems call @@ -54,14 +54,14 @@ user as tables like any other, but the DBMS stores its internal bookkeeping in them. One key difference between PostgreSQL and standard relational database systems is - that PostgreSQL stores much more information in its + that PostgreSQL stores much more information in its catalogs: not only information about tables and columns, but also information about data types, functions, access methods, and so on. These tables can be modified by - the user, and since PostgreSQL bases its operation + the user, and since PostgreSQL bases its operation on these tables, this means that PostgreSQL can be extended by users. By comparison, conventional - database systems can only be extended by changing hardcoded + database systems can only be extended by changing hardcoded procedures in the source code or by loading modules specially written by the DBMS vendor. @@ -209,7 +209,7 @@ parsed. Each position (either argument or return value) declared as anyelement is allowed to have any specific actual data type, but in any given call they must all be the - same actual type. Each + same actual type. Each position declared as anyarray can have any array data type, but similarly they must all be the same type. If there are positions declared anyarray and others declared diff --git a/doc/src/sgml/external-projects.sgml b/doc/src/sgml/external-projects.sgml index 8927ef344b1..129b9814ebe 100644 --- a/doc/src/sgml/external-projects.sgml +++ b/doc/src/sgml/external-projects.sgml @@ -218,7 +218,7 @@
- + Extensions @@ -247,7 +247,7 @@ There are several administration tools available for PostgreSQL. The most popular is - pgAdmin III, + pgAdmin III, and there are several commercially available ones as well. diff --git a/doc/src/sgml/filelist.sgml b/doc/src/sgml/filelist.sgml index 39cfcee9617..4361991ea99 100644 --- a/doc/src/sgml/filelist.sgml +++ b/doc/src/sgml/filelist.sgml @@ -134,7 +134,7 @@ - + diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index e4d00b24031..6992aaa2817 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -30,7 +30,7 @@ is present in other SQL database management systems, and in many cases this functionality is compatible and consistent between the various implementations. This chapter is also - not exhaustive; additional functions appear in relevant sections of + not exhaustive; additional functions appear in relevant sections of the manual. @@ -416,7 +416,7 @@ IS NOT NULL, respectively, except that the input expression must be of Boolean type. - + - A relation scheme R is a + A relation scheme R is a finite set of attributes A1, A2, @@ -416,7 +416,7 @@ attributes are taken from. We often write a relation scheme as SELECT (σ): extracts tuples from a relation that - satisfy a given restriction. Let R be a + satisfy a given restriction. Let R be a table that contains an attribute A. σA=a(R) = {t ∈ R ∣ t(A) = a} @@ -447,7 +447,7 @@ attributes are taken from. We often write a relation scheme as S be a table with arity k2. R × S - is the set of all + is the set of all k1 + k2-tuples whose first k1 @@ -477,7 +477,7 @@ attributes are taken from. We often write a relation scheme as set of tuples that are in R and in S. - We again require that R and + We again require that R and S have the same arity. @@ -497,14 +497,14 @@ attributes are taken from. We often write a relation scheme as JOIN (∏): connects two tables by their common - attributes. Let R be a table with the - attributes A,B + attributes. Let R be a table with the + attributes A,B and C and let S be a table with the attributes C,D and E. There is one attribute common to both relations, - the attribute C. + the attribute C. @@ -45,7 +45,7 @@ ;; 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% +(define %content-title-end-punct% '(#\. #\! #\? #\:)) ;; No automatic punctuation after honorific name parts @@ -114,7 +114,7 @@ (normalize "author") (normalize "authorgroup") (normalize "title") - (normalize "subtitle") + (normalize "subtitle") (normalize "volumenum") (normalize "edition") (normalize "othercredit") @@ -214,7 +214,7 @@ (empty-sosofo))) ;; Add character encoding and time of creation into HTML header -(define %html-header-tags% +(define %html-header-tags% (list (list "META" '("HTTP-EQUIV" "Content-Type") '("CONTENT" "text/html; charset=ISO-8859-1")) (list "META" '("NAME" "creation") (list "CONTENT" (time->string (time) #t))))) @@ -332,7 +332,7 @@ (make element gi: "A" attributes: (list (list "TITLE" (element-title-string nextsib)) - (list "HREF" + (list "HREF" (href-to nextsib))) (gentext-nav-next-sibling nextsib)))) @@ -346,7 +346,7 @@ (make element gi: "A" attributes: (list (list "TITLE" (element-title-string next)) - (list "HREF" + (list "HREF" (href-to next)) (list "ACCESSKEY" @@ -556,7 +556,7 @@ (my-simplelist-vert members)) ((equal? type (normalize "horiz")) (simplelist-table 'row cols members))))) - + (element member (let ((type (inherited-attribute-string (normalize "type")))) (cond @@ -585,7 +585,7 @@ (let ((table (ancestor-member nd ($table-element-list$)))) (if (node-list-empty? table) nd - table))) + table))) ;; (The function below overrides the one in print/dbindex.dsl.) @@ -652,7 +652,7 @@ (define (part-titlepage elements #!optional (side 'recto)) - (let ((nodelist (titlepage-nodelist + (let ((nodelist (titlepage-nodelist (if (equal? side 'recto) (reference-titlepage-recto-elements) (reference-titlepage-verso-elements)) @@ -670,7 +670,7 @@ 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 @@ -679,7 +679,7 @@ (make paragraph line-spacing: 1pt (literal "")) - + (let loop ((nl nodelist) (lastnode (empty-node-list))) (if (node-list-empty? nl) (empty-sosofo) @@ -717,7 +717,7 @@ (define (reference-titlepage elements #!optional (side 'recto)) - (let ((nodelist (titlepage-nodelist + (let ((nodelist (titlepage-nodelist (if (equal? side 'recto) (reference-titlepage-recto-elements) (reference-titlepage-verso-elements)) @@ -735,7 +735,7 @@ 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 @@ -744,7 +744,7 @@ (make paragraph line-spacing: 1pt (literal "")) - + (let loop ((nl nodelist) (lastnode (empty-node-list))) (if (node-list-empty? nl) (empty-sosofo) @@ -812,13 +812,13 @@ Lynx, or similar). (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$)) diff --git a/doc/src/sgml/vacuumlo.sgml b/doc/src/sgml/vacuumlo.sgml index 76e2282ad6d..65f55f03c96 100644 --- a/doc/src/sgml/vacuumlo.sgml +++ b/doc/src/sgml/vacuumlo.sgml @@ -75,7 +75,7 @@ vacuumlo [options] database [database2 ... databaseN] Force vacuumlo to prompt for a - password before connecting to a database. + password before connecting to a database. diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 2266d549ff5..a2724fad6b0 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -390,7 +390,7 @@ are points in the sequence of transactions at which it is guaranteed that the heap and index data files have been updated with all information written before the checkpoint. At checkpoint time, all dirty data pages are flushed to - disk and a special checkpoint record is written to the log file. + disk and a special checkpoint record is written to the log file. (The changes were previously flushed to the WAL files.) In the event of a crash, the crash recovery procedure looks at the latest checkpoint record to determine the point in the log (known as the redo diff --git a/doc/src/sgml/xindex.sgml b/doc/src/sgml/xindex.sgml index 8c829a9df7f..8f9fd21f386 100644 --- a/doc/src/sgml/xindex.sgml +++ b/doc/src/sgml/xindex.sgml @@ -373,7 +373,7 @@ - consistent - determine whether key satisfies the + consistent - determine whether key satisfies the query qualifier 1 @@ -387,12 +387,12 @@ 3 - decompress - compute a decompressed representation of a + decompress - compute a decompressed representation of a compressed key 4 - penalty - compute penalty for inserting new key into subtree + penalty - compute penalty for inserting new key into subtree with given subtree's key 5 @@ -940,7 +940,7 @@ SELECT * FROM table WHERE integer_column < 4; can be satisfied exactly by a B-tree index on the integer column. But there are cases where an index is useful as an inexact guide to the matching rows. For example, if a GiST index stores only bounding boxes - for geometric objects, then it cannot exactly satisfy a WHERE + for geometric objects, then it cannot exactly satisfy a WHERE condition that tests overlap between nonrectangular objects such as polygons. Yet we could use the index to find objects whose bounding box overlaps the bounding box of the target object, and then do the diff --git a/doc/src/sgml/xoper.sgml b/doc/src/sgml/xoper.sgml index a2592c304db..ea64a152f7e 100644 --- a/doc/src/sgml/xoper.sgml +++ b/doc/src/sgml/xoper.sgml @@ -52,7 +52,7 @@ CREATE OPERATOR + ( Now we could execute a query like this: - + SELECT (a + b) AS c FROM test_complex; diff --git a/doc/src/sgml/xtypes.sgml b/doc/src/sgml/xtypes.sgml index b020f28e876..972cc76bf9b 100644 --- a/doc/src/sgml/xtypes.sgml +++ b/doc/src/sgml/xtypes.sgml @@ -207,7 +207,7 @@ CREATE FUNCTION complex_send(complex) Finally, we can provide the full definition of the data type: CREATE TYPE complex ( - internallength = 16, + internallength = 16, input = complex_in, output = complex_out, receive = complex_recv, -- cgit v1.2.3