On Tue, Apr 24, 2012 at 10:04 PM, Thom Brown <thom@xxxxxxxxx> wrote:
yes, probably. I remember that it was a binary file, but i didn't know about the possibility of gzip in pg_dump.
Possibly the 2 GB size limit for a FAT partition was exceeded, but that would have resulted in an error, so i would have known.
i think it's time to restore my trust in the custom dumps. :)What was the experience? Is it possible you had specified a
compression level without the format set to custom? That would result
in a plain text output within a gzip file, which would then error out
if you tried to restore it with pg_restore, but would be perfectly
valid if you passed the uncompressed output directly into psql.
yes, probably. I remember that it was a binary file, but i didn't know about the possibility of gzip in pg_dump.
Possibly the 2 GB size limit for a FAT partition was exceeded, but that would have resulted in an error, so i would have known.
i do have one suggestion.
pg_restore only gives a user this feedback, when he makes this mistake:"pg_restore: [archiver] input file does not appear to be a valid archive".
Would it be feasible for pg_restore to detect that it is a different pg_dump format and inform the user about it?
Cheers,
WB
--
"Quality comes from focus and clarity of purpose" -- Mark Shuttleworth
