Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit7bfd95a

Browse files
committed
Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest
supported release.
1 parent6a2e19d commit7bfd95a

File tree

6 files changed

+18
-68
lines changed

6 files changed

+18
-68
lines changed

‎doc/src/sgml/datatype.sgml

Lines changed: 5 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.242 2010/02/17 04:19:37 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.243 2010/02/24 03:33:48 momjian Exp $ -->
22

33
<chapter id="datatype">
44
<title id="datatype-title">Data Types</title>
@@ -715,11 +715,7 @@ NUMERIC
715715

716716
<note>
717717
<para>
718-
Prior to <productname>PostgreSQL</productname> 7.4, the precision in
719-
<type>float(<replaceable>p</replaceable>)</type> was taken to mean
720-
so many <emphasis>decimal</> digits. This has been corrected to match the SQL
721-
standard, which specifies that the precision is measured in binary
722-
digits. The assumption that <type>real</type> and
718+
The assumption that <type>real</type> and
723719
<type>double precision</type> have exactly 24 and 53 bits in the
724720
mantissa respectively is correct for IEEE-standard floating point
725721
implementations. On non-IEEE platforms it might be off a little, but
@@ -795,11 +791,9 @@ ALTER SEQUENCE <replaceable class="parameter">tablename</replaceable>_<replaceab
795791

796792
<note>
797793
<para>
798-
Prior to <productname>PostgreSQL</productname> 7.3, <type>serial</type>
799-
implied <literal>UNIQUE</literal>. This is no longer automatic. If
800-
you wish a serial column to have a unique constraint or be a
801-
primary key, it must now be specified, just like
802-
any other data type.
794+
If you wish a serial column to have a unique constraint or be
795+
a primary key, it must be specified, just like any other data
796+
type.
803797
</para>
804798
</note>
805799

@@ -1521,14 +1515,6 @@ SELECT E'\\xDEADBEEF';
15211515
</tgroup>
15221516
</table>
15231517

1524-
<note>
1525-
<para>
1526-
Prior to <productname>PostgreSQL</productname> 7.3, writing just
1527-
<type>timestamp</type> was equivalent to <type>timestamp with
1528-
time zone</type>. This was changed for SQL compliance.
1529-
</para>
1530-
</note>
1531-
15321518
<para>
15331519
<type>time</type>, <type>timestamp</type>, and
15341520
<type>interval</type> accept an optional precision value

‎doc/src/sgml/ddl.sgml

Lines changed: 7 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.88 2009/10/23 05:24:52 petere Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.89 2010/02/24 03:33:48 momjian Exp $ -->
22

33
<chapter id="ddl">
44
<title>Data Definition</title>
@@ -1795,18 +1795,12 @@ REVOKE CREATE ON SCHEMA public FROM PUBLIC;
17951795
</para>
17961796

17971797
<para>
1798-
In <productname>PostgreSQL</productname> versions before 7.3,
1799-
table names beginning with <literal>pg_</> were reserved. This is
1800-
no longer true: you can create such a table name if you wish, in
1801-
any non-system schema. However, it's best to continue to avoid
1802-
such names, to ensure that you won't suffer a conflict if some
1803-
future version defines a system table named the same as your
1804-
table. (With the default search path, an unqualified reference to
1805-
your table name would then be resolved as the system table instead.)
1806-
System tables will continue to follow the convention of having
1807-
names beginning with <literal>pg_</>, so that they will not
1808-
conflict with unqualified user-table names so long as users avoid
1809-
the <literal>pg_</> prefix.
1798+
It is best to avoid table names beginning with <literal>pg_</>
1799+
because they might someday conflict with system catalogs of the
1800+
same name. (<productname>PostgreSQL</productname> system catalog
1801+
table names always start with <literal>pg_</>). Of course, table
1802+
names can always be schema-qualified to avoid conflicting with
1803+
system catalog table names.
18101804
</para>
18111805
</sect2>
18121806

