Re: 10x rowcount mis-estimation favouring merge over nestloop

From: Abhijit Menon-Sen <ams(at)oryx(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-performance(at)postgresql(dot)org, arnt(at)oryx(dot)com
Subject: Re: 10x rowcount mis-estimation favouring merge over nestloop
Date: 2006-11-10 07:07:00
Message-ID: 20061110070700.GA2751@penne.toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

At 2006-11-10 01:15:24 -0500, tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
>
> it seems that "field<=12" is true for a much smaller fraction of the
> rows satisfying (part!='' or value ilike '%,%') than for the general
> population of rows in the header_fields table.

Indeed. One-sixth of the rows in the entire table match field<=12, but
only one-fifteenth of the rows matching the part/value condition also
match field<=12.

> There's been some speculation about obtaining stats on partial indexes
> as a substitute for solving the general problem of correlation stats,

Oh. So my partial index's rowcount isn't being considered at all? That
explains a lot. Ok, I'll just run the query with mergejoin and seqscan
disabled. (I can't think of much else to do to speed it up, anyway.)

Thanks.

-- ams

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Ron Mayer 2006-11-10 18:54:01 Lying drives [Was: Re: Which OS provides the _fastest_ PostgreSQL performance?]
Previous Message Tom Lane 2006-11-10 06:15:24 Re: 10x rowcount mis-estimation favouring merge over nestloop