Re: Weird performance drop

From: "Dave Dutcher" <dave(at)tridecap(dot)com>
To: "'Vincenzo Romano'" <vincenzo(dot)romano(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Weird performance drop
Date: 2007-03-30 14:34:10
Message-ID: 01ea01c772d8$7b87aca0$2e00a8c0@tridecap.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> From: pgsql-performance-owner(at)postgresql(dot)org
> [mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of
> Vincenzo Romano
>
> Is there any "workaround"?
>
> In my opinion the later the query planner decisions are taken the more
> effective they can be.
> It could be an option for the function (body) to delay any
> query planner
> decision.

I think a possible workaround is to use a plpgsql function and the execute
statement. The docs will have more info.

Dave

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2007-03-30 16:13:00 Re: Wrong plan sequential scan instead of an index one
Previous Message Dimitri 2007-03-30 14:25:16 Re: Shared buffers, db transactions commited, and write IO on Solaris