Re: [PATCH] Don't bail with legitimate -N/-B options

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net>, Andreas Kling <andreas(dot)kling(at)acgnystrom(dot)se>
Subject: Re: [PATCH] Don't bail with legitimate -N/-B options
Date: 2008-03-07 21:09:10
Message-ID: 26805.1204924150@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> Anyway, it seems that we cannot raise the minimum value of
> shared_buffers to 200, or even 100, unless we are prepared to blow off
> SHMMAX = 2MB or do something about the fixed SLRU allocation.

After further thought I propose that we just eliminate the interlock
between -N and -B. I don't think it's accomplishing anything very
useful (for sure it's not enough to guarantee that you can't run out of
pinnable buffers), and the addition of the autovac worker processes
makes the whole thing too confusing to be helpful.

I am still interested in a TODO of increasing the minimum allowed value
of shared_buffers, but that's really an independent issue. And we can't
do very much there anyway until after eliminating the fixed-size-SLRU-
buffers problem.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Joseph S 2008-03-07 21:31:00 BUG #4020: RFE: have way to log autovacuum activity
Previous Message Bruce Momjian 2008-03-07 20:39:13 Re: [BUGS] BUG #3829: Wrong index reporting from pgAdmin III (v1.8.0 rev 6766-6767)