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

From Tom Lane
Subject Re: [GENERAL] Multiple Indexing, performance impact
Date
Msg-id 6007.993246769@sss.pgh.pa.us
Whole thread Raw
Responses Re: [GENERAL] Multiple Indexing, performance impact  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Strange that even at 1024 performance still drops off at 7.  Seems it
> may be more than buffer thrashing.

Yeah, if anything the knee in the curve seems to be worse at 1024
buffers.  Curious.  Deserves more investigation, perhaps.

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).  This wouldn't prevent
people from setting it small if they have a small SHMMAX, but it's
probably time to stop letting that case drive our default setting.
Since 64 is already too much to let 7.1 fit in SHMMAX = 1MB, I think
the original rationale for using 64 is looking pretty broken anyway.
Comments?

            regards, tom lane

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] Multiple Indexing, performance impact
Next
From: Tom Lane
Date:
Subject: Re: Extracting metadata about attributes from catalog