From: Tom Lane <tgl@sss.pgh.pa.us>
To: Diehl, Jeffrey <jdiehl@sandia.gov>
Cc: pgsql-sql@postgresql.org
Subject: Re: Out of free buffers... HELP!
Date: Tue, 30 Apr 2002 18:50:24 -0400
Message-ID: <2974.1020207024@sss.pgh.pa.us> (raw)
In-Reply-To: <369.1000942681@sss.pgh.pa.us>
References: <B51F0C636E578A4E832D3958690CD73E0130C03B@es04snlnt>
<369.1000942681@sss.pgh.pa.us>
[ digging through some old email ]
I wrote:
> "Diehl, Jeffrey" <jdiehl@sandia.gov> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, jdiehl@sandia.gov
Subject: Re: Out of free buffers... HELP!
In-Reply-To: <2974.1020207024@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox