-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Looks like I want -Fc and then I can also do away with the gzip.
But I'm wondering why the
dba didn't use it to begin with.
Brian Pitts wrote:
> On Mon, 2008-10-06 at 09:38 -0600, Robert L. Harris wrote:
>> 'lo all. Just found a new one. We have a number of postgres
>> backups we run nightly with the command:
>>
>> /usr/local/pgsql/bin/pg_dump -U postgres -Ft city | /bin/gzip -5
>> > city.out.bz
>>
>>
>> We just got a new one, one of the cities is just too big for tar:
>>
>>
>> 2008-10-06 07:18:31 - pg_dump: [tar archiver] archive member too
>> large for tar format
>>
>> Anyone run into this and know a way around it?
>>
>> Robert
>
> Here's what pg_backup_tar.c says
>
> /* * Maximum file size for a tar member: The limit inherent in the
> * format is 2^33-1 bytes (nearly 8 GB). But we don't want to
> exceed * what we can represent by an off_t. */ #ifdef
> INT64_IS_BUSTED #define MAX_TAR_MEMBER_FILELEN INT_MAX #else
> #define MAX_TAR_MEMBER_FILELEN (((int64) 1 << Min(33,
> sizeof(off_t)*8 - 1)) - 1) #endif
>
> Sounds like you need to switch formats.
>
> -Brian
>
> _______________________________________________ Ale mailing list
> Ale at ale.org http://mail.ale.org/mailman/listinfo/ale
- --
:wq!
====================================================================
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS With Dreams To Be A King,
ALONE. I speak for First One Should Be A Man
no-one else. - Manowar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iD8DBQFI6jZF8+1vMONE2jsRAgGVAKDLwRcnaoGGQ10/7No5+0FQjTclZwCfQGG0
ikEq4UEpOtj7Fi7LbvhGtxM=
=9MA6
-----END PGP SIGNATURE-----