pg_upgrade

Since pg_upgrade will not work for 7.1, should its installation be
prevented and the man page be disabled?

Probably. I am not sure it will ever be used again now that we have
numeric file names.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Since pg_upgrade will not work for 7.1, should its installation be
prevented and the man page be disabled?

Probably. I am not sure it will ever be used again now that we have
numeric file names.

Perhaps we should leave it for 7.1 because people will complain when
they can not find it. Maybe we can mention this may go away in the next
release.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Since pg_upgrade will not work for 7.1, should its installation be
prevented and the man page be disabled?

Probably. I am not sure it will ever be used again now that we have
numeric file names.

Perhaps we should leave it for 7.1 because people will complain when
they can not find it. Maybe we can mention this may go away in the next
release.

If it doesn't work, and will not be made to work, then let's remove it
from the tree. If someone wants to resurrect it, then it is easily
retrieved from the cvs attic. But istm that it is not a bad thing if
people can not find something which will not work ;)

Comments?

- Thomas

Thomas Lockhart <lockhart@alumni.caltech.edu> writes:

If it doesn't work, and will not be made to work, then let's remove it
from the tree.

I tend to agree with Peter's slightly less drastic proposal: remove it
from the installed fileset and disable its man page, without necessarily
'cvs remove'ing all the source files. (I see we have already removed
all the other documentation references to it, so disconnecting the ref
page from reference.sgml should be sufficient.)

I hope that pg_upgrade will be of use again in the future, so even
though it can't work for 7.1, a scorched-earth policy is not the way
to go...

regards, tom lane

Whatever you guys decide is fine with me.

Thomas Lockhart <lockhart@alumni.caltech.edu> writes:

If it doesn't work, and will not be made to work, then let's remove it
from the tree.

I tend to agree with Peter's slightly less drastic proposal: remove it
from the installed fileset and disable its man page, without necessarily
'cvs remove'ing all the source files. (I see we have already removed
all the other documentation references to it, so disconnecting the ref
page from reference.sgml should be sufficient.)

I hope that pg_upgrade will be of use again in the future, so even
though it can't work for 7.1, a scorched-earth policy is not the way
to go...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Tom Lane writes:

Thomas Lockhart <lockhart@alumni.caltech.edu> writes:

If it doesn't work, and will not be made to work, then let's remove it
from the tree.

I tend to agree with Peter's slightly less drastic proposal: remove it

from the installed fileset and disable its man page, without necessarily

'cvs remove'ing all the source files. (I see we have already removed
all the other documentation references to it, so disconnecting the ref
page from reference.sgml should be sufficient.)

I'll do this then.

I hope that pg_upgrade will be of use again in the future, so even
though it can't work for 7.1, a scorched-earth policy is not the way
to go...

regards, tom lane

--
Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/