public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Chris Browne <[email protected]>
Cc: [email protected]
Subject: Re: [DOCS] Autovacuum and XID wraparound
Date: Mon, 14 May 2007 18:16:19 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<1179117269.6047.3.camel@goldbach>
	<[email protected]>

Chris Browne wrote:

> Would the following 'maintenance' regimen be truly safe against XID
> wraparound:
> 
>  - Most tables are being vacuumed regularly, so that
>    pg_class.relfrozenxid is kept "safe."
> 
>  - There are some tables that periodically get TRUNCATEd so that, in
>    principle, they never need to be vacuumed.
> 
> Is it actually true that we'd never need to vacuum those tables
> (assuming 8.2+)?  I suppose it would be rather cheap to VACUUM
> immediately after the TRUNCATE...

You'd need to vacuum after the truncate.  It would be pretty cheap, the
tables being empty.

I suppose it would be pretty trivial to set the relfrozenxid to
RecentXmin or something during TRUNCATE.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

view thread (34+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [DOCS] Autovacuum and XID wraparound
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox