There are many possible problems, could you share your command line? For example. Dump on SAME drive as the DB files, can produce disk contention. Dump across the network, can have packet collision of network latency. I dump 20gb test server in a matter of a couple minutes here. But, I run multiple disk controllers, data drive one 1 iSCSI and archives on another iSCSI - both run SSD ... so obviously, in this design I am simply moving RAM from 1 gig channel to another 1 gig channel, both are private circuits - no network conflict, and I average no less than 1GBps A to B stack performance.
On Thu, Oct 18, 2018 at 8:25 AM Raghavendra Rao J S V < raghavendra...@gmail.com> wrote: > Hi All, > > We are using *pg_dump *backup utility in order to take the backup of the > database. Unfortunately,it is taking around 24hrs of time to take the > backup of 28GB database. Please guide me how to reduce the time and is > there any parameter need to be modified which will help us to reduce the > backup time. We are using Postgres 9.2 version > > *Note:-*Kindly suggest me options using pg_dump only. > > -- > Regards, > Raghavendra Rao > >
