The following bug has been logged online:

Bug reference: 2645
Logged by: Thomas Verchow
Email address: thomas@verchow.de
PostgreSQL version: 8.1.4
Operating system: GNU/Linux, Debian sarge
Description: pg_restore crashes
Details:

pg_restore ends with ,,Segmentation fault'' or ,,out of memory'' while
trying to restore a large custom-archive-backup (~ 30 GB).

If i choose a table, witch is at the beginning of the backup (according to
pg_restore --list), it works fine.

With smalltable, at the end of the archive, it
ends with a SegFault. So does the same with a big table.
(pg_restore --table=smalltable backup > out.sql)

The Error ,,out of memory'' appears during a restore into the db (using
--dbname=...).

It seems, that pg_restore can't read data behind a limit (2 GB, 8 GB?).

I piped pg_restore through gzip. After a filesize of ~ 7 GB pg_restore
crashes with ,,out of memory''. If the custom archive has the same
compression level, the assumtion for a 8 GB restriction seems to be valid.

This is bad, because you can't use pg_dump & pg_restore for bigger dbs

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

"Thomas Verchow" <thomas@verchow.de> writes:
> pg_restore ends with ,,Segmentation fault'' or ,,out of memory'' while
> trying to restore a large custom-archive-backup (~ 30 GB).

Can you provide a test case for this? Perhaps a SQL script to generate
a database full of junk data, which when dumped and restored causes the
failure?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq