| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_basebackup compression |
| Date: | 2020-06-29 16:58:57 |
| Message-ID: | 1972C732-E881-4D77-82F4-EE3EE8E99695@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Jun 29, 2020, at 10:53 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> Correct. Unless you turn on SSL compression, which ias been deprecated a long time ago and is actually quite tricky (or even impossible) on most modern Linux distros.
Thanks for confirming--shortly after I posted I remembered that I'd noticed the same issue with the same tool once before (Rancher, FYI), and what it is doing is labeling the y-axis as "Mbps" when it's actually displaying MBps. So, LOL, data is appearing on my disk 8x faster than that UI shows it transferring over the network ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-06-29 17:10:12 | Re: After renaming a database the subscription ( logical replication) stay sticky to the old database (master) |
| Previous Message | Magnus Hagander | 2020-06-29 16:53:57 | Re: pg_basebackup compression |