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

From Joshua D. Drake
Subject Re: Simple join optimized badly?
Date
Msg-id 452AD005.1090101@commandprompt.com
Whole thread Raw
In response to Re: Simple join optimized badly?  ("Jim C. Nasby" <jim@nasby.net>)
Responses Re: Simple join optimized badly?  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-performance
>
> 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.

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/



pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Simple join optimized badly?
Next
From: Tom Lane
Date:
Subject: Re: Simple join optimized badly?