Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id E76461337999 for ; Mon, 11 Oct 2010 00:22:12 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 17228-07 for ; Mon, 11 Oct 2010 03:22:03 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pz0-f46.google.com (mail-pz0-f46.google.com [209.85.210.46]) by mail.postgresql.org (Postfix) with ESMTP id 9BA1B1336705 for ; Mon, 11 Oct 2010 00:22:01 -0300 (ADT) Received: by pzk34 with SMTP id 34so901828pzk.19 for ; Sun, 10 Oct 2010 20:22:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:cc :subject:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=QqKhjcoF5bzQoklBohw3TDVAf7vtpEU3359rAYFfLfo=; b=mdYXyO/OzOg5tZyEBy0aTcoXzO/7CugqWRksOBTzp0CWVrpdHty2B/KXCzWZD/qLNx UWxBodMRFXHIyodX37w1JOfKU9sdYvpWmLhQpRB0UVJfKPro4gUl4xwROMiiTt1w70nT DGOip/l4TkgBlkTtJQPmmr2U52jQKudeQFzuw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:cc:subject:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Z2qF6ObDtxGvb5quJu50TqoTzpZJ+jh2+dwT4wJvaqNRDXimaBYVC5zjX+9wxHJfxV F5nMIB/corXFa4GWI5tIVkOSYg0kF6tn+hGgmIPE1m+wrh3I2TeKrTNlS0Q9Dwp32QK2 kENizOkuDUjJcm7N/sgzP8qVxiPKpOmi2JG7k= Received: by 10.114.111.5 with SMTP id j5mr6445636wac.28.1286767321167; Sun, 10 Oct 2010 20:22:01 -0700 (PDT) Received: from eddie (c-67-186-249-122.hsd1.ut.comcast.net [67.186.249.122]) by mx.google.com with ESMTPS id 36sm8594340wae.4.2010.10.10.20.21.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 10 Oct 2010 20:21:59 -0700 (PDT) Message-ID: <4cb282d7.2405720a.5ca5.fffff05b@mx.google.com> Date: Sun, 10 Oct 2010 21:21:54 -0600 From: Joshua Tolley To: Mladen Gogala Cc: Craig Ringer , Neil Whelchel , "pgsql-performance@postgresql.org" Subject: Re: Slow count(*) again... 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> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IR1Y5IvQhrKgS4e6" Content-Disposition: inline In-Reply-To: <4CB28123.5080300@vmsinfo.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201010/106 X-Sequence-Number: 40525 --IR1Y5IvQhrKgS4e6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 10, 2010 at 11:14:43PM -0400, Mladen Gogala wrote: > The fact is, however, that the question =20 > about slow sequential scan appears with some regularity on PostgreSQL =20 > forums. Definitely. Whether that's because there's something pathologically wrong w= ith 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.com --IR1Y5IvQhrKgS4e6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkyygtIACgkQRiRfCGf1UMP+MQCdEGCMY44nj1jv6psepbNlY1QC OOYAoINH4ZtVv5L22gXTRj7pbvRHeAVQ =IB+V -----END PGP SIGNATURE----- --IR1Y5IvQhrKgS4e6--