pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: marek.cvoren@gmail.com
Cc: pgsql-docs@postgresql.org
Subject: Re: Misleading
Date: Tue, 11 Apr 2017 12:14:37 -0400
Message-ID: <20170411161437.GE4667@momjian.us> (raw)
In-Reply-To: <cd5ff30e-d97c-126b-4e22-939e5ae85d74@2ndquadrant.com>
References: <20170328110253.2695.62609@wrigleys.postgresql.org>
	<cd5ff30e-d97c-126b-4e22-939e5ae85d74@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>

On Wed, Apr  5, 2017 at 12:28:46AM -0400, Peter Eisentraut wrote:
> On 3/28/17 07:02, marek.cvoren@gmail.com wrote:
> > My suggestion:
> >  - completely omit confusing default word:
> > `You can also specify user and port values, and whether you want the data
> > linked instead of copied.`
> 
> It's debatable whether that sentence is unclear, I think, but the change
> you propose actually loses the information about what mode is the
> default, which wouldn't be good.

I have applied the attached doc patch to clarify this.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Attachments:

pg_upgrade.diff (text/x-diff, 1.1K) download diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml new file mode 100644 index 49aaf51..bf58a0a *** a/doc/src/sgml/ref/pgupgrade.sgml --- b/doc/src/sgml/ref/pgupgrade.sgml *************** NET STOP postgresql-9.0 *** 336,343 **** Always run the <application>pg_upgrade</> binary of the new server, not the old one. <application>pg_upgrade</> requires the specification of the old and new cluster's data and executable (<filename>bin</>) directories. You can also specify ! user and port values, and whether you want the data linked instead of ! copied (the default). </para> <para> --- 336,343 ---- Always run the <application>pg_upgrade</> binary of the new server, not the old one. <application>pg_upgrade</> requires the specification of the old and new cluster's data and executable (<filename>bin</>) directories. You can also specify ! user and port values, and whether you want the data files linked ! instead of the default copy behavior. </para> <para>

view thread (3+ messages)

Message-ID: <20170411161437.GE4667@momjian.us>
Permalink:  ../20170411161437.GE4667@momjian.us/
Also on:    postgresql.org/message-id/20170411161437.GE4667@momjian.us

 ·  · 

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-docs@postgresql.org
  Cc: bruce@momjian.us, peter.eisentraut@2ndquadrant.com, marek.cvoren@gmail.com
  Subject: Re: Misleading
  In-Reply-To: <20170411161437.GE4667@momjian.us>

* 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