From: Jim C. Nasby <jnasby@pervasive.com>
To: John Vincent <pgsql-performance@lusis.org>
Cc: PGSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Optimizer internals
Date: Thu, 15 Jun 2006 17:23:45 -0500
Message-ID: <20060615222344.GB93655@pervasive.com> (raw)
In-Reply-To: <c841561b0606151243m1e55841fkdc10bfcb2a1d1ff9@mail.gmail.com>
References: <c841561b0606151105v459d830era158b9eea5f59a7e@mail.gmail.com>
<1150396425.31200.66.camel@archimedes>
<c841561b0606151146j5f8410f2qaeaff7649b70cd20@mail.gmail.com>
<1150398064.31200.76.camel@archimedes>
<c841561b0606151221v219987aap376194583dd30940@mail.gmail.com>
<c841561b0606151243m1e55841fkdc10bfcb2a1d1ff9@mail.gmail.com>
On Thu, Jun 15, 2006 at 03:43:09PM -0400, John Vincent wrote:
> >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.
decibel=# create index test on i ( sum(i) );
ERROR: cannot use aggregate function in index expression
decibel=#
BTW, there have been a number of proposals to negate the effect of not
having visibility info in indexes. Unfortunately, none of them have come
to fruition yet, mostly because it's a very difficult problem to solve.
But it is something that the community would like to see happen.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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: jnasby@pervasive.com, pgsql-performance@lusis.org
Subject: Re: Optimizer internals
In-Reply-To: <20060615222344.GB93655@pervasive.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