From: Richard Huxton <dev@archonet.com>
To: Eric Comeau <ecomeau@signiant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to get FK to use new index without restarting the database
Date: Thu, 16 Dec 2010 12:39:39 +0000
Message-ID: <4D0A088B.6020505@archonet.com> (raw)
In-Reply-To: <iecvmj$1j93$1@news.hub.org>
References: <iecvmj$1j93$1@news.hub.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dev@archonet.com, ecomeau@signiant.com
Subject: Re: How to get FK to use new index without restarting the database
In-Reply-To: <4D0A088B.6020505@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox