Fix incorrect error code in StartupReplicationOrigin().
authorAmit Kapila <[email protected]>
Mon, 30 Aug 2021 04:15:20 +0000 (09:45 +0530)
committerAmit Kapila <[email protected]>
Mon, 30 Aug 2021 04:15:20 +0000 (09:45 +0530)
ERRCODE_CONFIGURATION_LIMIT_EXCEEDED was used for checksum failure, use
ERRCODE_DATA_CORRUPTED instead.

Reported-by: Tatsuhito Kasahara
Author: Tatsuhito Kasahara
Backpatch-through: 9.6, where it was introduced
Discussion: https://postgr.es/m/CAP0=ZVLHtYffs8SOWcFJWrBGoRzT9QQbk+_aP+E5AHLNXiOorA@mail.gmail.com

src/backend/replication/logical/origin.c

index 01f88eaca89d2370e6f5d3a3c76d9476167ffe6d..cb1770c0d5dec3cf506b55dac867ef006cfdb459 100644 (file)
@@ -791,7 +791,7 @@ StartupReplicationOrigin(void)
    FIN_CRC32C(crc);
    if (file_crc != crc)
        ereport(PANIC,
-               (errcode(ERRCODE_CONFIGURATION_LIMIT_EXCEEDED),
+               (errcode(ERRCODE_DATA_CORRUPTED),
                 errmsg("replication slot checkpoint has wrong checksum %u, expected %u",
                        crc, file_crc)));