Re: counterintuitive behaviour in pl/pgsql - Mailing list pgsql-general

From Tom Lane
Subject Re: counterintuitive behaviour in pl/pgsql
Date
Msg-id 1516.1305991840@sss.pgh.pa.us
Whole thread Raw
In response to counterintuitive behaviour in pl/pgsql  (Dan S <strd911@gmail.com>)
Responses Re: counterintuitive behaviour in pl/pgsql  (Dan S <strd911@gmail.com>)
List pgsql-general
Dan S <strd911@gmail.com> writes:
> And yes I do know that I can fix the problem by renaming the output column
> to something else than i , I'm just curious about the behaviour and if it
> should work like this and why.

> CREATE OR REPLACE FUNCTION dynamic_query(i int) RETURNS TABLE (i int) as $$

This should probably throw an error.  There is a check that disallows
having two input or two output parameters named the same, but the
comment about it says:

            /*
             * As of Postgres 9.0 we disallow using the same name for two
             * input or two output function parameters.  Depending on the
             * function's language, conflicting input and output names might
             * be bad too, but we leave it to the PL to complain if so.
             */

It looks like plpgsql didn't get the memo about checking this.

            regards, tom lane

pgsql-general by date:

Previous
From: Björn Häuser
Date:
Subject: Re: counterintuitive behaviour in pl/pgsql
Next
From: Michael Glaesemann
Date:
Subject: Re: counterintuitive behaviour in pl/pgsql