Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?

From: Vick Khera <vivek(at)khera(dot)org>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
Date: 2012-03-13 12:14:11
Message-ID: CALd+dcdFgBv9W5WiLsuF_6qZ6rmzKoj31YLV2NzAajFvfcmB-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Mar 12, 2012 at 3:06 AM, Nur Hidayat <hidayat365(at)gmail(dot)com> wrote:
> I once have the same problem. In my case it's because most of my table using
> text datatype.
> When I change the field type to character varying (1000) database size
> reduced significantly

I'll bet what happened was postgres re-wrote your table for you,
effectively doing a compaction. You can get similar effect by doing
an alter table and "changing" an INTEGER field to be INTEGER.
Postgres does not optimize that do a no-op, so you get the re-writing
effect.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2012-03-13 13:16:38 Re: How to find compiled-in default port number?
Previous Message Martin Gregorie 2012-03-13 11:46:34 Re: How to find compiled-in default port number?