Re: Insert only tables and vacuum performance - Mailing list pgsql-performance

From Rod Taylor
Subject Re: Insert only tables and vacuum performance
Date
Msg-id 1083285855.30065.462.camel@jester
Whole thread Raw
In response to Re: Insert only tables and vacuum performance  (Joseph Shraibman <jks@selectacast.net>)
Responses Re: Insert only tables and vacuum performance
List 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?



pgsql-performance by date:

Previous
From: Joseph Shraibman
Date:
Subject: why can't 2 indexes be used at once?
Next
From: Joseph Shraibman
Date:
Subject: Re: Insert only tables and vacuum performance