Re: 10x rowcount mis-estimation favouring merge over nestloop - Mailing list pgsql-performance

From Abhijit Menon-Sen
Subject Re: 10x rowcount mis-estimation favouring merge over nestloop
Date
Msg-id 20061110070700.GA2751@penne.toroid.org
Whole thread Raw
In response to Re: 10x rowcount mis-estimation favouring merge over nestloop  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
At 2006-11-10 01:15:24 -0500, tgl@sss.pgh.pa.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

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: 10x rowcount mis-estimation favouring merge over nestloop
Next
From: Ron Mayer
Date:
Subject: Lying drives [Was: Re: Which OS provides the _fastest_ PostgreSQL performance?]