| From: | "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com> |
|---|---|
| To: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_restore real file size |
| Date: | 2016-02-28 17:12:28 |
| Message-ID: | CAE_gQfUqxgTEnU4YKZJ=NaHVp4F0gYn1UP6ubuJDLKxnfCeOfg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
This has been solved...
The difference between the files must be the indexes...
All good now.
Thank you
On 26 February 2016 at 17:26, drum(dot)lucas(at)gmail(dot)com <drum(dot)lucas(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2016-02-28 17:20:10 | Re: Designing tables based on user input and defined values |
| Previous Message | drum.lucas@gmail.com | 2016-02-28 17:12:02 | Export binary data - PostgreSQL 9.2 |