muneebkhan4 commented on issue #355: URL: https://github.com/apache/age/issues/355#issuecomment-1336141937
## First 3 Chapters of The Internals of PostgreSQL The short and compact summary Points which I have read and understand are given below: ### Chapter-1 Database Cluster, Databases, and Tables - The logical structure of a database cluster - The physical structure of a database cluster - The internal layout of a heap table file - The methods of writing and reading data to a table I understood the actually working behind the database and how actually things are stored and managed. I also get to know about the `oid` and things like `relfilenode`, `'_fsm' and '_vm'`. ### Chapter-2 Process and Memory Architecture - Process Architecture - Memory Architecture I understood different processes that run when we create and run a database server. The client-server architecture understanding in action and real-world example. I also get to know about server, background, and backend processes. The maximum default connections (100) and how to set them manually. The working memory and shared memory roles. I also learned about `pgbouncer` or `pgpool-II` for handling frequently connection disconnection request. ### Chapter-3 Query Processing - Parser - Analyzer - Rewriter - Planner - Executor I had done Compiler Construction in my Degree. I have got good understanding of the in depth understanding of Query Processing by reading this Chapter. I also got more knowledge about cost methodology PostgreSQL use and also came to know about the cost of running different query operations in depth. In addition, I read about the creation of Plan Tree for Single and Multi-Table Query, getting Cheapest Path, Hash Merge Nested Loop Join. I found it very much efficient, and I found real-world application of Dynamic Programming in getting cheapest path. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
