Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XHguO-0003Ba-H8 for pgsql-admin@arkaria.postgresql.org; Wed, 13 Aug 2014 22:20:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XHguM-0003hp-W2 for pgsql-admin@arkaria.postgresql.org; Wed, 13 Aug 2014 22:20:39 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XHguM-0003hh-2r for pgsql-admin@postgresql.org; Wed, 13 Aug 2014 22:20:38 +0000 Received: from mail-yh0-x235.google.com ([2607:f8b0:4002:c01::235]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1XHguI-0000Me-G2 for pgsql-admin@postgresql.org; Wed, 13 Aug 2014 22:20:35 +0000 Received: by mail-yh0-f53.google.com with SMTP id c41so391467yho.12 for ; Wed, 13 Aug 2014 15:20:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=dkyWYK4u+67VH2nJHEZqBB2ADLT8aMPMKXhtlvztetI=; b=GGA65VXpvYPd+2cdt/lKhwfsaCjH1e0Y9KAXr3yAals+7BrVdabfqap0bOFrZjMnyI E+fBzIL+BCvUa5BAWf99ROdZigj7M6zjXWvoYpie9KTh8+SwPL8/msWPk41aZzzDlh1J XLbKiMjw6+tCUUFJrHsaTz2mnw50BNQAuVx1noxzv+sMasPlDQL3Xto8/8NEPgZmyH2g n7pn+SCYg88qPlGVeFpTQDd/D/mlgeq+AzKOYaCH6jkdYFxJl96SeZGgk80vM+PGb1gm StH971r+NyRblvzZJBH67+lzUuuGkfFtLTE6nTyW1OQAMG0woshMTuJXPbzN9gt72h7j 4UXw== X-Received: by 10.236.54.10 with SMTP id h10mr10967674yhc.24.1407968432995; Wed, 13 Aug 2014 15:20:32 -0700 (PDT) Received: from [192.168.254.3] (h77.89.102.166.static.ip.windstream.net. [166.102.89.77]) by mx.google.com with ESMTPSA id q9sm3296999yhm.42.2014.08.13.15.20.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Aug 2014 15:20:32 -0700 (PDT) Message-ID: <53EBE4B6.5030904@gmail.com> Date: Wed, 13 Aug 2014 18:20:38 -0400 From: John Scalia User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: pg_upgrade hangs Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) 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 Hi all, My QA folks are doing an upgrade test, migrating a database from 9.2.2 to 9.3.3. By default on CentOS, the databases live at: /var/lib/pgsql/9.2/data & /var/lib/pgsql/9.3/data But, they've decided to move these to /data/postgres-9.2/data and /data/postgres-9.3/data and use symlinks back to the original locations, so they don't have to modify the /etc/init.d scripts. Now, pg_upgrade is just hangs regardless of whether I use the actual physical locations or the symlinked ones. I haven't yet tried attaching "strace" to the process, but is there any reason to believe that the symlinks might be causing the problem? Or do I need to look at something else? -- Jay -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin