PostgreSQL 9.3 beta: Federated databases and more

I am pretty excited to see this. I was just discussing with my partner a situation where we have a lot of data in separate DBs, and would like to keep it that way, but are unable to JOIN across the DBs. We also are considering moving a geocoder DB to another server but were concerned about the implications of that when it comes to accessing that data at the same time as other.

Nit, geography lesson needed:<p>&#62;&#62;Of course, if you're in the southern hemisphere, it's not spring for you. <i>Nor if you live in the north Midwest of the US or central Canada.</i> Sorry about that; we just track the weather with PostgreSQL, we don't control it.<p>I live in the north Midwest (Wisconsin) and it is currently 72F (should hit 80 today) and sunny, with birds chirping outside- I'm pretty sure it is spring- which started Wednesday, March 20 regardless of it being cold as hell here at the time.<p>I think some native Californians have trouble with the idea it can be under -15F in February and over 100F in August in some places.

Another feature I'm really looking forward to in 9.3 is native operators to query inside stored JSON documents. It works well in the dev build and will be a great addition to the NoSQL functionality in Postgres.

Can anyone give a quick explanation of what FDW offers beyond the existing dblink functionality? I haven't used either, but it seems like it'd be helpful to many to spell out the difference.

...and still no REPLACE, INSERT IGNORE or MERGE statements.

We've been using the FDW functionality quite heavily and it works great. Joins and "transactions" between Postgres &#38; MongoDB have been an amazing feature. I can't wait for 9.3 for write functionality, although I'm not looking forward to another database upgrade.

Now, just give us a way to apply exclusion constraints across federated partitions.

Sadly, no cassandra support yet..