From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Bruce Momjian <bruce@momjian.us>
Subject: Re: file cloning in pg_upgrade and CREATE DATABASE
Date: Tue, 2 Oct 2018 22:35:02 -0300
Message-ID: <20181003013502.gvb5rkopfxtqk2yh@alvherre.pgsql> (raw)
In-Reply-To: <20181002233248.GA2609@paquier.xyz>
On 2018-Oct-03, Michael Paquier wrote:
> There could be an argument for having an automatic more within this
> scheme, still I am not really a fan of this. When somebody integrates
> pg_upgrade within an upgrade framework, they would likely test if
> cloning actually works, bumping immediately on a failure, no? I'd like
> to think that copy should be the default, cloning being available as an
> option. Cloning is not supported on many filesystems anyway..
I'm not clear what interface are you proposing. Maybe they would just
use the clone-or-fail mode, and note whether it fails? If that's not
it, please explain.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, michael@paquier.xyz, peter.eisentraut@2ndquadrant.com, bruce@momjian.us
Subject: Re: file cloning in pg_upgrade and CREATE DATABASE
In-Reply-To: <20181003013502.gvb5rkopfxtqk2yh@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox