pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jim@nasby.net>
To: Jeff Davis <pgsql@j-davis.com>
Cc: Bucky Jordan <bjordan@lumeta.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: josh@agliodbs.com
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] Hints proposal
Date: Fri, 13 Oct 2006 12:30:24 -0500
Message-ID: <20061013173024.GE28647@nasby.net> (raw)
In-Reply-To: <1160760211.31966.231.camel@dogma.v10.wvs>
References: <78ED28FACE63744386D68D8A9D1CF5D4209CBD@MAIL.corp.lumeta.com>
	<1160760211.31966.231.camel@dogma.v10.wvs>

On Fri, Oct 13, 2006 at 10:23:31AM -0700, Jeff Davis wrote:
> Right. And I think the sane ideas are along the lines of estimate & cost
> corrections (like Tom is saying).

Let me ask this... how long do you (and others) want to wait for those?
It's great that the planner is continually improving, but it also
appears that there's still a long road ahead. Having a dune-buggy to get
to your destination ahead of the road might not be a bad idea... :)
-- 
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



view thread (74+ messages)  latest in thread

Message-ID: <20061013173024.GE28647@nasby.net>
Permalink:  ../20061013173024.GE28647@nasby.net/
Also on:    postgresql.org/message-id/20061013173024.GE28647@nasby.net

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: jim@nasby.net, pgsql@j-davis.com, bjordan@lumeta.com, alvherre@commandprompt.com, josh@agliodbs.com, pgsql-hackers@postgresql.org
  Subject: Re: [PERFORM] Hints proposal
  In-Reply-To: <20061013173024.GE28647@nasby.net>

* 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