More Related Content Similar to Federation with foreign_data_wrappers_pg_conf_eu_20131031 (20) More from David Fetter (15) Federation with foreign_data_wrappers_pg_conf_eu_201310311. Federation with
Foreign Data Wrappers
Foreign Data Wrappers
PGConf.EU 2013/10/31
Copyright© 2013
David Fetter david.fetter@disqus.com
All rights reserved.
22. A Disqus Hour
• 50 GB raw log data
• 30 GB event data
• 100 million embed loads
• ...last week.
64. IMPORT FOREIGN SCHEMA <foreign schema> [
LIMIT TO ( <table name list> )
| EXCEPT ( <table name list> )
]
FROM SERVER <foreign server name>
INTO <local schema>
Editor's Notes Feedback!!!
Nuair ar am,
A few rounds with the ISO standards committee, and then:
SQL:2003
Lots of "interesting" things added
Joe Conway did this. It's still going.
I did this with a lot of help from Andrew (RhodiumToad) Gierth. This was in 2004.
Seven functions, maybe in Python!
Thanks to George Courtsunis for the latest numbers. So we have good reasons to want to do things efficiently rather than with brute force.
Six more functions!
This is a WIP a.k.a. "Vaporware."
This is broken, too. Shouldn't these be in contrib? They fit in terms of being version-dependent, at least until we get our API stabilized.
SQL (Draft) Standard Ahead!
Some of this makes sense. Why not regex match, or at least glob? What happens when the remote side doesn't have schemas per se?
Actually, full compliance seems insane at first blush, but we can at least try for more.
Feedback!