From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [GENERAL] Idea for the statistics collector |
Date: | 2002-06-24 14:39:03 |
Message-ID: | 200206241439.g5OEd3M23053@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Christopher Kings-Lynne wrote:
> I was thinking of writing a command line tool like 'pgtune' that looks at
> the stats views and will generate SQL code for, or do automatically the
> following:
>
> * Dropping indices that are never used
> * Creating appropriate indices to avoid large, expensive sequential scans.
>
> This would put us in the 'mysql makes my indices for me by magic' league -
> but would be far more powerful and flexible. How to do multikey indices is
> beyond me tho.
This is a great idea. I have been wanting to do something like this
myself but probably won't get the time.
Does MySQL really make indexes by magic?
Also, I had to look up the contraction for "will not" because I always
get that confused (won't). I just found a web page on it:
http://www.straightdope.com/mailbag/mwont.html
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-24 14:42:47 | Re: Table name length (maximum identifier length) |
Previous Message | Jeff MacDonald | 2002-06-24 14:21:24 | functions for date parsing. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-06-24 15:34:11 | Re: [GENERAL] Idea for the statistics collector |
Previous Message | Dave Page | 2002-06-24 14:15:41 | Re: pgadmin.postgresql.org displaying errors |