bhavani-DBA

Migration to Postgres Database from Oracle Using Apache-Spark. dbalearnings.wordpress.com/2025/01/26/mig…

Did you know that the mere act of writing accumulated WAL data in Postgres can bring performance to its knees? Checkpoints are great, but it's possible to have too much of a good thing. Let's talk about avoiding that, shall we?

Get the plan for #SQL in Oracle AI Database with dbms_xplan.display_cursor But what if you want to get many at once? Lukas Eder demos: SELECT ... FROM v$sql s ,TABLE (dbms_xplan.display_cursor ( s.sql_id, s.child_number )) p WHERE s.sql_text LIKE ... blog.jooq.org/how-to-fetch-m…

Postgres hacking session live now: youtube.com/watch?v=74NFSq…

After 3 years using Claude, I can say it’s the technology that has revolutionized my life. Here are 18 prompts I use daily that have transformed my day to day; they could do the same for you: (Save this 🔖)

Deepak Mahto (@mahtodeepak05): Why Ora2Pg Should Be Your First Stop for PostgreSQL Conversion postgr.es/p/7wu

Oracle AI Database 26ai has a huge number of #SQL enhancements @FungwiHarris covers his favourites: No more FROM dual Shrinking Tablespaces Priority transactions GROUP BY ALL & alias DB_DEVELOPER_ROLE IF [NOT] EXISTS for DDL oralenoir.com/my-favorite-fe…

Just finished my latest blog post: "The absolute beginner's guide to databasemaxxing" with some stuff I wish I knew at the very beginning, when I first started to learn RDBMS internals. pthorpe92.dev/databasemaxxin…

Richard Yen: EXPLAIN's Other Superpowers postgr.es/p/7w0

And now the final element to building a Postgres Patroni cluster: HAProxy. You can use any proxy with HTTP status check capabilities, but HAProxy is the most well known. Come take a look!

today in worb: internal performance insights for tuning the database to its limits 🤌 worb.cloud

Hubert 'depesz' Lubaczewski: Waiting for PostgreSQL 19 – Introduce the REPACK command postgr.es/p/7vl

Ilya Kosmodemiansky: An Ultimate Guide to Upgrading Your PostgreSQL Installation: From 17 to 18 postgr.es/p/7vk

Vibhor Kumar: PostgreSQL HA Without SSH: Why Open Source efm_extension Matters in a Zero-Trust World postgr.es/p/7vm

enjoyed today's PG hacking session a lot -- a great, super precise troubleshooting tool is coming to Postgres ecosystem pwt (pg_wait_tracer), being developed by Dmitry and to be released soon, allows precise wait event tracing for Postgres, inspired by what's available for Oracle for many years somewhat related: PoC: USDT static tracepoints for wait event tracing github.com/NikolayS/postg…

Solving slow queries often involves adding another index. But overindexing is real and a lesser-known #Postgres feature is better: 𝑪𝑹𝑬𝑨𝑻𝑬 𝑺𝑻𝑨𝑻𝑰𝑺𝑻𝑰𝑪𝑺 💡 I often found myself trying to solve a slow query or bad execution plan by adding another, more specific index. Most of the times, it worked but ... damn it was expensive. Not just disk space, but also the cost of updating the index in the write path. A lesser-known feature in Postgres is extended statistics. Something, everybody should know about when using PG. And I've been on the wrong side for way too long myself. I wished I would've known earlier! 🫣 #PostgreSQL already has a bunch of knowledge about your tables out of the box. However this knowledge is all single-column (exceptions exist), and doesn't capture the meaning between two or more columns. CREATE STATISTICS (or extended statistics) enables PG to create additional, multi-column statistics to encode column-relationship, help with insight into likely, unlikely, and impossible value combinations, as well as improve resulting row estimates. To an extend of more than one magnitude better! It's important, because in the real world, data is usually not independent. Just like a coffee without a mug is just black water on your table. The best thing: it costs almost nothing. Virtually no memory or disk space, and way lighter to keep up-to-date when data changes. And it's as simple as this: ----- CREATE STATISTICS my_stats (mcv, dependencies) ON region, plan_tier, billing_status FROM tenants; ----- Storage requirement is 2 KiB. A similar index would use ~30 MiB for the same data set. And the created execution plans typically yield better results, too. 🤯 See my full blog post and find the benchmark (+ generated execution plans and reports) on GitHub for your convenience. I'd love to hear your thoughts on this! Have you used extended statistics already? If so, what is your experience? Leave them in the comments 👇 - Benchmark code + reports: github.com/simplyblock/ex… - Blog post: vela.simplyblock.io/blog/postgres-… Thank you to all the amazing friends and PG people that kept me in the Postgres community for years and taught me so much ❤️ There are a few of those people tagged on the photo. If you want to follow some incredible people? Here's the chance! #pg #database #queryoptimization #queryplan #simplyblock #slowquery #overindexing #statistics

Hamza Sajawal: pgNow Instant PostgreSQL Performance Diagnostics in Minutes postgr.es/p/7u-

Postgres isn't broken. Your workload eliminated the quiet period it was designed around. Here's a pattern that trips up even experienced teams. Write latency develops a rhythm you can't explain by traffic. Autovacuum is always running. Maintenance that used to take minutes now takes hours. Indexes, query plans, configs — everything looks correct. Nothing is misconfigured. The problem is architectural. Postgres maintenance was built around valleys. Batch ETL writes for two hours, the database rests and catches up. Continuous ingestion has no valleys. Every maintenance process runs in direct competition with writes. All day. All night. @mattstratton from @TigerDatabase breaks down exactly where the mechanics stop working. The workloads where this hits hardest — IoT, financial feeds, observability — share one trait: the data source runs on its own schedule, independent of what the database needs. Every quarter optimizing within the wrong architecture is a quarter where migration gets harder. Full breakdown from Matty: tsdb.co/1jjv7yx2

New Blog Post! shaneborden.com/2026/03/13/mor… #PostgreSQL #Databases

Part 2 is the "big one", where I walk through installing both Postgres and Patroni so they're up and running together, so it's a bit longer than Part 1 with etcd. I hope you find it useful!