[Postgres-xl-bugs] PGXL 9.5 beta1 | PGXL Bind and Prepared statement parameters mismatch problem.

Pavan Deolasee pavan.deolasee at gmail.com
Sun May 8 22:22:21 PDT 2016


Hi Vamshi,

This is now fixed in the upstream git repo. Please check and let me know.

Thanks,
Pavan

On Wed, May 4, 2016 at 12:00 PM, Vamshi Reddy <vamshi.reddy at citrix.com>
wrote:

> *Thanks Pavan.*
>
>
>
>
> *Vamshi Reddy,*
>
> *Software Engineer,*
>
> *Citrix R&D, Bangalore, India.*
>
>
> ------------------------------
> *From:* Pavan Deolasee <pavan.deolasee at gmail.com>
> *Sent:* Monday, May 2, 2016 3:52 AM
> *To:* Vamshi Reddy
> *Cc:* postgres-xl-bugs at lists.sourceforge.net; Raghu Goyal; Sovit Garg;
> Ramanuj Kumar
> *Subject:* Re: [Postgres-xl-bugs] PGXL 9.5 beta1 | PGXL Bind and Prepared
> statement parameters mismatch problem.
>
>
>
> On Wed, Apr 27, 2016 at 5:43 PM, Vamshi Reddy <vamshi.reddy at citrix.com>
> wrote:
>
>>
>>
>> 2016-04-26 13:15:39 UTC [10.102.126.216(40196)] [1576]: [53-1]
>> user=mpsroot,db=mpsdb,e=00000 LOG: * Connection error bind message
>> supplies 2 parameters, but prepared statement “_PLAN0x80e2d0400” **requires
>> 5** [ERROR: This might be taking the Query 1’s prepared statement into
>> consideration while binding the parameters of Query 2 because of same ID
>> and some query ID deallocation issues???]*
>>
>>
> Thanks for the report. I can reproduce this problem and will work to fix
> it soon.
>
>
>>
>> *Can you please help me resolve this problem?*
>>
>
> I can't think of a simple work-around right now. The only thing you can do
> is to use different names for the prepared statement in the same session
> until this get fixed.
>
> Thanks,
> Pavan
>
>
>
>
> --
>  Pavan Deolasee                   http://www.2ndQuadrant.com/
>  PostgreSQL Development, 24x7 Support, Training & Services
>



-- 
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.postgres-xl.org/private.cgi/postgres-xl-bugs-postgres-xl.org/attachments/20160509/f2748fb1/attachment.htm>


More information about the postgres-xl-bugs mailing list