Re: pg_restore - Real dump file size

Поиск
Список
Период
Сортировка
От drum.lucas@gmail.com
Тема Re: pg_restore - Real dump file size
Дата
Msg-id CAE_gQfVinu3LD9W4bgLdiTkQffXNbYzW4BCz8u--ytN8p=nk9g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pg_restore - Real dump file size  (Scott Mead <scottm@openscg.com>)
Список pgsql-admin
Thanks for the reply

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@openscg.com> wrote:

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 mistake


I've sent to general list now


On 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 -la

postgres 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



--
Scott Mead
OpenSCG
http://www.openscg.com
PostgreSQL, Java & Linux Experts

В списке pgsql-admin по дате отправления:

Предыдущее
От: Korry Douglas
Дата:
Сообщение: Re: pg_basebackup - Stale file handle for file under gprof
Следующее
От: Michael JOIGNY
Дата:
Сообщение: pgpool: DETAIL: no pool_hba.conf entry for host