| From: | Alvaro Herrera <alvherre(at)atentus(dot)com> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: CLUSTER and indisclustered | 
| Date: | 2002-08-09 00:57:23 | 
| Message-ID: | Pine.LNX.4.44.0208082055020.14590-100000@cm-lcon1-46-187.cm.vtr.net | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Tom Lane dijo:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom, should we be updating that flag after we CLUSTER instead of
> > requiring an ANALYZE after the CLUSTER?
> 
> Could do that I suppose, but I'm not super-excited about it.  ANALYZE is
> quite cheap these days (especially in comparison to CLUSTER ;-)).  I'd
> settle for a note in the CLUSTER docs that recommends a subsequent
> ANALYZE --- this seems no different from recommending ANALYZE after bulk
> data load or other major update of a table.
What if I [try to] extend the grammar to support an additional ANALYZE
in CLUSTER, so that it analyzes the table automatically? Say
CLUSTER <index> ON <table> [ANALYZE];
Or maybe just do an analyze of the table automatically after the
CLUSTERing.
What does everybody think?
-- 
Alvaro Herrera (<alvherre[a]atentus.com>)
"Para tener mas hay que desear menos"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2002-08-09 01:04:03 | Re: CLUSTER and indisclustered | 
| Previous Message | Bruce Momjian | 2002-08-08 23:53:04 | Re: Another python patch -- minor |