From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Faster pg_resore with autovacuum off? |
Date: | 2024-07-27 20:24:45 |
Message-ID: | CANzqJaCaLavwMjxnj+zQm+UfHBb9BjcXQ0fh0BK4nCtLBVLe7Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sat, Jul 27, 2024 at 4:06 PM Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:
> > On Jul 27, 2024, at 1:48 PM, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
> wrote:
> >
> > You can't forget to enable autovacuum when it's in the same script as
> the pg_restore.
>
> Similar argument applies to turning off fsync, which I have found to
> sometimes make a significant difference (depending on hardware).
>
> The other argument I've seen, that if there's a crash during restore
> you'll have a corrupted database, is bogus. What are you going to try to do
> with a database if there's a crash during restore???
>
Josh Berkus' blog post, which I linked to earlier, recommended that, and a
lot more, 10 years ago. It all still holds up. Bigger servers just means
some values need enlarging.
From | Date | Subject | |
---|---|---|---|
Next Message | Wasim Devale | 2024-07-28 04:04:52 | Re: Restoration query |
Previous Message | Scott Ribe | 2024-07-27 20:05:52 | Re: Faster pg_resore with autovacuum off? |