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

no-longer-maintained PgAccess.  Per Erik Rijkers.

diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index 50ce18f1a7483412948f68812b1cbaf1154f9136..7fe8723a4e22ddd1a6e334a039297a8a2d28a855 100644 (file)
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -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>

diff --git a/doc/src/sgml/start.sgml b/doc/src/sgml/start.sgml
index ef394a7810af046bde15bf1b11935c1e43bd4fe9..4e0cc0f52a55cbf0dcc8ffb6407321408b870174 100644 (file)
--- a/doc/src/sgml/start.sgml
+++ b/doc/src/sgml/start.sgml
@@ -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.