Skip site navigation (1) Skip section navigation (2)

Re: WIP: Join push-down for foreign tables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: Join push-down for foreign tables
Date: 2011-12-02 23:05:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> Hmm, so you're saying that the FDW function needs to be able to return 
> multiple paths for a single joinrel. Fair enough, and that's not 
> specific to remote joins. Even a single-table foreign scan could be 
> implemented differently depending on whether you prefer fast-start or 
> cheapest total.

... or ordered vs unordered, etc.  Yeah, good point, we already got this
wrong with the PlanForeignScan API.  Good thing we didn't promise that
would be stable.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Daniel FarinaDate: 2011-12-02 23:25:59
Subject: Re: backup_label during crash recovery: do we know how to solve it?
Previous:From: Dimitri FontaineDate: 2011-12-02 23:04:57
Subject: Re: Command Triggers

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group