Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: join on next row
- 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: Tue, 20 Jun 2006 17:31:07 +0200
- Message-id: <20060620153107(dot)GD25678(at)svana(dot)org>
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.
Attachment:
signature.asc
Description: Digital signature
- References:
- join on next row
- From: Sim Zacks
- Re: join on next row
- From: Gurjeet Singh
- Re: join on next row
- From: Sim Zacks
- join on next row
- Prev by Date: question about performance of libpq
- Next by Date: Re: Help requd in writing functions in C and using in Postgres
- Previous by thread: Re: join on next row
- Next by thread: Re: join on next row
- Indexes: