Re: [PERFORM] How to get FK to use new index without restarting the database

2010-12-17 Thread Eric Comeau
On 10-12-16 11:27 AM, Tom Lane wrote: Eric Comeau writes: > Is there a way force the db to re-evaluate its execution plan for a FK > without bouncing the DB? > PostgreSQL 8.1.17 You don't need to bounce

Re: [PERFORM] How to get FK to use new index without restarting the database

2010-12-16 Thread Eric Comeau
On 10-12-16 11:27 AM, Tom Lane wrote: Eric Comeau writes: Is there a way force the db to re-evaluate its execution plan for a FK without bouncing the DB? PostgreSQL 8.1.17 You don't need to bounce the whole DB, but you will need to start fresh sessions. We didn't add automatic invalida

Re: [PERFORM] How to get FK to use new index without restarting the database

2010-12-16 Thread Tom Lane
Eric Comeau writes: > Is there a way force the db to re-evaluate its execution plan for a FK > without bouncing the DB? > PostgreSQL 8.1.17 You don't need to bounce the whole DB, but you will need to start fresh sessions. We didn't add automatic invalidation of those plans until 8.3.

Re: [PERFORM] How to get FK to use new index without restarting the database

2010-12-16 Thread Eric Comeau
On 10-12-16 07:34 AM, Jayadevan M wrote: Hello, Is there a way force the db to re-evaluate its execution plan for a FK without bouncing the DB? PostgreSQL 8.1.17 In our latest release our developers have implemented some new foreign keys but forgot to create indexes on these keys. The prob

Re: [PERFORM] How to get FK to use new index without restarting the database

2010-12-16 Thread Richard Huxton
On 16/12/10 12:12, Eric Comeau wrote: The problem surfaced at one of our client installs where a maintenance DELETE query was running for over 24 hrs. We have since then identified the missing indexes and have sent the client a script to create them, but in our testing we could not been able to

Re: [PERFORM] How to get FK to use new index without restarting the database

2010-12-16 Thread Jayadevan M
Hello, > Is there a way force the db to re-evaluate its execution plan for a FK > without bouncing the DB? > > PostgreSQL 8.1.17 > > In our latest release our developers have implemented some new foreign > keys but forgot to create indexes on these keys. > > The problem surfaced at one of ou