Peter T Mount wrote:
>
> The only solution I was able to give was for them to use cursors, and
> fetch the result in chunks.
Got it!!!
Seems everyone has 'voted' for using cursors.
As a matter of fact, I have tested both a
BEGIN ; DECLARE CURSOR ; FETCH N; END;
and a
SELECT FROM
Both of them are locking for write the tables that they use, until end
of processing.
Fetching records in chunks (100) would speed up a little the processing.
But I am still convinced that if frontend would be able to process
tuples as soon as they come, the overall time of processing a big table
would be less.
Fetching in chunks, the frontend waits for the 100 records to come (time
A) and then process them (time B). A and B cannot be overlapped.
Thanks a lot for helping me to decide. Reports in PgAccess will use
cursors.
--
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA