TodoDone91
From PostgreSQL wiki
Jump to navigationJump to searchThis list contains all PostgreSQL bugs and features requests that were solved in 9.1. There is a Todo page too for bugs and features that are still not solved.
Administration
- [D]
Allow auto-selection of partitioned tables for min/max() operations
- There was a patch on -hackers from July 2009, but it has not been merged: MIN/MAX optimization for partitioned table
- [D]
Allow the client to authenticate the server in a Unix-domain socket connection, e.g., using SO_PEERCRED
Configuration files
- [D]
Allow pg_hba.conf to specify host names along with IP addresses
- Host name lookup could occur when the postmaster reads the pg_hba.conf file, or when the backend starts. Another solution would be to reverse lookup the connection IP and check that hostname against the host names in pg_hba.conf. We could also then check that the host name maps to the IP address.
Statistics Collector
- [D]
Allow the clearing of cluster-level statistics
- Resetting cluster-wide statistics
- pg_stat_reset_shared('bgwriter') (9.0) now handles the pg_stat_bgwriter subset of this
Point-In-Time Recovery (PITR)
Standby server mode
- [D]
Add capability to take and send a base backup over the streaming replication connection, making it possible to initialize a new standby server from a running primary server without a WAL archive or other access to the primary server.
Data Types
MONEY Data Type
XML
Functions
Multi-Language Support
- [D]
Allow more fine-grained collation selection
-
Right now the collation is fixed at database creation time.
- Re: Patch for collation using ICU
- FW: Win32 unicode vs ICU
- Re: FW: Win32 unicode vs ICU
- Proof of concept COLLATE support with patch
- For review: Initial support for COLLATE
- Proposed COLLATE implementation
- TODO item: locale per database patch (new iteration)
- Re: FW: Win32 unicode vs ICU
- Re: Fixed length data types issue
- [WIP] collation support revisited (phase 1)
- Todo:Collate
- Todo:ICU
- WIP patch: Collation support
- Re: WIP patch: Collation support
- PGDay.it collation discussion notes
- Unicode collation algorithm
- [D]
Set client encoding based on the client operating system encoding
- Currently client_encoding is set in postgresql.conf, which defaults to the server encoding.
SQL Commands
- [D]
Fix TRUNCATE ... RESTART IDENTITY so its effect on sequences is rolled back on transaction abort
- [D]
Enable standard_conforming_strings by default
- When this is done, backslash-quote should be prohibited in non-E'' strings because of possible confusion over how such strings treat backslashes. Basically, '' is always safe for a literal single quote, while \' might or might not be based on the backslash handling rules.
- [D]
Add support for functional dependencies
- This would allow omitting GROUP BY columns when grouping by the primary key.
CREATE
ALTER
- [D]
Don't require table rewrite on ALTER TABLE ... ALTER COLUMN TYPE, when the old and new data types are binary compatible
CLUSTER
Server-Side Languages
PL/Python
Clients
psql
libpq
Indexes
GIN
Locking
Write-Ahead Log
- [D]
Allow WAL logging to be turned off for a table, but the table might be dropped or truncated during crash recovery
- Allow tables to bypass WAL writes and just fsync() dirty pages on commit. This should be implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using non-default logging should not use referential integrity with default-logging tables. A table without dirty buffers during a crash could perhaps avoid the drop/truncate.
Optimizer / Executor
Hashing
Source Code
/contrib/pg_upgrade