| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Chris Angelico <rosuav(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: obtain the difference between successive rows |
| Date: | 2012-10-20 16:23:34 |
| Message-ID: | 29633.1350750214@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Chris Angelico <rosuav(at)gmail(dot)com> writes:
> To be quite honest, I would simply read the table directly and then do
> the processing in an application language :) But two window functions
> should do the trick. Whether or not it's actually more efficient that
> way is another question.
FWIW, Postgres is reasonably smart about the case of multiple window
functions with identical window definitions --- once you've got one
lag() in the query, adding more isn't going to cost much.
Having said that, they are pretty expensive. I tend to agree that doing
the processing on the application side might be faster --- but only if
you've got a place to put such code there. If you've just got generic
query-result display code, there may not be any convenient way to do it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raymond O'Donnell | 2012-10-20 16:29:24 | Re: obtain the difference between successive rows |
| Previous Message | Raymond O'Donnell | 2012-10-20 16:10:47 | Re: obtain the difference between successive rows |