Re: portal pinning

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(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 19:23:55
Message-ID: 9992839b-26e3-3223-67cb-7d41c9cb4069@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/10/18 13:53, Vladimir Sitnikov wrote:
>> 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.

Hmm, it seems like we are missing some test coverage in core for that.

I guess I'll have to revert this patch and go with the first approach of
putting it directly into PL/Perl and PL/Python.

--
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 Andres Freund 2018-01-10 19:34:07 Re: Dubious shortcut in ckpt_buforder_comparator()
Previous Message Sergey Burladyan 2018-01-10 19:07:14 Re: Why standby restores some WALs many times from archive?