[HACKERS] pg_upgrade docs

2012-09-04 Thread Bruce Momjian
This doc sentence about pg_upgrade is now inaccurate: If doing option--check/ with a running old server of a pre-9.1 version, and the old server is using a Unix-domain socket directory that is different from the default built into the new productnamePostgreSQL/ installation, set

Re: [HACKERS] pg_upgrade docs

2010-05-25 Thread Robert Haas
On Mon, May 24, 2010 at 11:35 PM, Bruce Momjian br...@momjian.us wrote: Have you read the docs?  It does mention the issue with /contrib and stuff.  How do I document a limitation I don't know about?  This is all very vague.  Please suggest some wording. OK, here's an attempt. Please

Re: [HACKERS] pg_upgrade docs

2010-05-25 Thread Bruce Momjian
Robert Haas wrote: On Mon, May 24, 2010 at 11:35 PM, Bruce Momjian br...@momjian.us wrote: Have you read the docs? ?It does mention the issue with /contrib and stuff. ?How do I document a limitation I don't know about? ?This is all very vague. ?Please suggest some wording. OK, here's an

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Bruce Momjian
Stefan Kaltenbrunner wrote: On 05/19/2010 05:16 PM, Bruce Momjian wrote: 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

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Stefan Kaltenbrunner
On 05/24/2010 07:43 PM, Bruce Momjian wrote: Stefan Kaltenbrunner wrote: On 05/19/2010 05:16 PM, Bruce Momjian wrote: 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,

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Bruce Momjian
Stefan Kaltenbrunner wrote: I have updated the paragraph to be: Upgrading from PostgreSQL 8.3 has additional restrictions not present when upgrading from later PostgreSQL releases. For example, pg_upgrade will not work for a migration from 8.3 if a user column is

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Robert Haas
On Mon, May 24, 2010 at 3:11 PM, Bruce Momjian br...@momjian.us wrote: Stefan Kaltenbrunner wrote: I have updated the paragraph to be:     Upgrading from PostgreSQL 8.3 has additional restrictions not present     when upgrading from later PostgreSQL releases.  For example,    

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Bruce Momjian
Robert Haas wrote: On Mon, May 24, 2010 at 3:11 PM, Bruce Momjian br...@momjian.us wrote: Stefan Kaltenbrunner wrote: I have updated the paragraph to be: ? ? Upgrading from PostgreSQL 8.3 has additional restrictions not present ? ? when upgrading from later PostgreSQL releases. ?For

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Robert Haas
On Mon, May 24, 2010 at 3:41 PM, Bruce Momjian br...@momjian.us wrote: Robert Haas wrote: On Mon, May 24, 2010 at 3:11 PM, Bruce Momjian br...@momjian.us wrote: Stefan Kaltenbrunner wrote: I have updated the paragraph to be: ? ? Upgrading from PostgreSQL 8.3 has additional

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Dave Page
On Mon, May 24, 2010 at 5:20 PM, Robert Haas robertmh...@gmail.com wrote: It works OK for me.  The link to /contrib/pg_upgrade within the nav section at the top righthand corner of the page seems to work just fine. http://wiki.postgresql.org/wiki/Todo#.2Fcontrib.2Fpg_upgrade The problem is

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Bruce Momjian
Robert Haas wrote: On Mon, May 24, 2010 at 3:41 PM, Bruce Momjian br...@momjian.us wrote: Robert Haas wrote: On Mon, May 24, 2010 at 3:11 PM, Bruce Momjian br...@momjian.us wrote: Stefan Kaltenbrunner wrote: I have updated the paragraph to be: ? ? Upgrading from PostgreSQL 8.3

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Robert Haas
On Mon, May 24, 2010 at 5:38 PM, Dave Page dp...@pgadmin.org wrote: On Mon, May 24, 2010 at 5:20 PM, Robert Haas robertmh...@gmail.com wrote: It works OK for me.  The link to /contrib/pg_upgrade within the nav section at the top righthand corner of the page seems to work just fine.

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Robert Haas
On Mon, May 24, 2010 at 5:50 PM, Bruce Momjian br...@momjian.us wrote: What is your point? My point is that I think Stefan has a good point when he says this: hmm that seems better thanks, however I just noticed that we don't have a general limitations section. The way the docs are now

Re: [HACKERS] pg_upgrade docs

2010-05-24 Thread Bruce Momjian
Robert Haas wrote: On Mon, May 24, 2010 at 5:50 PM, Bruce Momjian br...@momjian.us wrote: What is your point? My point is that I think Stefan has a good point when he says this: hmm that seems better thanks, however I just noticed that we don't have a general limitations

Re: [HACKERS] pg_upgrade docs

2010-05-20 Thread Stefan Kaltenbrunner
On 05/19/2010 05:16 PM, Bruce Momjian wrote: 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?

[HACKERS] pg_upgrade docs

2010-05-19 Thread Stefan Kaltenbrunner
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

Re: [HACKERS] pg_upgrade docs

2010-05-19 Thread Alvaro Herrera
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

Re: [HACKERS] pg_upgrade docs

2010-05-19 Thread Bruce Momjian
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

Re: [HACKERS] pg_upgrade docs

2010-05-19 Thread Bruce Momjian
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

Re: [HACKERS] pg_upgrade docs

2010-05-19 Thread Andres Freund
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

Re: [HACKERS] pg_upgrade docs

2010-05-19 Thread Bruce Momjian
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