More precise errors from initial pg_control check
authorPeter Eisentraut <[email protected]>
Fri, 8 Nov 2019 07:03:16 +0000 (08:03 +0100)
committerPeter Eisentraut <[email protected]>
Fri, 8 Nov 2019 07:03:16 +0000 (08:03 +0100)
commitb85e43feb3e837699239aba6b8e0f280a59417be
treed349f6fb09cf907e8125f5e3b528f7607e85d2d3
parente86c8ef243aad4570f66a406c81211f75774ced1
More precise errors from initial pg_control check

Use a separate error message for invalid checkpoint location and
invalid state instead of just "invalid data" for both.

Reviewed-by: Michael Paquier <[email protected]>
Discussion: https://www.postgresql.org/message-id/20191107041630[email protected]
src/backend/access/transam/xlog.c