Andrew Pogrebnoi

PBM-902: fix sharded cluster detection on mongo 6.0

3

Check for `db.adminCommand({ getCmdLineOpts: 1}).parsed.sharding.clusterRole` if `ConfigServerState` is anavaliable. Fixes https://jira.percona.com/browse/PBM-902

Physical backups improvements

12

### Added new command `pbm describe-restore` Outputs detailed information on the given restore. ``` $ pbm describe-restore 2022-08-03T09:25:54.4242858Z name: "2022-08-03T09:25:54.4242858Z" backup: "2022-07-28T12:10:13Z" type: logical status: done replsets: - name: rs1...

PBM-875: S3 concurrent download

5

Requesting parts of the source concurrently and then writing them sequentially into the destination. If the part comes too early, it will be sent to the buffer (heap) first. And...

Encrypts XLog pages while writing them to the segment file. This is just a POC without any proper key management.

As suggested by @dutow, since the tuples/XLog TDE data in the memory is decrypted, we should consider marking that memory as non-swappable. Or at least the memory with the encryption...

To ensure that cache wiping (master internal/keys etc) doesn't affect the DB

Need to spin up replica env and run basic `INSERT`, `UPDATE`, `DELETE` and `COPY FROM` scenarios. See `multi_insert` tests for `COPY ... FROM` (https://github.com/Percona-Lab/pg_tde/blob/main/sql/multi_insert.sql) And `insert_update_delete` tests for `INSERT`, `UPDATE`,...

Logical replication

2

Check how it works with encrypted WAL tuples. And fix if needed.

DELETE and UPDATE producing records with Replica Identity tuples in the XLog. These tuples/records are not encrypted. We should encrypt them. See `ExtractReplicaIdentity()` calls and XLog stuff in `pg_tde_delete()` and...