Re: [PERFORM] Large Table - Slow Window Functions (Better Approach?)

2013-03-12 Thread Jeff Adams - NOAA Affiliate
, Jeff Adams - NOAA Affiliate < jeff.ad...@noaa.gov> wrote: > 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 > wrote: > >> 2013/3/11 Jeff Adams - NOAA Affiliate : >

Re: [PERFORM] Large Table - Slow Window Functions (Better Approach?)

2013-03-11 Thread Jeff Adams - NOAA Affiliate
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 wrote: > 2013/3/11 Jeff Adams - NOAA Affiliate : > > Pavel, > > > > Thanks for the response. I have not yet had the opportunity to use

Re: [PERFORM] Large Table - Slow Window Functions (Better Approach?)

2013-03-11 Thread Jeff Adams - NOAA Affiliate
; 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 : > > Greetings, > > > > > > > > I have a large table (~90 million rows) c

[PERFORM] Large Table - Slow Window Functions (Better Approach?)

2013-03-11 Thread Jeff Adams - NOAA Affiliate
Greetings, I have a large table (~90 million rows) containing vessel positions. In addition to a column that contains the location information (the_geom), the table also contains two columns that are used to uniquely identify the vessel (mmsi and name) and a column containing the Unix time (epoc