On Mon, Jul 23, 2018 at 2:23 AM, Shay Rojansky <r...@roji.org> wrote: > Hi hackers, I've encountered some odd behavior with the new stored procedure > feature, when using INOUT parameters, running PostgreSQL 11-beta2. > > With the following procedure: > > CREATE OR REPLACE PROCEDURE my_proc(INOUT results text) > LANGUAGE 'plpgsql' > AS $BODY$ > BEGIN > select 'test' into results; > END; > $BODY$; > > executing CALL my_proc('whatever') yields a resultset with a "results" > column and a single row, containing "test". This is expected and is also how > functions work. > > 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.
I might be wrong, but that sounds like a bug. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company