Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Realtime VACUUM, was: performance of insert/delete/update

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Nicolai Tufar" <ntufar(at)apb(dot)com(dot)tr>,<pgsql-hackers(at)postgresql(dot)org>,"PgSQL Performance ML" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: [HACKERS] Realtime VACUUM, was: performance of insert/delete/update
Date: 2002-11-27 15:09:59
Message-ID: 03AF4E498C591348A42FC93DEA9661B8128C8C@mail.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-performance

> -----Original Message-----
> From: Nicolai Tufar [mailto:ntufar(at)apb(dot)com(dot)tr] 
> Sent: 27 November 2002 14:02
> To: pgsql-hackers(at)postgresql(dot)org; PgSQL Performance ML
> Subject: Re: [PERFORM] [HACKERS] Realtime VACUUM, was: 
> performance of insert/delete/update
> 
> 
> I always wandered if VACUUM is the right name for the 
> porcess. Now, when PostgreSQL is actively challenging in 
> Enterprise space, it might be a good idea to give it a more 
> enterprise-like name. Try to think how it is looking for an 
> outside person to see us, database professionals hold lenghty 
> discussions about the ways we vacuum a database. Why should 
> you need to vacuum a database? Is it dirty? In my personal 
> opinion, something like "space reclaiming daemon", "free-list 
> organizer", "tuple recyle job" or "segment coalesce process" 
> would sound more business-like .

As inspired by the SQL Server Enterprise Manager I've just been swearing
at:

"Database Optimizer"

Regards, Dave.

pgsql-performance by date

Next:From: Tommi MaekitaloDate: 2002-11-27 15:34:04
Subject: Re: [PERFORM] Realtime VACUUM, was: performance of insert/delete/update
Previous:From: ThrasherDate: 2002-11-27 14:52:20
Subject: Child process procedures

pgsql-hackers by date

Next:From: Manfred KoizarDate: 2002-11-27 15:11:55
Subject: Re: nested transactions
Previous:From: Jim BeckstromDate: 2002-11-27 14:43:01
Subject: Re: [HACKERS] Realtime VACUUM, was: performance of insert/delete/update

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group