This document discusses SQL/MED (SQL Management of External Data) as an approach to radically reduce network traffic when accessing universal data. It proposes pushing SQL predicates, joins, and aggregates to remote data sources rather than pulling all the data and processing it locally. The timeline outlines SQL/MED's inclusion in standards and PostgreSQL's ongoing implementation, with goals of adding features like write interfaces, join pushdown, and aggregate pushdown over the next few years. Resources are provided for further information on SQL/MED and PostgreSQL's support for it.

1. Universal Data Access
with SQL/MED
Copyright © 2012
David Fetter
dfetter@vmware.com

2. Obligatory Baby Picture

3. The Big Picture
Hard Drive Space Doubles Every 14 months
Bandwidth Doubles Every 2.4 years

9. Disaster!
The extinction of the human race will come from its inability to
EMOTIONALLY comprehend the exponential function.
Edward Teller

10. Approach:
SQL/MED

11. RADICALLY
Reduce netwoRk tRaffic

12. Encoding?

13. Not even close.

14. Stream compression?

15. Won't do it.

16. Push Code
★Predicates
★JOINs
★Aggregates

17. YES!

18. Timeline
(horribly incomplete)

19. 2003: SQL/MED defined in SQL Standard

20. 2004: DBI-Link started
2005: DBI-Link 1.0
2007: DBI-Link 2.0

21. Two Years Pass

22. 2009: SQL/MED: Doping for PostgreSQL
2011: Support for foreign tables (9.1)
2012: More support for foreign tables (9.2)
2013: Write interface, JOIN pushdown (aimed at 9.3)
201?: Aggregate pushdown, per-source optimization...
????: Stále více a více a více...

23. Resources
• Ye Wikie
• Bernd Helmle's Excellent Talk
• pgsql-hackers@postgresql.org

24. • Questions
• Comments
• Advice about my mental state
• https://2012.pgconf.eu/feedback

25. Děkujeme!