From: Joshua Tolley <eggyknap@gmail.com>
To: Mladen Gogala <mladen.gogala@vmsinfo.com>
Cc: Craig Ringer <craig@postnewspapers.com.au>
Cc: Neil Whelchel <neil.whelchel@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Slow count(*) again...
Date: Sun, 10 Oct 2010 21:21:54 -0600
Message-ID: <4cb282d7.2405720a.5ca5.fffff05b@mx.google.com> (raw)
In-Reply-To: <4CB28123.5080300@vmsinfo.com>
References: <201010091626.18636.neil.whelchel@gmail.com>
<4CB11CC7.8070300@vmsinfo.com>
<4CB167CA.9070109@postnewspapers.com.au>
<4CB1F46E.80205@vmsinfo.com>
<4CB2410C.6010603@postnewspapers.com.au>
<4cb25a0e.2a978e0a.7797.33d6@mx.google.com>
<4CB28123.5080300@vmsinfo.com>
On Sun, Oct 10, 2010 at 11:14:43PM -0400, Mladen Gogala wrote:
> The fact is, however, that the question
> about slow sequential scan appears with some regularity on PostgreSQL
> forums.
Definitely. Whether that's because there's something pathologically wrong with
sequential scans, or just because they're the slowest of the common
operations, remains to be seen. After all, if sequential scans were suddenly
fast, something else would be the slowest thing postgres commonly did.
All that said, if there's gain to be had by increasing block size, or
something else, esp. if it's low hanging fruit, w00t.
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.comAttachments:
signature.asc (application/pgp-signature, 196B) download
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: eggyknap@gmail.com, mladen.gogala@vmsinfo.com, craig@postnewspapers.com.au, neil.whelchel@gmail.com
Subject: Re: Slow count(*) again...
In-Reply-To: <4cb282d7.2405720a.5ca5.fffff05b@mx.google.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