| From: | momjian(at)postgresql(dot)org (Bruce Momjian - CVS) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql-server/src/interfaces/libpgtcl pgtclId.c |
| Date: | 2002-09-23 01:43:23 |
| Message-ID: | 20020923014323.86FDF4763A6@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql-server
Changes by: momjian(at)postgresql(dot)org 02/09/22 21:43:23
Modified files:
src/interfaces/libpgtcl: pgtclId.c
Log message:
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian - CVS | 2002-09-23 01:51:02 | pgsql-server/doc/src/sgml plpython.sgml |
| Previous Message | Bruce Momjian - CVS | 2002-09-23 01:39:06 | pgsql-server/doc TODO |