| Age | Commit message (Collapse) | Author |
|
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
|
|
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00082.php
|
|
* Consider increasing NUM_CLOG_BUFFERS
> http://archives.postgresql.org/pgsql-performance/2007-08/msg00024.php
|
|
* Consider increasing NUM_CLOG_BUFFERS
>
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00030.php
>
|
|
o Allow COPY in CSV mode to control whether a quoted zero-length
string is treated as NULL
Currently this is always treated as a zero-length string,
which generates an error when loading into an integer column
|
|
>
> o Allow COPY in CSV mode to control whether "" is treated as NULL
>
> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00905.php
|
|
>
> o Improve logic of determining if an identifier is a a
> variable or column name
>
> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00436.php
|
|
>
> * Add automated check for invalid C++ source code constructs
>
> http://archives.postgresql.org/pgsql-patches/2007-07/msg00056.php
|
|
> * Research use of signals and sleep wake ups
>
> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00003.php
|
|
* Test to see if calling PreallocXlogFiles() from the background writer
will help with WAL segment creation latency
http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php
|
|
> * Consider adding buffers the background writer finds reusable to the
> free list
>
> * Consider wither increasing BM_MAX_USAGE_COUNT improves performance
>
> http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php
|
|
* Reduce storage space for small NUMERICs
> http://archives.postgresql.org/pgsql-hackers/2007-06/msg00715.php
|
|
> o Consider normalizing fractions in postgresql.conf, perhaps
> using '%'
>
> http://archives.postgresql.org/pgsql-hackers/2007-06/msg00550.php
|
|
> * Consider sorting writes during checkpoint
>
> http://archives.postgresql.org/pgsql-hackers/2007-06/msg00541.php
|
|
>
> * Prefix command-line utilities like createuser with 'pg_'
>
> http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php
|
|
>
> * Change memory allocation for multi-byte functions so memory is
> allocated inside conversion functions
>
> Currently we preallocate memory based on worst-case usage.
|
|
* Consider increasing the number of default statistics target, and
reduce statistics target overhead
Also consider having a larger statistics target for indexed columns
and expression indexes
<
> http://archives.postgresql.org/pgsql-general/2007-06/msg00542.php
|
|
* Consider increasing the number of default statistics target, and
reduce statistics target overhead
Also consider having a larger statistics target for indexed columns
and expression indexes
> http://archives.postgresql.org/pgsql-general/2007-05/msg01228.php
>
|
|
>
> * Consider increasing the number of default statistics target, and
> reduce statistics target overhead
>
> Also consider having a larger statistics target for indexed columns
> and expression indexes
|
|
>
> * Consider using a hash for joining to a large IN (VALUES ...) list
>
> http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php
|
|
>
> * Consider a more compact data representation for dead tuples
>
> http://archives.postgresql.org/pgsql-patches/2007-05/msg00143.php
|
|
* 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/2007-05/msg00773.php
|
|
>
> * Add temporal versions of generate_series()
>
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg01180.php
|
|
o Review handling of MOVE and FETCH
http://archives.postgresql.org/pgsql-patches/2007-04/msg00527.php
|
|
> o Prevent pg_dump/pg_restore from being affected by
> statement_timeout
>
> Using psql to restore a pg_dump dump is also affected.
|
|
+ Setting <varname>statement_timeout</> in
+ <filename>postgresql.conf</> is not recommended because it
+ affects all sessions.
Backpatch to 8.3.X.
|
|
> * Allow statistics last vacuum/analyze execution times to be displayed
> without requiring stats_row_level to be enabled
|
|
|
|
<
< o Set up autovacuum to ignore statement_timeout set in
< postgresql.conf
<
< http://archives.postgresql.org/pgsql-hackers/2007-03/msg01753.php
|
|
>
> * Consider adding buffers the BGW finds reusable to the free list
>
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
>
> * Automatically tune bgwriter_delay based on activity rather then using a
> fixed interval
>
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php
|
|
because it affects all sessions, including autovacuum.
|
|
>
> o Set up autovacuum to ignore statement_timeout set in
> postgresql.conf
>
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01753.php
|
|
* Optimize referential integrity checks
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00744.php
|
|
* Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00218.php
|
|
than dividing them into 1GB segments as has been our longtime practice. This
requires working support for large files in the operating system; at least for
the time being, it won't be the default.
Zdenek Kotala
|
|
>
> * Consider increasing the minimum allowed number of shared buffers
>
> http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php
>
|
|
variables to it. More need to be converted, but I wanted to get this in
before it conflicts with too much...
Other than just centralising the text-to-int conversion for parameters,
this allows the pg_settings view to contain a list of available options
and allows an error hint to show what values are allowed.
|
|
-1 to 1, not 0 to 1. The actual behavior for values within this range
does not change. Kris Jurka
|
|
NOTICE-grade messages are not logged by default. Per pgsql-hackers
discussion back on 21-Nov-2007.
|