From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: Marius Andreiana <mandreiana@rdslink.ro>
Cc: pgsql-performance@postgresql.org
Subject: Re: NOT IN query takes forever
Date: Wed, 04 Aug 2004 09:32:53 +0800
Message-ID: <41103CC5.7030207@familyhealth.com.au> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB34101AF1A@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB34101AF1A@Herge.rcsinc.local>
> explain analyze actually runs the query to do timings. Just run explain
> and see what you come up with. More than likely there is a nestloop in
> there which is causing the long query time.
>
> Try bumping up shared buffers some and sort mem as much as you safely
> can.
Just use an EXISTS query I suggest.
Chris
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: chriskl@familyhealth.com.au, merlin.moncure@rcsonline.com, mandreiana@rdslink.ro
Subject: Re: NOT IN query takes forever
In-Reply-To: <41103CC5.7030207@familyhealth.com.au>
References: <6EE64EF3AB31D5448D0007DD34EEB34101AF1A@Herge.rcsinc.local> <41103CC5.7030207@familyhealth.com.au>
* 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