X-Original-To: pgsql-performance-postgresql.org@postgresql.org
Received: from localhost (mx1.hub.org [200.46.208.251])
	by postgresql.org (Postfix) with ESMTP id 3C3279FA5E7
	for <pgsql-performance-postgresql.org@postgresql.org>;
	Thu, 15 Jun 2006 16:43:19 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024)
	with ESMTP id 40641-09 for
	<pgsql-performance-postgresql.org@postgresql.org>;
	Thu, 15 Jun 2006 16:43:12 -0300 (ADT)
X-Greylist: domain auto-whitelisted by SQLgrey-
Received: from hu-out-0102.google.com (hu-out-0102.google.com [72.14.214.195])
	by postgresql.org (Postfix) with ESMTP id 528AD9FA13E
	for <pgsql-performance@postgresql.org>;
	Thu, 15 Jun 2006 16:43:11 -0300 (ADT)
Received: by hu-out-0102.google.com with SMTP id 34so173756hui
	for <pgsql-performance@postgresql.org>;
	Thu, 15 Jun 2006 12:43:10 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=ZzcENxrXGfkBgGvJlZcUGprFWMfHklwafETyXmd3XsOdPD9v41hSBWwhgt1bFApwEbXQIECQYwGqVkRcuQbYgB0vcsMuyxKJEdfUyi6aNOnqJhrY355gFYBGLLPu3ch5XKAd5YtLp0jUxR6b0SMpmc2UtMwVUKX72DlyPnP4KOQ=
Received: by 10.67.97.7 with SMTP id z7mr2044923ugl;
	Thu, 15 Jun 2006 12:43:09 -0700 (PDT)
Received: by 10.66.216.11 with HTTP; Thu, 15 Jun 2006 12:43:09 -0700 (PDT)
Message-ID: <c841561b0606151243m1e55841fkdc10bfcb2a1d1ff9@mail.gmail.com>
Date: Thu, 15 Jun 2006 15:43:09 -0400
From: "John Vincent" <pgsql-performance@lusis.org>
Reply-To: pgsql-performance@lusis.org
To: "PGSQL Performance" <pgsql-performance@postgresql.org>
Subject: Re: Optimizer internals
In-Reply-To: <c841561b0606151221v219987aap376194583dd30940@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_10291_18445274.1150400589686"
References: <c841561b0606151105v459d830era158b9eea5f59a7e@mail.gmail.com>
	<1150396425.31200.66.camel@archimedes>
	<c841561b0606151146j5f8410f2qaeaff7649b70cd20@mail.gmail.com>
	<1150398064.31200.76.camel@archimedes>
	<c841561b0606151221v219987aap376194583dd30940@mail.gmail.com>
X-Google-Sender-Auth: 07abb7d66f7e48f8
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200606/326
X-Sequence-Number: 19683

------=_Part_10291_18445274.1150400589686
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

> Any suggestions? FYI the original question wasn't meant as a poke at
> comparing PG to MySQL to DB2. I'm not making an yvalue judgements either
> way. I'm just trying to understand how we can use it the best way possible.
>
> If anyone from the bizgres team is watching, have they done any work in
> this area?
>
> Thanks.
> John
>

Actually we just thought about something. With PG, we can create an index
that is a SUM of the column where indexing, no? We're going to test this in
a few hours. Would that be able to be satisfied by an index scan?

Also, we're looking at the link provided for the materialized views in PG.

Thanks.

------=_Part_10291_18445274.1150400589686
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>Any suggestions? FYI the original question wasn't meant as a poke at comparing PG to MySQL to DB2. I'm not making an yvalue judgements either way. I'm just trying to understand how we can use it the best way possible.
<br><br>If anyone from the bizgres team is watching, have they done any work in this area? <br><br>Thanks.<br></div><div><span class="sg">John<br>

</span></div></blockquote></div><br>Actually we just thought about something. With PG, we can create
an index that is a SUM of the column where indexing, no? We're going to
test this in a few hours. Would that be able to be satisfied by an
index scan?
<br><br>Also, we're looking at the link provided for the materialized views in PG.<br><br>Thanks.<br>

------=_Part_10291_18445274.1150400589686--