Beginner tips | Postgres.FM 055 | #PostgreSQL #Postgres podcast

[ 🇬🇧_🇺🇸 Check out the subtitles – we now edit them, chatgpt+manually! You can also try YouTube's auto-translation of them from English to your language; try it and share it with people interested in Postgres!] Nikolay and Michael discuss 10 beginner tips Nikolay recently shared — they go into a bit more detail on each, and even disagree a little on one or two!

Here are some links to some things they mentioned:


0:00 Introduction

3:21 Tip 1: tuples are physical versions of rows

7:15 Tip 2: always use EXPLAIN (ANALYZE, BUFFERS)

10:36 Tip 3: throw away pgAdmin

17:34 Tip 4: enable as much logging as you can afford

22:05 Tip 5: install pg_stat_statements

25:04 Tip 6: run experiments on realistic data sets (use thin cloning and branching)

29:48 Tip 7: make sure data checksums are enabled

34:17 Tip 8: tune autovacuum to run frequently and move faster

37:01 Tip 9: query optimization will eventually be more important than configuration tuning

39:20 Tip 10: indexes need to be rebuilt, unfortunately, since their health decline over time

44:12 Bonus tip: the official documentation, release notes, and source code comments/readmes are your friends!

~~~

~~~

Postgres FM is brought to you by:

~~~

[kirkwolak]

do you only rebuild indexes based on bloat? Is this something you would schedule NIGHTLY (scan, and reindex anything that is bloated?)
Does the bloat % ever become "flexible" based on the table? I would assume you wouldn't want to do it only once a week (on weekends) if bloated? (in that case, maybe a lower bloat percentage)?