Re: How to force Nested Loop plan?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net>
Cc: PgSQL Performance ML <pgsql-performance(at)postgresql(dot)org>
Subject: Re: How to force Nested Loop plan?
Date: 2003-09-01 21:03:17
Message-ID: 10675.1062450197@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> writes:
> How about (if you don't already do it) ranked (or approximately
> ranked) b-tree indexes, where each node also stores the (approximate)
> count of tuple pointers under it?
> This way, the planner would know whether or how skewed a tree is,
> and (approximately) how many tuples a given WHERE predicate resolves
> to.

Why is that better than our existing implementation of column statistics?

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Vivek Khera 2003-09-02 16:01:16 Re: Hardware recommendations to scale to silly load
Previous Message Ron Johnson 2003-09-01 15:22:47 Re: How to force Nested Loop plan?