Update for 6.5.3, including new INSTALL file and updated HISTORY.

Author: bmomjian

HISTORY

@@ -2,7 +2,7 @@
 PostgreSQL Data Base Management System (formerly known as Postgres, then
 as Postgres95).
 
-This directory contains the stable version of 6.5.2 of the PostgreSQL
+This directory contains the stable version of 6.5.3 of the PostgreSQL
 database server.  The server is not ANSI SQL compliant, but it gets
 closer with every release.  After you unzip and untar the distribution
 file, look at file INSTALL for the installation notes and file HISTORY

INSTALL

@@ -96,6 +96,7 @@
    4.21) My large-object operations get invalid large obj descriptor.
    Why?
    4.22) How do I create a column that will default to the current time?
+   4.23) Why are my subqueries using IN so slow?
 
                             Extending PostgreSQL
 
@@ -198,8 +199,8 @@
    Unix/NT porting library. See pgsql/doc/README.NT in the distribution.
 
    There is also a web page at
-   http://members.tripod.com/~kevlo/postgres/portNT.html. There is
-   another port using U/Win at http://surya.wipro.com/uwin/ported.html.
+   http://www.freebsd.org/~kevlo/postgres/portNT.html. There is another
+   port using U/Win at http://surya.wipro.com/uwin/ported.html.
 
     1.5) Where can I get PostgreSQL?
 
@@ -913,10 +914,27 @@ BYTEA           bytea           variable-length array of bytes
 
    but this makes the column default to the time of table creation, not
    the time of row insertion. Instead do:
-        create table test (x int, modtime timestamp default text 'now');
+        CREATE TABLE test (x int, modtime timestamp default now() );
 
-   The casting of the value to text prevents the default value from being
-   computed at table creation time, and delays it until insertion time.
+   The calling of the function now() prevents the default value from
+   being computed at table creation time, and delays it until insertion
+   time. We believe this will not be a problem in post-6.5.* releases.
+   
+    4.23) Why are my subqueries using IN so slow?
+    
+   Currently, we join subqueries to outer queries by sequential scanning
+   the result of the subquery for each row of the outer query. A
+   workaround is to replace IN with EXISTS. For example, change:
+        SELECT *
+        FROM tab
+        WHERE col1 IN (SELECT col2 FROM TAB2)
+
+   to:
+        SELECT *
+        FROM tab
+        WHERE EXISTS (SELECT col2 FROM TAB2 WHERE col1 = col2)
+
+   We hope to fix this limitation in a future release.
      _________________________________________________________________
 
                             Extending PostgreSQL

README

@@ -1,6 +1,6 @@
 TODO list for PostgreSQL
 ========================
-Last updated:		Mon Sep  6 23:55:43 EDT 1999
+Last updated:		Sun Oct 10 16:40:40 EDT 1999
 
 Current maintainer:	Bruce Momjian (maillist@candle.pha.pa.us)
 
@@ -9,6 +9,9 @@ the PostgreSQL web site, http://www.PostgreSQL.org.
 
 A dash(-) marks changes that will appear in the next release.
 
+Names in brackets "[]" indicate more detailed information is available in
+the directory pgsql/doc/TODO.detail/ under that name.
+
 
 RELIABILITY
 -----------
@@ -17,7 +20,7 @@ RESOURCES
 
 * Elog() does not free all its memory(Jan)
 * spinlock stuck problem when elog(FATAL) and elog(ERROR) inside bufmgr
-* Recover or force failure when disk space is exhausted
+* -Recover or force failure when disk space is exhausted(Hiroshi)
 
 PARSER
 
@@ -26,57 +29,69 @@ PARSER
 * SELECT pg_class FROM pg_class generates strange error
 * Alter TABLE ADD COLUMN does not honor DEFAULT, add CONSTRAINT
 * Do not allow bpchar column creation without length
-* Select a[1] FROM test fails, it needs test.a[1]
-* -Array index references without table name cause problems
-* Update table SET table.value = 3 fails
+* -Select a[1] FROM test fails, it needs test.a[1](Tom)
+* -Array index references without table name cause problems [array](Tom)
+* Update table SET table.value = 3 fails(SQL standard says this is OK)
 * Creating index of TIMESTAMP & RELTIME fails, or rename to DATETIME(Thomas)
 * SELECT foo UNION SELECT foo is incorrectly simplified to SELECT foo
