Re: ALTER TYPE 3: add facility to identify further no-work cases

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 15:42:14
Message-ID: AANLkTimuCiwhZ9n8av-vw7zDig+oeJcd0FdmfooMHRAc@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 27, 2011 at 9:46 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> OK. I was thinking that instead moving this into
>> eval_const_expressions(), we just make the logic in
>> find_coercion_pathway() call the "exemptor" function (or whatever we
>> call it) right around here:
>
> No, no, no, no.  Didn't you read yesterday's discussion?  parse_coerce
> is entirely the wrong place for this.

I not only read it, I participated in it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-01-27 15:44:32 Re: SSI patch version 14
Previous Message Tom Lane 2011-01-27 15:24:19 Re: make -j2 error in ecpg/pgtypeslib in current GIT