Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UyeR1-0005KD-RR for pgsql-admin@arkaria.postgresql.org; Mon, 15 Jul 2013 08:47:08 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1UyeR1-0007wi-BU for pgsql-admin@arkaria.postgresql.org; Mon, 15 Jul 2013 08:47:07 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UyeR0-0007wc-JI for pgsql-admin@postgresql.org; Mon, 15 Jul 2013 08:47:06 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UyeQx-0003r9-GV for pgsql-admin@postgresql.org; Mon, 15 Jul 2013 08:47:06 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1UyeQw-0005L5-Fz; Mon, 15 Jul 2013 04:47:02 -0400 Date: Mon, 15 Jul 2013 04:47:02 -0400 From: Bruce Momjian To: Sergey Konoplev Cc: Wells Oliver , pgsql-admin Subject: Re: pg_upgrade (9.1 to 9.2) bombing on casts Message-ID: <20130715084702.GA1730@momjian.us> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -0.4 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On Sun, Jul 14, 2013 at 10:42:22PM -0700, Sergey Konoplev wrote: > On Thu, Jul 11, 2013 at 9:55 PM, Wells Oliver 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 http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin