pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marius Andreiana <mandreiana@rdslink.ro>
To: pgsql-performance@postgresql.org
Subject: Re: NOT IN query takes forever
Date: Tue, 03 Aug 2004 19:02:42 +0300
Message-ID: <1091548963.6915.2.camel@marte.biciclete.ro> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB34101AF1A@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB34101AF1A@Herge.rcsinc.local>

On Tue, 2004-08-03 at 08:05 -0400, Merlin Moncure wrote:
> > Trying to run this query:
> > EXPLAIN ANALYSE
> > select * FROM trans
> > WHERE query_id NOT IN (select query_id FROM query)
> > 
> > but it will remain like that forever (cancelled after 30 min).
> 
> 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.
Thank you, that did it!

With
shared_buffers = 3000		# min 16, at least max_connections*2, 8KB each
sort_mem = 128000		# min 64, size in KB

it takes <3 seconds (my hardware is not server-class).

-- 
Marius Andreiana
Galuna - Solutii Linux in Romania
http://www.galuna.ro




view thread (10+ messages)  latest in thread

Message-ID: <1091548963.6915.2.camel@marte.biciclete.ro>
Permalink:  ../1091548963.6915.2.camel@marte.biciclete.ro/
Also on:    postgresql.org/message-id/1091548963.6915.2.camel@marte.biciclete.ro

 · 

reply

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: mandreiana@rdslink.ro
  Subject: Re: NOT IN query takes forever
  In-Reply-To: <1091548963.6915.2.camel@marte.biciclete.ro>

* 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