pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_restore - Real dump file size
4+ messages / 2 participants
[nested] [flat]
* pg_restore - Real dump file size
@ 2016-02-26 04:25 drum.lucas@gmail.com <drum.lucas@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: drum.lucas@gmail.com @ 2016-02-26 04:25 UTC (permalink / raw)
To: pgsql-admin
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?
*pg_restore command:*
/usr/pgsql-9.2/bin/pg_restore -d dbname --exit-on-error --jobs=4 --verbose
devdb_0.sql
Cheers
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_restore - Real dump file size
@ 2016-02-26 05:19 drum.lucas@gmail.com <drum.lucas@gmail.com>
parent: drum.lucas@gmail.com <drum.lucas@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: drum.lucas@gmail.com @ 2016-02-26 05:19 UTC (permalink / raw)
To: pgsql-admin
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?
>
>
> *pg_restore command:*
>
> /usr/pgsql-9.2/bin/pg_restore -d dbname --exit-on-error --jobs=4 --verbose
> devdb_0.sql
>
> Cheers
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_restore - Real dump file size
@ 2016-02-26 15:29 Scott Mead <scottm@openscg.com>
parent: drum.lucas@gmail.com <drum.lucas@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Scott Mead @ 2016-02-26 15:29 UTC (permalink / raw)
To: 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 mistake
>
>
> I've sent to general list now
>
>
> On 26 February 2016 at 17:25, drum.lucas@gmail.com
> <mailto:drum.lucas@gmail.com> <drum.lucas@gmail.com
> <mailto: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;
http://www.openscg.com
PostgreSQL, Java & Linux Experts
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: pg_restore - Real dump file size
@ 2016-02-26 21:33 drum.lucas@gmail.com <drum.lucas@gmail.com>
parent: Scott Mead <scottm@openscg.com>
0 siblings, 0 replies; 4+ messages in thread
From: drum.lucas@gmail.com @ 2016-02-26 21:33 UTC (permalink / raw)
To: Scott Mead <scottm@openscg.com>; +Cc: 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
> <javascript:_e(%7B%7D,'cvml','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,
> <javascript:_e(%7B%7D,'cvml','drum.lucas@gmail.com');>drum.lucas@gmail.com
> <javascript:_e(%7B%7D,'cvml','drum.lucas@gmail.com');> <
> drum.lucas@gmail.com
> <javascript:_e(%7B%7D,'cvml','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;
> http://www.openscg.com
> PostgreSQL, Java & Linux Experts
>
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2016-02-26 21:33 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-02-26 04:25 pg_restore - Real dump file size drum.lucas@gmail.com <drum.lucas@gmail.com>
2016-02-26 05:19 ` drum.lucas@gmail.com <drum.lucas@gmail.com>
2016-02-26 15:29 ` Scott Mead <scottm@openscg.com>
2016-02-26 21:33 ` drum.lucas@gmail.com <drum.lucas@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox