More doc cleanups

This commit is contained in:
Bruce Momjian 2000-07-21 17:58:49 +00:00
parent c62e961da1
commit c281847fcd
3 changed files with 14 additions and 14 deletions

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.13 2000/03/27 17:14:42 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/create_operator.sgml,v 1.14 2000/07/21 17:58:49 momjian Exp $
Postgres documentation Postgres documentation
--> -->
@ -393,7 +393,7 @@ MYBOXES.description === box '((0,0),(1,1))'
Usage Usage
</title> </title>
<para>The following command defines a new operator, <para>The following command defines a new operator,
area-equality, for the BOX data type. area-equality, for the BOX data type:
</para> </para>
<programlisting> <programlisting>
CREATE OPERATOR === ( CREATE OPERATOR === (

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.11 2000/07/21 03:14:33 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/postgres-ref.sgml,v 1.12 2000/07/21 17:58:49 momjian Exp $
Postgres documentation Postgres documentation
--> -->
@ -126,7 +126,7 @@ postgres [ -B <replaceable class="parameter">nBuffers</replaceable> ] [ -C ] [ -
<para> <para>
Override restrictions, so system table structures can be modified. Override restrictions, so system table structures can be modified.
These tables are typically those with a leading These tables are typically those with a leading
"<literal>pg_</literal>" in the table name. <literal>pg_</literal> in the table name.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -136,9 +136,9 @@ postgres [ -B <replaceable class="parameter">nBuffers</replaceable> ] [ -C ] [ -
<listitem> <listitem>
<para> <para>
Ignore system indexes to scan/update system Ignore system indexes to scan/update system
tuples. <command>REINDEX</command> for system tables/indexes tuples. The <command>REINDEX</command> for system tables/indexes
requires this option. System tables are requires this option. System tables are
typically those with a leading "<literal>pg_</literal>" in the typically those with a leading <literal>pg_</literal> in the
table name. table name.
</para> </para>
</listitem> </listitem>

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.33 2000/05/12 00:54:52 momjian Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/ref/psql-ref.sgml,v 1.34 2000/07/21 17:58:49 momjian Exp $
Postgres documentation Postgres documentation
--> -->
@ -491,8 +491,8 @@ testdb=>
<para> <para>
The new query buffer is then re-parsed according to the normal rules of The new query buffer is then re-parsed according to the normal rules of
<application>psql</application>, where the whole buffer is treated as <application>psql</application>, where the whole buffer is treated as
a single line. (Thus you cannot make <quote>scripts</quote> this way, a single line. (Thus you cannot make scripts this way.
use <command>\i</command> for that.) This means also that Use <command>\i</command> for that.) This means also that
if the query ends with (or rather contains) a semicolon, it is immediately if the query ends with (or rather contains) a semicolon, it is immediately
executed. In other cases it will merely wait in the query buffer. executed. In other cases it will merely wait in the query buffer.
</para> </para>
@ -551,8 +551,8 @@ Tue Oct 26 21:40:57 CEST 1999
<listitem> <listitem>
<para> <para>
Sets the field separator for unaligned query output. The default is <quote><literal>|</literal></quote> Sets the field separator for unaligned query output. The default is
(a <quote>pipe</quote> symbol). See also <command>\pset</command> for a generic way pipe (<literal>|</literal>). See also <command>\pset</command> for a generic way
of setting output options. of setting output options.
</para> </para>
</listitem> </listitem>
@ -1533,7 +1533,7 @@ Access permissions for database "test"
<para> <para>
As of version 7.0, <application>psql</application> automatically issues a As of version 7.0, <application>psql</application> automatically issues a
password prompt whenever the backend requests password authentication. password prompt whenever the backend requests password authentication.
Because this is currently based on a <quote>hack</quote>, the automatic Because this is currently based on a hack, the automatic
recognition might mysteriously fail, hence this option to force a prompt. recognition might mysteriously fail, hence this option to force a prompt.
If no password prompt is issued and the backend requires password authentication If no password prompt is issued and the backend requires password authentication
the connection attempt will fail. the connection attempt will fail.
@ -2148,7 +2148,7 @@ $ ./configure --with-includes=/opt/gnu/include --with-libs=/opt/gnu/lib ...
<para> <para>
The first example shows how to spread a query over several lines of input. The first example shows how to spread a query over several lines of input.
Notice the changing prompt. Notice the changing prompt:
<programlisting> <programlisting>
testdb=> <userinput>CREATE TABLE my_table (</userinput> testdb=> <userinput>CREATE TABLE my_table (</userinput>
testdb(> <userinput> first integer not null default 0,</userinput> testdb(> <userinput> first integer not null default 0,</userinput>
@ -2186,7 +2186,7 @@ peter@localhost testdb=> SELECT * FROM my_table;
</programlisting> </programlisting>
Notice how the int4 colums in right aligned while the text column in left aligned. Notice how the int4 colums in right aligned while the text column in left aligned.
You can make this table look differently by using the <command>\pset</command> You can make this table look differently by using the <command>\pset</command>
command. command:
<programlisting> <programlisting>
peter@localhost testdb=> <userinput>\pset border 2</userinput> peter@localhost testdb=> <userinput>\pset border 2</userinput>
Border style is 2. Border style is 2.