Re: Arguments to foreign tables? - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Arguments to foreign tables?
Date
Msg-id 1352182171.6292.29.camel@jdavis-laptop
Whole thread Raw
In response to Re: Arguments to foreign tables?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Arguments to foreign tables?  (Ronan Dunklau <rdunklau@gmail.com>)
Re: Arguments to foreign tables?  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Re: Arguments to foreign tables?  (Simon Riggs <simon@2ndQuadrant.com>)
File Corruption recovery  ("md@rpzdesign.com" <md@rpzdesign.com>)
List pgsql-hackers
On Sun, 2012-11-04 at 15:13 -0500, Tom Lane wrote:
> Jeff Davis <pgsql@j-davis.com> writes:
> > Is there any fundamental or philosophical reason why a foreign table
> > can't accept arguments?
> 
> That isn't a table; it's some sort of function.  Now that we have
> LATERAL, there is no good reason to contort SQL's syntax and semantics
> in the direction you suggest.

Maybe I should rephrase this as a problem with SRFs: you don't get to
define the init/exec/end executor functions, and you don't get access to
the optimizer information.

It seems like foreign tables are a better mechanism (except for the
simple cases where you don't care about the details), and the only thing
an SRF can do that a foreign table can't is accept arguments. So, I
thought maybe it would make more sense to combine the mechanisms
somehow.

Take something as simple as generate_series: right now, it materializes
the entire thing if it's in the FROM clause, but it wouldn't need to if
it could use the foreign table mechanism.

Regards,Jeff Davis




pgsql-hackers by date:

Previous
From: "Karl O. Pinc"
Date:
Subject: Re: Doc patch, distinguish sections with an empty row in error code table
Next
From: Jeff Davis
Date:
Subject: Re: Statistics and selectivity estimation for ranges