From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Doc: document libpq's restriction to INT_MAX rows in a PGresult. |
Date: | 2017-08-29 19:38:58 |
Message-ID: | E1dmmLi-000063-Hs@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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
Branch
------
REL9_4_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/2338ad26374ef27c7601bb5a1517a6a0c82ef94e
Modified Files
--------------
doc/src/sgml/libpq.sgml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql | 2017-08-29 21:37:56 | pgsql: Tag refs/tags/REL9_3_19 was created |
Previous Message | Tom Lane | 2017-08-29 19:18:51 | pgsql: Teach libpq to detect integer overflow in the row count of a PGr |