1 / 18

Conceptual Architecture of PostgreSQL

Conceptual Architecture of PostgreSQL. S-Queue-L Khurrum A Mujeeb, Adam Abu Hijleh, Adam Ali Stephen McDonald, Wisam Zaghal. CISC 322 - Fall 2010. Overview. What is Postgres ? Research Methods Considered Alternatives Reference Architecture Conceptual Architecture

gerek
Download Presentation

Conceptual Architecture of PostgreSQL

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Conceptual Architectureof PostgreSQL S-Queue-L Khurrum A Mujeeb, Adam Abu Hijleh, Adam Ali Stephen McDonald, Wisam Zaghal CISC 322 - Fall 2010

  2. Overview • What is Postgres? • Research Methods • Considered Alternatives • Reference Architecture • Conceptual Architecture • Inside Subsystems – Query Processor • Inside Subsystems – Storage Manager • Inside Subsystems – Utilities • Use Case • Concurrency Control • Design Trade-offs • Limitations of Research • Lessons Learned • Summary • Q & A

  3. Whatis PostgreSQL? • Open-Source database management system • ‘Ingres Project’ at UC Berkeley • First Postgres version released in 1997 • Cross-Platform • Written in C • Used by organisations such as:- • Yahoo • MySpace • Skype

  4. ResearchMethods General understanding of PostgreSQL • Developers guide • PostgreSQLwikipage • PostgreSQL manual • Wikipedia Reference architecture for Database Management System • Backbone of conceptual architecture Conceptual architecture for PostgreSQL • Various available online documentation of Conceptual Architectures of PostgreSQL

  5. Considered Alternatives 1. Client – Server 2. Client – Server w/ Pipe & Filter 3. Client – Server w/ Pipeline & Repository

  6. ReferenceArchitecture • Figure. 1

  7. Conceptual Architecture Client Communications Manager Legend Utilities & Shared Components Server (Query Processor) Dependencies Storage Manager Figure 2.

  8. Query Processor Figure 3.

  9. Inside SubsystemsQuery Processor • Consists of :- • Parser: syntax • Traffic Cop : simple/complex • Utility Command: simple queries • Rewriter: rule augmentation • Planner/Optimizer: optimal plan • Executor: execute optimal plan • Models a Pipe & Filter style Architecture • Uses storage management & shared utilities

  10. Inside SubsystemsStorage Manager Legend Provides Shared memory for buffers & access to database. Suggests repository style Figure 4.

  11. Inside SubsystemsUtilities Legend Consists of : • Utilities • Catalog • Access Methods • Nodes/Lists Utilities are used by all sub-components of the query processor Figure 5.

  12. Use Case – Select Query Figure 6.

  13. Concurrency Control Postmasterspawns multiple server threads (process per request) Problem- overwriting or modifying data Solution… - MVCC – Multi-version concurrency control - Point in time DB snapshot - Locks – locks entire table from being altered/deleted

  14. Design Trade-offs Reliability vsPerformance Scalability vsMaintainability Security vs Performance

  15. Limitations of Research Personal Knowledge as well as experience with architectures & databases Determining depth of research Sources are incomplete

  16. LessonsLearned Cannot rely on one source for information, will have to go through several sources to build a complete picture Hard to decide on an architecture style The value of the reference architecture

  17. Summary Hybrid Conceptual Architecture Client Server – front/back connection Pipe & Filter – back end processes Repository – storage management/access Design Attributes Reliable& Secure - data integrity, strict SQL compliance, user authentication Performance - slower and more complicated

  18. Thank You! Questions?

More Related