database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-08-09 17:03:00 +03:00
Code Activity

Stamp

Browse Source
This commit is contained in:
Bruce Momjian
2007-09-11 17:19:07 +00:00
parent 85738a50ea
commit 4147492693
1 changed files with 198 additions and 137 deletions
Download Patch File Download Diff File Expand all files Collapse all files

335
doc/src/sgml/release.sgml
View File

@@ -1,10 +1,86 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.163.2.44 2007/09/11 17:19:07 momjian Exp $ -->
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.43 2007/04/20 03:28:17 tgl Exp $
Typical markup:
&<> use & escapes
[A-Z][A-Z ]+[A-Z] <command>
[A-Za-z_][A-Za-z0-9_]+() <function>
[A-Za-z_]/[A-Za-z_]+ <filename>
PostgreSQL <productname>
pg_[A-Za-z0-9_] <application>
[A-Z][A-Z] <type>, <envar>, <literal>
non-ASCII characters convert to HTML4 entity (&) escapes
official: http://www.w3.org/TR/html4/sgml/entities.html
one page: http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
other lists: http://www.zipcon.net/~swhite/docs/computers/browsers/entities.html
http://www.zipcon.net/~swhite/docs/computers/browsers/entities_page.html
http://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references
we cannot use UTF8 because SGML Docbook
does not support it
http://www.pemberley.com/janeinfo/latin1.html#latexta
wrap long lines
For new features, add links to the documentation sections. Use </link>
so that perl can remove it so HISTORY.html can be created with no
links to the main documentation. This was added only in 8.2, so don't
do it for earlier branch release files.
-->
<appendix id="release">
<title>Release Notes</title>
<sect1 id="release-7-3-20">
<title>Release 7.3.20</title>
<note>
<title>Release date</title>
<simpara>2007-09-17</simpara>
</note>
<para>
This release contains fixes from 7.3.19.
</para>
<sect2>
<title>Migration to version 7.3.20</title>
<para>
A dump/restore is not required for those running 7.3.X. However,
if you are upgrading from a version earlier than 7.3.13, see the release
notes for 7.3.13.
</para>
</sect2>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem>
<para>
Allow <command>CREATE DOMAIN ... DEFAULT NULL</> (Tom)
</para>
</listitem>
<listitem>
<para>
Require non-superusers who use <filename>/contrib/dblink</> to use only password
authentication, as a security measure (Joe)
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-7-3-19">
<title>Release 7.3.19</title>
@@ -155,11 +231,13 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.43 2007/04/20 03:28:
<para>
<function>to_number()</> and <function>to_char(numeric)</>
are now <literal>STABLE</>, not <literal>IMMUTABLE</>, for
new <application>initdb</> installs (Tom)
new <link linkend="APP-INITDB"><application>initdb</></link>
installs (Tom)
</para>
<para>
This is because <literal>lc_numeric</> can potentially
This is because <link
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
change the output of these functions.
</para>
</listitem>
@@ -178,7 +256,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.43 2007/04/20 03:28:
</sect2>
</sect1>
<sect1 id="release-7-3-16">
<title>Release 7.3.16</title>
@@ -205,7 +283,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.43 2007/04/20 03:28:
<sect2>
<title>Changes</title>
<itemizedlist>
<itemizedlist>
<listitem><para>Fix corner cases in pattern matching for
<application>psql</>'s <literal>\d</> commands</para></listitem>
<listitem><para>Fix index-corrupting bugs in /contrib/ltree
@@ -220,7 +298,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.43 2007/04/20 03:28:
</sect2>
</sect1>
<sect1 id="release-7-3-15">
<title>Release 7.3.15</title>
@@ -245,7 +323,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.163.2.43 2007/04/20 03:28:
<para>
Full security against the SQL-injection attacks described in
CVE-2006-2313 and CVE-2006-2314 may require changes in application
CVE-2006-2313 and CVE-2006-2314 might require changes in application
code. If you have applications that embed untrustworthy strings
into SQL commands, you should examine them as soon as possible to
ensure that they are using recommended escaping techniques. In
@@ -277,7 +355,7 @@ literals. By default, <literal>\'</> is rejected only when
GB18030, or UHC), which is the scenario in which SQL injection is possible.
A new configuration parameter <varname>backslash_quote</> is available to
adjust this behavior when needed. Note that full security against
CVE-2006-2314 may require client-side changes; the purpose of
CVE-2006-2314 might require client-side changes; the purpose of
<varname>backslash_quote</> is in part to make it obvious that insecure
clients are insecure.
</para></listitem>
@@ -312,7 +390,7 @@ Fuhr)</para></listitem>
</sect2>
</sect1>
<sect1 id="release-7-3-14">
<title>Release 7.3.14</title>
@@ -337,7 +415,7 @@ Fuhr)</para></listitem>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem><para>Fix potential crash in <command>SET
@@ -369,7 +447,7 @@ and <function>isinf</> during configure (Tom)</para></listitem>
</sect2>
</sect1>
<sect1 id="release-7-3-13">
<title>Release 7.3.13</title>
@@ -397,7 +475,7 @@ and <function>isinf</> during configure (Tom)</para></listitem>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem><para>Fix character string comparison for locales that consider
@@ -410,7 +488,7 @@ to ensure that <application>plperl</> won't change the locale later</para>
<para>This fixes a problem that occurred if the <application>postmaster</> was
started with environment variables specifying a different locale than what
<application>initdb</> had been told. Under these conditions, any use of
<application>plperl</> was likely to lead to corrupt indexes. You may need
<application>plperl</> was likely to lead to corrupt indexes. You might need
<command>REINDEX</> to fix existing indexes on
textual columns if this has happened to you.</para></listitem>
@@ -431,7 +509,7 @@ what's actually returned by the query (Joe)</para></listitem>
</sect2>
</sect1>
<sect1 id="release-7-3-12">
<title>Release 7.3.12</title>
@@ -456,7 +534,7 @@ what's actually returned by the query (Joe)</para></listitem>
<sect2>
<title>Changes</title>
<itemizedlist>
<listitem><para>Fix race condition in transaction log management</para>
@@ -478,7 +556,7 @@ table has been dropped</para></listitem>
</sect2>
</sect1>
<sect1 id="release-7-3-11">
<title>Release 7.3.11</title>
@@ -565,7 +643,7 @@ the variable is of pass-by-reference type</para></listitem>
It is strongly recommended that all installations repair this error,
either by initdb or by following the manual repair procedure given
below. The error at least allows unprivileged database users to crash
their server process, and may allow unprivileged users to gain the
their server process, and might allow unprivileged users to gain the
privileges of a database superuser.
</para>
@@ -591,12 +669,12 @@ COMMIT;
template databases then any subsequently created databases will contain
the same error. <literal>template1</> can be fixed in the same way
as any other database, but fixing <literal>template0</> requires
additional steps. First, from any database issue
additional steps. First, from any database issue:
<programlisting>
UPDATE pg_database SET datallowconn = true WHERE datname = 'template0';
</programlisting>
Next connect to <literal>template0</> and perform the above repair
procedure. Finally, do
procedure. Finally, do:
<programlisting>
-- re-freeze template0:
VACUUM FREEZE;
@@ -739,7 +817,7 @@ datestyles</para></listitem>
<itemizedlist>
<listitem><para>Repair possible failure to update hint bits on disk</para>
<para>
Under rare circumstances this oversight could lead to
Under rare circumstances this oversight could lead to
<quote>could not access transaction status</> failures, which qualifies
it as a potential-data-loss bug.
</para></listitem>
@@ -849,7 +927,7 @@ On some platforms, building with -fstrict-aliasing causes bugs.
</para></listitem>
<listitem><para>Make pg_restore handle 64-bit off_t correctly</para>
<para>
This bug prevented proper restoration from archive files exceeding 4Gb.
This bug prevented proper restoration from archive files exceeding 4 GB.
</para></listitem>
<listitem><para>Make contrib/dblink not assume that local and remote type OIDs
match (Joe)</para></listitem>
@@ -1149,7 +1227,7 @@ operations on bytea columns (Joe)</para></listitem>
A dump/restore is <emphasis>not</emphasis> required for those
running version 7.3. However, it should be noted that the main
<productname>PostgreSQL</productname> interface library, libpq,
has a new major version number for this release, which may require
has a new major version number for this release, which might require
recompilation of client code in certain cases.
</para>
</sect2>
@@ -1177,8 +1255,8 @@ operations on bytea columns (Joe)</para></listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-7-3">
<title>Release 7.3</title>
@@ -1385,7 +1463,7 @@ operations on bytea columns (Joe)</para></listitem>
<para>
<command>COPY</command> no longer considers missing trailing
columns to be null. All columns need to be specified.
(However, one may achieve a similar effect by specifying a
(However, one can achieve a similar effect by specifying a
column list in the <command>COPY</command> command.)
</para>
</listitem>
@@ -1941,7 +2019,7 @@ datestyles</para></listitem>
<itemizedlist>
<listitem><para>Repair possible failure to update hint bits on disk</para>
<para>
Under rare circumstances this oversight could lead to
Under rare circumstances this oversight could lead to
<quote>could not access transaction status</> failures, which qualifies
it as a potential-data-loss bug.
</para></listitem>
@@ -2082,8 +2160,8 @@ since <productname>PostgreSQL</productname> 7.1.
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-7-2-2">
<title>Release 7.2.2</title>
@@ -2125,8 +2203,8 @@ since <productname>PostgreSQL</productname> 7.1.
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-7-2-1">
<title>Release 7.2.1</title>
@@ -2286,7 +2364,7 @@ since <productname>PostgreSQL</productname> 7.1.
<listitem>
<para>
The semantics of the <command>VACUUM</command> command have
changed in this release. You may wish to update your
changed in this release. You might wish to update your
maintenance procedures accordingly.
</para>
</listitem>
@@ -2326,7 +2404,7 @@ since <productname>PostgreSQL</productname> 7.1.
<para>
The <literal>timestamp()</literal>, <literal>time()</literal>,
and <literal>interval()</literal> functions are no longer
available. Instead of <literal>timestamp()</literal>, use
available. Instead of <literal>timestamp()</literal>, use
<literal>timestamp 'string'</literal> or <literal>CAST</literal>.
</para>
</listitem>
@@ -2751,7 +2829,7 @@ since <productname>PostgreSQL</productname> 7.1.
<para>
<programlisting>
Remove unused WAL segements of large transactions (Tom)
Remove unused WAL segments of large transactions (Tom)
Multiaction rule fix (Tom)
PL/pgSQL memory allocation fix (Jan)
VACUUM buffer fix (Tom)
@@ -2798,7 +2876,7 @@ Fix PL/pgSQL SELECTs when returning no rows
Fix for psql backslash core dump
Referential integrity privilege fix
Optimizer fixes
pg_dump cleanups
pg_dump cleanups
</programlisting>
</para>
</sect2>
@@ -2881,7 +2959,7 @@ previous releases of <productname>PostgreSQL</productname> have forced
all data modifications to disk before each transaction commit. With
WAL, only one log file must be flushed to disk, greatly improving
performance. If you have been using -F in previous releases to
disable disk flushes, you may want to consider discontinuing its use.
disable disk flushes, you might want to consider discontinuing its use.
</para>
</listitem>
</varlistentry>
@@ -2922,7 +3000,7 @@ outer join syntax.
The previous C function manager did not
handle null values properly, nor did it support 64-bit <acronym>CPU</acronym>'s (Alpha). The new
function manager does. You can continue using your old custom
functions, but you may want to rewrite them in the future to use the new
functions, but you might want to rewrite them in the future to use the new
function manager call interface.
</para>
</listitem>
@@ -2937,7 +3015,7 @@ function manager call interface.
A large number of complex queries that were
unsupported in previous releases now work. Many combinations of views,
aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables
now work properly. Inherited tables are now accessed by default.
now work properly. Inherited tables are now accessed by default.
Subqueries in FROM are now supported.
</para>
</listitem>
@@ -2967,7 +3045,7 @@ Kerberos V fixes (David Wragg)
Fix for INSERT INTO...SELECT where targetlist has subqueries (Tom)
Prompt username/password on standard error (Bruce)
Large objects inv_read/inv_write fixes (Tom)
Fixes for to_char(), to_date(), to_ascii(), and to_timestamp() (Karel,
Fixes for to_char(), to_date(), to_ascii(), and to_timestamp() (Karel,
Daniel Baldoni)
Prevent query expressions from leaking memory (Tom)
Allow UPDATE of arrays elements (Tom)
@@ -2983,7 +3061,7 @@ Disallow DROP RULE, CREATE INDEX, TRUNCATE on views (Mark Hollomon)
Allow PL/pgSQL accept non-ASCII identifiers (Tatsuo)
Allow views to proper handle GROUP BY, aggregates, DISTINCT (Tom)
Fix rare failure with TRUNCATE command (Tom)
Allow UNION/INTERSECT/EXCEPT to be used with ALL, subqueries, views,
Allow UNION/INTERSECT/EXCEPT to be used with ALL, subqueries, views,
DISTINCT, ORDER BY, SELECT...INTO (Tom)
Fix parser failures during aborted transactions (Tom)
Allow temporary relations to properly clean up indexes (Bruce)
@@ -3019,14 +3097,14 @@ Improve ps status display for more platforms (Peter E, Marc)
Improve CREATE FUNCTION failure message (Ross)
JDBC improvements (Peter, Travis Bauer, Christopher Cain, William Webber,
Gunnar)
Grand Unified Configuration scheme/GUC. Many options can now be set in
Grand Unified Configuration scheme/GUC. Many options can now be set in
data/postgresql.conf, postmaster/postgres flags, or SET commands (Peter E)
Improved handling of file descriptor cache (Tom)
New warning code about auto-created table alias entries (Bruce)
Overhaul initdb process (Tom, Peter E)
Overhaul of inherited tables; inherited tables now accessed by default;
new ONLY key word prevents it (Chris Bitmead, Tom)
ODBC cleanups/improvements (Nick Gorham, Stephan Szabo, Zoltan Kovacs,
ODBC cleanups/improvements (Nick Gorham, Stephan Szabo, Zoltan Kovacs,
Michael Fork)
Allow renaming of temp tables (Tom)
Overhaul memory manager contexts (Tom)
@@ -3097,7 +3175,7 @@ New CIDR abbrev() function (Tom)
Performance
-----------
Write-Ahead Log (WAL) to provide crash recovery with less performance
Write-Ahead Log (WAL) to provide crash recovery with less performance
overhead (Vadim)
ANALYZE stage of VACUUM no longer exclusively locks table (Bruce)
Reduced file seeks (Denis Perchine)
@@ -3188,7 +3266,7 @@ Fix for psql \l+ when multibyte enabled (Tatsuo)
Allow PL/pgSQL to accept non ascii identifiers (Tatsuo)
Make vacuum always flush buffers (Tom)
Fix to allow cancel while waiting for a lock (Hiroshi)
Fix for memory aloocation problem in user authentication code (Tom)
Fix for memory allocation problem in user authentication code (Tom)
Remove bogus use of int4out() (Tom)
Fixes for multiple subqueries in COALESCE or BETWEEN (Tom)
Fix for failure of triggers on heap open in certain cases (Jeroen van
@@ -3319,7 +3397,7 @@ ecpg changes (Michael)
<simpara>2000-05-08</simpara>
</note>
<para>
<para>
This release contains improvements in many areas, demonstrating
the continued growth of <productname>PostgreSQL</productname>.
There are more improvements and fixes in 7.0 than in any previous
@@ -3395,7 +3473,7 @@ ecpg changes (Michael)
A dump/restore using <application>pg_dump</application>
is required for those wishing to migrate data from any
previous release of <productname>PostgreSQL</productname>.
For those upgrading from 6.5.*, you may instead use
For those upgrading from 6.5.*, you can instead use
<application>pg_upgrade</application> to upgrade to this
release; however, a full dump/reload installation is always the
most robust method for upgrades.
@@ -3416,7 +3494,7 @@ ecpg changes (Michael)
ease the transition by allowing
<productname>PostgreSQL</productname> to recognize
the deprecated type names and translate them to the new type
names, this mechanism may not be completely transparent to
names, this mechanism cannot be completely transparent to
your existing application.
</para>
</listitem>
@@ -3428,8 +3506,8 @@ ecpg changes (Michael)
decreased query times as the optimizer makes a better choice
for the preferred plan. However, in a small number of cases,
usually involving pathological distributions of data, your
query times may go up. If you are dealing with large amounts
of data, you may want to check your queries to verify
query times might go up. If you are dealing with large amounts
of data, you might want to check your queries to verify
performance.
</para>
</listitem>
@@ -3572,8 +3650,8 @@ Force permissions on PGDATA directory to be secure, even if it exists (Tom)
Added psql LASTOID variable to return last inserted oid (Peter E)
Allow concurrent vacuum and remove pg_vlock vacuum lock file (Tom)
Add privilege check for vacuum (Peter E)
New libpq functions to allow asynchronous connections: PQconnectStart(),
PQconnectPoll(), PQresetStart(), PQresetPoll(), PQsetenvStart(),
New libpq functions to allow asynchronous connections: PQconnectStart(),
PQconnectPoll(), PQresetStart(), PQresetPoll(), PQsetenvStart(),
PQsetenvPoll(), PQsetenvAbort (Ewan Mellor)
New libpq PQsetenv() function (Ewan Mellor)
create/alter user extension (Peter E)
@@ -3591,7 +3669,7 @@ Add CREATE/ALTER/DROP GROUP (Peter E)
All administration scripts now support --long options (Peter E, Karel)
Vacuumdb script now supports --all option (Peter E)
ecpg new portable FETCH syntax
Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF
Add ecpg EXEC SQL IFDEF, EXEC SQL IFNDEF, EXEC SQL ELSE, EXEC SQL ELIF
and EXEC SQL ENDIF directives
Add pg_ctl script to control backend start-up (Tatsuo)
Add postmaster.opts.default file to store start-up flags (Tatsuo)
@@ -3666,8 +3744,8 @@ Cleanups for int8 inputs, range checking, and type conversion (Tom)
Fix for SELECT timespan('21:11:26'::time) (Tom)
netmask('x.x.x.x/0') is 255.255.255.255 instead of 0.0.0.0 (Oleg Sharoiko)
Add btree index on NUMERIC (Jan)
Perl fix for large objects containing NUL characters (Douglas Thomson)
ODBC fix for for large objects (free)
Perl fix for large objects containing NUL characters (Douglas Thomson)
ODBC fix for large objects (free)
Fix indexing of cidr data type
Fix for Ethernet MAC addresses (macaddr type) comparisons
Fix for date/time types when overflows happened in computations (Tom)
@@ -3907,13 +3985,13 @@ Fix for EXPLAIN on inheritance(Tom)
Patch to allow vacuum on multisegment tables(Hiroshi)
R-Tree optimizer selectivity fix(Tom)
ACL file descriptor leak fix(Atsushi Ogawa)
New expresssion subtree code(Tom)
New expression subtree code(Tom)
Avoid disk writes for read-only transactions(Vadim)
Fix for removal of temp tables if last transaction was aborted(Bruce)
Fix to prevent too large row from being created(Bruce)
plpgsql fixes
Allow port numbers 32k - 64k(Bruce)
Add ^ precidence(Bruce)
Add ^ precedence(Bruce)
Rename sort files called pg_temp to pg_sorttemp(Bruce)
Fix for microseconds in time values(Tom)
Tutorial source cleanup
@@ -4075,10 +4153,10 @@ Add Win1250 (Czech) support (Pavel Behal)
The <citetitle>Administrator's Guide</citetitle> has a new
chapter on troubleshooting from Tom Lane.
And the <citetitle>Programmer's Guide</citetitle> has a
description of query processing, also from Stefan, and details
description of query processing, also from Stefan, and details
on obtaining the <productname>PostgreSQL</productname> source
tree via anonymous <productname>CVS</productname> and
<productname>CVSup</productname>.
<productname>CVSup</productname>.
</para>
</listitem>
</varlistentry>
@@ -4100,7 +4178,7 @@ Add Win1250 (Czech) support (Pavel Behal)
<para>
The new Multiversion Concurrency Control (MVCC) features can
give somewhat different behaviors in multiuser
environments. <emphasis>Read and understand the following section
environments. <emphasis>Read and understand the following section
to ensure that your existing applications will give you the
behavior you need.</emphasis>
</para>
@@ -4280,7 +4358,7 @@ JDBC fixes/features, see src/interfaces/jdbc/CHANGELOG(Peter)
Make % operator have precedence like /(Bruce)
Add new postgres -O option to allow system table structure changes(Bruce)
Update contrib/pginterface/findoidjoins script(Tom)
Major speedup in vacuum of deleted rows with indexes(Vadim)
Major speedup in vacuum of deleted rows with indexes(Vadim)
Allow non-SQL functions to run different versions based on arguments(Tom)
Add -E option that shows actual queries sent by \dt and friends(Masaaki Sakaida)
Add version number in start-up banners for psql(Masaaki Sakaida)
@@ -4295,7 +4373,7 @@ New pg_options: pretty_plan, pretty_parse, pretty_rewritten(Jan)
Better optimization statistics for system table access(Tom)
Better handling of non-default block sizes(Massimo)
Improve GEQO optimizer memory consumption(Tom)
UNION now suppports ORDER BY of columns not in target list(Jan)
UNION now supports ORDER BY of columns not in target list(Jan)
Major libpq++ improvements(Vince Vielhaber)
pg_dump now uses -z(ACL's) as default(Bruce)
backend cache, memory speedups(Tom)
@@ -4444,7 +4522,7 @@ Here is a brief, incomplete summary:
<itemizedlist>
<listitem>
<para>
Views and rules are now functional thanks to extensive new code in the
Views and rules are now functional thanks to extensive new code in the
rewrite rules system from Jan Wieck. He also wrote a chapter on it
for the <citetitle>Programmer's Guide</citetitle>.
</para>
@@ -4483,7 +4561,7 @@ which covers this topic.
<listitem>
<para>
Three new data types have been added.
Three new data types have been added.
Two types, <type>inet</type> and <type>cidr</type>, support various forms
of IP network, subnet, and machine addressing. There is now an 8-byte integer
type available on some platforms. See the chapter on data types
@@ -4515,7 +4593,7 @@ been.
<title>Migration to version 6.4</title>
<para>
A dump/restore using <application>pg_dump</application>
A dump/restore using <application>pg_dump</application>
or <application>pg_dumpall</application>
is required for those wishing to migrate data from any
previous release of <productname>PostgreSQL</productname>.
@@ -4585,7 +4663,7 @@ Readline cleanups(Tom)
Allow psql \f \ to make spaces as delimiter(Bruce)
Pass pg_attribute.atttypmod to the frontend for column field lengths(Tom,Bruce)
Msql compatibility library in /contrib(Aldrin)
Remove the requirement that ORDER/GROUP BY clause identifiers be
Remove the requirement that ORDER/GROUP BY clause identifiers be
included in the target list(David)
Convert columns to match columns in UNION clauses(Thomas)
Remove fork()/exec() and only do fork()(Bruce)
@@ -4593,7 +4671,7 @@ Jdbc cleanups(Peter)
Show backend status on ps command line(only works on some platforms)(Bruce)
Pg_hba.conf now has a sameuser option in the database field
Make lo_unlink take oid param, not int4
New DISABLE_COMPLEX_MACRO for compilers that can't handle our macros(Bruce)
New DISABLE_COMPLEX_MACRO for compilers that cannot handle our macros(Bruce)
Libpgtcl now handles NOTIFY as a Tcl event, need not send dummy queries(Tom)
libpgtcl cleanups(Tom)
Add -error option to libpgtcl's pg_result command(Tom)
@@ -4669,7 +4747,7 @@ New UNLISTEN command(Massimo)
psql and libpq now compile under Windows using win32.mak(Magnus)
Lo_read no longer stores trailing NULL(Bruce)
Identifiers are now truncated to 31 characters internally(Bruce)
Createuser options now availble on the command line
Createuser options now available on the command line
Code for 64-bit integer supported added, configure tested, int8 type(Thomas)
Prevent file descriptor leaf from failed COPY(Bruce)
New pg_upgrade command(Bruce)
@@ -4680,7 +4758,7 @@ New DECLARE and FETCH feature(Thomas)
libpq's internal structures now not exported(Tom)
Allow up to 8 key indexes(Bruce)
Remove ARCHIVE key word, that is no longer used(Thomas)
pg_dump -n flag to supress quotes around indentifiers
pg_dump -n flag to suppress quotes around indentifiers
disable system columns for views(Jan)
new INET and CIDR types for network addresses(TomH, Paul)
no more double quotes in psql output
@@ -4709,7 +4787,7 @@ NS32K platform fixes(Phil Nelson, John Buller)
SCO 7/UnixWare 2.x fixes(Billy,others)
Sparc/Solaris 2.5 fixes(Ryan)
Pgbuiltin.3 is obsolete, move to doc files(Thomas)
Even more documention(Thomas)
Even more documentation(Thomas)
Nextstep support(Jacek)
Aix support(David)
pginterface manual page(Bruce)
@@ -4756,7 +4834,7 @@ Correctly handles function calls on the left side of BETWEEN and LIKE clauses.
</itemizedlist>
</para>
<para>
A dump/restore is NOT required for those running 6.3 or 6.3.1. A
A dump/restore is NOT required for those running 6.3 or 6.3.1. A
<literal>make distclean</>, <literal>make</>, and <literal>make install</> is all that is required.
This last step should be performed while the postmaster is not running.
You should re-link any custom applications that use <productname>PostgreSQL</productname> libraries.
@@ -4833,7 +4911,7 @@ Improvements to the configuration autodetection for installation.
</itemizedlist>
</para>
<para>
A dump/restore is NOT required for those running 6.3. A
A dump/restore is NOT required for those running 6.3. A
<literal>make distclean</>, <literal>make</>, and <literal>make install</> is all that is required.
This last step should be performed while the postmaster is not running.
You should re-link any custom applications that use <productname>PostgreSQL</productname> libraries.
@@ -4910,7 +4988,7 @@ Better identify tcl and tk libs and includes(Bruce)
<listitem>
<para>
Socket interface for client/server connection. This is the default now
so you may need to start <application>postmaster</application> with the
so you might need to start <application>postmaster</application> with the
<option>-i</option> flag.
</para>
</listitem>
@@ -4946,9 +5024,9 @@ Better identify tcl and tk libs and includes(Bruce)
mention that without subselects, SQL is a very limited language.
Subselects are a major feature, and you should review your code for
places where subselects provide a better solution for your queries. I
think you will find that there are more uses for subselects than you may
think you will find that there are more uses for subselects than you might
think. Vadim has put us on the big SQL map with subselects, and fully
functional ones too. The only thing you can't do with subselects is to
functional ones too. The only thing you cannot do with subselects is to
use them in the target list.
</para>
<para>
@@ -4961,7 +5039,7 @@ Better identify tcl and tk libs and includes(Bruce)
Third, <type>char()</type> fields will now allow faster access than <type>varchar()</type> or
<type>text</type>. Specifically, the <type>text</> and <type>varchar()</type> have a penalty for access to
any columns after the first column of this type. <type>char()</type> used to also
have this access penalty, but it no longer does. This may suggest that
have this access penalty, but it no longer does. This might suggest that
you redesign some of your tables, especially if you have short character
columns that you have defined as <type>varchar()</type> or <type>text</type>. This and other
changes make 6.3 even faster than earlier releases.
@@ -4979,7 +5057,7 @@ Better identify tcl and tk libs and includes(Bruce)
<para>
User-created tables now no longer have SELECT privilege to PUBLIC by
default. This was done because the ANSI standard requires it. You can
of course GRANT any privileges you want after the table is created.
of course GRANT any privileges you want after the table is created.
System tables continue to be SELECT-able by PUBLIC.
</para>
<para>
@@ -5011,7 +5089,7 @@ Better identify tcl and tk libs and includes(Bruce)
<title>Migration to version 6.3</title>
<para>
A dump/restore using <application>pg_dump</application>
A dump/restore using <application>pg_dump</application>
or <application>pg_dumpall</application>
is required for those wishing to migrate data from any
previous release of <productname>PostgreSQL</productname>.
@@ -5057,7 +5135,7 @@ Check boolean input literals for 'true','false','yes','no','1','0'
and throw elog(ERROR) if unrecognized(Thomas)
Major large objects fix
Fix for GROUP BY showing duplicates(Vadim)
Fix for index scans in MergeJion(Vadim)
Fix for index scans in MergeJoin(Vadim)
Enhancements
------------
@@ -5065,7 +5143,7 @@ Subselects with EXISTS, IN, ALL, ANY key words (Vadim, Bruce, Thomas)
New User Manual(Thomas, others)
Speedup by inlining some frequently-called functions
Real deadlock detection, no more timeouts(Bruce)
Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP,
CURRENT_USER(Thomas)
Modify constraint syntax to be SQL92-compliant(Thomas)
Implement SQL92 PRIMARY KEY and UNIQUE clauses using indexes(Thomas)
@@ -5145,7 +5223,7 @@ Reduce system column overhead(Vadmin)
Remove pg_time table(Vadim)
Add pg_type attribute to identify types that need length (bpchar, varchar)
Add report of offending line when COPY command fails
Allow VIEW privileges to be set separately from the underlying tables.
Allow VIEW privileges to be set separately from the underlying tables.
For security, use GRANT/REVOKE on views as appropriate(Jan)
Tables now have no default GRANT SELECT TO PUBLIC. You must
explicitly grant such privileges.
@@ -5222,8 +5300,8 @@ Include example trigger function for inserting user names on table updates.
</itemizedlist>
</para>
<para>
This is a minor bug-fix release on 6.2.
For upgrades from pre-6.2 systems, a full dump/reload is required.
This is a minor bug-fix release on 6.2.
For upgrades from pre-6.2 systems, a full dump/reload is required.
Refer to the 6.2 release notes for instructions.
</para>
@@ -5325,14 +5403,14 @@ Catch non-functional delete attempts(Vadim)
Change time function names to be more consistent(Michael Reifenberg)
Check for zero divides(Michael Reifenberg)
Fix very old bug which made rows changed/inserted by a command
visible to the command itself (so we had multiple update of
visible to the command itself (so we had multiple update of
updated rows, etc.)(Vadim)
Fix for SELECT null, 'fail' FROM pg_am (Patrick)
SELECT NULL as EMPTY_FIELD now allowed(Patrick)
Remove un-needed signal stuff from contrib/pginterface
Fix OR (where x != 1 or x isnull didn't return rows with x NULL) (Vadim)
Fix time_cmp function (Vadim)
Fix handling of functions with non-attribute first argument in
Fix handling of functions with non-attribute first argument in
WHERE clauses (Vadim)
Fix GROUP BY when order of entries is different from order
in target list (Vadim)
@@ -5346,7 +5424,7 @@ Added JDBC driver as an interface(Adrian & Peter)
pg_password utility
Return number of rows inserted/affected by INSERT/UPDATE/DELETE etc.(Vadim)
Triggers implemented with CREATE TRIGGER (SQL3)(Vadim)
SPI (Server Programming Interface) allows execution of queries inside
SPI (Server Programming Interface) allows execution of queries inside
C-functions (Vadim)
NOT NULL implemented (SQL92)(Robson Paniago de Miranda)
Include reserved words for string handling, outer joins, and unions(Thomas)
@@ -5510,7 +5588,7 @@ optimizer which uses <firstterm>genetic</firstterm>
The interpretation of array specifiers (the curly braces around atomic
values) appears to have changed sometime after the original regression
tests were generated. The current <filename>./expected/*.out</filename> files reflect this
new interpretation, which may not be correct!
new interpretation, which might not be correct!
</para>
<para>
@@ -5579,7 +5657,7 @@ Enhancements
------------
attribute optimization statistics(Bruce)
much faster new btree bulk load code(Paul)
BTREE UNIQUE added to bulk load code(Vadim)
BTREE UNIQUE added to bulk load code(Vadim)
new lock debug code(Massimo)
massive changes to libpg++(Leo)
new GEQO optimizer speeds table multitable optimization(Martin)
@@ -5682,7 +5760,7 @@ because the COPY output format was improved from the 1.02 release.
<programlisting>
Bug Fixes
---------
ALTER TABLE bug - running postgress process needs to re-read table definition
ALTER TABLE bug - running postgres process needs to re-read table definition
Allow vacuum to be run on one table or entire database(Bruce)
Array fixes
Fix array over-runs of memory writes(Kurt)
@@ -5690,7 +5768,7 @@ Fix elusive btree range/non-range bug(Dan)
Fix for hash indexes on some types like time and date
Fix for pg_log size explosion
Fix permissions on lo_export()(Bruce)
Fix unitialized reads of memory(Kurt)
Fix uninitialized reads of memory(Kurt)
Fixed ALTER TABLE ... char(3) bug(Bruce)
Fixed a few small memory leaks
Fixed EXPLAIN handling of options and changed full_path option name
@@ -5734,7 +5812,7 @@ Change default decimal constant representation from float4 to float8(Bruce)
European date format now set when postmaster is started
Execute lowercase function names if not found with exact case
Fixes for aggregate/GROUP processing, allow 'select sum(func(x),sum(x+y) from z'
Gist now included in the distrubution(Marc)
Gist now included in the distribution(Marc)
Idend authentication of local users(Bryan)
Implement BETWEEN qualifier(Bruce)
Implement IN qualifier(Bruce)
@@ -5763,7 +5841,7 @@ Vacuum now had VERBOSE option(Bruce)
Source tree changes
-------------------
All functions now have prototypes that are compared against the calls
Allow asserts to be disabled easly from Makefile.global(Bruce)
Allow asserts to be disabled easily from Makefile.global(Bruce)
Change oid constants used in code to #define names
Decoupled sparc and solaris defines(Kurt)
Gcc -Wall compiles cleanly with warnings only from unfixable constructs
@@ -5776,13 +5854,13 @@ Name change from Postgres95 to PostgreSQL
New config.h file(Marc, Bryan)
PG_VERSION now set to 6.0 and used by postmaster
Portability additions, including Ultrix, DG/UX, AIX, and Solaris
Reduced the number of #define's, centeralized #define's
Reduced the number of #define's, centralized #define's
Remove duplicate OIDS in system tables(Dan)
Remove duplicate system catalog info or report mismatches(Dan)
Removed many os-specific #define's
Restructured object file generation/location(Bryan, Marc)
Restructured port-specific file locations(Bryan, Marc)
Unused/uninialized variables corrected
Unused/uninitialized variables corrected
</programlisting>
</para>
</sect2>
@@ -5922,8 +6000,8 @@ New Ports
</programlisting>
</para>
<!--
Contributors (appologies to any missed)
* Kurt J. Lidl &lt;lidl@va.pubnix.com&gt;
Contributors (apologies to any missed)
* Kurt J. Lidl &lt;lidl@va.pubnix.com&gt;
(missed in first run, but no less important)
* Erich Stamberger &lt;eberger@gewi.kfunigraz.ac.at&gt;
* Jason Wright &lt;jason@shiloh.vnet.net&gt;
@@ -5966,7 +6044,7 @@ Contributors (appologies to any missed)
<para>
The following notes are for the benefit of users who want to migrate
databases from <productname>Postgres95</> 1.0 to <productname>Postgres95</> 1.01.
databases from <productname>Postgres95</> 1.0 to <productname>Postgres95</> 1.01.
</para>
<para>
If you are starting afresh with <productname>Postgres95</> 1.01 and do not need
@@ -5974,7 +6052,7 @@ to migrate old databases, you do not need to read any further.
</para>
<para>
In order to <productname>Postgres95</> version 1.01 with databases created with
<productname>Postgres95</> version 1.0, the following steps are required:
<productname>Postgres95</> version 1.0, the following steps are required:
</para>
<procedure>
<step>
@@ -5985,7 +6063,7 @@ Set the definition of <symbol>NAMEDATALEN</symbol> in <filename>src/Makefile.glo
</step>
<step>
<para>
Decide whether you want to use Host based authentication.
Decide whether you want to use Host based authentication.
</para>
<substeps>
<step>
@@ -5998,7 +6076,7 @@ If you do, you must create a file name <literal>pg_hba</literal> in your top-lev
<step>
<para>
If you do not want host-based authentication, you can comment out
the line
the line:
<programlisting>
HBA = 1
</programlisting>
@@ -6021,7 +6099,7 @@ Compile and install 1.01, but DO NOT do the <command>initdb</command> step.
<step>
<para>
Before doing anything else, terminate your 1.0 postmaster, and
backup your existing <envar>$PGDATA</envar> directory.
backup your existing <envar>$PGDATA</envar> directory.
</para>
</step>
<step>
@@ -6044,7 +6122,7 @@ Start up a new 1.01 postmaster
<para>
Add the new built-in functions and operators of 1.01 to 1.0
databases. This is done by running the new 1.01 server against
your own 1.0 database and applying the queries attached and saving
your own 1.0 database and applying the queries attached and saving
in the file 1.0_to_1.01.sql. This can be done easily through <command>psql</command>.
If your 1.0 database is name <literal>testdb</literal>:
@@ -6129,12 +6207,12 @@ Enhancements:
is not desired, comment out HBA=1 in src/Makefile.global.
* changed regex handling to be uniform use of Henry Spencer's regex code
regardless of platform. The regex code is included in the distribution
* added functions and operators for case-insensitive regular expressions.
* added functions and operators for case-insensitive regular expressions.
The operators are ~* and !~*.
* pg_dump uses COPY instead of SELECT loop for better performance
Bug fixes:
* fixed an optimizer bug that was causing core dumps when
* fixed an optimizer bug that was causing core dumps when
functions calls were used in comparisons in the WHERE clause
* changed all uses of getuid to geteuid so that effective uids are used
* psql now returns non-zero status on errors when using -c
@@ -6170,11 +6248,11 @@ Incompatibilities:
Enhancements:
* sql LIKE syntax has been added
* copy command now takes an optional USING DELIMITER specification.
delimiters can be any single-character string.
delimiters can be any single-character string.
* IRIX 5.3 port has been added.
Thanks to Paul Walmsley and others.
* updated pg_dump to work with new libpq
* \d has been added psql
* \d has been added psql
Thanks to Keith Parks
* regexp performance for architectures that use POSIX regex has been
improved due to caching of precompiled patterns.
@@ -6224,7 +6302,7 @@ Incompatible changes:
* float literals (eg. 3.14) are now of type float4 (instead of float8 in
previous releases); you might have to do typecasting if you depend on it
being of type float8. If you neglect to do the typecasting and you assign
a float literal to a field of type float8, you may get incorrect values
a float literal to a field of type float8, you might get incorrect values
stored!
* LIBPQ has been totally revamped so that frontend applications
can connect to multiple backends
@@ -6243,34 +6321,34 @@ more compliant to the SQL-92 standard):
integer, int -&gt; int4
float, real -&gt; float4
char(N) and varchar(N) are implemented as truncated text types. In
addition, char(N) does blank-padding.
addition, char(N) does blank-padding.
* single-quote (') is used for quoting string literals; '' (in addition to
\') is supported as means of inserting a single quote in a string
* SQL standard aggregate names (MAX, MIN, AVG, SUM, COUNT) are used
(Also, aggregates can now be overloaded, i.e. you can define your
own MAX aggregate to take in a user-defined type.)
* CHANGE ACL removed. GRANT/REVOKE syntax added.
* CHANGE ACL removed. GRANT/REVOKE syntax added.
- Privileges can be given to a group using the "GROUP" key word.
For example:
GRANT SELECT ON foobar TO GROUP my_group;
The key word 'PUBLIC' is also supported to mean all users.
The key word 'PUBLIC' is also supported to mean all users.
Privileges can only be granted or revoked to one user or group
at a time.
at a time.
"WITH GRANT OPTION" is not supported. Only class owners can change
access control
- The default access control is to to grant users readonly access.
- The default access control is to grant users readonly access.
You must explicitly grant insert/update access to users. To change
this, modify the line in
src/backend/utils/acl.h
that defines ACL_WORLD_DEFAULT
this, modify the line in
src/backend/utils/acl.h
that defines ACL_WORLD_DEFAULT
Bug fixes:
* the bug where aggregates of empty tables were not run has been fixed. Now,
aggregates run on empty tables will return the initial conditions of the
aggregates. Thus, COUNT of an empty table will now properly return 0.
MAX/MIN of an empty table will return a row of value NULL.
MAX/MIN of an empty table will return a row of value NULL.
* allow the use of \; inside the monitor
* the LISTEN/NOTIFY asynchronous notification mechanism now work
* NOTIFY in rule action bodies now work
@@ -6285,7 +6363,7 @@ Other changes and enhancements:
* WARN and NOTICE messages no longer have timestamps on them. To turn on
timestamps of error messages, uncomment the line in
src/backend/utils/elog.h:
/* define ELOG_TIMESTAMPS */
/* define ELOG_TIMESTAMPS */
* On an access control violation, the message
"Either no such class or insufficient privilege"
will be given. This is the same message that is returned when
@@ -6304,8 +6382,8 @@ libpgtcl changes:
Portability enhancements and New Ports:
* flex/lex problems have been cleared up. Now, you should be able to use
flex instead of lex on any platforms. We no longer make assumptions of
what lexer you use based on the platform you use.
* The Linux-ELF port is now supported. Various configuration have been
what lexer you use based on the platform you use.
* The Linux-ELF port is now supported. Various configuration have been
tested: The following configuration is known to work:
kernel 1.2.10, gcc 2.6.3, libc 4.7.2, flex 2.5.2, bison 1.24
with everything in ELF format,
@@ -6339,9 +6417,9 @@ New documentation:
Incompatible changes:
* The SQL statement for creating a database is 'CREATE DATABASE' instead
of 'CREATEDB'. Similarly, dropping a database is 'DROP DATABASE' instead
of 'DESTROYDB'. However, the names of the executables 'createdb' and
of 'DESTROYDB'. However, the names of the executables 'createdb' and
'destroydb' remain the same.
New tools:
* pgperl - a Perl (4.036) interface to Postgres95
* pg_dump - a utility for dumping out a postgres database into a
@@ -6358,7 +6436,7 @@ The following ports have been incorporated into postgres95-beta-0.02:
The following bugs have been fixed in postgres95-beta-0.02:
* new lines not escaped in COPY OUT and problem with COPY OUT when first
attribute is a '.'
attribute is a '.'
* cannot type return to use the default user id in createuser
* SELECT DISTINCT on big tables crashes
* Linux installation problems
@@ -6487,20 +6565,3 @@ In general, however, 6.3 is substantially faster than previous releases (thanks,
</sect1>
]]>
</appendix>
<!-- Keep this comment at the end of the file
Local variables:
mode:sgml
sgml-omittag:nil
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"./reference.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:("/usr/lib/sgml/catalog")
sgml-local-ecat-files:nil
End:
-->