pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mikko Partio <mpartio@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Slow indexscan
Date: Wed, 20 Jun 2007 15:29:54 -0400
Message-ID: <29484.1182367794@sss.pgh.pa.us> (raw)
In-Reply-To: <2ca799770706200943l6ae9f6bfif54683e21fa33f35@mail.gmail.com>
References: <2ca799770706200702y1074f066s61279b67f93315d0@mail.gmail.com>
	<17907.1182352197@sss.pgh.pa.us>
	<2ca799770706200855w1a6b6a7cy8526b9be0ef9c97c@mail.gmail.com>
	<18952.1182355276@sss.pgh.pa.us>
	<2ca799770706200943l6ae9f6bfif54683e21fa33f35@mail.gmail.com>

"Mikko Partio" <mpartio@gmail.com> writes:
> I guess the sort_mem helped, or then part of the rows are in the cache
> already. Should increasing sort_mem help here since there are no sorts etc?

No, it wouldn't --- this change has to be due to the data being already
loaded into cache.

There's no obvious reason for the previous query to be so slow, unless
you've got horrendously slow or overloaded disk hardware.  What sort of
machine is this anyway, and was it doing any other work at the time?

			regards, tom lane



view thread (11+ messages)  latest in thread

Message-ID: <29484.1182367794@sss.pgh.pa.us>
Permalink:  ../29484.1182367794@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29484.1182367794@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, mpartio@gmail.com
  Subject: Re: Slow indexscan
  In-Reply-To: <29484.1182367794@sss.pgh.pa.us>

* 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