Re: pg_restore real file size - Mailing list pgsql-general

From Shulgin, Oleksandr
Subject Re: pg_restore real file size
Date
Msg-id CACACo5T=CrnWYac+_0ybCw2f+OdVt=hNyqNBjiFDUr1ApuEHZA@mail.gmail.com
Whole thread Raw
In response to Re: pg_restore real file size  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
On Fri, Feb 26, 2016 at 5:30 AM, John R Pierce <pierce@hogranch.com> wrote:
On 2/25/2016 8:26 PM, drum.lucas@gmail.com wrote:

I'm doing the pg_restore now in a 1.5TB file:

# ls -la

postgres postgres 1575324616939 Feb 20 13:55 devdb_0.sql

But, the restore has gone over 1.6 TB


the dump file does not contain the indexes, just CREATE INDEX statements

Not to mention that on-disk format is quite different from the SQL dump.  Due to row and page headers the on disk format could occupy more space, on the other hand if you have a lot of numeric data which can be represented compactly in the binary format, the restored database might occupy less space in the end.

--
Alex

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: pg_restore real file size
Next
From: Alban Hertroys
Date:
Subject: Re: pg_restore real file size