-* -INSERT ... SELECT ... GROUP BY groups by target columns not source columns
-* -CREATE TABLE test (a char(5) DEFAULT text '', b int4) fails on INSERT
+* -INSERT ... SELECT ... GROUP BY groups by target columns not source columns(Tom)
+* -CREATE TABLE test (a char(5) DEFAULT text '', b int4) fails on INSERT(Tom)
 * UNION with LIMIT fails
 * Unique index on base column not honored on inserts from inherited table
   INSERT INTO inherit_table (unique_index_col) VALUES (dup) should fail
+  [inherit] 
 * CREATE TABLE x AS SELECT 1 UNION SELECT 2 fails
 * CREATE TABLE test(col char(2) DEFAULT user) fails in length restriction
+* mismatched types in CREATE TABLE ... DEFAULT causes problems [default]
 * SELECT ... UNION ... ORDER BY fails when sort expr not in result list
 * Be smarter about promoting types when UNION merges different data types
 * SELECT ... UNION ... GROUP BY fails if column types disagree
 * redesign INSERT ... SELECT to have two levels of target list
 * -select * from pg_class where oid in (0,-1)
 * have INTERSECT/EXCEPT prevent duplicates unless ALL is specified
+* prevent primary key of nine columns [primary]
+* SELECT COUNT('asdf') FROM pg_class WHERE oid=12 crashes
+* SELECT DISTINCT ON col1 col1 col2 FROM tab1 is broken [distinct]
+* -When using aggregates + GROUP BY, no rows in should yield no rows out(Tom)
+* -Allow HAVING to use comparisons that have no aggregates(Tom)
 
 VIEWS
 
 * Views containing aggregates sometimes fail(Jan)
 * Views with spaces in view name fail when referenced
+* Creating view and inheriting the view causes view* to show
+  duplicates(inherit) 
 
 MISC
 
 * User who can create databases can modify pg_database table
 * Plpgsql does not handle quoted mixed-case identifiers
 * Fix btree to give a useful elog when key > 1/2 (page - overhead)
 * pg_dump should preserve primary key information
+* plpgsql regression tests fail on BSD/OS
+* database names with spaces fail
 
 ENHANCEMENTS
 ------------
 
 URGENT
 
-* Add referential integrity(Jan?)
-* Add OUTER joins, left and right(Thomas, Bruce)
+* Add referential integrity(Jan?)[primary]
+* Add OUTER joins, left and right[outer](Thomas, Bruce)
 * Allow long tuples by chaining or auto-storing outside db (chaining,large objs)
 * Eliminate limits on query length
-* Fix memory leak for expressions?, aggregates?(Tom?)
+* Fix memory leak for expressions[memory](Tom?) 
+* -Fix memory leak for aggregates(Tom)
 
 ADMIN
 
 * Better interface for adding to pg_group
 * More access control over who can create tables and access the database
-* Add syslog functionality
+* Test syslog functionality
 * Allow elog() to return error codes, not just messages
 * Allow international error message support and add error codes
-* Generate postmaster pid file and remove flock/fcntl lock code
-* Add ability to specifiy location of lock/socket files
+* Generate postmaster pid file and remove flock/fcntl lock code [flock]
+* Add ability to specifiy location of lock/socket files [flock]
 
 TYPES
 
@@ -99,11 +114,14 @@ TYPES
 * Add support for & operator
 * Allow LOCALE on a per-column basis, default to ASCII
 * Allow array on int8[]
+* Allow nulls in arrays
+* Allow arrays to be ORDER'ed
 * Remove Money type, add money formatting for decimal type
 * Declare typein/out functions in pg_proc with a special "C string" data type
 * Add non-large-object binary field
-* Add index on NUMERIC/DECIMAL type
+* -Add index on NUMERIC/DECIMAL type(Jan)
 * Make Absolutetime/Relativetime int4 because time_t can be int8 on some ports
+* Functions returning sets don't really work right[function]
 
 VIEWS
 
@@ -116,28 +134,29 @@ INDEXES
 * Allow CREATE INDEX zman_index ON test (date_trunc( 'day', zman ) datetime_ops)
   fails index can't store constant parameters
 * Allow creation of functional indexes to use default types
-* Permissions on indexes - prevent them?
+* Permissions on indexes, prevent them?
 * Allow SQL function indexes
 * Add FILLFACTOR to index creation
 * Allow indexing of LIKE with localle character sets
 * Allow indexing of more than eight columns
 
 COMMANDS
 
-* ALTER TABLE ADD COLUMN to inherited table put column in wrong place
+* ALTER TABLE ADD COLUMN to inherited table put column in wrong place [inherit]
 * Add ALTER TABLE DROP/ALTER COLUMN feature
