Re: bad estimates
От
Christopher Kings-Lynne
Тема
Re: bad estimates
Дата
Msg-id
0bf301c36e05$a72f90b0$2800a8c0@mars
Список
Дерево обсуждения
bad estimates / non-scanning aggregates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates / non-scanning aggregates Bruno Wolff III <bruno@wolff.to>
Re: bad estimates / non-scanning aggregates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates / non-scanning aggregates Bruno Wolff III <bruno@wolff.to>
Re: bad estimates / non-scanning aggregates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates / non-scanning aggregates Bruno Wolff III <bruno@wolff.to>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Bruno Wolff III <bruno@wolff.to>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Bruno Wolff III <bruno@wolff.to>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Jeff <threshar@torgo.978.org>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Bruno Wolff III <bruno@wolff.to>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Tom Lane <tgl@sss.pgh.pa.us>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Stephan Szabo <sszabo@megazone.bigpanda.com>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Sean Chittenden <sean@chittenden.org>
Re: bad estimates Ken Geis <kgeis@speakeasy.org>
Re: bad estimates Sean Chittenden <sean@chittenden.org>
> > I went through the code (7.4 beta2) that estimates the cost of an index > > scan path. What I need to be sure of is that when running a query in > > pgsql that uses only the columns that are in an index, the underlying > > table need not be accessed. I know that Oracle does this. PostgreSQL absolutely does not do this. It is also not possible to do this due to MVCC. Chris
В списке pgsql-performance по дате отправления
От: Shridhar Daithankar
Дата: