> leonbloy@sinectis.com.ar wrote:
> >
> > => explain select max(rid) from facturas;
> > NOTICE: QUERY PLAN:
> >
> > Aggregate (cost=21139.66 rows=342414 width=4)
> > -> Seq Scan on facturas (cost=21139.66 rows=342414 width=4)
> >
> > I understand that the query planner cannot be so clever
> > to grasp that this particular function (max or min)
> > might be evaluated by just travelling the BTREE index.
> > Am I correct?
>
> I believe you are unfortunately correct. :(
That would be a good optimization. Let me add it to the TODO list.
Much better than trying to keep the max stored somewhere.
--
Bruce Momjian | http://www.op.net/~candle
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026