summaryrefslogtreecommitdiff
path: root/doc/src
AgeCommit message (Collapse)Author
2008-03-21Add:Bruce Momjian
> > * Fix inconsistent precedence of =, >, and < compared to <>, >=, and <= > > http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php
2008-03-21Add:Bruce Momjian
> > o Prevent SSL from sending network packets to avoid interference > with Win32 signal emulation > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00455.php
2008-03-21Document that soft-mounting NFS is not recommended.Bruce Momjian
2008-03-21Adjust pgstatindex() to give correct answers for indexes larger thanTom Lane
2^31 blocks. Also fix pg_relpages() for the same case. Tatsuhito Kasahara
2008-03-20Arrange for an explicit cast applied to an ARRAY[] constructor to be appliedTom Lane
directly to all the member expressions, instead of the previous implementation where the ARRAY[] constructor would infer a common element type and then we'd coerce the finished array after the fact. This has a number of benefits, one being that we can allow an empty ARRAY[] construct so long as its element type is specified by such a cast. Brendan Jurd, minor fixes by me.
2008-03-20Support a --no-tablespaces option in pg_dump/pg_dumpall/pg_restore, so thatTom Lane
dumps can be loaded into databases without the same tablespaces that the source had. The option acts by suppressing all "SET default_tablespace" commands, and also CREATE TABLESPACE commands in pg_dumpall's case. Gavin Roy, with documentation and minor fixes by me.
2008-03-19Support ALTER TYPE RENAME. Petr JelinekTom Lane
2008-03-19Add -M (query mode) option per ITAGAKI TakahiroTatsuo Ishii
2008-03-19Add libpq new API lo_import_with_oid() which is similar to lo_import()Tatsuo Ishii
except that lob's oid can be specified.
2008-03-18Spit items:Bruce Momjian
* Experiment with multi-threaded backend better I/O utilization This would allow a single query to make use of multiple I/O channels simultaneously. One idea is to create a background reader that can pre-fetch sequential and index scan pages needed by other backends. This could be expanded to allow concurrent reads from multiple devices in a partitioned table. * Experiment with multi-threaded backend better CPU utilization This would allow several CPUs to be used for a single query, such as for sorting or query execution.
2008-03-18Update TODO description:Bruce Momjian
* Speed WAL recovery by allowing more than one page to be prefetched This should be done utilizing the same infrastructure used for prefetching in general to avoid introducing complex error-prone code in WAL replay.
2008-03-18Add to TODO:Bruce Momjian
> > * Consider not storing a NULL bitmap on disk if all the NULLs are > trailing > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php > http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php >
2008-03-18cvsweb lives on anoncvs.postgresql.org these days.Magnus Hagander
2008-03-18Wiki page about cvs now lives in the main wiki, the oneMagnus Hagander
on developer.postgresql.org is going away.
2008-03-18Add TODO URLs for:Bruce Momjian
o Allow UPDATE tab SET ROW (col, ...) = (SELECT...) > http://archives.postgresql.org/pgsql-patches/2007-04/msg00315.php > http://archives.postgresql.org/pgsql-patches/2008-03/msg00237.php
2008-03-18Add URLs for :Bruce Momjian
* Speed WAL recovery by allowing more than one page to be prefetched This involves having a separate process that can be told which pages the recovery process will need in the near future. > http://archives.postgresql.org/pgsql-general/2007-12/msg00683.php > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00497.php <
2008-03-18Add TODO:Bruce Momjian
> o Recreate pg_xlog/archive_status/ if it doesn't exist after > restoring from a PITR backup > > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00487.php
2008-03-18Add to TODO:Bruce Momjian
> > * Consider Cartesian joins when both relations are needed to form an > indexscan qualification for a third relation > > http://archives.postgresql.org/pgsql-performance/2007-12/msg00090.php
2008-03-18Add URL for:Bruce Momjian
o Allow COPY to report error lines and continue This requires the use of a savepoint before each COPY line is processed, with ROLLBACK on COPY failure. > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00572.php
2008-03-17Add to TODO:Bruce Momjian
> > * Allow SSL key file permission checks to be optionally disabled when > sharing SSL keys with other applications > > http://archives.postgresql.org/pgsql-bugs/2007-12/msg00069.php
2008-03-17Add:Bruce Momjian
> > * Reduce BIT data type overhead using short varlena headers > > http://archives.postgresql.org/pgsql-general/2007-12/msg00273.php
2008-03-17Add to TODO:Bruce Momjian
> * Reduce file system activity overhead of statistics file pgstat.stat > > http://archives.postgresql.org/pgsql-general/2007-12/msg00106.php >
2008-03-17Add to TODO:Bruce Momjian
> * Consider if CommandCounterIncrement() can avoid its > AcceptInvalidationMessages() call > > http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php
2008-03-17Add URL for:Bruce Momjian
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT > http://archives.postgresql.org/pgsql-hackers/2007-11/msg01334.php
2008-03-17Add:Bruce Momjian
> > o Remove pre-7.3 pg_dump code that assumes pg_depend does not exit
2008-03-17Add URL for:Bruce Momjian
* Improve text search error messages > http://archives.postgresql.org/pgsql-hackers/2007-11/msg01146.php
2008-03-17Added to TODO:Bruce Momjian
> * Improve text search error messages > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00966.php > > > * Fix /contrib/ltree operator > > http://archives.postgresql.org/pgsql-bugs/2007-11/msg00044.php
2008-03-17Add TODO:Bruce Momjian
> > o Fix server restart problem when the server was shutdown during > a PITR backup > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00800.php >
2008-03-17Adjust TODO spacing.Bruce Momjian
2008-03-17Add TODO URL for:Bruce Momjian
* Consider increasing the number of default statistics target, and reduce statistics target overhead > http://archives.postgresql.org/pgsql-hackers/2008-01/msg01066.php
2008-03-17Add:Bruce Momjian
> > o Allow Kerberos to disable stripping of realms so we can > check the username@realm against multiple realms > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00009.php
2008-03-17Done:Bruce Momjian
> o -During index creation, pre-sort the tuples to improve build speed
2008-03-16Add a note to the CREATE INDEX reference page about the impact ofTom Lane
maintenance_work_mem and effective_cache_size on index creation speed.
2008-03-14Fix duplicate word, per Guillaume Lelarge.Alvaro Herrera
2008-03-13Update release notes for 8.3.1 and 8.2.7 releases.Tom Lane
2008-03-13Add URL for:Bruce Momjian
* Do async I/O for faster random read-ahead of data Async I/O allows multiple I/O requests to be sent to the disk with results coming back asynchronously. > http://archives.postgresql.org/pgsql-performance/2007-09/msg00255.php
2008-03-12Add psql TODO:Bruce Momjian
< * Include the symbolic SQLSTATE name in verbose error reports < < http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php
2008-03-12Add to TODO:Bruce Momjian
> * Expire published xmin for read-only and idle transactions > > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00343.php
2008-03-12Fix LISTEN/NOTIFY race condition reported by Laurent Birtz, by postponingTom Lane
pg_listener modifications commanded by LISTEN and UNLISTEN until the end of the current transaction. This allows us to hold the ExclusiveLock on pg_listener until after commit, with no greater risk of deadlock than there was before. Aside from fixing the race condition, this gets rid of a truly ugly kludge that was there before, namely having to ignore HeapTupleBeingUpdated failures during NOTIFY. There is a small potential incompatibility, which is that if a transaction issues LISTEN or UNLISTEN and then looks into pg_listener before committing, it won't see any resulting row insertion or deletion, where before it would have. It seems unlikely that anyone would be depending on that, though. This patch also disallows LISTEN and UNLISTEN inside a prepared transaction. That case had some pretty undesirable properties already, such as possibly allowing pg_listener entries to be made for PIDs no longer present, so disallowing it seems like a better idea than trying to maintain the behavior.
2008-03-12Add:Bruce Momjian
> > * Consider a special data type for regular expressions > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php
2008-03-12Update TODO:Bruce Momjian
* Add array_accum() and array_to_set() functions for arrays The standards specify array_agg() and UNNEST. http://archives.postgresql.org/pgsql-hackers/2007-08/msg00464.php
2008-03-12Add URL for:Bruce Momjian
* Consider a simplified API for full text searches > http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php
2008-03-12Add for Win32 TODO:Bruce Momjian
> > o Convert MSVC build system to remove most batch files > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00961.php
2008-03-12Add URL for:Bruce Momjian
* Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY > http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php
2008-03-12Add for Win32 TODO:Bruce Momjian
> o Diagnose problem where shared memory can sometimes not be > attached by postmaster children > > http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php >
2008-03-12Add to TODO:Bruce Momjian
> > * Remove use of MAKE_PTR and MAKE_OFFSET macros > > http://archives.postgresql.org/pgsql-general/2007-08/msg01510.php
2008-03-12Add to TODO:Bruce Momjian
> > * Add array_accum() and array_to_set() functions for arrays > > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00464.php
2008-03-12Add URL for:Bruce Momjian
* 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-08/msg00307.php
2008-03-12Add:Bruce Momjian
> > * Allow domains to be cast > > http://archives.postgresql.org/pgsql-hackers/2003-06/msg01206.php > http://archives.postgresql.org/pgsql-hackers/2007-08/msg00289.php
2008-03-12Add:Bruce Momjian
> > * Consider simplifying how memory context resets handle child contexts > > http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php