Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning PostgreSQL 11 - Third Edition

You're reading from  Learning PostgreSQL 11 - Third Edition

Product type Book
Published in Jan 2019
Publisher
ISBN-13 9781789535464
Pages 556 pages
Edition 3rd Edition
Languages
Authors (2):
Salahaldin Juba Salahaldin Juba
Profile icon Salahaldin Juba
Andrey Volkov Andrey Volkov
Profile icon Andrey Volkov
View More author details
Toc

Table of Contents (18) Chapters close

1. Relational Databases 2. PostgreSQL in Action 3. PostgreSQL Basic Building Blocks 4. PostgreSQL Advanced Building Blocks 5. SQL Language 6. Advanced Query Writing 7. Server-Side Programming with PL/pgSQL 8. OLAP and Data Warehousing 9. Beyond Conventional Data Types 10. Transactions and Concurrency Control 11. PostgreSQL Security 12. The PostgreSQL Catalog 13. Optimizing Database Performance 14. Testing 15. Using PostgreSQL in Python Applications 16. Scalability 17. What's Next? 18. Other Books You May Enjoy

Detecting problems in query plans

The EXPLAIN command can show why a certain query is slow, especially if the BUFFER and ANALYZE options are used. There are some hints that enable us to decide whether the execution plan is good or not; these hints are as follows:

  • The estimated row number in comparison with the actual rows: This is important because this parameter defines the method of the query's execution. There are two cases: the estimated number of rows may either be overestimated or underestimated. An incorrect estimation affects the entire algorithm, which is used to fetch data from the hard disk, sort it, join it, and so on. In general, if the number of rows is overestimated, this affects performance, but not as much as if the number of rows is underestimated. On the one hand, if you perform a Nested Loop join on very big tables, the execution time will increase exponentially...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime}