Easy Foreign Data Wrappers, JSONB Cheatsheet, Cost Limits, Parallel Aggregate | Scaling Postgres 261

To get the show notes as well as get notified of new episodes, visit:

In this episode of Scaling Postgres, we discuss how to easily crate a foreign data wrapper to consume an API, present a convenient JSONB cheatsheet, changes to updating the vacuum cost limit and new parallel aggregates.

Want to learn more about Postgres performance?

Timestamps:
00:00 - Intro
00:28 - Making a Data Polyglot with PostgreSQL Foreign Data Wrappers
02:24 - PostgreSQL® JSONB Cheatsheet: Complete & Fast Lookup Guide
02:58 - Updating the Cost Limit On The Fly
04:11 - Parallel aggregate – PostgreSQL 16 – better performance
05:22 - Vacuum Cost Limit and Parallel Aggregate improvements in Postgres 16
05:43 - SQL Maxis: Why We Ditched RabbitMQ And Replaced It With A Postgres Queue
06:44 - Triggers and me
07:26 - Triggers: A Love/Hate Relationship
08:40 - STOP! Trigger Time
09:47 - PGSQL Phriday #007 – A word about triggers
10:09 - Audit Data with Triggers: PGSQL Phriday #007
10:24 - PGSQL Phriday #007 – Triggers for tracking changes in a table
10:34 - PGSQL Phriday #007: The Art of the Trigger
12:43 - Postgres 16 highlight - require_auth for libpq
13:23 - Supavisor - Postgres connection pooler
13:45 - Fun with PostgreSQL puzzles: Finding shortest paths and travel costs with functions
14:09 - How collation of punctuation and whitespace works
14:28 - Setting Up PostgreSQL Failover and Failback, the Right Way!
14:49 - PostgreSQL Schema: Learning PostgreSQL with Grant
15:13 - Partitioning
15:30 - Joël Cattin
15:39 - Developer Documentation With Grant Willcox | Rubber Duck Dev Show 81
15:59 - Outro

#postgres #postgresql

[jaimeduncan]

What we need is indirect indexes (optative). This channel does not get more than 1000 views for a video on average. And the videos are excellent and relevant. They need to make that change in other for Postgress to grow. Even with the UBER debacle, and even with test code showing massive advantage, the maintainers and the corporations that sale PostgreSQL derived software insist on doing nothing.