pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joseph Shraibman <jks@selectacast.net>
To: Rod Taylor <pg@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Insert only tables and vacuum performance
Date: Thu, 29 Apr 2004 20:53:21 -0400
Message-ID: <4091A381.3020307@selectacast.net> (raw)
In-Reply-To: <1083285855.30065.462.camel@jester>
References: <c6s1t4$1au1$1@news.hub.org>
	<c6s2rk$1qgd$1@news.hub.org>
	<1083285855.30065.462.camel@jester>

Rod Taylor wrote:
>>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 if most of the table is never updated then the inserts would tend to 
be at the end, right?

> But anyway,
> how do you handle a rolled back insert?
> 
It is considered like a deleted row to be vacuumed.



view thread (7+ messages)  latest in thread

Message-ID: <4091A381.3020307@selectacast.net>
Permalink:  ../4091A381.3020307@selectacast.net/
Also on:    postgresql.org/message-id/4091A381.3020307@selectacast.net

 · 

reply

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, pg@rbt.ca
  Subject: Re: Insert only tables and vacuum performance
  In-Reply-To: <4091A381.3020307@selectacast.net>

* 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