-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inactive replication slot causing warnings on DO managed Postgres #1285
Comments
I edited my question after noticing some typos - not sure if this is picked up in Linear. |
Hey @jocubeit. This is expected behaviour for Electric. You can read more about the need to keep around a replication slot in our docs, here. The summary is that one replication slot is used to retain a history of transactions in Postgres that allows Electric to resume streaming transactions to clients after a restart. The other slot is temporary, it is only created when Electric is running and is used for its logical replication connection to Postgres. Could you share a screenshot of the DO email? |
I got the same email again this morning. What I'm not clear about is whether the |
Thanks for the additional context! To clarify: The other slot is persisted, Electric uses that to maintain a point in time which it can resuming streaming from after a shutdown/restart. You won't be able to delete the |
Hi,
I set up a single primary managed Postgres on Digital Ocean, and ElectricSQL in on their App Platform.
I have not created any tables or electrified anything yet. I also do not have any clients connecting yet.
I received a warning email this morning about Inactive or Lagging Replication Slots Detected.
I see that the replication slot named
electric_replication_out_defaultdb
is inactive while the one namedelectric_replication_out_defaultdb_rc
is active. The inactive slot is the cause of the warning.Is it supposed to be inactive? Does in become active when I connect a client? Is the inactive slot used?
Any advice much appreciated.
The text was updated successfully, but these errors were encountered: