public inbox for
help / color / mirror / Atom feed
From: Patrick Macdonald <>
To: Announce List <>
Subject: Administrator 2.0 Alpha / Visual Explain 2.0 Beta
Date: Thu, 27 Feb 2003 21:01:00 -0000	[thread overview]
Message-ID: <> (raw)

First things first: the "Red Hat Database Project" is now known as 
the "PostgreSQL - Red Hat Edition Project" to align ourselves with 
other groups within Red Hat.  New name - same project and team.

And now on to the important stuff.

The latest development version of the PostgreSQL - Red Hat Edition
Graphical Tools Suite is available for checkout.  The Administrator
is still under development (with respect to PostgreSQL 7.3 support)
so we're calling it an alpha.  Visual Explain is functionally 
complete so it's being released as a beta.  The tools have been 
tested on Red Hat Linux Advanced Server 2.1 and Red Hat Linux 8.0 
using PostgreSQL 7.3 / 7.2 backends.  

The Administrator and Visual Explain source code can be checked out
from our cvs repository at

Enhancements to the tools include, but are not limited to:

Administrator 2.0-Alpha
 . Limited support for new functionality introduced in PostgreSQL 7.3 
   backends (schemas, operator classes, etc)
 . Table Data Viewer to browse data 
 . Increased tool navigation capabilities
 . Import / Export support
 . Full privilege support

Visual Explain 2.0-Beta
 . Full support for PostgreSQL 7.3 backends
 . Ability to save and restore resultant plans 
 . Stop button provided to halt Explain / Explain Analyze thread
 . Support for modifying GUC variables   
 . Tooltips for tree nodes show total time or cost 
 . Additional node information (node time, percentile of time, etc)


                 reply	other threads:[~2003-02-27 21:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

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

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).