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

From Robert Haas
Subject Re: ALTER TYPE 3: add facility to identify further no-work cases
Date
Msg-id AANLkTimuCiwhZ9n8av-vw7zDig+oeJcd0FdmfooMHRAc@mail.gmail.com
Whole thread Raw
In response to Re: ALTER TYPE 3: add facility to identify further no-work cases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ALTER TYPE 3: add facility to identify further no-work cases  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Thu, Jan 27, 2011 at 9:46 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: make -j2 error in ecpg/pgtypeslib in current GIT
Next
From: "Kevin Grittner"
Date:
Subject: Re: SSI patch version 14