Re: Stored procedures and out parameters

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Shay Rojansky <roji(at)roji(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Stored procedures and out parameters
Date: 2018-07-23 21:04:21
Message-ID: 0aaca430-27f9-64be-b0aa-6f6071210f09@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 23.07.18 19:38, Andrew Gierth wrote:
>>>>>> "Robert" == Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>
> >> However, connecting via Npgsql, which uses the extended protocol, I
> >> see something quite different. As a response to a Describe
> >> PostgreSQL message, I get back a NoData response rather than a
> >> RowDescription message, In other words, it would seem that the
> >> behavior of stored procedures differs between the simple and
> >> extended protocols, when INOUT parameters are involved.
>
> Robert> I might be wrong, but that sounds like a bug.
>
> Completely off the cuff, I'd expect 59a85323d might have fixed that;
> does it fail on the latest 11-stable?

Yes, that's supposed to address that.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2018-07-23 21:53:55 Re: Have an encrypted pgpass file
Previous Message Jeff Janes 2018-07-23 20:14:40 Re: BUG #15182: Canceling authentication due to timeout aka Denial of Service Attack