Date: Mon, 20 Jun 2016 11:16:36 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: PostgreSQL-documentation <pgsql-docs@postgresql.org>
Subject: Re: Pg_upgrade and collation
Message-ID: <20160620151636.GB26992@momjian.us>
References: <20160617220935.GF19359@momjian.us>
 <20160617221158.GA143199@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160617221158.GA143199@alvherre.pgsql>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On Fri, Jun 17, 2016 at 06:11:58PM -0400, Alvaro Herrera wrote:
> > Frankly, pg_upgrade is, by definition, upgrading on the same server, so
> > I don't even see how they could have mismatched collation library
> > versions, but it seemed good to document it.
> 
> By this argument, the proposed patch seems pointless to me.
> 
> > The larger issue of moving clusters is a separate issue that needs
> > documentation somewhere else.
> 
> Sure.

In looking at the docs, it seems it would go in the Backup section
somewhere:

	https://www.postgresql.org/docs/9.6/static/backup.html

Seems it would apply to both of these backup sections:

	24.2. File System Level Backup
	24.3. Continuous Archiving and Point-in-Time Recovery (PITR)

and also here:

	25.2. Log-Shipping Standby Servers

It seems odd to put it in all of these places, but where can we
centrally put it?

-- 
  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