Re: database is bigger after dump/restore - why? (60 GB to 109 GB)

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>
Subject: Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
Date: 2011-03-01 15:18:50
Message-ID: 201103010718.50601.adrian.klaver@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Monday, February 28, 2011 9:51:10 pm Aleksey Tsalolikhin wrote:

>
> Here is what I see:
>
>
>
> nspname | relname | tablesize
>
> | indexsize | toastsize | toastindexsize
>
> ------------------------+----------------------------------+------------+--
> ----------+------------+---------------- public | big
> | 744 MB
>
> | 737 MB | 48 GB | 278 MB
>
> public | big | 503 MB
>
> | 387 MB | 99 GB | 278 MB
>
> Check out that toastsize delta. What makes up TOAST? How can I
> compare the two TOAST tables in detail?
>

The compression/no compression thing tickled a memory. Run \d+ against the table
in question. It should show a storage column with values for each field. Are any
of those set to EXTERNAL instead of the default EXTENDED?

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2011-03-01 15:19:26 Re: Binary params in libpq
Previous Message Gary Fu 2011-03-01 15:10:25 Re: slow building index and reference after Sybase to Pg