| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: portal pinning |
| Date: | 2018-01-10 18:53:13 |
| Message-ID: | CAB=Je-Hj1KnMaKMRn5fa2atp20LgzNtvoNexFzsECJ-bPRRoEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> committed
I'm afraid it causes regressions for pgjdbc.
Here's CI log: https://travis-ci.org/pgjdbc/pgjdbc/jobs/327327402
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shubham Barai | 2018-01-10 18:55:57 | Re: [HACKERS] GSoC 2017 : Patch for predicate locking in Gist index |
| Previous Message | Fabien COELHO | 2018-01-10 18:45:25 | Re: General purpose hashing func in pgbench |