Message-ID: <3C5263F6.1BADDB0B@postgresql.org>
Date: Sat, 26 Jan 2002 19:08:22 +1100
From: Justin Clift <justin@postgresql.org>
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Zeugswetter Andreas SB SD <ZeugswetterA@spardat.at>,
	Vince Vielhaber <vev@michvhf.com>, pgsql-hackers@postgresql.org
Subject: Re: sequence indexes
References: <46C15C39FEB2C44BA555E356FBCD6FA42128E2@m0114.s-mxs.net>
	<6862.1011996346@sss.pgh.pa.us>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
> 
> "Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
> >> I've looked at the problem a little bit --- there's literature more
> >> recent than Lehmann-Yao that talks about how to do btree compaction
> >> without losing concurrency.  But it didn't get done for 7.2.
> 
> > Yes, there must be. Informix handles this case perfectly.
> > (It uses a background btree cleaner)

As an idle thought, I wonder what other maintenance tasks we could have
a process in the background automatically doing when system activity is
low ?

Maintenance
***********
- Index compaction
- Vacuum of various flavours

Tuning
******
- cpu_tuple costings (and similar) recalculation(s)


Can't think of anything else off the top of my head though.

Regards and best wishes,

Justin Clift

> 
> Right, I had hoped to fold it into lazy VACUUM, but ran out of time.
> (Of course, had I known in August that we'd still not have released
> 7.2 by now, I might have kept after it :-()
> 
>                         regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/users-lounge/docs/faq.html

-- 
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
   - Indira Gandhi