Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1flRet-0007lE-Oo for pgsql-admin@arkaria.postgresql.org; Fri, 03 Aug 2018 04:25:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1flRer-0002pd-JS for pgsql-admin@arkaria.postgresql.org; Fri, 03 Aug 2018 04:25:45 +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 1flRer-0002pW-C2 for pgsql-admin@lists.postgresql.org; Fri, 03 Aug 2018 04:25:45 +0000 Received: from sonic301-2.consmr.mail.bf2.yahoo.com ([74.6.129.41]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1flRem-0001Fb-Kk for pgsql-admin@postgresql.org; Fri, 03 Aug 2018 04:25:44 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1533270337; bh=xWl/tj1ZdE7+Gf683xEz4s4FDE8gSEsp2MvyHZ3yFrA=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject; b=Iu//JXMGZnRxnJxrFj5pV4fjHcqYFPtU3v4hNqQtbSzI2xMIEGSAvdafihUIspcxhmownGaWdR1KYghXM3e7lxLUb89HnKocN0K26E4NaXNepsfmZnL309Qn9CF/H9aMeIZ8GM9shaTOfYxo5mDA4dUZYUJsQw15M0t2jf6dm4z2LMZlUT5/bGBPrY6Qf5T9cq5KyESkaKnLD9ICQzDoQXIzlVo+2iR8Q31qphBkiLp8U4Rko6aF5whrhhONbi+aOSxSbY7xKoXjcjtCRkXncLcu2Gw3+q2WZaszzSwCP4h7IrGmHm/siDShbaFIr+I4Z6rEKc715hBhVTjDNAk6Mg== X-YMail-OSG: o_t418YVM1m.x2LR72_V7ZOVeD1hqQbSdEgcVGOPWB9anv.Nbi6UxJzGcLU6Noo jrOZexCQ2R0TnjZHNcmEZR78Nc0krb6tEuDT0rU3Ocl.udfvLwKN6JC6ZWw9iADlj.sog3oSccGR 8l3wvPDweiItuovnmxHzvqBjAQPE54vdedWz69ESiirqTj3DWCTWg7wMRJjG_vGJOcZeAsOBY_vc kVdaygrr36oW.0xsBHG20NOTeA.X1NMxbSfBAMUex.muOAFEzCsI6ukX40l9VJnpKbCSd48M1Tnb k5TKc1ncOFfGRT1s7tAbYegSGyx65Fh_17BPfag8Ek.VYM88dr8zJgBttMotrnp2QL6f6wkz2TH7 iS_6zOgKCxEohik8l6OsyNw6OIX0sEB3lcrpNxVSxRedZYe9medc__D9MXWtubvgeV.YBZPsBIxt GOgNps2Vx6DqpGmRe2AFbiGn8t8nw4dU0okdTsjswTX4K2Rv2loU0vKZ1kkWgVqSM8b4sbjTxdnx 01Cz22jFbmeE6VrimmlHxg5urTOJKjPmjfY62WE_hjrKRqK.yGzRWfVnwlU1TgTSTZ60bbJRBR22 46QEW.TJCFL.rxe2r4F8v6AyBCyFZYP6Szb5FkoVblm5Un1CTblSsbAQD1sUlhopToselqSstYux Y7cwZfsgoDxCquVU_d0z97LjtRopid8nymWzm4R2JqzXpLtWCcJ4yXi619xOLkdHc5Ocm6O1wTVi ZF_TmkCZTbg7SkaqS7N_niqSVQZdsWX1YLBHL2NrWYTuywCOH1QVa.ojzsO3SS3i4C6xOhflSwFt xB_QhmS0DGw0lUB.In6jNPQXSTUetnJ1U2F6gcSINBnXmNpKEJ5VnxE.VHU4ee1ZhpEtbBfizXiS tAV007vwVKkPeW89nu1LsLSUzkgHnLFwkPiqngNGdtBbCliJvf3vGjIvwfR9DUlbUPEW7uOKKNvA ezTzDm5fLzBOx7WTAt85qlQG8HxNbBhk..rV5_hlMRg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic301.consmr.mail.bf2.yahoo.com with HTTP; Fri, 3 Aug 2018 04:25:37 +0000 Date: Fri, 3 Aug 2018 04:25:32 +0000 (UTC) From: suresh neravati To: pgsql-admin , Debraj Manna Message-ID: <40500692.1442950.1533270332882@mail.yahoo.com> In-Reply-To: <962124430.1421515.1533269097117@mail.yahoo.com> References: <962124430.1421515.1533269097117@mail.yahoo.com> Subject: Re: Postgres 10 disk space requirement compared to postgres 9.5.4 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1442949_2064428.1533270332880" X-Mailer: WebService/1.1.12206 YMailNorrin Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0 Content-Length: 8987 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_1442949_2064428.1533270332880 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You will create a new data directory for 10 and the data from 9.5 will get= moved to that new folder after the upgrade.=C2=A0 The metadata info in the= catalog will get updated accordingly to pg10. At the end of the upgrade, the 9.5 folder can be dropped after making sure = everything is working. This script is also get generated by pg_upgrade. thanks,Suresh Neravati. On Thursday, August 2, 2018, 9:05:38 PM PDT, suresh neravati wrote: =20 =20 Hi Debraj, You can use pg_upgrade utility from Postgresql.=C2=A0 This works with inpla= ce option.=C2=A0 Look at this link below for more details. PostgreSQL: Documentation: 10: pg_upgrade |=20 |=20 |=20 | | | | | |=20 | |=20 PostgreSQL: Documentation: 10: pg_upgrade | | | This option is also be the fastest for upgrading from 9.5 to PG10 Thanks,Suresh Neravati On Thursday, August 2, 2018, 7:28:47 AM PDT, Debraj Manna wrote: =20 =20 Hi On moving from postgres 9.5.4 to postgres 10.x we have to do data migration= .=C2=A0 Can some one let me know will the disk space requirement remain same for sa= me set of tables with same number of rows in postgres 10.x and postgres 9.5= .4 ? Thanks, =20 ------=_Part_1442949_2064428.1533270332880 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You will create a new data directory for 10 and the data from = 9.5 will get moved to that new folder after the upgrade.  The metadata= info in the catalog will get updated accordingly to pg10.

At the end of the upgrade, the 9.5 folder can be dropped after mak= ing sure everything is working. This script is also get generated by pg_upg= rade.

thanks,
Suresh Neravati.
=

=20