Tom Lane wrote: > Bruce Momjian <bruce@xxxxxxxxxx> 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@xxxxxxxxxx> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
