Re: Suggested TODO: allow ALTERing of typemods without heap/index rebuild

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Suggested TODO: allow ALTERing of typemods without heap/index rebuild
Date: 2009-06-01 22:39:05
Message-ID: 25609.1243895945@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> yeah, you're right .. that would give us a short list of conversions
> which don't require a rewrite. However, as Tom points out, that
> doesn't mean that they might not need a reindex (as well as OID, there's
> also XML).

Um. I had actually forgotten about the reindexing point, but yup that
is a stumbling block to any "no work" conversions. It might be best to
only handle cases where the column's base type is not changing, so that
we don't have any index semantics changes happening. I think we could
still handle the varchar->text case (since they share index opclasses)
but that could be a hardwired special case.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-01 22:52:53 Re: Suggested TODO: allow ALTERing of typemods without heap/index rebuild
Previous Message Kevin Grittner 2009-06-01 22:32:00 Re: User-facing aspects of serializable transactions