11TB WAL, pgec Writes, Patroni 3 & Citus, PostgREST | Scaling Postgres 256

In this episode of Scaling Postgres, we discuss WAL growing to 11 Terabytes, pgec supporting writes, Patroni 3.0 & Citus for high availability, and setting up PostgREST.

Want to learn more about Postgres performance?

Timestamps:
00:00 - Intro
00:28 - 11TB WAL in PostgreSQL
02:11 - pgec reads: memory replicated cache, writes: PostgreSQL with a Redis API
03:23 - Patroni 3.0 & Citus: Scalable, Highly Available Postgres
04:53 - PostgREST: Get started with automated PostgreSQL APIs
05:53 - Handling integer sequence overflow without downtime in Postgres
06:28 - Introduction to Postgres Backups
07:53 - TLS setup on Postgres 15 – Common Practice
08:52 - Which is worse when working on production databases? Being drunk or tired?
09:25 - PostgreSQL 14 Internals
09:42 - PostgreSQL 16: part 4 or CommitFest 2023-01
10:00 - A PostgreSQL Developer’s Perspective: Five Interesting Patches From January’s Commitfest
10:20 - PGSqlPhriday #006: One Thing You Wish You Knew While Learning PostgreSQL: psql commands
10:56 - #PGSQLPhriday 006: Wrap Up & Summary
11:04 - Wait events
11:21 - Samay Sharma
11:30 - Monetizing Your Developer Content With Seb Wilgosz & Lucian Ghinda | Rubber Duck Dev Show 77
11:57 - Outro

#postgres #postgresql

[chackken]

Hey, would you consider episode about showing how to prepare postgres 13/14 failover and failback setup in something like keepalived cluster?
I tried to do something like this and it kinda works, but I know my knowledge of topic is minimal. Got two machines one master and one backup with replication. On failover event I stop master and add standby.signal to prevent writes, then on backup I remove this file and start database. System works as it should, but probably it can be done 100x better.

It would be great to compare my setup to advanced one.

Great channel, cheers!