So, I tested out the cursor approach, and it still chugs along for hours.
If the result set is large (and the available memory to process small),
does it matter what goes on within the cursor. Will it still choke trying
assemble and spit out the large result set?
On Mon, Mar 11, 2013 at 11:48 AM,
2013/3/11 Jeff Adams - NOAA Affiliate jeff.ad...@noaa.gov
Greetings,
I have a large table (~90 million rows) containing vessel positions.
...
Could you kindly provide a script to create the table and populate it with
several sample
rows, please? Also, provide the desired output for
Hello
you can try procedural solution - use a cursor over ordered data in
plpgsql and returns table
Regards
Pavel Stehule
2013/3/11 Jeff Adams - NOAA Affiliate jeff.ad...@noaa.gov:
Greetings,
I have a large table (~90 million rows) containing vessel positions. In
addition to a column
Pavel,
Thanks for the response. I have not yet had the opportunity to use cursors,
but am now curious. Could you perhaps provide a bit more detail as to what
the implementation of your suggested approach would look like?
On Mon, Mar 11, 2013 at 11:03 AM, Pavel Stehule
2013/3/11 Jeff Adams - NOAA Affiliate jeff.ad...@noaa.gov:
Pavel,
Thanks for the response. I have not yet had the opportunity to use cursors,
but am now curious. Could you perhaps provide a bit more detail as to what
the implementation of your suggested approach would look like?
an example:
Thanks again. The sorting does appear to be the issue. I will test out your
cursor idea...
On Mon, Mar 11, 2013 at 11:34 AM, Pavel Stehule pavel.steh...@gmail.comwrote:
2013/3/11 Jeff Adams - NOAA Affiliate jeff.ad...@noaa.gov:
Pavel,
Thanks for the response. I have not yet had the
