Mikael Carneholm wrote:
In terms of statistics we do have statistics and exhaustive logging that
can provide you with all of that information. Is there something
specific that
the information already provided really doesn't give you?
Can you give an example query for "list all queries executed since 12.00 AM, order by block_reads desc"? What I'm aiming for
is the ability to turn "measuring" on, regression test my application, turn "measuring" off again, and list the most offensive queries executed during the regression test. I know of at least one other DBMS that is capable of this...won't mention which one :)
You can use timestamp and one of the duration logging options for this.
"Built In" Failover/Clustering
This won't happen. The community stance, which is a good one is that no
single replication solutions fits everyone's needs and therefore we rely
out the outside
sources. Slony-I, Mammoth Replicator and pgpool being the most popular.
Too bad - I think that will keep a lot of potential users from evaluating Pg as a serious alternative. Good or bad, decide for yourself :)
Although that is one thought, the project is fairly good at supporting
the various solutions in terms of where and how they exist.
Most people that are going to seriously use postgresql are going to do
the very easy research to get the right answer they need.
Get coding man! :) We would love to have them.
Sure - as soon as I'm finished with my 4 other hobby projects. Too many ideas, too little time.. *sigh* :/
Perhaps you should drop the other 4 and concentrate on the important one ;)
Joshua D. Drake
/Mikael
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
--
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
