Re: COPY TO and VACUUM - Mailing list pgsql-performance

From Jeff Janes
Subject Re: COPY TO and VACUUM
Date
Msg-id CAMkU=1ytUAZbDcXcBC6MAN+wkP=La7duTuEAYe+yU9UZJFQAgg@mail.gmail.com
Whole thread Raw
In response to Re: COPY TO and VACUUM  (Roberto Grandi <roberto.grandi@trovaprezzi.it>)
Responses Re: COPY TO and VACUUM
List pgsql-performance
On Tue, Sep 3, 2013 at 11:15 PM, Roberto Grandi
<roberto.grandi@trovaprezzi.it> wrote:
> 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 dead rows as soon as possible, in fact my
scenariois: 
>
> - 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 really fast.

It isn't obvious to me why you would do this continuously.  Surely
your vendors don't change their catalogs exactly as fast as your
database can digest them!

In any event, I'd probably just incorporate a manual vacuum statement
into the delete/reload cycle.  Since delete and copy are not
throttled, while autovacuum is throttled by default to a rather low
level, it is quite possible that default autovacuum can never keep up
with the workload you are generating.  Rather than trying to tune
autovacuum to fit this special case, it would be easier to just throw
in some manual vacuuming.  (Not instead of autovac, just as a
supplement to it)

Cheers,

Jeff


pgsql-performance by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: higth performance write to disk
Next
From: Jeison Bedoya Delgado
Date:
Subject: Re: higth performance write to disk