| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | SHARMILA JOTHIRAJAH <sharmi_jo(at)yahoo(dot)com> |
| Cc: | General postgres mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Space for pg_dump |
| Date: | 2009-03-31 16:07:34 |
| Message-ID: | dcc563d10903310907h345d3da3v2a3ab11e6f3a30a4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 31, 2009 at 9:57 AM, SHARMILA JOTHIRAJAH
<sharmi_jo(at)yahoo(dot)com> wrote:
> But I need to pre-allocate some space for storing these dumps (there are other databases too that needs to be dumped). So Im trying to find a space estimate ....
> Do you have a rough estimate of pg_dump in general... like 1/4 th of the database size or something like that...I just need a rough estimate for now
Sadly, there is no exact maths for such things. If your database has
tons of indexes and such, it might be 20 or 100 times bigger on disk
than it will be during backup. If it's all compressible text with few
indexes, it might be a 1:1 or so size. You can't really tell without
running pg_dump. The advantage of doing pg_dump|wc -l is that the db
doesn't have to be stored somewhere.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-03-31 16:08:45 | Re: string_to_array with empty input |
| Previous Message | Scott Marlowe | 2009-03-31 16:00:11 | Re: Space for pg_dump |