From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kris Kiger <kris@musicrebellion.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Large file support needed? Trying to identify root of error.
Date: Mon, 19 Jul 2004 16:00:21 -0400
Message-ID: <25097.1090267221@sss.pgh.pa.us> (raw)
In-Reply-To: <40FC20F0.1000402@musicrebellion.com>
References: <40F6A366.5040701@musicrebellion.com>
<40F6B86B.3020400@spacemonkeylabs.com>
<40F6DC6F.4000707@musicrebellion.com>
<40FC20F0.1000402@musicrebellion.com>
Kris Kiger <kris@musicrebellion.com> writes:
> I've got a database that is a single table with 5 integers, a timestamp
> with time zone, and a boolean. The table is 170 million rows in length.
> The contents of the tar'd dump file it produced using:
> pg_dump -U postgres -Ft test > test_backup.tar
> is: 8.dat (approximately 8GB), a toc, and restore.sql.
Try -Fc instead. I have some recollection that tar format has a
hard-wired limit on the size of individual members.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, kris@musicrebellion.com
Subject: Re: Large file support needed? Trying to identify root of error.
In-Reply-To: <25097.1090267221@sss.pgh.pa.us>
References: <40F6A366.5040701@musicrebellion.com> <40F6B86B.3020400@spacemonkeylabs.com> <40F6DC6F.4000707@musicrebellion.com> <40FC20F0.1000402@musicrebellion.com> <25097.1090267221@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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