aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/explain.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2002-09-23 01:43:23 +0000
committerBruce Momjian <bruce@momjian.us>2002-09-23 01:43:23 +0000
commitf9a1ea6fa7fa07616aad12625031ff328624ed4a (patch)
tree85e7bbb6918611dcaa5c195b135f5e105dd80fe2 /src/backend/commands/explain.c
parent2816141978adb83b263c40e3b45f428e9bff7a5a (diff)
downloadpostgresql-f9a1ea6fa7fa07616aad12625031ff328624ed4a.tar.gz
postgresql-f9a1ea6fa7fa07616aad12625031ff328624ed4a.zip
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
Diffstat (limited to 'src/backend/commands/explain.c')
0 files changed, 0 insertions, 0 deletions