From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | Roberto Grandi <roberto(dot)grandi(at)trovaprezzi(dot)it>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: COPY TO and VACUUM |
Date: | 2013-09-03 20:34:30 |
Message-ID: | 1378240470.79541.YahooMailNeo@web162905.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Roberto Grandi <roberto(dot)grandi(at)trovaprezzi(dot)it> wrote:
> I'm running Postgres 8.4 on Ubuntu 10.4 Linux server (64bit)
> I have a big table tath contains product information: during the
> day we perform a process that import new product continously with
> statemtn COPY TO .. from files to this table.
>
> As result the table disk space is growing fast, it seems that
> postgres is not able to free space for old rows.
COPY TO would not free any space. Is there some other activity you
haven't yet mentioned?
> Is it possible to run a specific autovacuum acivity or say to
> postgres "every time I delete a row, delete it immedialty and
> don't take care of other transactions" ?
You can configure autovacuum to be more aggressive, or you could
run VACUUM statements.
> Do you have any suggestion for me?
8.4 is getting pretty old; there have been a lot of autovacuum
improvements in recent years.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Claudio Freire | 2013-09-03 21:47:11 | Weird case of wrong index choice |
Previous Message | Jesper Krogh | 2013-09-03 19:34:10 | Re: Slow query-plan generation (fast query) PG 9.2 |