Obviously noone has ever tested the doubling of availiable result ids

Bruce Momjian <bruce@momjian.us>

Commit: f9a1ea6fa7fa07616aad12625031ff328624ed4a
Author: Bruce Momjian <bruce@momjian.us>
Date: 2002-09-23T01:43:23Z
Releases: 7.3.1
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)

Gerhard Hintermayer

Files

PathChange+/−
src/interfaces/libpgtcl/pgtclId.c modified +4 −1