pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Various performance questions
Date: 27 Oct 2003 10:09:09 -0500
Message-ID: <87oew2yay2.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <m3isman8qx.fsf@wolfe.cbbrowne.com>
References: <20031026194449.GD2979@rlx11.zapatec.com>
	<87u15vxrue.fsf@stark.dyndns.tv>
	<20031027045431.GE2979@rlx11.zapatec.com>
	<m3r80zmd1a.fsf@wolfe.cbbrowne.com>
	<20031027071703.GF2979@rlx11.zapatec.com>
	<m3isman8qx.fsf@wolfe.cbbrowne.com>

Christopher Browne <cbbrowne@acm.org> writes:

> In the last exciting episode, dror@zapatec.com (Dror Matalon) wrote:
> > I was answering an earlier response that suggested that maybe the actual
> > counting took time so it would take quite a bit longer when there are
> > more rows to count.

That was my theory. I guess it's wrong. There is other work involved in
processing a record, but i'm surprised it's as long as the work to actually
pull the record from kernel and check if it's visible.

> Well, if a "where clause" allows the system to use an index to search
> for the subset of elements, that would reduce the number of pages that
> have to be examined, thereby diminishing the amount of work.

it's not. therein lies the mystery.

> Why don't you report what EXPLAIN ANALYZE returns as output for the
> query with WHERE clause?  That would allow us to get more of an idea
> of what is going on...

He did, right at the start of the thread.

For a 1 million record table without he's seeing

 select 1 from tab
 select count(*) from tab

being comparable with only a slight delay for the count(*) whereas

 select 1 from tab where c < 1000
 select count(*) from tab where c < 1000

are much faster even though they still use a sequential scan.

I'm puzzled why the where clause speeds things up as much as it does.

-- 
greg




view thread (23+ messages)  latest in thread

Message-ID: <87oew2yay2.fsf@stark.dyndns.tv>
Permalink:  ../87oew2yay2.fsf@stark.dyndns.tv/
Also on:    postgresql.org/message-id/87oew2yay2.fsf@stark.dyndns.tv

 · 

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: gsstark@mit.edu, cbbrowne@acm.org
  Subject: Re: Various performance questions
  In-Reply-To: <87oew2yay2.fsf@stark.dyndns.tv>

* 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