Oleksii Sholik comments

Results 129 comments of


                                            Oleksii Sholik

Electric should be resilient to disconnecting to Postgres

https://github.com/electric-sql/electric-next/pull/34 has been ready for review since last week. I keep rebasing it from time to time to resolve conflicts. It solves the core need of being able to resume...

Electric should be resilient to disconnecting to Postgres

https://github.com/electric-sql/electric-next/pull/205 makes Electric handle Postgres disconnection gracefully and reconnect when it's back up. There's no automated testing to verify this behaviour yet. I'll leave this issue open until we have...

Feature request: Drop replication connection when there's no active shapes and there's not a bigger backlog of wal to process

But wouldn't checking the WAL size periodically cause the database server to wake up anyway?

Feature request: Drop replication connection when there's no active shapes and there's not a bigger backlog of wal to process

@msfstef From the original description: > periodically check the wal size and wake up the publication to process data when it grows to large this is highly dependent on the...

Feature request: Drop replication connection when there's no active shapes and there's not a bigger backlog of wal to process

The first iteration of this is implemented in https://github.com/electric-sql/electric/pull/3126. The next step is to figure out a better strategy for waking up the DB connection. The dumb periodic check works...

Feature request: Drop replication connection when there's no active shapes and there's not a bigger backlog of wal to process

Fine, this is the easiest strategy to implement. I never thought this was the crux of the feature request because we have almost all of the pieces already in place:...

Feature request: Drop replication connection when there's no active shapes and there's not a bigger backlog of wal to process

Hey @felix-quotez . Thanks for sharing your perspective! I have a POC implemented in https://github.com/electric-sql/electric/pull/3126 and I have tested it with Neon to make sure it lets Neon shut down...

Feature request: Drop replication connection when there's no active shapes and there's not a bigger backlog of wal to process

@felix-quotez Just letting you know that is feature is implemented in `main`. You can start using it by pulling `electricsql/electric:canary` from Docker Hub. The documentation preview is available [here](https://deploy-preview-3273--electric-next.netlify.app/docs/api/config#electric-replication-idle-timeout).

Tune PG connection pool to serve initial syncs

@icehaunter That's not pool-related, it's a query running for longer than the default query timeout.

Tune PG connection pool to serve initial syncs

@magnetised `ownership_timeout` is specific to the [`DBConnection.Ownership`](https://hexdocs.pm/db_connection/DBConnection.Ownership.html) pool which one can use in place of the default [`DBConnection.ConnectionPool`](https://hexdocs.pm/db_connection/DBConnection.ConnectionPool.html). `timeout` is an option you pass to [`Postgrex.query()`](https://hexdocs.pm/postgrex/Postgrex.html#query/4-options). It is set to...