From: Alvaro Herrera on
Excerpts from Stefan Kaltenbrunner's message of mié may 19 15:53:18 -0400 2010:
> While looking at the docs for pg_upgrade I noticed some stuff that the
> following patch attempts to at least partly address.

Surely this para can be removed?

<para>
If you are using tablespaces and migrating to 8.4 or earlier, there must
- be sufficient directory permissions to allow pg_upgrade to rename each
+ be sufficient directory permissions to allow <application>pg_upgrade</> to rename each
tablespace directory to add a ".old" suffix.
</para>

--

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

From: Bruce Momjian on
Stefan Kaltenbrunner wrote:
> While looking at the docs for pg_upgrade I noticed some stuff that the
> following patch attempts to at least partly address.
> There is quite some confusion going on between using "Postgres" and
> PostgreSQL, I changed that to the later because that is how we spell the
> productname in all the other parts of the docs, also added some further
> markups and crossreferences to other docs.

Applied.

> Stuff that seems to need further work is more or less the "limitations"
> section, I don't think there are only issues when upgrade from 8.3 but
> also from 8.4 (though not as much iirc) there is also the rather bold

There are some limitations when migrating from 8.3 to 8.4, but not when
migrating from 8.3 to 9.0, because we added a feature to 9.0. Can you
give a specific example?

> "we will support upgrades from every snapshot and alpha release" which
> seems very optimistic...

Well, I didn't say "every".

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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

From: Bruce Momjian on
Alvaro Herrera wrote:
> Excerpts from Stefan Kaltenbrunner's message of mié may 19 15:53:18 -0400 2010:
> > While looking at the docs for pg_upgrade I noticed some stuff that the
> > following patch attempts to at least partly address.
>
> Surely this para can be removed?
>
> <para>
> If you are using tablespaces and migrating to 8.4 or earlier, there must
> - be sufficient directory permissions to allow pg_upgrade to rename each
> + be sufficient directory permissions to allow <application>pg_upgrade</> to rename each
> tablespace directory to add a ".old" suffix.
> </para>

Ah, yes, removed.

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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

From: Andres Freund on
On Wednesday 19 May 2010 22:39:32 Bruce Momjian wrote:
> There are some limitations when migrating from 8.3 to 8.4, but not when
> migrating from 8.3 to 9.0, because we added a feature to 9.0. Can you
> give a specific example?
Didnt the 'name' alignment change?

Andres

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

From: Bruce Momjian on
Andres Freund wrote:
> On Wednesday 19 May 2010 22:39:32 Bruce Momjian wrote:
> > There are some limitations when migrating from 8.3 to 8.4, but not when
> > migrating from 8.3 to 9.0, because we added a feature to 9.0. Can you
> > give a specific example?
> Didnt the 'name' alignment change?

Uh, the heading above that item is:

<title>Limitations in migrating <emphasis>from</> PostgreSQL
8.3</title>

What is unclear there? It covers going to 8.4 and 9.0.

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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