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: adrian(dot)klaver(at)gmail(dot)com
Cc: pgsql-general(at)postgresql(dot)org, 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:24:08
Message-ID: 16995.1298993048@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> Looks like the TOAST compression is not working on the second machine. Not sure
> how that could come to be. Further investigation underway:)

Somebody carelessly messed with the per-column SET STORAGE settings,
perhaps? Compare pg_attribute.attstorage settings ...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Johnston 2011-03-01 19:32:33 Re: Issues with imported blobs from Postgres 8 to 9
Previous Message Tom Lane 2011-03-01 15:19:26 Re: Binary params in libpq