Re: Want a routine vacuum for postgres

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Richa Rathore <richayuvasoft161(at)gmail(dot)com>
Cc: Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Want a routine vacuum for postgres
Date: 2016-09-22 20:57:02
Message-ID: CA+Tgmoat_LDWsL4vXnvxhkvicofOPFYXMCwt-G7GeukF+mUVuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Sep 8, 2016 at 3:35 AM, Richa Rathore
<richayuvasoft161(at)gmail(dot)com> wrote:
> As i can see when i am running some process so it is creating the file in
> /usr/local/pgsql/data/base/16385/22596 which are more then 50mb . it was
> doing my memory and cpu full. so can you please suggest me what will be the
> better option for creating the space in memory. it is in digital ocean and
> when i run VACUUM FULL command it deleted whole my data so can you help me
> for routine maintain of pg data without disturbing my important data.
> Thanks in advance

This report isn't really clear enough for anybody to help you, but it
is expected that VACUUM FULL will rewrite your data in a new file.
You might find this blog post helpful:

http://rhaas.blogspot.com/2014/03/vacuum-full-doesnt-mean-vacuum-but.html

Also, this doesn't seem to be a bug report. Ask general usage
questions on pgsql-general, not the bugs list - or contact one of the
PostgreSQL support companies for assistance.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2016-09-22 21:34:29 Re: BUG #14314: Mismatch of comment of a function.
Previous Message Robert Haas 2016-09-22 20:54:19 Re: 9.6rc1 Background worker starting multiple times