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:23 -0400
commit941e47fc43cc3d80bfd4112e013a1d11235ead6a (patch)
tree0f74b6dcbc1d49dc41853246df00d85800ecaefe /src/backend/executor/execParallel.c
parentbc95e5874ac9bc027d1549677ec4f61b9d36a2a3 (diff)
downloadpostgresql-941e47fc43cc3d80bfd4112e013a1d11235ead6a.tar.gz
postgresql-941e47fc43cc3d80bfd4112e013a1d11235ead6a.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