Skip to content

Commit 9bd8f6c

Browse files
committed
Update 5 files
- /0004_tuple_sparsenes.md - /0005_pg_stat_statements_part_1.md - /0003_how_to_troubleshoot_long_startup.md - /0002_how_to_troubleshoot_and_speedup_postgres_restarts.md - /0001_explain_analyze_buffers.md
1 parent bbb8705 commit 9bd8f6c

5 files changed

+5
-3
lines changed

0001_explain_analyze_buffers.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
Originally from: [tweet](https://twitter.com/samokhvalov/status/1706689567355732052), [LinkedIn post](https://www.linkedin.com/feed/update/urn:li:activity:7112529621178347520/).
22

33
---
4+
45
# EXPLAIN ANALYZE or EXPLAIN (ANALYZE, BUFFERS?
56

67
When analyzing Postgres query execution plans, I always recommend using the `BUFFERS` option:

0002_how_to_troubleshoot_and_speedup_postgres_restarts.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
Originally from: [tweet](https://twitter.com/samokhvalov/status/1707147450044297673), [LinkedIn post](...).
22

33
---
4+
45
# How to troubleshoot and speed up Postgres stop and restart attempts
56

67
#PostgresMarathon day 2. Let's discuss PostgreSQL shutdown and restarts. It's not uncommon to see quite long and even failed shutdown/restart attempts. If it's happening inside an incident troubleshooting, it often can provoke emotions and additional mistakes.

0003_how_to_troubleshoot_long_startup.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
Originally from: [tweet](https://twitter.com/samokhvalov/status/1707466169245171773), [LinkedIn post](...).
22

33
---
4+
45
# How to troubleshoot long Postgres startup
56

67
#PostgresMarathon day 3. In [the previous post](./0002_how_to_troubleshoot_and_speedup_postgres_restarts.md), we discussed how to quickly stop or restart PostgreSQL. Now it's time to discuss what to do if you are trying to start your server but see this:

0004_tuple_sparsenes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ nik=# explain (analyze, buffers, costs off) select * from t1 where user_id = 101
179179
```
180180
– also just 4 buffer hits – same as for the approach with covering index and Index-Only Scan. Though, here we have Index Scan.
181181

182-
===
182+
---
183183

184184
That's it for today – we discussed ctid. Sometime in the future, we'll continue with xmin and xmax and a deep inspection of table/index pages for practical reasons.
185185

0005_pg_stat_statements_part_1.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,5 +79,4 @@ Assuming you successfully obtained 2 snapshots of pgss (remembering timestamp wh
7979
That's it for the part 1 of pgss-related howto, in next parts we'll talk about dM/dc and %M, and other practical aspects of pgss-based macro optimization.
8080

8181
Let me know if it was useful, and please share with your colleagues and any people who work with
82-
PostgreSQL.
83-
.
82+
PostgreSQL.

0 commit comments

Comments
 (0)