Re: Insert only tables and vacuum performance
Rod Taylor <pg@rbt.ca>
From: Rod Taylor <pg@rbt.ca>
To: Joseph Shraibman <jks@selectacast.net>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Date: 2004-04-30T00:44:16Z
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?