something like http://www.oracle.com/technology/products/bi/db/11g/pdf/partitioning-11g-whitepaper.pdf

developer feature for clustering my scripts into logical units.

If yes, what specific functionality is needed?

Table placed only in RAM, visibility for all

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.

Sometimes you need to insert a column on a specific postion to group related information more visible.
Please give us the possibility to rearange columns or insert columns before/after existing ones without a drop and recreate

Needed wildcards:
* - stands for a string of characters of any length
? - stands for zero or one character
# - stands for exactly one character.
They can appear any times in any part of word. Thanks.

At present there is only one way of backing up a big databases in PG: full hot cluster backup with archived WAL sets. This method is insufficient in case of limited storage space and low time recovery. PG needs native incremental and differential block level backups for more scalability of database. There is some 3rd party efforts on that but definitely need native facility tools.

Allow to update multiple field in a table with a subselect

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.

Add this feature for implementing logging in procedure/function.
see http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14261/autonotransaction_pragma.htm

Internal time service which would be capable call stored procedure in time or periodicaly. Service can have properties similar to cron's.

Sample:

do
$$
begin
insert into test_table(id, name) values(:ID, :Name);
end
$$;

Having natively multi-master replication.

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 constraints currently accept this clause. All other constraint types are not deferrable." - http://www.postgresql.org/docs/8.4/interactive/sql-createtable.html I request deferrable check constraints!

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 some data is in a database and some is in files...

It happens way to often when users come and ask to recover some “lost” data from backups. It would be of a great benefit if one could recover only a single tablespace from the filesystem-based backups.

Right now one should recover a cluster in full, which is overkill quite often.

Cluster server means two or more servers share the same db disks in the san and accross network also share their memory like in oracle RAC.
This feature would be very effective in postgresqş for high availibility

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. Thanks for this feedback tool :)