Re: 57 minute SELECT - Mailing list pgsql-performance

From Samuel Stearns
Subject Re: 57 minute SELECT
Date
Msg-id CB03CD8D2C3F9347BAFEC8EA9DD89C9318D37ACA@ISP-OSB-DAG2.win2k.iinet.net.au
Whole thread Raw
In response to Re: 57 minute SELECT  (David Johnston <polobo@yahoo.com>)
List pgsql-performance
Thanks, David.

Can't run EXPLAIN (ANALYZE, BUFFERS) as I'm on 8.4.


-----Original Message-----
From: pgsql-performance-owner@postgresql.org [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of David
Johnston
Sent: Thursday, 3 October 2013 11:19 AM
To: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] 57 minute SELECT

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
secondsinitially - 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
downprocessing. 

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


pgsql-performance by date:

Previous
From: David Johnston
Date:
Subject: Re: 57 minute SELECT
Next
From: Claudio Freire
Date:
Subject: Re: 57 minute SELECT