From: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl> |
---|---|
To: | yasin malli <yasinmalli(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org Postgres General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dump --compress error |
Date: | 2010-08-31 06:38:07 |
Message-ID: | 1E28CD68-6477-46F3-AA68-8AD0CCB729A4@solfertje.student.utwente.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 31 Aug 2010, at 8:17, yasin malli wrote:
Don't reply to just me, include the list.
> if I took my dump file with 'pg_dump -Ft ' command, I would use 'pg_restore', but I take my dump file at plain-old format for compressing data ( tar format dump hasn't compress feature )
> when I tried your suggestion, I take this error : pg_restore: [archiver] input file does not appear to be a valid archive
Ah right, most people use --compress in combination with the custom format (-Fc).
> I have little space on my device so I have to compress db files.
> For example; when I took dump_file with 'pg_dump -Ft' dump_files size : 56K
> 'pg_dump --compress=5' : 4K
Try pg_dump -Fc --compress=5, I think you'll reach comparable sizes and you'll get much more flexibility to restore your database.
Shouldn't you be using level 9 btw, if you're worried about disk space?
> I can take a dump_file but I can't restore it. Is there any other way to restore compressed data ?
Didn't you read the man page for the --compress option? You can just pipe your dump through gunzip.
Alban Hertroys
--
Screwing up is an excellent way to attach something to the ceiling.
!DSPAM:737,4c7ca37210401517469623!
From | Date | Subject | |
---|---|---|---|
Next Message | yasin malli | 2010-08-31 07:50:53 | Re: pg_dump --compress error |
Previous Message | Alban Hertroys | 2010-08-31 05:59:15 | Re: pg_dump --compress error |