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: Tobias Brox <tobias@nordicbet.com>
Cc: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Simple join optimized badly?
Date: Tue, 10 Oct 2006 07:23:30 -0700
Message-ID: <452BACE2.5010700@commandprompt.com> (raw)
In-Reply-To: <20061010140222.GA72517@nasby.net>
References: <20061009213303.GA19144@oppetid.no>
	<20061009223030.GW72517@nasby.net>
	<452AD005.1090101@commandprompt.com>
	<20061010140222.GA72517@nasby.net>

Jim C. Nasby wrote:
> On Mon, Oct 09, 2006 at 03:41:09PM -0700, Joshua D. Drake wrote:
>>> One of the big problems with doing set enable_...=off is that there's no
>>> way to embed that into something like a view, so you're almost forced
>>> into putting into the application code itself, which makes matters even
>>> worse. If you could hint this within a query (maybe even on a per-table
>>> level), you could at least encapsulate that into a view.
>> You can easily pass multiple statements within a single exec() or push
>> it into an SPF.
> 
> Unless I'm missing something, putting multiple statements in a single
> exec means you're messing with the application code. And you can't
> update a SRF (also means messing with the application code). Though, I
> suppose you could update a view that pulled from an SRF...

I always think of application code as outside the db. I was thinking
more in layers.

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: <452BACE2.5010700@commandprompt.com>
Permalink:  ../452BACE2.5010700@commandprompt.com/
Also on:    postgresql.org/message-id/452BACE2.5010700@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, tobias@nordicbet.com, cbbrowne@acm.org
  Subject: Re: Simple join optimized badly?
  In-Reply-To: <452BACE2.5010700@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