| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Minimize checkpointer and walwriter io during pg_restore |
| Date: | 2024-06-05 09:52:55 |
| Message-ID: | 90a122788a5d29778873036617d5c9d421c7596b.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, 2024-06-04 at 11:32 -0400, Ron Johnson wrote:
> > I would not set "fsync" to off. It won't make a measurable difference for
> > pg_restore, and it may break your database. The same applies to "full_page_writes".
>
> If the pg_restore fails, I'm dropping the database no matter what. A few more minutes
> to drop $PGDATA and re-run initdb won't be noticed compared to the length of the pg_restore.
The *cluster* would be corrupted.
You'd have to start with a new "initdb".
If you want that... but it is a high price for very moderate gains.
> > What might make a difference is if you use the --single-transaction option of
> > pg_restore.
>
> A single 4+TB transaction??
Yes, sure. Why not?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-06-05 12:22:26 | Re: Minimize checkpointer and walwriter io during pg_restore |
| Previous Message | Kashif Zeeshan | 2024-06-05 03:53:54 | Re: Unable to create publication |