Re: SQL/MED - file_fdw

From: Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>
To: Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: SQL/MED - file_fdw
Date: 2010-12-24 13:36:15
Message-ID: AANLkTi=MifRZU7OEe+-yk91HiahoJaYVo+oMUBnEtczT@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 24, 2010 at 20:04, Shigeru HANADA <hanada(at)metrosystems(dot)co(dot)jp> wrote:
> Iterate is called in query context,

Is it an unavoidable requirement? If possible, I'd like to use per-tuple memory
context as the default. We use per-tuple context in FunctionScan for SETOF
functions. I hope we could have little difference between SRF and FDW APIs.

> Virtual tuple would be enough to carry column data, but virtual tuple
> doesn't have system attributes including tableoid...

We could add tts_tableOid into TupleTableSlot. We'd better avoid
materializing slot only for the tableoid support in foreign tables.
Almost all of the foreign tables should have different data format
from HeapTuple, including pgsql_fdw.

--
Itagaki Takahiro

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2010-12-24 13:50:39 Re: proposal : cross-column stats
Previous Message Tomas Vondra 2010-12-24 13:10:22 Re: proposal : cross-column stats