pgsql-server/src/interfaces/libpgtcl pgtclId.c - Mailing list pgsql-committers

From momjian@postgresql.org (Bruce Momjian - CVS)
Subject pgsql-server/src/interfaces/libpgtcl pgtclId.c
Date
Msg-id 20020923014323.86FDF4763A6@postgresql.org
Whole thread Raw
List pgsql-committers
CVSROOT:    /cvsroot
Module name:    pgsql-server
Changes by:    momjian@postgresql.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


pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian - CVS)
Date:
Subject: pgsql-server/doc TODO
Next
From: momjian@postgresql.org (Bruce Momjian - CVS)
Date:
Subject: pgsql-server/doc/src/sgml plpython.sgml