From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | "postgres Emanuel CALVO FRANCO" <postgres(dot)arg(at)gmail(dot)com> |
Subject: | Re: How to free disk space |
Date: | 2008-10-21 16:46:03 |
Message-ID: | 200810211246.03528.xzilla@users.sourceforge.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tuesday 21 October 2008 09:00:30 postgres Emanuel CALVO FRANCO wrote:
> After run VACUUM, you must run REINDEXDB to decrease indexes.
>
This is probably overkill, as you won't need to do this for a lot of tables in
your database, and the locking issues are probably unhelpful.
> You can pg_resetxlog too, but you need restart server to do that.
>
No No No!!! You should never ever ever run pg_resetxlog on a production
machine!! I'm not sure where you got this idea, but it is a bad one to be
sure!
> 2008/10/21 Ruben Blanco <rubenblan(at)gmail(dot)com>:
> > Hi:
> >
> > My database is growing fast taking too much disk space. How can I free
> > disk space without performing a VACCUM FULL? It locks the database for
> > several hours, and that is not a solution.
> >
> > I guess a backup-restore would do the work but, isn't there a better way
> > to do this without shutting down postgres?
> >
> > Thanks in advandce.
>
> --
> Emanuel Calvo Franco
> Syscope Postgresql DBA
> BaPUG Member
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-10-21 17:01:17 | Re: Varchar vs varchar(64) |
Previous Message | Teodor Sigaev | 2008-10-21 16:35:54 | Re: index scan leads to result that is different from sec scan after upgrading to 8.3.4 |