You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The WAL sync protocol only allows you to fetch frames for a range.
While the protocol does not have mechanism to determine what is the
latest frame on the server for pull, it does signal with HTTP status
code 400 when you attempt to read a frame that does not exists.
Let's use this signal to fix WAL pull logic not to fail always. In the
future, we might want to consider extending the protocol to allow
clients to proble for latest frame. That, however, will make the
protocol a bit more chatty, so I am trying to avoid that as long as I
can.
0 commit comments