locking/backend interaction problems may not be duplicated.<P>
Another method is to start <I>psql</I> in one window, then find the
-<small>PID</small> of the <i>postgres</i> process being used by the
+<small>PID</small> of the <i>postgres</i> process used by
<i>psql.</i> Use a debugger to attach to the <i>postgres</i>
-<small>PID.</small> You can set breakpoints in the debugger and issues
-queries from <i>psql.</i>
+<small>PID.</small> You can set breakpoints in the debugger and issue
+queries from <i>psql.</i> If you are debugging <i>postgres</i> startup,
+you can set PGOPTIONS="-W n", then start <i>psql.</i> This will cause
+startup to delay for <i>n</i> seconds so you can attach with the
+debugger and trace through the startup sequence.<P>
The postgres program has -s, -A, and -t options that can be very useful
for debugging and performance measurements.<P>
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/utils/cache/inval.c,v 1.36 2000/05/30 00:49:54 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/utils/cache/inval.c,v 1.37 2000/06/08 19:51:03 momjian Exp $
*
* Note - this code is real crufty...
*
"ImmediateInvalidateSharedHeapTuple");
}
+#ifdef NOT_USED
/*
* ImmediateSharedRelationCacheInvalidate
* Register shared relation cache invalidation immediately
RelationIdImmediateRegisterSharedInvalid(
RelOid_pg_class, RelationGetRelid(relation));
}
+#endif
* Portions Copyright (c) 1996-2000, PostgreSQL, Inc
* Portions Copyright (c) 1994, Regents of the University of California
*
- * $Id: inval.h,v 1.16 2000/01/26 05:58:38 momjian Exp $
+ * $Id: inval.h,v 1.17 2000/06/08 19:51:06 momjian Exp $
*
*-------------------------------------------------------------------------
*/
extern void ImmediateInvalidateSharedHeapTuple(Relation relation, HeapTuple tuple);
-extern void ImmediateSharedRelationCacheInvalidate(Relation relation);
-
#endif /* INVAL_H */