Skip to content

Commit 6f14a6f

Browse files
bmomjianbmomjian
committed
docs: remove unnecessary references to old PG versions
1 parent 4bad548 commit 6f14a6f

16 files changed

+27
-140
lines changed

‎doc/src/sgml/datatype.sgml

Lines changed: 2 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -750,11 +750,7 @@ NUMERIC
750750

751751
<note>
752752
<para>
753-
Prior to <productname>PostgreSQL</productname> 7.4, the precision in
754-
<type>float(<replaceable>p</replaceable>)</type> was taken to mean
755-
so many <emphasis>decimal</> digits. This has been corrected to match the SQL
756-
standard, which specifies that the precision is measured in binary
757-
digits. The assumption that <type>real</type> and
753+
The assumption that <type>real</type> and
758754
<type>double precision</type> have exactly 24 and 53 bits in the
759755
mantissa respectively is correct for IEEE-standard floating point
760756
implementations. On non-IEEE platforms it might be off a little, but
@@ -850,16 +846,6 @@ ALTER SEQUENCE <replaceable class="parameter">tablename</replaceable>_<replaceab
850846
</para>
851847
</note>
852848

853-
<note>
854-
<para>
855-
Prior to <productname>PostgreSQL</productname> 7.3, <type>serial</type>
856-
implied <literal>UNIQUE</literal>. This is no longer automatic. If
857-
you wish a serial column to have a unique constraint or be a
858-
primary key, it must now be specified, just like
859-
any other data type.
860-
</para>
861-
</note>
862-
863849
<para>
864850
To insert the next value of the sequence into the <type>serial</type>
865851
column, specify that the <type>serial</type>
@@ -1611,8 +1597,7 @@ SELECT E'\\xDEADBEEF';
16111597
The SQL standard requires that writing just <type>timestamp</type>
16121598
be equivalent to <type>timestamp without time
16131599
zone</type>, and <productname>PostgreSQL</productname> honors that
1614-
behavior. (Releases prior to 7.3 treated it as <type>timestamp
1615-
with time zone</type>.) <type>timestamptz</type> is accepted as an
1600+
behavior. <type>timestamptz</type> is accepted as an
16161601
abbreviation for <type>timestamp with time zone</type>; this is a
16171602
<productname>PostgreSQL</productname> extension.
16181603
</para>

‎doc/src/sgml/ddl.sgml

