Re: PQntuples return type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: PQntuples return type
Date: 2007-09-26 23:57:02
Message-ID: 14000.1190851022@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> This is silly. Have you forgotten that the max number of columns is
>> constrained to 1600 on the backend side?

> Uh, this is the number of returned rows, right? How does this relate to
> columns?

Duh, brain fade on my part, sorry. Still, I suspect the return type of
PQntuples would be the very least of the changes we'd need to make to
support resultsets > 2G rows. And I would not advise changing it to an
unsigned type, since that could cause hard-to-find breakage in
comparison logic in applications.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-09-27 00:24:12 Re: pg_dump (8.1.9) does not output copy statements
Previous Message Alvaro Herrera 2007-09-26 23:09:02 Re: RETURN NEXT on result set