Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7bSN-0001Kh-He for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Oct 2018 07:20:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1g7bSI-0006v0-AU for pgsql-hackers@arkaria.postgresql.org; Wed, 03 Oct 2018 07:20:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7bSH-0006tv-HP for pgsql-hackers@lists.postgresql.org; Wed, 03 Oct 2018 07:20:22 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1g7bS8-0006ts-3A for pgsql-hackers@postgresql.org; Wed, 03 Oct 2018 07:20:20 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 7EEE8B5F; Wed, 3 Oct 2018 03:20:09 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 03 Oct 2018 03:20:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=lOcf4CnDBTRMV5oMa811Y+yT9do vAYAAu6AnBJ2a1U4=; b=L/wvOkUzUlSKERJqLpojhTxtNHNvPFJHKh/Zh+wBFD7 PjL/29vPljwWHBW4Y/dj4/AyudeRUVY09HgxZEepMC9Y18WYqgsRMeEnnRvQoOhT EL2wsjYV22QmKIKxhRF4ZJVja1H9+MVPQ9aDxCPfsQuIac42SQA/CI125pCIYrx+ UEaUFEMY20UNJyHatZgBOny+u05BNwiYrRI8C1oZMHe3pslDyyQmfvQTyys+SJ14 psBx0k8qwZmXFaX/7ZPPE7e0wU8v+dNUSbU2iWbKvywjUkd31tcJFpnnIBp5J9xp VrWTazIWIPaF0XDD/cfZ6e9QbFrnPFT/VtEcjp/50gg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=lOcf4C nDBTRMV5oMa811Y+yT9dovAYAAu6AnBJ2a1U4=; b=bZzZ3exIM9iF8C8NxHRs5h WE7eUF04cJ8Kc6zL6cpc/OWPob80EjMbGfd7uDBXR32YbJqyNZMaygMFgZb6j9Li cZWRyodvI3n/TQttv7oE3961tFzfp1rPWMNINPpOouoVLZCl21IhEF4Pev1KrONp 0N2xe2HytmBrN9b/GD6dv9BP7/cXa8mbB5EZXphsGrBNrBW+3/4EzoTxSXSlykai 7ryNdxMbtoNWwyvAi51qS300eUUHXT1cZJHIwkc4erTTkUuGHBGEVjoICQPsHXyF xjgybxbDDVoz8HNgKUY6JedsnK6vdeLRYah9b+5KX9w/n0D4AGsJr0ZfrWwpNUJw == X-ME-Sender: X-ME-Proxy: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id EA46DE4074; Wed, 3 Oct 2018 03:20:06 -0400 (EDT) Date: Wed, 3 Oct 2018 16:20:03 +0900 From: Michael Paquier To: Alvaro Herrera Cc: Peter Eisentraut , pgsql-hackers , Bruce Momjian Subject: Re: file cloning in pg_upgrade and CREATE DATABASE Message-ID: <20181003072003.GG2609@paquier.xyz> References: <20181003014409.GC2609@paquier.xyz> <20181003020706.hykmk4vmy6brovoj@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FLPM4o+7JoHGki3m" Content-Disposition: inline In-Reply-To: <20181003020706.hykmk4vmy6brovoj@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --FLPM4o+7JoHGki3m Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --FLPM4o+7JoHGki3m Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlu0baMACgkQnvQgOdby QH1hvw//VV9UNJKBK08TlPQ+o9cBjhOjkAlXMQt/mrKocNh2ssXZxmqDaFw+xpJ5 UhSxUt1fVLM79LkUsspawmgTXeZiHqZAg/EoSrPI5KmAFKbP2sDMHFbi0tflS2yc aRzFxaykCt09F+VZpVwxwoyLb5sPU+obqXE2swA2KelsDc5eruwWbbaqbxFYz/Cd cEpgX8RYWHAQbv452c+15m2Qylq6r1f5/daKQSnAa9e1qyLMmnGK+ZCBhHXyUN4z r9ao5fCRbStYrdaMXdPUBfZPNtHFYpBICUKJ3C8510WblM+L8hV4x6lfGCtB/GyN 41lmP0Y+5VOW4Jg/4aOAENj2psUyOFYu2obI+PxOoDOKsfEXrnI41QbEl9q2SZNd ZxGKlS/igYds098k0ORPF8ywTmjm8CjT/rTIX2TmuhxseOahZfwvUbqjQYs7hZRw Glc0aYV/aa3WzRU49dUZ9M4mMKuTQ/eudAXqheRw+mmCaKUYBau92tPTGCco9cOb y74l7/BUBoCNus0Zxd1KwP4XEXktV+1SgDKQqZi9kTPdJXTgJ8eIIEwCpxIKbwCj BPHQaeekwM38gYUc0u+DO1UZ1pO0IrIh1idFFphib8I6WnZfX8J1enRQg5Giaz1V dKgDjZPSAzbFccKZJpGDAhnd3JjEzbJvG4UEMYpwUAq1caDyKJU= =qwy0 -----END PGP SIGNATURE----- --FLPM4o+7JoHGki3m--