pgsql: More precise errors from initial pg_control check

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: More precise errors from initial pg_control check
Date: 2019-11-08 07:17:46
Message-ID: E1iSyWg-0001Bl-Gi@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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 <michael(at)paquier(dot)xyz>
Discussion: https://www.postgresql.org/message-id/20191107041630.GK1768@paquier.xyz

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b85e43feb3e837699239aba6b8e0f280a59417be

Modified Files
--------------
src/backend/access/transam/xlog.c | 82 +++++++++++++++++++++++----------------
1 file changed, 48 insertions(+), 34 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Etsuro Fujita 2019-11-08 08:15:27 pgsql: postgres_fdw: Fix error message for PREPARE TRANSACTION.
Previous Message Peter Geoghegan 2019-11-08 01:12:33 pgsql: Use "low key" terminology in nbtsort.c.