From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
Cc: | Wells Oliver <wellsoliver(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade (9.1 to 9.2) bombing on casts |
Date: | 2013-07-15 08:47:02 |
Message-ID: | 20130715084702.GA1730@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sun, Jul 14, 2013 at 10:42:22PM -0700, Sergey Konoplev wrote:
> On Thu, Jul 11, 2013 at 9:55 PM, Wells Oliver <wellsoliver(at)gmail(dot)com> wrote:
> > Command executed:
> >
> > time \
> > /usr/lib/postgresql/9.2/bin/pg_upgrade -k \
> > -b /usr/lib/postgresql/9.1/bin \
> > -B /usr/lib/postgresql/9.2/bin \
> > -d /data/postgresql/9.1/test \
> > -D /data/postgresql/9.2/main \
> > -o '-D /etc/postgresql/9.1/test' \
> > -O '-D /etc/postgresql/9.2/main'
>
> In future I suggest you to use --check (from docs: check clusters
> only, don't change any data) when performing pg_upgrade first. I will
> show you all the errors but will not affect your cluster. And you can
> use safe it on a running instance BTW.
While that is a good suggstion, it would not have found this error
becaues --check does not test the restore of the database schemas.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bert | 2013-07-15 13:02:33 | restoring a table after an online backup |
Previous Message | Sergey Konoplev | 2013-07-15 05:42:22 | Re: pg_upgrade (9.1 to 9.2) bombing on casts |