Jeff Davis <pg...@j-davis.com> writes:
> Aha -- I think I see the problem you're having: if you try to rewrite
> one of the columns contained in the exclusion constraint, you get that
> error:
It fails for me regardless of which column is actually modified.
It could be this is a consequence of other changes I've been making,
but given the way ALTER TABLE works it's hard to see why the specific
column being modified would matter. Anything that forces a table
rewrite would lead to running through this code path.
I don't really agree with your argument that it's okay to reject the
case of altering the underlying column type, anyhow. There's enough
commonality of operator names that it's sensible to try to preserve
the constraint across a change. Consider replacing a circle with a
polygon, say. A no-overlap restriction is still sensible.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
