pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Craig A. James <cjames@modgraph-usa.com>
To: pgsql-performance@postgresql.org
Subject: Re: Overriding the optimizer
Date: Thu, 15 Dec 2005 19:38:36 -0800
Message-ID: <43A236BC.1070300@modgraph-usa.com> (raw)
In-Reply-To: <43A2327C.8000206@familyhealth.com.au>
References: <200512141603.52583.blargity@gmail.com>
	<7484.1134600423@sss.pgh.pa.us>
	<1134629567.14248.27.camel@firebolt>
	<200512150148.16125.blargity@gmail.com>
	<1134644526.14248.60.camel@firebolt>
	<43A1C40D.8040006@paradise.net.nz>
	<43A1F6DB.3080805@modgraph-usa.com>
	<43A21D74.8030002@familyhealth.com.au>
	<c2d9e70e0512151800l5561fc04q7ee79593dcb4ea5c@mail.gmail.com>
	<43A2203B.2050102@familyhealth.com.au>
	<43A2251A.60907@modgraph-usa.com>
	<43A227BE.9030106@familyhealth.com.au>
	<43A23079.8060307@modgraph-usa.com>
	<43A2327C.8000206@familyhealth.com.au>

Christopher Kings-Lynne wrote:
> So your main example bad query is possibly just a case of lack of 
> analyze stats and wrong postgresql.conf config?  And that's what causes 
> you to shut down your database?  Don't you want your problem FIXED?

I'm trying to help by raising a question that I think is important, and have an honest, perhaps vigorous, but respectful, discussion about it.  I respect everyone's opinion, and I hope you respect mine.  I've been in this business a long time, and I don't raise issues lightly.

Yes, I want my query fixed.  And I may post it, in a thread with a new title.  In fact, I posted a different query with essentially the same problem a while back and got nothing that helped:

    http://archives.postgresql.org/pgsql-performance/2005-11/msg00133.php

(I can't help but point out that Tom's response was to suggest a way to fool the optimizer so as to prevent it from "optimizing" the query.  In other words, he told me a trick that would force a particular plan on the optimizer.  Which is exactly the point of this discussion.)

The point is that the particular query is not relevant -- it's the fact that this topic (according to Tom) has been and continues to be raised.  This should tell us all something, that it's not going to go away, and that it's a real issue.

Regards,
Craig



view thread (41+ messages)  latest in thread

Message-ID: <43A236BC.1070300@modgraph-usa.com>
Permalink:  ../43A236BC.1070300@modgraph-usa.com/
Also on:    postgresql.org/message-id/43A236BC.1070300@modgraph-usa.com

 · 

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: cjames@modgraph-usa.com
  Subject: Re: Overriding the optimizer
  In-Reply-To: <43A236BC.1070300@modgraph-usa.com>

* 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