Обсуждение: Request for Guidance on Reducing PostgreSQL DB Restoration Time

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender immediately by email or delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. The opinion expressed in this mail is that of the sender and does not necessarily reflect that of Titan. WARNING: Despite best possible precautionary measures taken by Titan Company Limited, computer viruses can be transmitted via email. The recipient should check and scan this email and any attachments for the presence of viruses. Titan Company Limited accepts no liability for any damage caused by any virus transmitted by this email. *******************************************************************************************************************

Sensitivity: Internal

Hi Madhumitha,

P {margin-top:0;margin-bottom:0;}

Could you please advise us on how we can optimize or reduce the restoration time?

I suggest asking this in the pgsql-performance mailing list. Have a look at this first before posting: https://wiki.postgresql.org/wiki/Guide_to_reporting_problems

Just off the cuff, you have to find the actual bottleneck first. In case you already have evidence to rule out everything else, you can have a look on this page for some options: https://www.postgresql.org/docs/current/populate.html.     

Kind regards,

Mircea Cadariu