pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
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: Wed, 3 Oct 2018 16:20:03 +0900
Message-ID: <20181003072003.GG2609@paquier.xyz> (raw)
In-Reply-To: <20181003020706.hykmk4vmy6brovoj@alvherre.pgsql>
References: <20181003014409.GC2609@paquier.xyz>
	<20181003020706.hykmk4vmy6brovoj@alvherre.pgsql>

On Tue, Oct 02, 2018 at 11:07:06PM -0300, Alvaro Herrera wrote:
> I see.  Peter is proposing to have a fourth mode, essentially
> --transfer-mode=clone-or-copy.

Yes, a mode which depends on what the file system supports.  Perhaps
"safe" or "fast" could be another name, in the shape of the fastest
method available which does not destroy the existing cluster's data.

> Thinking about a generic tool that wraps pg_upgrade (say, Debian's
> wrapper for it) this makes sense: just use the fastest non-destructive
> mode available.  Which ones are available depends on what the underlying
> filesystem is, so it's not up to the tool's writer to decide which to
> use ahead of time.

This could have merit.  Now, it seems to me that we have two separate
concepts here, which should be addressed separately:
1) cloning file mode, which is the new actual feature.
2) automatic mode, which is a subset of the copy mode and the new clone
mode.  What I am not sure when it comes to that stuff is if we should
consider in some way the link mode as being part of this automatic
selection concept..
--
Michael

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (42+ messages)  latest in thread

Message-ID: <20181003072003.GG2609@paquier.xyz>
Permalink:  ../20181003072003.GG2609@paquier.xyz/
Also on:    postgresql.org/message-id/20181003072003.GG2609@paquier.xyz

 · 

reply

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: michael@paquier.xyz, alvherre@2ndquadrant.com, peter.eisentraut@2ndquadrant.com, bruce@momjian.us
  Subject: Re: file cloning in pg_upgrade and CREATE DATABASE
  In-Reply-To: <20181003072003.GG2609@paquier.xyz>

* 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