https://www.pgelephant.com/postgresql/postgresql-database-indexes-complete-production-troubleshooting 2026-08-29T08:57:53+00:00 weekly 0.85 https://i3.ytimg.com/vi/rO8MQa0m7w0/hqdefault.jpg PostgreSQL Database Indexes: Complete Production Troubleshooting Before we open a single terminal, here is what you are getting. Every index type PostgreSQL 18 ships, on a five million row table. Measured, not guessed. You will watch the planner refuse a perfectly good index, and you will find out why. If you have ever added an index and watched nothing get faster, this is the one that fixes it. https://www.youtube.com/embed/rO8MQa0m7w0 2026-08-29T08:57:53+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/amazon-aurora-postgresql-database-what-happens-when-it-fails 2026-08-12T09:15:10+00:00 weekly 0.85 https://i4.ytimg.com/vi/ktxMp16wyCw/hqdefault.jpg Amazon Aurora PostgreSQL Database: What Happens When It Fails? Managed doesn't mean unbreakable. But on Aurora, the thing that breaks is compute. Your data sits in a separate storage service that the instance failure never touched. So when the writer dies, what happens next depends on one question. Do you have a replica? With one, Aurora promotes it, usually in under thirty seconds. Without one, Aurora has to build you a new writer, and that takes minutes. Lose a whole availability zone and writes keep going. We'll build all of it, break it, and measure it. https://www.youtube.com/embed/ktxMp16wyCw 2026-08-12T09:15:10+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/postgresql-active-active-across-3-regions-production-ha 2026-08-10T05:49:12+00:00 weekly 0.85 https://i1.ytimg.com/vi/Pb40avdFFBs/hqdefault.jpg PostgreSQL Active-Active Across 3 Regions | Production HA Three writable PostgreSQL regions. No single global primary - all three accept writes at once. That is active-active, with pgEdge Spock. When one region dies, the survivors keep writing. https://www.youtube.com/embed/Pb40avdFFBs 2026-08-10T05:49:12+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/amazon-rds-postgresql-database-what-happens-when-it-fails 2026-08-07T13:20:26+00:00 weekly 0.85 https://i2.ytimg.com/vi/ETjUXzKFp4I/hqdefault.jpg Amazon RDS PostgreSQL Database: What Happens When It Fails? Managed doesn't mean it never breaks. When the writer goes away, every open connection goes with it. What happens next depends on the architecture you picked. Single-AZ has no standby, so recovery means a restart, or a replacement. AWS documents sixty to one hundred twenty seconds for a Multi-AZ DB instance, and under thirty-five for a Multi-AZ DB cluster. Sockets never migrate. So we build each pattern, break it, and measure what the application sees. https://www.youtube.com/embed/ETjUXzKFp4I 2026-08-07T13:20:26+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/postgresql-16-cores-this-query-uses-one 2026-08-05T19:28:28+00:00 weekly 0.85 https://i4.ytimg.com/vi/SxeeJnmdUf4/hqdefault.jpg PostgreSQL: 16 Cores. This Query Uses One PostgreSQL: 16 Cores. This Query Uses One. A detailed PostgreSQL article and long-form video by Dr. Ibrar Ahmed, with technical context, examples, and production guidance. https://www.youtube.com/embed/SxeeJnmdUf4 2026-08-05T19:28:28+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/postgresql-ha-architecture-surviving-a-full-region-failure 2026-08-04T09:18:02+00:00 weekly 0.85 https://i4.ytimg.com/vi/gcSWFKX89vo/hqdefault.jpg PostgreSQL HA Architecture: Surviving a Full Region Failure Let's build a PostgreSQL cluster that survives things going wrong, and let's build it one honest step at a time. This is where everyone starts: one application, one PostgreSQL eighteen server called db one. A write arrives, it is recorded in the write-ahead log, and the commit comes back. It works perfectly. And that is exactly the trap, because the postgres processes, the kernel, the disk, and the address your clients dial all live inside a single failure domain. https://www.youtube.com/embed/gcSWFKX89vo 2026-08-04T09:18:02+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/postgresql-high-availability-build-break-fix-patroni-etcd 2026-07-29T18:07:27+00:00 weekly 0.85 https://i2.ytimg.com/vi/a73oSuoeGPY/hqdefault.jpg PostgreSQL High Availability: Build, Break & Fix Patroni + etcd Let's build a PostgreSQL cluster that survives things going wrong, and let's build it one honest step at a time. This is where everyone starts: one application, one PostgreSQL eighteen server called db one. A write arrives, it is recorded in the write-ahead log, and the commit comes back. It works perfectly. And that is exactly the trap, because the postgres processes, the kernel, the disk, and the address your clients dial all live inside a single failure domain. https://www.youtube.com/embed/a73oSuoeGPY 2026-07-29T18:07:27+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/500-postgresql-connections-470-idle-fix-this-before-production-slows 2026-07-19T21:13:59+00:00 weekly 0.85 https://i4.ytimg.com/vi/7CBQcT8doaE/hqdefault.jpg 500 PostgreSQL Connections, 470 Idle: Fix This Before Production Slows 500 PostgreSQL Connections, 470 Idle: Fix This Before Production Slows. A detailed PostgreSQL article and long-form video by Dr. Ibrar Ahmed, with technical context, examples, and production guidance. https://www.youtube.com/embed/7CBQcT8doaE 2026-07-19T21:13:59+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/postgresql-uses-1-of-16-cpu-cores-here-s-the-fix 2026-07-13T12:02:35+00:00 weekly 0.85 https://i4.ytimg.com/vi/_1bqNyb_t1w/hqdefault.jpg PostgreSQL Uses 1 of 16 CPU Cores. Here's the Fix. PostgreSQL Uses 1 of 16 CPU Cores. Here's the Fix.. A detailed PostgreSQL article and long-form video by Dr. Ibrar Ahmed, with technical context, examples, and production guidance. https://www.youtube.com/embed/_1bqNyb_t1w 2026-07-13T12:02:35+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/your-postgresql-work-mem-is-a-400-gb-memory-bomb 2026-06-26T10:48:40+00:00 weekly 0.85 https://i2.ytimg.com/vi/1KJryLXOlMU/hqdefault.jpg Your PostgreSQL work_mem Is a 400 GB Memory Bomb Your PostgreSQL work_mem Is a 400 GB Memory Bomb. A detailed PostgreSQL article and long-form video by Dr. Ibrar Ahmed, with technical context, examples, and production guidance. https://www.youtube.com/embed/1KJryLXOlMU 2026-06-26T10:48:40+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/postgresql-19-the-join-stat-fix-we-waited-10-years-for 2026-06-25T23:20:01+00:00 weekly 0.85 https://i3.ytimg.com/vi/NeUJvl0y1fg/hqdefault.jpg PostgreSQL 19: The Join Stat Fix We Waited 10 Years For PostgreSQL 19: The Join Stat Fix We Waited 10 Years For. A detailed PostgreSQL article and long-form video by Dr. Ibrar Ahmed, with technical context, examples, and production guidance. https://www.youtube.com/embed/NeUJvl0y1fg 2026-06-25T23:20:01+00:00 Dr. Ibrar Ahmed yes no no https://www.pgelephant.com/postgresql/postgresql-19-finally-see-which-tables-need-vacuum-new-feature 2026-06-24T10:58:47+00:00 weekly 0.85 https://i3.ytimg.com/vi/Bjr5H-5PN4I/hqdefault.jpg PostgreSQL 19: Finally See Which Tables Need VACUUM (New Feature) If you run Postgres in production, this is the single most important video you can watch. Vacuum is not a maintenance command. Vacuum is the subsystem that decides whether your database keeps running or falls over. https://www.youtube.com/embed/Bjr5H-5PN4I 2026-06-24T10:58:47+00:00 Dr. Ibrar Ahmed yes no no