Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2)
Date
Msg-id 20120717205949.GA8146@momjian.us
Whole thread Raw
In response to Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2)  (Mike Wilson <mfwilson@gmail.com>)
List pgsql-bugs
On Sun, Jul 15, 2012 at 02:15:35PM -0700, Mike Wilson wrote:
> I've had some time to examine this closer over the weekend.  It appears that
> pg_upgrade for 9.2b2 segfaults which more than likely has something to do with
> the resulting converted database appearing to have no rows.  Earlier in this
> thread I reported that I was able to get the upgrade to work and this thread to
> be closed but I was in error.  At the time I was also testing with the 9.1.4
> pg_upgrade which does work and I thought that I had a successful 9.2b2
> pg_upgrade run.  Apologies for the confusion and let me know if you would like
> me to start a new thread.
>
> <pg_upgrade 9.2b2>
> ...
> pg_toast.pg_toast_948075_index: 948081 to 948081
> c0.page_metadata_values_pkey: 948082 to 948082
> c0.i_page_metadata_values_short_name: 948084 to 948084
>
>
> Segmentation Fault (core dumped)

What is the actual program output that appears before the core dump
message?

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

pgsql-bugs by date:

Previous
From: Chan Pham
Date:
Subject: Re: log_truncate_on_rotation=on is not truncating
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2)