From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Daniel Kalchev <daniel(at)digsys(dot)bg> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade |
Date: | 2002-01-11 05:42:45 |
Message-ID: | 200201110542.g0B5gjm18397@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Daniel Kalchev wrote:
> >>>Bruce Momjian said:
> > I will not enable it until everyone agrees. Are there people interested
> > in this tool being in 7.2, or who are against this tool being in 7.2?
>
> I have never trusted pg_upgrade on production databases. This is where it is
> actually targeted to (to minimize downtime). I have always done full
> pg_dumpall and then full recreation of the database system, which
> unfortunately in my cases take few hours. With so many little changes in the
> structures pg_upgrade it is probably not very safe method anyway?
>
> Just my opinion. :-)
I agree. There are just too many people who complain to me about a lack
of pg_upgrade that I have to do my best on it and let people decide if
they want to use it.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-01-11 06:00:51 | Re: pg_upgrade |
Previous Message | Daniel Kalchev | 2002-01-11 05:40:41 | Re: pg_upgrade |