Date: Wed, 4 Sep 2013 08:15:08 +0200 (CEST)
From: Roberto Grandi <roberto.grandi@trovaprezzi.it>
To: Kevin Grittner <kgrittn@ymail.com>
Cc: pgsql-performance@postgresql.org
Message-ID: <1680047223.718929.1378275308275.JavaMail.root@trovaprezzi.it>
In-Reply-To: <1378240470.79541.YahooMailNeo@web162905.mail.bf1.yahoo.com>
References: <535715181.700956.1378223895627.JavaMail.root@trovaprezzi.it>
 <441706222.701556.1378224973704.JavaMail.root@trovaprezzi.it>
 <1378240470.79541.YahooMailNeo@web162905.mail.bf1.yahoo.com>
Subject: Re: COPY TO and VACUUM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Thread-Topic: COPY TO and VACUUM
Thread-Index: avCr99Zb0ETYOTna2shp/M7ukzIcGw==
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Hi kevin

first of all thanks for your help. I did a mistake we are using postgres 8.=
3.

I didn't expect COPY TO frees space but I was wondering Autovacumm delete d=
ead rows as soon as possible, in fact my scenario is:

- Delete all products record for a vendor
- Reload all products record (from new listing) for the same vendor.

Obviously we repeat this process continously and table space is growing rea=
lly fast.

Can you suggest me an approach for autovacuum within this scenario and, if =
you want, suggest me an appropriate version of postgres that help solving m=
y problem?

Many thanks in advance again.

BR,
Roberto


----- Messaggio originale -----
Da: "Kevin Grittner" <kgrittn@ymail.com>
A: "Roberto Grandi" <roberto.grandi@trovaprezzi.it>, pgsql-performance@post=
gresql.org
Inviato: Marted=C3=AC, 3 settembre 2013 22:34:30
Oggetto: Re: [PERFORM] COPY TO and VACUUM

Roberto Grandi <roberto.grandi@trovaprezzi.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.=C2=A0 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


--=20
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance