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

From: Richard Huxton <dev(at)archonet(dot)com>
To: Eric Comeau <ecomeau(at)signiant(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: How to get FK to use new index without restarting the database
Date: 2010-12-16 12:39:39
Message-ID: 4D0A088B.6020505@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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 get postgres to use the new
> index for the FK cascade delete without bouncing the database.

Well, an ongoing DELETE isn't going to see a new index. I'd have thought
a new connection should though.

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Eric Comeau 2010-12-16 12:55:46 Re: How to get FK to use new index without restarting the database
Previous Message Richard Huxton 2010-12-16 12:37:50 Re: performance libpq vs JDBC