| 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: ALTER TYPE 3: add facility to identify further no-work cases |
| Date: | 2011-01-27 01:11:35 |
| Message-ID: | AANLkTimX3GGw1h9YJmxjXZJtfBPNHJYhKedX9-5N_V-O@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 26, 2011 at 6:06 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Well, I guess my thought was that we what we were doing is extending
>> the coercion system to be able to make decisions based on both type
>> OID and typemod.
>
> Well, that's an interesting thought, but the proposal at hand is far
> more limited than that --- it's only an optimization that can be applied
> in limited situations. If we want to do something like what you're
> suggesting here, it's not going to get done for 9.1.
Eh, why is this not entirely straightforward? *scratches head*
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-01-27 01:12:53 | Re: ALTER TYPE 3: add facility to identify further no-work cases |
| Previous Message | Tom Lane | 2011-01-27 01:08:31 | Re: new compiler warnings |