Return-Path: postarch
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA22511; Wed, 22 Jul 92 09:05:12 -0700
Message-Id: <9207221605.AA22511@postgres.Berkeley.EDU>
From: postarch (Postgres Mailing Archive)
Subject: Re: out of free buffers - how to fix?
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
Reply-To: mer@postgres.berkeley.edu
In-Reply-To: Your message of "Thu, 02 Jul 92 05:32:18 PDT."
             <9207021232.AA06097@postgres.Berkeley.EDU> 
Date: Wed, 22 Jul 92 09:05:03 PDT

you write:
> When I try to delete I get:
> 
> route66% monitor imageindex
> Welcome to the C POSTGRES terminal monitor
> 
> Go 
> * delete FILE \g
> 
> Query sent to backend is "delete FILE "
> WARN:Jul  2 07:29:36:out of free buffers: time to abort !
> 
> Is there a workaround or better suggestion for this?

Version 3.1 had many "buffer leaks" where queries allocate
and "pin" a shared memory buffer more times than they release it.
This can lead to a severe shortage of free buffers.  The only
workaround I can suggest is to grab version 4, as we have now taken
care of this problem.


Jeff