Haki Benita 12/21/2018

How We Solved a Storage Problem in PostgreSQL Without Adding a Single Byte of Storage

Read Original

The article details a real-world PostgreSQL performance problem where nightly ETL deduplication queries consumed excessive temporary disk space due to large sort operations. It explains the diagnosis using execution plans, identifies the `work_mem` parameter's role, and presents a solution: hashing the large binary sort key to drastically reduce its size, thereby eliminating the need for extra storage or configuration changes.

How We Solved a Storage Problem in PostgreSQL Without Adding a Single Byte of Storage

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

No top articles yet