Skip site navigation (1) Skip section navigation (2)

Re: declare/fetch problem with pgpool 2.2.3; Postgres 8.4; ODBC 8.03.04.00

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: Andreas Gaab <A(dot)Gaab(at)scanlab(dot)de>
Cc: "'pgsql-odbc(at)postgresql(dot)org'" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: declare/fetch problem with pgpool 2.2.3; Postgres 8.4; ODBC 8.03.04.00
Date: 2009-11-19 22:11:59
Message-ID: 4B05C2AF.1050305@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-odbc
Hi Andreas,

Andreas Gaab wrote:
> I encountered a problem using pgpool with two identical postgres 8.4 
> servers as  backends.>  
> 
> Activating the odbc-setting declare/fetch, our application creates an 
> data mismatch error.  
> 
> As far as I can track down the problem, it is caused because the cursors 
> are defined after an BEGIN, thus with load balancing disabled, but are 
> CLOSED after the COMMIT, thus are only closed on one server. This leads 
> to data inconsistency for the next query DECLARING an cursor.

Unfortunately I'm not familiar with pgpool.
Are DECLARE, FETCH and CLOSE regarded as members of SELECT family ?
If so, I'm suspicios if it's appropriate.
I would ask pgpool guys about it.

regards,
Hiroshi Inoue

In response to

Responses

pgsql-odbc by date

Next:From: Andreas GaabDate: 2009-11-20 07:55:54
Subject: Re: declare/fetch problem with pgpool 2.2.3; Postgres 8.4; ODBC 8.03.04.00
Previous:From: Steve.ToutantDate: 2009-11-19 19:48:32
Subject: Re: odbc access and pg_hba.conf FIXED

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group