> This is still missing a bet since it fails to mention the option of
> adjusting -B and -N instead of changing kernel parameters, but that's
> easily fixed.  I propose that we reword this message and the semget
> one to mention first the option of changing -B/-N and second the option
> of changing kernel parameters.  Then we could consider raising the
> default -B setting to something more realistic.

Yes, we could do that but it makes things harder for newbies and really
isn't the right numbers for production use anyway.  I think anyone using
default values should see a message asking them to tune it.  Can we
throw a message during initdb?  Of course, we don't have a running
backend at that point so you would always throw a message.

From postmaster startup, by default, could we try larger amounts of
buffer memory until it fails then back off and allocate that?  Seems
like a nice default to me.


-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

• Re: Spinlock performance improvement proposal at 2001-10-01 16:19:06 from Tom Lane

Responses

• Re: Spinlock performance improvement proposal at 2001-10-01 18:55:25 from Tom Lane

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 2001-10-01 18:50:33
	Subject: Re: patch contrib/intarray to current CVS
Previous:	From: Thomas Lockhart	Date: 2001-10-01 18:46:03
	Subject: Re: CVS changes