Re: How to shrink database in postgresql

From: Mario Marín <mmfmarin(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Rehan Saleem <pk_rehan(at)yahoo(dot)com>, "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org>
Subject: Re: How to shrink database in postgresql
Date: 2012-03-02 12:29:26
Message-ID: CACX0pozH6anBqWJryG_Z_T0AGHouafHxxKqoMtiWFS3uBa-wUQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

2012/2/29 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Hello
>
> the most similar tool in pg is "VACUUM FULL" statemet;

Hello,

From: http://wiki.postgresql.org/wiki/VACUUM_FULL "Many people, either
based on misguided advice on the 'net or on the assumption that it
must be "better", periodically run VACUUM FULL on their tables. This
is generally a really bad idea and can make your database slower not
faster", it is better to use autovacuum. Please read the wiki,
you'll find all the information you need.

Regards,

Mario Marín

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Emi Lu 2012-03-02 16:56:00 Re: Change Ownership Recursively
Previous Message tylersticky@gmail.com 2012-03-02 12:17:20 Problems with non use of indexes