2011/11/14 Robert Haas <robertmhaas@gmail.com>:
> On Mon, Nov 14, 2011 at 10:45 AM, Emanuel Calvo <postgres.arg@gmail.com> wrote:
>> 2011/11/10 Robert Haas <robertmhaas@gmail.com>:
>>> On Wed, Nov 9, 2011 at 12:31 PM, Emanuel Calvo <postgres.arg@gmail.com> wrote:
>>>>> \dew+ lists the actual options supplied to a foreign data wrapper already.
>>>>
>>>> Checked, but the options doesn't appear (the column exists, but is empty).
>>>
>>> Well, that just means that you didn't specify any options when you ran
>>> CREATE FOREIGN DATA WRAPPER.
>>>
>>> rhaas=# create foreign data wrapper dummy options (foo 'bar');
>>> CREATE FOREIGN DATA WRAPPER
>>> rhaas=# \dew+
>>> List of foreign-data wrappers
>>> Name | Owner | Handler | Validator | Access privileges | FDW Options
>>> | Description
>>> -------+-------+---------+-----------+-------------------+-------------+-------------
>>> dummy | rhaas | - | - | | (foo 'bar') |
>>> (1 row)
>>>
>>> I'm not sure we're talking about the same thing, though.
>>>
>>
>> No. I thought 'options' were the parameters when you create a fdw (example:
>> host, port, file, etc).
>
> Each FDW can make its own decisions about which options it wants to
> support - the core server support doesn't know anything about how the
> data will be used. You can set options on the FDW level, the server
> level, the foreign table level, and maybe a few other places.
> Normally I would expect things like host and port to be set on the
> server level, rather than the foreign data wrapper level.
>
Gotcha. Thanks Robert! I must report to the fdw creator.
--
--
Emanuel Calvo
Helpame.com