Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f7zCT-0007cc-MA for pgsql-performance@arkaria.postgresql.org; Mon, 16 Apr 2018 08:09:22 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1f7zCR-00016D-P2 for pgsql-performance@arkaria.postgresql.org; Mon, 16 Apr 2018 08:09:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1f7zCR-000163-Eq for pgsql-performance@lists.postgresql.org; Mon, 16 Apr 2018 08:09:19 +0000 Received: from edmmai03.elster.de ([217.237.175.36]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.89) (envelope-from ) id 1f7zCK-0006gH-Np for pgsql-performance@lists.postgresql.org; Mon, 16 Apr 2018 08:09:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=elster.de; s=18030501; t=1523866152; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=a4wTrMXtvRlQqxy+AjKagTfUrWS+oGIugBA0PFv1RpQ=; b=LfY3TsJcXPP7hOq1d4CQsLdjHLJrHUpGZFNiZab6j02zIkl97WxZGONF bHnXkQ4UDhBQD544Jh2kU8c4Z1kc4zbB+ymJ48MSBjkAyPTuJKQxH/j8v 7mH8ZQIX9P7sNOUE44Z3v+X5bpJ831FMt7OYJOkUgWVR686WMos++TbbQ OjxJg/8yKYXutJ4DYCpAReqIfAAZWvpaRr5xySVBNixyeTUBOd2N32RDa DqhydRaBCbn/qE4hdtjRV3MYpAU7uK0Hmlcdt5ncKd3xyg2JRBt+beBhB sYuqazYvkfHY/6/eqBrIZcohMzxkepqkgcz9iYupqBbNdj2k90zJ+cNz6 Q==; X-IronPort-AV: E=Sophos;i="5.48,459,1517871600"; d="scan'208";a="6930998" Received: from edmkop01.een.elster.de ([192.168.20.17]) by edmmai03.een.elster.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Apr 2018 10:09:10 +0200 Received: from [10.200.136.2] (unknown [10.250.1.11]) by edmkop01.een.elster.de (Postfix) with ESMTPSA id 7CB6225FD2B; Mon, 16 Apr 2018 10:09:10 +0200 (CEST) Received: from 10.200.136.2 (10.200.136.2) by ebnalg01-1.net.ebn.elster.de (10.200.211.21); Mon, 16 Apr 2018 10:09:10 +0200 Subject: Re: Data migration from postgres 8.4 to 9.4 To: pgsql-performance@lists.postgresql.org References: Cc: akshay.ballarpure@tcs.com From: "Gunnar \"Nick\" Bluth" Message-ID: Date: Mon, 16 Apr 2018 10:09:08 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Am 16.04.2018 um 09:03 schrieb Akshay Ballarpure: > Hello, Hi Akshay, > I need help in using postgresql 8.4 data in postgres 9.4 version. Do I > need to run any tool to achieve the same? Yes. (-performance is probably the wrong place to ask though, please try -general or -admin next time) Please check the release notes before doing *any* upgrade, esp. when skipping 4 major releases. They (among other very important information) contain instructions how to upgrade: https://www.postgresql.org/docs/current/static/release-9-4.html#id-1.11.6.48.4 You'll probably end up doing a pg_upgrade run (which is linked from the above). > > Steps i followed is ran postgresql 8.4 and 9.4, copied data from 8.4 > instance to 9.4 and try to start postgresql 9.4 but no luck, getting > below error. > > [root@ms-esmon esm-data]# su - postgres -c > "/opt/rh/rh-postgresql94/root/usr/bin/postgres -D > /var/ericsson/esm-data/postgresql-data/ 2>&1 &" > [root@ms-esmon esm-data]# LOG:  skipping missing configuration file > "/var/ericsson/esm-data/postgresql-data/postgresql.auto.conf" > 2018-04-16 06:52:01.546 GMT  *FATAL*:  database files are incompatible > with server > 2018-04-16 06:52:01.546 GMT  *DETAIL*:  The data directory was > initialized by PostgreSQL version 8.4, which is not compatible with this > version 9.4.9. That's exactly what's supposed to happen. The reasons are explained in the pg_upgrade documentation. BTW: Are you sure you want to go to 9.4? It is already rather outdated and will go out of support "soon" (given that you're running 8.4, I have to assume that your organisation requires quite some time to get an upgrade cycle through the red band jungle). Unless you have very good reasons not to, please consider going straight to 10, which will get you almost 5 years of community support. Best regards, -- Gunnar "Nick" Bluth DBA ELSTER Extern im Auftrag der Hays AG Tel: +49 911/991-4665 Mobil: +49 172/8853339