On Thursday, May 30, 2013 11:36 PM Josh Berkus wrote:
Amit,
I think it might be because of choosing custom plan option due to
which it might be generating new plan during exec_bind_message().
exec_bind_message()-GetCachedPlan()-choose_custom_plan(). If it
chooses custom plan, then it will
Two questions Please1.) Is there any way to clear the cache so that we can ensure that when we run "explain analyze" on a query and make some minor adjustments to that query and re-execute, the plan is not cached. Since the cached plan returns runtimes that are much lower than the initial
On Fri, May 31, 2013 at 7:32 PM, fburg...@radiantblue.com wrote:
1.) Is there any way to clear the cache so that we can ensure that when we
run explain analyze on a query and make some minor adjustments to that
query and re-execute, the plan is not cached.
PostgreSQL doesn't cache query plans
When you say interactively, does it mean that you are using psql to test the
same?
Yes. Of course, on the psql command line, there's no separate BIND
step, just PREPARE and EXECUTE.
From the changes, it doesn't seem that any of such changes can cause the
problem you have seen.
No, but
On Wednesday, May 29, 2013, Niels Kristian Schjødt wrote:
Hi,
I have a database with quite some data (millions of rows), that is heavily
updated all the time. Once a day I would like to reindex my database (and
maybe re cluster it - don't know if that's worth it yet?). I need the
database