-* Allow CLUSTER on all tables at once, and improve CLUSTER
-* Generate error on CREATE OPERATOR of ~~, ~ and and ~*
+* Allow CLUSTER on all tables at once, and improve CLUSTER, loses NOT
+	NULL specification on table [cluster]
 * Add SIMILAR TO to allow character classes, 'pg_[a-c]%'
 * Auto-destroy sequence on DROP of table with SERIAL(Ryan)
 * Allow LOCK TABLE tab1, tab2, tab3 so all tables locked in unison
 * Allow INSERT/UPDATE of system-generated oid value for a row
-* Allow ESCAPE '\' at the end of LIKE for ANSI compliance
+* Allow ESCAPE '\' at the end of LIKE for ANSI compliance [like]
 * Rewrite the LIKE handling by rewriting the user string with the 
-  supplied ESCAPE
-* Move LIKE index optimization handling to the optimizer
+  supplied ESCAPE [like]
+* -Move LIKE index optimization handling to the optimizer(Tom)
 * Allow RULE recompilation
 * Support UNION/INTERSECT/EXCEPT in sub-selects
+* Allow DELETE and UPDATE to use inheritance using tablename*
 
 CLIENTS
 
@@ -147,15 +166,15 @@ CLIENTS
 * Update reltuples from COPY command
 * Allow psql \copy to allow delimiters
 * Add a function to return the last inserted oid, for use in psql scripts
-* Allow psql to print nulls as distinct from ""(?)
-* PQrequestCancel() be able to terminate backend waiting for lock
+* Allow psql to print nulls as distinct from "" [null]
 
 EXOTIC FEATURES
 
 * Add sql3 recursive unions
 * Add the concept of dataspaces
 * Add replication of distributed databases
 * Allow queries across multiple databases
+* Allow nested transactions
 
 MISC
 
@@ -164,61 +183,63 @@ MISC
 * Create a background process for each database that runs while
   database is idle, finding superceeded rows, gathering stats and vacuuming
 * Add UNIQUE capability to non-btree indexes
-* Certain indexes will not shrink, i.e. oid indexes with many inserts
+* -Certain indexes will not shrink, i.e. oid indexes with many inserts(Vadim)
 * Restore unused oid's on backend exit if no one else has gotten oids
 * Have UPDATE/DELETE clean out indexes
-* Allow WHERE restriction on ctid
+* -Allow WHERE restriction on ctid(Hiroshi)
 * Allow cursors to be DECLAREd/OPENed/CLOSEed outside transactions
 * Allow PQrequestCancel() to terminate when in waiting-for-lock state
-* Transaction log, so re-do log can be on a separate disk by
-  with after-row images(Vadim)
+* -Transaction log, so re-do log can be on a separate disk by
+  with after-row images(Vadim) [logging](Vadim)
 * Populate backend status area and write program to dump status data
 * Make oid use unsigned int more reliably, pg_atoi()
 * Allow subqueries in target list
-* Put sort files, large objects in their on directory
-* Do autocommit so always in a transaction block
-* Show location of syntax error in query
-* Redesign the function call interface to handle NULLs better(Jan)
-* Document/trigger/rule so changes to pg_shadow create pg_pwd
-* Missing optimizer selectivities for date, r-tree, etc.
+* Put sort files, large objects in their own directory
+* Do autocommit so always in a transaction block(?)
+* Show location of syntax error in query [yacc]
+* Redesign the function call interface to handle NULLs better [function]
+* Document/trigger/rule so changes to pg_shadow recreate pg_pwd [pg_shadow]
+* Missing optimizer selectivities for date, r-tree, etc. [optimizer]
 * Overhaul mdmgr/smgr to fix double unlinking and double opens, cleanup
 * Overhaul bufmgr/lockmgr/transaction manager
 * Add PL/Perl(Mark Hollomon)
 * Make postgres user have a password by default
 * Add configure test to check for C++ need for *.h and namespaces
 * Allow BLCKSZ <= 64k, not <= 32k
 * redesign UNION structures to have separarate target lists
+* Allow multi-level query trees for INSERT INTO ... SELECT
 
 PERFORMANCE
 -----------
 
 FSYNC
 
