search

onemoredata / bagger

Massive log storage in PostgreSQL
BSD 2-Clause "Simplified" License
9 stars 0 forks source link

Add tools to prevent changes to Lenkwerk if agent is not replicating #76

Open einhverfr opened 8 months ago

einhverfr commented 8 months ago

One option would be to have a function which checks that the replication slot is in use and raises an error if not. Some other checks could be added as well. We need to think this through carefully and then add them.

This also means that on connection failure, schaufels should just stop and remain stopped until the effort is made to start them via the Lenkwerk agent.

einhverfr commented 8 months ago

For now, I think the simplest would be to check if the replication slot is set up and if it is active. this could be done on PGObject connection as a basic check.

einhverfr commented 8 months ago

On further thought this would impact testability in important ways. I think this problem needs more thought and we should bump to research after 1.0