Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d9XbN-0001Hb-OA for pgsql-admin@arkaria.postgresql.org; Sat, 13 May 2017 14:00:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d9XbN-0000UF-13 for pgsql-admin@arkaria.postgresql.org; Sat, 13 May 2017 14:00:57 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d9XbM-0000Tu-Ah; Sat, 13 May 2017 14:00:56 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1d9XbI-0002vY-9I; Sat, 13 May 2017 14:00:55 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 39BD720AE6; Sat, 13 May 2017 10:00:51 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Sat, 13 May 2017 10:00:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=AP2crIPJmSRVvs9Acq z/A8rErjZlGIEv9mPwFBag7GU=; b=KsntApB6nE3yHVlI7273q04C4TljkrHLZD L5/6skJMaUXdiZgZV7/xlBitDKSKuXIarYys48IldtkpJzqgEjwyRnyHGx9b6A8S lM1Wlc3f6P00iVhIEdrkX7lW/ahMyvUMIKP2zA5Vci7bi322z+ipF+Hq1D4QSdU5 MJ3A9if1rvLjsGMY8o5UMuC89/DF4EImkpvvPjDRuNujea1gAkLPkaSzk4dFDKIx eyeCMPgUKltVivecrZBEr1+TbvM31lZQWQjmDuos/ZN28qlYe7v0Yhu7ERkFMFn0 16sjVnAGdSbnR81GwEJTn/QZqQ88TtMziYoqMqkml1inXyqOdVoQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=AP2crIPJmSRVvs9Acqz/A8rErjZlGIEv9mPwFBag7GU=; b=gAFwPH0G WU5rSJEp2aPgSp9MdqFY4ynNTKGUAP/vwTyzR16ZhwwMgfq/lbXj8NSCtDJAefL7 vvx5RHrQsEVTmCOyyA7Niqz8ubz9SAZszROhV+cyUD32rY7lMlxvAyE9JVOWmLDl aODZ5alu8yaGLNdoiFZKRvyGbl52ufpnEwuV/btsbm4IpkWVLL+wF6igQEajSuH8 NSRIvKZkllzpVreTl6uCxl5t9wwIPgjGMFofwh9MkeLK2wVFsHyWJx0q6IYigrHQ lwi/CBBTseGIiuxMZ0rYOX5aSrV8n7fmvHaYEoOf+h0Cuhexol1vlkIKk3vfqafJ T8ZGbc+V3d2bhQ== X-ME-Sender: X-Sasl-enc: awuTqQ/7dYkN0VaCESVwwYTNDIKQ5sit4QlMFWWvdGTY 1494684050 Received: from [192.168.1.2] (97-126-85-89.tukw.qwest.net [97.126.85.89]) by mail.messagingengine.com (Postfix) with ESMTPA id 8F99D24812; Sat, 13 May 2017 10:00:50 -0400 (EDT) Subject: Re: [SQL] PostgreSQL 9.3 DB initialization issue To: Ashish Tiwari Cc: pgsql-admin@postgresql.org, pgsql-sql@postgresql.org References: From: Adrian Klaver Message-ID: <9e6bc162-5082-fd56-fab0-152989e4c002@aklaver.com> Date: Sat, 13 May 2017 07:00:49 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) 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 05/13/2017 06:41 AM, Ashish Tiwari wrote: > Hi Adrian, > > Please find the in line answers. > > Thanks. > > On May 13, 2017 18:55, "Adrian Klaver" > wrote: > > On 05/13/2017 06:11 AM, Ashish Tiwari wrote: > > What data, a dump file or the data directory? > > > Pgsql/9.3/main So you are using the deb packages. The above is for the Postgres 9.3 cluster, where is the data from the Postgres 9.2 cluster? > > What do you mean by setting of replication? > > Enabling the Archive and WAL setting. So was this done before the upgrade, during, after? I am just not seeing the connection to the error you reported. > > > Now when initializaing the DB getting the error as below. > > > So you ran initdb to create a cluster > > Yes .. What was the exact command you used. > > > > > The database cluster was initialized with PG_CONTROL_VERSION > 922, but the server was compiled with PG_CONTROL_VERSION 937. > > > The above would seem to indicate you tried to start a Postgres 9.3 > server using a Postgres 9.2 data directory. > > > Yes.it seems right. That is not possible as you found out. When doing an upgrade between major versions(see note below) in Postgres you either have to dump the data from the older version and restore it to the new version or you need to use pg_upgrade. *NOTE* Up to Postgres version 9.6.x a major version change was a change in either of the first two numbers. Starting with the next release (10.x) only the first number is a major version. At this point you should have two Postgres clusters on you machine, Something like: /var/lib/postgresql/9.2/main/ /var/lib/postgresql/9.3/main/ Is this correct? > > > > > Any solution if DB can be upgraded from 9.2 to 9.3. > > > You are trying to upgrade from Postgres 9.2 to 9.3? > > How was Postgres installed? > > > Sudo apt-get install > > > What OS and version? > > Ubuntu 14.04 LTS > > > > Thanks. > > Best regards, > Ashish > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin