Bruce Momjian
9f6ed2f47f
Update wording:
...
< Currently, ALTER USER and ALTER DATABASE support per-user and
> Currently ALTER USER and ALTER DATABASE support per-user and
< Currently, subtracting one date from another that crosses a
> Currently subtracting one date from another that crosses a
< Currently, SQL-language functions can only refer to parameters via $1, etc
> Currently SQL-language functions can only refer to dollar parameters,
> e.g. $1
< Currently, queries prepared via the libpq API are planned on first
> Currently queries prepared via the libpq API are planned on first
< Currently, SET <tab> causes a database lookup to check all
> Currently SET <tab> causes a database lookup to check all
< Currently, all statement results are transferred to the libpq
> Currently all statement results are transferred to the libpq
2007-02-18 01:34:35 +00:00
Bruce Momjian
0e461f275b
Add:
...
* Allow SQL-language functions to reference parameters by parameter name
Currently SQL-language functions can only refer to parameters via $1, etc
2007-02-18 01:32:55 +00:00
Bruce Momjian
37a22932f2
Add:
...
> * Allow holdable cursors in SPI
2007-02-17 02:01:02 +00:00
Bruce Momjian
c6ed4ead01
Add:
...
>
> o Allow row and record variables to be set to NULL constants,
> and allow NULL tests on such variables
>
> Because a row is not scalar, do not allow assignment
> from NULL-valued scalars.
2007-02-17 01:35:41 +00:00
Bruce Momjian
46bd3bff62
Add:
...
> o Consider reducing on-disk varlena length from four to two
> because a heap row cannot be more than 64k in length
2007-02-16 22:20:02 +00:00
Bruce Momjian
01191c7177
Add:
...
>
> o Use LC_TIME for localized weekday/month names, rather than
> LC_MESSAGES
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php
2007-02-14 21:00:17 +00:00
Bruce Momjian
33d72c7351
Add:
...
> * Clean up casting in /contrib/isn
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php
>
2007-02-14 04:24:42 +00:00
Bruce Momjian
7de3375f78
Add:
...
> * Improve logging of prepared statements recovered during startup
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php
>
2007-02-14 04:19:37 +00:00
Bruce Momjian
d7250994e6
Add URL for:
...
* Allow SQL-language functions to return results from RETURNING queries
>
> http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php
>
2007-02-14 02:49:37 +00:00
Bruce Momjian
65e2f55031
Add URL for:
...
>
> http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php
>
2007-02-14 00:47:05 +00:00
Bruce Momjian
e4f45d29be
Add URL for:
...
* Update Bonjour to work with newer cross-platform SDK
> http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php
2007-02-13 23:23:11 +00:00
Bruce Momjian
6e5c64b551
Add:
...
> * Improve failure message when DROP DATABASE is used on a database that
> has prepared transactions
2007-02-13 19:57:09 +00:00
Bruce Momjian
b9c65aed82
Add URL for:
...
* Update Bonjour to work with newer cross-platform SDK
>
> http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php
>
2007-02-13 18:08:39 +00:00
Bruce Momjian
954eb25a11
Add:
...
> * Update our code to handle 64-bit timezone files to match the zic
> source code, which now uses them
2007-02-13 17:03:16 +00:00
Bruce Momjian
1ad2f04bf2
Add blank line.
2007-02-09 03:39:59 +00:00
Bruce Momjian
9eddc28197
Add URL for:
...
<
> http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php
2007-02-09 03:39:39 +00:00
Bruce Momjian
19d561cbd0
Done!
...
< * Merge xmin/xmax/cmin/cmax back into three header fields
<
< Before subtransactions, there used to be only three fields needed to
< store these four values. This was possible because only the current
< transaction looks at the cmin/cmax values. If the current transaction
< created and expired the row the fields stored where xmin (same as
< xmax), cmin, cmax, and if the transaction was expiring a row from a
< another transaction, the fields stored were xmin (cmin was not
< needed), xmax, and cmax. Such a system worked because a transaction
< could only see rows from another completed transaction. However,
< subtransactions can see rows from outer transactions, and once the
< subtransaction completes, the outer transaction continues, requiring
< the storage of all four fields. With subtransactions, an outer
< transaction can create a row, a subtransaction expire it, and when the
< subtransaction completes, the outer transaction still has to have
< proper visibility of the row's cmin, for example, for cursors.
<
< One possible solution is to create a phantom cid which represents a
< cmin/cmax pair and is stored in local memory. Another idea is to
< store both cmin and cmax only in local memory.
<
> * -Merge xmin/xmax/cmin/cmax back into three header fields
2007-02-09 03:37:45 +00:00
Bruce Momjian
aba039df66
Update:
...
< * Consider placing all sequences in a single table
> * Consider placing all sequences in a single table, or create a system
> view
2007-02-09 01:29:48 +00:00
Bruce Momjian
5bdf44c647
Update:
...
< * Consider placing all sequences in a single table, now that system
< tables are full transactional
> * Consider placing all sequences in a single table
2007-02-09 00:34:31 +00:00
Bruce Momjian
18d36f9e19
Add:
...
> * Consider placing all sequences in a single table, now that system
> tables are full transactional
2007-02-09 00:32:15 +00:00
Bruce Momjian
2737f304ca
Add URL for:
...
* Add support for SQL-standard GENERATED/IDENTITY columns
> http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php
2007-02-08 21:51:50 +00:00
Bruce Momjian
869585cc8f
Split apart entries, one done now:
...
* -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h
* Consider making NAMEDATALEN more configurable in future releases
2007-02-06 16:44:14 +00:00
Bruce Momjian
fdd4a1ff0d
Updated TODO item:
...
> o Add a \set variable to control whether \s displays line numbers
> Another option is to add \# which lists line numbers, and
> allows command execution.
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
2007-02-05 17:17:13 +00:00
Bruce Momjian
fcbddea8b7
Modify:
...
< o Add \# to list command history like \s, but with line numbers
> o Add \# to list and execute command history
2007-02-05 16:49:13 +00:00
Bruce Momjian
03d442ca60
Add:
...
>
> * Allow custom variable classes that can restrict who can set the values
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php
>
2007-02-04 04:06:08 +00:00
Bruce Momjian
1d6653ee80
Update URL for:
...
* Allow sequential scans to take advantage of other concurrent
sequential scans, also called "Synchronised Scanning"
2007-02-04 02:32:03 +00:00
Bruce Momjian
28019984e9
Add:
...
>
> o Add \# to list command history like \s, but with line numbers
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
>
2007-02-04 01:50:59 +00:00
Bruce Momjian
300c43e303
Add URLs for:
...
* Allow sequential scans to take advantage of other concurrent
sequential scans, also called "Synchronised Scanning"
> http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php
2007-02-03 23:52:19 +00:00
Bruce Momjian
b6f6284802
Add:
...
> o Allow recovery.conf to allow the same syntax as
> postgresql.conf, including quoting
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
2007-02-03 22:32:49 +00:00
Bruce Momjian
b1b9c364cc
Add patches thread for:
...
* Reduce checkpoint performance degredation by forcing data to disk
more evenly
> http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php
2007-02-03 01:59:27 +00:00
Bruce Momjian
635425d845
Add URL for:
...
* Allow sequential scans to take advantage of other concurrent
sequential scans, also called "Synchronised Scanning"
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php
2007-02-02 23:05:36 +00:00
Bruce Momjian
69b90c49bc
Add:
...
> * Reduce checkpoint performance degredation by forcing data to disk
> more evenly
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php
2007-02-02 22:55:08 +00:00
Bruce Momjian
99be3fa3ee
Add URL for:
...
o Fix RENAME to work on variables other than OLD/NEW
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php
2007-02-02 21:34:39 +00:00
Bruce Momjian
98df90013f
Add:
...
> o Allow column display reordering by recording a display,
> storage, and permanent id for every column?
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php
>
2007-02-02 05:42:56 +00:00
Bruce Momjian
db047e571d
Add URL for:
...
o Add long file support for binary pg_dump output
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00551.php
2007-02-01 19:13:56 +00:00
Bruce Momjian
a867c5aa2f
Update URL for function permission checks
...
< http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php
>
2007-02-01 04:51:31 +00:00
Bruce Momjian
2ccb40b532
Add:
...
>
> * Tighten function permission checks
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
>
2007-02-01 04:50:58 +00:00
Bruce Momjian
fa3f06dc6b
Add:
...
>
> * Tighten trigger permission checks
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php
>
2007-02-01 04:49:43 +00:00
Bruce Momjian
e665137250
Add:
...
>
> * Fix problem when multiple subtransactions of the same outer transaction
> hold different types of locks, and one subtransaction aborts
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php
2007-02-01 04:35:52 +00:00
Bruce Momjian
40bf8717cf
Add URL for:
...
o Fix RENAME to work on variables other than OLD/NEW
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php
2007-02-01 00:32:45 +00:00
Bruce Momjian
147a3ce149
Add URL:
...
o Fix RENAME to work on variables other than OLD/NEW
>
> http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php
>
2007-01-31 04:23:47 +00:00
Bruce Momjian
99507b9a92
Add:
...
>
> * Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
>
> This is difficult because you must upgrade to an exclusive table lock
> to replace the existing index file. CREATE INDEX CONCURRENTLY does not
> have this complication. This would allow index compaction without
> downtime.
2007-01-31 03:17:49 +00:00
Bruce Momjian
62b2786b82
Update for VACUUM FULL:
...
< reindex rather than update the index.
> reindex rather than update the index. Also, index updates can
> bloat the index.
2007-01-31 03:07:36 +00:00
Bruce Momjian
aca00a8b98
Add:
...
> o ARRAY[[1,2],[3,4]])[1] should return the same values as
> ARRAY[[1,2],[3,4]])[1:1];
>
2007-01-30 22:55:12 +00:00
Bruce Momjian
631d7018df
Done:
...
< * Add Globally/Universally Unique Identifier (GUID/UUID)
> * -Add Globally/Universally Unique Identifier (GUID/UUID)
2007-01-29 21:19:30 +00:00
Bruce Momjian
abbf860f72
Add:
...
> * Enforce typmod for function inputs, function results and parameters for
> spi_prepare'd statements called from PLs
>
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php
2007-01-27 03:25:49 +00:00
Bruce Momjian
ddf569e3ed
Add:
...
> * Consider having the background writer update the transaction status
> hint bits before writing out the page
2007-01-27 02:29:32 +00:00
Bruce Momjian
f77b1f05f5
Add:
...
>
> * Consider increasing NUM_CLOG_BUFFERS
2007-01-27 02:28:16 +00:00
Bruce Momjian
2e6d1e5f7a
Add URL for shrinking tuple to just its headers:
...
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php
2007-01-25 22:25:53 +00:00
Bruce Momjian
9597446d11
Done:
...
> o -Add a GUC variable to control the tablespace for temporary objects
2007-01-25 04:38:59 +00:00