Re: [HACKERS] Re: ERROR: out of free buffers: time to abort !

From: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pghackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Re: ERROR: out of free buffers: time to abort !
Date: 2000-01-08 18:29:40
Message-ID: 38778214.E8D8F2B5@austin.rr.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> >> I am seeing the following error during a DB rebuild.

> >> ERROR: out of free buffers: time to abort !
> >>
> > This problem disappears when I up the number of shared mem buffers
> > with the -B flag from default of 64 to 256.
>
> That's the message you get if all the disk buffers are marked as
> "in use" (ref count > 0) so that there is noplace to read in another
> database page. I fixed several nasty buffer-ref-count-leakage bugs
> a couple of months ago, so I think this problem may be gone in current
> sources. (I'd appreciate it if you'd try this test case as soon as
> we are ready for 7.0 beta...)

Great. Thanks again, Tom.

> In the meantime, upping the number of buffers will at least postpone the
> problem. But I'm worried that it may not solve it completely --- you
> may still find that the error occurs after you've been running long
> enough.

Can I postpone/workaround the problem by periodic server restarts to reset
the counts? Or is this a persistent thing across server restarts?

Cheers,
Ed Loehr

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-01-08 18:58:54 Re: [HACKERS] Costs: Index vs Non-Index
Previous Message Tom Lane 2000-01-08 16:23:17 Re: [HACKERS] Another index "buglet"?