pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: SELECT's take a long time compared to other DBMS
Date: Wed, 03 Sep 2003 23:19:22 -0400
Message-ID: <m3ad9l6y11.fsf@chvatal.cbbrowne.com> (raw)
References: <bj611t$1o2g$1@news.hub.org>
	<3F569012.3090209@oasis.net.au>
	<bj647d$234o$1@news.hub.org>

Quoth "Relaxin" <me@yourhouse.com>:
> Yes I Analyze also, but there was no need to because it was a fresh
> brand new database.

That is _absolutely not true_.

It is not true with any DBMS that uses a cost-based optimizer.
Cost-based optimizers need some equivalent to ANALYZE in order to
collect statistics to allow them to pick any path other than a
sequential scan.

In this particular case, a seq scan is pretty likely to be the best
answer when there is no WHERE clause on the query.

Actually, it doesn't make all that much sense that the other systems
would be terribly much faster, because they obviously need to do some
processing on 102,384 records.

Can you tell us what you were *actually* doing?  Somehow it sounds as
though the other databases were throwing away the data whereas
PostgreSQL was returning it all "kawhump!" in one batch.

What programs were you using to submit the queries?
-- 
let name="cbbrowne" and tld="acm.org" in name ^ "@" ^ tld;;
http://cbbrowne.com/info/oses.html
"Computers let you make more  mistakes faster than any other invention
in  human  history,  with  the  possible  exception  of  handguns  and
tequila."  -- Mitch Radcliffe



view thread (34+ messages)  latest in thread

Message-ID: <m3ad9l6y11.fsf@chvatal.cbbrowne.com>
Permalink:  ../m3ad9l6y11.fsf@chvatal.cbbrowne.com/
Also on:    postgresql.org/message-id/m3ad9l6y11.fsf@chvatal.cbbrowne.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: SELECT's take a long time compared to other DBMS
  In-Reply-To: <m3ad9l6y11.fsf@chvatal.cbbrowne.com>
  References: <bj611t$1o2g$1@news.hub.org> <3F569012.3090209@oasis.net.au> <bj647d$234o$1@news.hub.org> <m3ad9l6y11.fsf@chvatal.cbbrowne.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