PostgreSQL 9.1 Open Items

== Project Planning ==
See the PostgreSQL 9.1 Development Plan.
== Meta-Issues ==
* standard_conforming_strings — readiness of drivers and applications
* Review "Long Term" list of items from PostgreSQL 9.0 Open Items
== Open Issues ==
=== Blockers for Next Beta / RC ===
=== Not Blockers for Next Beta / RC ===
* 
== Resolved Issues ==
=== Issues Resolved Prior to RC1 ===
* 
* 
** 
* 
* 
** 
** 
* 
** 
=== Issues Resolved Prior to Beta3 ===
* 
* ill-conceived grammar for NOT VALID constraints
* 
** 
** 
* 
* 
** 
* 
** 
* 
** 
* 
* 
* 
=== Issues Resolved Prior to Beta2 ===
* 
* 
* vacuum sometimes fails to update relpages/reltuples
* 
* 
* 
* 
* 
** (Problems found with patch, discussion and modifications in progress.)
* 
* 
* 
=== Issues Resolved Prior to Beta1 ===
* wal_buffers = -1 causes spurious chatter on reload
* is there a safeguard to prevent recovery from pausing before consistency is reached?
* 
** 
* 
* 
* replication/README needs to be updated
* backend wrongly waits for sync rep even though max_wal_senders = 0
* reload of the configuration file should not cause the server to end unexpectedly
* Fix ecpg preprocessor regression
* 
* 
* pause_at_recovery_target needs to be added in recovery.conf.sample
* 
* 
* consider renaming ident to peer authentication on local connections
* serious problem by multiple backups
* FK constraints "NOT VALID" by default
* sync rep very slow when fsync=off on standby
* No longer need to check synchronous_standby_names and max_wal_senders at startup
* 
** rhaas says: It's not clear there's an action item here, so moving to resolved. Feel free to move back with more details.
* either remove write_location completely, or revert the change that broke it
** original report of problem with write_location (but the other issues in that email are now fixed)
** possible patch
* 
* 
* 
** not done, would break things
* fix attinhcount tracking
* SSI: SIReadLock lines in pg_locks don't show pid
** questions have been raised whether pid should be suppressed after connection closes or even maybe after transaction completion
* synchronous_commit and synchronous_replication
* 
* comments on SQL/MED objects
** rhaas says: proposed patch
** rhaas says: thom brown points out that I forgot USER MAPPINGs
** fixing user mappings opens unduly large can of worms
* SSI: assertion failure on marking conflict-in due to race condition
** existing patch to recheck after trading shared LW locks for exclusive should fix
* keywords table needs updating
* SSI: clumsy error handling results in generic message rather than more specific message with hint
* SSI: disable optimization when in subtransaction
* SSI: LOG message about SLRU wrap-around
* sync rep and fast shutdown
** rhaas says: no easy resolution, i guess we'll leave this alone for now?
* SSI: three different HTABs contend for shared memory in a free-for-all
** Heikki proposes "We'll need to teach dynahash not to allocate any more entries after the preallocation. A new HASH_NO_GROW flag to hash_create() seems like a suitable interface."
** Alternatively, we could just use an initial allocation which matches the maximum entries, to ensure that all HTABs can allocate at least the configured maximum. (There's an existing patch for that.)
** I committed a patch to add the new flag to hash_create() - Heikki
* SSI: failure to clean up some SLRU-summarized locks
** existing patch to properly set commitSeqNo on the offending locks should fix
* 
* 
* assorted collation issues
** almost there...
* pl/python traceback fix
* gin indexes don't get used unless you vacuum
* SSI: High-contention UPDATE load on RAM disk database slows non-serializable transactions by a fraction of a percent
** Or speeds it up by a fraction of a percent. Either way it's too close to tease out from the noise easily.
** As insurance against any performance hit in extreme high contention loads, it might be worthwhile to do a quick return (without taking any locks) if no serializable transactions are active.
* SSI: UPDATE setting a TOASTed value is broken, regardless of transaction isolation level
** proposed patch
* foreign table permissions issues
* CREATE TABLE IF NOT EXISTS doesn't work
* 
** 
Category:PostgreSQL 9.1
Category:Open_Items