Re: Adding pipelining support to set returning functions

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Hannu Krosing <hannu(at)krosing(dot)net>
Cc: Hans-Juergen Schoenig <postgres(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Adding pipelining support to set returning functions
Date: 2008-04-11 11:11:22
Message-ID: 20080411111122.GD23648@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 11, 2008 at 01:00:04PM +0300, Hannu Krosing wrote:
> > i asked myself basically the same question some time ago.
> > pipelining seems fairly impossible unless we ban joins on those
> > "plugins" completely.
>
> Not really, just they have to be "materialized" before joins, or
> streaming node has to be at the driving side of the join, so you can
> fetch one tuple and then join it to index or hash lookup

I thought these was code in the planner already that said: if node A
requires seeking of subnode B and B doesn't support that, insert
Materialize node. Naturally there's a cost to that, so it would favour
plans that did not require seeking...

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-04-11 11:42:56 stat() vs cygwin
Previous Message Zeugswetter Andreas OSB SD 2008-04-11 10:41:57 Re: Index AM change proposals, redux