PostgreSQL: present and near future
•
0 likes•445 views
This document summarizes PostgreSQL features and development. It discusses how SQL allows users to access data more efficiently than other methods. It outlines scalability improvements in version 9.6 like parallel queries and replication. Community efforts for version 10 focus on further scalability, logical replication, and performance optimizations. The document suggests Tryton could benefit from PostgreSQL full text search, trigram indexes, and tools to analyze system performance.
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (15)
Similar to PostgreSQL: present and near future
Similar to PostgreSQL: present and near future (20)
More from NaN-tic
More from NaN-tic (15)
Recently uploaded
Recently uploaded (20)
PostgreSQL: present and near future
- 1. PostgreSQL: present and near future
- 2. 1/Less obvious than it should
- 3. ● SQL is much more than a language to acces your database: SQL allows you to forget about which is the most efficient way to obtain the data you need in a large dataset. 1.1/SQL sucks! Let's use semething new!
- 4. ● We usually compare PostgreSQL to Oracle as if that was the opponent to beat, but try to CREATE TABLE inside a transaction in Oracle... 1.2/Transactions don't look the same everywhere
- 5. ● Locking ● Indexes ● Storage optimized for lots of datatypes ● ... 1.3/And much, much more
- 6. ● EnterpriseDB – Robert Haas – Helped Amazon build RDS ● 2ndQuadrant – Simon Riggs – Developers around the world working on key core features ● Citus – Andres Freund – CitusDB: clustered PostgreSQL ● PostgreSQL Professional – Oleg Bartunov – Full Text Search ● Nippon Telegraph & Telephone... ● Tom Lane ● ... 1.4/...including an encredible (and profitable) community
- 7. 2/What's new in 9.6
- 8. ● A lot of work has gone in recent versions to make PostgreSQL highly scalable (vertically) by optimizing locked codeblocks. ● Multiple standby servers ● postgres_fdw 2.1/Scalability
- 9. 2.1.1/Multiple standby servers – replication
- 10. ● Previously only one processor/core could be used per query. Now it can be used in sequential scans, joins and aggregates. 2.2/Parallel queries
- 11. ● CUBE, ROLLUP, GROUPING SETS ● WITH & WITH RECURSIVE ● MATERIALIZED VIEWS ● Full text search ● Row-level security ● JSONB 2.3/SQL completeness
- 12. ● Checksums ● WAL ● synchronous_comit = on/of 2.4/Durability
- 13. RAM 2.4.1/Durability - Architecture Durable storage Postgres Shared memory Client Filesystem Cache Structured data WAL: Write Ahead Log
- 14. 3/What's the community working on for v10?
- 15. ● Even more scalability work (large number of cores and clients required for testing) ● Quorum commit ● Logical replication – pglogical in core ● Pushing more stuf into postgres_fdw 3.1/Scalability
- 17. ● AUTONOMOUS TRANSACTIONS 3.2/SQL completeness
- 18. ● CREATE INDEX – sorting ● Bitmap scans ● Index scans ● Asynchronous execution 3.3/Parallel queries
- 19. ● Amcheck – tool to check the correctness of data ● pg_heal 3.4/Durability
- 20. ● Sorting improvements ● Constant evaluation improvements ● Fetching several tuples “at once” 3.5/Performance
- 21. 4/What should Tryton be using but isn't and what can we learn?
- 22. ● Unaccent ● Full text search ● Trigram indexes for LIKE searches 4.1/Texts and searching
- 23. ● How do we create indexes which are not re-done on update? 4.2/Better indexes
- 24. ● PostgreSQL has lots of tools to try to understand what's going on. 4.3/To learn: tools to know what's going on
- 25. http://www.NaN-tic.com Albert Cervera i Areny albert@nan-tic.com @albertnan linkedin.com/in/albertca