Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 27452633048 for ; Sun, 7 Mar 2010 19:09:19 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 70281-08 for ; Sun, 7 Mar 2010 23:09:01 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from glacier.frostconsultingllc.com (glacier.frostconsultingllc.com [69.36.227.170]) by mail.postgresql.org (Postfix) with ESMTP id 8324D632FEA for ; Sun, 7 Mar 2010 19:09:07 -0400 (AST) Received: from adsl-63-195-55-98.dsl.snfc21.pacbell.net ([63.195.55.98] helo=Sidney-Stratton.local) by glacier.frostconsultingllc.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.69) (envelope-from ) id 1NoPaq-0006Ms-8v; Sun, 07 Mar 2010 15:09:06 -0800 Message-ID: <4B94320B.9000804@agliodbs.com> Date: Sun, 07 Mar 2010 15:08:59 -0800 From: Josh Berkus User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: Noel Proffitt CC: pgsql-testers@postgresql.org Subject: Re: Numerics of diffrent scales Raises Type Mismatch Error in a Set Returning Function References: <1267589227.25740.25.camel@keg> <4B92FD12.9070307@agliodbs.com> In-Reply-To: <4B92FD12.9070307@agliodbs.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.215 tagged_above=-10 required=5 tests=AWL=0.384, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/3 X-Sequence-Number: 52 On 3/6/10 5:10 PM, Josh Berkus wrote: > On 3/2/10 8:07 PM, Noel Proffitt wrote: >> [TEST REPORT] >> >> [Release]: 9.0 Alpha 4 >> >> [Test Type]: feature >> >> [Test]: NUMERICS OF DIFFERENT SCALE UNABLE TO CAST TO RESULTS IN SET >> RETURNING FUNCTION > > Verified as a problem in 9.0. Per pgsql-bugs, it's an expected compatibility issue due to unifying the SQL and PLPGSQL parsers. That is, the fact that plpgsql used to let you do this was regarded as a bug, and was not consistent with the SQL command line. Worth noting in the release notes as part of a general class of backwards-compatibility issues. --Josh Berkus