Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 85928476999 for ; Thu, 19 Sep 2002 06:28:22 -0400 (EDT) Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id 28B64476994 for ; Thu, 19 Sep 2002 06:28:22 -0400 (EDT) Received: by news.hub.org (Postfix, from userid 8) id 4494D381927; Thu, 19 Sep 2002 06:28:21 -0400 (EDT) From: g.hintermayer@inode.at (Gerhard Hintermayer) X-Newsgroups: comp.databases.postgresql.interfaces Subject: pg_exec not returning after 16 calls/ libpgtcl Date: 19 Sep 2002 03:27:05 -0700 Organization: http://groups.google.com/ Lines: 24 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: groups-abuse@google.com To: pgsql-interfaces@postgresql.org X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/60 X-Sequence-Number: 3121 Sorry if posted twice, got not confirmation about posting from google. Obviously noone has ever tested the doubling of availiable result ids up to reaching the hard limit. After opening 16(=current REST_START value) results via pg_exec, the next pg_exec tries to find an empty slot forever :-( . In PgSetResultId file pgtclId.c in the for loop there has to be done a break, if res_max ist reached. The piece of code should look like if (resid == connid->res_max) { resid = 0; break; /* the break as to be added */ } now everything works (double available results after reaching RES_START up to reaching RES_HARD_MAX) PS: sorry, posting via Google, so no attached diff available regards Gerhard Hintermayer http://www.inode.at/g.hintermayer