Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gmNqr-0006SA-5Q for pgsql-sql@arkaria.postgresql.org; Wed, 23 Jan 2019 19:06:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gmNqp-0007xS-Kk for pgsql-sql@arkaria.postgresql.org; Wed, 23 Jan 2019 19:06:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gmNqp-0007xL-8v for pgsql-sql@lists.postgresql.org; Wed, 23 Jan 2019 19:06:15 +0000 Received: from dc01pesav001.jacksonnational.com ([12.34.36.219]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gmNqi-0004Yr-CJ for pgsql-sql@lists.postgresql.org; Wed, 23 Jan 2019 19:06:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=jackson.com; i=@jackson.com; q=dns/txt; s=Internal; t=1548270368; x=1579806368; h=from:to:cc:subject:date:message-id:mime-version; bh=itdQt2/OsN/Nb7MQllBITFBBZHcv58aGargcBPidZ3U=; b=JB5WlEAjis1Pf1eZ68Vs6Bwo1m6xjUfRf/bFiQCB+iTZyiqG8uKxP7mS qSTsCkGdBKUSZoFSvk9q/1D6od3GxFgcI+LAkbRt3GaFtN2MzE8Dh91/q UYk9i7B2aOzUO/hGX7sYa+sDpVk7MWqyAJ1U0+bWdICCybwm2HnvW/LNL g=; X-IronPort-AV: E=Sophos;i="5.56,512,1539662400"; d="scan'208,217";a="30997228" Received: from dc0xpdlpv002.jacksonnational.com (HELO DC03PXMBP003.jacksonnational.com) ([10.5.49.47]) by DC01PESAV001.jacksonnational.com with ESMTP; 23 Jan 2019 14:06:06 -0500 Received: from DC03PXMBP003.jacksonnational.com (10.12.105.32) by DC03PXMBP003.jacksonnational.com (10.12.105.32) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 23 Jan 2019 14:06:05 -0500 Received: from DC03PXMBP003.jacksonnational.com ([10.12.105.32]) by DC03PXMBP003.jacksonnational.com ([10.12.105.32]) with mapi id 15.00.1367.000; Wed, 23 Jan 2019 14:06:05 -0500 From: "Rossi, Maria" To: "pgsql-sql@lists.postgresql.org" CC: "Rossi, Maria" Subject: Back-out V10 upgrade but keep new data Thread-Topic: Back-out V10 upgrade but keep new data Thread-Index: AdSzTLFSqGX0p4I+Qq2m+cerBnnwYQ== Date: Wed, 23 Jan 2019 19:06:05 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.12.16.10] x-tm-as-product-ver: SMEX-12.5.0.1300-8.5.1010-24386.002 x-tm-as-result: No-21.771800-5.000000-10 x-tmase-matchedrid: Sudfee3ORQoYcyu6gJU0i/0peXGEEBlvmHAp2UJ8+TxXG3yI9k2vbCWe OHilL0WHP5mpBtPr/e4BZOsOGHKpoUjlo2JU8qCxmHJeAYKlcpNxtWYlDuRQpY9osn8JrdJPn0/ rRQ9krRE15CBmcwx1mJJTzjwz+GzorhAB5C8gZ6oZS5uxXPxN6TNrbNX6yPHqInzOyTDR1usyJX WI0QewuTi0IRJqD7L6BEgxh/aLv5cAwWnlblYdAqgixLOnUig29nLtQ11erE6edUv+PWmGO98mf xiZsPBG14SfaeeUA9NnS6EbaFelym57zlzJSSCUngIgpj8eDcBbCjvvWZW+SbXQ3gWSm6d432mP O5tnasewxhlzj2zwmyU/o547I5IsSmixGpSoc4arVKzIrvJpkZPPVqmxHpo2S4W/MRhJ1X4= x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No x-tmase-result: 10--21.771800-5.000000 x-tmase-version: SMEX-12.5.0.1300-8.5.1010-24386.002 Content-Type: multipart/alternative; boundary="_000_a08cae634742427385728ce0209d80faDC03PXMBP003jacksonnati_" MIME-Version: 1.0 X-CFilter-Loop: Reflected List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_a08cae634742427385728ce0209d80faDC03PXMBP003jacksonnati_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, If I upgrade Postgres from V9.3 to V10, then need to roll-back to V9.3 afte= r data been entered, is there a way for me to save the new data so that I c= an re-apply it to the V9.3? After I restore my V9.3 backup, can I simply r= eplay the V10 log unto V9.3? What are my options, if any? Thanks. Maria A Rossi Database Administration Jackson National Life email: maria.rossi@jackson.com cell phone: 517.256.4392 work phone: 517.367.3099 work phone extension: 23099 --_000_a08cae634742427385728ce0209d80faDC03PXMBP003jacksonnati_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

If I upgrade Postgres from V9.3 to V10, then need to= roll-back to V9.3 after data been entered, is there a way for me to save t= he new data so that I can re-apply it to the V9.3?  After I restore my= V9.3 backup, can I simply replay the V10 log unto V9.3?  What are my options, if any?

 

Thanks.

 

Maria A Rossi

Database Administration

Jackson National Life

email: ma= ria.rossi@jackson.com
cell phone: 517.256.4392

work phone: 517.367.3099
work phone extension: 23099=

 

--_000_a08cae634742427385728ce0209d80faDC03PXMBP003jacksonnati_--