diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2017-08-29 15:38:05 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2017-08-29 15:38:28 -0400 |
commit | c7e990bb0f4dfa2fc33e3755a5996da890e5c9cc (patch) | |
tree | 76f32e7a780c1d1e37ce6ead04469eea1e061be2 /src | |
parent | dfd1042c6ae5973d4485d08bf6f122d0b00f50cb (diff) | |
download | postgresql-c7e990bb0f4dfa2fc33e3755a5996da890e5c9cc.tar.gz postgresql-c7e990bb0f4dfa2fc33e3755a5996da890e5c9cc.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')
0 files changed, 0 insertions, 0 deletions