Commit 0a143c33 authored by Amit Kapila's avatar Amit Kapila

Fix incorrect error code in StartupReplicationOrigin().

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
parent e1efc5b4
...@@ -796,7 +796,7 @@ StartupReplicationOrigin(void) ...@@ -796,7 +796,7 @@ StartupReplicationOrigin(void)
FIN_CRC32C(crc); FIN_CRC32C(crc);
if (file_crc != crc) if (file_crc != crc)
ereport(PANIC, ereport(PANIC,
(errcode(ERRCODE_CONFIGURATION_LIMIT_EXCEEDED), (errcode(ERRCODE_DATA_CORRUPTED),
errmsg("replication slot checkpoint has wrong checksum %u, expected %u", errmsg("replication slot checkpoint has wrong checksum %u, expected %u",
crc, file_crc))); crc, file_crc)));
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment