But wouldn't the stored procedure with parameters matching the order
of the parameters in the call be the stored procedure to be called?
On Sun, Feb 21, 2010 at 1:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> list_usr@spacebox.net writes:
>> I think the issue was the ordering of the parameters - after your
>> initial answer to my question I updated the stored procedure so the
>> ordering of the parameters matched the order that they appeared in the
>> insert statement. I recreated the stored procedure and continued to
>> encounter the problem which led me to believe that wasn't the issue.
>
> Note that two functions with the same names and differently ordered
> parameter lists are different objects to Postgres. I think maybe you
> forgot to drop the first version and it was still getting invoked.
>
> regards, tom lane
>