Re: file cloning in pg_upgrade and CREATE DATABASE

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: file cloning in pg_upgrade and CREATE DATABASE
Date: 2018-11-08 04:56:23
Message-ID: 20181108045623.GD1222@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 07, 2018 at 06:42:00PM +0100, Peter Eisentraut wrote:
> -n is often used for something like "dry run", so it didn't go for that
> here. I suspect the cloning will remain a marginal option for some
> time, so having only a long option is acceptable.

Good point. I didn't consider this, and it is true that --dry-run is
used, pg_rewind being one example.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-11-08 04:58:34 Re: csv format for psql
Previous Message Michael Paquier 2018-11-08 04:45:25 Adding a TAP test checking data consistency on standby with minRecoveryPoint