Stefanos Mousafeiris
Stefanos Mousafeiris
@balegas @robacourt should we close this issue and open new ones for specific improvements?
Picking this up as it has become quite necessary with the deploying of multiple examples and sharing of postgres instances.
We now provide the `onError` handler and have docs for this use case, and we have https://github.com/electric-sql/electric/pull/2184 as well to improve on it. Should we close this issue?
@alco just checking if what I'm thinking based on what you're saying is the same as what you're proposing, but we could do a mixed approach where on every publication...
@robacourt did we end up introducing any endpoint for a controlled shutdown of a single Electric that cleans up the replication slot? If not (cause I don't see one), should...
Based on a discussion with @robacourt I've created a separate `ShapeCleaner` process that handles the cleanups, and opened a followup PR https://github.com/electric-sql/electric/pull/2663 that removes the cleanup logic from everywhere else.
@robacourt @icehaunter if you can also review https://github.com/electric-sql/electric/pull/2663 along with this PR - can be merged separately or I can merge them together before going to main
Closing in favour of https://github.com/electric-sql/electric/pull/2672 - please do have a look at that one instead
Closing this as it has been addressed
Potenitally "live" requests still get held for 20sec and return an "up-to-date" but also mark whether replication is active so the client can decide what to do?