forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit5436cb3
committed
Fix end LSN determination in recently added test
The test added in commite44dae0 has a thinko: it wants to readinfo about a few WAL records, but it obtains the LSN of the final recordto read by asking for the WAL insert position; however,pg_get_wal_records_info only accepts to read up to the flush position(cf. IsFutureLSN()). In normal conditions there is no difference, sincethe last record written by the preceding loop is known flushed and it'sthe one the test wants; but it's possible to have some other processinsert another WAL record that isn't flushed, and that causes the wholetest to explode.Fix by having pg_get_wal_records_info() read only up to the flushedposition. Backpatch to 15, which is where pg_walinspect appeared.Author: Karina Litskevich <litskevichkarina@gmail.com>Discussion:https://postgr.es/m/a5559c95-52c3-5eea-cd63-9b4f1c70ff96@gmail.com1 parent2655ecd commit5436cb3
1 file changed
+1
-1
lines changedLines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
60 | 60 | | |
61 | 61 | | |
62 | 62 | | |
63 | | - | |
| 63 | + | |
64 | 64 | | |
65 | 65 | | |
66 | 66 | | |
| |||
0 commit comments
Comments
(0)