Just for my interest I also created a new PG 842 db (initdb) and put some s=
ample data it it and successfully did a pg_upgrade from 842 -> 920b2. What=
ever the issue is it seems to be related to my actual database as a sample =
db conversion works. Again, 842-914 conversion works for my db though so p=
ossibly it was some change that happened to pg_upgrade since 914 was releas=
ed that is having poor interaction with my actual db cluster.
Also, I wanted to make sure I wasn't using some git checkout of 920 I downl=
oaded the postgresql-9.2.beta2.tgz from the PostgreSQL site dir-browser and=
re-compiled. Still have the problem unfortunately.
Cheers.
Mike Wilson
mfwilson@gmail.com
On Jul 15, 2012, at 2:45 PM, Tom Lane wrote:
> Mike Wilson <mfwilson@gmail.com> writes:
>> 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.
>=20
> Yeah, more than likely :-(. Could we see a stack trace from the
> segfault?
>=20
>> Of possible note in this DB is that the previous DBA renamed the
>> "postgres" user.
>=20
> Hmm. There is a known bug in beta2 that's triggered by old and new
> clusters not having the same name for the bootstrap superuser; although
> I don't recall that the symptoms included a segfault. In any case,
> I'd suggest making sure the new cluster is initdb'd under the same
> account that currently owns the old cluster.
>=20
> regards, tom lane
