Re: index fragmentation on insert-only table with non-unique column - Mailing list pgsql-performance

From Tom Lane
Subject Re: index fragmentation on insert-only table with non-unique column
Date
Msg-id 969.1465142638@sss.pgh.pa.us
Whole thread Raw
In response to Re: index fragmentation on insert-only table with non-unique column  (Claudio Freire <klaussfreire@gmail.com>)
Responses Re: index fragmentation on insert-only table with non-unique column  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-performance
Claudio Freire <klaussfreire@gmail.com> writes:
> So correlated index scans look extra favourable vs bitmap index scans
> because bitmap heap scans consider random page costs sans correlation
> effects (even though correlation applies to bitmap heap scans as
> well).

Really?  How?  The index ordering has nothing to do with the order in
which heap tuples will be visited.

            regards, tom lane


pgsql-performance by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: index fragmentation on insert-only table with non-unique column
Next
From: Jeff Janes
Date:
Subject: Re: index fragmentation on insert-only table with non-unique column