aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/func.sgml4
-rw-r--r--doc/src/sgml/ref/create_table_as.sgml6
-rw-r--r--doc/src/sgml/ref/select_into.sgml6
-rw-r--r--doc/src/sgml/release.sgml12
4 files changed, 14 insertions, 14 deletions
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index f87b7657b59..2f609f00bf7 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.215 2004/08/03 20:32:31 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.216 2004/08/04 21:33:40 tgl Exp $
PostgreSQL documentation
-->
@@ -2408,7 +2408,7 @@ cast(-44 as bit(12)) <lineannotation>111111010100</lineannotation>
<note>
<para>
- Prior to <productname>PostgreSQL</productname> 7.5, casting an
+ Prior to <productname>PostgreSQL</productname> 8.0, casting an
integer to <type>bit(n)</> would copy the leftmost <literal>n</>
bits of the integer, whereas now it copies the rightmost <literal>n</>
bits. Also, casting an integer to a bit string width wider than
diff --git a/doc/src/sgml/ref/create_table_as.sgml b/doc/src/sgml/ref/create_table_as.sgml
index 633e77cbf57..3cf823e78ab 100644
--- a/doc/src/sgml/ref/create_table_as.sgml
+++ b/doc/src/sgml/ref/create_table_as.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.21 2004/03/09 16:57:47 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.22 2004/08/04 21:33:42 tgl Exp $
PostgreSQL documentation
-->
@@ -141,14 +141,14 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } ] TABLE <replaceable>table_name
</para>
<para>
- Prior to <productname>PostgreSQL</productname> 7.5, <command>CREATE
+ Prior to <productname>PostgreSQL</productname> 8.0, <command>CREATE
TABLE AS</command> always included OIDs in the table it
produced. Furthermore, these OIDs were newly generated: they were
distinct from the OIDs of any of the rows in the source tables of
the <command>SELECT</command> or <command>EXECUTE</command>
statement. Therefore, if <command>CREATE TABLE AS</command> was
frequently executed, the OID counter would be rapidly
- incremented. As of <productname>PostgresSQL</productname> 7.5,
+ incremented. As of <productname>PostgresSQL</productname> 8.0,
the <command>CREATE TABLE AS</command> command allows the user to
explicitely specify whether OIDs should be included. If the
presence of OIDs is not explicitely specified,
diff --git a/doc/src/sgml/ref/select_into.sgml b/doc/src/sgml/ref/select_into.sgml
index ef469876266..edd341e6e6a 100644
--- a/doc/src/sgml/ref/select_into.sgml
+++ b/doc/src/sgml/ref/select_into.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/select_into.sgml,v 1.28 2004/03/09 16:57:47 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/select_into.sgml,v 1.29 2004/08/04 21:33:42 tgl Exp $
PostgreSQL documentation
-->
@@ -94,13 +94,13 @@ SELECT [ ALL | DISTINCT [ ON ( <replaceable class="PARAMETER">expression</replac
</para>
<para>
- Prior to <productname>PostgreSQL</> 7.5, the table created by
+ Prior to <productname>PostgreSQL</> 8.0, the table created by
<command>SELECT INTO</command> always included OIDs. Furthermore,
these OIDs were newly generated: they were distinct from the OIDs
of any of the rows in the source tables of the <command>SELECT
INTO</command> statement. Therefore, if <command>SELECT
INTO</command> was frequently executed, the OID counter would be
- rapidly incremented. As of <productname>PostgreSQL</> 7.5, the
+ rapidly incremented. As of <productname>PostgreSQL</> 8.0, the
inclusion of OIDs in the table created by <command>SELECT
INTO</command> is controlled by the
<xref linkend="guc-default-with-oids"> configuration variable. This
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index d477869650d..4e4911599bb 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -1,12 +1,12 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.276 2004/08/03 01:14:57 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.277 2004/08/04 21:33:40 tgl Exp $
-->
<appendix id="release">
<title>Release Notes</title>
<sect1 id="release-7-5">
- <title>Release 7.5</title>
+ <title>Release 8.0</title>
<note>
<title>Release date</title>
@@ -153,7 +153,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.276 2004/08/03 01:14:57 momjian
</sect2>
<sect2>
- <title>Migration to version 7.5</title>
+ <title>Migration to version 8.0</title>
<para>
A dump/restore using <application>pg_dump</application> is
@@ -295,7 +295,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.276 2004/08/03 01:14:57 momjian
<para>
Below you will find a detailed account of the changes between
- release 7.5 and the previous major release.
+ release 8.0 and the previous major release.
</para>
<sect3>
@@ -1011,7 +1011,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.276 2004/08/03 01:14:57 momjian
<listitem>
<para>
- Warn of empty string being passes to oid/float4/float8 data types; 7.6
+ Warn of empty string being passed to oid/float4/float8 data types; 8.1
will throw an error instead (Neil)
</para>
</listitem>
@@ -3811,7 +3811,7 @@ DROP SCHEMA information_schema CASCADE;
turns out to have disabled rule-related permissions checks in many
not-so-corner cases. This would for example allow users to insert into views
they weren't supposed to have permission to insert into. We have therefore
-reverted the 7.3.3 patch. The original bug will be fixed in 7.5.
+reverted the 7.3.3 patch. The original bug will be fixed in 8.0.
</para></listitem>
<listitem><para>Repair incorrect order of operations in
GetNewTransactionId()</para>