pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Jim C. Nasby <jim@nasby.net>
Cc: Craig A. James <cjames@modgraph-usa.com>
Cc: Brian Herlihy <btherl@yahoo.com.au>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: Simple join optimized badly?
Date: Tue, 10 Oct 2006 07:24:49 -0700
Message-ID: <452BAD31.3010507@commandprompt.com> (raw)
In-Reply-To: <20061010140702.GB72517@nasby.net>
References: <20061010011042.93217.qmail@web52308.mail.yahoo.com>
	<452B108C.7020703@modgraph-usa.com>
	<452B11FF.5020904@commandprompt.com>
	<20061010140702.GB72517@nasby.net>

Jim C. Nasby wrote:
> On Mon, Oct 09, 2006 at 08:22:39PM -0700, Joshua D. Drake wrote:
>>> Imagine I got run over by a train, and someone was reading my code. 
>>> Which would be easier for them to maintain: Code with weird SQL, or code
>>> with sensible, well-written SQL and explicit hints?
>> You forgot the most important option:
>>
>> Code with appropriate documentation about your weird SQL.
>>
>> If you document your code, your argument is moot.
> 
> You apparently didn't read the whole email. He said he did document his
> code. But his point is still valid: obscure code is bad even with
> documentation. Would you put something from the obfuscated C contest
> into production with comments describing what it does, or would you just
> write the code cleanly to begin with?

You are comparing apples to oranges. We aren't talking about an
obfuscated piece of code. We are talking about an SQL statement that
solves a particular problem.

That can easily be documented, and documented with enough verbosity that
it is never a question, except to test and see if the problem exists in
current versions.

Sincerely,

Joshua D. Drake



-- 

   === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
   Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/





view thread (56+ messages)  latest in thread

Message-ID: <452BAD31.3010507@commandprompt.com>
Permalink:  ../452BAD31.3010507@commandprompt.com/
Also on:    postgresql.org/message-id/452BAD31.3010507@commandprompt.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: jd@commandprompt.com, jim@nasby.net, cjames@modgraph-usa.com, btherl@yahoo.com.au
  Subject: Re: Simple join optimized badly?
  In-Reply-To: <452BAD31.3010507@commandprompt.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