@@ -3040,15 +3034,6 @@ DROP TABLE products CASCADE;
30403034
</para>
30413035
</note>
30423036

3043-
<note>
3044-
<para>
3045-
Foreign key constraint dependencies and serial column dependencies
3046-
from <productname>PostgreSQL</productname> versions prior to 7.3
3047-
are <emphasis>not</emphasis> maintained or created during the
3048-
upgrade process. All other dependency types will be properly
3049-
created during an upgrade from a pre-7.3 database.
3050-
</para>
3051-
</note>
30523037
</sect1>
30533038

30543039
</chapter>

‎doc/src/sgml/libpq.sgml

Lines changed: 1 addition & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.300 2010/02/17 04:19:37 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/libpq.sgml,v 1.301 2010/02/24 03:33:49 momjian Exp $ -->
22

33
<chapter id="libpq">
44
<title><application>libpq</application> - C Library</title>
@@ -1203,14 +1203,6 @@ PQconninfoOption *PQconninfoParse(const char *conninfo, char **errmsg);
12031203
has been sent to the server and not yet completed.
12041204
</para>
12051205

1206-
<caution>
1207-
<para>
1208-
<function>PQtransactionStatus</> will give incorrect results when using
1209-
a <productname>PostgreSQL</> 7.3 server that has the parameter <literal>autocommit</>
1210-
set to off. The server-side autocommit feature has been
1211-
deprecated and does not exist in later server versions.
1212-
</para>
1213-
</caution>
12141206
</listitem>
12151207
</varlistentry>
12161208

‎doc/src/sgml/protocol.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/protocol.sgml,v 1.83 2010/02/22 18:12:04 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/protocol.sgml,v 1.84 2010/02/24 03:33:49 momjian Exp $ -->
22

33
<chapter id="protocol">
44
<title>Frontend/Backend Protocol</title>
@@ -165,8 +165,8 @@
165165

166166
<para>
167167
Data of a particular data type might be transmitted in any of several
168-
different <firstterm>formats</>. As of <productname>PostgreSQL</> 7.4
169-
the only supported formats are <quote>text</> and <quote>binary</>,
168+
different <firstterm>formats</>.
169+
The only supported formats are <quote>text</> and <quote>binary</>,
170170
but the protocol makes provision for future extensions. The desired
171171
format for any value is specified by a <firstterm>format code</>.
172172
Clients can specify a format code for each transmitted parameter value

‎doc/src/sgml/rules.sgml

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.53 2009/11/05 23:24:22 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.54 2010/02/24 03:33:49 momjian Exp $ -->
22

33
<chapter id="rules">
44
<title>The Rule System</title>
@@ -1828,9 +1828,6 @@ GRANT SELECT ON phone_number TO secretary;
18281828
</listitem>
18291829
</itemizedlist>
18301830

1831-
(This system was established in <productname>PostgreSQL</> 7.3.
1832-
In versions before that, the command status might show different
1833-
results when rules exist.)
18341831
</para>
18351832

18361833
<para>

‎doc/src/sgml/xindex.sgml

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/xindex.sgml,v 1.64 2008/12/07 23:46:39 alvherre Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/xindex.sgml,v 1.65 2010/02/24 03:33:49 momjian Exp $ -->
22

33
<sect1 id="xindex">
44
<title>Interfacing Extensions To Indexes</title>
@@ -895,16 +895,6 @@ ALTER OPERATOR FAMILY integer_ops USING btree ADD
895895
try to use these SQL features with the data type.
896896
</para>
897897

898-
<note>
899-
<para>
900-
In <productname>PostgreSQL</productname> versions before 7.4,
901-
sorting and grouping operations would implicitly use operators named
902-
<literal>=</>, <literal>&lt;</>, and <literal>&gt;</>. The new
903-
behavior of relying on default operator classes avoids having to make
904-
any assumption about the behavior of operators with particular names.
905-
</para>
906-
</note>
907-
908898
<para>
909899
Another important point is that an operator that
910900
appears in a hash operator family is a candidate for hash joins,

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp