-<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.107 2007/10/16 19:44:18 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.108 2007/11/28 15:42:30 petere Exp $ -->
<chapter id="backup">
<title>Backup and Restore</title>
(The path name is relative to the working directory of the server,
i.e., the cluster's data directory.)
Any <literal>%r</> is replaced by the name of the file containing the
- last valid restartpoint. That is the earliest file that must be kept
+ last valid restart point. That is the earliest file that must be kept
to allow a restore to be restartable, so this information can be used
to truncate the archive to just the minimum required to support
restart of the current restore. <literal>%r</> would only be used in a
<para>
The size of the WAL archive can be minimized by using the <literal>%r</>
option of the <varname>restore_command</>. This option specifies the
- last archive filename that needs to be kept to allow the recovery to
+ last archive file name that needs to be kept to allow the recovery to
restart correctly. This can be used to truncate the archive once
files are no longer required, if the archive is writable from the
standby server.
-<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.157 2007/11/28 05:01:24 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.158 2007/11/28 15:42:30 petere Exp $ -->
<chapter Id="runtime-config">
<title>Server Configuration</title>
</indexterm>
<listitem>
<para>
- Sets the realm to match Kerberos, GSSAPI and SSPI usernames against.
+ Sets the realm to match Kerberos, GSSAPI and SSPI user names against.
See <xref linkend="kerberos-auth">, <xref linkend="gssapi-auth"> or
<xref linkend="sspi-auth"> for details. This parameter can only be
set at server start.
Including <literal>csvlog</> in the <varname>log_destination</> list
provides a convenient way to import log files into a database table.
This option emits log lines in comma-separated-value format,
- with these columns: timestamp with milliseconds, username, database
- name, session id, host:port number, process id, per-process line
- number, command tag, session start time, virtual transaction id,
+ with these columns: timestamp with milliseconds, user name, database
+ name, session ID, host:port number, process ID, per-process line
+ number, command tag, session start time, virtual transaction ID,
regular transaction id, error severity, SQL state code, error message.
Here is a sample table definition for storing CSV-format log output:
- </para>
<programlisting>
CREATE TABLE postgres_log
PRIMARY KEY (session_id, process_line_num)
);
</programlisting>
+ </para>
<para>
To import a log file into this table, use the <command>COPY FROM</>
command:
- </para>
<programlisting>
COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
</programlisting>
+ </para>
<para>
There are a few things you need to do to simplify importing CSV log
<listitem>
<para>
Set <varname>log_rotation_size</varname> to 0 to disable
- size-based log rotation, as it makes the log filename difficult
+ size-based log rotation, as it makes the log file name difficult
to predict.
</para>
</listitem>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.76 2007/06/20 23:11:38 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.77 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="ddl">
<title>Data Definition</title>
range tests for range partitioning, as illustrated in the preceding
examples. A good rule of thumb is that partitioning constraints should
contain only comparisons of the partitioning column(s) to constants
- using btree-indexable operators.
+ using B-tree-indexable operators.
</para>
</listitem>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.413 2007/11/28 05:13:41 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.414 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="functions">
<title>Functions and Operators</title>
<entry>
<acronym>ASCII</acronym> code of the first character of the
argument. For <acronym>UTF8</acronym> returns the Unicode code
- point of the character. For other multi-byte encodings. the
+ point of the character. For other multibyte encodings. the
argument must be a strictly <acronym>ASCII</acronym> character.
</entry>
<entry><literal>ascii('x')</literal></entry>
<entry><type>text</type></entry>
<entry>
Character with the given code. For <acronym>UTF8</acronym> the
- argument is treated as a Unicode code point. For other multi-byte
+ argument is treated as a Unicode code point. For other multibyte
encodings the argument must designate a strictly
<acronym>ASCII</acronym> character.
</entry>
<parameter>src_encoding</parameter>. The
<parameter>string</parameter> must be valid in this encoding.
Conversions can be defined by <command>CREATE CONVERSION</command>.
- Also there are some pre-defined conversions. See <xref
+ Also there are some predefined conversions. See <xref
linkend="conversion-names"> for available conversions.
</entry>
<entry><literal>convert('text_in_utf8', 'UTF8', 'LATIN1')</literal></entry>
<para>
Notice that except for the two-argument form of <function>enum_range</>,
these functions disregard the specific value passed to them; they care
- only about its declared datatype. Either NULL or a specific value of
+ only about its declared data type. Either null or a specific value of
the type can be passed, with the same result. It is more common to
apply these functions to a table column or function argument than to
a hardwired type name as suggested by the examples.
...
]]></screen>
- If no table name is avaible, that is, when mapping a query or a
+ If no table name is available, that is, when mapping a query or a
cursor, the string <literal>table</literal> is used in the first
format, <literal>row</literal> in the second format.
</para>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.28 2007/11/28 10:10:14 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.29 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="high-availability">
<title>High Availability, Load Balancing, and Replication</title>
<para>
Performance must be considered in any choice. There is usually a
- tradeoff between functionality and
+ trade-off between functionality and
performance. For example, a full synchronous solution over a slow
network might cut performance by more than half, while an asynchronous
one might have a minimal performance impact.
</varlistentry>
<varlistentry>
- <term>Asynchronous Multi-Master Replication</term>
+ <term>Asynchronous Multimaster Replication</term>
<listitem>
<para>
For servers that are not regularly connected, like laptops or
remote servers, keeping data consistent among servers is a
- challenge. Using asynchronous multi-master replication, each
+ challenge. Using asynchronous multimaster replication, each
server works independently, and periodically communicates with
the other servers to identify conflicting transactions. The
conflicts can be resolved by users or conflict resolution rules.
</varlistentry>
<varlistentry>
- <term>Synchronous Multi-Master Replication</term>
+ <term>Synchronous Multimaster Replication</term>
<listitem>
<para>
- In synchronous multi-master replication, each server can accept
+ In synchronous multimaster replication, each server can accept
write requests, and modified data is transmitted from the
original server to every other server before each transaction
commits. Heavy write activity can cause excessive locking,
leading to poor performance. In fact, write performance is
often worse than that of a single server. Read requests can
be sent to any server. Some implementations use shared disk
- to reduce the communication overhead. Synchronous multi-master
+ to reduce the communication overhead. Synchronous multimaster
replication is best for mostly read workloads, though its big
advantage is that any server can accept write requests —
there is no need to partition workloads between master and
<entry>Warm Standby Using PITR</entry>
<entry>Master-Slave Replication</entry>
<entry>Statement-Based Replication Middleware</entry>
- <entry>Asynchronous Multi-Master Replication</entry>
- <entry>Synchronous Multi-Master Replication</entry>
+ <entry>Asynchronous Multimaster Replication</entry>
+ <entry>Synchronous Multimaster Replication</entry>
</row>
</thead>
</varlistentry>
<varlistentry>
- <term>Multi-Server Parallel Query Execution</term>
+ <term>Multiple-Server Parallel Query Execution</term>
<listitem>
<para>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/install-win32.sgml,v 1.41 2007/08/03 10:47:10 mha Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/install-win32.sgml,v 1.42 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="install-win32">
<title>Installation on <productname>Windows</productname></title>
<term><productname>ActiveState Perl</productname></term>
<listitem><para>
ActiveState Perl is required to run the build generation scripts. MinGW
- or Cygwin perl will not work. It must also be present in the PATH.
+ or Cygwin Perl will not work. It must also be present in the PATH.
Binaries can be downloaded from
<ulink url="http://www.activestate.com"></>.
</para></listitem>
</userinput>
</screen>
To change the default build configuration to debug, put the following
- in the buildenv.bat file:
+ in the <filename>buildenv.bat</filename> file:
<screen>
<userinput>
set CONFIG=Debug
<para>
To run the regression tests, make sure you have completed the build of all
required parts first. Also, make sure that the DLLs required to load all
- parts of the system (such as the perl and python DLLs for the procedural
- languages) are present in the system PATH. If they are not, set it through
+ parts of the system (such as the Perl and Python DLLs for the procedural
+ languages) are present in the system path. If they are not, set it through
the <filename>buildenv.bat</filename> file. To run the tests, run one of
the following commands from the <filename>src\tools\msvc</filename>
directory:
</screen>
To change the schedule used (default is the parallel), append it to the
- commandline like:
+ command line like:
<screen>
<userinput>
vcregress check serial
</varlistentry>
<varlistentry>
- <term>DocBook DSSL 1.79</term>
+ <term>DocBook DSSSL 1.79</term>
<listitem><para>
Download from
<ulink url="http://sourceforge.net/project/downloading.php?groupname=docbook&filename=docbook-dsssl-1.79.zip"></>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.297 2007/11/05 17:43:20 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.298 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
<term><envar>TCLSH</envar></term>
<listitem>
<para>
- Full path to the Tcl interpreter. This wil be used to
+ Full path to the Tcl interpreter. This will be used to
determine the dependencies for building PL/Tcl.
</para>
</listitem>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.246 2007/09/26 08:45:50 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.247 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="libpq">
<title><application>libpq</application> - C Library</title>
used. (Therefore, put more-specific entries first when you are using
wildcards.) If an entry needs to contain <literal>:</literal> or
<literal>\</literal>, escape this character with <literal>\</literal>.
- A host name of <literal>localhost</> matches both TCP (hostname
+ A host name of <literal>localhost</> matches both TCP (host name
<literal>localhost</>) and Unix domain socket (<literal>pghost</> empty
or the default socket directory) connections coming from the local
machine.
-<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.84 2007/10/07 01:16:42 alvherre Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.85 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="maintenance">
<title>Routine Database Maintenance Tasks</title>
<command>UPDATE</> or <command>DELETE</> of a row does not
immediately remove the old version of the row.
This approach is necessary to gain the benefits of multiversion
- concurrency control (see <xref linkend="mvcc">): the row version
+ concurrency control (see <xref linkend="mvcc">): the row versions
must not be deleted while it is still potentially visible to other
transactions. But eventually, an outdated or deleted row version is no
longer of interest to any transaction. The space it occupies must be
<para>
Beginning in <productname>PostgreSQL</productname> 8.3, autovacuum has a
- multi-process architecture: there is a daemon process, called the
+ multiprocess architecture: There is a daemon process, called the
<firstterm>autovacuum launcher</firstterm>, which is in charge of starting
an <firstterm>autovacuum worker</firstterm> process on each database every
<xref linkend="guc-autovacuum-naptime"> seconds. On each run, the worker
-<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.54 2007/09/25 20:03:37 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.55 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="monitoring">
<title>Monitoring Database Activity</title>
<entry>One row only, showing cluster-wide statistics from the
background writer: number of scheduled checkpoints, requested
checkpoints, buffers written by checkpoints and cleaning scans,
- and the number of times the bgwriter stopped a cleaning scan
+ and the number of times the background writer stopped a cleaning scan
because it had written too many buffers. Also includes
statistics about the shared buffer pool, including buffers written
by backends (that is, not by the background writer) and total buffers
<entry><literal><function>pg_stat_get_bgwriter_timed_checkpoints</function>()</literal></entry>
<entry><type>bigint</type></entry>
<entry>
- The number of times the bgwriter has started timed checkpoints
+ The number of times the background writer has started timed checkpoints
(because the <varname>checkpoint_timeout</varname> time has expired)
</entry>
</row>
<entry><literal><function>pg_stat_get_bgwriter_requested_checkpoints</function>()</literal></entry>
<entry><type>bigint</type></entry>
<entry>
- The number of times the bgwriter has started checkpoints based
+ The number of times the background writer has started checkpoints based
on requests from backends because the <varname>checkpoint_segments</varname>
has been exceeded or because the <command>CHECKPOINT</command>
command has been issued
<entry><literal><function>pg_stat_get_bgwriter_buf_written_checkpoints</function>()</literal></entry>
<entry><type>bigint</type></entry>
<entry>
- The number of buffers written by the bgwriter during checkpoints
+ The number of buffers written by the background writer during checkpoints
</entry>
</row>
<entry><literal><function>pg_stat_get_bgwriter_buf_written_clean</function>()</literal></entry>
<entry><type>bigint</type></entry>
<entry>
- The number of buffers written by the bgwriter for routine cleaning of
+ The number of buffers written by the background writer for routine cleaning of
dirty pages
</entry>
</row>
<entry><literal><function>pg_stat_get_bgwriter_maxwritten_clean</function>()</literal></entry>
<entry><type>bigint</type></entry>
<entry>
- The number of times the bgwriter has stopped its cleaning scan because
+ The number of times the background writer has stopped its cleaning scan because
it has written more buffers than specified in the
<varname>bgwriter_lru_maxpages</varname> parameter
</entry>
<para>
You should take care that the data types specified for the probe arguments
- match the datatypes of the variables used in the <literal>PG_TRACE</>
+ match the data types of the variables used in the <literal>PG_TRACE</>
macro. This is not checked at compile time. You can check that your newly
added trace point is available by recompiling, then running the new binary,
and as root, executing a DTrace command such as:
-<!-- $PostgreSQL: pgsql/doc/src/sgml/perform.sgml,v 1.66 2007/10/22 21:34:33 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/perform.sgml,v 1.67 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="performance-tips">
<title>Performance Tips</title>
<xref linkend="guc-from-collapse-limit"> and <xref
linkend="guc-join-collapse-limit">
are similarly named because they do almost the same thing: one controls
- when the planner will <quote>flatten out</> subselects, and the
+ when the planner will <quote>flatten out</> subqueries, and the
other controls when it will flatten out explicit joins. Typically
you would either set <varname>join_collapse_limit</> equal to
- <varname>from_collapse_limit</> (so that explicit joins and subselects
+ <varname>from_collapse_limit</> (so that explicit joins and subqueries
act similarly) or set <varname>join_collapse_limit</> to 1 (if you want
to control join order with explicit joins). But you might set them
differently if you are trying to fine-tune the trade-off between planning
-<!-- $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.117 2007/10/26 01:11:09 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.118 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="plpgsql">
<title><application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language</title>
where <literal>search_term</> is a <application>PL/pgSQL</application>
variable. The cached plan for this query will never use an index on
<structfield>word</>, since the planner cannot assume that the
- <literal>LIKE</> pattern will be left-anchored at runtime. To use
+ <literal>LIKE</> pattern will be left-anchored at run time. To use
an index the query must be planned with a specific constant
<literal>LIKE</> pattern provided. This is another situation where
<command>EXECUTE</command> can be used to force a new plan to be
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.97 2007/05/17 23:36:04 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.98 2007/11/28 15:42:31 petere Exp $
PostgreSQL documentation
-->
of course the integrity of the constraint cannot be guaranteed if the
triggers are not executed.
The trigger firing mechanism is also affected by the configuration
- variable <xref linkend="guc-session-replication-role">. Simply ENABLEd
+ variable <xref linkend="guc-session-replication-role">. Simply enabled
triggers will fire when the replication role is <quote>origin</>
(the default) or <quote>local</>. Triggers configured <literal>ENABLE REPLICA</literal>
will only fire if the session is in <quote>replica</> mode and triggers
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.48 2007/02/01 00:28:18 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.49 2007/11/28 15:42:31 petere Exp $
PostgreSQL documentation
-->
<para>
The obsolete options <literal>SORT1</>, <literal>SORT2</>,
<literal>LTCMP</>, and <literal>GTCMP</> were formerly used to
- specify the names of sort operators associated with a mergejoinable
+ specify the names of sort operators associated with a merge-joinable
operator. This is no longer necessary, since information about
- associated operators is found by looking at btree operator families
+ associated operators is found by looking at B-tree operator families
instead. If one of these options is given, it is ignored except
for implicitly setting <literal>MERGES</> true.
</para>
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/delete.sgml,v 1.31 2007/06/11 01:16:21 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/delete.sgml,v 1.32 2007/11/28 15:42:31 petere Exp $
PostgreSQL documentation
-->
from this cursor. The cursor must be a simple (non-join, non-aggregate)
query on the <command>DELETE</>'s target table.
Note that <literal>WHERE CURRENT OF</> cannot be
- specified together with a boolean condition.
+ specified together with a Boolean condition.
</para>
</listitem>
</varlistentry>
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/explain.sgml,v 1.40 2007/04/12 22:39:21 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/explain.sgml,v 1.41 2007/11/28 15:42:31 petere Exp $
PostgreSQL documentation
-->
</para>
<para>
- In order to measure the runtime cost of each node in the execution
+ In order to measure the run-time cost of each node in the execution
plan, the current implementation of <command>EXPLAIN
ANALYZE</command> can add considerable profiling overhead to query
execution. As a result, running <command>EXPLAIN ANALYZE</command>
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/select.sgml,v 1.101 2007/06/08 20:26:18 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/select.sgml,v 1.102 2007/11/28 15:42:31 petere Exp $
PostgreSQL documentation
-->
assumed by default. Alternatively, a specific ordering operator
name can be specified in the <literal>USING</> clause.
An ordering operator must be a less-than or greater-than
- member of some btree operator family.
+ member of some B-tree operator family.
<literal>ASC</> is usually equivalent to <literal>USING <</> and
<literal>DESC</> is usually equivalent to <literal>USING ></>.
(But the creator of a user-defined data type can define exactly what the
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/update.sgml,v 1.44 2007/06/11 01:16:22 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/update.sgml,v 1.45 2007/11/28 15:42:31 petere Exp $
PostgreSQL documentation
-->
from this cursor. The cursor must be a simple (non-join, non-aggregate)
query on the <command>UPDATE</>'s target table.
Note that <literal>WHERE CURRENT OF</> cannot be
- specified together with a boolean condition.
+ specified together with a Boolean condition.
</para>
</listitem>
</varlistentry>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.385 2007/11/08 15:21:03 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.386 2007/11/28 15:42:31 petere Exp $ -->
<chapter Id="runtime">
<title>Operating System Environment</title>
<acronym>NFS</> implementations have non-standard semantics, this can
cause reliability problems (see <ulink
url="http://www.time-travellers.org/shane/papers/NFS_considered_harmful.html"></ulink>).
- Specifically, delayed (asynchonous) writes to the <acronym>NFS</>
+ Specifically, delayed (asynch
ronous) writes to the <acronym>NFS</>
server can cause reliability problems; if possible, mount
- <acronym>NFS</> file systems synchonously (without caching) to avoid
+ <acronym>NFS</> file systems synchronously (without caching) to avoid
this. (Storage Area Networks (<acronym>SAN</>) use a low-level
communication protocol rather than <acronym>NFS</>.)
</para>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/textsearch.sgml,v 1.38 2007/11/20 15:58:52 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/textsearch.sgml,v 1.39 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="textsearch">
<title id="textsearch-title">Full Text Search</title>
Textual search operators have existed in databases for years.
<productname>PostgreSQL</productname> has
<literal>~</literal>, <literal>~*</literal>, <literal>LIKE</literal>, and
- <literal>ILIKE</literal> operators for textual datatypes, but they lack
+ <literal>ILIKE</literal> operators for textual data types, but they lack
many essential properties required by modern information systems:
</para>
<listitem>
<para>
- Map synonyms to a single word using <application>ispell</>.
+ Map synonyms to a single word using <application>Ispell</>.
</para>
</listitem>
<listitem>
<para>
Map different variations of a word to a canonical form using
- an <application>ispell</> dictionary.
+ an <application>Ispell</> dictionary.
</para>
</listitem>
<para>
<function>to_tsquery</function> creates a <type>tsquery</> value from
<replaceable>querytext</replaceable>, which must consist of single tokens
- separated by the boolean operators <literal>&</literal> (AND),
+ separated by the Boolean operators <literal>&</literal> (AND),
<literal>|</literal> (OR) and <literal>!</literal> (NOT). These operators
can be grouped using parentheses. In other words, the input to
<function>to_tsquery</function> must already follow the general rules for
<function>plainto_tsquery</> transforms unformatted text
<replaceable>querytext</replaceable> to <type>tsquery</type>.
The text is parsed and normalized much as for <function>to_tsvector</>,
- then the <literal>&</literal> (AND) boolean operator is inserted
+ then the <literal>&</literal> (AND) Boolean operator is inserted
between surviving words.
</para>
</programlisting>
Note that <function>plainto_tsquery</> cannot
- recognize either boolean operators or weight labels in its input:
+ recognize either Boolean operators or weight labels in its input:
<programlisting>
SELECT plainto_tsquery('english', 'The Fat & Rats:C');
</listitem>
<listitem>
<para>
- <literal>HighlightAll</literal>: boolean flag; if
+ <literal>HighlightAll</literal>: Boolean flag; if
<literal>true</literal> the whole document will be highlighted.
</para>
</listitem>
<type>tsvector</type> summary, so it can be slow and should be used with
care. A typical mistake is to call <function>ts_headline</function> for
<emphasis>every</emphasis> matching document when only ten documents are
- to be shown. <acronym>SQL</acronym> subselects can help; here is an
+ to be shown. <acronym>SQL</acronym> subqueries can help; here is an
example:
<programlisting>
<listitem>
<para>
- Linguistic - ispell dictionaries try to reduce input words to a
+ Linguistic - Ispell dictionaries try to reduce input words to a
normalized form; stemmer dictionaries remove word endings
</para>
</listitem>
</programlisting>
Below we create a dictionary and bind some token types to
- an astronomical thesaurus and english stemmer:
+ an astronomical thesaurus and English stemmer:
<programlisting>
CREATE TEXT SEARCH DICTIONARY thesaurus_astro (
Several predefined text search configurations are available, and
you can create custom configurations easily. To facilitate management
of text search objects, a set of <acronym>SQL</acronym> commands
- is available, and there are several psql commands that display information
+ is available, and there are several <application>psql</application> commands that display information
about text search objects (<xref linkend="textsearch-psql">).
</para>
);
</programlisting>
- Next we register the <productname>ispell</> dictionary
+ Next we register the <productname>Ispell</> dictionary
<literal>english_ispell</literal>, which has its own configuration files:
<programlisting>
<para>
For a more extensive demonstration, we
first create a <literal>public.english</literal> configuration and
- ispell dictionary for the English language:
+ Ispell dictionary for the English language:
</para>
<programlisting>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.45 2007/08/01 22:45:07 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/wal.sgml,v 1.46 2007/11/28 15:42:31 petere Exp $ -->
<chapter id="wal">
<title>Reliability and the Write-Ahead Log</title>
<firstterm>Asynchronous commit</> is an option that allows transactions
to complete more quickly, at the cost that the most recent transactions may
be lost if the database should crash. In many applications this is an
- acceptable tradeoff.
+ acceptable trade-off.
</para>
<para>
<para>
The user can select the commit mode of each transaction, so that
it is possible to have both synchronous and asynchronous commit
- transactions running concurrently. This allows flexible tradeoffs
+ transactions running concurrently. This allows flexible trade-offs
between performance and certainty of transaction durability.
The commit mode is controlled by the user-settable parameter
<xref linkend="guc-synchronous-commit">, which can be changed in any of
Certain utility commands, for instance <command>DROP TABLE</>, are
forced to commit synchronously regardless of the setting of
<varname>synchronous_commit</varname>. This is to ensure consistency
- between the server's filesystem and the logical state of the database.
+ between the server's file system and the logical state of the database.
The commands supporting two-phase commit, such as <command>PREPARE
TRANSACTION</>, are also always synchronous.
</para>
<acronym>WAL</acronym> records,
then changes made during that transaction <emphasis>will</> be lost.
The duration of the
- risk window is limited because a background process (the <quote>wal
+ risk window is limited because a background process (the <quote>WAL
writer</>) flushes unwritten <acronym>WAL</acronym> records to disk
every <xref linkend="guc-wal-writer-delay"> milliseconds.
The actual maximum duration of the risk window is three times
- <varname>wal_writer_delay</varname> because the wal writer is
+ <varname>wal_writer_delay</varname> because the WAL writer is
designed to favor writing whole pages at a time during busy periods.
</para>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/xoper.sgml,v 1.42 2007/02/06 04:38:31 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/xoper.sgml,v 1.43 2007/11/28 15:42:31 petere Exp $ -->
<sect1 id="xoper">
<title>User-Defined Operators</title>
some form of equality. In most cases it is only practical to support
hashing for operators that take the same data type on both sides.
However, sometimes it is possible to design compatible hash functions
- for two or more datatypes; that is, functions that will generate the
+ for two or more data types; that is, functions that will generate the
same hash codes for <quote>equal</> values, even though the values
have different representations. For example, it's fairly simple
to arrange this property when hashing integers of different widths.
if they are different) that appears in the same operator family.
If this is not the case, planner errors might occur when the operator
is used. Also, it is a good idea (but not strictly required) for
- a hash operator family that supports multiple datatypes to provide
- equality operators for every combination of the datatypes; this
+ a hash operator family that supports multiple data types to provide
+ equality operators for every combination of the data types; this
allows better optimization.
</para>
if they are different) that appears in the same operator family.
If this is not the case, planner errors might occur when the operator
is used. Also, it is a good idea (but not strictly required) for
- a btree operator family that supports multiple datatypes to provide
- equality operators for every combination of the datatypes; this
+ a btree operator family that supports multiple data types to provide
+ equality operators for every combination of the data types; this
allows better optimization.
</para>
projects / postgresql / commitdiff