[SOLVED] Re: Timestamp indicies not being used!
От | Pedro Doria Meunier |
---|---|
Тема | [SOLVED] Re: Timestamp indicies not being used! |
Дата | |
Msg-id | 4A636866.2040808@netmadeira.com обсуждение исходный текст |
Ответ на | Re: Timestamp indicies not being used! (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First of all *thank* you very much to all that replied! :) Sam's suggestion actually did the trick! I created the multi-column index and the stalling went away. Yay! Best regards, Pedro Doria Meunier GSM: +351 96 17 20 188 Skype: pdoriam Tom Lane wrote: > Andreas Kretschmer <akretschmer@spamfence.net> writes: >> Sam Mason <sam@samason.me.uk> wrote: >>> Based on your query, I think you want a multi-column >>> index---probably on (id,zulu_timestamp). >>> >>> The problem with just having an index on either column is that >>> it's difficult to combine them and PG hence just thinks that it >>> will be > >> Since 8.1 PG can do an bitmap index scan using both indexes... > > ... which produces an unordered result, so it's pretty useless for > this problem. I concur with Sam's suggestion. > > regards, tom lane > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFKY2hd2FH5GXCfxAsRAjj7AJ4lGNmNuwPUuTv6EwZ8s2faZcOASACgka8P aE4vwzcy3cIdbEyFtYWTjAw= =I5Jv -----END PGP SIGNATURE-----
В списке pgsql-general по дате отправления: