Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Fri, 30 Mar 2007 09:34:10 -0500
> 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
- References:
- Re: Weird performance drop
- From: Vincenzo Romano
- Re: Weird performance drop
- Prev by Date: Re: Shared buffers, db transactions commited, and write IO on Solaris
- Next by Date: Re: Wrong plan sequential scan instead of an index one
- Previous by thread: Re: Weird performance drop
- Next by thread: Scaling SELECT:s with the number of disks on a stripe
- Indexes: