pganalyze (@pganalyze) 's Twitter Profile
pganalyze

@pganalyze

Postgres performance at any scale. Deliver consistent database performance & availability through intelligent tuning advisors and continuous database profiling.

ID: 1952665526

linkhttps://pganalyze.com calendar_today10-10-2013 21:33:17

1,1K Tweet

932 Followers

331 Following

pganalyze (@pganalyze) 's Twitter Profile Photo

In yesterday's E111 of "5mins of Postgres" we took a look at faster B-Tree Index Scans coming to Postgres 17, when using IN lists or the ANY= operator. In one test case we saw up to a 4x performance improvement: hubs.li/Q02tycxH0

pganalyze (@pganalyze) 's Twitter Profile Photo

In today's 5mins of Postgres, we discuss the streaming I/O changes recently committed to Postgres 17 by Thomas Munro. These represent an important building block for async I/O in future releases, and already improve speed for Sequential Scans & ANALYZE now: pganalyze.com/blog/5mins-pos…

pganalyze (@pganalyze) 's Twitter Profile Photo

In this week's E112 of "5mins of Postgres" we looked at the streaming I/O changes in Postgres 17. This improves the performance of ANALYZE and Sequential Scans, and is an important step towards asynchronous I/O in future releases: hubs.li/Q02vf8cz0

pganalyze (@pganalyze) 's Twitter Profile Photo

In this week's E113 of "5mins of Postgres" we discuss a commonly encountered Postgres planner quirk, which is how Postgres behaves when you have a LIMIT and an ORDER BY clause, and it picks the wrong index: hubs.li/Q02w5Ncf0

pganalyze (@pganalyze) 's Twitter Profile Photo

In yesterday's E113 of "5mins of Postgres" we discussed what happens when ORDER BY + LIMIT causes the Postgres planner to choose the wrong index, sometimes resulting in surprisingly bad performance: hubs.li/Q02w5ST_0

Lukas Fittl (@lukasfittl) 's Twitter Profile Photo

I discovered a (small) Postgres security issue (CVE-2024-4317), and it's been fixed in this week's releases! This might affect you if you use extended statistics. Learn all the details in today's 5mins of Postgres episode, including how to apply the fix: pganalyze.com/blog/5mins-pos…

pganalyze (@pganalyze) 's Twitter Profile Photo

In last week's E114 of "5mins of Postgres" we discussed the security fix (CVE-2024-4317) contained in the recent Postgres minor releases, and how to resolve it on existing systems: hubs.li/Q02wSLMp0

pganalyze (@pganalyze) 's Twitter Profile Photo

In today's 5mins of Postgres, we discuss bad row estimates on JSONB columns and how to fix them. We feature (Dr.) Eric Fritz's post from earlier this week that used CREATE STATISTICS to improve planner stats, as well as previous posts by Vsevolod Solovyov & Adrien Nayrat: hubs.li/Q02xFZ4-0

pganalyze (@pganalyze) 's Twitter Profile Photo

In last week's E115 of "5mins of Postgres" we discussed bad query plans caused by incorrect JSONB selectivity estimates, and how to fix them: hubs.li/Q02xF-QY0

pganalyze (@pganalyze) 's Twitter Profile Photo

In today's 5mins of Postgres, we discuss Postgres 17 beta 1, which was released earlier this week. We also discuss a few of the changes that ended up being reverted since the feature freeze, and explain how to report bugs during beta testing: hubs.li/Q02ysBFy0

pganalyze (@pganalyze) 's Twitter Profile Photo

In last week's E116 of "5mins of Postgres" we discussed a few highlights of the Postgres 17 beta 1 release, and how to help during the beta testing period: hubs.li/Q02yswJX0

pganalyze (@pganalyze) 's Twitter Profile Photo

In today's 5mins of Postgres, we discuss JOIN column equivalence and when there are issues with IN/ANY filters not being considered as part of an equivalence class in #Postgres. Featuring a blog post by Deepak Mahto: hubs.li/Q02zbLSc0

pganalyze (@pganalyze) 's Twitter Profile Photo

In last week's E117 of "5mins of Postgres" we discussed JOIN column equivalence and when there are issues with IN/ANY filters, and how adding an extra WHERE clause helps improve query plans: hubs.li/Q02zbQCy0

Lukas Fittl (@lukasfittl) 's Twitter Profile Photo

Using materialized CTE Scans in your queries? You might see a surprising query plan for the rest of your query. In today's 5mins of Postgres episode we discuss a PG 17 change that fixes the passing along of column stats & sort order for materialized CTEs: pganalyze.com/blog/5mins-pos…

pganalyze (@pganalyze) 's Twitter Profile Photo

In today's 5mins of Postgres, we talk about tuning work_mem, and the surprising facts about how Postgres allocates memory based on it, and hash_mem_multiplier. Featuring a post by Shaun Thomas on the Tembo - Multi-Workload Postgres blog. hubs.ly/Q02C4N6q0

pganalyze (@pganalyze) 's Twitter Profile Photo

Blog post: We take a look at #ConstraintProgramming in action based on our experience optimizing index selection in #Postgres. We deep dive into what makes Postgres Index Selection difficult and how utilizing a CP model can help: pganalyze.com/blog/index-sel…

pganalyze (@pganalyze) 's Twitter Profile Photo

Join us Sept. 26 for our live event, "Hands on Postgres 17" to learn how enhancements, like faster B-tree scans, adaptive vacuum strategies, & streaming I/O updates, will impact your database performance & monitoring. Register->bit.ly/postgres17

Join us Sept. 26 for our  live event, "Hands on Postgres 17" to learn how enhancements, like  faster B-tree scans, adaptive vacuum strategies, & streaming I/O  updates, will impact your database performance & monitoring. Register->bit.ly/postgres17
pganalyze (@pganalyze) 's Twitter Profile Photo

Check out one of our most popular "5 mins of Postgres" episodes - No. 111 where we discuss faster B-tree index scans in Postgres 17. Watch the full episode here ➡️ lnkd.in/g2_zYCkM Register for next week's webinar, Hands on Postgres 17 ➡️ bit.ly/postgres17

pganalyze (@pganalyze) 's Twitter Profile Photo

Don't miss your chance to register for this Thursday's webinar, "Hands on Postgres 17" to learn how important updates will impact your database performance & monitoring. Register to join live or get the recording here ➡️ bit.ly/postgres17soci… #Postgresql #Database