Age | Commit message (Collapse) | Author |
|
> o -Allow multiple vacuums so large tables do not starve small
|
|
|
|
|
|
|
|
|
|
> * -Allow ORDER BY ... LIMIT # to select high/low value without sort or
<
< Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
< all values to return the high/low value. Instead The idea is to do a
< sequential scan to find the high/low value, thus avoiding the sort.
< MIN/MAX already does this, but not for LIMIT > 1.
<
|
|
< * Make standard_conforming_strings the default in 8.3?
> * Make standard_conforming_strings the default in 8.4?
|
|
< o Add support for MOVE and SCROLL cursors
<
< PL/pgSQL cursors should support the same syntax as
< backend cursors.
<
> o -Add support for MOVE cursors
> o Add support for SCROLL cursors
|
|
Jun Kuwamura
|
|
|
|
<H3 id="item3.6">3.6) What is the upgrade process for
PostgreSQL?</H3>
to reference both versioning and specific upgrade instructions.
|
|
> o -Allow commenting of variables in postgresql.conf to restore them
|
|
|
|
|
|
< o -Add MOVE
< o -Add support for SCROLL cursors
> o Add support for MOVE and SCROLL cursors
|
|
< o -Add support for WITH HOLD and SCROLL cursors
> o -Add support for SCROLL cursors
> o Add support for WITH HOLD cursors
|
|
< o Add support for WITH HOLD and SCROLL cursors
> o -Add support for WITH HOLD and SCROLL cursors
|
|
< o Add MOVE
> o -Add MOVE
|
|
< Currently all schemas are owned by the super-user because they are
< copied from the template1 database.
> Currently all schemas are owned by the super-user because they are copied
> from the template1 database. However, since all objects are inherited
> from the template database, it is not clear that setting schemas to the db
> owner is correct.
|
|
< * %Set proper permissions on non-system schemas during db creation
> * Set proper permissions on non-system schemas during db creation
|
|
< o Consider reducing on-disk varlena length from four to two
< because a heap row cannot be more than 64k in length
> o Consider reducing on-disk varlena length from four bytes to
> two because a heap row cannot be more than 64k in length
|
|
|
|
> * -Add RESET SESSION command to reset all session state
|
|
< o Allow single-byte header storage for arrays
> o Allow single-byte header storage for array elements
|
|
> o Allow single-byte header storage for arrays
|
|
> o Have WITH CONSTRAINTS also create constraint indexes
> http://archives.postgresql.org/pgsql-patches/2007-04/msg00149.php
|
|
* Simplify ability to create partitioned tables
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00151.php
|
|
> o -Make CLUSTER preserve recently-dead tuples per MVCC requirements
|
|
> o -Add more logical syntax CLUSTER table USING index;
|
|
> * -Allow use of indexes to search for NULLs
|
|
o -Support a smaller header for short variable-length fields
|
|
* Reduce WAL traffic so only modified values are written rather than
entire rows
>
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01589.php
>
|
|
<H3 id="item3.7">3.7) What computer hardware should I use?</H3>
|
|
> o -Allow PL/PythonU to return boolean rather than 1/0
|
|
< * Add transaction_idle_timeout GUC so locks are not held for long
> * Add idle_in_transaction_timeout GUC so locks are not held for long
|
|
< * Add idle_timeout GUC so locks are not held for log periods of time
> * Add transaction_idle_timeout GUC so locks are not held for long
> periods of time
|
|
> * Allow all data types to cast to and from TEXT
>
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00017.php
>
>
|
|
>
> * Add idle_timeout GUC so locks are not held for log periods of time
|
|
o Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
<
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00865.php
|
|
o Allow commenting of variables in postgresql.conf to restore them
to defaults
> http://archives.postgresql.org/pgsql-patches/2007-03/msg00180.php
|
|
o Allow a warm standby system to also allow read-only
statements
[pitr]
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00050.php
|
|
* Improve speed with indexes
For large table adjustments during VACUUM FULL, it is faster to cluster
or reindex rather than update the index. Also, index updates can bloat
the index.
>
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php
|
|
> o Have timestamp subtraction not call justify_hours()?
>
> http://archives.postgresql.org/pgsql-sql/2006-10/msg00059.php
>
< o Add overflow checking to timestamp and interval arithmetic
> o Add overflow checking to timestamp and interval arithmetic
|
|
< o Add table function support to pltcl, plpython
> o Add table function support to pltcl, plpythonu
< o Add PL/Python tracebacks
> o Add PL/PythonU tracebacks
< o Allow PL/Python to return boolean rather than 1/0
> o Allow PL/PythonU to return boolean rather than 1/0
|
|
> * Fix to_date()-related functions to consistently issue errors
>
> http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php
>
|
|
>
> o Allow PL/Python to return boolean rather than 1/0
>
> http://archives.postgresql.org/pgsql-patches/2007-01/msg00596.php
>
|
|
>
> * Consider reducing memory used for shared buffer reference count
>
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
|
|
o Allow RETURN to return row or record functions
> o Allow RETURN to return row or record functions
> http://archives.postgresql.org/pgsql-patches/2006-08/msg00397.php
> http://archives.postgresql.org/pgsql-hackers/2006-09/msg00388.php
|
|
< * Support a data type with specific enumerated values (ENUM)
<
< http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php
<
> * -Support a data type with specific enumerated values (ENUM)
|
|
>
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01803.php
|