Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d9aAu-0000L5-LR for pgsql-sql@arkaria.postgresql.org; Sat, 13 May 2017 16:45:49 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1d9aAt-0007K7-V8 for pgsql-sql@arkaria.postgresql.org; Sat, 13 May 2017 16:45:48 +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 1d9a9r-0003hY-6k; Sat, 13 May 2017 16:44:43 +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 1d9a9j-0005xj-WD; Sat, 13 May 2017 16:44:42 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B73142092B; Sat, 13 May 2017 12:44:34 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Sat, 13 May 2017 12:44:34 -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=Iz4i+HmkkjWMBliT/b cQy0IxbeiZ7waC1Nf4qs+mAgs=; b=Iq+Ed6DAW4DJtezLdp0fgJd3EQH2Sqip7u Jy88IQrJ5a4s3qYW/AplXV6x3bldjivTINtqXzk0C3R+8bjBjQi9n67nibyZRYDJ onEF9o3u7UnVe15rjOGPo6g0lFWUcgAEjD9hgGrukwOhzrpHfZvYCmJGTmOVdQQG 8RVGa2UoTaMdJ2XkVWqtlyEPl3YnGnPiqz4+2L1vOc/4LG/p8+bFEc5TWq/dNOxa kLtEaxf+bNXENKfQAevEymNHBoP1rpgfb/Btbf6k/+h/pHCQBvj65jSf2i1GlZUm kt2eNl+o1OZt74QjV4YJHBnNmZDg6mjWktYyT7d9SeKaO71S3vZA== 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=Iz4i+HmkkjWMBliT/bcQy0IxbeiZ7waC1Nf4qs+mAgs=; b=dKViCdde o9pvOdYmJbqWg6T0YD5tzXFlZAY0IsykRE3sn+1z9GBXCBlsU/Vq8wSfjS8mYEiA tFMrMTVW8e991trXDoWNRAcj155vp/x87QxsFYwcfJ2DiQuGsxoLnzdR6/9ARPY3 eXy0juFAVoEO8fk4VielIRqb/kXCQYiKqgcFmrY9PPN2i41MP8SDyun5AwhDbbu3 nuGRBihT8cXxzb4b6lzOaItxKH+dHV3fxjiBuwPzm4GAm5ZCKJaUeuwMBoQL2UWM NPAZ4FQsNwEZGk4l4pua6l63JWlyVkRVNCPGdE/AGQMNzC7TXO9vCd0HeSmBr9IH ktX6f7olMc9X4A== X-ME-Sender: X-Sasl-enc: 4WGHPM1IPHqfcY8Bgrj5CdF1EaVlPFlVmoGCWWhCFXnW 1494693874 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 2AA3824871; Sat, 13 May 2017 12:44:34 -0400 (EDT) Subject: Re: PostgreSQL 9.3 DB initialization issue To: Ashish Tiwari Cc: pgsql-admin@postgresql.org, pgsql-sql@postgresql.org References: <9e6bc162-5082-fd56-fab0-152989e4c002@aklaver.com> From: Adrian Klaver Message-ID: <727a25d0-00ab-15c3-9eff-1ec7b8e3588f@aklaver.com> Date: Sat, 13 May 2017 09:44:33 -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-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org On 05/13/2017 08:53 AM, Ashish Tiwari wrote: > Hi Andrian, > > The data have kept separate as in > > /pgsql/data2 directory. > > We are passing this path while starting the server using pg-ctl from bin > directory as well this data path is given in to postgresql.conf . > > So in current situation the binary is as of 9.3 and data is as of 9.2 > > As an alternative can we install the 9.2 and manually make the up DB is > it possible Or data is lost ?. finally If /pgsql/data2 represents the Postgres 9.2 data directory then the data is not lost. I am including information from your previous post in the below. > $./initdb -D /pgsql/9.3/main/data Are you overriding the default location that Debian uses?: https://wiki.debian.org/PostgreSql I would look at the above to see how you can use the Debian tools to maintain/create multiple Postgres clusters. > 9.2 is uninstalled now. You will need to install it again to be able to access the data in the 9.2 data directory you show above(/pgsql/data2). I would maintain that copy(/pgsql/data2) and just copy it into the 9.2 cluster when you get it reinstalled. If you want to upgrade to 9.3, then use the 9.3 pg_dumpall to dump the 9.2 data and then the 9.3 pg_restore to restore it into the 9.3 instance. > > Thanks. > BR,Ashish > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql