aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/numeric.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:05 -0400
commit6cbee65eee20c144bb4de169c6802f20e76785b0 (patch)
tree0c09a2455548da3bd2f6a63a74cc85febfb4df45 /src/backend/utils/adt/numeric.c
parent2e70d6b5e99b7e7b53336b1838f869bbea1b5024 (diff)
downloadpostgresql-6cbee65eee20c144bb4de169c6802f20e76785b0.tar.gz
postgresql-6cbee65eee20c144bb4de169c6802f20e76785b0.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/utils/adt/numeric.c')
0 files changed, 0 insertions, 0 deletions