Re: INOUT parameters in procedures

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INOUT parameters in procedures
Date: 2018-03-20 15:09:29
Message-ID: CAFj8pRBkXNpeYmUJrwPCmu+NiP=7CzQ=LVJQcMue-gL_+zOL0Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2018-03-20 15:18 GMT+01:00 Merlin Moncure <mmoncure(at)gmail(dot)com>:

> On Tue, Mar 20, 2018 at 9:09 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> >> Edit: In one case, after dropping the function and recreating it, I
> >> got the procedure to return 0 where it had not before, so this smells
> >> like a bug.
> >> postgres=# call p();
> >> 2018-03-20 09:04:50.543 CDT [21494] ERROR: function p() does not
> >> exist at character 6
> >> 2018-03-20 09:04:50.543 CDT [21494] HINT: No function matches the
> >> given name and argument types. You might need to add explicit type
> >> casts.
> >> 2018-03-20 09:04:50.543 CDT [21494] STATEMENT: call p();
> >> ERROR: function p() does not exist
> >> LINE 1: call p();
> >> ^
> >> HINT: No function matches the given name and argument types. You
> >> might need to add explicit type casts.
> >> Time: 0.297 ms
> >> postgres=# create or replace procedure p(a inout int default 7) as $$
> >> begin return; end; $$ language plpgsql;
> >> CREATE PROCEDURE
> >> Time: 1.182 ms
> >> postgres=# call p();
> >> a
> >> ───
> >> 0
> >> (1 row)
> >
> >
> > I wrote patch
>
> Confirmed this fixes the issue.
>

Thanks for info

Pavel

>
> merlin
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2018-03-20 15:23:20 Re: PATCH: Configurable file mode mask
Previous Message Christoph Berg 2018-03-20 15:01:09 Re: [PoC PATCH] Parallel dump to /dev/null