Skip site navigation (1) Skip section navigation (2)

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 <pgsql-general(at)postgresql(dot)org>
Subject: Re: database is bigger after dump/restore - why? (60 GB to 109 GB)
Date: 2011-02-24 21:11:44
Message-ID: AANLkTimgPyEEpgDxt_bKJw-qAcj+P4Xvw1vTzjJhqgv2@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Thu, Feb 24, 2011 at 11:46 AM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> On 02/24/11 11:02 AM, Aleksey Tsalolikhin wrote:
>
>> How do I check the fillfactor on the table, please?
>
> its in the field reloptions in pg_class.   so...
>
>    select reloptions from pg_class where relname='tablename';

Thanks, John!

autovacuum_enabled=true is the only option set on this table
on both the source database and the target.

>> How do I pg_restore it so that it is 50 GB in size?  Is it a setting
>> to pg_dump or to pg_restore?
>>
>
> are you truncating the table before restoring, or is this a restore into a
> new database, or what?

I've tried both.  Slony truncates the table before copying it over, and I've
tryind pg_restore'ing it into a new database.  In both cases, the 50 GB
table arrives as a 100 GB table.

Aleksey

In response to

Responses

pgsql-general by date

Next:From: David JohnstonDate: 2011-02-24 21:29:01
Subject: Index Ignored Due To Use Of View
Previous:From: Dmitriy IgrishinDate: 2011-02-24 21:08:52
Subject: Re: array size

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group