From: g.hintermayer@inode.at
To: pgsql-interfaces@postgresql.org
Subject: pg_exec not returning after 16 calls/ libpgtcl
Date: 19 Sep 2002 03:27:05 -0700
Message-ID: <bd4db85f.0209190227.386c458d@posting.google.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: g.hintermayer@inode.at
Subject: Re: pg_exec not returning after 16 calls/ libpgtcl
In-Reply-To: <bd4db85f.0209190227.386c458d@posting.google.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox