Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall
Date
Msg-id 677ed9ca-8653-4c27-80ca-0ea763f0f21f@eisentraut.org
Whole thread Raw
In response to add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: add --no-sync to pg_upgrade's calls to pg_dump and pg_dumpall
List pgsql-hackers
On 03.05.24 19:13, Nathan Bossart wrote:
> This is likely small potatoes compared to some of the other
> pg_upgrade-related improvements I've proposed [0] [1] or plan to propose,
> but this is easy enough, and I already wrote the patch, so here it is.
> AFAICT there's no reason to bother syncing these dump files to disk.  If
> someone pulls the plug during pg_upgrade, it's not like you can resume
> pg_upgrade from where it left off.  Also, I think we skipped syncing before
> v10, anyway, as the --no-sync flag was only added in commit 96a7128, which
> added the code to sync dump files, too.

Looks good to me.




pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: CREATE DATABASE with filesystem cloning
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Slow catchup of 2PC (twophase) transactions on replica in LR