Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 52D92B5DBE7 for ; Thu, 8 Sep 2011 17:04:51 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 65354-06 for ; Thu, 8 Sep 2011 20:04:45 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from collab.sm-wg.net (collab.sm-wg.net [86.43.106.231]) by mail.postgresql.org (Postfix) with ESMTP id DA847B5DBDA for ; Thu, 8 Sep 2011 17:04:44 -0300 (ADT) Received: from [172.16.2.71] (unknown [172.16.2.71]) by collab.sm-wg.net (Postfix) with ESMTPSA id 2FAC630C3D6F; Thu, 8 Sep 2011 21:02:27 +0100 (IST) Message-ID: <4E691FDC.7010902@sm-wg.net> Date: Thu, 08 Sep 2011 21:04:44 +0100 From: Bernhard Rohrer User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13 MIME-Version: 1.0 To: Bruce Momjian CC: pgsql-admin@postgresql.org Subject: Re: pg_upgrade from 9.0 to 9.1 References: <201109081949.p88Jnp723544@momjian.us> In-Reply-To: <201109081949.p88Jnp723544@momjian.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.404 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.504 X-Spam-Level: X-Archive-Number: 201109/40 X-Sequence-Number: 38277 On 08/09/11 20:49, Bruce Momjian wrote: > Bernhard Rohrer wrote: >> Hiya >> >> running lucid 64 bit. When I try to start pg_upgrade I get the following >> output: >> >> postgres@newcollab:/tmp$ /usr/lib/postgresql/9.1/bin/pg_upgrade -b >> /usr/lib/postgresql/9.0/bin -B /usr/lib/postgresql/9.1/bin >> -d/var/lib/postgresql/9.0/main -D /var/lib/postgresql/9.1/main >> Performing Consistency Checks >> ----------------------------- >> Checking current, bin, and data directories ok >> Checking cluster versions ok >> >> and after this nothing. top shows pg_config running at a solid 20% CPU, >> ps gives the following output: >> >> $ps aux | grep postg >> postgres 15559 0.0 0.0 89660 2628 pts/0 S 19:39 0:00 su postgres >> postgres 15560 0.0 0.0 11164 1964 pts/0 S 19:39 0:00 bash >> postgres 21385 0.0 0.0 50600 2252 pts/0 S+ 19:48 0:00 >> /usr/lib/postgresql/9.1/bin/pg_upgrade -b /usr/lib/postgresql/9.0/bin -B >> /usr/lib/postgresql/9.1/bin -d/var/lib/postgresql/9.0/main -D >> /var/lib/postgresql/9.1/main >> postgres 21390 0.0 0.0 4096 572 pts/0 S+ 19:48 0:00 sh -c >> "/usr/lib/postgresql/9.1/bin/pg_config" --pkglibdir >> postgres 21391 20.1 0.0 4096 576 pts/0 S+ 19:48 0:10 /bin/sh >> /usr/lib/postgresql/9.1/bin/pg_config --pkglibdir >> >> so far I have broken off after about 5 minutes. Has anybody seen this >> behaviour before? > Nope. I remember someone else complaining that pg_controldata or > pg_config was stuck, but I couldn't figure out why. > any debugging you want me to do? I am game. cheers B