Plans for 8.2?

From: "Mikael Carneholm" <Mikael(dot)Carneholm(at)WirelessCar(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Plans for 8.2?
Date: 2006-01-12 14:52:49
Message-ID: 7F10D26ECFA1FB458B89C5B4B0D72C2B0A022D@sesrv12.wirelesscar.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I wonder what features other users would like to see in the next version? (8.2) The features I'd (very much) would like to see implemented are:

- "Top offender statistics"
In other DBMS:es there are functions that allow you to turn on a sort of monitoring that can tell you, for a period of time:
1) which queries that generated the highest I/O
2) which queries that took the longest time to execute
3) percentage of total time spent on I/O wait, CPU time, etc

Statistics like these can be very helpful when it comes to identifying application bottlenecks / areas for improvements.

- Materialized views
What's the status on the matview project?

- "Built in" failover/clustering
There are lots of projects supplying replication/failover/clustering functionality (Slony-I, pgcluster, pgpool etc), but these are "non-official" in that they do not provide out-of-the box functionality (ie not bundled with a default Pg install)

- Analytic/window functions
In DBMS:es such as Oracle, there's rank(), dense_rank(), lag(), lead() etc. These functions may(?) be possible to implement using existing/new aggregates.

Comments?

/Mikael

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kai Hessing 2006-01-12 14:55:40 Problem with restoring database from 7.3.1 to 8.0.1
Previous Message SunWuKung 2006-01-12 14:45:41 Re: select into multiple variables