Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WFSPQ-0005d1-Fo for pgsql-admin@arkaria.postgresql.org; Mon, 17 Feb 2014 17:55:12 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WFSPP-0002Pd-H2 for pgsql-admin@arkaria.postgresql.org; Mon, 17 Feb 2014 17:55:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WFSOQ-0001p2-MC for pgsql-admin@postgresql.org; Mon, 17 Feb 2014 17:54:10 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WFSOJ-0001HB-Jd for pgsql-admin@postgresql.org; Mon, 17 Feb 2014 17:54:10 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1WFSOI-0007GL-NE; Mon, 17 Feb 2014 12:54:02 -0500 Date: Mon, 17 Feb 2014 12:54:02 -0500 From: Bruce Momjian To: Sebastien Douche Cc: pgsql-admin@postgresql.org Subject: Re: Can't upgrade a DB from 8.4 to 9.3 with pg_uprade: pg 9 not started Message-ID: <20140217175402.GA18934@momjian.us> References: <20140214021551.GB3244@momjian.us> 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: -2.5 (--) 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 Fri, Feb 14, 2014 at 06:16:02PM +0100, Sebastien Douche wrote: > On Fri, Feb 14, 2014 at 3:15 AM, Bruce Momjian wrote:\ > > Hi Bruce, > thanks for your time. > > > This is using /tmp because the old server is pre-9.1; it would normally > > use the current directory for the socket file. Are you perhaps using a > > non-standard setting? Our docs say: > > > > If using a pre-9.1 old server that is using a non-default Unix-domain > > socket directory or a default that differs from the default of the > > new cluster, set PGHOST to point to the old server's socket > > location. (This is not relevant on Windows.) > > Right, but It's broken also if I set unix_socket_directory to /tmp. Oh. > > Does that help? Did you use a different environment for the check and > > non-check phases? > > I found a fiable solution: remove the -w option on the pg_ctl' wrapper > (and added sleep 5 for waiting the launch) when pg_upgrade want to > start PG. Tested on several db w/o issues. This option is broken on PG > <9 (several workaround exist in the code of pg_upgrade for it). Oh, that's interesting. We used to have a loop in there for cases where you we couldn't use -w, like for non-default connection settings, but I thought -w still worked for defaults, even back to 8.4. It is possible we removed something that we should no one needed anymore but that 8.4 needs, but I am unclear what that would be. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin