From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Merlin Moncure <merlin(dot)moncure(at)rcsonline(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE TODO items |
Date: | 2004-05-06 16:56:39 |
Message-ID: | 200405061656.i46Gud810900@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > At a minimum, we should indicate we dropped the cluster on the index.
>
> [shrug] If you're going to make me do that, I might as well reinstall
> the bit on the new index. The code's problem is it doesn't know that
> any of the indexes it dropped were clustered, and finding that out is
> 90% of the issue.
>
> What I want to know is whether it is sensible to mark the revised index
> as clustered, given that its semantics might be significantly different
> from before.
OK, yea, just leave the bit. We can add documentation that they should
run CLUSTER again if they radically modified the column as part of the
ALTER>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-05-06 16:58:08 | Re: PostgreSQL pre-fork speedup |
Previous Message | Thomas Swan | 2004-05-06 16:54:52 | Re: PostgreSQL pre-fork speedup |