It seems that the difference between the file size and the DB was really the indexes
Thank you again
Lucas
On Saturday, 27 February 2016, Scott Mead <scottm@xxxxxxxxxxx> wrote:
On Saturday, 27 February 2016, Scott Mead <scottm@xxxxxxxxxxx> wrote:
On 02/26/2016 12:19 AM, drum.lucas@xxxxxxxxx wrote:
sorry I was going to send it to the general list.. but I've sent to admin by mistake
I've sent to general list now
On 26 February 2016 at 17:25, drum.lucas@xxxxxxxxx <drum.lucas@xxxxxxxxx> wrote:
Hi all,
I'm doing the pg_restore now in a 1.5TB file:
# ls -lapostgres postgres 1575324616939 Feb 20 13:55 devdb_0.sql
But, the restore has gone over 1.6 TB
# \l+
1639 GB
How is that even possible?
The dump itself doesn't contain index data. It'll contain a line that says 'CREATE INDEX .....'
The index is an on-disk entity that requires disk space, it's very common for a dump file and a restored database to very significantly in size.
pg_restore command:
/usr/pgsql-9.2/bin/pg_restore -d dbname --exit-on-error --jobs=4 --verbose devdb_0.sql
Cheers
