Re: Pg_upgrade and collation

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

Bruce Momjian wrote:
> On Fri, Jun 17, 2016 at 06:01:59PM -0400, Bruce Momjian wrote:
> > On Fri, Jun 17, 2016 at 05:51:54PM -0400, Alvaro Herrera wrote:
> > > Bruce Momjian wrote:
> > > > The attached patch documents that pg_upgrade requires old/new servers to
> > > > use compatibile collation library versions as well.
> > >
> > > I think this is way too thin to be helpful:
> >
> > Well, this is a much larger issue than pg_upgrade, e.g. moving a data
> > directory from one cluster to another with a different collation library
> > version could also cause problems, and I don't know that is documented
> > at all.
> >
> > If we want to go larger, we have to do this in a more central location.
>
> 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.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Guillaume Lelarge 2016-06-17 22:14:32 Quick fix on catalogs.sgml
Previous Message Bruce Momjian 2016-06-17 22:09:35 Re: Pg_upgrade and collation