Skip site navigation (1) Skip section navigation (2)

Re: Multiple Indexing, performance impact

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:02:45
Message-ID: 6081.993247365@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> This does remind me that I'd been thinking of suggesting that we
>> raise the default -B to something more reasonable, maybe 1000 or so
>> (yielding an 8-meg-plus shared memory area).

> BSD/OS has a 4MB max but we document how to increase it by recompiling
> the kernel.

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.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2001-06-22 22:06:38
Subject: Re: Multiple Indexing, performance impact
Previous:From: Tom LaneDate: 2001-06-22 21:58:39
Subject: Re: Extracting metadata about attributes from catalog

pgsql-general by date

Next:From: Bruce MomjianDate: 2001-06-22 22:06:38
Subject: Re: Multiple Indexing, performance impact
Previous:From: Bruce MomjianDate: 2001-06-22 21:56:46
Subject: Re: web site suggestion

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group