IMHO, it is worth duplicating the mvcc data to all index entries. To
summarize what I understand from this discussion, with the current
method:
a1 - Index seeks must return invisible tuples because mvcc data is not
found in the index. These tuples are eliminated once the data is read
from the actu
> > where productname is in the product table, and lotname in the lot
> > table. I would be interested in creating an index such as
>
> > CREATE INDEX ix_vw_lot ON vw_lot (lotname, productname);
>
> What purpose would this serve that indexes on the separate tables
> wouldn't serve?
>
> > The ind
against
lot the lot and inventory tables.
-Tiago
On Mon, 06 Sep 2004 10:17:24 -0700, Joshua D. Drake
<[EMAIL PROTECTED]> wrote:
>
>
> Tiago Wright wrote:
>
> >Are there any plans to support indexed views, or cross-table indexes,
> >or any form of "materialize
Are there any plans to support indexed views, or cross-table indexes,
or any form of "materialized views" in postgresql? How complex would
the implementation be? Indexed views are sometimes the best way to
improve the performance of complex queries.
-Tiago
---(end of broad
