Re: ALTER TYPE 3: add facility to identify further no-work cases - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ALTER TYPE 3: add facility to identify further no-work cases
Date
Msg-id 15364.1296146101@sss.pgh.pa.us
Whole thread Raw
In response to Re: ALTER TYPE 3: add facility to identify further no-work cases  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: ALTER TYPE 3: add facility to identify further no-work cases  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> Is it not OK for me to have a different idea about which way to go
> with something than you do?

Well, in this case I firmly believe that you're mistaken.

> My personal view is that we ought to try to be increasing the number
> of places where type modifiers behave like they're really part of the
> type, rather than being an afterthought that we deal with when
> convenient and otherwise ignore.

And this argument is 100% irrelevant to the problem.  The problem is
that you want to put an optimization into the wrong phase of processing.
That is going to hurt us, tomorrow if not today, and it has got *no*
redeeming social value in terms of beng more flexible about what typmods
are or how "well integrated" they are.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.
Next
From: Andrew Dunstan
Date:
Subject: Re: Caution when removing git branches