Re: pg_dump issues

From: DM <dm(dot)aeqa(at)gmail(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump issues
Date: 2010-02-02 23:41:14
Message-ID: eae6a62a1002021541s46bc40a8o7f173b80c4233f22@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

You were right, after zipping the dump file it came out to 6.9G

Thanks for your help.

thanks
Deepak

On Tue, Feb 2, 2010 at 3:20 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>wrote:

> On Tue, Feb 2, 2010 at 4:07 PM, DM <dm(dot)aeqa(at)gmail(dot)com> wrote:
> > Hi All,
> > I have a database with only one schema with 5 tables
> > nspname | relname | size
> > ---------+---------------------+---------
> > sch | job1 | 211 MB
> > sch | job2 | 5611 MB
> > sch | job3 | 6584 kB
> > sch | job4 | 89 MB
> > sch | job5 | 39 MB
> > Total sum of sizes of the table is less than 6 GB.
> > When I do a pg_dump of this database it is 20GB (I also did a pg_dump of
> > only schema data and the size was still the same). I am using postgres
> 8.4.1
> > version.
> > Could any one explain why the pg_dump size of the file is 3 times the
> size
> > of the tables?
>
> Your database is likely full of easily compressed text, which
> postgresql automagically compresses inline when storing it and
> decompresses when it retrieves it. To see if this is the case, try
> zipping or gzipping or bzip2ing the dump file and see if it comes out
> to something less than or about 6Gigs.
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Clemens Schwaighofer 2010-02-02 23:55:42 Re: Problem with partition tables and schemas
Previous Message Florent THOMAS 2010-02-02 23:28:13 Attribute a value to a record