From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(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:12:47 |
Message-ID: | 6150.993247967@sss.pgh.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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-06-22 22:22:48 | Re: Multiple Indexing, performance impact |
Previous Message | Bruce Momjian | 2001-06-22 22:06:38 | Re: Multiple Indexing, performance impact |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-06-22 22:22:48 | Re: Multiple Indexing, performance impact |
Previous Message | Bruce Momjian | 2001-06-22 22:06:38 | Re: Multiple Indexing, performance impact |