Kirill Petrov

Here is overview how Redis Enterprise takes consistent backup: https://redis.com/redis-enterprise/technology/backup-disaster-recovery/

@asure-king thanks for fix propose. It would be nice to fix CI and merge

@boldfield, I got the same issue and tried that JSON: > { "16393": { "loc": "/storage/test_restore/data/TBS_DATA", "link": "pg_tblspc/16393" }, "16394": { "loc": "/storage/test_restore/data/TBS_INDEXES", "link": "pg_tblspc/16394" }, "tablespaces": [ "16393","16394" ],...

we got the same issue on: Linux 4.16.9-1-ARCH wal-e 1.1.0 it's some king of concurrency issue: reducing `--pool-size 1` helps

@piyush-garg Before: ``` $ tkn version Client version: 0.24.0 ... $ time tkn task start --showlog hello I0906 19:28:32.642669 382538 request.go:665] Waited for 1.196621458s due to client-side throttling, not priority...

same happens with me: - clickhouse 19.8.5 - go 1.14 - go-clickhouse 1.3.0 I use conn string like that: ``` http://readwrite:*******@my-standalone-ch.ru:8123/default?read_timeout=10s&write_timeout=20s ``` ``` 2020.04.27 17:42:00.153602 [ 274 ] {} HTTPHandler-factory:...

Here is how to reproduce it on Go with docker-compose example: https://github.com/chobostar/pgbouncer-cancel-request ``` pgbouncer 1.12 postgres 11 ``` As said before, connections stuck inside `cancel_req_list`: ``` pgbouncer=# show lists; list...

Finally It's "almost" fixed with pgbouncer 1.16 ! https://github.com/pgbouncer/pgbouncer/releases/tag/pgbouncer_1_16_0 >Query cancel handling has been fixed. Under some circumstances, cancel requests would seemingly get stuck for a long time. This should...

No, a cause is not in `max_client_conn` ``` $ psql -h localhost -p 6432 -U pgbouncer -c "show version" version ------------------ PgBouncer 1.16.0 (1 row) $ psql -h localhost -p...

В зависимости от workload-а lock можно вешать по хешу таблицы куда идет вставка, а не использовать один хэш для всех спартицированных через утилиту таблиц.