Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning PostgreSQL 11

You're reading from   Learning PostgreSQL 11 A beginner's guide to building high-performance PostgreSQL database solutions

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher
ISBN-13 9781789535464
Length 556 pages
Edition 3rd Edition
Languages
Arrow right icon
Authors (2):
Arrow left icon
Andrey Volkov Andrey Volkov
Author Profile Icon Andrey Volkov
Andrey Volkov
Christopher Travers Christopher Travers
Author Profile Icon Christopher Travers
Christopher Travers
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

1. Relational Databases 2. PostgreSQL in Action FREE CHAPTER 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

Tuning performance for write

High write loads can have different patterns. For example, this can be a result of writing events to PostgreSQL or it can be a result of a bulk load from a database dump or an ETL job. You can tune PostgreSQL for high write loads by doing the following:

  • Hardware configuration:
    • You should use RAID 1+0 instead of RAID 5 or 6. RAID 10 has a much better performance for heavy writes. Also, it's better to store transaction logs (pg_xlog) on a separate hard disk.
    • You can use SSD hard disks with write-back cache (WBC), which significantly increases write performance. Also make sure your SSDs can persist cached data on power failure.
  • PostgreSQL server setting:
    • fsync: By default, fsync is on. This parameter makes sure that the database can be recovered in the event of a hardware crash. fsync makes sure that the data is actually written on the hard...
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 $19.99/month. Cancel anytime
Banner background image