Reference pgAdmin as a typical client-side tool, rather than the

no-longer-maintained PgAccess.  Per Erik Rijkers.

doc/src/sgml/plpgsql.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.122 2007/12/03 23:49:50 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/plpgsql.sgml,v 1.123 2008/01/23 02:04:47 tgl Exp $ -->
 
 <chapter id="plpgsql"> 
   <title><application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language</title>
@@ -3474,7 +3474,7 @@ $$ LANGUAGE plpgsql;
     Another good way to develop in <application>PL/pgSQL</> is with a
     GUI database access tool that facilitates development in a
     procedural language. One example of such as a tool is
-    <application>PgAccess</>, although others exist. These tools often
+    <application>pgAdmin</>, although others exist. These tools often
     provide convenient features such as escaping single quotes and
     making it easier to recreate and debug functions.
    </para>

doc/src/sgml/start.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/start.sgml,v 1.45 2007/06/21 10:43:09 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/start.sgml,v 1.46 2008/01/23 02:04:47 tgl Exp $ -->
 
  <chapter id="tutorial-start">
   <title>Getting Started</title>
@@ -298,7 +298,7 @@ createdb: database creation failed: ERROR:  permission denied to create database
      <listitem>
       <para>
        Using an existing graphical frontend tool like
-       <application>PgAccess</application> or an office suite with
+       <application>pgAdmin</application> or an office suite with
        <acronym>ODBC</acronym> support to create and manipulate a
        database.  These possibilities are not covered in this
        tutorial.