Re: Re: [GENERAL] Multiple Indexing, performance impact - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Re: [GENERAL] Multiple Indexing, performance impact
Date
Msg-id 200106230004.f5N04iK08743@candle.pha.pa.us
Whole thread Raw
In response to Re: [GENERAL] Multiple Indexing, performance impact  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> >> We could offer a --with switch to manually choose the default, too.
>
> > Good idea, yes.  Not sure if we need a --with switch because they can
> > just edit the postgresql.conf or postgresql.conf.sample file.
>
> Well, we have a --with switch for DEF_MAXBACKENDS, so one for the
> default number of buffers doesn't seem too unreasonable.  I wouldn't
> bother with it if configure didn't have to touch the value anyway...
> but it's just another line or two in configure.in...

Yes, we could add that too, but now that we have postgresql.conf should
we even be mentioning stuff like that in configure.  In the old days we
had a compiled-in limit but that is not true anymore, right?

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

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [GENERAL] Multiple Indexing, performance impact
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCH] by request: base64 for bytea