Received: from candle.pha.pa.us (216-55-132-35.dsl.san-diego.abac.net [216.55.132.35]) by postgresql.org (Postfix) with ESMTP id 58F00475AD1; Wed, 3 Apr 2002 14:07:46 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id g33J7f212383; Wed, 3 Apr 2002 14:07:41 -0500 (EST) From: Bruce Momjian Message-Id: <200204031907.g33J7f212383@candle.pha.pa.us> Subject: Re: [SQL] Logging option In-Reply-To: <005a01c1db20$2771f260$110a010a@headquarters.wcgroup.com> To: "Samuel J. Sutjiono" Date: Wed, 3 Apr 2002 14:07:41 -0500 (EST) Cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL97 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200204/123 X-Sequence-Number: 22846 Samuel J. Sutjiono wrote: > Does anybody know how to prevent this message from being displayed on the screen ? (I just want this message to be logged in the log file). The other question is how do you control the types of error to log ? > > NOTICE: Message from PostgreSQL backend: > The Postmaster has informed me that some other backend died abnormally and possibly corrupted shared memory. > I have rolled back the current transaction and am going to terminate your database system connection and exit. > Please reconnect to the database system and repeat your query. > > I appreciate your help. > In 7.3, you will be able to suppress all WARNING messages to the client with client_min_messages, but in 7.2.X there is no way except modifying postgres.c. Sorry. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026