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.lu...@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_
> On 26 Feb 2016, at 5:30, John R Pierce wrote:
>
> On 2/25/2016 8:26 PM, drum.lu...@gmail.com wrote:
>>
>> 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
>>
>
> the dump fi
On Fri, Feb 26, 2016 at 5:30 AM, John R Pierce wrote:
> On 2/25/2016 8:26 PM, drum.lu...@gmail.com wrote:
>
>
> 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
>
>
> the dump file d
On 2/25/2016 8:26 PM, drum.lu...@gmail.com wrote:
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
the dump file does not contain the indexes, just CREATE INDEX statements
--
john r pi
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