Re: file cloning in pg_upgrade and CREATE DATABASE - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: file cloning in pg_upgrade and CREATE DATABASE
Date
Msg-id 20181003013502.gvb5rkopfxtqk2yh@alvherre.pgsql
Whole thread Raw
In response to Re: file cloning in pg_upgrade and CREATE DATABASE  (Michael Paquier <michael@paquier.xyz>)
Responses Re: file cloning in pg_upgrade and CREATE DATABASE  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Relax transactional restrictions on ALTER ENUM ... ADD TYPE (redux)
Next
From: Michael Paquier
Date:
Subject: Re: file cloning in pg_upgrade and CREATE DATABASE