Max Sharnoff 5eb1738e8b Rework walkeeper protocol to use libpq (#366) ...

Most of the work here was done on the postgres side. There's more
information in the commit message there.
 (see: 04cfa326a5)

On the WAL acceptor side, we're now expecting 'START_WAL_PUSH' to
initialize the WAL keeper protocol. Everything else is mostly the same,
with the only real difference being that protocol messages are now
discrete CopyData messages sent over the postgres protocol.

For the sake of documentation, the full set of these messages is:

  <- recv: START_WAL_PUSH query
  <- recv: server info from postgres   (type `ServerInfo`)
  -> send: walkeeper info              (type `SafeKeeperInfo`)
  <- recv: vote info                   (type `RequestVote`)

  if node id mismatch:
    -> send: self node id (type `NodeId`); exit

  -> send: confirm vote (with node id) (type `NodeId`)

  loop:
    <- recv: info and maybe WAL block  (type `SafeKeeperRequest` + bytes)
         (break loop if done)
    -> send: confirm receipt           (type `SafeKeeperResponse`)

2021-08-13 11:25:16 -07:00

..

src

Rework walkeeper protocol to use libpq (#366)

2021-08-13 11:25:16 -07:00

tests

bin_ser: expand serialize error type, add serialized_size

2021-05-19 14:36:41 -07:00

Cargo.toml

Introduce authentication v0.1.

2021-08-11 20:05:54 +03:00