-
Bug
-
Resolution: Done
-
Major
-
0.5
-
None
When run on a database managed by Django 1.8.6, after the connector is created with curl POST, an insertion to a table causes connector to crash. Message seen on connector log:
WARN Postgres|dbsvname|records-stream-producer Closing replication stream due to db connection IO exception... [io.debezium.connector.postgresql.RecordsStreamProducer]
Message seen on postgresql log:
LOG: starting logical decoding for slot "debezium"
DETAIL: streaming transactions committing after 0/2978F88, reading WAL from 0/2978F50
LOG: logical decoding found consistent point at 0/2978F50
DETAIL: There are no running transactions.
LOG: server process (PID 66012) was terminated by signal 11: Segmentation fault
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
Environment:
OS: Mac OS 10.12.3
zookeeper: debezium/zookeeper:0.5 docker image
kafka: debezium/kafka:0.5 docker image
connect: debezium/connect:0.5 docker image
postgres: ver 9.6 installed via homebrew
django: ver 1.8.6