From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Trout <threshar(at)threshar(dot)is-a-geek(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Function returns wrong data after datatype change |
Date: | 2007-01-24 19:04:23 |
Message-ID: | 4050.1169665463@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Jeff Trout <threshar(at)threshar(dot)is-a-geek(dot)com> writes:
> On Jan 24, 2007, at 12:24 PM, Tom Lane wrote:
>> 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.
> The really curious thing is that it does't complain when restoring
> from the dump - or are those error supressed?
Yeah, pg_dump sets check_function_bodies = off. It more or less has to
because it can't understand the function contents well enough to know
what objects would need to be loaded first (and in fact there might be
no solution --- consider two mutually recursive functions ...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Maciej Babinski | 2007-01-24 19:14:50 | BUG #2930: Hash join abyssmal with many null fields. |
Previous Message | Jeff Trout | 2007-01-24 18:59:21 | Re: Function returns wrong data after datatype change |