From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jaime Casanova <el_vigia_ec@hotmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: select slow?
Date: Wed, 31 Mar 2004 10:40:21 -0500
Message-ID: <5090.1080747621@sss.pgh.pa.us> (raw)
In-Reply-To: <BAY8-F7R0ZJi4W8StO00001d4b4@hotmail.com>
References: <BAY8-F7R0ZJi4W8StO00001d4b4@hotmail.com>
"Jaime Casanova" <el_vigia_ec@hotmail.com> writes:
> There are no indexes yet, and the table is just 6 rows long so even if
> indexes exists the planner will do a seq scan. that's my whole point 63m for
> seq scan in 6 rows table is too much.
That was 63 milliseconds, according to your original post, which seems
perfectly reasonable to me seeing that it's not a super-duper server.
The problem sounds to be either on the client side or somewhere in your
network. I don't know anything about VB, but you might want to look
through the client-side operations to see what could be eating up the 13
seconds.
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, el_vigia_ec@hotmail.com
Subject: Re: select slow?
In-Reply-To: <5090.1080747621@sss.pgh.pa.us>
References: <BAY8-F7R0ZJi4W8StO00001d4b4@hotmail.com> <5090.1080747621@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