Re: SQL/MED compatible connection manager

Now I have a question about the FDW C interface.  The way I understand 
it, an SQL/MED-enabled server and a FDW each have a specific API by 
which they communicate.  Supposedly, each database vendor should be able 
to ship a binary library for its FDW and each SQL/MED-enabled server 
should be able to load and use it.  (If you don't believe in binary 
compatibility, then I think there should at least be source-level 
interface compatibility.)

Now the way I read the FDWs you provide (default and pgsql), you are 
creating your own API for initialization and options validation that is 
not in the standard.  That would appear to contradict the idea of a 
standard interface.  I understand that option validation is useful, and 
I don't see anything about it in the standard, but should we break the 
API like that?  What are your designs about this?