Age | Commit message (Collapse) | Author |
|
>
> * Fix inconsistent precedence of =, >, and < compared to <>, >=, and <=
>
> http://archives.postgresql.org/pgsql-bugs/2007-12/msg00145.php
|
|
>
> o Prevent SSL from sending network packets to avoid interference
> with Win32 signal emulation
>
> http://archives.postgresql.org/pgsql-hackers/2007-12/msg00455.php
|
|
|
|
2^31 blocks. Also fix pg_relpages() for the same case.
Tatsuhito Kasahara
|
|
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.
|
|
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.
|
|
|
|
|
|
except that lob's oid can be specified.
|
|
* 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.
|
|
* 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.
|
|
>
> * 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
>
|
|
|
|
on developer.postgresql.org is going away.
|
|
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
|
|
* 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
<
|
|
> 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
|
|
>
> * 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
|
|
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
|
|
>
> * 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
|
|
>
> * Reduce BIT data type overhead using short varlena headers
>
> http://archives.postgresql.org/pgsql-general/2007-12/msg00273.php
|
|
> * Reduce file system activity overhead of statistics file pgstat.stat
>
> http://archives.postgresql.org/pgsql-general/2007-12/msg00106.php
>
|
|
> * Consider if CommandCounterIncrement() can avoid its
> AcceptInvalidationMessages() call
>
> http://archives.postgresql.org/pgsql-committers/2007-11/msg00585.php
|
|
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
> http://archives.postgresql.org/pgsql-hackers/2007-11/msg01334.php
|
|
>
> o Remove pre-7.3 pg_dump code that assumes pg_depend does not exit
|
|
* Improve text search error messages
> http://archives.postgresql.org/pgsql-hackers/2007-11/msg01146.php
|
|
> * 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
|
|
>
> o Fix server restart problem when the server was shutdown during
> a PITR backup
>
> http://archives.postgresql.org/pgsql-hackers/2007-11/msg00800.php
>
|
|
|
|
* Consider increasing the number of default statistics target, and
reduce statistics target overhead
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg01066.php
|
|
>
> 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
|
|
> o -During index creation, pre-sort the tuples to improve build speed
|
|
maintenance_work_mem and effective_cache_size on index creation speed.
|
|
|
|
|
|
* 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
|
|
< * Include the symbolic SQLSTATE name in verbose error reports
<
< http://archives.postgresql.org/pgsql-general/2007-09/msg00438.php
|
|
> * Expire published xmin for read-only and idle transactions
>
> http://archives.postgresql.org/pgsql-hackers/2007-09/msg00343.php
|
|
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.
|
|
>
> * Consider a special data type for regular expressions
>
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php
|
|
* 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
|
|
* Consider a simplified API for full text searches
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg01067.php
|
|
>
> o Convert MSVC build system to remove most batch files
>
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00961.php
|
|
* Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
> http://archives.postgresql.org/pgsql-performance/2007-08/msg00289.php
|
|
> o Diagnose problem where shared memory can sometimes not be
> attached by postmaster children
>
> http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php
>
|
|
>
> * Remove use of MAKE_PTR and MAKE_OFFSET macros
>
> http://archives.postgresql.org/pgsql-general/2007-08/msg01510.php
|
|
>
> * Add array_accum() and array_to_set() functions for arrays
>
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00464.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-08/msg00307.php
|
|
>
> * 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
|
|
>
> * Consider simplifying how memory context resets handle child contexts
>
> http://archives.postgresql.org/pgsql-patches/2007-08/msg00067.php
|