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 13:50:45 |
Message-ID: | 20138.1190814645@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:
> Greg Sabino Mullane wrote:
>> There may be some other safeguards in place I did not see to prevent this,
>> but I don't see a reason why we shouldn't use unsigned int or
>> unsigned long int here, both for ntups and the return value of the
>> function.
> On second thought, I have at least updated the function documentation:
> Returns the number of rows (tuples) in the query result. Because
> it returns an integer result, large result sets might overflow the
> return value on 32-bit operating systems.
This is silly. Have you forgotten that the max number of columns is
constrained to 1600 on the backend side?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-09-26 14:45:19 | Re: Filesystem crash - corupted database |
Previous Message | Madison Kelly | 2007-09-26 13:24:36 | Re: subquery/alias question |