| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Identifying no-op length coercions |
| Date: | 2011-05-23 18:11:39 |
| Message-ID: | BANLkTimnAMzkgTJS9jW_vk7L9kDuw_2a+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 23, 2011 at 1:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Maybe. But casts would be the least of our concerns if we were trying
> to change the column type. Changing typmod doesn't affect the set of
> operations that could be applied to a column, whereas changing type
> surely does.
OK, this is the crucial point I was missing. Sorry for being a bit
fuzzy-headed about this.
My mental model of our type system, or of what a type system ought to
do, just doesn't match the type system we've got.
So let's do it the way you proposed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-05-23 18:26:15 | Re: sepgsql: fix relkind handling on foreign tables |
| Previous Message | Alexander Korotkov | 2011-05-23 17:54:14 | Re: WIP: collect frequency statistics for arrays |