Skip to content

Commit 731204e

Browse files
peterepetere
committed
Editorial review
1 parent a510bf4 commit 731204e

35 files changed

+1391
-1328
lines changed

‎doc/src/sgml/biblio.sgml

Lines changed: 1 addition & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/biblio.sgml,v 1.16 2001/11/21 05:53:40 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/biblio.sgml,v 1.17 2002/01/07 02:29:11 petere Exp $
33
-->
44

55
<bibliography id="biblio">
@@ -148,76 +148,6 @@ $Header: /cvsroot/pgsql/doc/src/sgml/biblio.sgml,v 1.16 2001/11/21 05:53:40 thom
148148
<title>PostgreSQL-Specific Documentation</title>
149149
<para>This section is for related documentation.</para>
150150

151-
<biblioentry id="admin-guide">
152-
<title>The <productname>PostgreSQL</productname> Administrator's Guide</title>
153-
<titleabbrev>The Administrator's Guide</titleabbrev>
154-
<editor>
155-
<firstname>Thomas</firstname>
156-
<surname>Lockhart</surname>
157-
</editor>
158-
159-
<pubdate>2001-04-13</pubdate>
160-
<publisher>
161-
<publishername>The PostgreSQL Global Development Group</publishername>
162-
</publisher>
163-
</biblioentry>
164-
165-
<biblioentry id="dev-guide">
166-
<title>The <productname>PostgreSQL</productname> Developer's Guide</title>
167-
<titleabbrev>The Developer's Guide</titleabbrev>
168-
<editor>
169-
<firstname>Thomas</firstname>
170-
<surname>Lockhart</surname>
171-
</editor>
172-
173-
<pubdate>2001-04-13</pubdate>
174-
<publisher>
175-
<publishername>The PostgreSQL Global Development Group</publishername>
176-
</publisher>
177-
</biblioentry>
178-
179-
<biblioentry id="pro-guide">
180-
<title>The <productname>PostgreSQL</productname> Programmer's Guide</title>
181-
<titleabbrev>The Programmer's Guide</titleabbrev>
182-
<editor>
183-
<firstname>Thomas</firstname>
184-
<surname>Lockhart</surname>
185-
</editor>
186-
187-
<pubdate>2001-04-13</pubdate>
188-
<publisher>
189-
<publishername>The PostgreSQL Global Development Group</publishername>
190-
</publisher>
191-
</biblioentry>
192-
193-
<biblioentry id="tutorial-guide">
194-
<title>The <productname>PostgreSQL</productname> Tutorial Introduction</title>
195-
<titleabbrev>The Tutorial</titleabbrev>
196-
<editor>
197-
<firstname>Thomas</firstname>
198-
<surname>Lockhart</surname>
199-
</editor>
200-
201-
<pubdate>2001-04-13</pubdate>
202-
<publisher>
203-
<publishername>The PostgreSQL Global Development Group</publishername>
204-
</publisher>
205-
</biblioentry>
206-
207-
<biblioentry id="users-guide">
208-
<title>The <productname>PostgreSQL</productname> User's Guide</title>
209-
<titleabbrev>The User's Guide</titleabbrev>
210-
<editor>
211-
<firstname>Thomas</firstname>
212-
<surname>Lockhart</surname>
213-
</editor>
214-
215-
<pubdate>2001-04-13</pubdate>
216-
<publisher>
217-
<publishername>The PostgreSQL Global Development Group</publishername>
218-
</publisher>
219-
</biblioentry>
220-
221151
<biblioentry id="SIM98">
222152
<title>Enhancement of the ANSI SQL Implementation of PostgreSQL</title>
223153
<titleabbrev>Simkovics, 1998</titleabbrev>

‎doc/src/sgml/datatype.sgml

Lines changed: 9 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.82 2002/01/04 17:02:02 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.83 2002/01/07 02:29:11 petere Exp $
33
-->
44

