Re: PQntuples return type

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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 21:31:40
Message-ID: 200709262131.l8QLVer15979@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> 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?

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

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Erik Jones 2007-09-26 22:22:40 Re: datestyle question
Previous Message Keaton Adams 2007-09-26 20:44:52 Memory usage of COPY command