Re: Pg_upgrade and collation

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Pg_upgrade and collation
Date: 2016-06-20 15:16:36
Message-ID: 20160620151636.GB26992@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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(at)momjian(dot)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 +

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message mschwan 2016-06-20 16:00:47 DROP EXTENSION
Previous Message Bruce Momjian 2016-06-20 15:09:34 Re: pg_rewind option clarification