Thread: pgsql: logical decoding: beware of an unset specinsert change

pgsql: logical decoding: beware of an unset specinsert change

From
Alvaro Herrera
Date:
logical decoding: beware of an unset specinsert change

Coverity complains that there is no protection in the code (at least in
non-assertion-enabled builds) against speculative insertion failing to
follow the expected protocol.  Add an elog(ERROR) for the case.

Branch
------
REL_11_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/05c7426bac43aa3f07c32f40c16a78712d1f0c87

Modified Files
--------------
src/backend/replication/logical/reorderbuffer.c | 2 ++
1 file changed, 2 insertions(+)