Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 5B26863317B for ; Wed, 18 Feb 2009 12:37:51 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 76537-02 for ; Wed, 18 Feb 2009 12:37:46 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from nrccenexf1.nrc.ca (nrccenexf1.nrc.ca [132.246.15.80]) by mail.postgresql.org (Postfix) with ESMTP id D0E49633171 for ; Wed, 18 Feb 2009 12:37:45 -0400 (AST) Received: from nrccenexf1.nrc.ca ([132.246.15.80]) by nrccenexf1.nrc.ca with Microsoft SMTPSVC(6.0.3790.3959); Wed, 18 Feb 2009 11:37:42 -0500 Received: from [192.168.11.209] ([132.246.15.68]) by nrccenexf1.nrc.ca over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 18 Feb 2009 11:37:42 -0500 Message-ID: <499C3955.6000403@nrc-cnrc.gc.ca> Date: Wed, 18 Feb 2009 08:37:41 -0800 From: Isabella Ghiurea Reply-To: isabella.ghiurea@nrc-cnrc.gc.ca Organization: CADC -NRC User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Ray Stell CC: pgsql-admin@postgresql.org Subject: Re: Upgrade 8.3.6 issues References: <499C32D5.2060003@nrc-cnrc.gc.ca> <20090218162250.GB7812@cns.vt.edu> In-Reply-To: <20090218162250.GB7812@cns.vt.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Feb 2009 16:37:42.0286 (UTC) FILETIME=[382F32E0:01C991E7] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/137 X-Sequence-Number: 31358 Thank you , that worked! Isabella Ray Stell wrote: > > btw, no dump is required to flip from 8.3x to 8.3x, but > testing is a good thing. > > check the postmaster.pid > > [postgresql@swallowtail alerts_oamp]$ cat postmaster.pid > 2545 > /var/database/pgsql/alerts_oamp > 5478001 0 > alerts_oamp]$ ps -ef | grep 2545 > 500 2545 1 0 Jan11 ? 00:00:29 > /usr/local/pgsql833/bin/postgres -D /var/database/pgsql/alerts_oamp > 500 2546 2545 0 Jan11 ? 00:00:00 postgres: logger > process > 500 2548 2545 0 Jan11 ? 00:00:00 postgres: writer > process > 500 2549 2545 0 Jan11 ? 00:00:00 postgres: wal writer > process > 500 2550 2545 0 Jan11 ? 00:00:00 postgres: autovacuum > launcher process > 500 2551 2545 0 Jan11 ? 00:00:02 postgres: stats > collector process > > > > > > On Wed, Feb 18, 2009 at 08:09:57AM -0800, Isabella Ghiurea wrote: > > > > Hi All, > > I'm testing for the first time a PG upgrade process, presently running > > 8.3.4 and try to upgrade to 8.3.6. I have installed 8.3.6 in > separate dir > > - run pg_dumpall using the new PG 8.3.6 version > > - shutdown the server > > - create a new db cluster with 8.3.6 initdb > > -copy pg_gba.conf and postgres.conf to 8.3.6 PG location > > -Now I can't start the db server using the pg 8.3.6 version ., I'm using > > same port # default . Here is my message: > > > pg_ctl status > > > pg_ctl: no server running > > >0:bin$ pg_ctl start > > server starting > > postgres@cvodb0:bin$ 2009-02-18 08:00:59 PST::@:[16713]:LOG: could not > > bind IPv6 socket: Address already in use > > 2009-02-18 08:00:59 PST::@:[16713]:HINT: Is another postmaster already > > running on port 5432? If not, wait a few seconds and retry. > > 2009-02-18 08:00:59 PST::@:[16713]:LOG: could not bind IPv4 socket: > > Address already in use > > 2009-02-18 08:00:59 PST::@:[16713]:HINT: Is another postmaster already > > running on port 5432? If not, wait a few seconds and retry. > > 2009-02-18 08:00:59 PST::@:[16713]:FATAL: could not create any TCP/IP > > sockets > > pg_ctl status > > pg_ctl: no server running > > > > What do I miss ? > > > > -- > > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > > To make changes to your subscription: > > http://www.postgresql.org/mailpref/pgsql-admin >