Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f21Fjxx52999 for ; Thu, 1 Mar 2001 10:45:59 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f21Fjq921218; Thu, 1 Mar 2001 10:45:52 -0500 (EST) To: Blaise Carrupt cc: pgsql-sql@postgresql.org Subject: Re: BufTableDelete: BufferLookup table corrupted In-reply-to: <200103011304.NAA16646@mjtsa.com> References: <200103011304.NAA16646@mjtsa.com> Comments: In-reply-to Blaise Carrupt message dated "Thu, 01 Mar 2001 13:04:55 +0000" Date: Thu, 01 Mar 2001 10:45:52 -0500 Message-ID: <21215.983461552@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/7 X-Sequence-Number: 1648 Blaise Carrupt writes: > When I connect to database (with psql, e.g.), I receive the message > 'FATAL 1: BufTableDelete: BufferLookup table corrupted'. Try restarting the postmaster. AFAICS your problems are just with datastructures in shared memory, so a postmaster restart should clean them up. If you can figure out the sequence of actions that produced this state in the first place, please file a bug report with details ... regards, tom lane