Re: portal pinning - Mailing list pgsql-hackers

From Vladimir Sitnikov
Subject Re: portal pinning
Date
Msg-id CAB=Je-Hj1KnMaKMRn5fa2atp20LgzNtvoNexFzsECJ-bPRRoEQ@mail.gmail.com
Whole thread Raw
In response to Re: portal pinning  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: portal pinning  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
> committed

I'm afraid it causes regressions for pgjdbc.

The errors are:
testMetaData[typeName = REF_CURSOR, cursorType = 2,012](org.postgresql.test.jdbc2.RefCursorTest)  Time elapsed: 0.032 sec 
 <<< ERROR! org.postgresql.util.PSQLException: ERROR: cannot drop pinned portal "<unnamed portal 1>"   

It looks like "refcursor" expressions are somehow broken.

The test code is to execute testspg__getRefcursor procedure
that is defined as follows

CREATE OR REPLACE FUNCTION testspg__getRefcursor () RETURNS refcursor AS '
declare v_resset refcursor; begin open v_resset for select id from testrs order by id; 
return v_resset; end;' LANGUAGE plpgsql;

Would you please check that?

Vladimir

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: General purpose hashing func in pgbench
Next
From: Shubham Barai
Date:
Subject: Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index