Skip site navigation (1) Skip section navigation (2)

Re: Insert only tables and vacuum performance

From: Joseph Shraibman <jks(at)selectacast(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Insert only tables and vacuum performance
Date: 2004-04-29 23:24:40
Message-ID: c6s2rk$1qgd$ (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Joseph Shraibman wrote:
> I have a table that is never updated, only INSERTED into. Is there a way 
> I can prevent vacuum wasting time on this table besides vacuuming each 
> table in the db by itself and omitting this table?
> How feasable would it be to have a marker somewhere in pg that is 
> "updated since last vacuum" that would be cleared when vacuum runs, and 
> if set vacuum will ignore that table?

Or even better an offset into the datatable for the earliest deleted 
row, so if you have a table where you update the row shortly after 
insert and then never touch it vacuum can skip most of the table 
(inserts are done at the end of the table, right?)

In response to


pgsql-performance by date

Next:From: Rod TaylorDate: 2004-04-30 00:44:16
Subject: Re: Insert only tables and vacuum performance
Previous:From: Joseph ShraibmanDate: 2004-04-29 23:19:09
Subject: why can't 2 indexes be used at once?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group