-* Allow transaction commits with rollback with no-fsync performance
-* Prevent fsync in SELECT-only queries
+* -Allow transaction commits with rollback with no-fsync performance [fsync](Vadim)
+* -Prevent fsync in SELECT-only queries(Vadim)
 
 INDEXES
 
 * Use indexes in ORDER BY for restrictive data sets, min(), max()
 * Pull requested data directly from indexes, bypassing heap data
 * Use index to restrict rows returned by multi-key index when used with
   non-consecutive keys or OR clauses, so fewer heap accesses
-* Convert function(constant) into a constant for index use
+* -Convert function(constant) into a constant for index use(Tom)
 * Allow LIMIT ability on single-table queries that have no ORDER BY to use
-  a matching index
-* Improve LIMIT processing by using index to limit rows processed
-* Have optimizer take LIMIT into account when considering index scans
+  a matching index [limit]
+* Improve LIMIT processing by using index to limit rows processed [limit]
+* Have optimizer take LIMIT into account when considering index scans [limit]
 * Make index creation use psort code, because it is now faster(Vadim)
 * Allow creation of sort temp tables > 1 Gig
 * Create more system table indexes for faster cache lookups
 * fix indexscan() so it does leak memory by not requiring caller to free
 * Improve _bt_binsrch() to handle equal keys better, remove _bt_firsteq()(Tom)
-* Allow SELECT * FROM tab WHERE int2col = 4 use int2col index
-* Allow optimizer to prefer plans that match ORDER BY
+* Allow SELECT * FROM tab WHERE int2col = 4 use int2col index, int8,
+  float4, numeric/decimal too [optimizer]
+* -Allow optimizer to prefer plans that match ORDER BY(Tom)
 
 CACHE
 
-* Cache most recent query plan(s?)
+* Cache most recent query plan(s) [prepare]
 * Shared catalog cache, reduce lseek()'s by caching table size in shared area
 * elog() flushes cache, try invalidating just entries from current xact,
   perhaps using invalidation cache
@@ -227,33 +248,37 @@ CACHE
 MISC
 
 * Allow compression of log and meta data
-* Update pg_statistic table to remove operator column
 * Allow char() not to use variable-sized header to reduce disk size
 * Do async I/O to do better read-ahead of data
-* -Fix memory exhaustion when using many OR's
+* -Fix memory exhaustion when using many OR's [cnfify](Tom)
 * Get faster regex() code from Henry Spencer <henry@zoo.utoronto.ca>
   when it is available
 * Use mmap() rather than SYSV shared memory(?)
-* Process const = const parts of OR clause in separate pass
+* -Process const = const parts of OR clause in separate pass(Tom)
 * Make oid use oidin/oidout not int4in/int4out in pg_type.h
 * Improve Subplan list handling
 * Allow Subplans to use efficient joins(hash, merge) with upper variable
+  [subquery]
 * use fmgr_info()/fmgr_faddr() instead of fmgr() calls in high-traffic
   places, like GROUP BY, UNIQUE, index processing, etc.
 * improve dynamic memory allocation by introducing tuple-context memory
-  allocation
+  allocation [memory]
 * fix memory leak in cache code when non-existant table is referenced
 * In WHERE tab1.x=3 AND tab1.x=tab2.y, add tab2.y=3
-* pass atttypmod through parser in more cases(Bruce)
+* pass atttypmod through parser in more cases [atttypmod]
 * remove duplicate type in/out functions for disk and net
+* Allow persistent backends [persistent]
+* Misc [performance]
 
 SOURCE CODE
 -----------
 * Add use of 'const' for varibles in source tree
-* Fix C optimizer problem where fmgr_ptr calls return different types
-* Add needed includes and removed unneede include files(Bruce)
+* Fix C optimizer problem where fmgr_ptr calls return different types [alpha]
+* -Add needed includes and removed unneeded include files(Bruce)
 * Make configure --enable-debug add -g on compile line
-
+* Does Mariposa source contain any other bug fixes?
+* Remove SET KSQO option if OR processing is improved(Tom)
+* rename 'createuser' to 'pg_createuser', and add 'pg_' to other commands
 ---------------------------------------------------------------------------
 
 

doc/FAQ

@@ -27,7 +27,7 @@ System Configuration
 
   Operating System (example: Linux 2.0.26 ELF) 	:
 
-  PostgreSQL version (example: PostgreSQL-6.5.2):   PostgreSQL-6.5.2 
+  PostgreSQL version (example: PostgreSQL-6.5.3):   PostgreSQL-6.5.3 
 
   Compiler used (example:  gcc 2.8.0)		:
 

doc/TODO

@@ -1,6 +1,6 @@
 
 
-(1999-09-15)
+(1999-10-13)
 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.