From: Joseph Shraibman <jks@selectacast.net>
To: pgsql-performance@postgresql.org
Subject: Re: Insert only tables and vacuum performance
Date: Thu, 29 Apr 2004 19:24:40 -0400
Message-ID: <c6s2rk$1qgd$1@news.hub.org> (raw)
In-Reply-To: <c6s1t4$1au1$1@news.hub.org>
References: <c6s1t4$1au1$1@news.hub.org>
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?)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jks@selectacast.net
Subject: Re: Insert only tables and vacuum performance
In-Reply-To: <c6s2rk$1qgd$1@news.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox