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

From Aleksey Tsalolikhin
Subject Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
Date
Msg-id AANLkTimY89Vbv_dj=qyiskedr3HtPA5y_cz4pHjgQGxu@mail.gmail.com
Whole thread Raw
In response to Re: database is bigger after dump/restore - why? (60 GB to 109 GB)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: database is bigger after dump/restore - why? (60 GB to 109 GB)  (Adrian Klaver <adrian.klaver@gmail.com>)
List pgsql-general
On Tue, Mar 1, 2011 at 7:24 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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 ...



Thank you.  I compared the STORAGE settings and I have "extended" on
both databases,
no "external".

Any other ideas?

Yours truly,
-at

pgsql-general by date:

Previous
From: Greg Williamson
Date:
Subject: Re: I need your help to get opinions about this situation
Next
From: "Gauthier, Dave"
Date:
Subject: updating all records of a table