From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade |
Date: | 2002-01-11 06:00:51 |
Message-ID: | 27526.1010728851@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> ... I'm just looking at the emails
> and it gives me the creeps already.
FWIW, I would *never* trust a production database to pg_upgrade in its
current state; it's untested and can't possibly get enough testing
before release to be trustable. But if Bruce wants to work on it,
where's the harm? The discussions I've had with him over the past
couple days are more than valuable enough for development of a future
bulletproof pg_upgrade, whether or not the current script ever helps
anyone.
The only mistake we could make here is to advertise pg_upgrade as
reliable. Which we will not do.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-01-11 06:09:55 | Re: pg_upgrade |
Previous Message | Bruce Momjian | 2002-01-11 05:42:45 | Re: pg_upgrade |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-01-11 06:09:55 | Re: pg_upgrade |
Previous Message | Bruce Momjian | 2002-01-11 05:21:30 | Re: pg_upgrade |