Re: Weird performance drop - Mailing list pgsql-performance

From Dave Dutcher
Subject Re: Weird performance drop
Date
Msg-id 01ea01c772d8$7b87aca0$2e00a8c0@tridecap.com
Whole thread Raw
In response to Re: Weird performance drop  (Vincenzo Romano <vincenzo.romano@gmail.com>)
Responses Re: Weird performance drop  (Vincenzo Romano <vincenzo.romano@gmail.com>)
List pgsql-performance
> From: pgsql-performance-owner@postgresql.org
> [mailto:pgsql-performance-owner@postgresql.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



pgsql-performance by date:

Previous
From: Dimitri
Date:
Subject: Re: Shared buffers, db transactions commited, and write IO on Solaris
Next
From: Tom Lane
Date:
Subject: Re: Wrong plan sequential scan instead of an index one