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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
Date: 2011-02-27 15:56:08
Message-ID: 3996.1298822168@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com> writes:
> i've installed the "pageinspect" contrib module as Tomas suggested but
> I don't know what to do with it or what to look at. I looked at the
> manual for it but it's totally over my head right now.

Personally I'd try pgstattuple first:
http://www.postgresql.org/docs/8.4/static/pgstattuple.html

The stats from that for the table and each index should at least let us
narrow down where the bloat is.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Julia Jacobson 2011-02-27 17:01:56 Re: Linking against static libpq using Visual C++
Previous Message Scott Ribe 2011-02-27 15:47:10 Re: ERROR: invalid byte sequence for encoding "UTF8": 0xc35c