> On 26 Feb 2016, at 5:30, John R Pierce <pierce@xxxxxxxxxxxx> wrote: > > On 2/25/2016 8:26 PM, drum.lucas@xxxxxxxxx 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 Or page alignment padding, or the effects of fill factors, to name a few more reasons. Besides, your dump-file is compressed. It's being restored using pg_restore (or can it restore using plain text sql scripts these days?) instead of psql. Lastly, how does a database in unicode fare for text size (without toasted values) against a plain text dump file in, say, utf-8 - which isn't even the worst case scenario? That's the simplistic case; in reality some values will get toasted and the dump file is compressed. Alban Hertroys -- If you can't see the forest for the trees, cut the trees and you'll find there is no forest. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
