From: | Igor Korot <ikorot01(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Retrieving query results |
Date: | 2017-08-23 01:04:05 |
Message-ID: | CA+FnnTzmmm6Ck=MfbJAWTUon3+yuazVAbs-Pakf4tUCFevB-0Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi, Michael,
On Tue, Aug 22, 2017 at 8:32 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Wed, Aug 23, 2017 at 3:19 AM, Igor Korot <ikorot01(at)gmail(dot)com> wrote:
>> [quote]
>> PQntuples
>>
>> 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.
>>
>> int PQntuples(const PGresult *res);
>> [/quote]
>>
>> Is there another way to not to overflow the result?
>
> Not really with the existing API.
What do you mean "not really"
> Note that getting at 2 billion rows
> is really a lot, and would cause performance issues on the application
> side because a bunch of data would need to be processed, and getting
> out this much data is not network-wise anyway.
That's OK, As long as my program works with arbitrary number of rows.
Thank you.
> --
> Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-08-23 01:53:08 | Re: pg_rewind - restore new slave failed to startup during recovery |
Previous Message | Michael Paquier | 2017-08-23 00:55:07 | Re: Fwd: PostgreSQL 9.4.13 is facing issue in shutting down |