Rename heap_replace to heap_update.

src/backend/bootstrap/bootstrap.c

@@ -7,7 +7,7 @@
  * Copyright (c) 1994, Regents of the University of California
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/bootstrap/bootstrap.c,v 1.71 1999/11/07 23:07:59 momjian Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/bootstrap/bootstrap.c,v 1.72 1999/11/24 00:58:48 momjian Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -1159,7 +1159,7 @@ build_indices()
 		 * Unfortunately, there are always two indices defined on each
 		 * catalog causing us to update the same pg_class tuple twice for
 		 * each catalog getting an index during bootstrap resulting in the
-		 * ghost tuple problem (see heap_replace).	To get around this we
+		 * ghost tuple problem (see heap_update).	To get around this we
 		 * change the relhasindex field ourselves in this routine keeping
 		 * track of what catalogs we already changed so that we don't
 		 * modify those tuples twice.  The normal mechanism for updating

src/backend/utils/cache/syscache.c

@@ -7,7 +7,7 @@
  *
  *
  * IDENTIFICATION
- *	  $Header: /cvsroot/pgsql/src/backend/utils/cache/syscache.c,v 1.41 1999/11/22 17:56:32 momjian Exp $
+ *	  $Header: /cvsroot/pgsql/src/backend/utils/cache/syscache.c,v 1.42 1999/11/24 00:58:48 momjian Exp $
  *
  * NOTES
  *	  These routines allow the parser/planner/executor to perform
@@ -71,7 +71,7 @@ typedef HeapTuple (*ScanFunc) ();
     function names in the same order as the cache list for clarity.
 
     Finally, any place your relation gets heap_insert() or
-	heap_replace calls, include code to do a CatalogIndexInsert() to update
+	heap_update calls, include code to do a CatalogIndexInsert() to update
 	the system indexes.  The heap_* calls do not update indexes.
 	
     bjm 1999/11/22