Remove previous timeline ID from checkpoint.
authorRobert Haas <rhaas@postgresql.org>
Mon, 18 Apr 2022 20:01:13 +0000 (16:01 -0400)
committerRobert Haas <rhaas@postgresql.org>
Tue, 19 Apr 2022 12:26:12 +0000 (08:26 -0400)
commit77fe03bc10454ed3a00e71d1e0eeb711a3e95b9f
tree8878ced158f6bf68baa1a97c3425d824cc08e374
parent59b804658ff9fc97964a9296b9612d5039d5a3f3
Remove previous timeline ID from checkpoint.

Since recovery now always ends with an end-of-recovery record rather
than a checkpoint, a checkpoint never causes a timeline switch.
Therefore, it doesn't need to store a previous timeline ID and a
current timeline ID any more.

Note that this affects the signature of the SQL-callable function
pg_control_checkpoint().
doc/src/sgml/func.sgml
src/backend/access/rmgrdesc/xlogdesc.c
src/backend/access/transam/xlog.c
src/backend/access/transam/xlogrecovery.c
src/backend/utils/misc/pg_controldata.c
src/bin/pg_controldata/pg_controldata.c
src/bin/pg_resetwal/pg_resetwal.c
src/include/catalog/pg_control.h
src/include/catalog/pg_proc.dat