55
<chapter id="datatype">
@@ -270,7 +270,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.82 2002/01/04 17:02:02 th
270270
paths, or have several possibilities for formats, such as the date
271271
and time types.
272272
Most of the input and output functions corresponding to the
273-
base types (e.g., integers and floating point numbers) do some
273+
base types (e.g., integers and floating-point numbers) do some
274274
error-checking.
275275
Some of the input and output functions are not invertible. That is,
276276
the result of an output function may lose precision when compared to
@@ -354,7 +354,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.82 2002/01/04 17:02:02 th
354354
<para>
355355
Numeric types consist of two-, four-, and eight-byte integers,
356356
four- and eight-byte
357-
floating point numbers and fixed-precision decimals.
357+
floating-point numbers and fixed-precision decimals.
358358
</para>
359359

360360
<para>
@@ -511,7 +511,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/datatype.sgml,v 1.82 2002/01/04 17:02:02 th
511511
numbers and carry out all calculations exactly. It is especially
512512
recommended for storing monetary amounts and other quantities
513513
where exactness is required. However, the <type>numeric</type>
514-
type is very slow compared to the floating point types described
514+
type is very slow compared to the floating-point types described
515515
in the next section.
516516
</para>
517517

@@ -568,11 +568,11 @@ NUMERIC
568568

569569

570570
<sect2 id="datatype-float">
571-
<title>Floating Point Types</title>
571+
<title>Floating-Point Types</title>
572572

573573
<para>
574574
The data types <type>real</type> and <type>double
575-
precision</type> are inexact, variable precision numeric types.
575+
precision</type> are inexact, variable-precision numeric types.
576576
In practice, these types are usually implementations of <acronym>IEEE</acronym> 754
577577
binary floating point (single and double precision,
578578
respectively), to the extent that the underlying processor,
@@ -606,7 +606,7 @@ NUMERIC
606606

