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 1flROG-0006rm-7x for pgsql-admin@arkaria.postgresql.org; Fri, 03 Aug 2018 04:08:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1flROD-0006EO-Vo for pgsql-admin@arkaria.postgresql.org; Fri, 03 Aug 2018 04:08:33 +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.89) (envelope-from ) id 1flROD-0006EH-G8 for pgsql-admin@lists.postgresql.org; Fri, 03 Aug 2018 04:08:33 +0000 Received: from mail-oi0-x241.google.com ([2607:f8b0:4003:c06::241]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1flROA-0003mw-C8 for pgsql-admin@lists.postgresql.org; Fri, 03 Aug 2018 04:08:32 +0000 Received: by mail-oi0-x241.google.com with SMTP id 13-v6so7576481ois.1 for ; Thu, 02 Aug 2018 21:08:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=qakwu8cUCLDUfLjGed2+w9WMY/rzt8FSpRF4pewZsZE=; b=NZEiz/FM7wgoE6xKdpVuPIWOuPaUU7p7sVRxGj+qlYmv0bbkOSplGvkBVLCtW0iF/2 U30yMP0s9KpdYfKLpsWQD3MXR7NNQCfC7YdKg99J2DLC6ub76aNtvcFzYXw0V2e0mKiV pQ4ZA9QgouvHsURjG8dEoDj9NG4wixxIfhX1h9AvC1Ze5z85npKj9KJKngMJsjLyzbyn UzTCD7RqubElqWKAzDyGaG/BLAG4/wTdoKVHgqAsR+qnS9ZHerPewuM6Ft5710DnQO5k +d7+RTeRb9L3ugVT202Wv0xyUgfcEzJdmhdP3sZQsR0PZ9Tx5aHS06dl+KnS1hyqDnwM GKvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=qakwu8cUCLDUfLjGed2+w9WMY/rzt8FSpRF4pewZsZE=; b=Ca4B7xkqPgdIwkIykmcXwEEnaBZj1e3hbm6l5Zqr3YB80ZAW4GYVCFtqPlKwegrFU1 RlxqJgnTrZY8QIAHaZmflLEhazsjYDcrnaOBEwiIWDGh5qbH5jbVKTG1wQ5aW4IK+MOO 36x4SRssT8zPP61Jn4X6XOG+S6339vMU+5fO3J7d1kPCSUg9RN++5M8Ukrm0/Lmw24kn Y+dZ1G0Rozkch+0JpXunRieRHnvItRoCXcWdeTAZxZitgxBEo0f2vmmrk/uodRuCA32v b004Z//0lu+WzLqxhPcBOstVlQ1zmkuVTRgxeCy5sHcU+IBU6P/72uNTe2Ce/06Tlfnn 1bag== X-Gm-Message-State: AOUpUlHXgM2/AueV3OsqZ0yI5tr3SAZogotUB1sETFvBH+6UGGVKqQnn vbajoMFyLsdtkRyv5VT5uRnUUbh2 X-Google-Smtp-Source: AA+uWPwLF8rwVr0MW26Cf5hyVzqgzTbwRR0CChTaYBqp3GcBk8rh4dkz0l6+RzAztUGRQsI7O/Clag== X-Received: by 2002:aca:5155:: with SMTP id f82-v6mr1651805oib.272.1533269309252; Thu, 02 Aug 2018 21:08:29 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id 22-v6sm2294661oix.58.2018.08.02.21.08.28 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Aug 2018 21:08:28 -0700 (PDT) Subject: Re: Postgres 10 disk space requirement compared to postgres 9.5.4 To: pgsql-admin@lists.postgresql.org References: <962124430.1421515.1533269097117@mail.yahoo.com> From: Ron Message-ID: Date: Thu, 2 Aug 2018 23:08:27 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <962124430.1421515.1533269097117@mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------0E9F3895FBFDC8740AF042C4" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------0E9F3895FBFDC8740AF042C4 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit How fast is fast?  Does it need to rewrite all the data (would take a while on a Really Large Database), or just change a bit of metadata? On 08/02/2018 11:04 PM, suresh neravati wrote: > Hi Debraj, > > You can use pg_upgrade utility from Postgresql.  This works with inplace > option.  Look at this link below for more details. > > PostgreSQL: Documentation: 10: pg_upgrade > > > > > > > > > > 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: > > > Hi > > On moving from postgres 9.5.4 to postgres 10.x we have to do data migration. > > Can some one let me know will the disk space requirement remain same for > same set of tables with same number of rows in postgres 10.x and postgres > 9.5.4 ? > > Thanks, -- Angular momentum makes the world go 'round. --------------0E9F3895FBFDC8740AF042C4 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit How fast is fast?  Does it need to rewrite all the data (would take a while on a Really Large Database), or just change a bit of metadata?

On 08/02/2018 11:04 PM, suresh neravati wrote:
Hi Debraj,

You can use pg_upgrade utility from Postgresql.  This works with inplace option.  Look at this link below for more details.

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 <subharaj.manna@gmail.com> wrote:


Hi

On moving from postgres 9.5.4 to postgres 10.x we have to do data migration. 

Can some one let me know will the disk space requirement remain same for same set of tables with same number of rows in postgres 10.x and postgres 9.5.4 ?

Thanks,

--
Angular momentum makes the world go 'round.
--------------0E9F3895FBFDC8740AF042C4--