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

From: Aleksey Tsalolikhin <atsaloli(dot)tech(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
Date: 2011-03-04 02:15:50
Message-ID: AANLkTimY89Vbv_dj=qyiskedr3HtPA5y_cz4pHjgQGxu@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Mar 1, 2011 at 7:24 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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 ...

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

Any other ideas?

Yours truly,
-at

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Gauthier, Dave 2011-03-04 03:03:59 updating all records of a table
Previous Message Greg Williamson 2011-03-04 01:05:37 Re: I need your help to get opinions about this situation