Prepare for final release.

HISTORY

-PostgreSQL 6.3               Sun Feb  1 14:57:30 EST 1998
+PostgreSQL 6.3               Sun Mar  1 14:57:30 EST 1998
 -------------------------------------------------------------
 
 A dump/restore is required for those wishing to migrate data from
@@ -39,16 +39,16 @@ Generate elog(ERROR) on over-large integer(Bruce)
 Allow multiple-argument functions in constraint clauses(Thomas)
 Check boolean input literals for 'true','false','yes','no','1','0'
 	and throw elog(ERROR) if unrecognized(Thomas)
-Change default table creation from ACL_RD to ACL_NO (aka private tables)(marc)
-
+Major large objects fix
 
 Enhancements
 ------------
+Subselects with EXISTS, IN, ALL, ANY keywords (Vadim, Bruce, Thomas)
+New User Manual(Thomas, others)
+Speedup by inlining some frequently-called functions
 Real deadlock detection, no more timeouts(Bruce)
-<NOT DONE YET> Subselects with EXISTS, IN, ALL, ANY keywords (Vadim, Bruce, Thomas)
 Add SQL92 "constants" CURRENT_DATE, CURRENT_TIME, CURRENT_TIMESTAMP, 
 	CURRENT_USER(Thomas)
-Speedup by inlining some frequently-called functions
 Modify constraint syntax to be SQL92-compliant(Thomas)
 Implement SQL92 PRIMARY KEY and UNIQUE clauses using indices(Thomas)
 Recognize SQL92 syntax for FOREIGN KEY. Throw elog notice(Thomas)
@@ -107,7 +107,6 @@ Add UNION, GROUP, DISTINCT to INSERT(Bruce)
 varchar() stores only necessary bytes on disk(Bruce)
 Fix for BLOBs(Peter)
 Mega-Patch for JDBC...see README_6.3 for list of changes(Peter)
-Allow installation data block size and max tuple size configuration(Darren)
 Remove unused "option" from PQconnectdb()
 New LOCK command and lock manual page describing deadlocks(Bruce)
 Add new psql \da, \dd, \df, \do, \dS, and \dT commands(Bruce)
@@ -122,8 +121,17 @@ Add Unix socket support to DBD::Pg(Goran)
 New python interface (PyGreSQL 2.0)(D'Arcy)
 New frontend/backend protocol has a version number, network byte order(Phil)
 Security features in pg_hba.conf enhanced and documented, many cleanups(Phil)
-New HTML and Postscript documentation(Thomas)
-
+CHAR() now faster access than VARCHAR() or TEXT
+ecpg embedded SQL preprocessor
+Add GROUP BY to INSERT INTO table SELECT * FROM table2
+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 permissions 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 permissions.
 
 Source Tree Changes
 -------------------
@@ -160,6 +168,7 @@ Start an AUX port
 Start a Cygnus port
 Add string functions to regression suite(Thomas)
 Expand a few function names formerly truncated to 16 characters(Thomas)
+Remove un-needed malloc() calls and replace with palloc()(Bruce)
 
 
 PostgreSQL 6.2.1                 Fri Oct 17 00:01:27 EDT 1997

migration/6.2.1_to_6.3

 This migration requires a complete dump of the 6.2 or 6.2.1 database and a
 restore of the database in 6.3.
 
-In addition, 6.3 has separate permissions for views, rather than relying
-on the permissions set on the underlying tables.  For this reason, you will
-have to set permissions on your views if you want anything but the default
-permissions.
-
-6.3 has had its default permissions on a table set such that unless you 
-are the owner, when a table is created, other users of the system won't 
-have access to them.  You *must* do a 'GRANT' for each table you wish open
-to other ppl.  
-
-Those migrating from earlier 1.* releases should first upgrade to 1.09
-because the COPY output format was improved from the 1.02 release.
+There are some general 6.3 issues that I want to mention.  These are
+only the big items that can not be described in one sentence.  A review
+of the HISTORY files is still needed.
+
+First, we now have subselects.  Now that we have them, I would like to
+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.  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
+use them in the target list.
+
+Second, 6.3 uses unix domain sockets rather than TCP/IP by default.  To
+enable connections from other machines, you have to use the new
+postmaster -i option, and of course edit pg_hba.conf.  Also, for this
+reason, the format of pg_hba.conf has changed.
+
+Third, char() fields will now allow faster access than varchar() or
+text. Specifically, the text and varchar() have a penalty for access to
+any columns after the first column of this type.  char() used to also
+have this access penalty, but it no longer does.  This may suggest that
+you redesign some of your tables, especially if you have short character
+columns that you have defined as varchar() or text.  This and other
+changes make 6.3 even faster than earlier releases.
+
+We now have passwords definable independent of any Unix file.  There are
+new SQL USER commands.  See the pg_hba.conf manual page for more
+information.  There is a new table, pg_shadow, which is used to store
+user information and user passwords, and it by default only SELECT-able
+by the postgres super-user.  pg_user is now a view of pg_shadow, and is
+SELECT-able by PUBLIC.  You should keep using pg_user in your
+application without changes.
+
+User-created tables now no longer have SELECT permission to PUBLIC by
+default.  This was done because the ANSI standard requires it.  You can
+of course GRANT any permissions you want after the table is created. 
+System tables continue to be SELECT-able by PUBLIC.
+
+We also have real deadlock detection code.  No more sixty-second
+timeouts.  And the new locking code implements a FIFO better, so there
+should be less resource starvation during heavy use.  For performance
+reasons, time travel is gone, but can be implemented using triggers (see
+pgsql/contrib/spi/README).  Please check out the new \d command for
+types, operators, etc.  Also, views have their own permissions now, not
+based on the underlying tables, so permissions on them have to be set
+separately.  Check /pgsql/interfaces for some new ways to talk to
+PostgreSQL.
+
+This is the first release that really required an explaination for
+existing users.  In many ways, this was necessary because the new
+release removes many limitations, and the work-arounds people were using
+are no longer needed.
+
+Long live PostgreSQL.
+
+-- Bruce Momjian

register.txt

 
 
-(1998-02-01)
+(1998-03-01)
 PostgreSQL has a Web site at http://www.postgresql.org/ which carries details
 on the latest release, upcoming features, and other information to make your
 work or play with PostgreSQL more productive.