From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Auto-indexing |
Date: | 2001-02-07 03:14:17 |
Message-ID: | 200102070314.WAA04241@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Probably both, but if it's done there should be options to:
>
> .) disable it completely or by table/database or even threshold or
> disk free parameters (indicies can be large)
> .) log any auto-created databases to inform the DBA.
> .) if disabled optionally log when it would have created an index on
> the fly. (suggest an index)
> .) expire old and unused auto-created indecies.
>
> Generally Postgresql assumes the user knows what he's doing, but
> it couldn't hurt too much to provide an option to have it assist
> the user.
I want to implement a SET PERFORMANCE_TIPS, hopefully for 7.2:
* Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
ANALYZE, and CLUSTER
I think suggesting items to the adminstrator is the way to go.
--
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 | JP Sugarbroad | 2001-02-07 04:27:49 | CORBA? |
Previous Message | Alfred Perlstein | 2001-02-07 02:36:16 | Re: Auto-indexing |