From: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
---|---|
To: | Andrus <kobruleht2(at)hot(dot)ee> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Compressed Backup too big |
Date: | 2007-11-18 11:00:26 |
Message-ID: | 92869e660711180300v7364fc12ve3fa8f76ca38367f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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?
--
Filip Rembiałkowski
From | Date | Subject | |
---|---|---|---|
Next Message | Mag Gam | 2007-11-18 13:56:32 | tsearch2 best practices |
Previous Message | A. Kretschmer | 2007-11-18 07:58:23 | Re: how should I do to disable the foreign key in postgres? |