From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-hackers(at)postgresql(dot)org, "Robert Treat" <xzilla(at)users(dot)sourceforge(dot)net>, "Decibel!" <decibel(at)decibel(dot)org>, "Christopher Browne" <cbbrowne(at)gmail(dot)com> |
Subject: | Re: [PATCHES] Better default_statistics_target |
Date: | 2008-02-01 15:50:16 |
Message-ID: | 24107.1201881016@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> On Thu, Jan 31, 2008 at 10:19 PM, in message
> <200801312319(dot)59723(dot)xzilla(at)users(dot)sourceforge(dot)net>, Robert Treat
> <xzilla(at)users(dot)sourceforge(dot)net> wrote:
>> Bad plans from boosting to 100 or less? Or something much higher?
> I boosted on a large number of columns based on domains. County
> number columns (present in most tables) were set to 80. Some
> columns were set all the way to 1000. When performance tanked, we
> didn't have time to experiment, so we just backed it all out.
> Perhaps I could do some more controlled testing soon against 8.3,
> to narrow it down and confirm the current status of the issue. I
> do seem to recall that simple queries weren't suffering, it was
> those which joined many tables which had multiple indexes.
That fits with the idea that eqjoinsel() is a main culprit.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-02-01 16:01:56 | Re: FW: bitemporal functionality for PostgreSQL |
Previous Message | Tom Lane | 2008-02-01 15:47:34 | Re: Limit changes query plan |
From | Date | Subject | |
---|---|---|---|
Next Message | Luke Lonergan | 2008-02-02 17:53:27 | Re: Bitmap index scan preread using posix_fadvise (Was: There's random access and then there's random access) |
Previous Message | Kevin Grittner | 2008-02-01 15:18:00 | Re: [PATCHES] Better default_statistics_target |