Re: pg_dump/pg_restore --jobs practical limit?

From: Marc Millas <marc(dot)millas(at)mokadb(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump/pg_restore --jobs practical limit?
Date: 2023-11-03 10:09:27
Message-ID: CADX_1aanC4gibvwJJeomUxgxTT9xw8gAvRctc4jwgNbSpJO9nQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Marc MILLAS
Senior Architect
+33607850334
www.mokadb.com

Testing pg_restore with different --jobs= values will be easier. pg_dump
> is what's going to be reading from a constantly varying system.
>
> Hello,
>
each time I do a replatforming of this kind, with DB up to 2 TB, I did
create the target DB, eventually needed users then the appropriate
databases, and finally, a simple script to pipe pg_dump into psql,
databases one by one.
So.. one thread. Each time, it was limited by the network bandwidth. My
last replatforming with a 10 Gb net and a 1.5 TB DB did show a transfer of
500 Mbytes per second (5Gbs) so.. less than an hour.
which is just fine. Launch it, have lunch, a coffee, and ...done for test.
For Prod, I am used to do it at the quietest night of the week end. and
have a nap ( a short one !)...:-)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ben Hancock 2023-11-03 13:18:19 Local postgres manual
Previous Message Inzamam Shafiq 2023-11-03 10:04:28 Re: Regarding HA, Failover and Load Balancing