pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedUpper limit for a dump file?
2+ messages / 2 participants
[nested] [flat]
* Upper limit for a dump file?
@ 2004-06-08 21:34 Kris Kiger <kris@musicrebellion.com>
2004-06-09 01:42 ` Re: Upper limit for a dump file? Sam Barnett-Cormack <s.barnett-cormack@lancaster.ac.uk>
0 siblings, 1 reply; 2+ messages in thread
From: Kris Kiger @ 2004-06-08 21:34 UTC (permalink / raw)
To: pgsql-admin
I am trying to restore a dump of two independant databases. Each
database is the same in table structure (there is only one table that
consists of 5 integers, a timestamp with time zone, and a boolean).
Here are the number of rows:
DB1 - 115,539,855 rows
DB2 - 118,022,948 rows
There are no keys/indexes/etc on the table. The uncompressed tar file
is 5.5GB. I am running PG 7.4.
When I try to move this data to another database (via pg_dump &
pg_restore) it fails each time, for each database) with:
pg_restore: [archiver (db)] error returned by PQputline
I find it highly unlikely that I have corrupted data in each database,
since each were generated on different postgres installations on
different machines. I can still query the original databases (DB1 &
DB2) with no problem. It looks like all of the data is intact. Any
ideas what may be the root of the problem or how I can find out more
about this error PQputline returned?
In advance, I appreciate your help!
Kris
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Upper limit for a dump file?
2004-06-08 21:34 Upper limit for a dump file? Kris Kiger <kris@musicrebellion.com>
@ 2004-06-09 01:42 ` Sam Barnett-Cormack <s.barnett-cormack@lancaster.ac.uk>
0 siblings, 0 replies; 2+ messages in thread
From: Sam Barnett-Cormack @ 2004-06-09 01:42 UTC (permalink / raw)
To: Kris Kiger <kris@musicrebellion.com>; +Cc: pgsql-admin
On Tue, 8 Jun 2004, Kris Kiger wrote:
> I am trying to restore a dump of two independant databases. Each
> database is the same in table structure (there is only one table that
> consists of 5 integers, a timestamp with time zone, and a boolean).
> Here are the number of rows:
> DB1 - 115,539,855 rows
> DB2 - 118,022,948 rows
>
> There are no keys/indexes/etc on the table. The uncompressed tar file
> is 5.5GB. I am running PG 7.4.
>
> When I try to move this data to another database (via pg_dump &
> pg_restore) it fails each time, for each database) with:
> pg_restore: [archiver (db)] error returned by PQputline
>
> I find it highly unlikely that I have corrupted data in each database,
> since each were generated on different postgres installations on
> different machines. I can still query the original databases (DB1 &
> DB2) with no problem. It looks like all of the data is intact. Any
> ideas what may be the root of the problem or how I can find out more
> about this error PQputline returned?
Perhaps the other machine has a filesystem limit forbidding such large
files? Various filesystems have historically been limited to 2GB
--
Sam Barnett-Cormack
Software Developer | Student of Physics & Maths
UK Mirror Service (http://www.mirror.ac.uk) | Lancaster University
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2004-06-09 01:42 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-06-08 21:34 Upper limit for a dump file? Kris Kiger <kris@musicrebellion.com>
2004-06-09 01:42 ` Sam Barnett-Cormack <s.barnett-cormack@lancaster.ac.uk>
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