From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: SAKAMOTO Masahiko <sakamoto.masahiko@oss.ntt.co.jp>
Cc: pgsql-hackers@postgresql.org
Subject: Re: patch: SQL/MED(FDW) DDL
Date: Wed, 15 Sep 2010 21:28:40 +0300
Message-ID: <4C911058.1050005@enterprisedb.com> (raw)
In-Reply-To: <AANLkTimSga5zVCshB98_HzKnvgn5q90aW_qaDyKHhvn2@mail.gmail.com>
References: <4C905DB0.6040302@oss.ntt.co.jp>
<4C906F81.4010108@enterprisedb.com>
<AANLkTimSga5zVCshB98_HzKnvgn5q90aW_qaDyKHhvn2@mail.gmail.com>
On 15/09/10 21:21, Robert Haas wrote:
> I wonder if we might not think of the foreign data wrapper problem as
> an instance of an even more general problem. Right now, we have
> semi-pluggable index access methods - it's probably not quite possible
> to implement one as a standalone module because of XLOG, and maybe
> other reasons, but at least there's some abstraction layer there.
> Perhaps we should be thinking about a similar facility of table-access
> methods. What if someone wants to implement column-oriented storage,
> or index-organized tables, or or tables that are really slow under
> heavy write loads but can instantaneously compute SELECT COUNT(*) FROM
> table, or mauve-colored tables with magic pixie dust? I don't want to
> raise the bar for this project to the point where we can never get it
> off the ground, but if there's a way to avoid baking in the assumption
> that only foreign tables can ever have special capabilities, that
> might be valuable.
Well, you could implement all that as a foreign data wrappers. Tables
made out of pixie dust feels pretty foreign to me ;-).
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: heikki.linnakangas@enterprisedb.com, robertmhaas@gmail.com, sakamoto.masahiko@oss.ntt.co.jp
Subject: Re: patch: SQL/MED(FDW) DDL
In-Reply-To: <4C911058.1050005@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox