pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron Johnson <ron.l.johnson@cox.net>
To: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: How to force Nested Loop plan?
Date: Mon, 01 Sep 2003 10:22:47 -0500
Message-ID: <1062429767.7340.92.camel@haggis> (raw)
In-Reply-To: <29706.1062371570@sss.pgh.pa.us>
References: <16208.41885.960000.12706@gargle.gargle.HOWL>
	<24637.1062255721@sss.pgh.pa.us>
	<16208.50934.351000.90704@gargle.gargle.HOWL>
	<2074.1062260382@sss.pgh.pa.us>
	<16209.3105.94000.204936@gargle.gargle.HOWL>
	<4040.1062281441@sss.pgh.pa.us>
	<16209.15488.141000.729032@gargle.gargle.HOWL>
	<29706.1062371570@sss.pgh.pa.us>

On Sun, 2003-08-31 at 18:12, Tom Lane wrote:
> Rob Nagler <nagler@bivio.biz> writes:
> > Are there plans for explicit hints to the planner?
> 
> Personally, I'm philosophically opposed to planner hints; see previous
> discussions in the archives.

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.

-- 
-----------------------------------------------------------------
Ron Johnson, Jr. ron.l.johnson@cox.net
Jefferson, LA USA

"Fair is where you take your cows to be judged."
Unknown




view thread (13+ messages)  latest in thread

Message-ID: <1062429767.7340.92.camel@haggis>
Permalink:  ../1062429767.7340.92.camel@haggis/
Also on:    postgresql.org/message-id/1062429767.7340.92.camel@haggis

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: ron.l.johnson@cox.net
  Subject: Re: How to force Nested Loop plan?
  In-Reply-To: <1062429767.7340.92.camel@haggis>
  References: <16208.41885.960000.12706@gargle.gargle.HOWL> <24637.1062255721@sss.pgh.pa.us> <16208.50934.351000.90704@gargle.gargle.HOWL> <2074.1062260382@sss.pgh.pa.us> <16209.3105.94000.204936@gargle.gargle.HOWL> <4040.1062281441@sss.pgh.pa.us> <16209.15488.141000.729032@gargle.gargle.HOWL> <29706.1062371570@sss.pgh.pa.us> <1062429767.7340.92.camel@haggis>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox