Dnia 2004-02-02 15:46, Uytkownik Rigmor Ukuhe napisa:
Hi,
I have many indexes somehow overlaping like:
... btree (STATUS, VISIBLE, NP_ID);
... btree (STATUS, VISIBLE);
is perfomance gained by more exact index worth overhead with managing
indexes.
The second (2 columns) index is useless - it's
On Mon, 2 Feb 2004, Tomasz Myrta wrote:
Dnia 2004-02-02 15:46, U?ytkownik Rigmor Ukuhe napisa3:
Hi,
I have many indexes somehow overlaping like:
... btree (STATUS, VISIBLE, NP_ID);
... btree (STATUS, VISIBLE);
is perfomance gained by more exact index worth overhead with managing
Dnia 2004-02-02 19:30, Uytkownik scott.marlowe napisa:
Not entirely, since it only has to sort two columns, it will be smaller,
and will therefore be somewhat faster.
Can you say something more about it? Will it be enough faster to keep
them both? Did anyone make such tests?
Regards,
Tomasz
On Mon, 2 Feb 2004, Tomasz Myrta wrote:
Dnia 2004-02-02 19:30, U¿ytkownik scott.marlowe napisa³:
Not entirely, since it only has to sort two columns, it will be smaller,
and will therefore be somewhat faster.
Can you say something more about it? Will it be enough faster to keep
them
On Mon, 2004-02-02 at 13:43, Tomasz Myrta wrote:
Dnia 2004-02-02 19:30, Uytkownik scott.marlowe napisa:
Not entirely, since it only has to sort two columns, it will be smaller,
and will therefore be somewhat faster.
Can you say something more about it? Will it be enough faster to keep
