On 07/22/2011 11:34 AM, Robert Haas wrote:
No, you can specify connection details at per-server and
per-foreign-table level too. The FDW implementation is free to accept or
reject options where-ever it wants.
Well, if we are going to take that viewpoint, then not having a user
mapping *shouldn't* be an error, for any use-case. What would be an
error would be not having the foreign-user-name-or-equivalent specified
anywhere in the applicable options, but it's up to the FDW to notice and
complain about that.
+1.
What does the standard say?
You can get around most of the inconvenience with an empty PUBLIC user
mapping, although it's mildly annoying if you've forgotten to make one.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
