Here are some of the fixes in 6.3 if people want to test them.
The only problem I know of is that:
update test set x = max(test2.y)
only updates one row each time it is run. Any ideas on a fix?
---------------------------------------------------------------------------
RELIABILITY
-----------
* Overhaul mdmgr/smgr to fix double unlinking and double opens, cleanup
* Overhaul bufmgr/lockmgr/transaction manager
* -Fix CLUSTER
* Remove EXTEND?
* -Aggregates on VIEW always returns zero (maybe because there is no oid for views?)
* CREATE VIEW requires super-user priviledge
* can lo_export()/lo_import() read/write anywhere, causing a security problem?
* Tables that start with xinv confused to be large objects
* Two and three dimmensional arrays display improperly, missing {}
* -Add GROUP BY to INSERT INTO table SELECT * FROM table2
* lo_unlink() crashes server
* Prevent auto-table reference, like SELECT table.col WHERE col = 3 (?)
* -Remove un-needed malloc() calls and replace with palloc().
* SELECT * FROM table WHERE int4_column = '1' fails
* SELECT a[1] FROM test fails, it needs test.a[1]
* -SELECT COUNT(*) FROM TAB1, TAB2 fails
* -SELECT SUM(2+2) FROM table dumps core
* UPDATE table SET table.value = 3 fails
* -UPDATE key_table SET keyval=count(reftab.num) fails
* -INSERT INTO ... SELECT DISTINCT ... does not accept DISTINCT
* -INSERT INTO table SELECT id, count(*) FROM table2 GROUP BY id generates error
* Make pg_dump preserve inheritance column order, do non-inherits first
* User who can create databases can modify pg_database table
--
Bruce Momjian
maillist@candle.pha.pa.us