Do you have a feature request or a good idea for how to improve PostgreSQL? You can use this forum to let us know. (This is an experiment; see http://www.postgresql.org/support/ for more offical ways to contact the PostgreSQL project. Please report actual bugs and conduct development discussions there.)
-
144 votes
Materialized Views
Materialized views will boost performance for every web application and not only that is must for our era.
-
100 votes
Synchronous replication
Send WAL replication information to the slave without delay, so the data is known committed on the slave before the master reports the command or transaction complete to its client.
Status: started -
90 votes
parallel query option
Rationale:
We are running a BI w/mid-size data warehouse. PostgreSQL scales reasonably well for the BI app - i.e. when there is enough users running dashboards, ad-hoc queries, etc the server is as busy as expected.
HOWEVER when running the ETL overnight most of the processors are iddle - BECAUS... more -
87 votes
Index-only scans
For performance reasons (reduced-IO) it would be good for PostgreSQL to obtain index-only scans.
Status: started -
79 votes
MERGE/UPSERT/REPLACE
Insert, if unique constraint violation then update; or update, if not found then insert.
-
64 votes
Better administration and monitoring tools
If yes, what specific functionality is needed?
-
52 votes
Allow in place upgrades (without dump/restore)
Currently when upgrading from one major version to another a dump/restore is required. The work that has started with pg_migrator should be merged into the main trunk. The installers should offer an upgrade of the existing data directory during installation (instead of running initdb)
Status: started -
52 votes
Oracle-style table partitioning
something like http://www.oracle.com/technology/products/bi/db/11g/pdf/partitioning-11g-whitepaper.pdf
Status: started -
45 votes
pl/sql packages (like Oracle)
developer feature for clustering my scripts into logical units.
-
36 votes
support of ddl and logon triggers
the support of ddl and logon triggers would be great for monitoring and countionous validating a database.
-
26 votes
SQL/MED datalinks
Implement datalink datatype, as specified by SQL/MED.
Implement additional operations on datalinks, such as reading and writing contents of files pointed to by datalinks.
This could be very useful for content management, workflow applications, etc... Right now this is rather clumsy, because so... more
-
26 votes
Allow update table a,b,c = (select x,y,z )
Allow to update multiple field in a table with a subselect
Status: planned -
18 votes
Add DEFERRED option to check constraints
To improve data consistency foreign keys and simple row based checks isn't always enough. Sometimes you would like to write a stored procedure that does more advanced checks. This is fine until you would like to make that advanced constraint deferred which is not possible. "Only foreign key ... more
Status: planned -
17 votes
Per-column locale and collation support
You can currently define locale and collation per database. This should be settable for each column individually.
Status: planned -
16 votes
case insensitive
Allow db columns in UTF-8 databases to be case insensitive to sorting / selecting. From what I understand this is not possible. I've looked everywhere. It is possible in lots of other DBs from my experience and would be very useful. There is UPPER but that would reduce performance.
Status: plannedThis will likely be implemented as part of customizable, per-column locale settings.
-
14 votes
CREATE ASSERTION, or CHECK constraints with subselects
With tables that are not updated frequently, and when I'm fully aware of the performance implications, I'd like to have as many data integrity constraints as possible. I'm fully aware it can be burdensome to implement, but I cannot think of anything else to improve my current Postgres experience.... more
-
14 votes
-
13 votes
Query progress, reported by percentage in pg_stat_activity.
This wouldn't need to be perfectly accurate or linear, but would help admins know how far along a long running query was in executing its plan. Even better would be a way to add to EXPLAIN output what part of the plan was executing and its percentage progress.
Status: planned -
13 votes
add primary key to view definition
Right now Postgresql views cannot have a primary key constraint. Oracle views can. Certain frameworks like sql2java require this to work. So without this the migration to Postgresql ist not possible in some projects.
