Not really. It was decided long ago that in that way madness lies. OTOH, there are ways to tune the behaviour through changes to random_page_cose, cpu_xxx_cost and effective_cache_size settings.
Then there's the mallet to the forebrain that are the set enable_nestloop=off type settings. They work, but they shouldn't be your first line of attack so much as a troubleshooting tool to figure out what pgsql might be getting wrong. On Mon, Jun 2, 2008 at 1:43 PM, John Cieslewicz <[EMAIL PROTECTED]> wrote: > I'm doing some performance experiments with postgres (8.3.1) and would like > to force postgres to execute a particular query plan. Is there a > straightforward way to specify a query plan to postgres either interactively > or programatically? > > Thanks. > > John Cieslewicz. > > -- > Sent via pgsql-general mailing list ([email protected]) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- Sent via pgsql-general mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
