From: Tom Lane <tgl@sss.pgh.pa.us>
To: nickf@ontko.com
Cc: pgsql-performance@postgresql.org
Subject: Re: SELECT's take a long time compared to other DBMS
Date: Thu, 04 Sep 2003 01:03:08 -0400
Message-ID: <14159.1062651788@sss.pgh.pa.us> (raw)
In-Reply-To: <NEBBLAAHGLEEPCGOBHDGOEBKIDAA.nickf@ontko.com>
References: <NEBBLAAHGLEEPCGOBHDGOEBKIDAA.nickf@ontko.com>
"Nick Fankhauser" <nickf@ontko.com> writes:
> This apparently wasn't the source of problem since he did an analyze anyway,
> but my impression was that a fresh brand new database is exactly the
> situation where an analyze is needed- ie: a batch of data has just been
> loaded and stats haven't been collected yet.
Indeed. But as someone else already pointed out, a seqscan is the only
reasonable plan for an unqualified "SELECT whatever FROM table" query;
lack of stats wouldn't deter the planner from arriving at that
conclusion.
My guess is that the OP is failing to account for some client-side
inefficiency in absorbing a large query result.
regards, tom lane
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: tgl@sss.pgh.pa.us, nickf@ontko.com
Subject: Re: SELECT's take a long time compared to other DBMS
In-Reply-To: <14159.1062651788@sss.pgh.pa.us>
References: <NEBBLAAHGLEEPCGOBHDGOEBKIDAA.nickf@ontko.com> <14159.1062651788@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