Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit bdf6c4f

Browse files
author
Thomas G. Lockhart
committed
Update porting list.
Fix markup to get clean compile.
1 parent d570460 commit bdf6c4f

File tree

6 files changed

+18
-113
lines changed

6 files changed

+18
-113
lines changed

‎doc/src/sgml/advanced.sgml

Lines changed: 1 addition & 100 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.10 2000/04/07 13:30:58 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.11 2000/04/11 05:39:06 thomas Exp $
33
-->
44

55
<chapter id="advanced">
@@ -234,105 +234,6 @@ SELECT SAL_EMP.schedule[1:2][1:1]
234234
</sect2>
235235
</sect1>
236236

237-
<!--
238-
239-
We haven't had Time Travel for two or three years, so let's stop
240-
mentioning it. - thomas 2000-04-02
241-
242-
<sect1>
243-
<title>Time Travel</title>
244-
245-
<para>
246-
As of <productname>Postgres</productname> v6.2, <emphasis>time
247-
travel is no longer supported</emphasis>. There are
248-
several reasons for this: performance impact, storage size, and a
249-
pg_time file which grows
250-
toward infinite size in a short period of time.
251-
</para>
252-
253-
<para>
254-
New features such as triggers allow one to mimic the behavior of
255-
time travel when desired, without
256-
incurring the overhead when it is not needed (for most users, this
257-
is most of the time).
258-
See examples in the <filename>contrib</filename> directory for
259-
more information.
260-
</para>
261-
262-
<note>
263-
<title>Time travel is deprecated</title>
264-
<para>
265-
The remaining text in this section is retained only until it can
266-
be rewritten in the context
267-
of new techniques to accomplish the same purpose.
268-
Volunteers? - thomas 1998-01-12
269-
</para>
270-
</note>
271-
272-
<para>
273-
<productname>Postgres</productname> supports the notion of time
274-
travel. This feature
275-
allows a user to run historical queries. For
276-
example, to find the current population of Mariposa
277-
city, one would query:
278-
279-
<programlisting>
280-
SELECT * FROM cities WHERE name = 'Mariposa';
281-
282-
+---------+------------+----------+
283-
|name | population | altitude |
284-
+---------+------------+----------+
285-
|Mariposa | 1320 | 1953 |
286-
+---------+------------+----------+
287-
</programlisting>
288-
289-
<productname>Postgres</productname> will automatically find the
290-
version of Mariposa's
291-
record valid at the current time.
292-
One can also give a time range. For example to see the
293-
past and present populations of Mariposa, one would
294-
query:
295-
296-
<programlisting>
297-
SELECT name, population
298-
FROM cities['epoch', 'now']
299-
WHERE name = 'Mariposa';
300-
</programlisting>
301-
302-
where "epoch" indicates the beginning of the system
303-
clock.
304-
305-
<note>
306-
<para>
307-
On Unix systems, this is always midnight, January 1, 1970 GMT.
308-
</para>
309-
</note>
310-
</para>
311-
312-
<para>
313-
If you have executed all of the examples so
314-
far, then the above query returns:
315-
316-
<programlisting>
317-
+---------+------------+
318-
|name | population |
319-
+---------+------------+
320-
|Mariposa | 1200 |
321-
+---------+------------+
322-
|Mariposa | 1320 |
323-
+---------+------------+
324-
</programlisting>
325-
</para>
326-
327-
<para>
328-
The default beginning of a time range is the earliest
329-
time representable by the system and the default end is
330-
the current time; thus, the above time range can be
331-
abbreviated as ``[,].''
332-
</para>
333-
</sect1>
334-
-->
335-
336237
<sect1>
337238
<title>More Advanced Features</title>
338239

‎doc/src/sgml/ports.sgml

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -150,11 +150,15 @@
150150
(<ulink url="mailto:t-ishii@sra.co.jp">Tatsuo Ishii</ulink>)</entry>
151151
</row>
152152
<row>
153-
<entry>NetBSD</entry>
153+
<entry>NetBSD 1.4</entry>
154154
<entry>arm32</entry>
155-
<entry>v6.5</entry>
156-
<entry>1999-04-14</entry>
155+
<entry>v7.0</entry>
156+
<entry>2000-04-08</entry>
157+
<entry>(<ulink url="mailto:prlw1@newn.cam.ac.uk">Patrick
158+
Welche</ulink>)</entry>
159+
<!--
157160
<entry>(<ulink url="mailto:a.mcmurry1@physics.oxford.ac.uk">Andrew McMurry</ulink>)</entry>
161+
-->
158162
</row>
159163
<row>
160164
<entry>NetBSD 1.4U</entry>

‎doc/src/sgml/query.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.10 2000/04/07 13:30:58 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.11 2000/04/11 05:39:06 thomas Exp $
33
-->
44

55
<chapter id="query">
@@ -21,8 +21,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/query.sgml,v 1.10 2000/04/07 13:30:58 thoma
2121
flavor of <acronym>SQL</acronym> and is in no way a complete tutorial on
2222
<acronym>SQL</acronym>. Numerous books have been written on
2323
<acronym>SQL92</acronym>, including
24-
<xref linkend="MELT93" endterm="MELT93-title"> and
25-
<xref linkend="DATE97" endterm="DATE97-title">.
24+
<xref linkend="MELT93" endterm="MELT93"> and
25+
<xref linkend="DATE97" endterm="DATE97">.
2626
You should be aware that some language features
2727
are extensions to the <acronym>ANSI</acronym> standard.
2828
</para>

‎doc/src/sgml/ref/comment.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/ref/comment.sgml,v 1.3 1999/10/26 16:36:28 momjian Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/comment.sgml,v 1.4 2000/04/11 05:39:15 thomas Exp $
33
Postgres documentation
44
-->
55

@@ -101,7 +101,7 @@ COMMENT
101101
<para>
102102
<command>COMMENT</command> adds a comment to an object that can be
103103
easily retrieved with <application>psql's</application>
104-
<emphasize>\dd</emphasize> command.
104+
<emphasis>\dd</emphasis> command.
105105
To remove a comment, use <literal>NULL</literal>.
106106
Comments are automatically dropped when the object is dropped.
107107
</para>

‎doc/src/sgml/ref/create_index.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.10 2000/03/16 14:39:30 thomas Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.11 2000/04/11 05:39:15 thomas Exp $
33
Postgres documentation
44
-->
55

@@ -46,8 +46,8 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable>
4646
Causes the system to check for
4747
duplicate values in the table when the index is created (if data
4848
already exist) and each time data is added. Attempts to
49-
insert or update non-duplicate data will generate an
50-
error.
49+
insert or update data which would result in duplicate entries
50+
will generate an error.
5151
</para>
5252
</listitem>
5353
</varlistentry>

‎doc/src/sgml/ref/update.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/ref/update.sgml,v 1.8 2000/03/26 18:32:27 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.9 2000/04/11 05:39:15 thomas Exp $
33
Postgres documentation
44
-->
55

@@ -182,7 +182,7 @@ SELECT * FROM films WHERE kind = 'Dramatic' OR kind = 'Drama';
182182
the positioned UPDATE statement:
183183

184184
<synopsis>
185-
UPDATE table SET column = expression [, ...]
185+
UPDATE <replaceable>table</replaceable> SET <replaceable>column</replaceable> = <replaceable>expression</replaceable> [, ...]
186186
WHERE CURRENT OF <replaceable class="parameter">cursor</replaceable>
187187
</synopsis>
188188

0 commit comments

Comments
 (0)