Lines changed: 4 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1106,9 +1106,8 @@ CREATE TABLE circles (
11061106
within a single transaction. In practice this limit is not a
11071107
problem &mdash; note that the limit is on the number of
11081108
<acronym>SQL</acronym> commands, not the number of rows processed.
1109-
Also, as of <productname>PostgreSQL</productname> 8.3, only commands
1110-
that actually modify the database contents will consume a command
1111-
identifier.
1109+
Also, only commands that actually modify the database contents will
1110+
consume a command identifier.
11121111
</para>
11131112
</sect1>
11141113

@@ -1873,11 +1872,8 @@ REVOKE CREATE ON SCHEMA public FROM PUBLIC;
18731872
</para>
18741873

18751874
<para>
1876-
In <productname>PostgreSQL</productname> versions before 7.3,
1877-
table names beginning with <literal>pg_</> were reserved. This is
1878-
no longer true: you can create such a table name if you wish, in
1879-
any non-system schema. However, it's best to continue to avoid
1880-
such names, to ensure that you won't suffer a conflict if some
1875+
Since system table names begin with <literal>pg_</>, it is best to
1876+
avoid such names to ensure that you won't suffer a conflict if some
18811877
future version defines a system table named the same as your
18821878
table. (With the default search path, an unqualified reference to
18831879
your table name would then be resolved as the system table instead.)

‎doc/src/sgml/extend.sgml

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1161,16 +1161,6 @@ include $(PGXS)
11611161
or on the <literal>make</literal> command line.
11621162
</para>
11631163

1164-
<caution>
1165-
<para>
1166-
Changing <varname>PG_CONFIG</varname> only works when building
1167-
against <productname>PostgreSQL</productname> 8.3 or later.
1168-
With older releases it does not work to set it to anything except
1169-
<literal>pg_config</>; you must alter your <varname>PATH</>
1170-
to select the installation to build against.
1171-
</para>
1172-
</caution>
1173-
11741164
<para>
11751165
You can also run <literal>make</literal> in a directory outside the source
11761166
tree of your extension, if you want to keep the build directory separate.

‎doc/src/sgml/func.sgml

Lines changed: 4 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -3549,11 +3549,9 @@ cast(-44 as bit(12)) <lineannotation>111111010100</lineannotation>
35493549

35503550
<note>
35513551
<para>
3552-
Prior to <productname>PostgreSQL</productname> 8.0, casting an
3553-
integer to <type>bit(n)</> would copy the leftmost <literal>n</>
3554-
bits of the integer, whereas now it copies the rightmost <literal>n</>
3555-
bits. Also, casting an integer to a bit string width wider than
3556-
the integer itself will sign-extend on the left.
3552+
Casting an integer to <type>bit(n)</> copies the rightmost
3553+
<literal>n</> bits. Casting an integer to a bit string width wider
3554+
than the integer itself will sign-extend on the left.
35573555
</para>
35583556
</note>
35593557

@@ -6959,12 +6957,6 @@ SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
69596957
If you disagree with this, please write your complaint to:
69606958
Pope, Cathedral Saint-Peter of Roma, Vatican.
69616959
</para>
6962-
6963-
<para>
6964-
<productname>PostgreSQL</productname> releases before 8.0 did not
6965-
follow the conventional numbering of centuries, but just returned
6966-
the year field divided by 100.
6967-
</para>
69686960
</listitem>
69696961
</varlistentry>
69706962

@@ -7160,12 +7152,6 @@ SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
71607152
Years in the 1900s are in the second millennium.
71617153
The third millennium started January 1, 2001.
71627154
</para>
7163-
7164-
<para>
7165-
<productname>PostgreSQL</productname> releases before 8.0 did not
7166-
follow the conventional numbering of millennia, but just returned
7167-
the year field divided by 1000.
7168-
</para>
71697155
</listitem>
71707156
</varlistentry>
71717157

@@ -10747,8 +10733,7 @@ nextval('foo'::text) <lineannotation><literal>foo</literal> is looked up at
1074710733
next <function>nextval</function> will return exactly the specified
1074810734
value, and sequence advancement commences with the following
1074910735
<function>nextval</function>. Furthermore, the value reported by
10750-
<function>currval</> is not changed in this case (this is a change
10751-
from pre-8.3 behavior). For example,
10736+
<function>currval</> is not changed in this case. For example,
1075210737

1075310738
<screen>
1075410739
SELECT setval('foo', 42); <lineannotation>Next <function>nextval</> will return 43</lineannotation>

‎doc/src/sgml/libpq.sgml

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1611,15 +1611,6 @@ PGTransactionStatusType PQtransactionStatus(const PGconn *conn);
16111611
<literal>PQTRANS_ACTIVE</literal> is reported only when a query
16121612
has been sent to the server and not yet completed.
16131613
</para>
1614-
1615-
<caution>
1616-
<para>
1617-
<function>PQtransactionStatus</> will give incorrect results when using
1618-
a <productname>PostgreSQL</> 7.3 server that has the parameter <literal>autocommit</>
1619-
set to off. The server-side autocommit feature has been
1620-
deprecated and does not exist in later server versions.
1621-
</para>
1622-
</caution>
16231614
</listitem>
16241615
</varlistentry>
16251616

‎doc/src/sgml/pgrowlocks.sgml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,8 +113,7 @@ SELECT * FROM accounts AS a, pgrowlocks('accounts') AS p
113113
WHERE p.locked_row = a.ctid;
114114
</programlisting>
115115

116-
Be aware however that (as of <productname>PostgreSQL</> 8.3) such a
117-
query will be very inefficient.
116+
Be aware however that such a query will be very inefficient.
118117
</para>
119118
</sect2>
120119

‎doc/src/sgml/plpgsql.sgml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -388,9 +388,8 @@ BEGIN
388388
END;
389389
$$ LANGUAGE plpgsql;
390390
</programlisting>
391-
The other way, which was the only way available before
392-
<productname>PostgreSQL</productname> 8.0, is to explicitly
393-
declare an alias, using the declaration syntax
391+
The other way is to explicitly declare an alias, using the
392+
declaration syntax
394393

395394
<synopsis>
396395
<replaceable>name</replaceable> ALIAS FOR $<replaceable>n</replaceable>;

‎doc/src/sgml/plpython.sgml

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,11 @@
2727
</tip>
2828

2929
<para>
30-
As of <productname>PostgreSQL</productname> 7.4, PL/Python is only
31-
available as an <quote>untrusted</> language, meaning it does not
32-
offer any way of restricting what users can do in it. It has
33-
therefore been renamed to <literal>plpythonu</>. The trusted
34-
variant <literal>plpython</> might become available again in future,
35-
if a new secure execution mechanism is developed in Python. The
30+
PL/Python is only available as an <quote>untrusted</> language, meaning
31+
it does not offer any way of restricting what users can do in it and
32+
is therefore named <literal>plpythonu</>. A trusted
33+
variant <literal>plpython</> might become available in the future
34+
if a secure execution mechanism is developed in Python. The
3635
writer of a function in untrusted PL/Python must take care that the
3736
function cannot be used to do anything unwanted, since it will be
3837
able to do anything that could be done by a user logged in as the

‎doc/src/sgml/ref/create_cast.sgml

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -331,17 +331,6 @@ SELECT CAST ( 2 AS numeric ) + 4.0;
331331
mostly because of requirements of the SQL standard.)
332332
</para>
333333

