From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Tobias Brox <tobias(at)nordicbet(dot)com>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Simple join optimized badly? |
Date: | 2006-10-10 14:02:22 |
Message-ID: | 20061010140222.GA72517@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-10-10 14:07:03 | Re: Simple join optimized badly? |
Previous Message | Jim C. Nasby | 2006-10-10 14:00:50 | Re: Simple join optimized badly? |