typos
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: pgsql-hackers@postgresql.org
Cc: Michael Paquier <michael@paquier.xyz>
Date: 2022-01-24T03:00:01Z
Lists: pgsql-hackers
Attachments
- 0001-incorrect-file-names-in-header-comment.patch (text/x-diff)
Most of this is new in v15 or doesn't affect user-facing docs so doesn't need to be backpatched. Feel free to ignore this for now and revisit in April... @Michael: I'm not sure what this is trying to say. 1e9475694b0ae2cf1204d01d2ef6ad86f3c7cac8 + First, scan the directory where the WAL segment files are written and + find the newest completed segment file, using as starting point the + beginning of the next WAL segment file. This is calculated independently + on the compression method used to compress each segment. I suppose it should say independently *of* the compression method, but then I still don't know what it means. I checked FindStreamingStart(). It that doesn't look like it's "calculated independently" - actually, it takes the compression method into account and explicitly handles each compression method. Is there any reason the user-facing docs need to say anything about this at all?
Commits
-
doc: Fix some grammar
- 11cd377f53bf 10.20 landed
- acd4f44fe1ab 11.15 landed
- fcc434047d09 12.10 landed
- 35893cc96856 13.6 landed
- 29d9da36b7b1 14.2 landed
-
Fix various typos, grammar and code style in comments and docs
- 410aa248e5a8 15.0 landed
-
doc: Describe calculation method of streaming start for pg_receivewal
- 1e9475694b0a 15.0 cited