Re: pg_restore - Real dump file size
От | Scott Mead |
---|---|
Тема | Re: pg_restore - Real dump file size |
Дата | |
Msg-id | 56D06F72.3000604@openscg.com обсуждение исходный текст |
Ответ на | Re: pg_restore - Real dump file size ("drum.lucas@gmail.com" <drum.lucas@gmail.com>) |
Ответы |
Re: pg_restore - Real dump file size
|
Список | pgsql-admin |
On 02/26/2016 12:19 AM, drum.lucas@gmail.com wrote:
sorry I was going to send it to the general list.. but I've sent to admin by mistakeI've sent to general list nowOn 26 February 2016 at 17:25, drum.lucas@gmail.com <drum.lucas@gmail.com> 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
В списке pgsql-admin по дате отправления: