From: David Johnston <polobo@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: Re: 57 minute SELECT
Date: Wed, 2 Oct 2013 18:48:41 -0700 (PDT)
Message-ID: <1380764921339-5773187.post@n5.nabble.com> (raw)
In-Reply-To: <CB03CD8D2C3F9347BAFEC8EA9DD89C9318D379E4@ISP-OSB-DAG2.win2k.iinet.net.au>
References: <CB03CD8D2C3F9347BAFEC8EA9DD89C9318D3785F@ISP-OSB-DAG2.win2k.iinet.net.au>
<1380763034169-5773174.post@n5.nabble.com>
<CB03CD8D2C3F9347BAFEC8EA9DD89C9318D379A1@ISP-OSB-DAG2.win2k.iinet.net.au>
<CB03CD8D2C3F9347BAFEC8EA9DD89C9318D379E4@ISP-OSB-DAG2.win2k.iinet.net.au>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Samuel Stearns-2 wrote
> EXPLAIN:
>
> QUERY PLAN
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Hash Join (cost=408.53..1962721.39 rows=98068 width=126) (actual
> time=30121.265..3419306.752 rows=1929714 loops=1)
You are selecting and returning 2 million records...how fast do you want
this to run? For some reason I read 57 seconds initially - I guess 57
minutes is a bit much...but the most obvious solution is RAM.
Might want to include buffers output in the explain as well but:
I'm doubting the contents of your result fit into the server memory so your
disk is involved which will severely slow down processing.
Hopefully someone more knowledgeable and experience will chime in to help
you.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/57-minute-SELECT-tp5773169p5773187.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: polobo@yahoo.com
Subject: Re: 57 minute SELECT
In-Reply-To: <1380764921339-5773187.post@n5.nabble.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