Re: Re: pg_upgrade

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: lockhart(at)fourpalms(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: pg_upgrade
Date: 2001-03-19 14:21:39
Message-ID: 200103191421.JAA00791@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Whatever you guys decide is fine with me.

> Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)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(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-03-19 14:29:01 Re: Allowing WAL fsync to be done via O_SYNC
Previous Message Alfred Perlstein 2001-03-19 12:55:01 Re: Fw: [vorbis-dev] ogg123: shared memory by mmap()