Features To Avoid? | Scaling Postgres 351

To get the show notes as well as get notified of new episodes, visit:
www.scalingpos...
In this episode of Scaling Postgres, we talk about some features you may want to avoid like commit_delay, index_cleanup off, & logon triggers, a way to detect a table rewrite and a zero downtime upgrade.
Want to learn more about Postgres performance?
Join my FREE training called Postgres Performance Demystified here: www.scalingpos...
Timestamps:
00:34 - commit_delay for better performance: a PostgreSQL benchmark
04:01 - VACUUM (INDEX_CLEANUP OFF) Considered Harmful
05:42 - Logon trigger in PostgreSQL
07:32 - When Does ALTER TABLE Require a Rewrite?
09:08 - A Major Postgres Upgrade with Zero Downtime
10:39 - Reads causing writes
11:58 - Reads causing writes in Postgres
12:20 - Indexing Partitioned Table Disaste
13:01 - Postgres Café: Deploying distributed PostgreSQL at scale with Citus Data
13:22 - How I got started as a developer & in Postgres with Daniel Gustafsson
13:35 - Consulting Corner
16:35 - Outro
#postgres #postgresql

[@minma02262]

Thumbs up. I like your channel. I'm learned postgres as my staple database, your channel helps a lot 👍

[@professortrog7742]

If there are lag spikes at regular intervals i usually first have a good look at the monitoring setup. Wouldn’t be the first time PMM is to blame.

[@ScalingPostgres]

Actually, it happened at random intervals. The average was maybe 15 minutes. It could happen with a delay from 5 to even 35+ minutes. Again, correlated with one table's vacuum conclusion.