Martin Pihlak wrote:
How about extending the syntax by adding validator function(s) instead (similar
to CREATE LANGUAGE)? For instance for postgresql wrapper we might want to check
that a password is provided for a user mapping. The default validator for
postgres
wrapper would be supplied, but n
Peter Eisentraut wrote:
> Eventually, the postgresql_fdw library should contain an implementation that
> actually connects to a PostgreSQL database and does useful things (dblink
> replacement, basically). Right now, we are proposing to use it as connection
> information storage. But I think
Peter Eisentraut wrote:
> We could just use the dummy wrapper and set an
> option for the foreign data wrapper that tells what options are valid. That
> is, you would say
>
> CREATE FOREIGN DATA WRAPPER postgresql_dummy LIBRARY 'dummy_fdw' LANGUAGE C
> OPTIONS (valid_options '{host,port,
I have been thinking that we are setting up the foreign-data wrapper dummies
wrongly.
Eventually, the postgresql_fdw library should contain an implementation that
actually connects to a PostgreSQL database and does useful things (dblink
replacement, basically). Right now, we are proposing to u
