Arseny Sher 5e972ccdc4 WIP safekeeper walsender: read-write from single task. ...

- Use postgres_backend_async throughout safekeeper.
- Use Framed in postgres_backend_async, it allows polling interface and
  takes some logic.
- Do read-write from single task in walsender.

The latter turned out to be more complicated than I initially expected due to 1)
borrow checking and 2) anon Future types. 1) required SendRc<Refcell<...>>
construct just to satisfy the checker; 2) is currently done via boxing futures,
which is a pointless heap allocation in active path.

I'll probably try to workaround 2) with transmute, but it made me wonder whether
socket split, like it was done previously, would be better. It is also messy
though:
- we need to manage two tasks, properly join them and should on exit/error
  should join pgbackend back to leave it in valid state; pgbackend itself must
  swell a bit to provide splitted interface.
- issues with tls
- tokio::io::split has pointless mutex inside

fixing walreceiver and proxy is not done yet

2023-02-02 12:03:45 +04:00

..

src

WIP safekeeper walsender: read-write from single task.

2023-02-02 12:03:45 +04:00

Cargo.toml

Enable licenses check for 3rd-parties

2023-01-03 15:11:50 +01:00