| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | rlemaroi <remi(dot)le-marois(at)capgemini(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: dump restoration performance |
| Date: | 2015-09-30 02:38:28 |
| Message-ID: | CAB7nPqTB1ZzuXhNugF_9Xj8QUdD+A6qNAO5_ZqVGrFnZQ59cpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Sep 25, 2015 at 10:43 PM, rlemaroi <remi(dot)le-marois(at)capgemini(dot)com> wrote:
> Please how long does it take approximately to restore a 300 Go database using
> pg_restore ? Are there benchmarks for that ?
That's not an exact science and this is really application-dependent.
For example the more your schema has index entries to rebuild at
restore the longer it would take. There are as well ways to tune the
server to perform a faster restore, by for example increasing
maintenance_work_mem, disabling autovacuum, moving wal_level to
minimum, etc.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2015-09-30 17:06:46 | Re: Queries Per Second (QPS) |
| Previous Message | Bertrand Paquet | 2015-09-29 20:51:33 | Re: Performance problem with gin index |