Return-Path: owner-postman Received: from faerie.CS.Berkeley.EDU (faerie.CS.Berkeley.EDU [128.32.37.53]) by nobozo.CS.Berkeley.EDU (8.6.10/8.6.3) with ESMTP id OAA15167 for ; Fri, 3 Mar 1995 14:18:46 -0800 Received: from localhost.Berkeley.EDU (localhost.Berkeley.EDU [127.0.0.1]) by faerie.CS.Berkeley.EDU (8.6.10/8.6.3) with SMTP id OAA05918; Fri, 3 Mar 1995 14:18:12 -0800 Message-Id: <199503032218.OAA05918@faerie.CS.Berkeley.EDU> X-Authentication-Warning: faerie.CS.Berkeley.EDU: Host localhost.Berkeley.EDU didn't use HELO protocol From: aoki@CS.Berkeley.EDU (Paul M. Aoki) To: "V.Grabner" Cc: linux-postgres@native-ed.bc.ca, postgres-arch@postgres.Berkeley.EDU Subject: Re: SIMarkEntryData cache state reset Reply-To: aoki@CS.Berkeley.EDU (Paul M. Aoki) In-reply-to: Your message of Fri, 03 Mar 1995 12:20:13 +0100 Date: Fri, 03 Mar 95 14:18:11 -0800 Sender: aoki@postgres.Berkeley.EDU X-Mts: smtp "V.Grabner" writes: > NOTICE Mar 3 010834 SIMarkEntryData cache state reset this message is a NOTICE, which does not in itself cause an abort or a core dump or anything. this particular message simply means that the Shared Invalidation buffer overflowed -- "too many" metadata (catalog) updates occurred. when a given backend makes a catalog update, it places an invalidation message into a shared memory queue. this queue is read by the other servers when they commit their current transaction and is used to invalidate entries in the internal system metadata caches (e.g., pg_class and pg_attribute entries). an overflow means that everything will get invalidated and is typically caused by one or more servers sitting too long without committing. the other message (about the other backends exiting) is due to one or more backends having dumped core. the only way to know what happened there is to fire up gdb. -- Paul M. Aoki | University of California at Berkeley aoki@CS.Berkeley.EDU | Dept. of EECS, Computer Science Division (#1776) | Berkeley, CA 94720-1776