| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
| |
* SMP scalability improvements
> http://archives.postgresql.org/pgsql-hackers/2007-09/msg00206.php
|
|
|
|
|
|
| |
* SMP scalability improvements
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php
|
|
|
|
|
|
|
| |
>
> * SMP scalability improvements
>
> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00439.php
|
|
|
|
|
|
|
|
|
| |
* Allow statistics last vacuum/analyze execution times to be displayed
without requiring stats_row_level to be enabled
>
> http://archives.postgresql.org/pgsql-docs/2007-04/msg00028.php
>
|
|
|
|
|
|
|
| |
> * Improve reporting of UNION type mismatches
>
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00944.php
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00597.php
|
|
|
|
|
|
|
| |
< o Allow pre/data/post files when dumping a single object, for
< performance reasons
> o Allow pre/data/post files when schema and data are dumped
> separately, for performance reasons
|
|
|
|
|
| |
< o Support pgxs
> o Support pgxs when using MSVC
|
|
|
|
| |
> http://archives.postgresql.org/pgsql-patches/2008-02/msg00176.php
|
|
|
|
|
|
|
| |
>
> * Avoid tuple some tuple copying in sort routines
>
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php
|
|
|
|
|
|
|
| |
>
> * Sort large UPDATE/DELETEs so it is done in heap order
>
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg01119.php
|
|
|
|
|
|
|
|
|
| |
* 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-patches/2008-01/msg00170.php
|
|
|
|
|
|
|
| |
<
< * Avoid tuple some tuple copying in sort routines
<
< http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php
|
|
|
|
|
|
|
|
| |
> o Allow pre/data/post files when dumping a single object, for
> performance reasons
>
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg00205.php
>
|
|
|
|
|
|
|
|
| |
>
> o Fix MSVC NLS support, like for to_char()
>
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg00485.php
> http://archives.postgresql.org/pgsql-patches/2008-02/msg00038.php
|
|
|
|
|
|
|
|
| |
>
> * Improve WAL concurrency by increasing lock granularity
>
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg00556.php
>
|
|
|
|
|
| |
>
> o Support pgxs
|
|
|
|
|
|
|
| |
>
> * Avoid tuple some tuple copying in sort routines
>
> http://archives.postgresql.org/pgsql-hackers/2008-02/msg01206.php
|
|
|
|
|
|
| |
o Add checks to prevent a CREATE RULE views on inherited tables
> http://archives.postgresql.org/pgsql-general/2008-03/msg00077.php
|
|
|
|
|
|
|
| |
>
> o Add checks to prevent a CREATE RULE views on inherited tables
>
> http://archives.postgresql.org/pgsql-general/2008-02/msg01420.php
|
|
|
|
|
|
| |
* Simplify ability to create partitioned tables
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00387.php
|
|
|
|
|
|
| |
* Simplify ability to create partitioned tables
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00248.php
|
|
|
|
|
|
|
| |
>
> * Improve performance of shared invalidation queue for multiple CPUs
>
> http://archives.postgresql.org/pgsql-performance/2008-01/msg00023.php
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Simplify ability to create partitioned tables
This would allow creation of partitioned tables without requiring
creation of triggers or rules for INSERT/UPDATE/DELETE, and constraints
for rapid partition selection. Options could include range and hash
partition selection.
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00028.php
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00413.php
|
|
|
|
|
|
|
|
| |
>
> * Convert single quotes to apostrophes in the PDF documentation
>
> http://archives.postgresql.org/pgsql-docs/2007-12/msg00059.php
>
|
|
|
|
|
|
|
| |
>
> * 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
>
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
* 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
|