Re: prevent immature WAL streaming
Alvaro Herrera <alvherre@alvh.no-ip.org>
Attachments
- v6-0001-Implement-FIRST_IS_ABORTED_CONTRECORD.patch (text/x-diff)
On 2021-Sep-15, Kyotaro Horiguchi wrote: > + CopyXLogRecordToWAL(rechdr->xl_tot_len, isLogSwitch, > + flags & XLOG_SET_ABORTED_PARTIAL, > + rdata, StartPos, EndPos); > > The new xlog flag XLOG_SET_ABORTED_PARTIAL is used only by > RM_XLOG_ID/XLOG_OVERWRITE_CONTRECORD records, so the flag value is the > equivalent of the record type. In the new version I removed all this; it was wrong. > + if (set_aborted_partial) > + pagehdr->xlp_info |= XLP_FIRST_IS_ABORTED_PARTIAL; > + > > I'm not sure about the reason for the change from the previous patch > (I might be missing something), this sets the flag on the *next* page > of the page where the record starts. So in the first place we > shouldn't set the flag there. You're right, this code is wrong. And in fact I had already noticed it yesterday, but much to my embarrasment I forgot to fix it. Here is a fixed version, where I moved the flag set back to AdvanceXLInsertBuffer. I think doing it anywhere else is going to be very painful. AFAICT we do the right thing now, but amusingly we don't have any tooling to verify that the XLP flag is set in the page where we want it. With this patch we now have two recptrs: the LSN of the broken record, and the LSN of the missing contrecord. The latter is where to start writing WAL after recovery is done, and the former is currently unused but we could use it to double-check that we're aborting (forgetting) the correct record. I didn't try to implement that, but IIUC it is xlogreader that would have to do that. -- Álvaro Herrera 39°49'30"S 73°17'W — https://www.EnterpriseDB.com/ "Si quieres ser creativo, aprende el arte de perder el tiempo"
Commits
-
Fix determination of broken LSN in OVERWRITTEN_CONTRECORD
- ef41c3fd6c86 13.6 landed
- d24dac954906 14.2 landed
- 9c6ab1ef3382 12.10 landed
- 72cf39d51ade 10.20 landed
- 44bd3ed332d6 15.0 landed
- 2c3fddcbbd8a 11.15 landed
-
Fix instability in 026_overwrite_contrecord.pl test.
- b66767b56b1c 15.0 landed
- 9959a078f2d7 12.10 landed
- 5a3240cf6b2e 13.6 landed
- 4dc2cb74d00e 11.15 landed
- 3aa858c8932e 14.2 landed
- 18ce21768a80 10.20 landed
-
Fix typo
- f914b8badc21 12.9 landed
- c3bda112ebe2 10.19 landed
- 7c0a78f08998 13.5 landed
- 3aa572b8b296 11.14 landed
- 9b6194eb0aa5 9.6.24 landed
-
Change recently added test code for stability
- 79c7fe1af82d 14.1 landed
- 6287b8e195f3 11.14 landed
- 5ec87619bc5d 9.6.24 landed
- 4b7abbe48a11 12.9 landed
- 41cce2326135 10.19 landed
- 2cdf97fd1ec8 13.5 landed
- 010e5233733a 15.0 landed
-
Remove unstable, unnecessary test; fix typo
- d186d233dfde 15.0 landed
- 0ce67bce0071 14.1 landed
-
Repair two portability oversights of new test
- e3731bac52cf 14.1 landed
- d03bca4d70c2 15.0 landed
-
Fix WAL replay in presence of an incomplete record
- 64a8687a6891 14.1 landed
- ff9f111bce24 15.0 landed
- d9fe2cc7dd3e 10.19 landed
- cfedb279a6b8 11.14 landed
- 1df0a914d58f 12.9 landed
- 1d97d3d0867f 13.5 landed
- 148c6ee3be39 9.6.24 landed
-
Document XLOG_INCLUDE_XID a little better
- c1d1ae1db237 14.0 landed
- ade24dab97a2 15.0 landed
-
Revert "Avoid creating archive status ".ready" files too early"
- e456167a8af4 12.9 landed
- c801c3a1ff73 11.14 landed
- aa8bd0890bb2 14.0 landed
- 9aaf7dbff36f 10.19 landed
- 96b665083eb7 15.0 landed
- 518621c40b23 13.5 landed
- 121cdaff1068 9.6.24 landed
-
Avoid creating archive status ".ready" files too early
- 5065aeafb0b7 12.9 cited
-
Fix scenario where streaming standby gets stuck at a continuation record.
- 066871980183 11.0 cited
-
Teach xlogreader to follow timeline switches
- 1148e22a82ed 10.0 cited
-
Forbid using pg_xlogfile_name() and pg_xlogfile_name_offset() during
- 370f770c15a4 9.0.0 cited