Skip to content

fix: add proper timeout error; improve backoff logic on replication recovery#1697

Open
filipecabaco wants to merge 3 commits intomainfrom
fix/handle-timeout-better-backoff
Open

fix: add proper timeout error; improve backoff logic on replication recovery#1697
filipecabaco wants to merge 3 commits intomainfrom
fix/handle-timeout-better-backoff

Conversation

@filipecabaco
Copy link
Member

What kind of change does this PR introduce?

  • Properly log out the timeout error on replication connection
  • Improve backoff policy to include exponential backoff to provide more time to db instance to recover

@blacksmith-sh
Copy link
Contributor

blacksmith-sh bot commented Feb 4, 2026

Found 1 test failure on Blacksmith runners:

Failure

Test View Logs
test WAL bloat handling track PID changes during WAL bloat creation (Realtime.Integrati
on.RtChannelTest) › Parameters: %{serializer: RealtimeWeb.Socket.V2Serializer} › test/
integration/
rt_channel_test.exs:2301 › ** (MatchError) no match of right hand side value: %Postgrex
.Result{command: :select, columns: ["active_pid"], rows: [], num_rows: 0, connection_id
: 722, messages: []} › code: %{rows: [[new_db_pid]]} = Postgrex.query!(db_conn, active_
slot_query, [])/stacktrace
View Logs

Fix in Cursor

@filipecabaco filipecabaco force-pushed the fix/handle-timeout-better-backoff branch from faacf5e to ccaf7f9 Compare February 4, 2026 23:42
Copy link
Member

@edgurgel edgurgel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants