Bruce Momjian f9a1ea6fa7 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

2002-09-23 01:43:23 +00:00

..

cli

pgindent run.

2002-09-04 20:31:48 +00:00

ecpg

Remove commas for compatibility with newer bisons.

2002-09-22 21:54:31 +00:00

jdbc

Added regression test for using server side prepared statements in jdbc

2002-09-14 03:52:56 +00:00

libpgtcl

Obviously noone has ever tested the doubling of availiable result ids

2002-09-23 01:43:23 +00:00

libpq

Translation updates, some messages tweaked.

2002-09-22 20:57:21 +00:00

python

pgindent run.

2002-09-04 20:31:48 +00:00

Makefile

perl5 interface moved to gborg

2002-08-30 13:06:22 +00:00