Make sure text files end with a newline

borisz · borisz · commit 2d6f69fefb57 · 2023-12-31T14:57:26.000+01:00
diff --git a/0001_explain_analyze_buffers.md b/0001_explain_analyze_buffers.md
@@ -44,4 +44,4 @@ Don't think about the timing numbers when you're inside the optimization process
 
 Finally, when optimizing a query, if you managed to reduce the BUFFERS numbers, this means that to execute this query, Postgres will need fewer buffers in the buffer pool involved, reducing IO, minimizing risks of contention, and leaving more space in the buffer pool for something else. Following this approach may eventually provide a global positive effect for the general performance of your database.
 
-A blog post on this topic: [EXPLAIN (ANALYZE) needs BUFFERS to improve the Postgres query optimization process](https://postgres.ai/blog/20220106-explain-analyze-needs-buffers-to-improve-the-postgres-query-optimization-process)
+A blog post on this topic: [EXPLAIN (ANALYZE) needs BUFFERS to improve the Postgres query optimization process](https://postgres.ai/blog/20220106-explain-analyze-needs-buffers-to-improve-the-postgres-query-optimization-process)
diff --git a/0004_tuple_sparsenes.md b/0004_tuple_sparsenes.md
@@ -188,4 +188,4 @@ That's it for today – we discussed ctid. Sometime in the future, we'll continu
 
 [Subscribe](https://twitter.com/samokhvalov), share, like!
 
-Not to forget, I'm mirroring these tips in this GitLab repo: https://gitlab.com/postgres-ai/postgresql-consulting/postgres-howtos/
+Not to forget, I'm mirroring these tips in this GitLab repo: https://gitlab.com/postgres-ai/postgresql-consulting/postgres-howtos/
diff --git a/0006_pg_stat_statements_part_2.md b/0006_pg_stat_statements_part_2.md
@@ -44,4 +44,4 @@ Let's consider the meanings of various derived metrics obtained in such way:
 
 ---
 
-Tomorrow, we'll finish with step 3 of this pgss-related how-to.
+Tomorrow, we'll finish with step 3 of this pgss-related how-to.
diff --git a/0008_how_to_speed_up_pg_dump.md b/0008_how_to_speed_up_pg_dump.md
@@ -134,4 +134,4 @@ A good post about dealing with snapshots when making database dumps: ["Postgres
 
 ---
 
-That's it for today. Good dumping speeds in production (2+ TiB/h) to everyone!
+That's it for today. Good dumping speeds in production (2+ TiB/h) to everyone!
diff --git a/0009_lsn_values_and_wal_filenames.md b/0009_lsn_values_and_wal_filenames.md
@@ -86,4 +86,4 @@ This can be very helpful if you need to work with LSN values or WAL filenames or
 
 ---
 
-Thanks for reading! As usual: please share it with your colleagues and friends who work with #PostgreSQL.
+Thanks for reading! As usual: please share it with your colleagues and friends who work with #PostgreSQL.
diff --git a/0010_flamegraphs_for_postgres.md b/0010_flamegraphs_for_postgres.md
@@ -189,4 +189,4 @@ In this case, the planning time is really low, sub-millisecond – but I encount
 
 ---
 
-Was it useful? Let me know – and please share with your colleagues and friends who use #PostgreSQL!
+Was it useful? Let me know – and please share with your colleagues and friends who use #PostgreSQL!
diff --git a/0018_over_indexing.md b/0018_over_indexing.md
@@ -137,4 +137,3 @@ A couple of good reads on this topic:
   too): [LWLock: lockmanager](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/wait-event.lw-lock-manager.html)
 - [Postgres Partition Pains - LockManager Waits](https://kylehailey.com/post/postgres-partition-pains-lockmanager-waits)
   by [@kylelf_](https://twitter.com/kylelf_)
-

Original file line number	Diff line number	Diff line change
`@@ -44,4 +44,4 @@ Don't think about the timing numbers when you're inside the optimization process`
`44`	`44`
`45`	`45`	`Finally, when optimizing a query, if you managed to reduce the BUFFERS numbers, this means that to execute this query, Postgres will need fewer buffers in the buffer pool involved, reducing IO, minimizing risks of contention, and leaving more space in the buffer pool for something else. Following this approach may eventually provide a global positive effect for the general performance of your database.`
`46`	`46`
`47`		`-A blog post on this topic: [EXPLAIN (ANALYZE) needs BUFFERS to improve the Postgres query optimization process](https://postgres.ai/blog/20220106-explain-analyze-needs-buffers-to-improve-the-postgres-query-optimization-process)`
	`47`	`+A blog post on this topic: [EXPLAIN (ANALYZE) needs BUFFERS to improve the Postgres query optimization process](https://postgres.ai/blog/20220106-explain-analyze-needs-buffers-to-improve-the-postgres-query-optimization-process)`
Original file line number	Diff line number	Diff line change
`@@ -188,4 +188,4 @@ That's it for today – we discussed ctid. Sometime in the future, we'll continu`
`188`	`188`
`189`	`189`	`[Subscribe](https://twitter.com/samokhvalov), share, like!`
`190`	`190`
`191`		`-Not to forget, I'm mirroring these tips in this GitLab repo: https://gitlab.com/postgres-ai/postgresql-consulting/postgres-howtos/`
	`191`	`+Not to forget, I'm mirroring these tips in this GitLab repo: https://gitlab.com/postgres-ai/postgresql-consulting/postgres-howtos/`
Original file line number	Diff line number	Diff line change
`@@ -44,4 +44,4 @@ Let's consider the meanings of various derived metrics obtained in such way:`
`44`	`44`
`45`	`45`	`---`
`46`	`46`
`47`		`-Tomorrow, we'll finish with step 3 of this pgss-related how-to.`
	`47`	`+Tomorrow, we'll finish with step 3 of this pgss-related how-to.`
Original file line number	Diff line number	Diff line change
`@@ -134,4 +134,4 @@ A good post about dealing with snapshots when making database dumps: ["Postgres`
`134`	`134`
`135`	`135`	`---`
`136`	`136`
`137`		`-That's it for today. Good dumping speeds in production (2+ TiB/h) to everyone!`
	`137`	`+That's it for today. Good dumping speeds in production (2+ TiB/h) to everyone!`
Original file line number	Diff line number	Diff line change
`@@ -86,4 +86,4 @@ This can be very helpful if you need to work with LSN values or WAL filenames or`
`86`	`86`
`87`	`87`	`---`
`88`	`88`
`89`		`-Thanks for reading! As usual: please share it with your colleagues and friends who work with #PostgreSQL.`
	`89`	`+Thanks for reading! As usual: please share it with your colleagues and friends who work with #PostgreSQL.`
Original file line number	Diff line number	Diff line change
`@@ -189,4 +189,4 @@ In this case, the planning time is really low, sub-millisecond – but I encount`
`189`	`189`
`190`	`190`	`---`
`191`	`191`
`192`		`-Was it useful? Let me know – and please share with your colleagues and friends who use #PostgreSQL!`
	`192`	`+Was it useful? Let me know – and please share with your colleagues and friends who use #PostgreSQL!`