Your SlideShare is downloading. ×
0
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Postgres Open Keynote: The Next 25 Years
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Postgres Open Keynote: The Next 25 Years

710

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
710
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. 1986 - 1995The Berkeley Years
  • 2. 1996open source
  • 3. advances● development● features● performance● reliability● enterprise adoption
  • 4. no
  • 5. production ready ● 8k row limit ● crash safe ● SMP scaling
  • 6. user adoption
  • 7. windows logo is property of Microsoft
  • 8. conferences
  • 9. walsender walreciever walreciever replication
  • 10. upgrade-in-placewith pg_upgrade
  • 11. expansion
  • 12. predestined?
  • 13. the firebird logo is property of IB Phoenix and is used here under principles of fair use
  • 14. MySQL logo is property of Oracle, Inc.
  • 15. Oracle logo is property of Oracle, Inc.
  • 16. elephant photo from the IUCN photo archive. used with permission
  • 17. Rocky Balboa statue photo is licensed Creative Commons by Adam Fagen, http://www.flickr.com/photos/afagen
  • 18. this year
  • 19. innovation● transaction-controlled synchronous replication● serializable snapshot isolation● K-nearest neighbor indexes● writeable common table expressions● security-enhanced Postgres
  • 20. next yearPostgreSQL 9.2
  • 21. performancelazy VXID locksreduced table locksindex-only scansdecreased I/O
  • 22. more innovation● range types● space-GiST
  • 23. year after next● more innovations● performance ● scaling to 256 cores ● advanced partitioning
  • 24. year after next● heavyweight clustering ● PostgresXC ● TransLattice ● more “big data” clustering
  • 25. PostgreSQL 10 and beyond
  • 26. adaptability
  • 27. adaptable Linux
  • 28. adaptable Linux
  • 29. virtualization
  • 30. real 2010virtual hosts
  • 31. photo by @expressmonorail flicker, licensed Creative Commons Share Alike
  • 32. virtualization challenges● zero administration● lowering resource use● sharing● autotuning● lightweight clustering
  • 33. NoSQL
  • 34. radio photos courtesy Sarah Lowry of Transistor.org. Used with permission.
  • 35. stock Elvis in concert photo. public domain
  • 36. radio photos courtesy Sarah Lowry of Transistor.org. Used with permission.
  • 37. photo property Elizabeth Farmer
  • 38. adapt● JSON & XML● direct language interfaces● zero administration● MM replication
  • 39. PostGresql As A Service (PGAAS)
  • 40. PostgreSQL 20.0
  • 41. we can do it● performance● security● availability● durability
  • 42. we know data
  • 43. See You In 2036!
  • 44. more information● Postgres: www.postgresql.org● Josh Berkus: www.pgexperts.com● Bruce Momjian: www.momjian.us Text and graphics of this talk are licensed Creative Commons Share-Alike. Many photos in the presentation are used with permission and may not be reproduced or redistributed without permission of their owners. Logos used in this presentation are property of their respective owners and are used under principles of fair use.

×