pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL and Linux 2.6 kernel.
Date: Fri, 16 Apr 2004 08:24:46 +0100
Message-ID: <KGEFLMPJFBNNLNOOOPLGKEPACHAA.simon@2ndquadrant.com> (raw)
In-Reply-To: <200404151339.45615.josh@agliodbs.com>


>Josh Berkus
> > Treating the optimizer as a black box is something I'm very
> used to from
> > other RDBMS. My question is, how can you explicitly
> re-write a query now
> > to "improve" it? If there's no way of manipulating queries without
> > actually re-writing the optimizer, we're now in a position where we
> > aren't able to diagnose when the optimizer isn't working
> effectively.
>
> Well, there is ... all of the various query cost parameters.

They are very blunt instruments for such a delicate task.

Surely someone of your experience might have benefit from something
more?

My feeling is, I would, though I want those tools as *a developer*
rather than for tuning specific queries for people, which is always so
sensitive to upgrades etc.

> But, ultimately, improvements on the planner are still
> bottlenecked by having
> only one developer actually hacking the changes.
>

Do we have a clear list of optimizations we'd like to be working on?

The TODO items aren't very related to specific optimizations...

The only ones I was aware of was deferred subselect evaluation for
DBT-3.



...sounds like there's more to discuss here, so I'll duck out now and
get back to my current project...

Best Regards, Simon Riggs




view thread (34+ messages)

Message-ID: <KGEFLMPJFBNNLNOOOPLGKEPACHAA.simon@2ndquadrant.com>
Permalink:  ../KGEFLMPJFBNNLNOOOPLGKEPACHAA.simon@2ndquadrant.com/
Also on:    postgresql.org/message-id/KGEFLMPJFBNNLNOOOPLGKEPACHAA.simon@2ndquadrant.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: simon@2ndquadrant.com, josh@agliodbs.com
  Subject: Re: PostgreSQL and Linux 2.6 kernel.
  In-Reply-To: <KGEFLMPJFBNNLNOOOPLGKEPACHAA.simon@2ndquadrant.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