Re: Background writer and checkpointer in crash recovery
Amul Sul <sulamul@gmail.com>
From: Amul Sul <sulamul@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>,
Aleksander Alekseev <aleksander@timescale.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-08-02T13:40:20Z
Lists: pgsql-hackers
On Mon, Aug 2, 2021 at 6:47 PM Robert Haas <robertmhaas@gmail.com> wrote: > > On Mon, Aug 2, 2021 at 1:37 AM Thomas Munro <thomas.munro@gmail.com> wrote: > > I pushed 0001. > > That's great. I just realized that this leaves us with identical > RequestCheckpoint() calls in two nearby places. Is there any reason > not to further simplify as in the attached? > +1, also, can we just get rid off "promoted" flag? The only inconvenience is we might need to check three flags instead of one to perform the checkpoint at the end.
Commits
-
Clear ps display of startup process at the end of recovery
- 848c323c1295 15.0 landed
- fbb5f54b67c2 16.0 landed
-
Further simplify a bit of logic in StartupXLOG().
- 8f7c8e2bef2b 15.0 landed
-
Run checkpointer and bgwriter in crash recovery.
- 7ff23c6d277d 15.0 landed
-
Add some checkpoint/restartpoint status to ps display
- df9274adf309 14.0 cited
-
Start background writer during archive recovery. Background writer now performs
- cdd46c765488 8.4.0 cited