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

Re: Insert only tables and vacuum performance

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Joseph Shraibman <jks(at)selectacast(dot)net>
Cc: Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Insert only tables and vacuum performance
Date: 2004-04-30 00:44:16
Message-ID: 1083285855.30065.462.camel@jester (view raw or flat)
Thread:
Lists: pgsql-performance
> 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?)

Inserts are done at the end of the table as a last resort. But anyway,
how do you handle a rolled back insert?



In response to

Responses

pgsql-performance by date

Next:From: Joseph ShraibmanDate: 2004-04-30 00:53:21
Subject: Re: Insert only tables and vacuum performance
Previous:From: Joseph ShraibmanDate: 2004-04-29 23:24:40
Subject: Re: Insert only tables and vacuum performance

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