Refactor pg_rewind for more clear decision making.
authorHeikki Linnakangas <[email protected]>
Wed, 4 Nov 2020 09:21:09 +0000 (11:21 +0200)
committerHeikki Linnakangas <[email protected]>
Wed, 4 Nov 2020 09:21:09 +0000 (11:21 +0200)
commiteb00f1d4bf96bdba236bcc089f3ae94db9b7c603
tree1f5b070298ec7d383c1bbf92c8dca94062eb03f1
parentffb4e27e9c5ea87f9fecb7036dfc7cc1f38169b6
Refactor pg_rewind for more clear decision making.

Deciding what to do with each file is now a separate step after all the
necessary information has been gathered. It is more clear that way.
Previously, the decision-making was divided between process_source_file()
and process_target_file(), and it was a bit hard to piece together what
the overall rules were.

Reviewed-by: Kyotaro Horiguchi, Soumyadeep Chakraborty
Discussion: https://www.postgresql.org/message-id/0c5b3783-af52-3ee5-f8fa-6e794061f70d%40iki.fi
src/bin/pg_rewind/copy_fetch.c
src/bin/pg_rewind/file_ops.c
src/bin/pg_rewind/filemap.c
src/bin/pg_rewind/filemap.h
src/bin/pg_rewind/libpq_fetch.c
src/bin/pg_rewind/parsexlog.c
src/bin/pg_rewind/pg_rewind.c