From: Michael Paquier <michael@paquier.xyz>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Subject: Re: file cloning in pg_upgrade and CREATE DATABASE
Date: Fri, 19 Oct 2018 08:50:46 +0900
Message-ID: <20181018235046.GA2099@paquier.xyz> (raw)
In-Reply-To: <d4bc3dae-fdea-2407-5629-cac68be893a3@2ndquadrant.com>
References: <20181003014409.GC2609@paquier.xyz>
<20181003020706.hykmk4vmy6brovoj@alvherre.pgsql>
<20181010195002.GA7806@momjian.us>
<325b5baf-adcc-9954-2a55-d67b4f3155f0@2ndquadrant.com>
<d4bc3dae-fdea-2407-5629-cac68be893a3@2ndquadrant.com>
On Thu, Oct 18, 2018 at 11:59:00PM +0200, Peter Eisentraut wrote:
> New patch that removes all the various reflink modes and adds a new
> option --clone that works similar to --link. I think it's much cleaner now.
Thanks Peter for the new version.
+
+ {"clone", no_argument, NULL, 1},
+
{NULL, 0, NULL, 0}
Why newlines here?
@@ -293,6 +300,7 @@ usage(void)
printf(_(" -U, --username=NAME cluster superuser (default \"%s\")\n"), os_info.user);
printf(_(" -v, --verbose enable verbose internal logging\n"));
printf(_(" -V, --version display version information, then exit\n"));
+ printf(_(" --clone clone instead of copying files to new cluster\n"));
printf(_(" -?, --help show this help, then exit\n"));
printf(_("\n"
An idea for a one-letter option could be -n. This patch can live
without.
+ pg_fatal("error while cloning relation \"%s.%s\": could not open file \"%s\": %s\n",
+ schemaName, relName, src, strerror(errno));
The tail of those error messages "could not open file" and "could not
create file" are already available as translatable error messages.
Would it be better to split those messages in two for translators? One
is generated with pg_fatal("error while cloning relation \"%s.%s\":
could not open file \"%s\": %s\n",
+ schemaName, relName, src, strerror(errno));
The tail of those error messages "could not open file" and "could not
create file" are already available as translatable error messages.
Would it be better to split those messages in two for translators? One
is generated with PG_VERBOSE to mention that cloning checks are
done, and the second one is fatal with the actual errors.
Those are all minor points, the patch looks good to me.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
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, peter.eisentraut@2ndquadrant.com, bruce@momjian.us, alvherre@2ndquadrant.com
Subject: Re: file cloning in pg_upgrade and CREATE DATABASE
In-Reply-To: <20181018235046.GA2099@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