Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 2E0324758E3 for ; Tue, 30 Apr 2002 18:50:25 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 38AEE475476 for ; Tue, 30 Apr 2002 18:50:24 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3UMoPF02977; Tue, 30 Apr 2002 18:50:25 -0400 (EDT) To: "Diehl, Jeffrey" Cc: pgsql-sql@postgresql.org Subject: Re: Out of free buffers... HELP! In-reply-to: <369.1000942681@sss.pgh.pa.us> References: <369.1000942681@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Wed, 19 Sep 2001 19:38:01 -0400" Date: Tue, 30 Apr 2002 18:50:24 -0400 Message-ID: <2974.1020207024@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/372 X-Sequence-Number: 7636 [ digging through some old email ] I wrote: > "Diehl, Jeffrey" writes: >> Brick* implies 1334 tables > Hmm ... I wonder if the query is somehow holding onto a buffer pin for > the last block of each successively-accessed table? Will look into it. I find that indeed 7.1 and older versions do that, but 7.2 does not (due to simplifications in heap_getnext). So this problem should be gone as of the current release. regards, tom lane