Re: Simple join optimized badly? - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: Simple join optimized badly?
Date
Msg-id 20061010140222.GA72517@nasby.net
Whole thread Raw
In response to Re: Simple join optimized badly?  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Simple join optimized badly?  ("Joshua D. Drake" <jd@commandprompt.com>)
List 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@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Simple join optimized badly?
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Simple join optimized badly?