Re: Re: Use int8 for int4/int2 aggregate accumulators? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: Use int8 for int4/int2 aggregate accumulators?
Date
Msg-id 17602.997801229@sss.pgh.pa.us
Whole thread Raw
In response to Use int8 for int4/int2 aggregate accumulators?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: Use int8 for int4/int2 aggregate accumulators?
Re: Re: Use int8 for int4/int2 aggregate accumulators?
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
>> create function rtest_viewfunc1(int4) returns int4 as
>> 'select count(*) from rtest_view2 where a = $1'
>> language 'sql';
>> + ERROR:  return type mismatch in function: declared to return integer, returns bigint

> Maybe instead of testing for strict equality of the types, test for
> compatibility.

We could try to force-convert the result of an SQL function to the right
thing, I suppose, but I'm worried that that might mask programmer errors
more than it helps.

On the other hand, the equivalent forced conversion happens already in
plpgsql functions; it's only SQL-language functions that are so picky.
Maybe your idea is good.  Anyone else have an opinion?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Rename config.h to pg_config.h?
Next
From: Liam Stewart
Date:
Subject: RFC: Inserting multiple values via INSERT ... VALUES ...