Re: Function returns wrong data after datatype change - Mailing list pgsql-bugs

From Jeff Trout
Subject Re: Function returns wrong data after datatype change
Date
Msg-id B14F6CC6-1DA7-4C79-BE99-184850F19162@torgo.978.org
Whole thread Raw
In response to Re: Function returns wrong data after datatype change  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Function returns wrong data after datatype change  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Jan 24, 2007, at 12:24 PM, Tom Lane wrote:

> Jeff Trout <threshar@threshar.is-a-geek.com> writes:
>> I just ran across this, and I do not think it is entirely a PG bug or
>> even something that the backend can detect and handle.
>> The problem stems from swapping a table definition from under a
>> function.
>
> Hmm.  This should yield an error (SQL function not returning the type
> it claims to), and we probably should plug the hole by invoking
> check_sql_fn_retval every time not just at creation.
>
> I thought you were about to complain about plpgsql, which has much
> worse
> problems due to plan caching...

The really curious thing is that it does't complain when restoring
from the dump - or are those error supressed?
--
Jeff Trout <jeff@jefftrout.com>
http://www.dellsmartexitin.com/
http://www.stuarthamm.net/

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Function returns wrong data after datatype change
Next
From: Tom Lane
Date:
Subject: Re: Function returns wrong data after datatype change