Re: ALTER TABLE TODO items

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(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:51:59
Message-ID: 1293.1083862319@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Swan 2004-05-06 16:54:52 Re: PostgreSQL pre-fork speedup
Previous Message sdv mailer 2004-05-06 16:48:25 Re: PostgreSQL pre-fork speedup