607607
<listitem>
608608
<para>
609-
Comparing two floating point values for equality may or may
609+
Comparing two floating-point values for equality may or may
610610
not work as expected.
611611
</para>
612612
</listitem>
@@ -682,14 +682,6 @@ CREATE TABLE <replaceable class="parameter">tablename</replaceable> (
682682
will never be duplicates, either.
683683
</para>
684684

685-
<important>
686-
<para>
687-
The implicit sequence created for the <type>serial</type> type will
688-
<emphasis>not</emphasis> be automatically removed when the
689-
table is dropped.
690-
</para>
691-
</important>
692-
693685
<para>
694686
The type names <type>serial</type> and <type>serial4</type> are
695687
equivalent: both create <type>integer</type> columns. The type
@@ -741,7 +733,7 @@ CREATE TABLE <replaceable class="parameter">tablename</replaceable> (<replaceabl
741733

742734
<para>
743735
Input is accepted in a variety of formats, including integer and
744-
floating point literals, as well as <quote>typical</quote>
736+
floating-point literals, as well as <quote>typical</quote>
745737
currency formatting, such as <literal>'$1,000.00'</literal>.
746738
Output is in the latter form.
747739
</para>
@@ -1165,8 +1157,6 @@ SELECT b, char_length(b) FROM test2;
11651157
escape character.
11661158
</para>
11671159

1168-
<sect2 id="datatype-binary-compat">
1169-
<title>Compatibility</title>
11701160
<para>
11711161
<type>Bytea</type> provides most of the functionality of the binary
11721162
string type per SQL99 section 4.3. A comparison of SQL99 Binary
@@ -1248,7 +1238,6 @@ SELECT b, char_length(b) FROM test2;
12481238
</tbody>
12491239
</tgroup>
12501240
</table>
1251-
</sect2>
12521241
</sect1>
12531242

12541243

@@ -1335,7 +1324,7 @@ SELECT b, char_length(b) FROM test2;
13351324
specifies the number of fractional digits retained in the seconds
13361325
field. By default, there is no explicit bound on precision. The
13371326
effective limit of precision is determined by the underlying double
1338-
precision floating point number used to store values (in seconds
1327+
precision floating-point number used to store values (in seconds
13391328
for <type>interval</type> and
13401329
in seconds since 2000-01-01 for <type>timestamp</type>). The
13411330
useful range of <replaceable>p</replaceable> is from 0 to about

‎doc/src/sgml/dfunc.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.17 2001/11/21 05:53:41 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.18 2002/01/07 02:29:11 petere Exp $
33
-->
44

55
<sect2 id="dfunc">
@@ -40,7 +40,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.17 2001/11/21 05:53:41 thoma
4040

4141
<para>
4242
In the following examples we assume that your source code is in a
43-
file <filename>foo.c</filename> and we will create an shared library
43+
file <filename>foo.c</filename> and we will create a shared library
4444
<filename>foo.so</filename>. The intermediate object file will be
4545
called <filename>foo.o</filename> unless otherwise noted. A shared
4646
library can contain more than one object file, but we only use one
@@ -121,8 +121,8 @@ ld -b -o foo.sl foo.o
121121
</varlistentry>
122122

123123
<varlistentry>
124-
<term><productname>Irix</productname></term>
125-
<indexterm><primary>Irix</></>
124+
<term><productname>IRIX</productname></term>
125+
<indexterm><primary>IRIX</></>
126126
<listitem>
127127
<para>
128128
<acronym>PIC</acronym> is the default, no special compiler

‎doc/src/sgml/ecpg.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.32 2002/01/06 17:54:14 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.33 2002/01/07 02:29:11 petere Exp $
33
-->
44

55
<chapter id="ecpg">
@@ -300,7 +300,7 @@ struct sqlca
300300
</varlistentry>
301301

302302
<varlistentry>
303-
<term><computeroutput>-206 (ECPG_FLOAT_FORMAT): Not correctly formatted floating point type: %s line %d.</computeroutput></term>
303+
<term><computeroutput>-206 (ECPG_FLOAT_FORMAT): Not correctly formatted floating-point type: %s line %d.</computeroutput></term>
304304
<listitem>
305305
<para>
306306
This means the host variable is of type <type>float</type> and

‎doc/src/sgml/extend.sgml

Lines changed: 19 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.15 2002/01/07 02:29:11 petere Exp $
33
-->
44

55
<chapter id="extend">
@@ -18,7 +18,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thom
1818
</listitem>
1919
<listitem>
2020
<para>
21-
types
21+
data types
2222
</para>
2323
</listitem>
2424
<listitem>
@@ -56,17 +56,16 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thom
5656
extended by users. By comparison, conventional
5757
database systems can only be extended by changing hardcoded
5858
procedures within the <acronym>DBMS</acronym> or by loading modules
59-
specially-written by the <acronym>DBMS</acronym> vendor.
59+
specially written by the <acronym>DBMS</acronym> vendor.
6060
</para>
6161

6262
<para>
6363
<productname>PostgreSQL</productname> is also unlike most other data managers in
6464
that the server can incorporate user-written code into
6565
itself through dynamic loading. That is, the user can
66-
specify an object code file (e.g., a compiled .o file
67-
or shared library) that implements a new type or function
66+
specify an object code file (e.g., a shared library) that implements a new type or function
6867
and <productname>PostgreSQL</productname> will load it as required. Code written
69-
in <acronym>SQL</acronym> are even more trivial to add to the server.
68+
in <acronym>SQL</acronym> is even more trivial to add to the server.
7069
This ability to modify its operation <quote>on the fly</quote> makes
7170
<productname>PostgreSQL</productname> uniquely suited for rapid prototyping of new
7271
applications and storage structures.
@@ -80,14 +79,14 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thom
8079
The <productname>PostgreSQL</productname> type system
8180
can be broken down in several ways.
8281
Types are divided into base types and composite types.
83-
Base types are those, like <firstterm>int4</firstterm>, that are implemented
84-
in a language such as <productname>C</productname>. They generally correspond to
82+
Base types are those, like <type>int4</type>, that are implemented
83+
in a language such as C. They generally correspond to
8584
what are often known as <firstterm>abstract data types</firstterm>; <productname>PostgreSQL</productname>
8685
can only operate on such types through methods provided
8786
by the user and only understands the behavior of such
8887
types to the extent that the user describes them.
8988
Composite types are created whenever the user creates a
90-
table. EMP is an example of a composite type.
89+
table.
9190
</para>
9291

9392
<para>
@@ -100,10 +99,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thom
10099
<productname>PostgreSQL</productname> base types are further
101100
divided into built-in
102101
types and user-defined types. Built-in types (like
103-
<firstterm>int4</firstterm>) are those that are compiled
102+
<type>int4</type>) are those that are compiled
104103
into the system.
105104
User-defined types are those created by the user in the
106-
manner to be described below.
105+
manner to be described later.
107106
</para>
108107
</sect1>
109108

@@ -118,7 +117,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thom
118117
information given here, so mark this page for later
119118
reference.
120119
All system catalogs have names that begin with
121-
<firstterm>pg_</firstterm>.
120+
<literal>pg_</literal>.
122121
The following tables contain information that may be
123122
useful to the end user. (There are many other system
124123
catalogs, but there should rarely be a reason to query
@@ -149,23 +148,23 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thom
149148
</row>
150149
<row>
151150
<entry>pg_index</entry>
152-
<entry> secondary indexes</entry>
151+
<entry> indexes</entry>
153152
</row>
154153
<row>
155154
<entry>pg_proc</entry>
156-
<entry> procedures (both C and SQL)</entry>
155+
<entry> procedures/functions </entry>
157156
</row>
158157
<row>
159158
<entry>pg_type</entry>
160-
<entry> types (both base and complex)</entry>
159+
<entry> data types (both base and complex)</entry>
161160
</row>
162161
<row>
163162
<entry>pg_operator</entry>
164163
<entry> operators</entry>
165164
</row>
166165
<row>
167166
<entry>pg_aggregate</entry>
168-
<entry> aggregates and aggregate functions</entry>
167+
<entry> aggregate functions</entry>
169168
</row>
170169
<row>
171170
<entry>pg_am</entry>
@@ -198,7 +197,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thom
198197
</mediaobject>
199198
</figure>
200199

201-
The Reference Manual gives a more detailed explanation
200+
The <citetitle>Developer's Guide</citetitle> gives a more detailed explanation
202201
of these catalogs and their columns. However,
203202
<xref linkend="EXTEND-CATALOGS">
204203
shows the major entities and their relationships
@@ -257,10 +256,9 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.14 2001/11/21 05:53:41 thom
257256
have obvious meanings, but there are many
258257
(particularly those that have to do with access
259258
methods) that do not. The relationships between
260-
pg_am, pg_amop, pg_amproc, pg_operator and
261-
pg_opclass are particularly hard to understand
262-
and will be described in depth (in the section
263-
on interfacing types and operators to indexes)
259+
<classname>pg_am</>, <classname>pg_amop</>, <classname>pg_amproc</>, <classname>pg_operator</>, and
260+
<classname>pg_opclass</> are particularly hard to understand
261+
and will be described in depth (in <xref linkend="xindex">)
264262
after we have discussed basic extensions.
265263
</para>
266264
</listitem>

‎doc/src/sgml/func.sgml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.89 2001/12/27 21:36:57 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.90 2002/01/07 02:29:12 petere Exp $
33
PostgreSQL documentation
44
-->
55

@@ -4506,7 +4506,7 @@ SELECT NULLIF(value, '(none)') ...
45064506
<type>bigint</type>, <type>real</type>, <type>double
45074507
precision</type>, <type>numeric</type>, <type>interval</type>.
45084508
The result is of type <type>numeric</type> for any integer type
4509-
input, <type>double precision</type> for floating point input,
4509+
input, <type>double precision</type> for floating-point input,
45104510
otherwise the same as the input data type.
45114511
</entry>
45124512
</row>
@@ -4555,7 +4555,7 @@ SELECT NULLIF(value, '(none)') ...
45554555
data types: <type>smallint</type>, <type>integer</type>,
45564556
<type>bigint</type>, <type>real</type>, <type>double
45574557
precision</type>, <type>numeric</type>. The result is of type
4558-
<type>double precision</type> for floating point input,
4558+
<type>double precision</type> for floating-point input,
45594559
otherwise <type>numeric</type>.
45604560
</entry>
45614561
</row>
@@ -4571,7 +4571,7 @@ SELECT NULLIF(value, '(none)') ...
45714571
The result is of type <type>bigint</type> for <type>smallint</type>
45724572
or <type>integer</type> input, <type>numeric</type> for
45734573
<type>bigint</type>
4574-
input, <type>double precision</type> for floating point input,
4574+
input, <type>double precision</type> for floating-point input,
45754575
otherwise the same as the input data type.
45764576
</entry>
45774577
</row>

0 commit comments

Comments
 (0)