334-
<para>
335-
Prior to <productname>PostgreSQL</> 7.3, every function that had
336-
the same name as a data type, returned that data type, and took one
337-
argument of a different type was automatically a cast function.
338-
This convention has been abandoned in face of the introduction of
339-
schemas and to be able to represent binary-coercible casts in the
340-
system catalogs. The built-in cast functions still follow this naming
341-
scheme, but they have to be shown as casts in the system catalog
342-
<structname>pg_cast</> as well.
343-
</para>
344-
345334
<para>
346335
While not required, it is recommended that you continue to follow this old
347336
convention of naming cast implementation functions after the target data

‎doc/src/sgml/ref/create_table_as.sgml

Lines changed: 2 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -236,19 +236,11 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE <replaceable
236236
</para>
237237

238238
<para>
239-
Prior to <productname>PostgreSQL</productname> 8.0, <command>CREATE
240-
TABLE AS</command> always included OIDs in the table it
241-
created. As of <productname>PostgreSQL</productname> 8.0,
242-
the <command>CREATE TABLE AS</command> command allows the user to
239+
The <command>CREATE TABLE AS</command> command allows the user to
243240
explicitly specify whether OIDs should be included. If the
244241
presence of OIDs is not explicitly specified,
245242
the <xref linkend="guc-default-with-oids"> configuration variable is
246-
used. As of <productname>PostgreSQL</productname> 8.1,
247-
this variable is false by default, so the default behavior is not
248-
identical to pre-8.0 releases. Applications that
249-
require OIDs in the table created by <command>CREATE TABLE
250-
AS</command> should explicitly specify <literal>WITH (OIDS)</literal>
251-
to ensure desired behavior.
243+
used.
252244
</para>
253245
</refsect1>
254246

0 commit comments

Comments
 (0)