Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
Date
Msg-id 16995.1298993048@sss.pgh.pa.us
Whole thread Raw
In response to Re: database is bigger after dump/restore - why? (60 GB to 109 GB)  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: database is bigger after dump/restore - why? (60 GB to 109 GB)  (Aleksey Tsalolikhin <atsaloli.tech@gmail.com>)
List pgsql-general
Tree view 
Adrian Klaver <adrian.klaver@gmail.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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Binary params in libpq
Next
From: Gary Fu
Date:
Subject: Re: slow building index and reference after Sybase to Pg