| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: join on next row |
| Date: | 2006-06-20 15:31:07 |
| Message-ID: | 20060620153107.GD25678@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jun 20, 2006 at 05:13:50PM +0200, Sim Zacks wrote:
> Thank you for responding.
> I was thinking along those lines as well, though that would be an
> absolute performance killer.
I shouldn't be too bad, if you have the appropriate indexes defined.
However, it seems to me this is the kind of problem that is solved
trivially in a function. You simply store the previous row and when you
get the next one you output both.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2006-06-20 15:34:50 | Re: Help requd in writing functions in C and using in Postgres |
| Previous Message | Lee Riquelmei | 2006-06-20 15:30:49 | question about performance of libpq |