Re: Multiple Indexing, performance impact

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Daniel Åkerud <zilch(at)home(dot)se>, PostgreSQL-general <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Multiple Indexing, performance impact
Date: 2001-06-22 22:22:48
Message-ID: 200106222222.f5MMMmx27786@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> Hmm. Anyone like the idea of a platform-specific default established
> >> by configure? We could set it in the template file on platforms where
> >> the default SHMMAX is too small to allow 1000 buffers.
>
> > Template file seems like a good idea for platforms that can't handle the
> > default. I don't think configure should be doing such tests because the
> > target could be a different kernel.
>
> Right, I wasn't thinking of an actual run-time test in configure, just
> that we could use it to let the OS-specific template file override the
> normal default.
>
> 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.

--
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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2001-06-22 23:04:19 Re: [GENERAL] [Help] Temporary Table: Implicitely created index not shown in \d i
Previous Message Tom Lane 2001-06-22 22:12:47 Re: Multiple Indexing, performance impact

Browse pgsql-hackers by date

  From Date Subject
Next Message Pedro Abelleira Seco 2001-06-22 23:01:42 RE: Universal admin frontend
Previous Message Tom Lane 2001-06-22 22:12:47 Re: Multiple Indexing, performance impact