| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CLUSTER ALL syntax |
| Date: | 2002-11-18 01:36:04 |
| Message-ID: | 21265.1037583364@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> What I don't understand is what are the parameters in the
> ReindexDatabase function for. For example, the boolean all is always
> false in tcop/utility.c (and there are no other places that the function
> is called). Also, the database name is checked to be equal to a
> "constant" value, the database name that the standalone backend is
> connected to. Why are those useful?
Well, passing all=true would implement REINDEX ALL ...
As for the database name, we could perhaps change the syntax to just
REINDEX DATABASE; not sure if it's worth the trouble.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-11-18 01:50:17 | FW: PostgreSQL 7.3 Platform Testing |
| Previous Message | Alvaro Herrera | 2002-11-18 01:31:40 | Re: CLUSTER ALL syntax |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2002-11-18 01:41:27 | documentation fix |
| Previous Message | Alvaro Herrera | 2002-11-18 01:31:40 | Re: CLUSTER ALL syntax |