When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)

When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)

When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)

When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)

When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)

When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)

When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)

When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)

When the WAL record is divided into 2 files, both xl_info and xl_rmid are in one
file, and the checksum is in the other. Then, when processing the first file,
xl_info and xl_rmid could have been changed, but not the checksum, since it is
in another file. When processing the next file, the checksum would also not have
been changed since xl_info and xl_rmid are in the previous file. This led to the
fact that we could get a recovery error stating that the checksum did not
converge.

Fix this by reading and processing records from previous and next files,
regardless of which part of the records divided into 2 files is in the current
file.
These changes also revealed a number of errors in the tests related to incorrect
filling of the xlp_rem_len header field. These errors have also been fixed.

Ticket: ADBM-2436
(cherry picked from commit cfcf088)