> -----Original Message----- > From: Nicolai Tufar [mailto:[EMAIL PROTECTED]] > Sent: 27 November 2002 14:02 > To: [EMAIL PROTECTED]; 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. ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
