aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/execParallel.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2017-08-29 15:38:05 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2017-08-29 15:38:15 -0400
commitff59f30dc30ecb4fb777a28774110c6637b10dc1 (patch)
treebe3285e87db0a88d1bc0508d982e614a26044365 /src/backend/executor/execParallel.c
parentb481b39b876f4bd0e793d93f6202071713bc0edb (diff)
downloadpostgresql-ff59f30dc30ecb4fb777a28774110c6637b10dc1.tar.gz
postgresql-ff59f30dc30ecb4fb777a28774110c6637b10dc1.zip
Doc: document libpq's restriction to INT_MAX rows in a PGresult.
As long as PQntuples, PQgetvalue, etc, use "int" for row numbers, we're pretty much stuck with this limitation. The documentation formerly stated that the result of PQntuples "might overflow on 32-bit operating systems", which is just nonsense: that's not where the overflow would happen, and if you did reach an overflow it would not be on a 32-bit machine, because you'd have OOM'd long since. Discussion: https://postgr.es/m/CA+FnnTxyLWyjY1goewmJNxC==HQCCF4fKkoCTa9qR36oRAHDPw@mail.gmail.com
Diffstat (limited to 'src/backend/executor/execParallel.c')
0 files changed, 0 insertions, 0 deletions