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
------
REL9_5_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/02bfd6d415bfacdf16a273420fd86c67189556ff

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