forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit69059d3
committed
In TrimCLOG(), don't reset XactCtl->shared->latest_page_number.
Since the CLOG page number is not recorded directly in the checkpointrecord, we have to use ShmemVariableCache->nextXid to figure out thelatest CLOG page number at the start of recovery. However, as recoveryprogresses, replay of CLOG/EXTEND records will update our notion ofthe latest page number, and we should rely on that being accuraterather than recomputing the value based on an updated notion ofnextXid. ShmemVariableCache->nextXid is only an approximationduring recovery anyway, whereas CLOG/EXTEND records are anauthoritative representation of how the SLRU has been updated.Commit0fcc2de makes thissimplification possible, as before that change clog_redo() mighthave injected a bogus value here, and we'd want to get rid ofthat before entering normal running.Patch by me, reviewed by Heikki Linnakangas.Discussion:http://postgr.es/m/CA+TgmoZYig9+AQodhF5sRXuKkJ=RgFDugLr3XX_dz_F-p=TwTg@mail.gmail.com1 parent0fcc2de commit69059d3
1 file changed
+0
-5
lines changedLines changed: 0 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
773 | 773 | | |
774 | 774 | | |
775 | 775 | | |
776 | | - | |
777 | | - | |
778 | | - | |
779 | | - | |
780 | | - | |
781 | 776 | | |
782 | 777 | | |
783 | 778 | | |
| |||
0 commit comments
Comments
(0)