Holy awesome! I really like postgres and, with FDW, a question comes to mind.<p>Can I basically put up a PG instance and have that manage/proxy to all of my backend stores? It would be nice to be able to just use my one DB library to query Riak, Redis and Postgresql [my usual datastore stack]. I didn't see anything in here about doing CUD operations on the FDW stores, but the benefit of having a single consistent interface for READs might be large enough to adopt this.
very cool, anyone using these foreign data wrappers in production? along with the json support this is the kind of thing that will push me over the edge and make me switch from mysql to postgres. It looks like the answer to the nosql vs sql debate might be "both, togther".
The FDW wrapper that they have is really not worthy of Redis. It only supports K/V and none of the structured types. Might as well be talking to memcached. The README is useful in this case:<p><a href="https://github.com/dpage/redis_fdw/blob/master/README" rel="nofollow">https://github.com/dpage/redis_fdw/blob/master/README</a>
You can even write your own foreign data wrappers in python: <a href="http://multicorn.org/implementing-an-fdw/#id3" rel="nofollow">http://multicorn.org/implementing-an-fdw/#id3</a> Their "Hello, world" example is less than 15 lines of code.