From: | Stuart Bishop <stuart(at)stuartbishop(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Compressed Backup too big |
Date: | 2007-11-23 12:51:05 |
Message-ID: | 4746CCB9.3050208@stuartbishop.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Filip Rembiałkowski wrote:
> 2007/11/15, Andrus <kobruleht2(at)hot(dot)ee>:
>> "PostgreSQL 8.2.3 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2
>> (mingw-special)"
>> Database size in disk returned by pg_database_size() is 210 MB
>>
>> Database compressesed backup file size is now 125 MB.
>
> How do you produce this dump? pg_dump -Fc ?
>
> If you create plain dump ( pg_dump DBNAME > dump.file ) and zip it
> (normal deflate, like winzip or sth like that), what's the size?
>
> If this is much smaller than 125MB, maybe you got some corner case
> with postgres builtin compression.
>
> You cannot *always* expect 10x ratio... it depends on data. Maybe
> usage patterns of your database changed and now the data is less
> compressable?
We find we get much, much better compression using bzip2.
(It would be wonderful if pg_restore supported this natively, but I don't
know enough to know if it is possible or not.)
--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-11-23 14:18:58 | Forming the UK User Group |
Previous Message | Stuart Bishop | 2007-11-23 12:47:17 | Re: plpython array support |