Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37]) by hub.org (8.9.3/8.9.3) with ESMTP id VAA41070; Sun, 18 Jul 1999 21:56:38 -0400 (EDT) (envelope-from vadim@krs.ru) Received: from krs.ru (dune.krs.ru [195.161.16.38]) by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id JAA06318; Mon, 19 Jul 1999 09:56:26 +0800 (KRSS) Sender: root@sunpine.krs.ru Message-ID: <379285C8.BE592155@krs.ru> Date: Mon, 19 Jul 1999 09:56:24 +0800 From: Vadim Mikheev Organization: OJSC Rostelecom (Krasnoyarsk) X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Wayne Piekarski CC: pgsql-sql@postgreSQL.org, pgsql-hackers@postgreSQL.org Subject: Re: [HACKERS] Fix up for BTP_CHAIN problems References: <199907170340.NAA10098@helpdesk.senet.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Wayne Piekarski wrote: > > The indexes grew a little bit, but now we have not had *ANY* BTP_CHAIN > faults at all, and to test it we really thrashed the machine to see if we > could cause it to die. It worked perfectly and we were all really happy > because BTP_CHAIN was very annoying to fix up. It was occuring a lot when > the machine was under high load. ^^^^^^^^^^^^^^^ Hiroshi made patch for this case. This patch is in 6.5. I should post it to general list and put on ftp... sorry. I'll do it today. Vadim