pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Kirkwood <markir@paradise.net.nz>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Hints proposal
Date: Tue, 17 Oct 2006 01:34:30 +1300
Message-ID: <45337C56.8000209@paradise.net.nz> (raw)
In-Reply-To: <4532D17B.20106@modgraph-usa.com>
References: <78ED28FACE63744386D68D8A9D1CF5D4209CBF@MAIL.corp.lumeta.com>
	<4532D17B.20106@modgraph-usa.com>

Craig A. James wrote:
>
> 
> 2. Hints
>   a) On a aesthetic/theoretical level, hints suck.  They're ugly and rude
>   b) On a practical level, introducing hints will cause short- and 
> long-term problems
>   c) Hints would help DBAs solve urgent problems for which there is no 
> other solution

Pretty good summary!

Maybe there should be a 2d), 2e) and 2f).

2d) Hints will damage the ongoing development of the optimizer by 
reducing or eliminating test cases for its improvement.
2e) Hints will divert developer resource away from ongoing development 
of the optimizer.
2f) Hints may demoralize the developer community - many of whom will 
have been attracted to Postgres precisely because this was a realm where 
crude solutions were discouraged.

I understand that these points may seem a bit 'feel-good' and intangible 
- especially for the DBA's moving to Pg from Oracle, but I think they 
illustrate the mindset of the Postgres developer community, and the 
developer community is, after all - the primary reason why Pg is such a 
good product.

Of course - if we can find a way to define 'hint like' functionality 
that is more in keeping with the 'Postgres way' (e.g. some of the 
relation level statistical additions as discussed), then some of 2d-2f) 
need not apply.

Best wishes

Mark









view thread (74+ messages)  latest in thread

Message-ID: <45337C56.8000209@paradise.net.nz>
Permalink:  ../45337C56.8000209@paradise.net.nz/
Also on:    postgresql.org/message-id/45337C56.8000209@paradise.net.nz

 · 

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: markir@paradise.net.nz, cjames@modgraph-usa.com
  Subject: Re: Hints proposal
  In-Reply-To: <45337C56.8000209@paradise.net.nz>

* 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