Re: Minimize checkpointer and walwriter io during pg_restore

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Minimize checkpointer and walwriter io during pg_restore
Date: 2024-06-06 13:33:07
Message-ID: CANzqJaDQf16025tPN8h7b+5sEuVdciHFtJyJarQ9dhwNomGL9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Thu, Jun 6, 2024 at 8:54 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:

> On Thu, Jun 6, 2024 at 4:06 AM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
> wrote:
> [snip]
>
>> There are certainly negative effects of a large transaction, but I
>> thought you want
>> to optimize the performance of a "pg_restore". If you optimize one
>> thing, you will
>> certainly pessimize some other things. In the case at hand, you
>> shouldn't run a
>> heavy data modifying workload in the same database concurrently to the
>> large pg_restore.
>>
>
> pg_restore will be the only thing running.
>
> The mere size of a transaction can be a problem as such in other databases
>> like
>> Oracle, but not in PostgreSQL.
>>
>
> Understood. I'll see if I can run another test before the "real"
> migration starts.
>

And... --single-transaction conflicts with --jobs. Oh well.

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message M Sarwar 2024-06-06 21:06:05 How to find the view modified date and time and user name
Previous Message Ron Johnson 2024-06-06 12:54:01 Re: Minimize checkpointer and walwriter io during pg_restore